From: Chris Snook <csnook@redhat.com>
To: Joshua David Williams <yurimxpxman.lkml@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: GPLv3 dispute solution - new open source license?
Date: Tue, 19 Jun 2007 17:37:45 -0400 [thread overview]
Message-ID: <46784CA9.4060609@redhat.com> (raw)
In-Reply-To: <200706181725.01584.yurimxpxman@gmail.com>
Joshua David Williams wrote:
> I've been keeping tabs on the GPLv3 dispute for quite some time. It seems to
> me that the best solution would be for us to write our own open source
> license - one that would be written specifically to uphold the ten rights in
> the open source definition.
Your solution for license fragmentation is more license fragmentation? GPLv2 is
a damn good license. If we're going to undertake the arduous task of
relicensing the kernel, it had better be worth the payoff. GPLv3 is being
considered because:
1) A lot of the GPLv2 code in the kernel was explicitly authorized by the
contributor to be distributed under future versions of the GPL published by the
FSF. This means we only have to go through the headache of getting
authorization to relicense for a much smaller code base than the whole kernel.
2) The influence of the FSF and ubiquity of GNU tools means that a large chunk
of code is going to be released under GPLv3. This cannot be said for your license.
> I'm not a lawyer
GPLv3 was written by a whole bunch of lawyers, all of them trained and
experienced to consider the extended ramifications of the precise wording of the
license in numerous jurisdictions worldwide. The current draft is already a
compromise between GPLv2 and earlier GPLv3 drafts. It's quite possible that the
kernel will never relicense, and that's okay, because we already have a good
license, the GPLv2, which was also written by a lawyer.
-- Chris
next prev parent reply other threads:[~2007-06-19 21:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-18 21:25 GPLv3 dispute solution - new open source license? Joshua David Williams
2007-06-18 21:38 ` H. Peter Anvin
2007-06-19 21:37 ` Chris Snook [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-06-18 21:47 Joshua David Williams
2007-06-18 22:01 ` Carlo Wood
2007-06-18 23:24 ` Alan Cox
2007-06-18 23:22 ` alan
2007-06-18 22:07 Joshua David Williams
2007-06-18 22:43 ` david
2007-06-19 2:39 ` Alexandre Oliva
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=46784CA9.4060609@redhat.com \
--to=csnook@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=yurimxpxman.lkml@gmail.com \
/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