[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070615164347.GA4952@alinoe.com>
Date: Fri, 15 Jun 2007 18:43:47 +0200
From: Carlo Wood <carlo@...noe.com>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Daniel Hazelton <dhazelton@...er.net>,
Bernd Paysan <bernd.paysan@....de>,
Theodore Tso <tytso@....edu>,
Alexandre Oliva <aoliva@...hat.com>,
Sean <seanlkml@...patico.ca>, Adrian Bunk <bunk@...sta.de>,
Valdis.Kletnieks@...edu, Alan Cox <alan@...rguk.ukuu.org.uk>,
Greg KH <greg@...ah.com>,
debian developer <debiandev@...il.com>, david@...g.hm,
Tarkan Erimer <tarkan@...one.net.tr>,
linux-kernel@...r.kernel.org,
Andrew Morton <akpm@...ux-foundation.org>, mingo@...e.hu
Subject: Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3
On Fri, Jun 15, 2007 at 08:45:43AM -0700, Linus Torvalds wrote:
> I'm sorry, but I've learnt more about copyright law, and talked to more
> lawyers about licensing that probably most of the rest of the people
> involved in this discussion have *combined*.
Which is why I have taken everything you said so far for granted
as being a fact -- no need to try to convince me of something ;)
In my case it suffices if you say that you are sure (and before
anyone says: you're nuts - what I REALLY mean is 'for the purpose
of this discussion'. For me, it makes no sense to waste more time
on discussing such an issue; I won't bet all my money it, of course).
[..snip..]
> > I always thought that it would be necessary to get signatures of each
> > and every contributor before you can change a license of a file.
>
> You are mostly correct. The "mostly" comes because I would not say "every
> contributor", but would clarify it by saying "every copyright holder". The
> difference? Not all contributions are necessarily copyrightable. If you
> send in trivial one-liners, we will credit you for them, but that does not
> automatically mean that you necessarily own copyright in something.
I knew that.
> But yes, somebody who wrote an original file (that has some artistic
> expression, and isn't just a list of PCI ID's, for example) will be the
> copyright owner in that file. Some *very* few people have actually sent me
> paperwork to transfer the ownership of copyrights, but they seem to have
> done that because they were just used to doing it with the FSF, and I
> actually don't care.
>
> Linus
The point is: can you, or can't you (legally) relicense the whole kernel
tree under the GPLv3 (or GPLv2+GPLv3)?
At first I thought that you cannot, because too many (significant) contributors
have been involved (and you will never get signatures from them all).
Then someone surprised me by claiming that the original author had
copyright for everything - even files added by others. To me, this
seemed to say: even if those contributors don't like it, the original
author can still sell the whole to some company under a proprietary
license (also still having the original under the GPL on the net, of
course), as he could do when he was the sole author.
Then you reply with:
> Carlo> Huh - surely not to files added to the kernel that were written by
> Carlo> others from scratch!
>
Linus> Actually, yes. Even to those - when they are part of "the whole".
But the rest of your reply made it a bit unclear again.
Assume you stopped taking your meds and next week you think that GPLv3
is THE thing for the kernel. Then could you legally, or can't you, go
ahead and change the license of the whole kernel to GPLv3? And if you
can't, then roughly how many files / authors are stopping you from
doing so?
If the answer is: I can't. Then I think you're a lucky bastard, and
have escaped years and years of discussions with people trying to
convince you that the GPLv3 is better ;)
I think that the question: can OTHERS "upgrade" the kernel to GPLv3
has been answered clearly now: No they can't. But if you can, you're
probably not done with dealing with people who want that to happen.
--
Carlo Wood <carlo@...noe.com>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists