Update license-mapping.json for BSD-3-Clause #253
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
BSD-3-Clause and BSD-4-Clause both had the name "BSD License", s.t. an unique mapping was not possible. The BSD-4-Clause is the "original" BSD-Clause, while BSD-3 is the "2.0". Therefore, I changed the name "BSD License" for the BSD-3-Clause to "BSD License 2.0". Signed-off-by: italvi <[email protected]>
|
I agree that "BSD License" should not be mapped to "BSD-3-Clause" as it's not clear which BSD version is meant in the former (we did remove this mapping in ORT a while a go, BTW). However, I'm not sure whether mapping "BSD License 2.0" instead is a good idea, as it could easily be misread as "BSD License 2", which in turn could be misread as "BSD-2-Clause". I acknowledge that Wikipedia mentions "BSD License 2.0" as an alias for "BSD-3-Clause", but I'm wondering whether there's any real-life example of a software package that uses "BSD License 2.0" as part of its license metadata? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
BSD-3-Clause and BSD-4-Clause both had the name "BSD License", s.t. an unique mapping was not possible. The BSD-4-Clause is the "original" BSD-Clause, while BSD-3 is the "2.0". Therefore, I changed the name "BSD License" for the BSD-3-Clause to "BSD License 2.0".