I think SourceForge would be a little over the top, not to mention that the
K3 code is not in the public domain.
I agree a single place to see what requests have been made and what the
status is. There is a page at
http://www.zerobeat.net/mediawiki/index.php/Firmware_Enhancements_on_Elecra
At 1/20/2008 05:27 AM, David Ferrington, M0XDF wrote:
I think SourceForge would be a little over the top, not to mention that the
K3 code is not in the public domain.
I agree a single place to see what requests have been made and what the
status is. There is a page at
Brett Howard wrote:
What is really needed is a Sourceforge page. Where users can search for
Sourceforge isn't a possibility, as they only accept open source
software. However, Elecraft could run their own Bugzilla server.
is from the consensus in here things would be posted TONS of
On Sun, 20 Jan 2008, David Ferrington, M0XDF wrote:
I think SourceForge would be a little over the top, not to mention that the
K3 code is not in the public domain.
I agree a single place to see what requests have been made and what the
status is. There is a page at
Like W4ZV, I was a beta tester for that other SDR. Bear in mind my post of a
few weeks ago in which I cautioned about avoiding groupie-ism and holding
manufacturers to high standards. Here's my 2-cents on the subject:
1. I agree with W4TV that Elecraft should update the approximate delivery
I don't want to add to all the noise about deliveries and delays, but
I do want to make a suggestion. First, as some of you know, I was
lucky to receive my K3 early on. While I was able to enjoy it sooner
than most, my K3 had more problems and features to deal with than
the K3s that are
K1EP:
The point of all this is, I would like to see a list.
I know of no development group that doesn't already
maintain a list of bugs and ongoing projects.
Elecraft does maintain a list of issues that
the Field Test team has access to. Although I can
see arguments both pro and con
What is really needed is a Sourceforge page. Where users can search for
bugs and submit bugs and the developers can assign resources to them and
put notes on them and put schedules on them but the main thing is that
everything is held in one easy to manage place. The real issue though
is from
8 matches
Mail list logo