[Elecraft] Tracking Elecraft Feature Requests

[Harry Yingst]

It should be hosted by Elecraft.


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.



      From: John <john at eeek.org.uk>
 To: 'Joe Stone (KF5WBO)' <kf5wbo at wickedbeernut.com>; elecraft at mailman.qth.net 
 Sent: Tuesday, February 14, 2017 10:23 AM
 Subject: Re: [Elecraft] Tracking Elecraft Feature Requests
   
Joe,

Why limit it just to list subscribers? Surely there are those out there who
may want a specific feature, but are not part of this list and don't wish to
be (for whatever reason) but may still own an Elecraft item?

Where are you planning to post these? Who's going to host whatever website
it is?

Just my £0.02

73, and a firm left handshake,
John (XLX)

-----Original Message-----
From: Elecraft [mailto:elecraft-bounces at mailman.qth.net] On Behalf Of Joe
Stone (KF5WBO)
Sent: 14 February 2017 15:14
To: elecraft at mailman.qth.net
Subject: [Elecraft] Tracking Elecraft Feature Requests

It would be nice if we could track Elecraft feature requests in a more
structured manner.  The same feature requests come up over and over again. 
We often hear, "Elecraft will never develop feature X unless N users ask for
the feature."  Rather than having subscribers respond to the Elecraft email
list saying, "Count me in", "Me too", ... why not allow subscribers to
express interest in a proposed feature by adding their name / callsign to a
"feature logbook"?  One logbook per feature request.  Logbooks would be
organized (tagged) by Elecraft product.  Each logbook would include fields
such as:

    Created by
    Created on
    Abstract
    Description
    Applicable Elecraft products
    Disposition 
    Disposition updated on
    ...

We wouldn't need to burden Elecraft with maintaining the logbooks.  We could
designate a few admins.  We would need a means of authenticating a
subscriber (e.g., Elecraft email list username / password, QRZ.com username
/ password, ...).  Any subscriber could create a new feature logbook or an
admin could create a logbook on a subscriber's behalf.  An admin would
update a logbook disposition to reflect feedback from Elecraft (e.g.,
"planned for release R", "rejected due to technical limitation T", "under
consideration", ...).  An admin would reconcile duplicate / overlapping
logbooks.  Subscribers would only express interest in a proposed feature
(not disinterest).  Comments, questions and concerns regarding a proposed
feature would be reconciled through the Elecraft email list and reflected /
updated in the logbook description by the Creator or an admin.

Thoughts?

Joe
KF5WBO



--
View this message in context:
http://elecraft.365791.n2.nabble.com/Tracking-Elecraft-Feature-Requests-tp76
26877.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 john at eeek.org.uk

______________________________________________________________
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 hlyingst at yahoo.com