13 ms·
I think this is an important distinction to be aware of. Licenses like the GPL exist for a reason. And that reason is an attempt to maximize the amount of sof
by btilly 11y ago
I think this is an important distinction to be aware of.
Licenses like the GPL exist for a reason. And that reason is an attempt to maximize the amount of software that is free.
Licenses like the MIT and BSD license exist for a different reason. And that reason is to give people who want to share what they did on generous terms a way to do so. And historically this was done in the belief that enlightened users would see it as being in their interest to contribute back.
The result was that people who used generous licenses got frustrated that others would come along, use their software, criticize the original author for "not protecting freedom", then create a modified version that the original author was not free to use as they wish!
Historically the free software movement was very clearly described with long essays by Stallman. With the open source marketing campaign, there were essays that people who liked more generous licenses could get behind. And indeed lots of people began producing free software with no encounter with the ideas that started the free software movement. The link above was Stallman's response to this.
If you understand the conflict, then you can form your own opinion. Here is mine.
When you choose a license, you should choose correctly for what you want to have happen. Would it outrage you for someone else to take your code, put a pretty GUI on top, sell it, and make millions while you make nothing? Well then, you shouldn't use a BSD license. By contrast you shouldn't use the GPL if your response would be, "Bully for them, I had fun and they made the world better."
Conversely if someone else used an open source license, DO NOT assume that their motivations are yours. It is their code with their choice of license chosen for their reasons. Respect that.
- PaulHoule 11y agoFor instance, the Gnu Public License serves the needs of Oracle very well and quite possibly helped MySQL AB be salable to Sun and thus to Oracle. Most of us who use MySQL are limited by the GPL, whereas Oracle has the right to use it in other ways, license it to specific customers on different terms, etc.
- iwwr 11y agoThat's why Stallman prefers distributed code copyright: if contributors own their contributions, then dual-licensing won't work. On the other hand, this prevented a project like the linux kernel from moving to gplv3 since the distributed corpus of contributors could not all agree to switch.
- btilly 11y agoStallman does? Historically the FSF required copyright assignment for FSF works. This was to avoid having any potential problems where a contributor thought they were OK to contribute, but the employer potentially had a "work for hire" claim. (The ease with which such claims can exist varies by local law, and many are not aware of the fact that they have such a liability.)
- icebraining 11y agoHistorically the FSF required copyright assignment for FSF works. This was to avoid having any potential problems where a contributor thought they were OK to contribute, but the employer potentially had a "work for hire" claim. How would that work? If you don't have the legal standing to contribute to the project, you certainly can't reassign the copyright to another party. The copyright assignment is so that the FSF can sue if someone break the project's license. They also require a disclaimer that the work isn't for-hire, but that's a different issue. http://www.gnu.org/licenses/why-assign.en.html http://www.gnu.org/licenses/why-assign.en.html
- btilly 11y agoThe process of getting the employer disclaimer mentioned in your link exists exactly to catch cases where the contributor was mistaken about their ability to legally contribute.
- icebraining 11y agoYes, but the disclaimer is not the copyright assignment, they're different legal acts.
- btilly 11y agoTrue, they are different forms. However they are both part of the process of making sure that the FSF actually owns that copyright.
- nanny 11y ago>For instance, the Gnu Public License GPL stands for "General Public License", just fyi.
- sarciszewski 11y agoI write open source application security software (e.g. https://github.com/paragonie/easydb https://github.com/paragonie/easydb) and use a very permissive license to encourage the wider adoption of better practices. I don't care if I make some schmuck billions of dollars off my work while I suffer through poverty (which won't happen from a simple DB library), I care about making the Internet more secure, even if only a little. (My motivation was this blog post http://www.thoughtcrime.org/blog/saudi-surveillance/ http://www.thoughtcrime.org/blog/saudi-surveillance/ by moxie) However, for everything else, I'm inclined to use GPLv3 / AGPL and offer commercial licensing under MIT for companies (h/t 'patio11) instead. Just my $0.02
- icebraining 11y agorms himself has advocated for permissible licenses to encourage wider freedom (e.g. in the case of libogg).
- btilly 11y agoHe always does so for strategic reasons. For example with libogg he was primarily concerned that the world would get locked into proprietary video code that was patent encumbered. (An issue which has happened a number of times. For example at various points free software had trouble with patents on things like the compression algorithm used by the gif format, and the RSA algorithm used in encryption. Both are thankfully long expired now. But video encodings in particular have a ton of patent issues.)
- JoshTriplett 11y ago> However, for everything else, I'm inclined to use GPLv3 / AGPL and offer commercial licensing under MIT for companies Do you actually use MIT, or something similarly permissive but without permission to redistribute in source form? Because offering a true MIT license to paying customers means they could then redistribute that version to everyone. (Of course, doing so might mean they don't get any future versions from you under that license, but still...)
- coldtea 11y ago>Licenses like the GPL exist for a reason. And that reason is an attempt to maximize the amount of software that is free. Does that work well out in practice though? I think companies are much more likely to work with and contribute to open source programs if they are MIT/BSD/Apache. >The result was that people who used generous licenses got frustrated that others would come along, use their software, criticize the original author for "not protecting freedom", then create a modified version that the original author was not free to use as they wish! How many cases has that happened?
- btilly 11y agoDoes that work well out in practice though? In 2015 most of the internet is running on free applications running on top of free operating systems and commercial companies are spending billions to maintain this situation. If you had predicted that circa 1990, you would have been dismissed as a lunatic. So something resembling success has happened for the free software movement. And no matter how you ascribe credit, it is hard to say that it would have happened without RMS. How many cases has that happened? A lot, but you don't hear about it if you're not swimming upstream trying to maintain code under a generous license. For a random example where it boiled out in public, see http://lwn.net/Articles/247872/ http://lwn.net/Articles/247872/.
- icebraining 11y agoI'd rephrase parent's statement to "that reason is an attempt to maximize the relative amount of software that is free." So, if with BSD/MIT you'd end up with a few more contributions, but you'd also help a few companies build proprietary software that restricts their users, it's better to use GPL since fewer users end up being restricted by proprietary software. And yes, I know that the users have the choice to not use proprietary software, but regardless of that discussion, that still doesn't mean you should help that happen.
- Tyr42 11y agoSo, OpenWRT (https://openwrt.org/ https://openwrt.org/) exists only because of the FSF enforcing the GPL. A non-complient company tried to unlawfully withhold it, and only because the GPL has some teeth did it actually end up with the source available.
- Sir_Substance 11y agoI really don't get why people don't just declare their work public domain. I hate having to dig through and grok licenses to figure out what using some random library does to the precarious legal framework of my project. Developers often engineer software dependencies badly, but we don't bother engineering legal dependencies at all, we just slap them in like new coders copy-pasting from stack overflow. I see people saying this: >Licenses like the GPL exist for a reason. And that reason is an attempt to maximize the amount of software that is free. But mostly I think they are really concerned about this: >Would it outrage you for someone else to take your code, put a pretty GUI on top, sell it, and make millions while you make nothing? It's just another means of jealous control. We bag commercial licenses for stealing developer freedom, and then willfully use licences that deliberately obstruct people from using our work as a foundation for successful entrepreneurial efforts, because we can't handle the idea, even the /mere possibility/, that someone might be more successful with our own project then we are. We even have the nerve to pretend that we're being generous when we do this! I think it takes guts and trust to really let your work go, but I'd like to see more of it. I also truly believe that making our works public domain will foster innovation now we have tools like github that allow living public domain works. People won't stop contributing just because you aren't forcing them, BSD is proof of that, and I'd be using way more open source libraries and doing way less Not Invented Here if I didn't have to wade through legalese to do so.
- deleted 11y ago[deleted]
- kazinator 11y ago> I really don't get why people don't just declare their work public domain. Firstly, people do. Secondly, those who do are uninformed. Declaring your work to be "public domain" does not actually place it in the public domain. It in fact remains copyrighted. Passage into public domain occurs when a copyright expires.
- Sir_Substance 11y agoThat's actually not correct, you can willingly and deliberately forfeit your copyright.
- kazinator 11y agoI use the BSD license for all the GPL reasons, plus one more: I am not bothered by the existence of other uses, and do not wish to eradicate them. I don't see them as a threat. The free version of the code is there, and gives users all the same rights as the GPL, and more. I like all the freedom and sharing as does Stallman. I just don't see proprietary software as evil, and I don't think that if I prevent some code of mine from being proprietized, that I'm striking some blow against proprietary software. If anything, it might backfire: instead of using my quality, debugged code, they will have to choose something else that is perhaps not as good (or worse: whip something up from scratch). Somehow, in some way, that will come back and bite me.
- belorn 11y agoWhile I believe there are those who is genuine when saying that, I am a bit burned by all those people who would quickly complain if someone made a patched version of their code and put it under GPL.
- kazinator 11y agoYes, that's just silly. If you allow proprietary use of your code (Microsoft can compile it into a binary and ship it with Windows without source) how can you possibly have a fit over it being used in GPL-ed code. What I would do is help myself to their patch, if it's worthwhile and backport it to the BSD-licensed version. The code is my copyright, and the patch is a derived work of something of mine; therefore I own it and it falls under my license. Not to mention that if you take someone's BSD program, and just slap a GPL on it, it doesn't actually hold. Once the users are aware that it's actually a re-labeled BSD program from another author, they can just go with that license.
- japhyr 11y agoAre you sure that's correct, from a legal perspective? If I release an MIT project, someone makes a GPL fork with a significant new feature, wouldn't pulling that feature back into my project make my project GPL?
- japhyr 11y agoWhen I choose MIT over GPL I'm usually trying to make my work as easy for others to adopt as possible. I want some of the software I wrote to become a commodity. The MIT seems a clearer path to commoditized software than the GPL. Is that a reasonable line of thinking?
- icebraining 11y agoYes, and in fact rms himself has made that decision in the past.
- japhyr 11y agoThat's the LGPL, right?
- icebraining 11y agoNo, rms actually support moving from the LGPL to BSD, to achieve the maximum possible reach of the software: http://lists.xiph.org/pipermail/icecast-dev/2001-February/000005.html http://lists.xiph.org/pipermail/icecast-dev/2001-February/00...
- mikegioia 11y agoI think this is for one hyper-specific case that he in fact "okayed" the switch to BSD. In response to the change of license, Richard Stallman of the Free Software Foundation says, "I agree. It is wise to make some of the Ogg Vorbis code available for use in proprietary software, so that commercial companies doing proprietary software will use it, and help Vorbis succeed in competition with other formats that would be restricted against our use.
- bahamat 11y agoThe problem with the GPL is that it presupposes its own supremacy and refuses to work with other free licenses. Two prime examples are MPL and CDDL (which was based on the MPL). Both of which GNU regards as free software licenses, but says to not use them because they don't bow to the FSF. The binary in memory linking clause is the most harmful thing to ever happen to free software. It destroys collaboration and restricts user freedom. It causes partisanship and infighting within our communities and prevents good ideas, the best ideas, from being freely shared (breaking both freedoms 2 & 3!). GNU has declared war on other licenses for far less than that. Can we all admit that the in memory linking clause makes GPL non-free software? We'd all be better off to realize it.
- phkahler 11y agoLicense proliferation was a problem largely supported by the OSI. IMHO there are really only 3 free/open licenses necessary - GPL, LGPL and BSD (or MIT). Anyone else is trying to be open or free while also supporting some other agenda. If you want it both ways, go dual lincense with GPL and a commercial license. Just be up front and honest about it. That said, I need to reread GPL3 in detail...
- ArtB 11y agoDon't forget the AGPL.
- reitanqild 11y agoGPL is just a subset of AGPL, isn't it?
- dredmorbius 11y agoThere are a few other variants. Affero, as noted, also the Mozilla Public License, which applies on a file-by-file basis and allows for proprietary code to be integrated into a MozPL licensed work as a whole and distributed. But otherwise, yes: GPL, LGPL, BSD/MIT are the principle cases.
- rmc 11y ago> * Would it outrage you for someone else to take your code, put a pretty GUI on top, sell it, and make millions while you make nothing? Well then, you shouldn't use a BSD license.* Pedantically, with the GPL, that could happen. However it'll be a GPLed GUI programme. That sort of business, selling units of software, doesn't like when customers can just copy the software and sell it themselves (so GPL would kill that business models), however many non-technical consumers would not know that they could do that, or have the business acumen to pull it off. We often say execution is important for a business, so does the GPL matter much for that?
- Coding_Cat 11y agoAnd, IANAL, but I remember reading the the GPL doesn't cover SAAS either because you're not distributing a program.
- empyrical 11y agoI could be wrong, but I think if you communicate with the GPL application using the command line under the hood, the application doesn't fall under the GPL either; which I think is how the closed source applications that provide a Git frontend work
- jholman 11y agoI hate it when people repeat gossip without actually knowing what they're talking about, but here I go doing that very thing! My ignorant understanding of this issue is that it has not been tested in court, and there are differing opinions about whether or not the strategy you describe is open to legal action. In the GPL v2.0, there's some language in section 2 that suggests that if you ship your closed-source app with the open-source app, then you're licensing both under the GPL. GPL2 isn't super clear on the issue. In GPL 3.0, there's a lot of language in section 1 about "Corresponding Source" which I believe was believed by the authors to specifically close the loophole you describe. So, if I were trying to obey the letter of the law religiously, I wouldn't do what you describe. And if I was trying to obey the _spirit_ of the law, I'd do what a previous employer of mine did: personally contact the authors of the GPL code in question and verbally ask for permission.
- Dylan16807 11y ago>Licenses like the MIT and BSD license exist for a different reason. And that reason is to give people who want to share what they did on generous terms a way to do so. And historically this was done in the belief that enlightened users would see it as being in their interest to contribute back. And this works on an individual level, but once corporate bureaucracy gets involved it tends to turn into "why would we give away proprietary code?". GPL has its flaws, but it helps to fight short-sightedness.
- callahad 11y ago> It is their code with their choice of license chosen for their reasons. Respect that. If I may offer one addition to this: if you intend for your software to be open source, please use a recognized open source license, rather than rolling your own. Doing so makes it much easier for outside parties to understand how you would like them to interact with your software. The Open Source Initiative has a good index of licenses: http://opensource.org/licenses/ http://opensource.org/licenses/
- Deejahll 11y ago> Would it outrage you for someone else to take your code ... and make millions while you make nothing? ... You shouldn't use the GPL if your response would be, "Bully for them, I had fun and they made the world better." This is wrong. Copyleft licenses are concerned with freedom, not price. I don't care if somebody gets rich off my software while I don't. I don't want somebody to take the work I have done and turn it into proprietary software that other users may no longer have the freedom to inspect, modify, and share. THAT is why all my work is GPL or AGPL. It has nothing to do with whether you make money or those users spend money or I get a cut of some money. Now that we have so many SaaS startups, "turn it into proprietary software" includes "use it to build a service and never distribute the sources." GPL and AGPL protects my code from this happening, while licenses like MIT and BSD ("permissive" licenses) do not. Permissive licensing, in the context of SaaS, is functionally equivalent to proprietary licensing. Somebody benefits (not necessarily monetarily) from the use of my software without paying its price: improvements must be shared.
- TazeTSchnitzel 11y ago> This is wrong. Copyleft licenses are concerned with freedom, not price. Precisely. The thought that someone might take the code I wrote and make it into a proprietary product, removing the freedoms I had, is horrible. But if someone made an free software product based on it and made millions, all the better for them!
- reitanqild 11y ago> The thought that someone might take the code I wrote and make it into a proprietary product, removing the freedoms I had, is horrible. I feel this argument is weak: even if I license my works under BSD, no one can make my BSD licensed code that has already been distributed into to a proprietary product, even not myself. To make that software that I licensed under BSD a proprietary product they would need to somehow convince all users of my software to get rid of all copies as well as convincing me to stop distributing it under a free licence. Building a proprietary product that includes my code does NOT remove anyones freedom to use my code, no?
- alecco 11y agoAnd even the GPL was too short sighted. The "ASP/PHP" loophole exploited by Google and others had a dismal impact in the free software community. They used the code, extended but never shared it. Some sociopathic corporations made BILLIONS on top of it buy contributed back almost nothing. Yes, the glorious Google being the prime example, but there are many others. And let's not forget the patent trick Oracle pulled on Apache and Google. I used to be a BSD fan, but from my own experience and some close firends's experience I learned the lesson. I would only release via Affero-GPL from now on. I hope the FSF will eventually bring out a revised version with a more aggressive stance against software patents (e.g. not valid to use if you ever sued anybody with a software patent or something like that).
- deleted 11y ago[deleted]
- reitanqild 11y ago> I would only release via Affero-GPL from now on. Fine with me. Do as you please. Everyone else keep in mind that your potential userbase drops dramatically if you only offer your software under AGPL. Even adding a commercial option in addition makes AGPL more usable.
- giancarlostoro 11y agoI always avoid AGPL altogether. The idea that if I change 1 line of code I now have to setup a public repository is just crazy to me. Unless my reading of the AGPL is entirely wrong?
- SXX 11y ago> The idea that if I change 1 line of code I now have to setup a public repository is just crazy to me. Like with GPL you only have to provide source code on demand. Also you can always link original project and provide patch applied.
- wstrange 11y agoTo be fair, Google has contributed a ton of code back to the community. They have also made Linux relevant on the "desktop" (if you consider Android / Chromebooks desktop substitutes). Net net, I would say their use of open source has been a benefit to the community.
- dredmorbius 11y agoYou're missing a _technical_ reason for using a BSD/MIT license, and one that's been relied on to great effect: to promote use of a standard. Apache was licensed under the BSD license in part due to philosophical preferences of its creators, but with the effect of promoting HTTP as a standard transport for online documents. Nobody had to ask for permission to use Apache, or to incorporate it into their own products (as IBM did). Arguably the orginal use of the BSD license, to spread use of Berkeley Unix, achieved similar aims. From the ideological standpoint: * If your goal is to promote Free Software, use the GPL (or a variant with stronger ties to distribution for Web or online services). * If your goal is to promote use of Free Software Libraries, in an environment where there are numerous non-free alternatives, the LGPL has benefits. * If your goal is to promote use of an open standard, the BSD/MIT licenses are more effective because they allow for proprietary use.
- overgard 11y ago> Licenses like the MIT and BSD license exist for a different reason. And that reason is to give people who want to share what they did on generous terms a way to do so. And historically this was done in the belief that enlightened users would see it as being in their interest to contribute back. I think the thing that people ignore is that there's a huge incentive to contribute back with licenses like MIT/BSD. The incentive is not having to maintain a set of patches and an in-house fork. Proprietary forks can be expensive (an engineer will have to apply those patches every release -- and engineers are expensive. Not to mention the good ones won't want this kind of work.) The notion of a company taking a BSD-licensed product and taking it to market while leaving the creator out in the cold seems rare. I won't say it never happens, but for most companies it makes economic sense to contribute back.
- Daishiman 11y agoOn the contrary, out of all the free OSes out there, it was Linux with GPL the most successful, because companies could contribute back knowing that their competitors would not take the code and run away and produce proprietary forks backed by large marketings budgets. See FreeBSD and Mac OS. If I contribute to Darwin, Apple will take my changes to improve their product. I get nothing in return. This may be fine for an individual, but for a company who depends on a product, it's a bad scenario.
- comex 11y agoIt makes economic sense... if you plan to ever update the software (especially more than a small handful of times). For most software, that's a pretty sane assumption, but there's a fairly important niche where it's not: embedded firmware, all the way from the GUI of some random thing-with-a-cheap-LCD to device drivers for flagship Android phones (which are more likely to be in the "small handful" category than "never", but still). In the latter case, even though Linux is under the GPL, at the rate the hardware changes there is often little incentive to contribute back to mainline. Or fulfill GPL obligations at all, for that matter - but at least most big Western manufacturers have some place to get a source dump. If Linux were BSD-licensed, things would be even worse.
- avinassh 11y ago> When you choose a license, you should choose correctly for what you want to have happen. Would it outrage you for someone else to take your code, put a pretty GUI on top, sell it, and make millions while you make nothing? Well then, you shouldn't use a BSD license. Which license you should use? I thought licenses does not discriminate wether you use it for personal use or commercial use. Sorry, newb here.
- riquito 11y ago> When you choose a license, you should choose correctly for what you want to have happen. Would it outrage you for someone else to take your code, put a pretty GUI on top, sell it, and make millions while you make nothing? Well then, you shouldn't use a BSD license. By contrast you shouldn't use the GPL if your response would be, "Bully for them, I had fun and they made the world better." BSD or GPL equally won't get you a dime, this example is flawed. The difference is that with GPL they must redistribute whatever modification they did (unless they are providing a "service", then you had to protect the code with AGPL).