From: Frederik Van Slycken <frederik.van.slycken@gmail.com>
To: antonynpavlov <antonynpavlov@gmail.com>
Cc: barebox <barebox@lists.infradead.org>
Subject: picoTCP, barebox, and licenses
Date: Thu, 5 Jun 2014 21:24:51 +0200 [thread overview]
Message-ID: <CAGF38F=VxqD8L3EqZUneAvXHTtORDPXcOEynfbjaK_Zu2Zuh6w@mail.gmail.com> (raw)
Dear Antony,
I applaud that you're working on incorporating picoTCP into barebox -
I work for the company that developed picoTCP, and so I am naturally
enthusiastic about this. However, one small thing that should be taken
into account, concerning licensing.
According to the wiki, barebox is licensed under "gplv2 or later",
while picoTCP is licensed only under gplv2. I Am Not A Lawyer, but I
think this means that, if your work would at some point make it into
the master branch of barebox, the licensing notes may need to be
changed to something like "either version 2 of the License, or (at
your option) any later version (except for the picoTCP part, which is
version 2 only)."
Another option would be for barebox to drop the "or later"-part...
although some people here may feel strongly about keeping it in.
(Let's just hope I didn't ignite a gplv2/v3 flame war by suggesting
this!)
Maybe there are other options - what are your thoughts on this issue?
Keep up the good work!
Best Regards,
Frederik Van Slycken
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2014-06-05 19:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-05 19:24 Frederik Van Slycken [this message]
2014-06-05 19:30 ` Robert Schwebel
2014-06-05 19:36 ` Frederik Van Slycken
2014-06-05 19:48 ` Frederik Van Slycken
2014-06-06 7:37 ` Antony Pavlov
2014-06-09 20:33 ` Jean-Christophe PLAGNIOL-VILLARD
2014-06-07 3:18 ` Antony Pavlov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAGF38F=VxqD8L3EqZUneAvXHTtORDPXcOEynfbjaK_Zu2Zuh6w@mail.gmail.com' \
--to=frederik.van.slycken@gmail.com \
--cc=antonynpavlov@gmail.com \
--cc=barebox@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox