-
Notifications
You must be signed in to change notification settings - Fork 8
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
Qa/checkstyle #47
base: develop
Are you sure you want to change the base?
Qa/checkstyle #47
Conversation
* See the License for the specific language governing permissions and | ||
* limitations under the License. | ||
*/ | ||
// Copyright 2021 The Terasology Foundation |
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.
2014 -> 2021? What has changed? If nothing else in the file has changed then I might just leave the 2014 date in there.
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.
This is the case for most of the changes in this pull request.
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.
let's stick with our current practice of updating to the current year for now so we keep consistency
as mentioned on Discord, we can discuss our copyright practices in the next reviver meeting
@soloturn please update all copyright headers in hear to the current year 2023
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.
@jdrueckert i looked it up this time, and not updating would be the safe option:
https://techwhirl.com/updating-copyright-notices/
“the year date [in the copyright notice] is more than one year later than the year in which publication first occurred, the work is considered to have been published without any notice….”
that would mean, if somebody using code older than a year, it would have some default copyright and any committer could sue the person using it. of course one can argue that in git one sees that it was there before and had a different copyright. but for binary downloads? of course nobody of the persons committing here is a copyright troll. but why play with the fire if not necessary. @jdrueckert. i do agree thus with @BenjaminAmos and reverted all to the original. but feel free to ping here in case you really discussed it in a reviewer meeting.
4d18100
to
6deb5ca
Compare
6deb5ca
to
91508b5
Compare
No description provided.