choosealicense.com/_data/rules.yml

permissions:
- description: This software and derivatives may be used for commercial purposes.
  label: Commercial use
  tag: commercial-use
- description: This software may be modified.
  label: Modification
  tag: modifications
- description: This software may be distributed.
  label: Distribution
  tag: distribution
- 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 contributors.
  label: Patent use
  tag: patent-use

conditions:
- description: A copy of the license and copyright notice must be included with the software.
  label: License and copyright notice
  tag: include-copyright
- description: A copy of the license and copyright notice must be included with the software in source form, but is not required for binaries.
  label: License and copyright notice for source
  tag: include-copyright--source
- description: Changes made to the code must be documented.
  label: State changes
  tag: document-changes
- 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 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
  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 trademark rights, even though licenses without such a statement probably do not grant any implicit trademark rights.
  label: Trademark use
  tag: trademark-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
rename/order license properties better reflect how licenses work and are structured grant (permissions) conditioned on (conditions) with limitations Permissions coming first combats mistaken but apparently widespread impression that licenses impose conditions, even such that without a license, there would be no conditions/work would be in the public domain. Requirements->Conditions emphasizes that they are pertinent if one wants to take advantage of permissions. Forbiddens->Limitations is more accurate: in most cases licenses don't give permission to hold licensors liable, in some cases to use licensors' trademarks or patents, but a licensee does not lose the permissions granted by the license if the licensee holds licensor liable, etc. Also emphasizes that there are limitatations on the license grant, not that the license imposes prohibitions. The most concise place to see both the rename and reorder is in _includes/license-overview.html I did not reorder the appearance of the groups of properties in license source files (.txt files in _licenses) as those orderings are not used to render anything on the webiste. Might do so later. 2016-03-01 13:33:15 -08:00			`permissions:`
first pass at jekyll2ification 2014-07-31 12:36:56 -04:00			`- description: This software and derivatives may be used for commercial purposes.`
convert rule labels to sentance case 2017-03-14 19:44:38 -04:00			`label: Commercial use`
first pass at jekyll2ification 2014-07-31 12:36:56 -04:00			`tag: commercial-use`
			`- description: This software may be modified.`
			`label: Modification`
			`tag: modifications`
Don't inlcude 'you' in any rule descriptions Descriptions should make sense whether reader is licensor or licensee 2017-03-26 16:56:26 -07:00			`- description: This software may be distributed.`
first pass at jekyll2ification 2014-07-31 12:36:56 -04:00			`label: Distribution`
			`tag: distribution`
spel 2017-03-27 08:35:39 -07:00			`- description: This software may be used and modified in private.`
convert rule labels to sentance case 2017-03-14 19:44:38 -04:00			`label: Private use`
first pass at jekyll2ification 2014-07-31 12:36:56 -04:00			`tag: private-use`
Don't inlcude 'you' in any rule descriptions Descriptions should make sense whether reader is licensor or licensee 2017-03-26 16:56:26 -07:00			`- description: This license provides an express grant of patent rights from contributors.`
convert rule labels to sentance case 2017-03-14 19:44:38 -04:00			`label: Patent use`
Rename "Patent Grant" to "Patent Use" Per the discussion in #168, the consumers of the softare are granted the right to use patents. So "Patent Use" makes more sense from a consumer perspective than "Patent Grant". 2015-11-01 22:51:13 -05:00			`tag: patent-use`
first pass at jekyll2ification 2014-07-31 12:36:56 -04:00
sort license properties in the order permissions > conditions > limitations (fixes #387) 2016-08-22 18:25:24 +01:00			`conditions:`
Don't inlcude 'you' in any rule descriptions Descriptions should make sense whether reader is licensor or licensee 2017-03-26 16:56:26 -07:00			`- description: A copy of the license and copyright notice must be included with the software.`
convert rule labels to sentance case 2017-03-14 19:44:38 -04:00			`label: License and copyright notice`
sort license properties in the order permissions > conditions > limitations (fixes #387) 2016-08-22 18:25:24 +01:00			`tag: include-copyright`
Add include-copyright--source condition to more precisely describe bsl-1.0 and zlib 2019-11-18 10:21:22 -08:00			`- description: A copy of the license and copyright notice must be included with the software in source form, but is not required for binaries.`
			`label: License and copyright notice for source`
			`tag: include-copyright--source`
Don't inlcude 'you' in any rule descriptions Descriptions should make sense whether reader is licensor or licensee 2017-03-26 16:56:26 -07:00			`- description: Changes made to the code must be documented.`
convert rule labels to sentance case 2017-03-14 19:44:38 -04:00			`label: State changes`
sort license properties in the order permissions > conditions > limitations (fixes #387) 2016-08-22 18:25:24 +01:00			`tag: document-changes`
spel 2017-03-27 08:35:39 -07:00			`- description: Source code must be made available when the software is distributed.`
convert rule labels to sentance case 2017-03-14 19:44:38 -04:00			`label: Disclose source`
sort license properties in the order permissions > conditions > limitations (fixes #387) 2016-08-22 18:25:24 +01:00			`tag: disclose-source`
Don't inlcude 'you' in any rule descriptions Descriptions should make sense whether reader is licensor or licensee 2017-03-26 16:56:26 -07:00			`- description: Users who interact with the software via network are given the right to receive a copy of the source code.`
convert rule labels to sentance case 2017-03-14 19:44:38 -04:00			`label: Network use is distribution`
sort license properties in the order permissions > conditions > limitations (fixes #387) 2016-08-22 18:25:24 +01:00			`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.`
De-capitalize one mistakenly-capitalized 'License' The surround text (and following items) use the phrase "Same license" and no evidence is present of capitalization of License as a proper noun in this text. 2017-04-08 21:23:05 -07:00			`label: Same license`
sort license properties in the order permissions > conditions > limitations (fixes #387) 2016-08-22 18:25:24 +01:00			`tag: same-license`
same-license--variations 2017-02-19 14:37:32 -08:00			`- 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.`
convert rule labels to sentance case 2017-03-14 19:44:38 -04:00			`label: Same license (file)`
same-license--variations 2017-02-19 14:37:32 -08:00			`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.`
convert rule labels to sentance case 2017-03-14 19:44:38 -04:00			`label: Same license (library)`
same-license--variations 2017-02-19 14:37:32 -08:00			`tag: same-license--library`
sort license properties in the order permissions > conditions > limitations (fixes #387) 2016-08-22 18:25:24 +01:00
rename/order license properties better reflect how licenses work and are structured grant (permissions) conditioned on (conditions) with limitations Permissions coming first combats mistaken but apparently widespread impression that licenses impose conditions, even such that without a license, there would be no conditions/work would be in the public domain. Requirements->Conditions emphasizes that they are pertinent if one wants to take advantage of permissions. Forbiddens->Limitations is more accurate: in most cases licenses don't give permission to hold licensors liable, in some cases to use licensors' trademarks or patents, but a licensee does not lose the permissions granted by the license if the licensee holds licensor liable, etc. Also emphasizes that there are limitatations on the license grant, not that the license imposes prohibitions. The most concise place to see both the rename and reorder is in _includes/license-overview.html I did not reorder the appearance of the groups of properties in license source files (.txt files in _licenses) as those orderings are not used to render anything on the webiste. Might do so later. 2016-03-01 13:33:15 -08:00			`limitations:`
Don't inlcude 'you' in any rule descriptions Descriptions should make sense whether reader is licensor or licensee 2017-03-26 16:56:26 -07:00			`- 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.`
convert rule labels to sentance case 2017-03-14 19:44:38 -04:00			`label: Trademark use`
first pass at jekyll2ification 2014-07-31 12:36:56 -04:00			`tag: trademark-use`
no-liability -> liability, warranty rename and add tag and associated descriptions fixes #412 2016-12-12 14:29:25 -08:00			`- description: This license includes a limitation of liability.`
			`label: Liability`
			`tag: liability`
Don't inlcude 'you' in any rule descriptions Descriptions should make sense whether reader is licensor or licensee 2017-03-26 16:56:26 -07:00			`- description: This license explicitly states that it does NOT grant any rights in the patents of contributors.`
convert rule labels to sentance case 2017-03-14 19:44:38 -04:00			`label: Patent use`
Add "forbidden" property for "patent-use", mirroring "trademark-use", for the sorry licenses that explicitly do not grant any patent permissions 2016-02-28 12:10:23 -08:00			`tag: patent-use`
no-liability -> liability, warranty rename and add tag and associated descriptions fixes #412 2016-12-12 14:29:25 -08:00			`- description: The license explicitly states that it does NOT provide any warranty.`
			`label: Warranty`
			`tag: warranty`