Skip to content

update copyright year - #386

Merged
meeg merged 3 commits into
mainfrom
update-copyright-year
Jan 26, 2026
Merged

update copyright year#386
meeg merged 3 commits into
mainfrom
update-copyright-year

Conversation

@mmdiego

@mmdiego mmdiego commented Jan 26, 2026

Copy link
Copy Markdown
Contributor

No description provided.

@meeg

meeg commented Jan 26, 2026

Copy link
Copy Markdown
Contributor

This is something people argue about online . . . it seems like 2021, 2021 - 2026 updated every year, 2021 - present, and no year at all are all used by major projects (including things run by big companies with good lawyers).

I am fine with whatever but:

  • whatever we do, we should be consistent in the RtD conf.py and the LICENSE file
  • if there is not a strong opinion we should avoid 2021 - 2026, because it requires updating every year and it is not worth it
  • if there is no opinion at all, I prefer to avoid making a change when it is not necessary

thoughts?

@mmdiego

mmdiego commented Jan 26, 2026

Copy link
Copy Markdown
Contributor Author

I'm ok with removing the year 👍

@meeg

meeg commented Jan 26, 2026

Copy link
Copy Markdown
Contributor

Done, some examples (taken from the pages I linked previously):

For the record - the reason not to keep it as is with 2021 is that maybe it gives the impression that the project is not in active development.

@meeg
meeg merged commit b65260c into main Jan 26, 2026
3 checks passed
@meeg meeg changed the title updated copyright year to 2026 update copyright year Jan 26, 2026
@meeg
meeg deleted the update-copyright-year branch January 28, 2026 03:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants