docs/choosealicense.com
docs/choosealicense.com
1
0
Fork 0
mirror of https://github.com/github/choosealicense.com synced 2024-12-21 12:20:10 +01:00
Code Issues Releases Wiki Activity

Harmonize capitalization in section headings

Browse Source
This commit is contained in:
Waldir Pimenta 2020-10-13 17:47:00 +01:00
parent 20eaccfa54
commit c915a5a8da
3 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
CONTRIBUTING.md
View File

@ -1,4 +1,4 @@
# How to Contribute
# How to contribute
We love Pull Requests! Your contributions help make ChooseALicense.com great.
@ -6,7 +6,7 @@ Contributions to this project are [released](https://help.github.com/articles/gi
Please note that this project is released with a [Contributor Code of Conduct](CODE_OF_CONDUCT.md). By participating in this project you agree to abide by its terms.
## Getting Started
## Getting started
So you want to contribute to ChooseALicense. Great! We welcome any help we can
get. But first, please make sure you understand what
@ -34,7 +34,7 @@ If your proposed license meets the above criteria, here's a few other things to
* The text of the license should match the corresponding text found in [spdx/license-list-data](https://github.com/spdx/license-list-data/blob/master/text/). If there are errors there, please fix them in [spdx/license-list-XML](https://github.com/spdx/license-list-XML) (from which the plain text version is generated) so as to minimize license text variation and make it easier for choosealicense.com to eventually consume license texts directly from SPDX.
* The body of the file should be the text of the license in plain text.
## Making Changes
## Making changes
The easiest way to make a change is to simply edit a file from your browser.
When you click the edit button, it will fork the repository under your account.

2
README.md
View File

@ -12,7 +12,7 @@ We catalog [select](CONTRIBUTING.md#adding-a-license) open source licenses with
* Collaborate with and reinforce other licensing best practices and standards projects.
* Not comprehensive. Seems like an odd goal, but there are a bajillion licenses out there. We're going to have to filter that down to a small list of those that matter.
## Run It On Your Machine
## Run it on your machine
### Managing Dependencies

2
non-software.md
View File

@ -18,6 +18,6 @@ Any open source software license or open license for media (see [above](#data-me
The [SIL Open Font License 1.1](/licenses/ofl-1.1/) keeps fonts open but allows them to be freely used in other works.
### Mixed Projects
### Mixed projects
If your project contains a mix of software and other material, you can include multiple licenses, as long as you are explicit about which license applies to each part of the project. See [the license notice for this site](https://github.com/github/choosealicense.com#license) as an example.