h759bkyo4/Documentation
1
0
Fork 0
Code Issues Pull requests Actions Packages Projects Releases Wiki Activity

Changes Unlicense to 0BSD and removes some PD wording

Browse source
This commit is contained in:
Michiel Appelman 2021-10-14 15:42:48 +02:00
parent 608da3f36d
commit 81fda8059c
1 changed files with 9 additions and 9 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

18
content/getting-started/licensing.md
View file

@ -8,12 +8,12 @@ eleventyNavigation:
Codeberg's mission is to support the development and creation of Free Software, thus we only allow those repos licensed under an OSI/FSF-approved license.
Software is considered [free software](https://www.gnu.org/philosophy/free-sw.html) if it's users have the following four freedoms:
Software is considered [free software](https://www.gnu.org/philosophy/free-sw.html) if it's users have the following four freedoms (according to the [GNU free software philosophy](https://www.gnu.org/philosophy/free-sw.html#four-freedoms):
* The freedom to run the program as you wish, for any purpose (freedom 0).
* The freedom to study how the program works, and change it so it does your computing as you wish (freedom 1). Access to the source code is a precondition for this.
* The freedom to redistribute copies so you can help others (freedom 2).
* The freedom to distribute copies of your modified versions to others (freedom 3). By doing this you can give the whole community a chance to benefit from your changes. Access to the source code is a precondition for this.
> * The freedom to run the program as you wish, for any purpose (freedom 0).
> * The freedom to study how the program works, and change it so it does your computing as you wish (freedom 1). Access to the source code is a precondition for this.
> * The freedom to redistribute copies so you can help others (freedom 2).
> * The freedom to distribute copies of your modified versions to others (freedom 3). By doing this you can give the whole community a chance to benefit from your changes. Access to the source code is a precondition for this.
This page highlights some of the major topics to think about when licensing your code and aims to make it easy to choose one quickly. However, do make sure to dedicate more time to this if you have very specific goals in mind or expect a significant impact of your code.
@ -25,7 +25,7 @@ One of the main principles that's important to understand is *copyleft*. Very si
An example of one of the strongest copyleft licenses is the [GNU Affero General Public License](https://www.gnu.org/licenses/why-affero-gpl.html). It adds a requirement that even when a modified program is run on a server and lets other users communicate with it, your server must also allow them to download the source code corresponding to the modified version.
The other end of the spectrum is dedicating the software to the public domain. *Not* specifying a license does not automatically mean that you've put it in the public domain. If that's what you want, specify for example [The Unlicense](https://unlicense.org/).
The other end of the spectrum is licensing your software under no restrictions at all. An example of this is the [0-Clause BSD license](https://spdx.org/licenses/0BSD.html). *Not* specifying a license for your code does not automatically mean you've made it available without restrictions; you are still its copyright holder and must explicitly make the code free by choosing a free license.
## Recommended Licenses
@ -34,11 +34,11 @@ The [list of OSI-approved licenses](https://opensource.org/licenses) highlights
* [GNU Affero General Public License](https://www.gnu.org/licenses/agpl-3.0.html)
* [GNU General Public License (GPL)](https://www.gnu.org/licenses/gpl-3.0.html)
* [MIT license](https://opensource.org/licenses/MIT)
* [The Unlicense](https://unlicense.org/)
* [0-Clause BSD license](https://spdx.org/licenses/0BSD.html)
For more licenses, more details and some considerations when using any of them, see the [GNU list of licenses](https://www.gnu.org/licenses/license-list.html).
Please do not use custom licenses, [they are usually a bad idea](https://en.wikipedia.org/wiki/License_proliferation) and might result in legal uncertainty (can I really really use this project or might a terribly-written-license put me as a user in danger?). However, we sometimes tolerate repositories that aren't perfectly licensed correctly and focus on spreading awareness on the topic of improper FLOSS licensing and it's issues.
Please do not use custom licenses, [they are usually a bad idea](https://en.wikipedia.org/wiki/License_proliferation) and might result in legal uncertainty. However, we sometimes tolerate repositories that aren't perfectly licensed correctly and focus on spreading awareness on the topic of improper FLOSS licensing and it's issues.
## Non-code Licensing
@ -48,4 +48,4 @@ For documentation, writing and other non-code assets a [Creative Commons (CC)](h
* [CC-BY](https://creativecommons.org/licenses/by/4.0/)
* [CC-BY-SA](https://creativecommons.org/licenses/by-sa/4.0/)
Do not use [CC licenses on code](https://creativecommons.org/faq/#can-i-apply-a-creative-commons-license-to-software).
Like CC themselves, Codeberg **recommends against** using a [CC license on code](https://creativecommons.org/faq/#can-i-apply-a-creative-commons-license-to-software).