linux-kernel - Re: GPLv3 Position Statement

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20060928135510.GR13641@csclub.uwaterloo.ca>
Date:	Thu, 28 Sep 2006 09:55:10 -0400
From:	Lennart Sorensen <lsorense@...lub.uwaterloo.ca>
To:	Chase Venters <chase.venters@...entec.com>
Cc:	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

On Wed, Sep 27, 2006 at 11:39:04PM -0500, Chase Venters wrote:
> This is really why I got upset when I saw all the crap in the press over the 
> last few days. I think both sides have pissed the other off to the point that 
> some of us are actively forgetting that we're just, as Eben once 
> said, "singing slightly different lyrics to slightly different music, and 
> it's dissonant, and it jars us..."
> 
> Some amount of contention is naturally good, so long as it does not undermine 
> the great ends both movements are achieving. When our flamewars spill out 
> into the industry press, it's just likely to make both sides look crazy. I 
> wish that most people who choose to take sides could see (and acknowledge!) 
> the real value the other side has, even if they don't agree with the approach 
> or phraseology. And I wish that more of us wouldn't pick sides; that we'd be 
> those "Passionate Moderates" Linus just invented. But we do need loud voices!

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).  The current GPLv3 draft may be in the spirit of what RMS
intended the GPLv2 to be, but it isn't in the spirit of what the GPLv2
says and does.

No one has a problem with people making new licenses.  People have a
problem with people making new licenses and wanting to retroactively
replace existing licenses with a new and very different license.

Now what would be a good name for the GPLv3?  GRLv1 (GNU Restricted
License v1) perhaps. :)  That is essentially what it is doing.
Restricting what you can do with the code.

--
Len Sorensen
-
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/