-
Notifications
You must be signed in to change notification settings - Fork 31
Update LICENSE to Community Specification License #261
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
Conversation
WDYM? |
|
Check the bottom of this:
https://raw.githubusercontent.com/JustinCappos/uptane-standard-licensefix/master/uptane-standard.md
Is this automatically added to the file? Is this just a comment we should
remove?
…On Wed, Sep 27, 2023 at 5:04 PM Trishank Karthik Kuppusamy < ***@***.***> wrote:
I don't know the right way to fix the text at the bottom of the standard
WDYM?
—
Reply to this email directly, view it on GitHub
<#261 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAGROD4OMY4E2BIRMCLCBZ3X4SIGFANCNFSM6AAAAAA5JMI7FQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
FYI: other files in our repo should have "SPDX-License-Identifier: Community-Spec-1.0". The change should also happen for the PUREs repo, but I'll wait for this to be approved, etc. first. |
trishankatdatadog
left a comment
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.
The LICENSE update LGTM
IDK but that change isn't part of this PR |
Right, I was trying to solicit help / suggestions from someone in the know about this. It looks like @tkfu was the one who added it. Jon, can you comment on this? Should we just change / excise this mention? Is it autogenerated? |
|
In order to move to the Community Specification license I believe we need to add some other supplementary files in the repository as well. The License references these. See below... Here is a good reference of how we can adopt the license. |
I don't know the right way to fix the text at the bottom of the standard. Please don't merge until we figure that out.