-
Notifications
You must be signed in to change notification settings - Fork 224
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
Bump copyright year in README.md #3299
Bump copyright year in README.md #3299
Conversation
This commit bumps the copyright year in the README.md file.
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.
Same as in the other PRs of the same kind already, thanks for the change. I was unable to find more places that would require a change.
Happy New Year! What about https://github.com/corona-warn-app/cwa-website/blob/master/NOTICE? I don't know if this file even makes sense in fact. There are various opinions on the Internet about whether it is legally necessary to update Copyright notices on websites or not. That would be a question for the lawyers. It does however give readers an idea about whether the website is up-to-date or not. |
@MikeMcC399 To me, it looks like the NOTICE file of this repository was never correctly established. When comparing the file from this repository to the file in the documentation repository , it looks like the contributors are missing. But also there, in the documentation repo, the copyright year has never been changed. I'm unsure if this file is really relevant. |
Honestly, I'm not sure. I will forward it and let you know. I'd suggest we merge this and make a separate PR for the notice. Also Happy New Year to both of you. I will be on vacation for around two weeks and only check in here irregularly, but @dsarkar is back in action. 🎉 |
https://www.apache.org/licenses/LICENSE-2.0 in the section "HOW TO APPLY THE APACHE LICENSE TO YOUR WORK" says: however since the suggested text is already in the README, Licensing section and NOTICE is incorrectly completed, then I suggest that the NOTICE file is deleted as part of any Copyright update review. |
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.
Thanks for the PR @Ein-Tim!
I'd like to merge this now that we've had a change to the FAQ. The concerns about the NOTICE file have been forwarded and we will take action if necessary, thanks for the information @MikeMcC399.
If the README only refers to itself: "Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License." and the NOTICE file refers to "them" without specifying what "them" means as in: "you may not use them except in compliance with the License." then this should be cleaned up. My reading of opinions about Copyright notices says that they are not really necessary, so if they are not necessary, then it doesn't matter if they are clean or not, however this should be sorted out by legal experts. Thank for passing on the concerns in any case. |
Description
This PR bumps the copyright year in the README.md file.
Happy new year! 🎉
Note
This PR should only be merged once a change to any content of this repository was done.
Internal Tracking ID: EXPOSUREAPP-14521