annotations: Use SPDX License Expressions for licenses#680
Merged
vbatts merged 1 commit intoopencontainers:masterfrom May 19, 2017
Merged
annotations: Use SPDX License Expressions for licenses#680vbatts merged 1 commit intoopencontainers:masterfrom
vbatts merged 1 commit intoopencontainers:masterfrom
Conversation
aa63dac to
25588f0
Compare
Instead of comma-separated short identifiers, which have unclear semantics (are the delimiters AND or OR?). I don't see any discussion of the syntax for this field in [1] (which landed it), but I'd floaded license expressions before in the sub-thread starting at [2]. Greg had pushed back against my earlier proposal (licensing information on descriptors) with [3]: > No, that's not going to work at all, you can't properly describe the > license for a whole layer in any form of a string that could be > standardized or parsed. SPDX is great for describing the individual > licenses of things, but not for a collection of things, which almost > always has an arbitrary license (example, what's the license, in a > simple string, for a Ubuntu base layer?) But SPDX License Expression are both more expressive and better defined than the current comma delimiters. Everything you could have said with the comma-delimited string you can say more clearly with a SPDX License Expression. And because the syntax is not OCI-specific, you're more likely to be able to find tooling that handles these values out of the box. [1]: opencontainers#636 [2]: opencontainers#501 (comment) [3]: opencontainers#501 (comment) Signed-off-by: W. Trevor King <wking@tremily.us>
Member
Contributor
Author
That SPDX appendix isn't very long ;). Reading through it a few times seems better than inventing an OCI-specific syntax that is more limited. If maintainers want to limit what you can say (for some reason), then making
So "I'm leaning towards LGTM but want to think about it more and/or hear what others think"? Or is there some way I can adjust the wording to make you happier now? |
Member
|
👍 == LGTM |
Contributor
Merged
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
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.
Instead of comma-separated short identifiers, which have unclear semantics (are the delimiters
ANDorOR?). I don't see any discussion of the syntax for this field in #636 (which landed it), but I'd floaded license expressions before in the sub-thread starting here. @gregkh had pushed back against my earlier proposal (licensing information on descriptors) with:But SPDX License Expressions are both more expressive and better defined than the current comma delimiters. Everything you could have said with the comma-delimited string you can say more clearly with a SPDX License Expression. And because the syntax is not OCI-specific, you're more likely to be able to find tooling that handles these values out of the box.
There are other annotation adjustments in flight with #678, but that's not currently touching the
licensesentry.