docs/choosealicense.com
docs/choosealicense.com
1
0
Fork 0
mirror of https://github.com/github/choosealicense.com synced 2024-12-22 04:40:09 +01:00
Code Issues Releases Wiki Activity

Fix Code Search link in CONTRIBUTING

Browse Source 
2.8M instead of 4 files under MIT license is more like it? ;-)
This commit is contained in:
Michael Vorburger ⛑️ 2023-10-31 00:49:50 +01:00 committed by GitHub
parent 080f59b058
commit a240a1f4e6
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
CONTRIBUTING.md
View File

@ -21,7 +21,7 @@ Choosealicense.com is intended to demystify license choices, not present or cata
* [List of OSI approved licenses](https://opensource.org/licenses/alphabetical) * [List of OSI approved licenses](https://opensource.org/licenses/alphabetical)
* [GNU's list of free licenses](https://www.gnu.org/licenses/license-list.en.html) (*note: the license must be listed in one of the three "free" categories*) * [GNU's list of free licenses](https://www.gnu.org/licenses/license-list.en.html) (*note: the license must be listed in one of the three "free" categories*)
* [Open Definition's list of conformant licenses](https://opendefinition.org/licenses/) (non-code) * [Open Definition's list of conformant licenses](https://opendefinition.org/licenses/) (non-code)
3. The license must be used in at least *1,000* public repositories. This may be documented, for example, with a [GitHub code search](https://github.com/search?q=MIT+filename%3ALICENSE&type=Code). 3. The license must be used in at least *1,000* public repositories. This may be documented, for example, with a [GitHub code search](https://github.com/search?q=MIT+path%3ALICENSE&type=Code).
4. 3 notable projects using the license must be identified. These must have straightforward LICENSE files which serve as examples newcomers can follow and that could be detected by [licensee](https://github.com/licensee/licensee) if it knew about the license. 4. 3 notable projects using the license must be identified. These must have straightforward LICENSE files which serve as examples newcomers can follow and that could be detected by [licensee](https://github.com/licensee/licensee) if it knew about the license.
If your proposed license meets the above criteria, here's a few other things to keep in mind as you propose the license's addition: If your proposed license meets the above criteria, here's a few other things to keep in mind as you propose the license's addition: