-
-
Notifications
You must be signed in to change notification settings - Fork 30.3k
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
Use static copyright years #126133
Comments
+1 example: 2001-200x 2001-201x |
IMNSHO lets just adopt this already. Do not update existing copyright dates in existing files. Ex: From other your examples above - Google's policy was always "never touch the year" with the year of file creation or copyright statement addition being the standard. As noted in https://opensource.google/documentation/reference/releasing/preparing#license-headers |
Do you mean leave them as-is, and stop updating them each year? However, I expect we will still see many PRs from people who see "2001-2024" and want to help by updating to "2001-2025". It will be easy, though tedious, for us to close them, but at the expense of having wasted the time of contributors. Or to remove the end years? I think this is better, as I doubt we'll get PRs updating "2001" to "2001-2025". Here's a draft PR to illustrate: #126236. |
Short version
Each January we update the PSF copyright years in the repo:
2025 is approaching.
Can we get permission from the PSF to adopt a copyright that does not need updating every year?
I suggest something like one of the following:
Longer version
Last year, we updated it in 15 places in 10 files:
Sometimes we miss a few and have to update them later:
2023 Update copyright years to 2023. #100848
Update additional copyright years to 2023. #100859
2022 Update copyright year to 2022. #30335
Or we miss something, merge the fix a year late, which needs refixing:
Update README.rst #25514
Fix copyright years in
README.rst
#31347And sometimes we backport these to (some) older branches, but other years don't:
[3.10] Update copyright years to 2023. (gh-100848). #100850
[3.9] Update copyright years to 2023. (gh-100848). #100851
[3.8] Update copyright years to 2023. (gh-100848). #100852
[3.7] Update copyright years to 2023. (gh-100848). #100853
[3.9] Update copyright year to 2022. (GH-30335) #30337
[3.7] Bring Python into the next decade. (GH-17801). #17803
[3.6] Bring Python into the next decade. (GH-17801). #17804
[2.7] Bring Python into the next decade. (GH-17801). #17805
[3.8] Bring Python into the new year. (GH-24036) #24046
[3.7] Bring Python into the new year. (GH-24036) #24047
[3.7] Bring Python into the new year. (GH-24036) #24052
[3.6] Bring Python into the new year (GH-24036) #24054
[3.6] Bump copyright years to 2019. (GH-11404). #11407
[2.7] Bump copyright years to 2019. (GH-11404). #11408
[2.7] advance copyright years to 2018 (GH-5094). #5105
Sometimes there's lots of duplicate PRs that end up closed and wasting everyone's time:
Not only is this tedious work, it is likely unnecessary. A lot of big projects have stopped updating copyright years: https://hynek.me/til/copyright-years/
For example:
These either have only have the first year, omit years altogether, or end with "present".
Can we do something similar?
Linked PRs
The text was updated successfully, but these errors were encountered: