Tracking Elecraft Feature Requests
Locked
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 |
|
|
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:[hidden email]] On Behalf Of Joe Stone (KF5WBO) Sent: 14 February 2017 15:14 To: [hidden email] 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:[hidden email] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to [hidden email] ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[hidden email] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to [hidden email] |
Re: 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 traceability / accountability. We want to discourage users from expressing interest in a proposed feature on another user's (or users') behalf. > Where are you planning to post these? Who's going to host whatever website > it is? We'll need to work out the technical details. At this point, I'm simply trying to gauge interest in the concept. Joe KF5WBO |
Re: Tracking Elecraft Feature Requests
|
|
In reply to this post by John-6
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 <[hidden email]> To: 'Joe Stone (KF5WBO)' <[hidden email]>; [hidden email] 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:[hidden email]] On Behalf Of Joe Stone (KF5WBO) Sent: 14 February 2017 15:14 To: [hidden email] 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:[hidden email] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to [hidden email] ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[hidden email] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to [hidden email] ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[hidden email] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to [hidden email] |
Re: 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:[hidden email] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to [hidden email] |
Re: Tracking Elecraft Feature Requests
|
|
In reply to this post by Elecraft mailing list
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 |
Re: 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 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 <[hidden email]> 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 > [hidden email] > http://observer.wunderwood.org/ (my blog) > > >> On Feb 14, 2017, at 8:56 AM, Joe Stone (KF5WBO) <[hidden email]> 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:[hidden email] >> >> This list hosted by: http://www.qsl.net >> Please help support this email list: http://www.qsl.net/donate.html >> Message delivered to [hidden email] > > ______________________________________________________________ > Elecraft mailing list > Home: http://mailman.qth.net/mailman/listinfo/elecraft > Help: http://mailman.qth.net/mmfaq.htm > Post: mailto:[hidden email] > > This list hosted by: http://www.qsl.net > Please help support this email list: http://www.qsl.net/donate.html > Message delivered to [hidden email] ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[hidden email] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to [hidden email] |
|
|
In reply to this post by Joe Stone (KF5WBO)
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 a Customer/Company reconciled and consolidated list would most likely be best.
Also mentioned that a similar database for known firmware defects would be useful. I reported at least 3 possible issues related to the KX2 and know from professional experience that to accurately document and report suspected issues can take significant time - An ongoing, up-to-date list of Elecraft acknowledged problems would help Users avoid wasting time investigating perceived problems. And make Customers more prone to report potential issues - Everybody wins. And BTW, this includes documentation. Additionally, a firmware upgrade/fix release schedule for known defects might also prove useful. Bob |
|
|
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 suppliers.
|
|
|
In reply to this post by Joe Stone (KF5WBO)
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 been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[hidden email] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to [hidden email] |
Fwd: Re: Tracking Elecraft Feature Requests
|
|
Yes Joe, why should you be privvy to proprietary Elecraft information?
K0PP _________________________________ 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 ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[hidden email] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to [hidden email] |
Re: Tracking Elecraft Feature Requests
|
|
In reply to this post by kstover
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 "upgrade" you would have to buy the new radio. With Elecraft, you get those "upgrades" at no cost, just download the firmware. You knew (or should have known) the capabilities of the radio when you bought it - you did review the specializations and features before you purchased it, did you not? I don't think we need to have visibility into the Elecraft engineering resources, and prioritization of requests for added functions. Those at Elecraft *do* listen and often respond to such customer requests, but the prioritization of those requests must be on Elecraft's terms for reasons of availability of engineering resources and the sales benefit of those changes. Bug reports will get a different response than those requests for changed operation. If bug reports are proven valid and repeatable, they will be attended to promptly. 73, Don W3FPR On 2/16/2017 7:54 PM, Kevin wrote: > 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. >> ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[hidden email] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to [hidden email] |
Re: Fwd: Re: Tracking Elecraft Feature Requests
|
|
In reply to this post by Ken G Kopp
> 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. |
Re: Fwd: Re: Tracking Elecraft Feature Requests
|
|
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:[hidden email] > > This list hosted by: http://www.qsl.net > Please help support this email list: http://www.qsl.net/donate.html > Message delivered to [hidden email] ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[hidden email] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to [hidden email] |
Tracking Elecraft Feature Requests
|
|
In reply to this post by Joe Stone (KF5WBO)
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 had, and I have had no hesitation to mention them on this reflector. Perhaps uniquely among producers of the type, as I understand it Elecraft monitors these posts. If an idea has merit, acquires some me-toos, and would work within the financial and technical framework of the company and its processes, I have confidence it will be considered. But I do not believe the company owes me even so much as an acknowledgment. No more than I owe them an explanation about why I haven’t yet bought a KX2. Elecraft is a very good amateur radio equipment maker. I am a happy repeat customer. So long as I like their gear and their service, I’ll keep buying it. If it were a publicly listed company I might very well buy stock in it. But it isn’t, and I haven’t. Ted, KN1CBR ------------------------------ Message: 8 Date: Thu, 16 Feb 2017 20:14:44 -0500 From: Don Wilhelm <[hidden email]> To: [hidden email] Subject: Re: [Elecraft] Tracking Elecraft Feature Requests Message-ID: <[hidden email]> 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. 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 "upgrade" you would have to buy the new radio. With Elecraft, you get those "upgrades" at no cost, just download the firmware. You knew (or should have known) the capabilities of the radio when you bought it - you did review the specializations and features before you purchased it, did you not? I don't think we need to have visibility into the Elecraft engineering resources, and prioritization of requests for added functions. Those at Elecraft *do* listen and often respond to such customer requests, but the prioritization of those requests must be on Elecraft's terms for reasons of availability of engineering resources and the sales benefit of those changes. Bug reports will get a different response than those requests for changed operation. If bug reports are proven valid and repeatable, they will be attended to promptly. 73, Don W3FPR On 2/16/2017 7:54 PM, Kevin wrote: > 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. >> ------------------------------ ------------------------------ Message: 21 Date: Thu, 16 Feb 2017 23:37:35 -0700 From: David Gilbert <[hidden email]> To: [hidden email] Subject: Re: [Elecraft] Fwd: Re: Tracking Elecraft Feature Requests Message-ID: <[hidden email]> Content-Type: text/plain; charset=utf-8; format=flowed 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 ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[hidden email] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to [hidden email] |
Re: Tracking Elecraft Feature Requests
|
|
Dear Ted and Co,
Years ago I requested a pod to control memory and VFO. It did not happen and I requested again but then assumed it a lost cause and looked at the fine K3 in front of me and the service given and decided well maybe there is a reason and that is that. Other solutions came out but it was still not really what I hoped for. Then out of the blue Elecraft brings in the K-Pod which is far better than anything ever expected. In time some of the many other requested features may be introduced but it is an Elecraft decision whether either practical or worth while. If you have a better radio available purchase it. Meanwhile I am perhaps a bit cranky but if as a company I openly solicit suggestions the idea that they would be recorded by a third party who would dictate to my enterprise well maybe I would be thick and stop bothering with a reflector. For me the fact that Elecraft has done so much development on an existing product and kept older versions of the product up to date is just wonderful. Then quietly Elecraft goes off and develops the KX2 post KX3 - oh I will never need one of those. Then I saw the KX2 at Friedrichshafen and fell in love all over again. Let us not be too critical and let us appreciate the ability to talk to the design engineers who own and manage Elecraft. 73 Doug EI2CN -----Original Message----- From: Elecraft [mailto:[hidden email]] On Behalf Of Dauer, Edward Sent: 17 February 2017 14:11 To: [hidden email] 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 had, and I have had no hesitation to mention them on this reflector. Perhaps uniquely among producers of the type, as I understand it Elecraft monitors these posts. If an idea has merit, acquires some me-toos, and would work within the financial and technical framework of the company and its processes, I have confidence it will be considered. But I do not believe the company owes me even so much as an acknowledgment. No more than I owe them an explanation about why I haven't yet bought a KX2. Elecraft is a very good amateur radio equipment maker. I am a happy repeat customer. So long as I like their gear and their service, I'll keep buying it. If it were a publicly listed company I might very well buy stock in it. But it isn't, and I haven't. Ted, KN1CBR ------------------------------ Message: 8 Date: Thu, 16 Feb 2017 20:14:44 -0500 From: Don Wilhelm <[hidden email]> To: [hidden email] Subject: Re: [Elecraft] Tracking Elecraft Feature Requests Message-ID: <[hidden email]> 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. 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 "upgrade" you would have to buy the new radio. With Elecraft, you get those "upgrades" at no cost, just download the firmware. You knew (or should have known) the capabilities of the radio when you bought it - you did review the specializations and features before you purchased it, did you not? I don't think we need to have visibility into the Elecraft engineering resources, and prioritization of requests for added functions. Those at Elecraft *do* listen and often respond to such customer requests, but the prioritization of those requests must be on Elecraft's terms for reasons of availability of engineering resources and the sales benefit of those changes. Bug reports will get a different response than those requests for changed operation. If bug reports are proven valid and repeatable, they will be attended to promptly. 73, Don W3FPR On 2/16/2017 7:54 PM, Kevin wrote: > 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. >> ------------------------------ ------------------------------ Message: 21 Date: Thu, 16 Feb 2017 23:37:35 -0700 From: David Gilbert <[hidden email]> To: [hidden email] Subject: Re: [Elecraft] Fwd: Re: Tracking Elecraft Feature Requests Message-ID: <[hidden email]> Content-Type: text/plain; charset=utf-8; format=flowed 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 ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[hidden email] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to [hidden email] ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[hidden email] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to [hidden email] |
«
Return to Elecraft
|
1 view|%1 views
| Free forum by Nabble | Edit this page |