A site to provide non-judgmental guidance on choosing a license for your open source project
Ruby HTML CSS CoffeeScript Shell
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
_data http->https for misc links outside of license texts May 22, 2018
_includes http->https for misc links outside of license texts May 22, 2018
_layouts Removed license text header Apr 27, 2016
_licenses http->https for misc links outside of license texts May 22, 2018
assets vertical spacing Jun 6, 2016
script check-approval: Fix missing license_ids variable Jan 3, 2018
spec http->https for misc links outside of license texts May 22, 2018
.bowerrc move bower to assets/vendor so we can version the swf Feb 1, 2014
.gitattributes Clean up .gitignore and .gitattributes. Dec 9, 2013
.gitignore update script/server for jekyll 3 Feb 9, 2016
.rubocop.yml pages now using ruby 2.4.0 May 27, 2017
.travis.yml update ruby to current pages version Dec 29, 2017
CNAME revert 48261c1 Jul 25, 2013
CODE_OF_CONDUCT.md Add Code of Conduct Feb 20, 2016
CONTRIBUTING.md http->https for misc links outside of license texts May 22, 2018
Gemfile spec_helper: Extract FSF approval from wking.github.io/fsf-api Jan 3, 2018
LICENSE.md Update License year to 2018 Jan 3, 2018
README.md http->https for misc links outside of license texts May 22, 2018
Rakefile mindlessly satisfy rubocop 0.48 Mar 27, 2017
_config.yml Replace gems with plugins to follow up jekyll update Oct 19, 2017
about.md focus additional resources on choosing an open license, not lists of … Mar 14, 2017
appendix.md Add pipe character for sort filter to fix liquid syntax warning Oct 20, 2017
bower.json Replaced zeroclipboard with clipboard.js Oct 25, 2015
existing.md change no-license internal links Dec 30, 2017
favicon.ico initial work on new design Sep 12, 2012
index.html change no-license internal links Dec 30, 2017
licenses.html vertical spacing Jun 6, 2016
no-permission.md rename and redirect no-license to no-permission avodiing licensee fal… Dec 30, 2017
non-software.md http->https for misc links outside of license texts May 22, 2018
robots.txt Remove `layout: nil`. Dec 20, 2014
terms-of-service.md a few minor markdown formatting fixes Feb 13, 2016

README.md

Choosealicense.com

Build Status

Like a Choose Your Own Adventure site, but only much less interesting.

Intro

A lot of repositories on GitHub.com don't have a license. GitHub provides a license chooser, but if you don't know anything about licenses, how are you supposed to make an informed decision?

ChooseALicense.com is designed to help people make an informed decision about licenses by demystifying license choices through non-judgmental guidance.

Immediate Goals

  • Non-judgmental. Our goal is to help you find a license that meets your goals.
  • Well designed, but that goes without saying.
  • The homepage should have just enough to help 99% of folks make a decision.
  • For the 1%, the site will contain a list of licenses common to specific communities and situations.
  • 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

git clone https://github.com/github/choosealicense.com.git
cd choosealicense.com
script/bootstrap
script/server

Open http://localhost:4000 in your favorite browser.

Adding a license

For information on adding a license, see the CONTRIBUTING file.

License metadata

Licenses sit in the /_licenses folder. Each license has YAML front matter describing the license's properties. The body of the file contains the text of the license in plain text. The available metadata fields are:

Required fields

  • title - The license full name specified by https://spdx.org/licenses/
  • spdx-id - Short identifier specified by https://spdx.org/licenses/
  • source - The URL to the license source text
  • description - A human-readable description of the license
  • how - Instructions on how to implement the license
  • using - A list of 3 notable projects using the license with straightforward LICENSE files which serve as examples newcomers can follow and that can be detected by licensee in the form of project_name: license_file_url
  • permissions - Bulleted list of permission rules
  • conditions - Bulleted list of condition rules
  • limitations - Bulleted list of limitation rules

Optional fields

  • featured - Whether the license should be featured on the main page (defaults to false)
  • hidden - Whether the license is neither popular nor fills out the spectrum of licenses from strongly conditional to unconditional (defaults to true)
  • nickname - Customary short name if applicable (e.g, GPLv3)
  • note - Additional information about the licenses
  • redirect_from - Relative path(s) to redirect to the license from, to prevent breaking old URLs

Auto-populated fields

The licenses on choosealicense.com are regularly imported to GitHub.com to be used as the list of licenses available when creating a repository. When we create a repository, we will replace certain strings in the license with variables from the repository. These can be used to create accurate copyright notices. The available variables are:

Fields

  • fullname - The full name or username of the repository owner
  • login - The repository owner's username
  • email - The repository owner's primary email address
  • project - The repository name
  • description - The description of the repository
  • year - The current year
  • projecturl - The repository URL or other project website

License properties

The license properties (rules) are stored as a bulleted list within the licenses YAML front matter. Each rule has a name e.g., include-copyright, a human-readable label, e.g., Copyright inclusion, and a description Include the original copyright with the code. To add a new rule, simply add it to _data/rules.yml and reference it in the appropriate license.

Rules

Permissions

  • commercial-use - This software and derivatives may be used for commercial purposes.
  • modifications - This software may be modified.
  • distribution - This software may be distributed.
  • private-use - This software may be used and modified in private.
  • patent-use - This license provides an express grant of patent rights from contributors.

Conditions

  • include-copyright - A copy of the license and copyright notice must be included with the software.
  • document-changes - Changes made to the code must be documented.
  • disclose-source - Source code must be made available when the software is distributed.
  • network-use-disclose - Users who interact with the software via network are given the right to receive a copy of the source code.
  • same-license - Modifications must be released under the same license when distributing the software. In some cases a similar or related license may be used.
  • same-license--file - Modifications of existing files must be released under the same license when distributing the software. In some cases a similar or related license may be used.
  • same-license--library - Modifications must be released under the same license when distributing the software. In some cases a similar or related license may be used, or this condition may not apply to works that use the software as a library.

Limitations

  • trademark-use - This license explicitly states that it does NOT grant trademark rights, even though licenses without such a statement probably do not grant any implicit trademark rights.
  • liability - This license includes a limitation of liability.
  • patent-use - This license explicitly states that it does NOT grant any rights in the patents of contributors.
  • warranty - The license explicitly states that it does NOT provide any warranty.

License

The content of this project itself is licensed under the Creative Commons Attribution 3.0 license, and the underlying source code used to format and display that content is licensed under the MIT license.