I, OTOH, given the conflict between Stallman's position on selling GPL exceptions vs. his position on non-copyleft licenses, and given the GPLv3's domain-based discrimination in what is required freedom, thing Stallman and the FSF have ideologically incoherent positions.
> I disagree that BSD solutions will necessarily "win" in the long run. There's no incentive to share.
There is only no incentive to share if you think that open source has no independent value to producers, that its a sacrifice they make in order to be permitted to use others work. While the GPL model and a mass of early high-quality software licensed under that model was probably essential in getting people to accept the value to producers of open source, once that value was widely accepted -- as it now is by many major software producers -- the incentive to share isn't from someone holding a gun to the producer's head, its from the value of community engagement with the code that permission to use it fosters.
With BSD, there is no legal incentive for somebody to take their ball and go home, or take your ball and sell it. Depending on what you want, that can be a good thing.
Making commercialization difficult is not always bad -- if you own the copyrights, you can license to commercial users under terms favorable to you.
Wanna stop basically everything commercial related? AGPL
Wanna stop tivozation? GPL 3
Wanna allow tivozation? GPL 2
Wanna allow general commercialization? 2-clause BSD
EDIT: if anyone remembers the OSS license feature matrix site that's new, plz reply.
It stops anyone from using the code (including extensions to the code) as a unique differentiator. In no way does it prevent "everything commercial related". If there are other barriers to entry, you can still perfectly well charge for access to a service running AGPL code.
The whole business of the company I work for, and of the large network of peers around the world, is built around a piece of AGPL licensed software called OpenERP[1].
In other words, my paycheck disagrees with you :)
It's just another way of being proprietary by obscurity.
If you use BSD, MIT, etc, you can't combine any GPL licensed code.
You have more possibilities of combining code by choosing GPL for your project.
But GPL is the license that rather explicitly forbids combining with some licenses.
EDIT: If you're saying that you cannot combine free with "free" and remain free, then you're right -- you cannot combine MIT with GPL.
And you're right in that a nonfree project can incorporate free code into it. So they have more options, but the end result remains nonfree.
So if I'm going to subject myself to licensing restrictions, it's silly to restrict myself to some code.
Care to shed some light on your or your lawyer's interpretation of the license? Can you point out what causes incompatibility?
The GPL on the other hand does prohibit many licenses. Whether you want it or not. Or whether the people who use your code want it or not.
In the LedgerSMB project, I have started licensing core framework libraries under the BSD license because that should allow easier bridging to proprietary software. We started doing this with PHP libraries, but then decided that Perl shouldn't be a second-class language integration-wise.
There's no reason that GPL code can't depend on BSD code.
These licenses can co-exist and one can choose to license some parts of a project under the GPL and others under a BSD license.
If you want a software package that you own to be openly collaborated, but still controlled by you, the GPL is a great copyright construct to do that with.
There isn't a right answer here. I think Stallman has an ideologically pure argument that is appealing to me as a consumer, but not always ideal for my business needs.
I disagree that BSD solutions will necessarily "win" in the long run. There's no incentive to share.