K3: Issues and Enhancements document

[DOUGLAS ZWIEBEL]

RE:  Issues and Enhancements document

I agree that it is time to make this available.

It seems that Elecraft has really ramped up the production (at least
for now) of the K3s.  There are ostensibly over 300 in the hands of
users.  Customer expectations are shifting.

I too would like to see a place on the Elecraft page where we can see
just what's on "the list" in terms of:

1.  Known issues (problem list / bugs) that are either "in the works
and being resolved" or "soon to be addressed."

2.  Requested enhancements ("wish list") with some sort of priority
flag (high, med, low, and "don't hold your breath")

Since "the list" is often cited on the Elecraft Reflector, I would
hope that it would not take a whole of time and effort to post "the
list" somewhere.

Okay....this probably does not meet the email list criteria since it
is a "me too" comment, but I hope I don't get stomped on too badly.
;-)

de Doug KR2Q
K2 5285
1st K3 #295
2nd K3 (on order since Nov 21)

And did I tell you that I really like the K3 and the Elecraft customer service!
_______________________________________________
Elecraft mailing list
Post to: [hidden email]
You must be a subscriber to post to the list.
Subscriber Info (Addr. Change, sub, unsub etc.):
 http://mailman.qth.net/mailman/listinfo/elecraft   

Help: http://mailman.qth.net/subscribers.htm
Elecraft web page: http://www.elecraft.com

[Vic K2VCO]

DOUGLAS ZWIEBEL wrote:
> RE:  Issues and Enhancements document

> 1.  Known issues (problem list / bugs) that are either "in the works
> and being resolved" or "soon to be addressed."
>
> 2.  Requested enhancements ("wish list") with some sort of priority
> flag (high, med, low, and "don't hold your breath")

I too would like this, but as a software developer I know why they don't
do it (at least, I know why *I* don't do it).

1) The amount of time it would take to compile such a list might not be
unreasonable. But then they have to respond to all the questions,
suggestions, and arguments that it will generate. And the 'they' is
basically Wayne, who really has more to do now than one regular human
can do.

2) Once something is listed as a future feature, many will interpret
that as a contract. If it turns out later to have been a bad idea, too
complicated, etc. then the decision to not do it will have to be justified.

Think about this in terms of the *thousands* of people who have an
interest in the K3 and you can see why it would be a heavy load.
--
73,
Vic, K2VCO
Fresno CA
http://www.qsl.net/k2vco
_______________________________________________
Elecraft mailing list
Post to: [hidden email]
You must be a subscriber to post to the list.
Subscriber Info (Addr. Change, sub, unsub etc.):
 http://mailman.qth.net/mailman/listinfo/elecraft   

Help: http://mailman.qth.net/subscribers.htm
Elecraft web page: http://www.elecraft.com

[M0XDF]

It Elecraft send me their bug / issues list, I will treat it confidential
and put together an agreed (with them) page for the Wiki.

Could we not do this on an 'as seen' basis, no questions to Elecraft about
the issues, or at least not that you should expect Wayne/Eric/Lyle/Greg to
answer (sorry if I missed anyone :)



On 6/2/08 18:49, "Vic K2VCO" <[hidden email]> sent:

> DOUGLAS ZWIEBEL wrote:
>> RE:  Issues and Enhancements document
>
>> 1.  Known issues (problem list / bugs) that are either "in the works
>> and being resolved" or "soon to be addressed."
>>
>> 2.  Requested enhancements ("wish list") with some sort of priority
>> flag (high, med, low, and "don't hold your breath")
>
> I too would like this, but as a software developer I know why they don't
> do it (at least, I know why *I* don't do it).
>
> 1) The amount of time it would take to compile such a list might not be
> unreasonable. But then they have to respond to all the questions,
> suggestions, and arguments that it will generate. And the 'they' is
> basically Wayne, who really has more to do now than one regular human
> can do.
>
> 2) Once something is listed as a future feature, many will interpret
> that as a contract. If it turns out later to have been a bad idea, too
> complicated, etc. then the decision to not do it will have to be justified.
>
> Think about this in terms of the *thousands* of people who have an
> interest in the K3 and you can see why it would be a heavy load.

--
When I am working on a problem I never think about beauty.
I only think about how to solve the problem.
But when I have finished, if the solution is not beautiful,
I know it is wrong.
-R. Buckminster Fuller, engineer, designer, and architect (1895-1983)


_______________________________________________
Elecraft mailing list
Post to: [hidden email]
You must be a subscriber to post to the list.
Subscriber Info (Addr. Change, sub, unsub etc.):
 http://mailman.qth.net/mailman/listinfo/elecraft   

Help: http://mailman.qth.net/subscribers.htm
Elecraft web page: http://www.elecraft.com

[Brett Howard]

Would it make you feel better if it was said that getting a list is on the
list?  Cause I'm willing to be that's all you'll get.


_______________________________________________
Elecraft mailing list
Post to: [hidden email]
You must be a subscriber to post to the list.
Subscriber Info (Addr. Change, sub, unsub etc.):
 http://mailman.qth.net/mailman/listinfo/elecraft   

Help: http://mailman.qth.net/subscribers.htm
Elecraft web page: http://www.elecraft.com

[M0XDF]

Not A Lot
:)


On 6/2/08 20:03, "Brett Howard" <[hidden email]> sent:

> Would it make you feel better if it was said that getting a list is on the
> list?  Cause I'm willing to be that's all you'll get.

--
I know that you believe that you understood what you think I said, but I am
not sure you realize that what you heard is not what I meant.
- Robert McCloskey, State Department spokesman (attributed)


_______________________________________________
Elecraft mailing list
Post to: [hidden email]
You must be a subscriber to post to the list.
Subscriber Info (Addr. Change, sub, unsub etc.):
 http://mailman.qth.net/mailman/listinfo/elecraft   

Help: http://mailman.qth.net/subscribers.htm
Elecraft web page: http://www.elecraft.com

[Thom LaCosta]

On Wed, 6 Feb 2008, David Ferrington, M0XDF wrote:

> It Elecraft send me their bug / issues list, I will treat it confidential
> and put together an agreed (with them) page for the Wiki.

If Elecraft really wanted to have such information posted, they could do it
themseleves on their web site, or in the wiki....one one expect that they are
organized enough to already have an internal list.

Discounting the strawman argument of no time, one could take the position that
they simply do no want to release the information....which is their right, since
it's their product.

One of the reasons the K3 wiki and forum was started was to allow K3 owners to
contribute to the overall knowledge base, based on their experience and
technical interests.

So, if the company doesn't release the information and the users don't post it,
the community might be thought of as mushrooms...waiting for the next release of
nutrient.

73 k3hrn
Thom,EIEIO
Email, Internet, Electronic Information Officer

www.baltimorehon.com/                    Home of the Baltimore Lexicon
www.tlchost.net/hosting/                 Web Hosting as low as 3.49/month
_______________________________________________
Elecraft mailing list
Post to: [hidden email]
You must be a subscriber to post to the list.
Subscriber Info (Addr. Change, sub, unsub etc.):
 http://mailman.qth.net/mailman/listinfo/elecraft   

Help: http://mailman.qth.net/subscribers.htm
Elecraft web page: http://www.elecraft.com

[Stewart Baker]

As Wiki is open, I suggest that David you make a start by putting
your data into the appropriate section. I will then put on what I
know (or have surmised). If others contribute, it should grow.

Of course postings should be limited to those who already have a
K3, assembled and used in anger.

This way Elecraft can look, note and comment if desired. All
without tying up their limited resources, making promises or
revealing their hand.

73
Stewart G3RXQ
On Wed, 06 Feb 2008 19:11:51 +0000, David Ferrington, M0XDF wrote:
> It Elecraft send me their bug / issues list, I will treat it
confidential
> and put together an agreed (with them) page for the Wiki.
>
> Could we not do this on an 'as seen' basis, no questions to
Elecraft about
> the issues, or at least not that you should expect
Wayne/Eric/Lyle/Greg to
> answer (sorry if I missed anyone :)
>
>
> On 6/2/08 18:49, "Vic K2VCO" <[hidden email]> sent:
>
>> DOUGLAS ZWIEBEL wrote:
>>> RE:  Issues and Enhancements document
>>>
>>> 1.  Known issues (problem list / bugs) that are either "in the
works
>>> and being resolved" or "soon to be addressed."
>>>
>>> 2.  Requested enhancements ("wish list") with some sort of
priority
>>> flag (high, med, low, and "don't hold your breath")
>>>
>> I too would like this, but as a software developer I know why
they don't
>> do it (at least, I know why *I* don't do it).
>>
>> 1) The amount of time it would take to compile such a list
might not be
>> unreasonable. But then they have to respond to all the
questions,
>> suggestions, and arguments that it will generate. And the
'they' is
>> basically Wayne, who really has more to do now than one regular
human
>> can do.
>>
>> 2) Once something is listed as a future feature, many will
interpret
>> that as a contract. If it turns out later to have been a bad
idea, too
>> complicated, etc. then the decision to not do it will have to
be justified.
>>
>> Think about this in terms of the *thousands* of people who have
an
>> interest in the K3 and you can see why it would be a heavy
load.


_______________________________________________
Elecraft mailing list
Post to: [hidden email]
You must be a subscriber to post to the list.
Subscriber Info (Addr. Change, sub, unsub etc.):
 http://mailman.qth.net/mailman/listinfo/elecraft

Help: http://mailman.qth.net/subscribers.htm
Elecraft web page: http://www.elecraft.com