mirror of
https://github.com/github/choosealicense.com
synced 2024-06-26 21:53:02 +02:00
810eeb5618
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. |
||
|---|---|---|
| .. | ||
| afl-3.0.txt | ||
| agpl-3.0.txt | ||
| apache-2.0.txt | ||
| artistic-2.0.txt | ||
| bsd-2-clause.txt | ||
| bsd-3-clause-clear.txt | ||
| bsd-3-clause.txt | ||
| cc-by-4.0.txt | ||
| cc-by-sa-4.0.txt | ||
| cc0-1.0.txt | ||
| epl-1.0.txt | ||
| eupl-1.1.txt | ||
| gpl-2.0.txt | ||
| gpl-3.0.txt | ||
| isc.txt | ||
| lgpl-2.1.txt | ||
| lgpl-3.0.txt | ||
| lppl-1.3c.txt | ||
| mit.txt | ||
| mpl-2.0.txt | ||
| ms-pl.txt | ||
| ms-rl.txt | ||
| ofl-1.1.txt | ||
| osl-3.0.txt | ||
| unlicense.txt | ||
| wtfpl.txt | ||