From: Al Viro <viro@ftp.linux.org.uk>
To: Alexandre Oliva <aoliva@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: how about mutual compatibility between Linux's GPLv2 and GPLv3?
Date: Thu, 21 Jun 2007 19:00:29 +0100 [thread overview]
Message-ID: <20070621180029.GR21478@ftp.linux.org.uk> (raw)
In-Reply-To: <orlkedpryc.fsf@oliva.athome.lsd.ic.unicamp.br>
On Thu, Jun 21, 2007 at 06:39:07AM -0300, Alexandre Oliva wrote:
> Here's an idea that just occurred to me, after all the discussions
> about motivations, tit-for-tat, authors' wishes and all.
>
> If GPLv3 were to have a clause that permitted combination/linking with
> code under GPLv2, this wouldn't be enough for GPLv3 projects to use
> Linux code, and it wouldn't be enough for Linux code to use GPLv3
> projects. That's because GPLv2 would still demand all code to be
> licensed under GPLv2, and GPLv3 wouldn't permit this.
>
> However, if GPLv3 had a permission to combine/link with code under
> GPLv2, *and* Linux (and any other projects interested in mutual
> compatibility) introduced an additional permission to combine/link
> with code under GPLv3 (or even GPLv3+, constrained by some condition
> if you will), then:
>
> - the kernel Linux could use code from GPLv3 projects
... and inherit GPLv3 additional restrictions. No.
> - GPLv3 projects could use code from Linux
Oh, rapture! How could one object against such a glorious outcome?
> - each copyright holder would still get to enforce the terms s/he
> chose for his/her own code
... except for that pesky "no added restrictions" part, but hey, who
cares?
> If you were to permit compatibility with GPLv3+ (rather than GPLv3),
> would you constrain it? Would something like:
>
> as long as the later version grants each licensee the same
> permissions as GPLv2, except for constraining permissions that would
> enable one licensee to deny other licensees the exercise of the
> permissions granted by both licenses
... because it's For The Benefit Of User Freedoms!!!
No. Permission denied. And I don't know of any suckers who would buy that
and hadn't been already hooked by FSF peddlers already.
If somebody wants to dual-license their code, they can do it just fine.
If somebody wants to dual-license *others* code, they can go and play
with themselves until they reach RMS-level clarity of vision.
next prev parent reply other threads:[~2007-06-21 18:01 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
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 [this message]
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=20070621180029.GR21478@ftp.linux.org.uk \
--to=viro@ftp.linux.org.uk \
--cc=aoliva@redhat.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
Powered by JetHome