I actually read the AGPL as driven by mostly pragmatic factors. It didn't even come from the FSF initially, but from a developer (Affero) who believed it fit their business strategy better than the existing licenses.
One of the traditional business strategies built on the GPL, which RMS does not greatly like, but is quite possible to do, is the dual-licensed GPL/proprietary approach. People who are willing to GPL their own software may incorporate your code under the GPL's terms. Other people who prefer more traditional commercial terms can, alternately, purchase a commercial license.
In the webapp setting this approach no longer works, because the GPL only covers "distribution", and a webapp backend is never distributed. Therefore nobody will buy a commercial license. The AGPL more or less restores the traditional GPL terms in the webapp setting, where you have to GPL your product if you ship an app containing the GPL'd code: only now, deploying a public webapp is a form of "shipping" (which is how most software devs actually do see the situation... deploying a live webapp is a modern-day form of shipping software).
And in practice, it seems the most common alternative to the AGPL in this setting is to just keep your code fully proprietary, so competitors can't build on it. I think in that sense AGPL is helpful if it encourages more releases, e.g. if it encourages more companies to take the Launchpad approach with their code (AGPL) rather than the GitHub approach to it (proprietary). The other common alternative is to release the source but under a non-OSI license like "free for noncommercial use only, commercial users must buy a license". The AGPL seems at least more generous than that.
He actually does like it:
He is very rigorous in many of his other beliefs (GNU/Linux, this "open vs "free" debate).
If he does not agree with BSD/MIT licenses because they inevitably allow companies to limit the "freedom" of their customers, how is selling an exception any different except that the open source project is now making money? I mean an argument could be made at that point that you are selling off your principles to the highest bidder. I don't necessarily believe that, but still...
Compare this to our current situation, where everyone's so used to clicking "I Agree" on an EULA screen before they can use a program that many Free Software programs (most famously Firefox) started including such screens, even though there is no requirement to agree to any terms before using them! Of course, there are usually terms related to redistribution and re-use of the code, but that can be done without ever seeing such a screen.
Stallman doesn't disagree with BSD/MIT licenses; he only advocates the GPL as a short-term measure to get to the goal quicker. BSD/MIT code is (usually) a valued contribution, as it lifts everyone up equally; Free Software is lifted, but so is proprietary software since it is trivial for anyone to repackage it as proprietary. That's fine if your goal is to advance the state-of-the-art, give unimpeded access to better security, get your ideas out there, etc. but it doesn't do very much for (or against) the goal of having mostly Free Software.
The only way to go the other way and turn proprietary software into Free Software is by a dedicated effort on the part of the copyright holder (who may be dead!). Hence the playing field is heavily biased in proprietary software's favour, which endangers the mostly-Free goal. The GPL tries to rebalance things by going the other way.
In a mostly-Free world, this bias would (hopefully) be counteracted by the inertia of Free Software, so the GPL would be unnecessary and the more permissive licenses would be a better choice.
Notice that Open Source didn't feature in the paragraphs above, since it's unrelated. That's Stallman's argument: it misses the point. He doesn't say it's intrinsically bad, although it may cause indirect harm to Free Software through distraction and confusion. Of course it also does indirect good, by leading people to Free Software who would never have been exposed to a purely Free Software message.
This is in part due to the fact that for a long time it was difficult to forgo the EULA screen on the Nullsoft Scriptable Install System, which a lot of free software projects were using for their Windows ports.
For me the question is about corporate control, rather than end-user access to the code. For this reason I see the following things as harmful:
1. Dual licensing
2. Requiring copyright assignment for contributions.
These things place organizations in control of the software, and they are things less important to more permissive licenses.
Hence my view is that the BSD license is more radically anti-corporate than the GPL.
There's the video of Brian Aker trying to antagonise rms at FOSS 2009[1], wherein rms lays out some additional rationale, if you're interested.
"Selling exceptions means that the copyright holder of the code releases it to the public under a free software license, then lets customers pay for permission to use the same code under different terms, for instance allowing its inclusion in proprietary applications."
Users still have access to the same exact code. There is no loss. He goes to on further detail what you might find confusing:
"We must distinguish the practice of selling exceptions from something crucially different: proprietary extensions or proprietary versions of a free program. These two activities, even if practiced simultaneously by one company, are different issues. In selling exceptions, the same code that the exception applies to is available to the general public as free software. An extension or a modified version that is only available under a proprietary license is proprietary software, pure and simple, and no better than any other proprietary software. This article is concerned with cases that involve strictly and only the sale of exceptions."
Sure, there's loss of what the other party builds on top of the code. While I don't think this is a real loss, the argument that it is is exactly the argument that Stallman uses against the desirability of non-copyleft licenses, so Stallman's positions on these issues seem incoherent viewed together, even if each might be viewed as reasonable enough on its own.
Ah, but the beauty of it is that the principles haven't been sold. It's still Free Software, which is all that matters. Except now, it is Free Software funded by proprietary software companies.
You can't effectively dual license software unless the public license has restrictions that don't serve your target market. The more restrictive the license, the more it favors dual licensing. This is actually my biggest concern with the GPL.
> And in practice, it seems the most common alternative to the AGPL in this setting is to just keep your code fully proprietary, so competitors can't build on it.
Efficito (of which I am a co-founder) offers hosting for a web-app based on open source software. We have few specific enhancements that don't make it upstream but those are really specific to our hosting offers (i.e. they don't provide customer-facing functionality, but provide functionality to us as hosting provider). Almost all of our work gets contributed back. The software is licensed under the GPL v2+, and the community is (I think rightly) hostile towards upgrading to the GPL v3.
I don't like the AGPL. I think that once you start encumbering services, then you have added a series of restrictions which really are even unheard of in the proprietary software world. Yes, it is pragmatic, but this is the way real freedom is lost, by insisting that practice serve some notion of freedom rather than the other way around.
In practice, the restrictions in the proprietary software world are insane compared to the AGPL, imo. There are restrictions on, to make a non-exhaustive list:
1. Commercial vs. non-commercial use. Just yesterday there was a JS chart library that got positive comments here on HN, whose terms for the free version are that you cannot make any money from sites using the charts, even indirectly (a single affiliate link on your website and it's a license violation!).
2. Number of developers. Your three-man team asked a fourth person to make some edits to the code? Now you need to upgrade your license to cover a 4-seat setup!
3. Number of deployed servers or sockets or CPUs. You're load-balancing across more than 32 cores? Now you need to negotiate an Enterprise license!
4. Number of users. You got linked on HN and got 10,000 hits today? You've exceeded the size of site that's eligible for the free license!
Would you prefer MySQL or PostgreSQL? ;-)
Here's a case of a BSD-licensed project overrunning a GPL-licensed one.
And I personally disagree with the statement that BSD-like licenses are definitely better than GPL. As always, it depends. What would have happened to Linux without GPL? Would it support as many devices as it does? Would it be as widespread as it is? On the other hand, I agree that a BSD-like license has been a plus for PostgreSQL, by permitting the existence of various 'PostgreSQL enhanced' companies selling their versions and offering support.
What's ultimately more important than the license is the people working on the project and the community that forms around it. They are what ultimately lead to success or failure, not the choice of a license.
Is it? Look at the router industry - licenses like zlib, the busybox license, and the "no copyright" sqlite licenses have enabled an entire industry to take open source software and use it for profit without having to invest developer hours to making it themselves. But they still sell that software, and take away their users freedoms, on their routers. Every time I buy a new one, I have to either look for one with an open source firmware already installed, or be very careful to make sure one I get is supposed so I can reflash it (if its even possible on some models) to reclaim my freedoms.
Tons of other embedded devices do the same. As long as Linux at least is gpl v2, they can get away with using the kernel as well as long as they don't modify it directly.
And who knows how much open source code Microsoft and Apple have in their OS installs that has been heavily modified without any of that work being contributed back to the source projects while those companies profit off license key sales?
Community is what is important, I would agree.
> Every time I buy a new one, I have to either look for one with an open source firmware already installed, or be very careful to make sure one I get is supposed so I can reflash it (if its even possible on some models) to reclaim my freedoms.
Now, why do you do this? What motivates you? Is it ideology? Or do you have a practical reason for wanting that power over the appliance?
Now, if you have a practical reason, then you have proven what I have been arguing, namely that freedom is of economic value. I.e. freedom is important not because of some abstract value but rather what you can produce with it.
If we accept that, then in the long run, software with more freedom will outcompete software with less freedom.
So what if there are a bunch of router companies selling proprietary products consisting largely of (permissive) Free Software components? It does not harm to those projects; in fact, they probably get more bug reports and other fringe benefits. So what if someone's making money off those components; is that money somehow being taken from the authors? No. That would be a claim far more dubious than even the RIAA's.
We can ask "what if those components were copyleft?", and I can think of three answers:
1) All of this whizz-bang technology we have will also be copyleft, and hence Free Software. 2) We'd have completely unknown, secret, proprietary technology in its place. This would presumably be less capable, more locked-down, less secure and likely much further behind than what we have now (since it had to be written from scratch). 3) We wouldn't have that kind of technology, since nobody finds it profitable enough to develop.
Scenario (1) wouldn't be an inevitability if those components were copyleft. Those companies aren't "getting away" with using Linux; they're using it in a perfectly legitimate way. If you find that usage unethical (like I do) then strive to: 1) (ideally) Replace their technology with something better. 2) (acceptable) Avoid using it (we managed for thousands of years without issue). 3) (unfortunate) Put up with it, but support those who are trying 1 and 2.
This is the approach I take, for example with regards to social networks.
I don't understand your point. There are people taking advantage of both GPL and BSD. Some (not all) of the GPL violators can be made to comply, and none of the BSD "violators" can be made to comply, because they are not actual violators.
All of the previous statements do not alter at all that all the software pieces that are "taken advantage of" are huge value contributions to society at large and that their success is not dependent on the license choice.
If you are angered by "other people profiting with my free software" you will of course choose GPL to have an option to sue. If you don't care, you will choose BSD or GPL for another reason. Neither option will make much of a difference on the success of your project.
But whereas it is fine that they take advantage of the GPL, because they must publish their modifications and anything linking against it, with BSD they can make all the changes they want, link to whatever they want, and sell the result.
I get you are fine with that, but some of us aren't. Which is why we use copyleft licenses and try to explain out positions like this.
> are huge value contributions to society at large and that their success is not dependent on the license choice.
LLVM vs GCC - Apple effectively built the former ground up because the latter wouldn't budge on the GPL. There are a lot of parallels - be it busybox vs coreutils, or bionic vs glibc - where the license does matter, and what happens is businesses that are uncomfortable with providing freedom spend the effort (which is entirely in their right) to rebuild the whole thing under a different license.
The license does matter. And the GPL does help, because it means you either need to preserve your users freedoms or rewrite it yourself. It is a great motivator to drive the ideology if you can put great software in front of someone and say "all it takes is you behaving ethically, and you can avoid having to write this all by yourself". But the license really matters, it is why there is this conflict of interest in the first place and not everyone just uses the GPL without hesitation.
As long as they comply. There are lots of people who don't comply and are sued where possible, which is not at all in all cases.
> LLVM vs GCC - Apple effectively built the former ground up because the latter wouldn't budge on the GPL.
And how is that better for the world, duplicating functionality and reinventing the wheel?
And what I've said twice (and now thrice) is that the license choice does not determine the SUCCESS of a project. People are a way more important factor.
As you said, you need that great software and awesome community, but you need it FIRST.
Healthy competition. Fresh ideas. Something to turn to should there be an unfixable problem with the other thing.
Monocultures are dangerous and come with a high risk of stagnation.
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.
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.
1. I think that enumerating freedoms is at best a waste of time and at worst a way to justify abridging the freedoms that matter.
2. I think the question really is who gets to direct downstream licensing and under what circumstances. The MIT license allows an individual to add restrictions to the license without even making contributions. The AGPL encumbers services provided with license terms. The other licenses are in the middle.
Instead of enumerating freedom, I would rather define it, namely as the right to engage in economic production without upstream obligations. From this viewpoint, the AGPL is significantly less free than the license of the closed source redistributable libraries that come with Microsoft Visual Studio. Since I find the latter too restrictive for my taste, I won't touch the former.
They might be compatible with the GPLv3, because of its allowance of extra terms; they are strictly incompatible with the GPLv2, een though the FSF claimed that they were compatible with it when the GPLv2 was the current GPL version (the FSF's claim that they are compatible -- a self-interested one to induce people to relicenses BSD-licensed code as GPL-licensed code, is indefensible since both versions require specific copyright notices, the BSD license itself, and the specific disclaimer of warranty included as part of the BSD license, and all of those requirements are additional requirements incompatible with the GPLv2.)
The FSF has an overt interest in promoting the relicensing of code under the GPL which gives them a motive to exaggerate the degree to which this action is valid under other licenses. They are not neutral, objective party when it comes to license compatibility.
Here's my take. The 2/3 clause BSD licenses are clearly compatible with the GPL v2 because they offer a strict superset of rights. I.e. they don't offer any restrictions not found in the GPL v2. Consequently the work as a whole can be licensed under the GPL v2 without worrying about whether any piece of it has additional permissions which satisfy the license.
The GPL v3 however provides some real reasons for caution here. The additional permission section is clearly compatible with the MIT license, but is clearly incompatible, as it stands, with the BSD license which does not explicitly grant sublicensing rights (meaning you can't relicense someone else's BSD code under the GPL without their permission). So you can't include BSD licensed code and count on the additional permissions section as protecting you. (This is based on my discussions with Richard Fontana and other lawyers involved in free software issues.)
The question then becomes whether section 7(b) legal notices can be read broadly enough to include the BSD license. I.e. the author of the BSD licensed code is merely giving notice that all users have the permission, directly from him, to use the code as allowed under the BSD license. This is not an additional permission under the GPL, but an additional permission directly from the author, and notice is merely being preserved.
If this is the case, then the GPL v3 is compatible with BSD licenses which do not have an obnoxious advertising clause. But if it is not, and if all additional permissions must be removable even in the absence of software modification, then they are incompatible.
Freedom certainly can be defined in such a way, even if you don't happen to fall in with that definition. Put bluntly the big question between the two major license types is whether you're pushing for individual freedom or collective freedom.
Rather I think the point that Stallman misses (or more likely, chooses to argue against) is that many open source programmers deliberately choose not to be "Free Software" political activists, but simply choose open source licenses for technical or social (but not political) reasoning. They don't want to save the world, they want to sling the best code.
He hopes to communicate to those who have that short-sighted view, that their interests are not best served by focusing on just the code.
It's an attitude which says that as long as the elite class of techies get freedom to do as they like, that's good enough. The freedom of the end-users does not matter, even to the point that when Free Software advocates ask developers to take their end-user's freedoms into account, that request is met with outright hostility.
It's a very selfish and one-sided type of freedom. Freedom for us, not for them. Freedom to oppress, monetize and lock-in the peons who don't know how to code.
I actually don't see the additional restrictions in the GPL as doing much for end users, per se. The real beneficiaries are still developers, just developers one level further removed from the licensor than the beneficiaries of the freedom in permissive licenses. But if you think that a substantial portion of the people using your work under a permissive license are themselves likely to offer a Free/Open license (whether permissive or copyleft), a copyleft license actually may reduce the freedom actually experienced by the indirect beneficiaries as well as that experienced by direct licensees.
Well, no.
The question (if you read the blog post I linked to) is whether you go for institution-centric and centralizing controls here or whether you go for decentralized controls and questions of community structure.
The point is the best protection for everyone is widespread ownership over private property. Ownership means "the right to use" here. The BSD licenses demand greater community controls because the community cannot survive without them.
> Freedom to oppress, monetize and lock-in the peons who don't know how to code.
And yet, if you demand that there be a stronger power capable of preventing oppression, then you typically get stronger organizations more capable of oppression. The end goal is, really, to decentralize and ensure that end users have a choice of what to use.
Interestingly I am living in Indonesia right now. It is amazing to see a Distributist economy in motion and see that, although the nation is poor on paper, the society functions for the poor much better than it does in the US, and so real poverty is far less of a problem. Sure the poor may have fewer television sets than in the US but they do have better access to housing and wholesome, nutritious food.....
The reason why things work so well is because the economy is so heavily decentralized. 70% of the economy is self-employed. Self-employment means that capital and labor are not separate. This is what the freedom to produce things with the software has to offer our economy.
Less permissive licenses, and the GPL in particular, restrict both users and techies.
Users can be subject to oppression, monetization and lock-in if they are willing. But it is their choice. And if they so want, they can grab that free code and hire a developer to "oppress, monetize, and lock-in" the other guy. If he is willing to be oppressed.
BSD allow anyone to do anything to BSD code. GPL prevents developers from doing everything to GPL code. That says more about users being selfish and eilitst than the other way around.
Why? Just because they are end-users means they are better then me? That's exactly selfish right there.
How is "freedom to engage creative or productive endeavors without micromanagement from others" not a "freedom from restriction"? Is the implication here that using the GPL is tantamount to "micromanagement from others"? Because I don't really see it.
>one need not worry so much about people misappropriating things because in the end they cannot out-compete what is free and open. Yeah, SunOS forked from BSD. How is it doing these days compared to the open source versions?
That's not the example I would pick. How about Apple forking FreeBSD?
>The question, rather literally is who has a right to tell you what license your works go under
I'm not sure what this has to do with GPL vs BSD. Nobody has the right to force you to use a particular license. Ideally, nobody gets to change the license of code you wrote either, just because they changed a variable name. It is this particular guarantee that the GPL provides and BSD doesn't.
OpenBSD uses it.
When ever I see this question put forth regarding GPL, I see it as extremely dishonest question. No one want to license software just for licensing sake. What some people want to do is to prohibit copying, modification and usage of work in order to create profits.
The question you actually asking is: Who has the right to tell if restrictions on copying, modification and usage is allowed on a work. It has nothing to do with freedom, and the answer is always going to be the author. Political philosophers has long since past agreed that permission to restrict other people freedom is not liberty.
Read the full blog post. The question goes effectively to a question of enumerated liberties vs work ownership, and myself siding with the latter. There may be lots of reasons to license or not under the BSD license but once you do, then you are saying that anyone downstream gets to own their own work.
Again I define "own" and "work" in the piece. I would recommend you read it.
Usually the biggest barriers to entry by free software are network effects and proprietary agreements. See the recent article about Bloomberg
http://mattturck.com/2014/03/19/can-the-bloomberg-terminal-b...
(I bet someone at bloomberg read it because they released an article the next day: http://www.bloombergview.com/articles/2014-03-20/tesla-can-t...)
Again, freedom is economically valuable.
How is BSD doing compared to Linux? (Keeping in mind that BSD is officially something like 20 years older than Linux.) I wonder how much better it would be doing if it hadn't been forked so many times by so many really smart people in the 80's and 90's?
It's hard to say for sure. However, from what I have seenof the FreeBSD community, they seem quite active and vibrant.
I did a little research to try to figure out what you meant; tell me if I have it right:
MIT allows you to redistribute the code under a different license. The problem is that the sublicense might be more permissive than the MIT license, potentially allowing someone to bypass the requirements of the MIT license.
Is that what you meant?
One right that can be passed on is the right to sublicense, which gives the licensee the right to issue new licenses. The licensee cannot provide downstream licenses to rights he or she did not receive. So the license can never be more permissive than the existing one.
The difference is that under the BSD license, the original author grants licenses and requires notice on downstream redistribution. Someone can add code, however, and add restrictions to that code. The MIT license allows something very different, which is the right of a mere licensee to negotiate licenses (provided they are no more permissive than what was granted) on behalf of the licensor.
So you can take MIT licensed code with no changes and relicense it under the GPL. The BSD license requires that you license only your code in it (and the corresponding work as a whole) under the GPL, but the MIT license allows you to add restrictions to code you did not author.
The question, rather literally is who has a right to tell you what license your works go under, and under what circumstances. If freedom to create things is economically valuable (and I think it is), then one need not worry so much about people misappropriating things because in the end they cannot out-compete what is free and open. Yeah, SunOS forked from BSD. How is it doing these days compared to the open source versions?
These days, my preferred license is the BSD license. I am uncomfortable with the MIT license's sublicensing grant, and I am even more uncomfortable with the AGPL, which strikes me as a demonstration that freedom in the name of freedom is ultimately self-consuming and self-defeating. I am willing to tolerate the GPL and in fact most of my works are licensed under that license for legacy code reasons.
But I still prefer the BSD license. This license is very simple. I own my work and give everyone else a right to use it. They own their own contributions and an decide how to license those. Since freedom to create new solutions with the software is economically valuable, there I can expect that the original BSD-licensed versions will win out over the long run.
[1] http://ledgersmbdev.blogspot.com/2013/04/a-distributist-view...