From: Alexandre Oliva <aoliva@redhat.com>
To: davids@webmaster.com
Cc: "Linux-Kernel\@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>
Subject: Re: how about mutual compatibility between Linux's GPLv2 and GPLv3?
Date: Thu, 21 Jun 2007 20:37:46 -0300 [thread overview]
Message-ID: <orr6o4j2ut.fsf@oliva.athome.lsd.ic.unicamp.br> (raw)
In-Reply-To: <MDEHLPKNGKAHNMBLJOLKOEJBEMAC.davids@webmaster.com> (David Schwartz's message of "Thu\, 21 Jun 2007 14\:13\:36 -0700")
On Jun 21, 2007, "David Schwartz" <davids@webmaster.com> wrote:
> Are you seriously suggesting that the Linux kernel source contain code with
> various different licenses
It already does. All the way from permissive Free Software licenses
to GPLv2-incompatible non-Free Software licenses.
> Over time, the code will get so combined and interwoven that the
> intersection of all permitted licenses would soon apply to
> effectively the entire kernel.
If you don't keep things clearly separate, yes.
I was honestly thinking more along the lines of ZFS as a separate
driver than about your bringing GPLv3 code into the core of the
kernel.
But then, it would be your call either way.
This option of mutual cooperation wouldn't work for either party if
you're not willing to cooperate, and that's what I believe makes it
fair.
Now, if you guys can't recognize a goodwill gesture when you see one,
and prefer to live in the paranoid beliefs that "those evil FSFers are
trying to force me into a situation in which they'll then be able to
steal my code", that's really up to you. Don't try to shift the blame
of your decisions onto the FSF.
One thing is missing the spirit of the GPL and using it to serve a
different purpose, without realizing it doesn't provide you with
exactly what you want (tivoization, for example); another completely
different is to try to put it as FSF's fault that clarifications and
amendments are desirable to ensure the ability for authors to enforce
the intent of the GPL.
> Unless, that is, GPLv3 makes itself compatible with GPlv2.
Hey, but that was precisely what I was suggesting! Except that it
wasn't with GPLv2 alone, because this doesn't work. Each copyleft
license insists that it be *the* license. So, in order to be able to
combine two copyleft licenses, you need mutual compatibility
provisions in both. Which is what I was proposing.
--
Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/
FSF Latin America Board Member http://www.fsfla.org/
Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org}
next prev parent reply other threads:[~2007-06-21 23:38 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-21 9:39 Alexandre Oliva
2007-06-21 11:35 ` jimmy bahuleyan
2007-06-21 17:53 ` Alexandre Oliva
2007-06-21 18:00 ` david
2007-06-21 20:02 ` Alexandre Oliva
2007-06-21 21:13 ` David Schwartz
2007-06-21 23:37 ` Alexandre Oliva [this message]
2007-06-22 0:31 ` David Schwartz
2007-06-22 1:00 ` Alexandre Oliva
2007-06-22 1:34 ` Al Viro
2007-06-22 4:19 ` Theodore Tso
2007-06-22 6:00 ` Alexandre Oliva
2007-06-22 14:43 ` Theodore Tso
2007-06-25 13:28 ` Lennart Sorensen
2007-06-25 19:54 ` Alexandre Oliva
2007-06-26 4:10 ` Jan Harkes
2007-06-26 6:33 ` Alexandre Oliva
2007-06-26 7:47 ` Alexandre Oliva
2007-06-26 16:25 ` Jan Harkes
2007-06-27 23:08 ` Alexandre Oliva
2007-06-27 23:53 ` David Schwartz
2007-06-28 0:56 ` Alexandre Oliva
2007-06-28 1:37 ` David Schwartz
2007-06-28 2:37 ` Alexandre Oliva
2007-06-28 2:51 ` Daniel Hazelton
2007-06-28 4:45 ` Alexandre Oliva
2007-06-28 4:52 ` Daniel Hazelton
2007-06-28 6:15 ` David Schwartz
2007-06-28 17:40 ` Alexandre Oliva
2007-06-28 19:13 ` David Schwartz
2007-06-30 2:53 ` Alexandre Oliva
2007-06-30 4:04 ` David Schwartz
2007-06-30 6:16 ` Alexandre Oliva
2007-06-28 3:44 ` David Schwartz
2007-06-28 4:57 ` Alexandre Oliva
2007-06-28 5:08 ` Jan Harkes
2007-06-28 6:58 ` Alexandre Oliva
2007-06-28 17:52 ` Alexandre Oliva
2007-07-01 8:48 ` Alexandre Oliva
2007-06-22 9:14 ` Alan Cox
2007-06-22 14:47 ` Theodore Tso
2007-06-22 19:14 ` Alexandre Oliva
2007-06-22 4:26 ` Alexandre Oliva
2007-06-22 5:23 ` Al Viro
2007-06-22 6:15 ` Alexandre Oliva
2007-06-22 9:05 ` Alan Cox
2007-06-22 21:28 ` David Schwartz
2007-06-21 20:44 ` Jesper Juhl
2007-06-21 23:08 ` Alexandre Oliva
2007-06-21 23:20 ` Jesper Juhl
2007-06-22 0:13 ` Alexandre Oliva
2007-06-21 18:00 ` Al Viro
2007-06-21 20:15 ` Alexandre Oliva
2007-06-21 23:04 ` Al Viro
2007-06-22 0:47 ` Alexandre Oliva
2007-06-21 18:29 ` David Schwartz
2007-06-21 19:56 ` Alexandre Oliva
2007-06-21 20:48 ` David Schwartz
2007-06-21 23:23 ` Alexandre Oliva
2007-06-22 0:58 ` Jan Harkes
2007-06-22 4:14 ` Alexandre Oliva
2007-06-22 4:59 ` Jan Harkes
2007-06-22 1:33 ` Bron Gondwana
2007-06-22 4:40 ` Alexandre Oliva
2007-06-22 1:18 ` Bron Gondwana
2007-06-22 4:34 ` Alexandre Oliva
2007-06-22 5:25 ` Al Viro
2007-06-22 5:31 ` Randy Dunlap
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=orr6o4j2ut.fsf@oliva.athome.lsd.ic.unicamp.br \
--to=aoliva@redhat.com \
--cc=davids@webmaster.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®