public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-amd64@lists.gentoo.org
Subject: [gentoo-amd64]  Re: Sun and GPL
Date: Mon, 28 May 2007 11:52:09 +0000 (UTC)	[thread overview]
Message-ID: <pan.2007.05.28.11.52.09@cox.net> (raw)
In-Reply-To: 200705280542.32246.bss03@volumehost.net

"Boyd Stephen Smith Jr." <bss03@volumehost.net> posted
200705280542.32246.bss03@volumehost.net, excerpted below, on  Mon, 28 May
2007 05:42:32 -0500:

>> So, Duncan's idea of dual-licensing the kernel under GPL v2/v3 until
>> all bits of kernel code written by non-agreeing parties are removed
>> would not work.
> 
> Right, but Linus could take the stance that all new submission have to
> be licenced (to him) under GPLv2/GPLv3 and then one there's no
> GPLv2-only code left, release a kernel under GPLv3.  Until the point
> where there's no GPLv2 only code, Linus could only release the whole
> work under GPLv2, but everyone would know the transition was in the
> works.

That's basically what I had in mind, yes.  Only I (inadvertently) took a 
logical shortcut while explaining it, and Richard obviously didn't follow 
me when I veered off.  =8^\  That's the whole reason it couldn't simply 
be made GPLv3 in an instant, however.  New code (and presumably the old 
code from all currently active contributors who agreed and continued to 
contribute) would instantly be dual-licensed, so it could use the old 
GPLv2 only code with the GPLv2 license, while the GPLv3 license remained 
in place but basically unused until all the GPLv2 only code was removed, 
at which point the GPLv2 dual license could be dropped off the new code 
as well (tho anyone wanting it could get it under GPLv2 could get it 
under that last dual licensed snapshot, until further new GPLv3 only code 
was added, anyway).  Finally, the kernel was GPLv2 and later for quite 
some time, the GPLv2 only being a relatively new development as well.  
Thus, anything in the last GPL2 or later snapshot could immediately be 
upgraded to GPLv2/v3 as well.  All told, within a few months, the large 
majority could be dual-licensed.  It's just that last 20, 10, 5, 2, 1%, 
as an increasing focus is placed on the issue, that's the sticking point, 
and that could ultimately cause the switchover to take five years or so.

Still, it's doable, just over some significant time and with some 
substantial effort required.

Thanks for pointing that out, Richard, and Boyd for clarifying what I 
meant.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

-- 
gentoo-amd64@gentoo.org mailing list



  parent reply	other threads:[~2007-05-28 11:55 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-26 19:07 [gentoo-amd64] Can I run a complete desktop remotely? Mark Knecht
2007-05-26 19:37 ` Olivier Crête
2007-05-27 15:40   ` Mark Knecht
2007-05-27 15:56     ` Peter Davoust
2007-05-27 16:04     ` Richard Freeman
2007-05-27 16:56     ` YoYo Siska
2007-05-26 19:49 ` Aleksey Kunitskiy
2007-05-26 19:53 ` Conway S. Smith
2007-05-26 20:29   ` Simon Cooper
2007-05-26 22:24     ` Conway S. Smith
2007-05-26 21:47   ` Nuitari
2007-05-26 22:20     ` [gentoo-amd64] " Duncan
2007-05-27  0:00       ` Duncan
2007-05-26 22:51     ` [gentoo-amd64] " Conway S. Smith
2007-05-27  6:48       ` Joerg Gollnick
2007-05-27 10:57         ` Richard Freeman
2007-05-27 11:11         ` [gentoo-amd64] Sun and GPL Isidore Ducasse
2007-05-27 23:32           ` [gentoo-amd64] " Duncan
2007-05-28  0:41             ` Isidore Ducasse
2007-05-28  3:42               ` Wil Reichert
2007-05-28  6:12                 ` Naga
2007-05-28  3:56               ` Boyd Stephen Smith Jr.
2007-05-28  9:25                 ` Richard Freeman
2007-05-28 10:42                   ` Boyd Stephen Smith Jr.
2007-05-28 10:56                     ` robert burrell donkin
2007-05-28 11:52                     ` Duncan [this message]
2007-05-28 16:23                     ` Hemmann, Volker Armin
2007-05-28 17:28                       ` Nuitari
2007-05-28 11:14               ` Duncan
2007-05-28 13:14                 ` Conway S. Smith
2007-05-28 17:46                   ` Duncan
2007-05-28 18:38                     ` [gentoo-amd64] Baselayout 2 (Was: Sun and GPL) Sebastian Redl
2007-05-28 22:56                       ` [gentoo-amd64] " Duncan
2007-05-29  0:50                         ` Wil Reichert
2007-05-30  0:33                           ` Florian D.
2007-05-30  4:09                             ` Joshua Hoblitt
2007-05-30  4:38                               ` Wil Reichert
2007-05-30  7:39                                 ` Duncan
2007-05-30  7:43                                 ` Isidore Ducasse
2007-05-30 22:57                                 ` Joshua Hoblitt
2007-05-30  9:12                               ` Florian D.

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=pan.2007.05.28.11.52.09@cox.net \
    --to=1i5t5.duncan@cox.net \
    --cc=gentoo-amd64@lists.gentoo.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