-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update LICENSE to Community Specification License 1.0 #79
base: master
Are you sure you want to change the base?
Conversation
FYI: We also will need to change the ITE repo and ensure that files in our repo have the "SPDX-License-Identifier: Community-Spec-1.0". {Note that since the CSL 1.0 in LICENSE is itself CC-BY-4.0, it should have that SPDX License identifier.) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't feel very qualified to comment on this change, but I think it mostly looks okay?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
A short description of why we are making this change will be useful for recordkeeping @JustinCappos |
For rationale: I had a conversation with Mike Dolan from the LF and there is a good reason for us to consider using the Community License Specification for the in-toto specification. See some of the discussion on the SBOMit sandbox thread: ossf/tac#191 (comment) This won't make any difference for anyone who uses or works on an implementation of in-toto. It will effectively just make the specification / ITE editors more visibly aligned with the "Apache 2.0" principles that apply to the implementations. |
Looks like there's a slightly different process for applying this license documented here: https://github.com/CommunitySpecification/Community_Specification/blob/main/..Getting%20Started.md |
No description provided.