Linked by Thom Holwerda on Wed 28th Mar 2007 21:02 UTC, submitted by Ali Davoodifar
GNU, GPL, Open Source The FSF has released the third draft of the revised third version of the GNU General Public License. Some of the changes in the new draft, such as the increased clarification and legal language, or the housekeeping changes that reflect new aspects of the license are likely to be accepted. However, the license also includes a new approach to the controversial issue of lock-down technologies as well as more explicit language about patents, including language designed to prevent a re-occurrence of agreements such as the one that Novell entered into with Microsoft - all of which is apt to kindle heated debate as the revision process enters its final stages after fifteen months of intensive work.
Thread beginning with comment 225463
To read all comments associated with this story, please click here.
Let's see
by sigzero on Wed 28th Mar 2007 22:33 UTC
Member since:

- GPL3 goes final
- Linus keeps Linux kernel at GPL2
- Too many people against GPL3
- All GNU tools forked off the GPL2 version and development continues
- Everything keeps going skipping GPL3 altogether

The license sucks for the very fact that it has pretty much split the community and will continue to do so after its release.

Edited 2007-03-28 22:34

Reply Score: 5

RE: Let's see
by TechGeek on Wed 28th Mar 2007 22:43 in reply to "Let's see"
TechGeek Member since:

The kernel is its own beast. Changes cant be made whether Linus wants to or not. As for the rest, you dont know how many people are going to be against this GPLv3 draft since it just came out. This one seems to be a lot more even handed than the last. Theyve taken out hardware restrictions and talk completely about the software. As for forking, that will depend on the major distributions. Few will adopt GPL3 on their software if it means they will automatically get forked (for the most part)

Reply Parent Score: 1

RE[2]: Let's see
by unavowed on Wed 28th Mar 2007 23:12 in reply to "RE: Let's see"
unavowed Member since:

Actually I remember having read a comment by Alan Cox saying that Torvalds may have just removed the "(or any later version)" clause some time into the development process, which would invalidate such a change.

A search on Google returned this LKML post (I don't remember if it's the same one, but it's still interesting):

Edited 2007-03-28 23:17

Reply Parent Score: 3

RE: Let's see
by sbergman27 on Wed 28th Mar 2007 22:45 in reply to "Let's see"
sbergman27 Member since:

The license sucks for the very fact that it has pretty much split the community and will continue to do so after its release.

It hasn't even gotten started yet. The *real* damage starts after its release date, when the division of the community goes from being a concept, which can be repaired, to being a matter of law, which can't.

Edited 2007-03-28 22:46

Reply Parent Score: 4

RE[2]: Let's see
by jessta on Thu 29th Mar 2007 00:32 in reply to "RE: Let's see"
jessta Member since:

when you refer to 'division of the community' what are you talking about?

Are you refering to the fact that GPLv3 won't be compatiable with GPLv2?
- This hasn't been a problem in the past with many licences not being GPLv2 compatible.(eg. BSD)

This won't be a problem because developers who originally released their software under GPLv2 wanted to enforced continued freedom in the use of the code they write(otherwise they would have chosen something like BSD Licence). GPLv3 will continue this enforcement while pluging up some holes in GPLv2, so I can't see why many projects wouldn't relicense if they can.

For those to value freedom in there software I can't see the GPLv3 really changing much.

Reply Parent Score: 5

RE[2]: Let's see
by dylansmrjones on Thu 29th Mar 2007 21:12 in reply to "RE: Let's see"
dylansmrjones Member since:

What division? There is going to be no division here. It is for all matters just another license. GCC can go GPL3 and the Linux kernel can stay GPL2 and whatever package can stay as it is.

Reply Parent Score: 2

RE: Let's see
by h times nue equals e on Thu 29th Mar 2007 07:59 in reply to "Let's see"
h times nue equals e Member since:

As this is thrown up quite frequently, I decided to do a little investigation on the topic of

"Why, for the Flying Spaghetti Monster's sake, should anybody have to fork the GNU tools when GPLv3 arrives?"

As IANAL, you are of course very welcome to correct and/or augment my findings. Thanks in advance.

First of all, the glibc is covered by the LGPL and not the GPL[1], which pretty much ensures, that even non-compatible licensed code (yes, closed source, proprietary code too) can link against (or like they word it: use) it.

5. A program that contains no derivative of any portion of the Library, but is designed to work with the Library by being compiled or linked with it, is called a “work that uses the Library”. Such a work, in isolation, is not a derivative work of the Library, and therefore falls outside the scope of this License.

In related news, the FAQ of the GNU[2] project addresses the problem of developing code with incompatible licenses explicitly[3]:

Q: Can I use GPL-covered editors such as GNU Emacs to develop non-free programs? Can I use GPL-covered tools such as GCC to compile them?
A: Yes, because the copyright on the editors and tools does not cover the code you write. Using them does not place any restrictions, legally, on the license you use for your code.
(Q: and A: added by myself for the
sake of clarity)

If soon-to-be GPLv3 covered projects, like perhaps SUN's Java use a classpath linkage exception[4], they more or less emulate the behavior of the LGPL and won't cause any direct problems too (not that SUN's Java is a part of the GNU tools, but gjc is).

So, for me, the situation boils down to this:

- A GPLv3 covered GNU toolchain won't hinder the Linux devs from developing, testing and debugging their GPLv2 covered kernel, as long as they don't transfer code from the GNU tools directly to their kernel (and although I'm no big guru when it comes to kernel development, I doubt that significant parts of the kernel are for example derived from the C compiler). If I interpret the FAQ correctly, even MS could develop their Windows operating systems using gcc and g++ without fearing the anger of the mighty GNU :-).

- most FOSS software with a strict GPLv2 policy I'm aware of is very tightly bound to kernels (poster child example: BusyBox with their GPLv2 only[5], although they state on their homepage[6], that they are under GPLv2 or later, weird) and probably can't but in generally don't need not to fork for similar reasons either.

- Proprietary software, that needs to interface with the glibc (and analogously licensed works) can still do so by virtue of the LGPL.

- I don't see many projects who had no problems using the GNU userland tools under GPLv2 dropping it, because they would have had already alternatives available under less restrictive terms (BSD-fileutils, for example).

Basically, the GPLv3 should - in large - not affect people, companies and projects, that have already tried to comply with both letter and spirit of the GPLv2.

My personal opinion is, that entities, that generate an income from a dual-license model should have a pretty big motivation to go for GPLv3, as this increases the possibility to sell licenses for their products, that allow a direct proprietary usage. As of this, I personally would not read too much into actions like MySQL removing the "or later" clause from their product, as it is a different thing to feature such a clause, when the GPLv3 is a distant event on the horizon compared to a situation, where the release is nearing steadily and still large changes (compare this draft to the previous ones) are possible.

As of MySQL, Trolltech and their likes, they are typically the sole holders of the copyright for their projects and therefore in the position to maneuver very agile wrt license changes.

Neglecting the later-as-March-28-2007 addition for a moment, the only ones, that I see in need of forks of the GNU (and other, like SAMBA for example) tools are entities like Novell, who plan or do base their business model on exploiting a bug in the GPLv2.

As I said above, please feel free to correct / augment / contradict my findings, thanks for your attention.


EDIT: fixed some typos I spotted and clarify the Novell relevant part wrt 2007/03/28 clause.


Edited 2007-03-29 08:15

Reply Parent Score: 5