On Friday 15 June 2007 03:49, Rob Landley wrote: > (Right now, nobody EXCEPT the FSF has the right to sue somebody to > enforce the license terms on something like gcc. Do you find that a > comforting thought?) Have you ever signed a copyright transfer agreement to the FSF? Obviously not, because then you wouldn't utter such nonsense. The agreement reads that you transfer a non-exclusive right to the FSF to distribute the code under GPL (versions of your choice, they have this right anyway, but making it explicit is always good), and the right to enforce the license. You still have the right to relicense the work as you like. You also have the right to enforce the license yourself, or to transfer that right to somebody else like gpl-violations.org. The FSF even doesn't require to transfer copyright if you make a GNU project, but if you don't, the FSF won't help you (because they can't). They make very obvious promises about what they care ("four freedoms"), and that they will be very consistent in doing so. So far, all track records have proven that they indeed are very consistent in doing so - the main controversy here is not whether the FSF protects the "four freedoms", but whether these four freedoms are the right goal, and if they really should try so hard to protect these four freedoms. This part of the discussion is fully acceptable, what's not acceptable is that the Linus-fancurve claims things the GPL sais which it doesn't (like "tit-for-tat") or doesn't say which it does (like section 6 - direct license from the licensor, and in cases like Linux where no copyright transfer agreements whatsoever exist, these are the individual contributors). Or that Linux 0.something was already under GPLv2 only, when GPLv2 clearly says that there may be updates, and when you as author don't say something, you are allowing users to update if they like. The last point IMHO makes clear that my interpretation of the comment is valid: This is a commend made by Linus Torvalds, as how he understands or misunderstands the license text. It's not even something you can take as legal advice, because Linus is not a lawyer (fortunately - think how the kernel would look like if it was programmed by a lawyer ;-). Sure, if you as outsider strip the kernel of obvious GPLv2-only code to relicense it as a whole under GPLv3, you need a good asbestos suite, a good lawyer, and good arguments. But let's assume Microsoft really succeeds with its patent FUD against Linux, and the only way out is GPLv3, when will opinions here change? -- Bernd Paysan "If you want it done right, you have to do it yourself" http://www.jwdt.com/~paysan/
Attachment:
pgpX3z7IiNwCI.pgp
Description: PGP signature
- Follow-Ups:
- Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3
- From: [email protected] (Lennart Sorensen)
- Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3
- From: Rob Landley <[email protected]>
- Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3
- References:
- Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3
- From: Adrian Bunk <[email protected]>
- Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3
- From: Carlo Wood <[email protected]>
- Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3
- From: Rob Landley <[email protected]>
- Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3
- Prev by Date: Re: [PATCH] Introduce compat_u64 and compat_s64 types
- Next by Date: Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3
- Previous by thread: Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3
- Next by thread: Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3
- Index(es):