-
Notifications
You must be signed in to change notification settings - Fork 9
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
[Onboarding checklist] clarify requirements around copyright notice #38
Comments
Assigning myself, I'll help get these answers for you, Tobie. |
@brianwarner let's make sure we capture these answers somewhere for documentation purposes, perhaps on the onboarding repo? |
Generally speaking, we recommend something like "Copyright Contributors to the [projectname]" as opposed to "Copyright [foundationname]". |
I would also follow up to this and say - never remove existing copyright notices. While this line applies to all project contributors going forward, it doesn't replace notices which are already there (for a variety of reasons, where one is that it could be required by the license). |
That’s just content in licenses and headers right? Nor for the website itself? |
The onboarding checklist contains the following item:
It would be great to clarify the following:
For the website:
For the LICENSEs and READMEs:
For source code files:
I understand that the above may differ depending on what license the project is under, or whether the project ues a CLA, DCO, or nothing (see openjs-foundation/cross-project-council#387 on that topic). Regardless, I think having those guidelines somewhere would be helpful.
The text was updated successfully, but these errors were encountered: