-
Notifications
You must be signed in to change notification settings - Fork 568
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
Add a LICENSE file? #721
Comments
What kind of license should we add? Something Creative Commons since there is no code in this repo? |
Yeah, I imagine we'd need to consult with the Foundation (and I can bring this to the CPC), but CC0 would be great by me. If we want to restrict people's ability to alter the image (so they don't alter it to include the wrong dates or an unsavory message), there's CC-BY-ND. And for more options: https://creativecommons.org/about/cclicenses/ |
If it helps at all with deciding what license, we generate the image using https://github.com/nodejs/lts-schedule (which has its own license ambiguity nodejs/lts-schedule#13) based on the schedule.json data in this repository. |
Foundation guidance on licences - https://github.com/openjs-foundation/cross-project-council/blob/main/IP_POLICY_GUIDANCE.md#1-licensing CC BY 4.0 are the two listed for documentation |
@mhdawson the link is now broken. |
This is the new link for the IP policy guidance if that is what you meant - https://github.com/openjs-foundation/cross-project-council/blob/main/governance/IP_POLICY_GUIDANCE.md |
I was asked today how to get permission to use the image in the README. I went to see what the content is licensed with and there doesn't seem to be an indication.
The text was updated successfully, but these errors were encountered: