Except that you explicitly and repeatedly whined every time you brought it up that Elecraft wasn't willing to do those things, and in my opinion they have zero obligation and little practical reason to do so. If you want someone to maintain such a database, do so yourself (or talk somebody else into it) without getting all moralistic about it. It might be important to you, but it isn't important for Elecraft to do it for you.
Dave AB7E On 2/16/2017 11:02 PM, Joe Stone (KF5WBO) wrote:
It's important that we have visibility not only into features in the pipeline, but also proposed features which have been rejected.Why? [js] {hypothetically} I have an idea for a new feature, P3 mouse support. Before proposing the feature on the Elecraft mailing list, I first go to the Elecraft feature / defect tracking system and search for "mouse". I find a feature called, "Mouse-n-Click QSY". I see the feature was created on December 16, 2011 by Dave Perry (N4QS). According to the feature description, Dave replied to a thread titled "P3SVGA - Coming soon" authored by Eric Swartz (WA6HHQ). Dave replied, "SVGA display looks great. Will we also have point and click capability with a mouse?" I further discover the feature has been closed with the disposition, "The P3 doesn’t have the MIPS to sample IQ, process the 1024-point FFT, update the displays (spectrum and waterfall), field remote-control commands, … and position a marker based on the delta-X field in a mouse HID descriptor.” Oh well, it was a great idea. But I see due to technical limitations, the P3 isn't capable of mouse support. Yes Joe, why should you be privvy to proprietary Elecraft information? [js] We're not talking about proprietary information. We're talking about features and defects raised by the Elecraft user community. We're talking about the same features and defects discussed on this mailing list every day. The same system may track "top-secret" features which aren't exposed to the public. The system may serve to track internally discovered defects which aren't exposed to the public (e.g., defects corresponding to an unreleased firmware version). Even publicly-visible features and defects will have some fields and attributes which aren't exposed to the public (e.g., assigned engineer, effort estimate, test plan, ...). This is all standard, vanilla stuff. -- View this message in context: http://elecraft.365791.n2.nabble.com/Tracking-Elecraft-Feature-Requests-tp7626877p7627033.html Sent from the Elecraft mailing list archive at Nabble.com. ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[email protected] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to [email protected]
______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[email protected] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to [email protected]
