4 ms·
The accepted answer is bizarre. It starts out with the correct answer -- Tivoization -- devotes a single word to it, and then goes on a multi-paragraph rant ab
by kelnos 7y ago
The accepted answer is bizarre. It starts out with the correct answer -- Tivoization -- devotes a single word to it, and then goes on a multi-paragraph rant about Google. It has nothing to do with Google; the commenter there has a very exaggerated opinion of the influence Google wields over Linux kernel development.
Might as well go straight to the source, Torvalds himself: https://lkml.org/lkml/2007/6/13/289 https://lkml.org/lkml/2007/6/13/289
Edit: It's also a good point to make (as noted below), that it would be nearly impossible to change Linux's license at this point, since all of the many thousands(?) of contributors would have to be tracked down and agree to the change. Although, since the GPLv2 and GPLv3 are compatible licenses, it's presumably possible to license the kernel as a whole as GPLv3, with new contributions GPLv3-licensed, without touching the licensing of the existing code. That would likely be a nightmare to manage, and it would get really tricky to point to a particular piece of (old but recently changed) code and say "what license is this bit under?"
- kevin_thibedeau 7y agoIt has nothing to do with Tivoization. The kernel is a collective work without copyright assignment to a central authority. It would be too much work to contact everyone with a claim to copyright (including estates of deceased coders) to get their blessing for a relicense. Conversely, everything under the aegis of FSF transitioned to GPL3 because they "own" the code via assignment.
- kadoban 7y agoI think it's two separate but each probably sufficient reasons: 1) Linus doesn't want to (unless his stance has changed, haven't seen it). 2) It would be almost impossible because of contributor copyright/license reasons, as you explained. So I'd really say it's both.
- kelnos 7y agoIt's both. Torvalds initially fixed the licensing information as "GPLv2 only" due to uncertainly; he simply wasn't comfortable agreeing to license his work under some unknown future license. While GPLv3 was being drafted, he publicly came out against the anti-Tivoization provisions. So I guess it's correct to say it's still GPLv2 because it's always been that way, and getting agreement from all contributors to change it (if that was even desirable) would be prohibitively difficult. But it seems like the question was actually trying to get at why Torvalds (et al.) don't like GPLv3.
- jra_samba 7y agoNo, the FSF did not transition everything to GPLv3. glibc, IMHO one of their most important projects remains at LGPLv2+. This is due to Stallmans fear of losing popularity of 'his' code and is the reason I no longer have any respect for the FSF, who unfortunately have been exposed as hypocrites.
- jpalomaki 7y agoOne comment in the SO points to a write-up which seems to make the point that changing the license might not be impossible (check the heading "If the license is attached to your collective-work copyright") [1]. [1] http://www.catb.org/~esr/Licensing-HOWTO.html http://www.catb.org/~esr/Licensing-HOWTO.html
- phoe-krk 7y ago> Although, since the GPLv2 and GPLv3 are compatible licenses No. GPLv2 is not compatible with GPLv3. GPLv2 states that the modified code must not place any new restrictions on the resulting code. GPLv3 places such a restriction via its patent-provisions and anti-tivoization clauses. Therefore, you cannot combine GPLv2 code with GPLv3 code, or release GPLv2 code under any license other than GPLv2. What you likely mean is code licensed under GPLv2+, which means that it can be licensed under GPLv2 or any later GPL version. Linux is not licensed that way - it is strictly GPLv2-only.
- kelnos 7y agoAh, that's a good point. So there's pretty much no way that any kernel code can be GPLv3, short of contacting each and every contributor and getting them to agree to switch.