linux-kernel - Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3

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: <20070614210537.GB14076@elte.hu>
Date:	Thu, 14 Jun 2007 23:05:37 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Al Viro <viro@....linux.org.uk>
Cc:	Alexandre Oliva <aoliva@...hat.com>,
	Alan Cox <alan@...rguk.ukuu.org.uk>,
	Daniel Hazelton <dhazelton@...er.net>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Greg KH <greg@...ah.com>,
	debian developer <debiandev@...il.com>, david@...g.hm,
	Tarkan Erimer <tarkan@...one.net.tr>,
	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3

* Al Viro <viro@....linux.org.uk> wrote:

> On Thu, Jun 14, 2007 at 09:55:17PM +0200, Ingo Molnar wrote:
> > This "right to modify" and "have the same rights as the hardware maker" 
> > arguments are _totally_ bogus, they were made up after the fact, just 
> > because quite apparently RMS had a fit over Tivo and started this verbal 
> > (and legal) vendetta. The FSF is now attempting to rewrite history and 
> > pretends that this "always was in the GPLv2" and applies this newly 
> > thought up concept to the GPLv3 in a way that substantially departs from 
> > the spirit of the GPLv2. Which spirit the GPLv2 explicitly promised to 
> > uphold in Section 9. Which could make any contrary section of the GPLv3 
> > unenforceable, when applied to "GPLv2 or later" licensed software.
> 
> That, BTW, is perhaps the worst problem with v2 (inherited by v3). WTF 
> _is_ "the spirit of the license" and who gets to decide if two 
> licenses are in the same spirit? [...]

yeah. I see this as: "RMS does not want to let go of the community". 
This clause amounts to "power to relicense" _vast_ amounts of free 
software and this is by far the worst problem with the "GPLv3 process".

The GPLv3 process was pretended to be "open", but regardless of what the 
"GPL comittees" said, in the end it was one person: the president of the 
FSF (Richard Stallman) who singlehandedly decided what went into the 
GPLv3 draft and what not. For example he singlehandedly has ignored all 
the criticism that the the "Tivo" section has received.

And note how hypocritic RMS's position is here. Where is that freedom 
when it comes to the licensing process? Why does RMS have more rights 
over modifications to the license than all the other free software 
developers have? Should not he give that freedom to others too? Shouldnt 
there be a fair and just election, a vote? You know, that democracy 
thing.

And with his current attitude he affects somewhere around of 1 billion 
lines of free software. Via a license that is just a few hunded lines 
long.

I believe RMS should accept the fact that most of that code was written 
without people having bought into his ideology, and he should accept 
_responsibility_ for the power he has acquired by genius or by accident 
(your choice) and he should try to _understand_ how those people tick - 
instead of trying to further his own personal agenda.

He shouldnt say what amounts to "oh, my original intent was this and 
that, if you didnt understand it and still wrote code and used the 
default 'or later' license, it's your damn fault".

He should accept that what happened happened, after he wrote 100,000 
lines of original GNU code another ten thousand people wrote about a 
_ten thousand times more_ code. He should also accept that the "open 
source" community is about many other things, and it is alot more varied 
than his thinking is. He does not have to _like_ Tivo, but he should try 
to _understand_ them, and he should be compassionate about other 
people's right to have their own opinion and their own approaches to 
freedom. It is very clear that he has not even attempted to do that so 
far.

And the best way to start would be to significantly limit the 'same 
spirit' clause by putting in something like this:

 'in the event of a section of this license being rules unenforceable by 
  a court of law the FSF has the option to modify the license in the 
  most minimal fashion to make that section enforceable again'.

but this would mean RMS would have to give up power irreversibly. Will 
that ever happen?

	Ingo
-
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/