Skip to contentSkip to conversation

GPLv3 dispute solution - new open source license?

DISCUSSION Joshua David Williams 4 participants 4 messages Jun 18, 2007

lore
Share & tools
lore
#0 lore raw
Quoted 2 lines · H. Peter Anvin

You probably don't want do design a license without involving a competent lawyer. We don't expect lawyers to write kernel code, either.

True enough, and I realized this when I wrote my initial post, but it's not what I wrote so much as the concept. I haven't seen the idea come up in any threads, so I thought I'd throw it out there.

Open source and free software are clearly two different things, so it doesn't make sense that an open source project would use a free software license. The FSF has made it very clear that their objectives are very different from ours.

The GPLv2 is a great license, but it's not perfect. The FSF recognised several of the problems when they introduced the first public draft of v3. Since they are heading in an opposite direction from the open source community, I believe that we are now facing a clear dividing line between the two camps. We cannot cling to the fifteen year-old license forever, expecting to never be burnt.

If we can't adopt the GPLv3, it seems obvious to me that we need our own solution.

Signature · 1 line
It's a commonly known fact that most intruders come in through Windows.
#1 lore raw

I think that one of the main problems with the GPLv2 versus GPLv3 dispute is the discord that it saws between developers around the world. Right now, 66% is GPL, 6.5% is LGPL (using the stats from freshmeat here), 6% BSD, and the rest can be neglected ;) (see bottom of http://freshmeat.net/stats/)

That means that if someone decides that he wants to write free software (and license it under the GPL), he can choose from a large code base.

What those stats don't say, however - is how many people said "version 2 or later", and how many said "version 2".

If next people start to write software - they might be forced to use GPLv2 because they want to use other software that was only version 2. While others will start to write new software under version 3 (if only because they don't know better - like 90% of the people who copied the template with "version 2 or later").

The result is that two seperate groups of software will start to emerge that cannot use from eachother. And because both will be consirably large, that is a Bad Thing(tm).

Imho, it is much worse that this seperation of the pool of open source code will occur than everyone using version 2, or everyone using version 3, and the effect that that will have.

Now, writing yet another license for the linux kernel is therefore NOT the solution - if you get my drift.

Signature · 1 line
Carlo Wood <[email protected]>
#3 lore raw
Quoted 4 lines · Alan Cox
Quoted 2 lines

If we can't adopt the GPLv3, it seems obvious to me that we need our own solution.

Its called GPL v2.

Its not the Spirit of the GPLv3 I object to, its the hangover the next morning.

Why do I see this horse-shaped hole that people continue to want to hit with sticks?

Signature · 4 lines
"ANSI C says access to the padding fields of a struct is undefined.
ANSI C also says that struct assignment is a memcpy. Therefore struct
assignment in ANSI C is a violation of ANSI C..."
                                  - Alan Cox