Remove explicit copyright end year from LICENSE #624
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
Codecov Report
@@ Coverage Diff @@
## dev #624 +/- ##
=======================================
Coverage 87.27% 87.27%
=======================================
Files 135 135
Lines 5672 5672
=======================================
Hits 4950 4950
Misses 722 722 |
Constantly having to keep this year updated to the present year seems to simply be a long-standing norm in the open source community, rather than something that's legally required. There doesn't seem to be a consensus on exactly what to remove and what to keep, however, so replacing the end year with "present" seems like the most conservative option that still removes the need to constantly keep the year updated. This was inspired by tox-dev/tox#2941, which also links to a couple other "testimonies": * https://daniel.haxx.se/blog/2023/01/08/copyright-without-years/ * https://hynek.me/til/copyright-years/
ddabble
force-pushed
the
remove-explicit-copyright-end-year
branch
from
b503944
to
4e712cf
Compare
ddabble
added a commit
to MAKENTNU/octopi-setup
that referenced
this pull request
Apr 1, 2023
Constantly having to keep this year updated to the present year seems to simply be a long-standing norm in the open source community, rather than something that's legally required. There doesn't seem to be a consensus on exactly what to remove and what to keep, however, so replacing the end year with "present" seems like the most conservative option that still removes the need to constantly keep the year updated. See MAKENTNU/web#624 for additional details.
ddabble
added a commit
to MAKENTNU/Backup-and-cleanup-Minecraft-Worlds
that referenced
this pull request
Apr 1, 2023
Constantly having to keep this year updated to the present year seems to simply be a long-standing norm in the open source community, rather than something that's legally required. There doesn't seem to be a consensus on exactly what to remove and what to keep, however, so replacing the end year with "present" seems like the most conservative option that still removes the need to constantly keep the year updated. See MAKENTNU/web#624 for additional details.
ddabble
added a commit
to MAKENTNU/Backup-and-cleanup-Minecraft-Worlds
that referenced
this pull request
Apr 1, 2023
Constantly having to keep this year updated to the present year seems to simply be a long-standing norm in the open source community, rather than something that's legally required. There doesn't seem to be a consensus on exactly what to remove and what to keep, however, so replacing the end year with "present" seems like the most conservative option that still removes the need to constantly keep the year updated. See MAKENTNU/web#624 for additional details.
ddabble
added a commit
to MAKENTNU/Backup-to-Drive
that referenced
this pull request
Apr 1, 2023
Constantly having to keep this year updated to the present year seems to simply be a long-standing norm in the open source community, rather than something that's legally required. There doesn't seem to be a consensus on exactly what to remove and what to keep, however, so replacing the end year with "present" seems like the most conservative option that still removes the need to constantly keep the year updated. See MAKENTNU/web#624 for additional details.
ddabble
added a commit
to MAKENTNU/stream
that referenced
this pull request
Apr 1, 2023
Constantly having to keep this year updated to the present year seems to simply be a long-standing norm in the open source community, rather than something that's legally required. There doesn't seem to be a consensus on exactly what to remove and what to keep, however, so replacing the end year with "present" seems like the most conservative option that still removes the need to constantly keep the year updated. See MAKENTNU/web#624 for additional details.
Gunvor4
approved these changes
May 5, 2023
Merged
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.
Proposed changes
Constantly having to keep this year updated to the present year seems to simply be a long-standing norm in the open source community, rather than something that's legally required.
There doesn't seem to be a consensus on exactly what to remove and what to keep, however, so replacing the end year with "present" seems like the most conservative option that still removes the need to constantly keep the year updated.
This was inspired by tox-dev/tox#2941, which also links to a couple other "testimonies":
Areas to review closely
Checklist
(If any of the points are not relevant, mark them as checked)