[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: JNOS in Debian



Ian and Debian Group.

I have read through this email with dismay, and ended with anger.

While I agree that you can make decisions as to the direction of Debian, I believe that you're pushing your decisions into the region of fanatical/puritanical  obsession.   That's all well and good as there's always choice in supporting this distribution or not.

BUT in reading your last paragraph where you suggest that because because ax25-node is being dropped by you, Debian, it is now alright for nodejs to hijack/appropiate this name, 'node' is entirely past anything I can tolerate.  It seems to me that you are speaking far to sweepingly for the Linux Community in general and you're actually looking to reintroduce the 'bug' that originally existed.  Debian it's self required, nay forced the name change originally even though node had been used by ax25 far longer than the js folks.

Please do not presume to speak for the entire Linux community; you've already forced one change because of "node", and now you invite yet another that can cause harm to other distributions through churn and who knows what else.

Please remember that you're not the only fish/distribution out there.  You shouldn't be poisoning the environment for others.

Hans Oeste
VE7OES


On Sat, 2015-03-21 at 10:35 +0000, Iain R. Learmonth wrote:
Hi All,

On Mon, Mar 09, 2015 at 02:01:18PM +0000, Iain R. Learmonth wrote:
> I came across JNOS today and it looks like an interesting piece of software
> that it would be nice to include in Debian.

There was a fair bit of discussion around this so this is just an email to
let everyone know what is happening.

While this software falls directly under the scope of the team and it would
be useful to have in Debian, this is non-free software, and so could not be
included in main.

There have been many many many contributors to this codebase, and
relicensing will not be easy, though has not been entirely ruled out.

This software has a lot of history behind it and I think it's awesome that
it's still going and still in active use. I hope that licensing issues are
not the reason this software falls out of use or ceases development when it
does.

The license used was a "semi-permissive" license. The only violation of the
DFSG I could see was that it restricted use by field of endevour. Some
seemed to think this was a good thing, and you're entitled to your opinions,
but I'd just like to quickly outline a couple of examples where restricting
software to "amateur radio use only" actually harms the hobby:

1) In the UK, it is permissible to use AX.25 on one of the CB channels.
There are also provisions for this in Europe. Restricting the use of packet
software to only amateur radio use, users of CB would not fall under this,
as amateur radio is well defined in law. This means that those that may have
found this software as a gateway into the hobby, where they find they are
interested and get themselves licensed so they can experiment more, are left
out.

2) I'm an Internet Engineering researcher at a University. I have recently
been playing with enhancing TCP for use on AX.25 packet links. I'm not able
to use amateur radio if I'm being paid for it so would have to perform these
experiments in a bit of private spectrum. I would not be able to modify and
use software that is restricted to "amateur radio use only" as I'm working
in private spectrum, and again, this doesn't fit the legal definition of
amateur radio. I would have to duplicate the work, then perform the
experiments, and I wouldn't be able to contribute the code back directly. I
would then have to put on my amateur radio hat and write the code again for
it to be useful to the non-free software.

It was mentioned that JNOS is restricted to using IP addresses from the 44/8
network. It's also worth mentioning that in the UK, the TCP/IP packet
networks I've seen on VHF use RFC1918 addresses. To enable quick
experimentation, this is far easier than going through the AMPRnet portal
and waiting for a co-ordinator to allocate you a subnet to use. I would see
this as a bug, not a feature.

So, sadly, for now, JNOS will not be entering Debian. If you are looking for
node software, Dave MM3ZRZ is currently working on packaging UROnode and
this will be available in the repositories after the release of jessie. We
will be looking to remove ax25-node from the repositories after this, which
would free up the "node" name also allowing it to be used by nodejs if they
want it. (They currently rename the interpreter to nodejs from node which
has caused me, and I'm guessing others, some not easy to spot problems with
scripts).

Thanks,
Iain.


Reply to: