-
-
Save kemitchell/68633f5aef7215f070b7dc685c3a155d to your computer and use it in GitHub Desktop.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Berneout Kit License CON-NOT-PAT-SVC | |
| Version 0.0.0-prerelease | |
| https://berneout.org/kit/0.0.0-prerelease/CON-NOT-PAT-SVC | |
| Each contributor uses this license to make their | |
| contributions to the software freely available to others | |
| at minimum risk to themself. | |
| **This software comes "as is". No contributor makes any | |
| warranty.** | |
| **You may not sue any contributor for any reason related | |
| to this license or their contributions to the software.** | |
| Each contributor gives everyone permission to do everything | |
| that would otherwise infringe copyright in the software. | |
| PAT: Each contributor gives everyone permission to | |
| do everything with the software that would otherwise | |
| infringe patents they have or acquire, on account of | |
| their contributions. | |
| NOT: You must ensure that everyone who receives a | |
| copy of the software from you also receives copies, | |
| or free-of-charge access to copies, of this license, | |
| any licensing notices, and any notices about how to get | |
| source code. | |
| CON: Unless you add written notice of different license | |
| terms to specific work, you must license work on the | |
| software that you send to any contributor as contributions | |
| under this license. | |
| SVC: This license does not obligate any contributor to fix | |
| software bugs, add features, provide support, or perform | |
| any other services. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
@jashkenas: It struck me that my comments on compatibility were pretty inside-baseball. A few notes there:
Software public license compatibility issues are almost exclusivity a problem of copyleft licenses. There are some permissive licenses with annoying procedural requirements that create the odd compat problem, but those licenses are so rare (often for just this reason) that we don't see them much.
Traditional copyleft licenses, which require licensing derivative works on the same terms, address compatibility issues with special relicensing or add-ons to make nice with particular versions of particular copyleft licenses, usually GPL-2.0 or GPL-3.0. For example:
The Berneout Kit repository has some early sketches of copyleft-style source disclosure and license-terms components, but copyleft is probably a Kit 2.0 feature, if at all. As a general rule, permissive/pushover/academic licenses are far easier to write, though they're still far from easy, full stop.