Linked by Thom Holwerda on Sat 29th Sep 2007 21:24 UTC, submitted by Kishe
GNU, GPL, Open Source "A research firm serving the mobile phone industry has published an 18-page whitepaper about open source licensing. Entitled 'GPLv2 vs. GPLv3', the paper examines the meteoric rise of open source software, and the forces that shaped each license, before concluding with an extremely detailed point-by-point comparison."
Permalink for comment 275794
To read all comments associated with this story, please click here.
RE BSD license.
by pinky on Wed 3rd Oct 2007 00:01 UTC in reply to "RE BSD license."
pinky
Member since:
2005-07-15

In some later post you write this:

>The above quoted line is an example of the lack of respect for others which I see too often in posts by overly-enthusiastic FSF supporters/

And i have to read things like "FSF doublespeak. For an organization which claims to take the moral high ground, they play the doublespeak game to a level which rivals the large multinationals."

Sorry but such statements are disrespectful too. So please practice what you preach.

Now to the topic:

>No. I mean that if you are a GPLv3 project you can take code from, say, an Apache project without changing your license. But if you are an Apache project, you cannot incorporate the GPL'd project's changes to your code back into your code without changing your license.

You don't have to change your license only the license of the whole will be GPL.

But again whether you do it or not is neither a technical nor a legal barrier it's i only a personal question.

Lets make it concrete (BSDL project wants to uses GPL code):

We agree that both licenses are Free Software licenses the basic difference is that GPL requests that the software stays free while the BSD says "do what you want".

Now a BSDL project want to use a GPL module. They can use it. There is absolutely no technical or legal barrier which stops the project.
They can use the GPL module and their code can be BSDL. Sure the complete work would be GPL because you are using parts which say that it's not only free but it also wants to stay free. But this has no effect on the BSDL code. Everyone who gets the program can use all the BSDL code under the terms of the BSDL.

The other way around is basically the same. If a GPL project wants to use a BSDL module the BSDL module will always be BSDL. So everyone who will get a copy of the program can use the BSDL part under the terms of the BSDL.

So what's stops BSD code to use GPL code? It's not the GPL who stops them and it's not any legal or technical barrier. It's is only the opinion of the author who wants a 100% BSDL program. So the only one who stops the BSD project is the BSD project by itself.

This is also exactly the same problem for authors of GPL projects who want a 100% GPL project. This author would probably refuse to use BSDL code. But than again this wouldn't be a compatibility, legal or technical problem but only a personal problem/decision.

You can combine BSDL code with GPL code and you can combine GPL code with BSDL code and in both cases every code would keep its license.

Reply Parent Score: 2