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: <orabv0x1gh.fsf@oliva.athome.lsd.ic.unicamp.br>
Date:	Fri, 15 Jun 2007 20:06:06 -0300
From:	Alexandre Oliva <aoliva@...hat.com>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Daniel Hazelton <dhazelton@...er.net>,
	Jesper Juhl <jesper.juhl@...il.com>,
	Alan Cox <alan@...rguk.ukuu.org.uk>,
	Chris Friesen <cfriesen@...tel.com>,
	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

On Jun 15, 2007, Ingo Molnar <mingo@...e.hu> wrote:

> * Alexandre Oliva <aoliva@...hat.com> wrote:

>> >> You're again confusing legal terms with the intent.  The legal 
>> >> terms provide an indication of the intent, but the preamble, along 
>> >> with the free software definition it alludes to, do an even better 
>> >> job at that.

>> > And the preamble, not being part of the active portion of the 
>> > license, has absolutely *ZERO* bearing. Just as it is not the 
>> > *intent* of RMS, the FSF or *ANY* person (or legal entity) that had 
>> > a hand in crafting the GPLv2 or GPLv3 which is looked at when 
>> > determining the "intent" of the license. It is the intent of the 
>> > person and/or "legal entity" that has placed their work under said 
>> > license.

>> No disagreement.  You keep forgetting that I'm not here to say what 
>> Linux licensing means or doesn't mean.

> it is _you_ forgetting to read what you wrote just 1 mail ago above. 
> _Read_ it:

>   "The legal terms provide an indication of the intent, but the 
>    preamble, along with the free software definition it alludes to, do 
>    an even better job at that.".

You still don't seem to get the difference between spirit and letter,
and the difference between author of the license and licensor of the
software (I guess I wasn't clear about this).

When I talk about the spirit of the GPL, I'm talking about how its
authors designed it, how they described their motivations in the
preamble, in the Free Software Definition, in speeches explaining it,
etc.

When I talked about the meaning of the Linux licensing above, I'm
talking about the intent of the Linux authors when choosing the GPLv2.

They aren't necessarily the same.

Some Linux authors may have read the preamble and understood something
else.  Some may have simply skipped it, and focused in the legal
terms.  Some even understood the legal terms in different senses.  But
they have all agreed to license their code under GPLv2, whatever the
motivations each one of them had, and none of them has to match the
spirit of the GPL.


Now, the spirit of the GPL, the intent behind its design, is something
that may be entirely different.  And when I say that GPLv3 didn't
change the spirit of the GPL, I'm saying that from the perspective of
someone who understands very deeply the philosphy and motivations
behind it.


Please understand that these are two separate issues.  That the spirit
doesn't change, and that you don't share that spirit, or that you
didn't think that was the spirit, doesn't justify a claim that the
revision is changing the spirit.  It's not.  The spirit is, and has
always been, to defend users' freedoms (the 4 freedoms of the Free
Software definition), such that Free Software remains Free.


The fact that they can be different means that GPLv3 may not match the
goals you had when you chose GPLv2 for your contributions.  That's
unfortunate.  But this doesn't mean that GPLv3 is changing the spirit
of the GPL.  It's merely exposing that your goals don't match the
spirit of the GPL.  There's nothing wrong about this, GPLv2 is not a
bad license, just like the LGPLv2 is not a bad license.  They just
don't defend users' freedoms as well as GPLv3 will do.

-- 
Alexandre Oliva         http://www.lsd.ic.unicamp.br/~oliva/
FSF Latin America Board Member         http://www.fsfla.org/
Red Hat Compiler Engineer   aoliva@...dhat.com, gcc.gnu.org}
Free Software Evangelist  oliva@...d.ic.unicamp.br, gnu.org}
-
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ