Hello Joe,

> I have to say I don't remember your ever having contributed usefully to
> the open-source WSJT project, so I consider your
> complaints-to-contributions ratio to be rather high.  Perhaps I am being
> unfair to your ultimately friendly purposes for the benefit of Amateur
> Radio.
>

I'm not surprised you don't remember. After all, it's just been a minor
patch so far. I don't think that should matter though, I'm not trying to
complain, I'm trying to participate in this debate. I'm trying to back up
my arguments with facts, and I'm expressing my opinions as based on my
understanding of software licensing. I'm not the guy that's intending to
cause trouble here, I'm here to tell you that your current situation is
inviting trouble.

We're working hard to meet deadlines related to the Jarvis expedition's
> schedule.  Please be patient for us to catch up with clear and complete
> licensing statements.
>

I don't share the particular interest in DXpeditioning, and as such I don't
have a great personal interest in the fox/hound or superfox mode in general.


> In the meantime, try saving a few *.wav files when monitoring K8R, or
> ask for some example files recorded by someone else.  Then execute the
> standalone SuperFox decoder sfrx, using something like the following
> simple command at your bash shell prompt, and see the subsequent output.
>
> $ sfrx 240720_132400.wav
> 132400  -7  0.3  750 ~  JH6KOQ K8R RR73
> 132400  -7  0.3  750 ~  N0AN K8R RR73
> 132400  -7  0.3  750 ~  YO3ICT K8R RR73
> 132400  -7  0.3  750 ~  IK0NKA K8R +01
> 132400  -7  0.3  750 ~  DF2RQ K8R +10
> 132400  -7  0.3  750 ~  OH3FVP K8R +04
> 132400  -7  0.3  750 ~  W2ZQ K8R +03
> K8R verified
>
> If need be, I will send you a few files.
>

Thanks, it's nice you're taking the time to show me how it works, but it's
not necessarily what I intended to happen. It's not important for me to
understand how these decoders works, it's important that such information
is made available to the general audience, maybe packaged together with the
binaries. This information may eventually become relevant for my work on
OpenWebRX, but given that I've worked with the other decoders I'm pretty
sure I would have been able to figure this out myself. At this time I'm
trying to make a different point: the lack of such information makes it
very easy to argue that the superfox binaries are not, as claimed,
standalone, thus forcing you to release their code. You may disagree on
that, which is fine for me, but it's also kind of a great risk to take for
some missing documentation.

The same goes for the binary packages. It's quite risky to shove these
binaries out the door just because they're needed for a DXpedition while at
the same time not taking care of the licensing.

73s
Jakob DD5JFK
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Reply via email to