From: Jerry Van Baren <gerald.vanbaren@ge.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] u-boot-v2 and GPL license version?
Date: Thu, 09 Jul 2009 07:35:28 -0400 [thread overview]
Message-ID: <4A55D600.1090004@ge.com> (raw)
In-Reply-To: <m2r5wqayqb.fsf@ohwell.denx.de>
Detlev Zundel wrote:
> Hi Jerry,
>
>> Kumar Gala wrote:
>>> Sascha,
>>>
>>> You seem to be the person acting as maintainer of u-boot-v2. Do you
>>> have any input if u-boot-v2 would stay with GPLv2 or move to GPLv3?
>>>
>>> - k
>> U-Boot v2 is the usage case I had in mind in my question:
>>> Would U-Boot be willing to have as much GPLv2++ (GPLv3) as possible, and
>>> supporting a run time plug-in system to accommodate GPLv2-only modules?
>> <http://thread.gmane.org/gmane.comp.boot-loaders.u-boot/61801/focus=62886>
>>
>> RMS' opinion was that this approach could be taken WRT GPLv3 of the
>> U-Boot core and allow GPLv2 plug-ins, preferably via an explicit
>> exception. He was also OK with the concept from an ethical point of view.
>> <http://thread.gmane.org/gmane.comp.boot-loaders.u-boot/61801/focus=62920>
>
> Don't forget that RMS also noted that this case also needs the exception
> on the GPLv2 only code to be used in conjunction with GPLv3.
Oops, I /had/ forgotten that. That puts a pretty big pothole in that
road. :-/
Best case, we would still have to contact all the authors of GPLv2
drivers and convince them to change their copyright licensing. Worst
case, some wouldn't agree to the license change and we would have to
rewrite their code, resulting in no net gain.
> Cheers
> Detlev
Thanks,
gvb
next prev parent reply other threads:[~2009-07-09 11:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-08 17:48 [U-Boot] u-boot-v2 and GPL license version? Kumar Gala
2009-07-08 18:13 ` Jerry Van Baren
2009-07-09 11:21 ` Detlev Zundel
2009-07-09 11:35 ` Jerry Van Baren [this message]
2009-07-09 15:29 ` Mike Frysinger
2009-07-08 19:01 ` Mike Frysinger
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=4A55D600.1090004@ge.com \
--to=gerald.vanbaren@ge.com \
--cc=u-boot@lists.denx.de \
/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