Changing the Copyright notice #14848

New Issue

GiteaMirror · 2025-11-02T11:24:21-06:00

GiteaMirror commented

2025-11-02 11:24:21 -06:00

Originally created by @WasixXD on GitHub (Aug 8, 2025).

Feature Description

Many files have outdated copyright notices, dating 2, 3, or even 8 years back.

Should we update them to 2025 or use a range (e.g., 2017–2025)?

Screenshots

No response

Originally created by @WasixXD on GitHub (Aug 8, 2025). ### Feature Description Many files have outdated copyright notices, dating 2, 3, or even 8 years back. Should we update them to 2025 or use a range (e.g., 2017–2025)? ### Screenshots _No response_

GiteaMirror added the type/proposal label 2025-11-02 11:24:22 -06:00

GiteaMirror closed this issue

2025-11-02 11:24:22 -06:00

GiteaMirror commented

2025-11-02 11:24:22 -06:00

@techknowlogick commented on GitHub (Aug 8, 2025):

Thank you for your question. These are dated at the time the file is created, and not updated to a more recent date (including using a range). One of the benefits of this approach is that it reduces the noise of such updates, especially around the new year. I know some projects, such as curl, have gone away with putting a year at all, especially since the dates of changes are tracked via git commits, but I wouldn't want to go that far. Our approach strikes a balance between all of these factors, and we lack the necessary legal expertise to determine if changing it is acceptable.

@techknowlogick commented on GitHub (Aug 8, 2025): Thank you for your question. These are dated at the time the file is created, and not updated to a more recent date (including using a range). One of the benefits of this approach is that it reduces the noise of such updates, especially around the new year. I know some projects, such as curl, have gone away with putting a year at all, especially since the dates of changes are tracked via git commits, but I wouldn't want to go that far. Our approach strikes a balance between all of these factors, and we lack the necessary legal expertise to determine if changing it is acceptable.

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#14848