docs: remove (dynamic) years from copyright #58
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Setting copyright programatically to a range up to datetime.today() is legally dubious. It effectively signals that the copyright changes/extends whenever a downstream (perhaps even not holding no copyright of their own) builds the documentation, rather than when the code was authored. I do not believe this to be the case in any jurisdiction. Rather than replace it with a static year (2023 currently) and then keep updating it on a yearly basis, remove the years altogether, as they serve little purpose: the dates are readily available through git, changelogs, PyPI etc. This follows what other projects have done or are in the process of doing as well; for example, see: https://daniel.haxx.se/blog/2023/01/08/copyright-without-years/ https://hynek.me/til/copyright-years/ As a side-effect and primary motivation for this commit, this resolves a rather small build reproducibility (FTBR) issue, where builds in different years would yield different outputs. Signed-off-by: Faidon Liambotis <paravoid@debian.org>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Setting copyright programatically to a range up to datetime.today() is legally dubious. It effectively signals that the copyright changes/extends whenever a downstream (perhaps even not holding no copyright of their own) builds the documentation, rather than when the code was authored. I do not believe this to be the case in any jurisdiction.
Rather than replace it with a static year (2023 currently) and then keep updating it on a yearly basis, remove the years altogether, as they serve little purpose: the dates are readily available through git, changelogs, PyPI etc. This follows what other projects have done or are in the process of doing as well; for example, see:
https://daniel.haxx.se/blog/2023/01/08/copyright-without-years/
https://hynek.me/til/copyright-years/
As a side-effect and primary motivation for this commit, this resolves a rather small build reproducibility (FTBR) issue, where builds in different years would yield different outputs.