-
Notifications
You must be signed in to change notification settings - Fork 7
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
Switching to Community-Spec-1.0 for specification license #14
Conversation
…quested by LF IP Review for OpenSSF Sandbox application !13 Signed-off-by: Ian Dunbar-Hall <ian.dunbar-hall@lmco.com>
Does this require getting signoff from all committers to the project (to change the license they used with their contributions)? |
lgtm |
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.
For now, do not merge this PR!
There is still a discussion ongoing and some of our early folks were very opposed to this license. I'm following up with the OpenSSF in the linked issue on their tracker.
Switching to draft to ensure its not merged until licensing until discussion with LF and maintainers is resolved. |
@JustinCappos thoughts on this PR? We have support from @mnm678 @colek42 and @trishankatdatadog. |
Had a great conversation with Mike Dolan and Jory about the details here. We can merge! |
resolves #13 |
See issue !13.
LF started IP/License review of SBOMit for the OpenSSF sandbox application, and requested we switch the license of the spec to Community Specification License 1.0
See https://github.com/CommunitySpecification/Community_Specification/blob/main/1._Community_Specification_License-v1.md
This is required by the OpenSSF Charter (Section 5, Page 9):
https://cdn.platform.linuxfoundation.org/agreements/openssf.pdf