1
0
mirror of https://github.com/github/choosealicense.com synced 2024-12-22 12:50:24 +01:00
choosealicense.com/CONTRIBUTING.md

45 lines
2.5 KiB
Markdown
Raw Normal View History

2013-01-22 16:31:07 -08:00
# How to Contribute
We love Pull Requests! Your contributions help make ChooseALicense.com great.
## Getting Started
2013-10-30 19:10:25 +02:00
So you want to contribute to ChooseALicense. Great! We welcome any help we can
get. But first, please make sure you understand what
[this site is all about](http://choosealicense.com/about). Its not a comprehensive list of all possible licenses.
2013-01-22 16:31:07 -08:00
## Adding new licenses
2013-01-22 16:31:07 -08:00
2016-01-05 12:22:07 -08:00
Choosealicense.com is intended to demystify license choices, not present all of them. As such, there are several requirements for a license to be listed on the site:
2013-01-22 16:31:07 -08:00
2016-01-05 12:22:07 -08:00
1. The license must have [an SPDX identifier](https://spdx.org/licenses/). If your license isn't registered with SPDX, please [request that it be added](https://spdx.org/spdx-license-list/request-new-license-or-exception).
2. The license must be listed on one of the following approved lists of licenses:
* [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 thre three "free" categories*)
* [Open Definition's list of conformant licenses](http://opendefinition.org/licenses/) (non-code)
3. A [GitHub code search](https://github.com/search?q=MIT+filename%3ALICENSE&type=Code) must reveal at least *1,000* public repositories using the license
If your proposed license meets the above criteria, please follow [these instructions for adding a new license](https://github.com/github/choosealicense.com#adding-a-license). Almost without exception, new licenses should be added as hidden (`hidden: true` in the YAML front matter), such that they are directly linkable and detectable, but not otherwise listed.
2013-01-22 16:31:07 -08:00
## Making Changes
2013-10-30 19:10:25 +02:00
The easiest way to make a change is to simply edit a file from your browser.
2013-01-22 16:31:07 -08:00
When you click the edit button, it will fork the repository under your account.
Note what issue/issues your patch fixes in the commit message.
For example, to [change this file](/CONTRIBUTING.md),
2013-10-30 19:10:25 +02:00
find it in the GitHub repository. Then click the `Edit` button. Make your
2013-01-22 16:31:07 -08:00
changes, type in a commit message, and click the `Propose File Change` button.
Thats it!
For more advanced changes, check out [the bootstrap instructions](https://github.com/github/choosealicense.com#run-it-on-your-machine) in the [project's readme](/README.md).
2013-10-23 00:07:51 -07:00
## Testing
[HTML::Proofer](https://github.com/gjtorikian/html-proofer) is set up to validate all links within the project. You can run this locally to ensure that your changes are valid:
```shell
./script/bootstrap
./script/cibuild
2013-10-23 00:07:51 -07:00
```