Re: [Elecraft] Tracking Elecraft Feature Requests

February 2017 14:11 To: elecraft@mailman.qth.net Subject: [Elecraft] Tracking Elecraft Feature Requests I agree fully with Don and Dave (messages below) and others who have made similar points. To me it's very simple: We are customers, not shareholders. There are features I wish their products

[Elecraft] Tracking Elecraft Feature Requests

acking Elecraft Feature Requests Message-ID: <8c06109e-9e67-081c-ca5d-838185010...@embarqmail.com> Content-Type: text/plain; charset=windows-1252; format=flowed I agree with Kevin's "Why" Tell me of another amateur radio manufacturer who maintains such a list.

Re: [Elecraft] Tracking Elecraft Feature Requests

I agree with Kevin's "Why" Tell me of another amateur radio manufacturer who maintains such a list. This is *not* open source programming. If such a list exists for any other amateur radio manufacturer, they would come out with an "improved" new radio (Mark VI) version and if you wanted the

Re: [Elecraft] Tracking Elecraft Feature Requests

Why? On 2/14/2017 10:56 AM, Joe Stone (KF5WBO) wrote: [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 -- R. Kevin Stover AC0H ARRL FISTS #11993 SKCC #215 NAQCC #3441 --- This email has

Re: [Elecraft] Tracking Elecraft Feature Requests

In a competitive business environment especially where you are viewed as an innovator, having a public prioritized list of potential new features could negatively impact a company. I think Elecraft has done a much better job of responding to customers requests than most all Amateur radio

Re: [Elecraft] Tracking Elecraft Feature Requests

Asked Elecraft Support, and Wayne directly, some weeks ago about a company maintained "public" Product Feature Request list - No specific reply so I assume company not interested in making information on suggestions they receive available. Any feedback collected via this forum might be helpful but

Re: [Elecraft] Tracking Elecraft Feature Requests

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

Re: [Elecraft] Tracking Elecraft Feature Requests

The Jira issue tracker supports voting. http://blogs.atlassian.com/2013/09/jira-tip-of-the-month-crowdsourcing-issue-triage/ wunder Walter Underwood wun...@wunderwood.org http://observer.wunderwood.org/ (my

Re: [Elecraft] Tracking Elecraft Feature Requests

FWIW No interest here K0PP __ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please

Re: [Elecraft] Tracking Elecraft Feature Requests

KF5WBO)' <kf5...@wickedbeernut.com>; elecraft@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

Re: [Elecraft] Tracking Elecraft Feature Requests

> 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? 1. I'm trying to reduce spam. 2. I'm looking for an element of

[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