docs/choosealicense.com
docs/choosealicense.com
1
0
Fork 0
mirror of https://github.com/github/choosealicense.com synced 2025-01-03 10:31:44 +01:00
Code Issues Releases Wiki Activity

Merge branch 'gh-pages' into home-reform

Browse Source
This commit is contained in:
Mike Linksvayer 2017-06-26 18:48:43 -07:00 committed by GitHub
commit ba5ed87706
55 changed files with 647 additions and 141 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
.rubocop.yml
View File

@ -1,9 +1,12 @@
AllCops:
TargetRubyVersion: 2.1
TargetRubyVersion: 2.4
Exclude:
- _site/**/*
- vendor/**/*
Metrics/BlockLength:
Enabled: false
Metrics/LineLength:
Enabled: false

2
.travis.yml
View File

@ -5,7 +5,7 @@ script: "./script/cibuild"
#environment
language: ruby
rvm:
- 2.0.0
- 2.4.0
branches:
only:

4
CONTRIBUTING.md
View File

@ -14,12 +14,13 @@ get. But first, please make sure you understand what
Choosealicense.com is intended to demystify license choices, not present or catalog all of them. As such, only a small number are highlighted on the home page or <http://choosealicense.com/licenses>, and there are several requirements for a license to be [cataloged](http://choosealicense.com/appendix/) on the site:
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).
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).
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 the 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
4. Identification of 3 notable projects using the license with straightforward LICENSE files which serve as examples newcomers can follow and that could be detected by [licensee](https://github.com/benbalter/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:
@ -28,6 +29,7 @@ If your proposed license meets the above criteria, here's a few other things to
* The license files should be in the format of `_licenses/[lowercased-spdx-id].txt` (e.g., `_licenses/mit.txt`)
* Each license has both [required and optional metadata](https://github.com/github/choosealicense.com#license-metadata) that should be included.
* The text of the license should be wrapped to a 78 character width.
* The text of the license should match the corresponding text found at https://spdx.org/licenses/
* The body of the file should be the text of the license in plain text.
## Making Changes

2
Gemfile
View File

@ -1,3 +1,5 @@
# frozen_string_literal: true
source 'https://rubygems.org'
require 'json'

2
LICENSE.md
View File

@ -1,4 +1,4 @@
Copyright (c) 2013-2016 GitHub, Inc. and contributors
Copyright (c) 2013-2017 GitHub, Inc. and contributors
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal

25
README.md
View File

@ -44,6 +44,7 @@ Licenses sit in the `/_licenses` folder. Each license has YAML front matter desc
* `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](https://github.com/benbalter/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
@ -54,7 +55,6 @@ Licenses sit in the `/_licenses` folder. Each license has YAML front matter desc
* `hidden` - Whether the license is neither [popular](https://opensource.org/licenses) nor fills out the [spectrum of licenses](http://choosealicense.com/licenses/) from strongly conditional to unconditional (defaults to true)
* `nickname` - Customary short name if applicable (e.g, GPLv3)
* `note` - Additional information about the licenses
* `using` - A list of up to 3 notable projects using the license with straightforward LICENSE files which serve as examples newcomers can follow and that can be detected by [licensee](https://github.com/benbalter/licensee) in the form of `project_name: license_file_url`
* `redirect_from` - Relative path(s) to redirect to the license from, to prevent breaking old URLs
### Auto-populated fields
@ -80,23 +80,26 @@ The license properties (rules) are stored as a bulleted list within the licenses
* `commercial-use` - This software and derivatives may be used for commercial purposes.
* `modifications` - This software may be modified.
* `distribution` - You may distribute this software.
* `private-use` - You may use and modify the software without distributing it.
* `patent-use` - This license provides an express grant of patent rights from the contributor to the recipient.
* `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` - Include a copy of the license and copyright notice with the code.
* `document-changes` - Indicate changes made to the code.
* `disclose-source` - Source code must be made available when distributing the software.
* `network-use-disclose` - Users who interact with the software via network are given the right to receive a copy of the corresponding source code.
* `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 you trademark rights, even though licenses without such a statement probably do not grant you any implicit trademark rights.
* `no-liability` - Software is provided without warranty and the software author/license owner cannot be held liable for damages.
* `patent-use` - This license explicitly states that it does NOT grant you any rights in the patents of contributors.
* `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

7
Rakefile
View File

@ -1,3 +1,5 @@
# frozen_string_literal: true
require 'html-proofer'
require 'rspec/core/rake_task'
@ -13,7 +15,8 @@ task :test do
HTMLProofer.check_directory('./_site',
check_html: true,
validation: { ignore_script_embeds: true },
url_swap: { %r{http://choosealicense.com} => '' }).run
url_swap: { %r{https://choosealicense.com} => '' },
check_img_http: true).run
end
task :approved_licenses do
@ -24,7 +27,7 @@ task :approved_licenses do
puts approved.join(', ')
puts "\n"
potential = approved - licenses.map { |l| l['id'] }
potential = approved - (licenses.map { |l| l['id'] })
puts "#{potential.count} potential additions:"
puts potential.join(', ')
end

2
_config.yml
View File

@ -3,7 +3,7 @@ title: Choose a License
description: Non-judgmental guidance on choosing a license for your open source project
relative_permalinks: false
markdown: kramdown
url: "http://choosealicense.com"
url: "https://choosealicense.com"
collections:
licenses:

8
_data/meta.yml
View File

@ -33,6 +33,10 @@
description: Bulleted list of limited rules
required: true
- name: using
description: '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](https://github.com/benbalter/licensee) in the form of `project_name: license_file_url`'
required: true
# Optional fields
- name: featured
@ -51,10 +55,6 @@
description: Additional information about the licenses
required: false
- name: using
description: 'A list of up to 3 notable projects using the license with straightforward LICENSE files which serve as examples newcomers can follow and that can be detected by [licensee](https://github.com/benbalter/licensee) in the form of `project_name: license_file_url`'
required: false
- name: redirect_from
description: Relative path(s) to redirect to the license from, to prevent breaking old URLs
required: false

53
_data/rules.yml
View File

@ -1,44 +1,53 @@
permissions:
- description: This software and derivatives may be used for commercial purposes.
label: Commercial Use
label: Commercial use
tag: commercial-use
- description: This software may be modified.
label: Modification
tag: modifications
- description: You may distribute this software.
- description: This software may be distributed.
label: Distribution
tag: distribution
- description: You may use and modify the software without distributing it.
label: Private Use
- description: This software may be used and modified in private.
label: Private use
tag: private-use
- description: This license provides an express grant of patent rights from the contributor to the recipient.
label: Patent Use
- description: This license provides an express grant of patent rights from contributors.
label: Patent use
tag: patent-use
conditions:
- description: Include a copy of the license and copyright notice with the code.
label: License and Copyright Notice
- description: A copy of the license and copyright notice must be included with the software.
label: License and copyright notice
tag: include-copyright
- description: Indicate changes made to the code.
label: State Changes
- description: Changes made to the code must be documented.
label: State changes
tag: document-changes
- description: Source code must be made available when distributing the software.
label: Disclose Source
- description: Source code must be made available when the software is distributed.
label: Disclose source
tag: disclose-source
- description: Users who interact with the software via network are given the right to receive a copy of the corresponding source code.
label: Network Use is Distribution
- description: Users who interact with the software via network are given the right to receive a copy of the source code.
label: Network use is distribution
tag: network-use-disclose
- description: Modifications must be released under the same license when distributing the software. In some cases a similar or related license may be used.
label: Same License
label: Same license
tag: same-license
- description: 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.
label: Same license (file)
tag: same-license--file
- description: 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.
label: Same license (library)
tag: same-license--library
limitations:
- description: This license explicitly states that it does NOT grant you trademark rights, even though licenses without such a statement probably do not grant you any implicit trademark rights.
label: Trademark Use
- description: 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.
label: Trademark use
tag: trademark-use
- description: Software is provided without warranty and the software author/license owner cannot be held liable for damages.
label: Hold Liable
tag: no-liability
- description: This license explicitly states that it does NOT grant you any rights in the patents of contributors.
label: Patent Use
- description: This license includes a limitation of liability.
label: Liability
tag: liability
- description: This license explicitly states that it does NOT grant any rights in the patents of contributors.
label: Patent use
tag: patent-use
- description: The license explicitly states that it does NOT provide any warranty.
label: Warranty
tag: warranty

5
_licenses/afl-3.0.txt
View File

@ -7,6 +7,8 @@ description: The Academic Free License is a variant of the Open Software License
how: Create a text file (typically named LICENSE or LICENSE.txt) in the root of your source code and copy the text of the license into the file. Files licensed under AFL 3.0 must also include the notice "Licensed under the Academic Free License version 3.0" adjacent to the copyright notice.
using:
permissions:
- commercial-use
- modifications
@ -20,7 +22,8 @@ conditions:
limitations:
- trademark-use
- no-liability
- liability
- warranty
---

5
_licenses/agpl-3.0.txt
View File

@ -12,6 +12,8 @@ how: Create a text file (typically named LICENSE or LICENSE.txt) in the root of
note: The Free Software Foundation recommends taking the additional step of adding a boilerplate notice to the top of each file. The boilerplate can be found at the end of the license.
using:
permissions:
- commercial-use
- modifications
@ -27,7 +29,8 @@ conditions:
- same-license
limitations:
- no-liability
- liability
- warranty
---

3
_licenses/apache-2.0.txt
View File

@ -29,7 +29,8 @@ conditions:
limitations:
- trademark-use
- no-liability
- liability
- warranty
---

7
_licenses/artistic-2.0.txt
View File

@ -8,6 +8,8 @@ description: Heavily favored by the Perl community, the Artistic license require
how: Create a text file (typically named LICENSE or LICENSE.txt) in the root of your source code, and copy the text of the license into the file. Do not replace the copyright notice (year, author), which refers to the license itself, not the licensed project.
using:
permissions:
- commercial-use
- modifications
@ -20,8 +22,9 @@ conditions:
- document-changes
limitations:
- no-liability
- liability
- trademark-use
- warranty
---
@ -135,7 +138,7 @@ you do at least ONE of the following:
(c) allow anyone who receives a copy of the Modified Version to
make the Source form of the Modified Version available to others
under
(i) the Original License or
(ii) a license that permits the licensee to freely copy,

5
_licenses/bsd-2-clause.txt
View File

@ -9,6 +9,8 @@ description: A permissive license that comes in two variants, the <a href="/lice
how: Create a text file (typically named LICENSE or LICENSE.txt) in the root of your source code and copy the text of the license into the file. Replace [year] with the current year and [fullname] with the name (or names) of the copyright holders.
using:
permissions:
- commercial-use
- modifications
@ -19,7 +21,8 @@ conditions:
- include-copyright
limitations:
- no-liability
- liability
- warranty
---

5
_licenses/bsd-3-clause-clear.txt
View File

@ -7,6 +7,8 @@ description: A variant of the <a href="/licenses/bsd-3-clause/">BSD 3-Clause Lic
how: Create a text file (typically named LICENSE or LICENSE.txt) in the root of your source code and copy the text of the license into the file. Replace [year] with the current year and [fullname] with the name (or names) of the copyright holders. Replace [project] with the project organization, if any, that sponsors this work.
using:
permissions:
- commercial-use
- modifications
@ -17,8 +19,9 @@ conditions:
- include-copyright
limitations:
- no-liability
- liability
- patent-use
- warranty
---

5
_licenses/bsd-3-clause.txt
View File

@ -8,6 +8,8 @@ description: A permissive license similar to the <a href="/licenses/bsd-2-clause
how: Create a text file (typically named LICENSE or LICENSE.txt) in the root of your source code and copy the text of the license into the file. Replace [year] with the current year and [fullname] with the name (or names) of the copyright holders. Replace [project] with the project organization, if any, that sponsors this work.
using:
permissions:
- commercial-use
- modifications
@ -18,7 +20,8 @@ conditions:
- include-copyright
limitations:
- no-liability
- liability
- warranty
---

5
_licenses/bsl-1.0.txt
View File

@ -9,6 +9,8 @@ how: Create a text file (typically named LICENSE or LICENSE.txt) in the root of
note: Boost recommends taking the additional step of adding a boilerplate notice to the top of each file. The boilerplate can be found at the [Boost Software License FAQ](http://www.boost.org/users/license.html#FAQ).
using:
permissions:
- commercial-use
- modifications
@ -19,7 +21,8 @@ conditions:
- include-copyright
limitations:
- no-liability
- liability
- warranty
---

9
_licenses/cc-by-4.0.txt
View File

@ -5,7 +5,9 @@ source: https://creativecommons.org/licenses/by/4.0/legalcode.txt
description: Permits almost any use subject to providing credit and license notice. Frequently used for media assets and educational materials. The most common license for Open Access scientific publications. Not recommended for software.
how: Create a text file (typically named LICENSE or LICENSE.txt) in the root of your source code and copy the text of the license into the file. It is also acceptable to soley supply a link to a copy of the license, usually to the <a href='https://creativecommons.org/licenses/by/4.0/'>canonical URL for the license</a>.
how: Create a text file (typically named LICENSE or LICENSE.txt) in the root of your source code and copy the text of the license into the file. It is also acceptable to solely supply a link to a copy of the license, usually to the <a href='https://creativecommons.org/licenses/by/4.0/'>canonical URL for the license</a>.
using:
permissions:
- commercial-use
@ -18,9 +20,10 @@ conditions:
- document-changes
limitations:
- no-liability
- liability
- trademark-use
- patent-use
- warranty
---
@ -75,7 +78,7 @@ exhaustive, and do not form part of our licenses.
such as asking that all changes be marked or described.
Although not required by our licenses, you are encouraged to
respect those requests where reasonable. More_considerations
for the public:
for the public:
wiki.creativecommons.org/Considerations_for_licensees
=======================================================================

9
_licenses/cc-by-sa-4.0.txt
View File

@ -5,7 +5,9 @@ source: https://creativecommons.org/licenses/by-sa/4.0/legalcode.txt
description: Similar to <a href='/licenses/cc-by-4.0/'>CC-BY-4.0</a> but requires derivatives be distributed under the same or a similar, <a href="https://creativecommons.org/compatiblelicenses/">compatible</a> license. Frequently used for media assets and educational materials. A previous version is the default license for Wikipedia and other Wikimedia projects. Not recommended for software.
how: Create a text file (typically named LICENSE or LICENSE.txt) in the root of your source code and copy the text of the license into the file. It is also acceptable to soley supply a link to a copy of the license, usually to the <a href='https://creativecommons.org/licenses/by-sa/4.0/'>canonical URL for the license</a>.
how: Create a text file (typically named LICENSE or LICENSE.txt) in the root of your source code and copy the text of the license into the file. It is also acceptable to solely supply a link to a copy of the license, usually to the <a href='https://creativecommons.org/licenses/by-sa/4.0/'>canonical URL for the license</a>.
using:
permissions:
- commercial-use
@ -19,9 +21,10 @@ conditions:
- same-license
limitations:
- no-liability
- liability
- trademark-use
- patent-use
- warranty
---
@ -76,7 +79,7 @@ exhaustive, and do not form part of our licenses.
such as asking that all changes be marked or described.
Although not required by our licenses, you are encouraged to
respect those requests where reasonable. More_considerations
for the public:
for the public:
wiki.creativecommons.org/Considerations_for_licensees
=======================================================================

5
_licenses/cc0-1.0.txt
View File

@ -10,6 +10,8 @@ how: Create a text file (typically named LICENSE or LICENSE.txt) in the root of
note: Creative Commons recommends taking the additional step of adding a boilerplate notice to the top of each file. The boilerplate can be <a href="https://wiki.creativecommons.org/wiki/CC0_FAQ#May_I_apply_CC0_to_computer_software.3F_If_so.2C_is_there_a_recommended_implementation.3F">found on their website</a>.
using:
permissions:
- commercial-use
- modifications
@ -19,9 +21,10 @@ permissions:
conditions: []
limitations:
- no-liability
- liability
- trademark-use
- patent-use
- warranty
---

236
_licenses/ecl-2.0.txt Normal file
View File

@ -0,0 +1,236 @@
---
title: Educational Community License v2.0
spdx-id: ECL-2.0
source: https://opensource.org/licenses/ECL-2.0
description: The Educational Community License version 2.0 ("ECL") consists of the Apache 2.0 license, modified to change the scope of the patent grant in section 3 to be specific to the needs of the education communities using this license.
how: Create a text file (typically named LICENSE or LICENSE.txt) in the root of your source code and copy the text of the license into the file.
note: The Apereo Foundation recommends taking the additional step of adding a boilerplate notice to the header of each source file. You can find the notice at the very end of the license in the appendix.
using:
- Sakai: https://github.com/sakaiproject/sakai/blob/master/LICENSE
- OAE: https://github.com/oaeproject/Hilary/blob/master/LICENSE
- Opencast Matterhorn: https://bitbucket.org/opencast-community/matterhorn/src/e5b1684a822c0bd9bb07f3e53b4e1f22932da5ef/LICENSE?fileviewer=file-view-default
permissions:
- commercial-use
- modifications
- distribution
- patent-use
- private-use
conditions:
- include-copyright
- document-changes
limitations:
- trademark-use
- liability
- warranty
---
Educational Community License
Version 2.0, April 2007
http://opensource.org/licenses/ECL-2.0
The Educational Community License version 2.0 ("ECL") consists of the Apache
2.0 license, modified to change the scope of the patent grant in section 3 to
be specific to the needs of the education communities using this license. The
original Apache 2.0 license can be found at:
http://www.apache.org/licenses/LICENSE-2.0
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction, and
distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by the
copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all other
entities that control, are controlled by, or are under common control with
that entity. For the purposes of this definition, "control" means (i) the
power, direct or indirect, to cause the direction or management of such
entity, whether by contract or otherwise, or (ii) ownership of fifty percent
(50%) or more of the outstanding shares, or (iii) beneficial ownership of such
entity.
"You" (or "Your") shall mean an individual or Legal Entity exercising
permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation source, and
configuration files.
"Object" form shall mean any form resulting from mechanical transformation or
translation of a Source form, including but not limited to compiled object
code, generated documentation, and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or Object form,
made available under the License, as indicated by a copyright notice that is
included in or attached to the work (an example is provided in the Appendix
below).
"Derivative Works" shall mean any work, whether in Source or Object form, that
is based on (or derived from) the Work and for which the editorial revisions,
annotations, elaborations, or other modifications represent, as a whole, an
original work of authorship. For the purposes of this License, Derivative
Works shall not include works that remain separable from, or merely link (or
bind by name) to the interfaces of, the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including the original
version of the Work and any modifications or additions to that Work or
Derivative Works thereof, that is intentionally submitted to Licensor for
inclusion in the Work by the copyright owner or by an individual or Legal
Entity authorized to submit on behalf of the copyright owner. For the purposes
of this definition, "submitted" means any form of electronic, verbal, or
written communication sent to the Licensor or its representatives, including
but not limited to communication on electronic mailing lists, source code
control systems, and issue tracking systems that are managed by, or on behalf
of, the Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise designated
in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity on behalf
of whom a Contribution has been received by Licensor and subsequently
incorporated within the Work.
2. Grant of Copyright License.
Subject to the terms and conditions of this License, each Contributor hereby
grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free,
irrevocable copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the Work and
such Derivative Works in Source or Object form.
3. Grant of Patent License.
Subject to the terms and conditions of this License, each Contributor hereby
grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free,
irrevocable (except as stated in this section) patent license to make, have
made, use, offer to sell, sell, import, and otherwise transfer the Work, where
such license applies only to those patent claims licensable by such
Contributor that are necessarily infringed by their Contribution(s) alone or
by combination of their Contribution(s) with the Work to which such
Contribution(s) was submitted. If You institute patent litigation against any
entity (including a cross-claim or counterclaim in a lawsuit) alleging that
the Work or a Contribution incorporated within the Work constitutes direct or
contributory patent infringement, then any patent licenses granted to You
under this License for that Work shall terminate as of the date such
litigation is filed. Any patent license granted hereby with respect to
contributions by an individual employed by an institution or organization is
limited to patent claims where the individual that is the author of the Work
is also the inventor of the patent claims licensed, and where the organization
or institution has the right to grant such license under applicable grant and
research funding agreements. No other express or implied licenses are granted.
4. Redistribution.
You may reproduce and distribute copies of the Work or Derivative Works
thereof in any medium, with or without modifications, and in Source or Object
form, provided that You meet the following conditions:
You must give any other recipients of the Work or Derivative Works a copy of
this License; and You must cause any modified files to carry prominent notices
stating that You changed the files; and You must retain, in the Source form of
any Derivative Works that You distribute, all copyright, patent, trademark,
and attribution notices from the Source form of the Work, excluding those
notices that do not pertain to any part of the Derivative Works; and If the
Work includes a "NOTICE" text file as part of its distribution, then any
Derivative Works that You distribute must include a readable copy of the
attribution notices contained within such NOTICE file, excluding those notices
that do not pertain to any part of the Derivative Works, in at least one of
the following places: within a NOTICE text file distributed as part of the
Derivative Works; within the Source form or documentation, if provided along
with the Derivative Works; or, within a display generated by the Derivative
Works, if and wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and do not modify the
License. You may add Your own attribution notices within Derivative Works that
You distribute, alongside or as an addendum to the NOTICE text from the Work,
provided that such additional attribution notices cannot be construed as
modifying the License. You may add Your own copyright statement to Your
modifications and may provide additional or different license terms and
conditions for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use, reproduction, and
distribution of the Work otherwise complies with the conditions stated in this
License.
5. Submission of Contributions.
Unless You explicitly state otherwise, any Contribution intentionally
submitted for inclusion in the Work by You to the Licensor shall be under the
terms and conditions of this License, without any additional terms or
conditions. Notwithstanding the above, nothing herein shall supersede or
modify the terms of any separate license agreement you may have executed with
Licensor regarding such Contributions.
6. Trademarks.
This License does not grant permission to use the trade names, trademarks,
service marks, or product names of the Licensor, except as required for
reasonable and customary use in describing the origin of the Work and
reproducing the content of the NOTICE file.
7. Disclaimer of Warranty.
Unless required by applicable law or agreed to in writing, Licensor provides
the Work (and each Contributor provides its Contributions) on an "AS IS"
BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions of TITLE,
NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You
are solely responsible for determining the appropriateness of using or
redistributing the Work and assume any risks associated with Your exercise of
permissions under this License.
8. Limitation of Liability.
In no event and under no legal theory, whether in tort (including negligence),
contract, or otherwise, unless required by applicable law (such as deliberate
and grossly negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a result of
this License or out of the use or inability to use the Work (including but not
limited to damages for loss of goodwill, work stoppage, computer failure or
malfunction, or any and all other commercial damages or losses), even if such
Contributor has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability.
While redistributing the Work or Derivative Works thereof, You may choose to
offer, and charge a fee for, acceptance of support, warranty, indemnity, or
other liability obligations and/or rights consistent with this License.
However, in accepting such obligations, You may act only on Your own behalf
and on Your sole responsibility, not on behalf of any other Contributor, and
only if You agree to indemnify, defend, and hold each Contributor harmless for
any liability incurred by, or claims asserted against, such Contributor by
reason of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Educational Community License to your work
To apply the Educational Community License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "{}" replaced with
your own identifying information. (Don't include the brackets!) The text
should be enclosed in the appropriate comment syntax for the file format. We
also recommend that a file or class name and description of purpose be
included on the same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright {yyyy} {name of copyright owner} Licensed under the Educational
Community License, Version 2.0 (the "License"); you may not use this file
except in compliance with the License. You may obtain a copy of the License at
http://opensource.org/licenses/ECL-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
License for the specific language governing permissions and limitations under
the License.

3
_licenses/epl-1.0.txt
View File

@ -27,7 +27,8 @@ conditions:
- same-license
limitations:
- no-liability
- liability
- warranty
---

7
_licenses/eupl-1.1.txt
View File

@ -2,7 +2,7 @@
title: European Union Public License 1.1
spdx-id: EUPL-1.1
redirect_from: /licenses/eupl-v1.1/
source: https://joinup.ec.europa.eu/community/eupl/og_page/european-union-public-licence-eupl-v11
source: https://joinup.ec.europa.eu/community/eupl/og_page/eupl-text-11-12
description: The “European Union Public Licence” (EUPL) is a copyleft free/open source software license created on the initiative of and approved by the European Commission in 22 official languages of the European Union.
@ -10,6 +10,8 @@ how: Create a text file (typically named COPYING or LICENCE.txt) in the root of
note: The European Commission recommends taking the additional step of adding a [boilerplate notice](https://joinup.ec.europa.eu/sites/default/files/ckeditor_files/files/EUPL%201_1%20Guidelines%20EN%20Joinup.pdf#page=17) to the top of each file.
using:
permissions:
- commercial-use
- modifications
@ -25,8 +27,9 @@ conditions:
- same-license
limitations:
- no-liability
- liability
- trademark-use
- warranty
---

3
_licenses/gpl-2.0.txt
View File

@ -29,7 +29,8 @@ conditions:
- same-license
limitations:
- no-liability
- liability
- warranty
---

3
_licenses/gpl-3.0.txt
View File

@ -32,7 +32,8 @@ conditions:
- same-license
limitations:
- no-liability
- liability
- warranty
---

5
_licenses/isc.txt
View File

@ -10,7 +10,7 @@ how: Create a text file (typically named LICENSE or LICENSE.txt) in the root of
using:
- documentation.js: https://github.com/documentationjs/documentation/blob/master/LICENSE
- Node.js semver: https://github.com/npm/node-semver/blob/master/LICENSE
- OpenStreetMap iD: https://github.com/openstreetmap/iD/blob/master/LICENSE
- OpenStreetMap iD: https://github.com/openstreetmap/iD/blob/master/LICENSE.md
permissions:
- commercial-use
@ -22,7 +22,8 @@ conditions:
- include-copyright
limitations:
- no-liability
- liability
- warranty
---

7
_licenses/lgpl-2.1.txt
View File

@ -12,6 +12,8 @@ how: Create a text file (typically named LICENSE or LICENSE.txt) in the root of
note: The Free Software Foundation recommends taking the additional step of adding a boilerplate notice to the top of each file. The boilerplate can be found at the end of the license.
using:
permissions:
- commercial-use
- modifications
@ -22,10 +24,11 @@ conditions:
- include-copyright
- disclose-source
- document-changes
- same-license
- same-license--library
limitations:
- no-liability
- liability
- warranty
---

7
_licenses/lgpl-3.0.txt
View File

@ -12,6 +12,8 @@ how: This license is an additional set of permissions to the <a href="/licenses/
note: The Free Software Foundation recommends taking the additional step of adding a boilerplate notice to the top of each file. The boilerplate can be found at the end of the <a href="/licenses/gpl-3.0">GNU GPLv3 license</a>. Insert the word “Lesser” before “General” in all three places in the boilerplate notice to make sure that you refer to the GNU LGPLv3 and not the GNU GPLv3.
using:
permissions:
- commercial-use
- modifications
@ -23,10 +25,11 @@ conditions:
- include-copyright
- disclose-source
- document-changes
- same-license
- same-license--library
limitations:
- no-liability
- liability
- warranty
---

60
_licenses/lppl-1.3c.txt
View File

@ -3,12 +3,14 @@ title: LaTeX Project Public License v1.3c
spdx-id: LPPL-1.3c
source: https://latex-project.org/lppl/lppl-1-3c.html
description: The LaTeX Project Public License (LPPL) is the primary license under which the LaTeX kernel and the base LaTeX packages are distributed.
description: The LaTeX Project Public License (LPPL) is the primary license under which the LaTeX kernel and the base LaTeX packages are distributed.
how: To use this license, place in each of the components of your work both an explicit copyright notice including your name and the year the work was authored and/or last substantially modified. Include also a statement that the distribution and/or modification of that component is constrained by the conditions in this license.
note: An example boilerplate and more information about how to use the license can be found at the end of the license.
using:
permissions:
- commercial-use
- modifications
@ -17,11 +19,12 @@ permissions:
conditions:
- include-copyright
- document-changes
- document-changes
- disclose-source
limitations:
- no-liability
- liability
- warranty
---
@ -43,8 +46,8 @@ which the LaTeX kernel and the base LaTeX packages are distributed.
You may use this license for any work of which you hold the copyright
and which you wish to distribute. This license may be particularly
suitable if your work is TeX-related (such as a LaTeX package), but
it is written in such a way that you can use it even if your work is
suitable if your work is TeX-related (such as a LaTeX package), but
it is written in such a way that you can use it even if your work is
unrelated to TeX.
The section `WHETHER AND HOW TO DISTRIBUTE WORKS UNDER THIS LICENSE',
@ -71,11 +74,11 @@ In this license document the following terms are used:
`Work'
Any work being distributed under this License.
`Derived Work'
Any work that under any applicable law is derived from the Work.
`Modification'
`Modification'
Any procedure that produces a Derived Work under any applicable
law -- for example, the production of a file containing an
original file associated with the Work or a significant portion of
@ -85,7 +88,7 @@ In this license document the following terms are used:
`Modify'
To apply any procedure that produces a Derived Work under any
applicable law.
`Distribution'
Making copies of the Work available from one person to another, in
whole or in part. Distribution includes (but is not limited to)
@ -106,16 +109,16 @@ In this license document the following terms are used:
no such explicit nomination then it is the `Copyright Holder' under
any applicable law.
`Base Interpreter'
`Base Interpreter'
A program or process that is normally needed for running or
interpreting a part or the whole of the Work.
interpreting a part or the whole of the Work.
A Base Interpreter may depend on external components but these
are not considered part of the Base Interpreter provided that each
external component clearly identifies itself whenever it is used
interactively. Unless explicitly specified when applying the
license to the Work, the only applicable Base Interpreter is a
`LaTeX-Format' or in the case of files belonging to the
`LaTeX-Format' or in the case of files belonging to the
`LaTeX-format' a program implementing the `TeX language'.
@ -156,8 +159,8 @@ the Derived Work.
distribute a Derived Work provided the following conditions are met
for every component of the Work unless that component clearly states
in the copyright notice that it is exempt from that condition. Only
the Current Maintainer is allowed to add such statements of exemption
to a component of the Work.
the Current Maintainer is allowed to add such statements of exemption
to a component of the Work.
a. If a component of this Derived Work can be a direct replacement
for a component of the Work when that component is used with the
@ -167,13 +170,13 @@ to a component of the Work.
clearly and unambiguously identifies itself as a modified version
of this component to the user when used interactively with that
Base Interpreter.
b. Every component of the Derived Work contains prominent notices
detailing the nature of the changes to that component, or a
prominent reference to another file that is distributed as part
of the Derived Work and that contains a complete and accurate log
of the changes.
c. No information in the Derived Work implies that any persons,
including (but not limited to) the authors of the original version
of the Work, provide any support, including (but not limited to)
@ -183,7 +186,7 @@ to a component of the Work.
d. You distribute at least one of the following with the Derived Work:
1. A complete, unmodified copy of the Work;
1. A complete, unmodified copy of the Work;
if your distribution of a modified component is made by
offering access to copy the modified component from a
designated place, then offering equivalent access to copy
@ -210,15 +213,15 @@ format, where the Work or that Derived Work (in whole or in part) is
then produced by applying some process to that format, does not relax or
nullify any sections of this license as they pertain to the results of
applying that process.
10. a. A Derived Work may be distributed under a different license
provided that license itself honors the conditions listed in
Clause 6 above, in regard to the Work, though it does not have
to honor the rest of the conditions in this license.
b. If a Derived Work is distributed under a different license, that
Derived Work must provide sufficient documentation as part of
itself to allow each recipient of that Derived Work to honor the
itself to allow each recipient of that Derived Work to honor the
restrictions in Clause 6 above, concerning changes from the Work.
11. This license places no restrictions on works that are unrelated to
@ -287,7 +290,7 @@ the Work through the following steps:
a. If it is being maintained, then ask the Current Maintainer
to update their communication data within one month.
b. If the search is unsuccessful or no action to resume active
maintenance is taken by the Current Maintainer, then announce
within the pertinent community your intention to take over
@ -297,17 +300,17 @@ the Work through the following steps:
3a. If the Current Maintainer is reachable and agrees to pass
maintenance of the Work to you, then this takes effect
immediately upon announcement.
b. If the Current Maintainer is not reachable and the Copyright
Holder agrees that maintenance of the Work be passed to you,
then this takes effect immediately upon announcement.
then this takes effect immediately upon announcement.
4. If you make an `intention announcement' as described in 2b. above
and after three months your intention is challenged neither by
the Current Maintainer nor by the Copyright Holder nor by other
people, then you may arrange for the Work to be changed so as
to name you as the (new) Current Maintainer.
5. If the previously unreachable Current Maintainer becomes
reachable once more within three months of a change completed
under the terms of 3b) or 4), then that Current Maintainer must
@ -390,7 +393,7 @@ Here is an example of such a notice and statement:
% version 2005/12/01 or later.
%
% This work has the LPPL maintenance status `maintained'.
%
%
% The Current Maintainer of this work is M. Y. Name.
%
% This work consists of the files pig.dtx and pig.ins
@ -404,7 +407,7 @@ referring to any `LaTeX-Format', and both `Copyright Holder' and
`Current Maintainer' referring to the person `M. Y. Name'.
If you do not want the Maintenance section of LPPL to apply to your
Work, change `maintained' above into `author-maintained'.
Work, change `maintained' above into `author-maintained'.
However, we recommend that you use `maintained', as the Maintenance
section was added in order to ensure that your Work remains useful to
the community even when you can no longer maintain and support it
@ -434,10 +437,9 @@ Important Recommendations
using a line such as:
% This work consists of all files listed in manifest.txt.
in that place. In the absence of an unequivocal list it might be
impossible for the licensee to determine what is considered by you
to comprise the Work and, in such a case, the licensee would be
entitled to make reasonable conjectures as to which files comprise
the Work.

5
_licenses/mit.txt
View File

@ -11,7 +11,7 @@ how: Create a text file (typically named LICENSE or LICENSE.txt) in the root of
using:
- jQuery: https://github.com/jquery/jquery/blob/master/LICENSE.txt
- .NET Core: https://github.com/dotnet/corefx/blob/master/LICENSE
- .NET Core: https://github.com/dotnet/corefx/blob/master/LICENSE.TXT
- Rails: https://github.com/rails/rails/blob/master/activerecord/MIT-LICENSE
permissions:
@ -24,7 +24,8 @@ conditions:
- include-copyright
limitations:
- no-liability
- liability
- warranty
---

5
_licenses/mpl-2.0.txt
View File

@ -26,11 +26,12 @@ permissions:
conditions:
- disclose-source
- include-copyright
- same-license
- same-license--file
limitations:
- no-liability
- liability
- trademark-use
- warranty
---

4
_licenses/ms-pl.txt
View File

@ -7,6 +7,8 @@ description: An open source license with a patent grant.
how: Create a text file (typically named LICENSE or LICENSE.txt) in the root of your source code and copy the text of the license into the file.
using:
permissions:
- commercial-use
- modifications
@ -18,7 +20,7 @@ conditions:
- include-copyright
limitations:
- no-liability
- warranty
- trademark-use
---

6
_licenses/ms-rl.txt
View File

@ -7,6 +7,8 @@ description: An open source license with a patent grant similar to the <a href="
how: Create a text file (typically named LICENSE or LICENSE.txt) in the root of your source code and copy the text of the license into the file.
using:
permissions:
- commercial-use
- modifications
@ -17,10 +19,10 @@ permissions:
conditions:
- disclose-source
- include-copyright
- same-license
- same-license--file
limitations:
- no-liability
- warranty
- trademark-use
---

64
_licenses/ncsa.txt Normal file
View File

@ -0,0 +1,64 @@
---
title: University of Illinois/NCSA Open Source License
spdx-id: NCSA
nickname: UIUC/NCSA
source: https://opensource.org/licenses/NCSA
description: The University of Illinois/NCSA Open Source License, or UIUC license, is a permissive free software license, based on the <a href="/licenses/mit/">MIT/X11 license</a> and the <a href="/licenses/bsd-3-clause/">BSD 3-clause License</a>. Its conditions include requiring the preservation of copyright and license notices both in source and in binary distributions and the prohibtion of using the names of the authors or the project organization to promote or endorse derived products.
how: Create a text file (typically named LICENSE or LICENSE.txt) in the root of your source code and copy the text of the license into the file. Replace [year] with the current year and [fullname] with the name (or names) of the copyright holders. Replace [project] with the project organization, if any, that sponsors this work.
using:
- LLDB: https://github.com/llvm-mirror/lldb/blob/master/LICENSE.TXT
- ROCR-Runtime: https://github.com/RadeonOpenCompute/ROCR-Runtime/blob/master/LICENSE.txt
- RLTK: https://github.com/chriswailes/RLTK/blob/master/LICENSE
permissions:
- commercial-use
- modifications
- distribution
- private-use
conditions:
- include-copyright
limitations:
- liability
- warranty
---
University of Illinois/NCSA Open Source License
Copyright (c) [year] [fullname]. All rights reserved.
Developed by: [fullname]
[project]
[project_url]
Permission is hereby granted, free of charge, to any person
obtaining a copy of this software and associated documentation files
(the "Software"), to deal with the Software without restriction,
including without limitation the rights to use, copy, modify, merge,
publish, distribute, sublicense, and/or sell copies of the Software,
and to permit persons to whom the Software is furnished to do so,
subject to the following conditions:
* Redistributions of source code must retain the above copyright notice,
this list of conditions and the following disclaimers.
* Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimers in the
documentation and/or other materials provided with the distribution.
* Neither the names of [fullname], [project] nor the names of its
contributors may be used to endorse or promote products derived from
this Software without specific prior written permission.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
CONTRIBUTORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS WITH
THE SOFTWARE.

5
_licenses/ofl-1.1.txt
View File

@ -10,6 +10,8 @@ how: Create a text file (typically named LICENSE or LICENSE.txt) in the root of
note: This license doesn't require source provision, but recommends it. All files derived from OFL files must remain licensed under the OFL.
using:
permissions:
- private-use
- commercial-use
@ -21,7 +23,8 @@ conditions:
- same-license
limitations:
- no-liability
- liability
- warranty
---

3
_licenses/osl-3.0.txt
View File

@ -30,7 +30,8 @@ conditions:
limitations:
- trademark-use
- no-liability
- liability
- warranty
---

48
_licenses/postgresql.txt Normal file
View File

@ -0,0 +1,48 @@
---
title: PostgreSQL License
spdx-id: PostgreSQL
source: https://opensource.org/licenses/PostgreSQL
description: A very short, BSD-style license, used specifically for PostgreSQL.
how: To use it, say that it is The PostgreSQL License, and then substitute the copyright year and name of the copyright holder into the body of the license. Then put the license into a prominent file ("COPYRIGHT", "LICENSE" or "COPYING" are common names for this file) in your software distribution.
using:
- pgBadger: https://github.com/dalibo/pgbadger/blob/master/LICENSE
- pgAdmin: https://github.com/postgres/pgadmin4/blob/master/LICENSE
- .NET Access to PostgreSQL: https://github.com/npgsql/npgsql/blob/dev/LICENSE.txt
permissions:
- commercial-use
- modifications
- distribution
- private-use
conditions:
- include-copyright
limitations:
- liability
- warranty
---
PostgreSQL Licence
Copyright (c) [year], [fullname]
Permission to use, copy, modify, and distribute this software and its
documentation for any purpose, without fee, and without a written agreement is
hereby granted, provided that the above copyright notice and this paragraph
and the following two paragraphs appear in all copies.
IN NO EVENT SHALL [fullname] BE LIABLE TO ANY PARTY FOR DIRECT, INDIRECT,
SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES, INCLUDING LOST PROFITS, ARISING
OUT OF THE USE OF THIS SOFTWARE AND ITS DOCUMENTATION, EVEN IF [fullname]
HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
[fullname] SPECIFICALLY DISCLAIMS ANY WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE. THE SOFTWARE PROVIDED HEREUNDER IS ON AN "AS IS" BASIS,
AND [fullname] HAS NO OBLIGATIONS TO PROVIDE MAINTENANCE, SUPPORT, UPDATES,
ENHANCEMENTS, OR MODIFICATIONS.

7
_licenses/unlicense.txt
View File

@ -10,8 +10,8 @@ how: Create a text file (typically named UNLICENSE or UNLICENSE.txt) in the root
using:
- youtube-dl: https://github.com/rg3/youtube-dl/blob/master/LICENSE
- stacktrace.js: https://github.com/stacktracejs/stacktrace.js/blob/master/LICENSE
- kakoune: https://github.com/mawww/kakoune/blob/master/UNLICENSE
- RDF.rb: https://github.com/ruby-rdf/rdf/blob/master/UNLICENSE
permissions:
- private-use
@ -22,7 +22,8 @@ permissions:
conditions: []
limitations:
- no-liability
- liability
- warranty
---
@ -49,4 +50,4 @@ OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,
ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
OTHER DEALINGS IN THE SOFTWARE.
For more information, please refer to <http://unlicense.org>
For more information, please refer to <https://unlicense.org>

4
_licenses/wtfpl.txt
View File

@ -7,6 +7,8 @@ description: The easiest license out there. It gives the user permissions to do
how: Create a text file (typically named LICENSE or LICENSE.txt) in the root of your source code and copy the text of the license into the file.
using:
permissions:
- commercial-use
- modifications
@ -22,7 +24,7 @@ limitations: []
DO WHAT THE FUCK YOU WANT TO PUBLIC LICENSE
Version 2, December 2004
Copyright (C) 2004 [fullname] <[email]>
Copyright (C) 2004 Sam Hocevar <sam@hocevar.net>
Everyone is permitted to copy and distribute verbatim or modified
copies of this license document, and changing it is allowed as long

5
_licenses/zlib.txt
View File

@ -7,6 +7,8 @@ description: A short permissive license, compatible with GPL. Requires altered s
how: Create a text file (typically named LICENSE or LICENSE.txt) in the root of your source code and copy the text of the license into the file. Replace [year] with the current year and [fullname] with the name (or names) of the copyright holders.
using:
permissions:
- commercial-use
- modifications
@ -18,7 +20,8 @@ conditions:
- document-changes
limitations:
- no-liability
- liability
- warranty
---

7
about.md
View File

@ -18,12 +18,11 @@ See our [appendix](/appendix) for a table of all of the licenses cataloged in th
{: .bullets}
* Open Source Initiative's [list of licenses](https://opensource.org/licenses/) approved as conforming to the [Open Source Definition](https://opensource.org/osd)
* Free Software Foundation's [comments on various licenses](http://www.gnu.org/licenses/license-list.html) and [advice on how to choose a license](https://www.gnu.org/licenses/license-recommendations.en.html)
* Linux Foundation's [SPDX License List](https://spdx.org/licenses/)
* [Comparison of free and open-source software licenses](https://en.wikipedia.org/wiki/Comparison_of_free_and_open-source_software_licenses) on English Wikipedia
* Open Source Initiative's FAQ on [Which Open Source license should I choose to release my software under?](https://opensource.org/faq#which-license)
* Free Software Foundation's [advice on how to choose a license](https://www.gnu.org/licenses/license-recommendations.en.html)
* [License differentiator](http://www.oss-watch.ac.uk/apps/licdiff/) ([source](https://github.com/ox-it/licdiff)) from [OSS Watch](http://www.oss-watch.ac.uk/)
* [Free/Libre/Open Source license selection wizard](http://vrici.lojban.org/~cowan/floss/) by John Cowan
* [The Legal Side of Open Source](https://opensource.guide/legal/), an Open Source Guide covering licensing and related issues
## Help us improve it

22
appendix.md
View File

@ -17,7 +17,7 @@ If you're here to choose a license, **[start from the home page](/)** to see a f
{% for type in types %}
{% assign rules = site.data.rules[type] | sort: "label" %}
{% for rule_obj in rules %}
{% if seen_tags contains rule_obj.tag %}
{% if seen_tags contains rule_obj.tag or rule_obj.tag contains '--' %}
{% continue %}
{% endif %}
{% capture seen_tags %}{{ seen_tags | append:rule_obj.tag }}{% endcapture %}
@ -33,20 +33,22 @@ If you're here to choose a license, **[start from the home page](/)** to see a f
{% assign rules = site.data.rules[type] | sort: "label" %}
{% for rule_obj in rules %}
{% assign req = rule_obj.tag %}
{% if seen_tags contains req %}
{% if seen_tags contains req or rule_obj.tag contains '--' %}
{% continue %}
{% endif %}
{% capture seen_tags %}{{ seen_tags | append:req }}{% endcapture %}
{% assign seen_req = false %}
{% for t in types %}
{% if license[t] contains req %}
<td class="license-{{ t }}" style="text-align:center">
<span class="{{ req }}">
<span class="license-sprite {{ req }}"></span>
</span>
</td>
{% assign seen_req = true %}
{% endif %}
{% for r in license[t] %}
{% if r contains req %}
<td class="license-{{ t }}" style="text-align:center">
<span class="{{ r }}">
<span class="license-sprite {{ r }}"></span>
</span>
</td>
{% assign seen_req = true %}
{% endif %}
{% endfor %}
{% endfor %}
{% unless seen_req %}
<td></td>

2
non-software.md
View File

@ -12,7 +12,7 @@ Open source software licenses can be used for non-software works, and often are
### Documentation
Any open source software license or open Creative Commons license is applicable to software documentation. If you use different licenses for your software and its documentation, you may wish to take care that source code examples in the documentation are also licensed under the software license.
Any open source software license or open license for media (see [above](#data-media-etc)) is applicable to software documentation. If you use different licenses for your software and its documentation, you may wish to take care that source code examples in the documentation are also licensed under the software license.
### Fonts

2
script/check-approval
View File

@ -1,4 +1,6 @@
#!/usr/bin/env ruby
# frozen_string_literal: true
# Checks if a given license meets the approval criteria to be added to choosealicense.com
# See https://github.com/github/choosealicense.com/blob/gh-pages/CONTRIBUTING.md#adding-a-license
# Usage: script/check-approval [SPDX LICENSE ID]

7
script/downcase
View File

@ -1,7 +0,0 @@
#! /usr/bin/env ruby
# downcases all licenses in a git-friendly way
Dir['_licenses/*'].each do |file|
system "git mv #{file} #{file.downcase}2"
system "git mv #{file.downcase}2 #{file.downcase}"
end

2
script/generate-docs
View File

@ -1,4 +1,6 @@
#!/usr/bin/env ruby
# frozen_string_literal: true
# Usage: script/generate-docs
# Reads in the fields, meta, and rules YAML files and produces markdown output
# suitable for documenting in the project's README

34
spec/ci_ruby_version_spec.rb Normal file
View File

@ -0,0 +1,34 @@
# frozen_string_literal: true
require 'json'
require 'open-uri'
require 'spec_helper'
require 'yaml'
describe 'ruby version' do
pages_versions = JSON.parse(open('https://pages.github.com/versions.json').read)
pages_ruby_version = pages_versions['ruby']
ci_config_file = '.travis.yml'
ci_config = YAML.load_file(ci_config_file)
ci_ruby_version = ci_config['rvm'][0]
context "in #{ci_config_file} and pages ruby version" do
it 'match' do
msg = "#{ci_ruby_version} != #{pages_ruby_version}; please add a commit bumping in #{ci_config_file}"
expect(ci_ruby_version).to eql(pages_ruby_version), msg
end
end
rubocop_config_file = '.rubocop.yml'
rubocop_config = YAML.load_file(rubocop_config_file)
rubocop_ruby_version = rubocop_config['AllCops']['TargetRubyVersion']
pages_ruby_version_minor = pages_ruby_version.match('^(\d+)\.(\d+)')[0]
context "in #{rubocop_config_file} and pages ruby minor version" do
it 'match' do
msg = "#{rubocop_ruby_version} != #{pages_ruby_version_minor}; please add a commit bumping in #{rubocop_config_file}"
expect(rubocop_ruby_version.to_s).to eql(pages_ruby_version_minor), msg
end
end
end

2
spec/license_bom_spec.rb
View File

@ -1,3 +1,5 @@
# frozen_string_literal: true
require 'spec_helper'
describe 'byte order marks' do

4
spec/license_fields_spec.rb
View File

@ -1,3 +1,5 @@
# frozen_string_literal: true
require 'spec_helper'
describe 'license fillable fields' do
@ -5,7 +7,7 @@ describe 'license fillable fields' do
context "The #{license['title']} license" do
it 'should only contain supported fillable fields' do
matches = license['content'].scan(/\[([a-z]+)\]/)
extra_fields = matches.flatten - fields.map { |f| f['name'] }
extra_fields = matches.flatten - (fields.map { |f| f['name'] })
expect(extra_fields).to be_empty
end
end

32
spec/license_meta_spec.rb
View File

@ -1,3 +1,5 @@
# frozen_string_literal: true
require 'spec_helper'
describe 'license meta' do
@ -7,7 +9,7 @@ describe 'license meta' do
context "The #{license['title']} license" do
it 'should only contain supported meta fields' do
extra_fields = raw_fields.keys - meta.map { |m| m['name'] }
extra_fields = raw_fields.keys - (meta.map { |m| m['name'] })
expect(extra_fields).to be_empty
end
@ -16,6 +18,34 @@ describe 'license meta' do
missing = required - raw_fields.keys
expect(missing).to be_empty
end
it 'using contains 3 examples' do
legacy = [
'afl-3.0',
'agpl-3.0',
'artistic-2.0',
'bsd-2-clause',
'bsd-3-clause',
'bsd-3-clause-clear',
'bsl-1.0',
'cc0-1.0',
'cc-by-4.0',
'cc-by-sa-4.0',
'eupl-1.1',
'gpl-2.0',
'lgpl-2.1',
'lgpl-3.0',
'lppl-1.3c',
'ms-pl',
'ms-rl',
'ofl-1.1',
'wtfpl',
'zlib'
]
skip 'added before 3 using examples required' if legacy.include?(license['slug'])
examples = raw_fields['using'] || []
expect(examples.length).to eq(3)
end
end
end
end

2
spec/license_rules_spec.rb
View File

@ -1,3 +1,5 @@
# frozen_string_literal: true
require 'spec_helper'
describe 'license rules' do

6
spec/license_shown_spec.rb
View File

@ -1,9 +1,11 @@
# frozen_string_literal: true
require 'spec_helper'
describe 'shown licenses' do
# Whitelist of popular licenses that are shown (non-hidden)
# Note: most new licenses that are added should be hidden by default
SHOWN_LICENSES = %w(
SHOWN_LICENSES = %w[
agpl-3.0
apache-2.0
bsd-2-clause
@ -16,7 +18,7 @@ describe 'shown licenses' do
mit
mpl-2.0
unlicense
).freeze
].freeze
it 'has the expected number of shown licenses' do
expect(shown_licenses.count).to eql(12)

2
spec/license_spec.rb
View File

@ -1,3 +1,5 @@
# frozen_string_literal: true
require 'spec_helper'
describe 'licenses' do

4
spec/spec_helper.rb
View File

@ -1,3 +1,5 @@
# frozen_string_literal: true
require 'jekyll'
require 'open-uri'
require 'json'
@ -41,7 +43,7 @@ def licenses
end
def shown_licenses
licenses.select { |l| !l['hidden'] }
licenses.reject { |l| l['hidden'] }
end
def site