linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexandre Oliva <aoliva@redhat.com>
To: Al Viro <viro@ftp.linux.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: how about mutual compatibility between Linux's GPLv2 and GPLv3?
Date: Thu, 21 Jun 2007 17:15:03 -0300	[thread overview]
Message-ID: <orhcp1jc8o.fsf@oliva.athome.lsd.ic.unicamp.br> (raw)
In-Reply-To: <20070621180029.GR21478@ftp.linux.org.uk> (Al Viro's message of "Thu\, 21 Jun 2007 19\:00\:29 +0100")

On Jun 21, 2007, Al Viro <viro@ftp.linux.org.uk> wrote:

> On Thu, Jun 21, 2007 at 06:39:07AM -0300, Alexandre Oliva wrote:

>> - the kernel Linux could use code from GPLv3 projects

> ... and inherit GPLv3 additional restrictions.  No.

Respecting the wishes of the author of that code.  Are you suggesting
they should not be respected?

Anyone who's not happy about it can still take that portion out,
unless you accept changes that make this nearly impossible, which I
suppose you wouldn't given how strongly you feel about this.

Without this provision, you wouldn't be able to use the code in the
first place, so I don't perceive any loss for anyone.  Do you?

>> - GPLv3 projects could use code from Linux

> Oh, rapture!  How could one object against such a glorious outcome?

Exactly ;-)

Two-way cooperation.  I'm told that's good.  I was told this was even
desirable.

I can see that one-way cooperation could be perceived as unfair, even
if permissions granted by GPLv3 are all granted by GPLv2 as well.

>> - 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?

But see, nobody would be adding restrictions to *your* code.  You'd
only be enabling mutual cooperation with projects whose authors
weren't happy about restrictions some licensees could impose on others
(including the authors themselves).

>> 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!!!

It is either way.  Do you deny that tivoization also benefits one
user/licensee?  And in detriment of others, while at that?

> No.  Permission denied.

Your opinion is duly noted.  Thanks.

> If somebody wants to dual-license *others* code,

This is not about dual licensing at all, and this is not about others
code.  This is a decision you would have to make in order to enable
cooperation between projects.

If you don't want to make this decision, that's fine.  Nobody can be
forced to cooperate.  This works in both directions.

Don't try to frame those who want to respect and defend users'
freedoms as uncooperative.  This is *your* decision, and your decision
alone.

-- 
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}

  reply	other threads:[~2007-06-21 20:15 UTC|newest]

Thread overview: 68+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-21  9:39 how about mutual compatibility between Linux's GPLv2 and GPLv3? 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
2007-06-21 20:15   ` Alexandre Oliva [this message]
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=orhcp1jc8o.fsf@oliva.athome.lsd.ic.unicamp.br \
    --to=aoliva@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@ftp.linux.org.uk \
    /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;
as well as URLs for NNTP newsgroup(s).