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

45 lines
1.9 KiB
YAML
Raw Normal View History

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
conditions:
first pass at jekyll2ification
2014-07-31 12:36:56 -04:00
- description: Include a copy of the license and copyright notice with the code.
harmonize capitalization of labels (title case)
2016-03-06 23:13:18 +00:00
label: License and Copyright Notice
first pass at jekyll2ification
2014-07-31 12:36:56 -04:00
tag: include-copyright
state changes missing from 4 licenses which have condition also drop 'significant' from description, does not correspond to any license
2016-04-25 15:08:39 -07:00
- description: Indicate changes made to the code.
first pass at jekyll2ification
2014-07-31 12:36:56 -04:00
label: State Changes
tag: document-changes
remove note about LGPL and OSL, see discussion in #343
2016-02-05 09:15:05 -08:00
- description: Source code must be made available when distributing the software.
first pass at jekyll2ification
2014-07-31 12:36:56 -04:00
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
tag: network-use-disclose
make same-license requirement, add to all copyleft licenses
2016-02-05 10:25:19 -08:00
- 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
first pass at jekyll2ification
2014-07-31 12:36:56 -04: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
permissions:
first pass at jekyll2ification
2014-07-31 12:36:56 -04:00
- 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: You may distribute this software.
label: Distribution
tag: distribution
- description: You may use and modify the software without distributing it.
label: Private Use
tag: private-use
- description: This license provides an express grant of patent rights from the contributor to the recipient.
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
label: Patent Use
tag: patent-use
first pass at jekyll2ification
2014-07-31 12:36:56 -04: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:
BSD and OFL licenses have no endorsement clauses, not explicit non-grant of trademark rights. Generalize description of trademark a bit to 'or' include other marks, as some licenses include others, though trademark the only universal among such licenses.
2015-12-14 11:15:38 -08:00
- description: While this may be implicitly true of all licenses, this license explicitly states that it does NOT grant you any rights in the trademarks or other marks of contributors.
Use Trademark -> Trademark Use to match otther Use Xs
2016-02-28 12:15:51 -08:00
label: Trademark Use
first pass at jekyll2ification
2014-07-31 12:36:56 -04:00
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
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
- description: This license explicitly states that it does NOT grant you any rights in the patents of contributors.
label: Patent Use
tag: patent-use
Reference in New Issue Copy Permalink