Add LICENSE file with the CC BY-NC-SA 4.0 legal code#17
Open
EHxuban11 wants to merge 1 commit into
Open
Conversation
The README declares CC BY-NC-SA 4.0 but no LICENSE file exists at the repository root, so tooling and downstream users see no license at all. This adds the verbatim license text the authors already chose.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The README states that this work is licensed under CC BY-NC-SA 4.0 (added in response to #4), but there is no
LICENSEfile at the repository root. This PR adds one, containing the verbatim legal code of the license you already chose, taken directly from creativecommons.org. No terms are changed, and no new decision is being asked of you.GitHub's license detection (licensee) does not recognise CC BY-NC-SA 4.0, so the repository sidebar will show a generic "View license" link rather than a named license badge. That is expected, and is not a problem with the file itself. There is currently no way to get a named badge for this license on GitHub.
An optional question, entirely up to you
Creative Commons recommend against using CC licenses for software, because they do not address patent grants or the source versus object code distinction, and "NonCommercial" is well known for being undefined in practice. If your intent is "free for research, not for commercial use", then PolyForm Noncommercial 1.0.0 expresses exactly that in software specific language. I would be happy to send a follow up PR if you prefer that. Otherwise, this PR simply makes official what the README already says.
Thanks for the great work on AnyDepth