Skip to content
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

Update and Standardize Copyrights #29709

Closed
wants to merge 11 commits into from
Closed

Conversation

drewroberts
Copy link

This PR updates copyrights from 2023 to 2024 for "The Bitcoin Core developers" and "Bitcoin Developers" while leaving copyrights for other entities alone. It also standardizes the use of copyrights as there were approximately 20 files that said "-present" while hundreds said "-2023" or another end year that hadn't been updated. Although this is a trivial change, a significant number of files were edited, so please thoroughly review before merging. I double-checked every edit I made but would appreciate your feedback.

2024 is here and we're less than a month away from the halving!

@DrahtBot
Copy link
Contributor

DrahtBot commented Mar 23, 2024

The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.

Code Coverage

For detailed information about the code coverage, see the test coverage report.

Reviews

See the guideline for information on the review process.
A summary of reviews will appear here.

@achow101
Copy link
Member

achow101 commented Mar 23, 2024

-present is intentional and it's purpose is to avoid having to update the copyright headers every year, and also so we can avoid constantly getting PRs such as this.

Besides that, the copyright year notice is typically updated at the end of the year being added, and is only done to files that were changed within that year. But I think we're probably going to stop doing that now too. It's kinda pointless.

@achow101 achow101 closed this Mar 23, 2024
@drewroberts
Copy link
Author

That makes sense. Thank you for taking the time to explain the procedure to me, @achow101

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.

None yet

3 participants