Update copyright year to 2023 #1300
Conversation
|
Hey, thanks for the contribution! However, updating the copyright year when there has been no change to the code is incorrect. The notice is supposed to be indication of when the copyrighted work was created or materially changed. For example, updating the copyright year to 2023 when there have been no copyrightable changes made in 2023 would be incorrect. You can find more information about this in a range of places online, including some related relevant advice from the FSF: https://www.gnu.org/licenses/gpl-howto.html#copyright-notice I am, of course, not a lawyer. Nevertheless, the advice from experts seems pretty clear on this one. I'll close this PR, but welcome your future contributions! If you have any questions, let me know. |
In xsf#1300 (comment) it was said that we do not longer simply bump the copyright year range. But keeping the copyright year at 2021 of all XEPs, including newer ones from 2023, is also far from ideal. So let's simply extract the copyright year from the revision information we already have.
That comes a bit surprising, given that bumping the copyright year of all XEPs is what we always did. It is not that I disagree with your rationale, though. However, not bumping the copyright year is a even worse situation. Hence #1310 |
No description provided.