[Elecraft] Tracking Elecraft Feature Requests

[Joe Stone (KF5WBO)]

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-tp7626877.html
Sent from the Elecraft mailing list archive at Nabble.com.