[Elecraft] Tracking Elecraft Feature Requests

[Phil Hystad]

Managing feature requests is traditional with software products.  I worked in software for 45
years prior to retirement and even started a company where enhancements to the various
products were very important to our customer base.

We had a feature request web site that we hosted and licensed customers had access to this
web site.  Prior to the web site, from 1970s to 1990s, we managed feature requests by paper
in the same manner of a customer submitting a bug report and reviewed such features with
customers during the annual user group meetings.

Given that radios, and in particular Elecraft gear, is almost just as much a software system
as hardware that such feature request management should be encouraged by Elecraft and
accessed via their http://elecraft.com web site  although not necessarily hosted by elecraft.com
since I am not sure how they manage their web site.  Access should be to anyone who has an 
Elecraft rig identified by serial number since I think being assigned login credentials should
be granted to owners only.  Yes, I know that there are Elecraft productst that do not have
serial numbers but they also are likely not to be generating feature requests anyway.

My two-bits.

73, phil, K7PEH


> On Feb 14, 2017, at 9:04 AM, Walter Underwood <wunder at wunderwood.org> wrote:
> 
> The Jira issue tracker supports voting.
> 
> http://blogs.atlassian.com/2013/09/jira-tip-of-the-month-crowdsourcing-issue-triage/ <http://blogs.atlassian.com/2013/09/jira-tip-of-the-month-crowdsourcing-issue-triage/>
> 
> wunder
> Walter Underwood
> wunder at wunderwood.org
> http://observer.wunderwood.org/  (my blog)
> 
> 
>> On Feb 14, 2017, at 8:56 AM, Joe Stone (KF5WBO) <kf5wbo at wickedbeernut.com> wrote:
>> 
>> It should be hosted by Elecraft. 
>> 
>> [js] That would be ideal.
>> 
>> I have another radio (mcHF) that the developers take request and implement
>> changes, it's actually a nice feature since you can see what is being
>> requested and to a degree the status of the request.
>> 
>> [js] Of course, new feature requests wouldn't be limited to software /
>> firmware.  Subscribers could request new hardware features (e.g., internal
>> KX3 lithium-ion battery pack, PX3 HDMI video adapter, KX2 real time clock +
>> RX I/Q board, ...).
>> 
>> [js] It's important that we have visibility not only into features in the
>> pipeline, but also proposed features which have been rejected.
>> 
>> Joe
>> KF5WBO
>> 
>> 
>> 
>> --
>> View this message in context: http://elecraft.365791.n2.nabble.com/Tracking-Elecraft-Feature-Requests-tp7626877p7626890.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:Elecraft at mailman.qth.net
>> 
>> This list hosted by: http://www.qsl.net
>> Please help support this email list: http://www.qsl.net/donate.html
>> Message delivered to wunder at wunderwood.org
> 
> ______________________________________________________________
> Elecraft mailing list
> Home: http://mailman.qth.net/mailman/listinfo/elecraft
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:Elecraft at mailman.qth.net
> 
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html
> Message delivered to phystad at mac.com