Skip to content

docs: update copyright headers to 2020-2026 range#4904

Open
pranavs321 wants to merge 2 commits intoossf:mainfrom
pranavs321:fix/issue-1534-copyright-range
Open

docs: update copyright headers to 2020-2026 range#4904
pranavs321 wants to merge 2 commits intoossf:mainfrom
pranavs321:fix/issue-1534-copyright-range

Conversation

@pranavs321
Copy link

@pranavs321 pranavs321 commented Jan 10, 2026

What kind of change does this PR introduce?

This is a documentation and automation update to standardize copyright headers.

What is the current behavior?

Currently, copyright headers are inconsistent across the project, with various files showing different years (e.g., 2021, 2023, 2024). The automation in main.yml did not enforce a specific year range, leading to manual updates and potential CI failures.
What is the new behavior?

I have updated the addlicense command in .github/workflows/main.yml to include the -y 2020-2026 flag. I also ran the tool locally to apply this range to all relevant files, ensuring project-wide consistency for the current year.
Which issue(s) this PR fixes

Fixes #1534

@pranavs321 pranavs321 requested a review from a team as a code owner January 10, 2026 08:26
@pranavs321 pranavs321 requested review from raghavkaul and spencerschrock and removed request for a team January 10, 2026 08:26
@dosubot dosubot bot added the size:L This PR changes 100-499 lines, ignoring generated files. label Jan 10, 2026
Signed-off-by: Pranav <pranav.shomys@gmail.com>
@pranavs321 pranavs321 force-pushed the fix/issue-1534-copyright-range branch from 7b28061 to 75c4301 Compare January 10, 2026 08:33
Copy link
Member

@spencerschrock spencerschrock left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi, the guidance in #1534 seems to say different, specifically that we should omit a years field so that we dont need to update it:

Instead, many LF project communities recommend using a more general statement in a form similar to the following (where XYZ is the project’s name):

Copyright The XYZ Authors.
Copyright The XYZ Contributors.
Copyright Contributors to the XYZ project.
These statements are intended to communicate the following:
the work is copyrighted;
the contributors of the code licensed it, but retain ownership of their copyrights; and
it was licensed for distribution as part of the named project.
By using a common format, the project avoids having to maintain lists of names of the authors or copyright holders, years or ranges of years, and variations on the (c) symbol.

https://www.linuxfoundation.org/blog/blog/copyright-notices-in-open-source-software-projects

So if we're going to touch the copywrite in every file, can we do it with an empty -y="" argument?

P.S. How did you get the tool to re-create all the licenses locally? When I tried it just now, it skipped all the files because they already had a license declared

@github-actions
Copy link

This pull request has been marked stale because it has been open for 10 days with no activity

@github-actions github-actions bot added the Stale label Jan 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size:L This PR changes 100-499 lines, ignoring generated files. Stale

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

2 participants