You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Copy file name to clipboardExpand all lines: README.md
+13-13Lines changed: 13 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -43,9 +43,9 @@ Licenses sit in the `/_licenses` folder. Each license has YAML front matter desc
43
43
*`source` - The URL to the license source text
44
44
*`description` - A human-readable description of the license
45
45
*`how` - Instructions on how to implement the license
46
-
*`required` - Bulleted list of required rules
47
-
*`permitted` - Bulleted list of permitted rules
48
-
*`forbidden` - Bulleted list of forbidden rules
46
+
*`permissions` - Bulleted list of permission rules
47
+
*`conditions` - Bulleted list of condition rules
48
+
*`limitations` - Bulleted list of limitation rules
49
49
50
50
#### Optional fields
51
51
@@ -77,7 +77,15 @@ The license properties (rules) are stored as a bulleted list within the licenses
77
77
78
78
### Rules
79
79
80
-
#### Required
80
+
#### Permissions
81
+
82
+
*`commercial-use` - This software and derivatives may be used for commercial purposes.
83
+
*`modifications` - This software may be modified.
84
+
*`distribution` - You may distribute this software.
85
+
*`private-use` - You may use and modify the software without distributing it.
86
+
*`patent-use` - This license provides an express grant of patent rights from the contributor to the recipient.
87
+
88
+
#### Conditions
81
89
82
90
*`include-copyright` - Include a copy of the license and copyright notice with the code.
83
91
*`document-changes` - Indicate significant changes made to the code.
@@ -86,15 +94,7 @@ The license properties (rules) are stored as a bulleted list within the licenses
86
94
*`rename` - You must change the name of the software if you modify it.
87
95
*`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.
88
96
89
-
#### Permitted
90
-
91
-
*`commercial-use` - This software and derivatives may be used for commercial purposes.
92
-
*`modifications` - This software may be modified.
93
-
*`distribution` - You may distribute this software.
94
-
*`private-use` - You may use and modify the software without distributing it.
95
-
*`patent-use` - This license provides an express grant of patent rights from the contributor to the recipient.
96
-
97
-
#### Forbidden
97
+
#### Limitations
98
98
99
99
*`trademark-use` - 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.
100
100
*`no-liability` - Software is provided without warranty and the software author/license owner cannot be held liable for damages.
Copy file name to clipboardExpand all lines: _data/rules.yml
+3-3Lines changed: 3 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,4 @@
1
-
required:
1
+
conditions:
2
2
- description: Include a copy of the license and copyright notice with the code.
3
3
label: License and copyright notice
4
4
tag: include-copyright
@@ -18,7 +18,7 @@ required:
18
18
label: Same License
19
19
tag: same-license
20
20
21
-
permitted:
21
+
permissions:
22
22
- description: This software and derivatives may be used for commercial purposes.
23
23
label: Commercial Use
24
24
tag: commercial-use
@@ -35,7 +35,7 @@ permitted:
35
35
label: Patent Use
36
36
tag: patent-use
37
37
38
-
forbidden:
38
+
limitations:
39
39
- 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.
Copy file name to clipboardExpand all lines: _licenses/afl-3.0.txt
+3-3Lines changed: 3 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -6,17 +6,17 @@ description: The Academic Free License is a variant of the Open Source License t
6
6
7
7
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 OSL 3.0 must also include the notice "Licensed under the Academic Free License version 3.0" adjacent to the copyright notice.
Copy file name to clipboardExpand all lines: _licenses/agpl-3.0.txt
+3-3Lines changed: 3 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -12,21 +12,21 @@ how: Create a text file (typically named LICENSE or LICENSE.txt) in the root of
12
12
13
13
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.
Copy file name to clipboardExpand all lines: _licenses/apache-2.0.txt
+3-3Lines changed: 3 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -10,18 +10,18 @@ how: Create a text file (typically named LICENSE or LICENSE.txt) in the root of
10
10
11
11
note: The Apache 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.
Copy file name to clipboardExpand all lines: _licenses/artistic-2.0.txt
+3-3Lines changed: 3 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -7,18 +7,18 @@ description: Heavily favored by the Perl community, the Artistic license require
7
7
8
8
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.
0 commit comments