4 ms·
Use a BSD style license for your Open Source Project (2021)
- znpy 4y ago> In 1969 the US Department of Justice charged IBM with destroying businesses by bundling free software with IBM hardware. As a result of this suit, IBM unbundled its software; that is, software became independent products separate from hardware. I wonder what 1969-era Justice would think of iphones
- usr1106 4y agoOr of Google. Or of Meta.
- zabzonk 4y agocompares with gpl, but not with mit. i would think that gpl and mit are the two licences you would mostly want to consider these days - i don't think i've ever used any bsd software, but i might be wrong.
- graphe 4y agoLots of websites use BSD. PS3+PS4, osx is more unix then Linux because it's BSD derived.
- bragr 4y agoBSD and MIT (and a handful of others) are basically all the same terms, with slightly different wording.
- zabzonk 4y agowell, the thing about legal documents such as licences is that the devil is in the wording. bsd and mit, to me, seem to have quite different terms.
- mustache_kimono 4y agoCan you explain?
- zabzonk 4y agofor example, some bsd licences have limitations on advertising, and other things. the mit licence is one para that basically says, maintain copyright notices and do what you want.
- loeg 4y ago> some bsd licences have limitations on advertising That's the "4-clause" BSD, which hasn't been very popular (since the 1980s? 90s?). > the mit licence is one para that basically says, maintain copyright notices and do what you want. The 2-clause BSD license is similar in length to the MITL (which is 3 paragraphs) and substantially similar in contents as well.
- nishs 4y agoThe common BSD-style licenses, 2-clause BSD and 3-clause BSD, are similar to the MIT license. The 2-clause BSD is effectively the same as the MIT license. The 3-clause BSD adds "don't use the names of the original software contributors to promote your derived work." (The Go programming language and Chromium use BSD-style licenses.)
- e12e 4y agoYou don't use ssh/opensshd?
- bch 4y ago> Unix author Ken Thompson returned to his alma mater, University of California Berkeley (UCB), in 1975 and taught the kernel line-by-line. Wow. TIL
- Falonix 4y ago[flagged]
- rwmj 4y agoIf you want companies to use your work and risk them not giving back. Otherwise use a copyleft license.
- nix23 4y agoCan you please give me the patched google internal kernel? It's GPL right?
- fsckboy 4y agoare you saying that a goal you support has not been achieved, or that it's a stupid goal?
- rakoo 4y agoYou're not using it, only services on top of it, so you're not entitled to it. On the other hand, there's a reason Google forbids even spelling the letters AGPL, because then they might have to give you the source code. Copyleft doing exactly what it's supposed to do.
- nix23 4y ago>You're not using it, only services on top of it, so you're not entitled to it. So when i sit in a car (service) i don't use the Street (below the service)? But you are right, and that's exactly why the GPL is NOT preventing Closed-source software per se.
- leonidasv 4y agoGPL talks only about "object code or executable form" as means of software distribution. When you ping a network server, it's not covered by the license. That's the whole point of AGPL: it covers network access as a mean of software distribution too.
- nix23 4y agoThat's what i wrote, and that's why i said the GPL is not preventing Closed-source systems...per se.
- nequo 4y agoThis is based largely on an essay from 18 to 20 years ago.[1] The claim that GPL benefits large companies that want to maintain monopolistic market power is not supported by several developments in the years up till today. Intel’s stealth computer that runs inside of yours called the Intel Management Engine is running Minix, a non-GPL OS. Apple’s macOS/iOS/iPadOS is non-GPL. Sun’s Solaris was open sourced under CDDL, not GPL. Microsoft’s VS Code is not under GPL either. [1] https://web.archive.org/web/20080201042548/http://alumni.cse.ucsc.edu/~brucem/open_source_license.htm https://web.archive.org/web/20080201042548/http://alumni.cse...
- msla 4y ago> The claim that GPL benefits large companies that want to maintain monopolistic market power is not supported by several developments in the years up till today. It's also blatantly the exact opposite of what companies have always done, back to the early days of BSD Unix, which is use software licensed under simple, permissive terms to base proprietary codebases off of. Them making that claim must be in bad faith, given how absolutely contrary it is to reality how it directly attacks a reason people don't use those kinds of licenses. I could bring up how proprietary software companies go out of their way to insult the GPL by calling it "viral" but the breathtaking dishonesty of that argument alone makes my case for me.
- mustache_kimono 4y ago> I could bring up how proprietary software companies go out of their way to insult the GPL by calling it "viral" but the breathtaking dishonesty of that argument alone makes my case for me. I'm willing to say it -- the reason this narrative has so much purchase is that the FSF wants the GPL to be "viral" via its "interpretations" of its own license. If you don't want people to think you're part of the loony fringes, stop hanging out at the loony fringes. As to whether the GPL actually is legally "viral", I have my doubts. I think the reason you actually don't see the FSF, SFLC, SFC in court is they think they've already lost at the fringes. The last several years of copyright law has been very, very hostile to any of the legal arguments they might make, say, re: dynamically linking modules. Credibility-wise they'd be wiped out. So, they keep soldiering on, pretending to man the battlements day after day.
- c0l0 4y ago... if you want to foster and ensure the existence of proprietary software. Fair enough, I guess - but not something I would personally feel compelled to do. Also note that the document never takes into account the needs of the eventual user of the appropriately licensed software, but only ever its (or other) developer(s).
- nix23 4y ago[flagged]
- daveguy 4y agoWhy would the eventual user care whether or not something is GPL or BSD? They're both free as in cookies and make no allowance or restriction on simple use of the software. The distinction is 100% about what a future developer can do or not do.
- enriquto 4y ago> Why would the eventual user care whether or not something is GPL or BSD? As a user, I definitely prefer to use a copylefted program. This means that I am guaranteed to enjoy the four software freedoms; in particular, I can look at how the program works and I can change its behavior, or hire a programmer to change it. A non-copylefted program, however, may be distributed by some middleman that deprives me of this freedom. Even if the original developer of the program shared it under a free-software licence, it can be re-packaged as a non-free wrapper. This is impossible with copyleft licenses. Thus, even if copyleft "imposes" some mild restrictions to developers, it is certainly very liberating to users! Notice that the only "restriction" imposed to developers is that they cannot re-package a copylefted program so that it becomes un-free.
- daveguy 4y ago>As a user, I definitely prefer to use a copylefted program. Okay. Good for you. As a user who likes to combine software ideas, I don't want my work or inspiration to be tainted by a work that would try to restrict my work in the future. You are free to enjoy what your freedoms and I am free to enjoy mine.
- knorker 4y agoSeems to me that every argument is missing a crucial link. Not saying it's wrong, but it's fantastically poorly written. E.g. why can users of GPL stuff not just fork, just like BSD? Why can't someone take abandoned GPL and run with it? "projects using licenses like the GPL… live under constant threat of having someone take over the project by producing a better version of the code and doing it faster than the original owners." And BSD doesn't? Cough, open, net, FreeBSD.
- nishs 4y ago> E.g. why can users of GPL stuff not just fork, just like BSD? A GPL-licensed project can be forked. But, if you release work that uses or is derived from the GPL-licensed project, among other things: 1. you must include or make easily available the source code for your derived work. 2. roughly speaking, the license of your derived work cannot be less free than the GPL license (i.e. cannot infringe on rights granted by the original GPL license). Releasing work derived from a BSD-licensed project does not have these requirements. References: https://en.wikipedia.org/wiki/GNU_General_Public_License#Terms_and_conditions https://en.wikipedia.org/wiki/GNU_General_Public_License#Ter... (edit: and on second glance, sorry, it seems like these details aren't really that relevant to the point of your questions.)
- nishs 4y agoOn: "projects using licenses like the GPL… live under constant threat of having someone take over the project by producing a better version of the code and doing it faster than the original owners." Yeah, I don't understand what the article is trying to say. Honestly the above seems like a good thing.
- kitsunesoba 4y agoIn other words, it's not that abandoned GPL can't be forked, it's that it's significantly less likely to be forked because the number of parties that could potentially fork it is significantly smaller. Particularly for more niche projects, it depends not only on a party with the same use case and licensing needs as the original author stumbling across it, but also having the skill and will to take it over and judging that it's better to do that than to start from scratch. There's so many funnels there I wouldn't be surprised if for many projects only a single-digit number of people match that description.
- WalterBright 4y agoThe D Language Foundation uses the Boost license: https://www.boost.org/users/license.html https://www.boost.org/users/license.html because it does not require the binaries to reproduce the license.
- nine_k 4y agoI'd formulate it like so. * Use BSD/MIT for a utility. You want the utility to be universally available, and included into larger systems to make them more useful and compatible to each other. A compression library, a file format, a single-purpose program like sshd would benefit from a permissive license. * Use GPL for a platform. If your stuff allows to build things based on it, if it is intended to serve as a backbone and a foundation, protect if from being grabbed by proprietary hands. Instead, make it safe for participants large and small (but especially large) to contribute to it openly without fear that somebody else would grab their contribution and turn it into a proprietary fork. Something like an OS kernel, or a desktop environment, or an application / database / etc server, or a compiler, may benefit from being released under GPL. I don't have a strong opinion about programming languages: as long as the toolchain is open-source under whatever license, it usually thrives on its own merits, not due to licenses prodding its use one way or another. The language specification of course needs to be open for re-implementation, and the standard library should be licensed so that it could be included in closed-source projects. Dual licensing (copyleft + paid commercial) is also a reasonable option.
- kitsunesoba 4y agoWhere would you say a UI framework (e.g. AppKit, Qt, etc) falls under this? Seems to straddling between utility and platform, and while I can see the benefit in keeping proprietary forks at bay one would probably want to enable the widest possible usage.
- rakoo 4y ago[...] if you want proprietary software, not just non-copyleft, to prosper. The reason Google, Facebook, Netflix, Twitter, even Amazon could gobble up so much of our data and communications and lives is thanks to licenses that didn't make it mandatory for those companies to share their source code. Non-copyleft is free work that can be turned into a commercial product. "Freedom of the developer" doesn't exist in the vacuum. Your freedom to do what you want has impacts on the way other people will use the computer. If your freedom is more important than the collective well-being of sharing resources, products and knowledge, you are not a good person.
- tmtvl 4y agoThis article at no point talks about protection of the end user's freedoms, it's like an article defending factory farming which doesn't mention animal welfare or overuse of antibiotics and hormonal supplements.
- torstenvl 4y agoIt should be noted that not even OpenBSD advocates for the BSD license anymore. They recommend a variant of the ISC license. https://www.openbsd.org/policy.html https://www.openbsd.org/policy.html
- nishs 4y agoAlso worth noting that the page says: > The above observations regarding moral rights imply that putting code under an ISC or two-clause BSD license essentially makes the code as free as it can possibly get. Emphasis on: or two-clause BSD license. That said, the ultimate recommendation on the page is ISC, but only because: > The ISC copyright is functionally equivalent to a two-term BSD copyright with language removed that is made unnecessary by the Berne convention.
- nishs 4y agoDoes anyone know which parts in the 2-clause BSD license were made unnecessary by the Berne convention?
- torstenvl 4y agoThere's some discussion here: https://marc.info/?l=openbsd-misc&m=120618313520730&w=2 https://marc.info/?l=openbsd-misc&m=120618313520730&w=2
- nishs 4y agoA negative for the ISC license: there has been controversy about "and/or" vs. "and" wording in the ISC license text. [1] The OpenBSD project uses the "and" wording, whereas the license text on the OSI website uses the "and/or" wording. Given all this, it seems to me that recommending the 2-clause BSD is the most straightforward option, because its only (and innocuous) issue is that it contains some no-longer-necessary language after the Berne convention agreements. [1] From Wikipedia: When initially released, the license did not include the term "and/or", which was changed from "and" by ISC in 2007. Paul Vixie stated on the BIND mailing list that the ISC license started using the term "and/or" to avoid controversy similar to the events surrounding the University of Washington's refusal to allow distribution of the Pine email software.
- Luker88 4y agoI am highly in favor of {,A,L}GPL licenses, but my new library will be Apache2. I would not release on MIT or BSD. Apache2 is not that different, but at least has a patent clause. With MIT/BSD you are in "let's just hope" territory. Letting others change your license is saying you don't care about your work, but that's just my feeling. Each project has its own target, and should chose the licenses accordingly, but I don't see reason for bsd/mit over apache. My rule of the thumb is: * apache for software that needs to be linked to proprietary * LGPL for other library * AGPL/GPL depending on your stance on network connectivity, and if you don't care about scaring companies that don't read licenses. (funny how EULA are ok for those companies though) I would also like to see git hosting software (github, gitlab, gitea...) provide a checkbox to only accept contributions from people who agree on a CLA, and developers would only need a checkbox to agree to it. Otherwise you are going to be stuck with GPL2 like linux, and you can't fix things that might make sense in your environment, both as being more restrictive, and being less restrictive. People can always fork if you do bad things anyway.