lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Thu, 28 Sep 2006 16:19:32 +0200 From: DervishD <lkml@...vishd.net> To: Lennart Sorensen <lsorense@...lub.uwaterloo.ca> Cc: Chase Venters <chase.venters@...entec.com>, Sergey Panov <sipan@...an.org>, Linus Torvalds <torvalds@...l.org>, Patrick McFarland <diablod3@...il.com>, Theodore Tso <tytso@....edu>, Alan Cox <alan@...rguk.ukuu.org.uk>, Jan Engelhardt <jengelh@...ux01.gwdg.de>, James Bottomley <James.Bottomley@...eleye.com>, linux-kernel <linux-kernel@...r.kernel.org> Subject: Re: GPLv3 Position Statement Hi Lennart :) * Lennart Sorensen <lsorense@...lub.uwaterloo.ca> dixit: > I wonder if perhaps the solution should be that the GPLv3 draft > should be renamed to something else to allow RMS to create his new > license that does exactly what he wants it to do, without hijacking > existing GPLv2 code using a license that in many people's opinion > is NOT in the spirit of the GPLv2 (which it could be argued > overrides the "or later" part of the license). That's quite curious, because my wife (who doesn't have a great software background and that knows FOSS and GPL through me) said exactly the same when I told her yesterday the problem that people like me, who has released code under GPLv2, may face if GPLv3 is applied retroactively to every software that says "or any later version". She said that of course anybody has the right of making new licenses, but that, as far as she could tell, the new license shouldn't be named "GPL" because it was very different from what we now call "GPL". Of course her vision may be highly biased by what I told her, but since I still don't have a clear position about all this GPLv2 vs. GPLv3 issue, I don't think that the bias is so high. Probably the renaming is just common sense and will avoid ALL problems. People like me are concerned only because all GPLv2 that doesn't state otherwise will be released automagically under GPLv3 as soon as the latest draft is made the official version. Otherwise, I wouldn't give a hump about any new license until I have the time to read it and see if I like it. Raúl Núñez de Arenas Coronado -- Linux Registered User 88736 | http://www.dervishd.net It's my PC and I'll cry if I want to... RAmen! - 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