1
0
mirror of https://github.com/github/choosealicense.com synced 2024-06-26 05:33:02 +02:00

rm 'rename' field; never used to describe any license

Searched with `git log -Srename`

Arguably *could* be used to describe ofl-1.1 or artistic-2.0, but
renaming is an option for licensors to include in ofl-1.1 and one
of a few ways to comply with artistic-2.0. Doesn't seem straightforward
or common enough to catalog here.
This commit is contained in:
Mike Linksvayer 2016-04-11 17:07:11 -07:00
parent c3e53e968d
commit e5a92ccb50
2 changed files with 0 additions and 4 deletions

View File

@ -87,7 +87,6 @@ The license properties (rules) are stored as a bulleted list within the licenses
* `document-changes` - Indicate significant 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.
* `rename` - You must change the name of the software if you modify it.
* `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.
#### Limitations

View File

@ -11,9 +11,6 @@ conditions:
- 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
- description: You must change the name of the software if you modify it.
label: Rename
tag: rename
- 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