3 ms·
I hadn't seen Zero-Clause BSD before: https://opensource.org/license/0bsd/ https://opensource.org/license/0bsd/ > Note: Despite its name, Zero-Clause BSD is an
by simonw 3y ago
I hadn't seen Zero-Clause BSD before: https://opensource.org/license/0bsd/ https://opensource.org/license/0bsd/
> Note: Despite its name, Zero-Clause BSD is an alteration of the ISC license, and is not textually derived from licenses in the BSD family. Zero-Clause BSD was originally approved under the name “Free Public License 1.0.0”.
Anyone seen a good write-up of the tradeoffs for this license? I like how short and simple it is.
- ameliaquining 3y agoIt's appropriate for software designed for use cases where an attribution requirement would be inconvenient or otherwise undesirable. For example, https://github.com/microsoft/tslib https://github.com/microsoft/tslib uses it, because that library is automatically included in any TypeScript program that uses downleveling, so if it had an attribution requirement then that requirement would apply to every program written in TypeScript, which nobody wants. (GCC and LLVM do something similar with their special runtime-library exceptions to the GPL and Apache License, respectively, but tslib lives in a separate repository from the rest of TypeScript and so could easily just get a separate license.)
- zvr 3y agoIt's a nice license when you don't want to burden users of your software with providing attribution. A typical use case is for stuff that will be included in many different projects, while not being a crucial part of it. For example, all the code snippets in the Intel Software Developer Manuals (https://www.intel.com/content/www/us/en/developer/articles/technical/intel-sdm.html https://www.intel.com/content/www/us/en/developer/articles/t...) are licensed under 0BSD, so that people can easily re-use them (with or without adapting them).
- etoulas 3y agoThis is handy but might not classify as a "write-up". https://www.tldrlegal.com/ https://www.tldrlegal.com/