Advertisement
Embedded Android Training, Hands-On
AOSP, Kernel Androidisms, System Server, Internals / 5-days / O'Reilly Author Instructor
| |||||||||||||
|
| |||||||||||||
RelicensingRelicensingPosted Jul 13, 2006 19:39 UTC (Thu) by ringerc (subscriber, #3071)In reply to: ZFS by paulj Parent article: The 2006 Linux Filesystems Workshop (Part III)
"and persuade Linus to reconsder the GPLv2 only license"
He can't. He could relicense _his_ contributions under GPlv3, but he can't relicense the whole kernel as no one person (him or otherwise) holds the copyright, and the license currently states that it is GPLv2 ONLY. Relicensing the whole kernel would require the consent of every contributor (or their estate) which is awfully unlikely to happen, and insanely impractical. How would you find them all? Heck, how would you find out who they all were?
(Log in to post comments)
Relicensing Posted Sep 25, 2006 9:36 UTC (Mon) by forthy (guest, #1525) [Link] He can. He wrote the GPLv2-only statement as interpretative comment on the lincense himself in the 2.4.0-pre-versions, without asking anyone, so he can remove it as well. It's his right as redistributor of GPL code to choose the license, when it is originally under GPLv2-or-later, and it is his right to change his choice. If anyone wants his code in Linux to be GPLv2-only, he has to mark it himself as such. AFAIK, nobody ever did (while quite a lot clairified that they really meant GPLv2-or-later). Note that Linus does not have the right to change the GPL. All he can is to add comments to it. The GPLv2 is GPLv2 or later by default, unless explicitely stated otherwise, and you get the license from the original author. However, each redistributor can only be forced to do what he's obliged to under the license version he chose.
|
|
||||||||||||