GPLv3 & additional permissions/restrictions [LWN.net]

GPLv3 & additional permissions/restrictions

Posted Sep 26, 2006 11:35 UTC (Tue) by mingo (subscriber, #31122)
In reply to: GPLv3 & additional permissions/restrictions by drag
Parent article: Some GPLv3 clarifications from the FSF

So following your logic wouldn't that make ALL GPLv3 code essentially "GPLv3 + permissions" pretty much automaticly? And how would it be democratic to force authors who may want their code to be "GPLv3 pure" and have other people make it "GPLv3 + permissions"? Maybe I am just tired, but none of that realy makes sense to me.

yes, that's my point - it makes no sense either way. There's just no solution i can see at all but to get all developers in the GPL ecosystem agree - anything else will result in inequality on either the "restrictive" (pure) side or on the "permissive" side.

The reason for that inequality is that in an assymetric licensing model there's just no technical way to determine who put how much effort into some code, hence there is simply no mechanism to be fair - the only solution is equal treatment.

I see the GPLv2 as a pretty well working "agreement" that isnt perfect but seems to unify alot of people who ended up writing a body of code that currently consists of 300+ million lines of code and who are currently producing tens of millions of new lines of code per year. Trend: "accelerating exponentially". I'd be very, very careful to mess with that powerful machinery.

(Log in to post comments)

GPLv3 & additional permissions/restrictions

Posted Sep 26, 2006 19:38 UTC (Tue) by drag (subscriber, #31333) [Link]

I think that how it is stated in GPLv3 is how GPLv2 works right now.

Say I modify a GPLv2 and add some permissions. Now that's not GPL proper anymore, but basicly it's the the same thing as saying GPLv2 + permissions.

Now that code is still GPL compatable and a person can strip away those permissions and use it in a "GPLv2" proper. The original author now can't turn around and use code from that GPLv2 proper program and add permissions without special agreement with the copyright holders.

So that is the way the GPLv2 works right now, is it not?

Isn't this part of the 'viral' nature of the GPL and the sort of thing people having to work with 'GPL compatable' licenses have to deal with on a regular basis?

To me it's no difference between GPLv2 and GPLv3 in this regard. I think that this GPL+permissions language was added to make the GPL to be more 'universal' and work the same way in more countries as it works in the U.S. or most places in Europe. Different countries may not interprete the GPL in the same way as their copyright laws maybe different or they use different conventions. But you'd have to ask the FSF people about that.