mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-28 10:55:54 +03:00
[GH-ISSUE #1052] Copyright year not updated #878
Labels
No labels
awaiting feedback
bug
cannot reproduce
dns provider request
duplicate
enhancement
enhancement
enhancement
good first issue
help wanted
invalid
need more info
no certbot plugin available
product-support
pull-request
question
stale
troll
upstream issue
v2
v2
v2
v3
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nginx-proxy-manager-NginxProxyManager#878
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @KucharczykL on GitHub (Apr 30, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1052
github.com/jc21/nginx-proxy-manager@b42cc9ed3e/frontend/js/i18n/messages.json (L63)I thought I was on old version because the year is still 2019 in the footer. This whole line should probably not be in the translatable strings because there is nothing to translate and it will inevitably get obsolete (as evidenced by this issue).
@jakern commented on GitHub (May 7, 2021):
I have heard that it shouldn't be updated https://stackoverflow.com/questions/2390230/do-copyright-dates-need-to-be-updated
@jc21 commented on GitHub (May 8, 2021):
Yep and I was aware somehow that copyrights only last 5 years - though I can't back that statement up atm 🤷
As someone in the stack overflow commented, it could just be removed.
@johntdavis84 commented on GitHub (May 10, 2021):
Disclaimer: I am a lawyer, but this is not legal advice.
For the United States, re: Copyright Term: https://www.copyright.gov/help/faq/faq-duration.html
Re: Registration and Enforceability (beware massive oversimplification here): In the United States,
As others have mentioned, I would suggest keeping the copyright and making it a date range. Earliest year to current year. If nothing else, that's super useful for seeing how old a project is and if it's still in development (assuming you manually update the year).
@war59312 commented on GitHub (Jul 30, 2023):
Indeed, I'd just change to javascript so always the latest year.
@github-actions[bot] commented on GitHub (Mar 12, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@github-actions[bot] commented on GitHub (Apr 24, 2025):
Issue was closed due to inactivity.