-
Notifications
You must be signed in to change notification settings - Fork 56
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 LICENSE-MIT #211
Update LICENSE-MIT #211
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ACK 7ccf7e8; successfully ran local tests; fine by me
Written ok from me in relation to any work I have done on this crate - if such a thing is needed. |
According to this random Stack Exchange answer, the copyright year should be either the year the license went into effect or a range (e.g. |
What is the benefit of this now? Do we have to update the 2025 every year? That seems like a step backwards. |
i can delete the Copyright year fully |
Perhaps make a case for why this change is needed in the first place otherwise it looks to me like its not. I am not a lawer and have zero interest in copyright, I care about maintainability though. |
I can't spell either. |
I think we should try to remember to do it every decade or so, as long as the project is maintained. In theory if we have a super old date such that a copyright from that date would've lapsed, somebody could claim they thought the work had fallen into the public domain. But IANAL and I also really don't think this matters. I would not advise deleting the year unless there is a clear reason for it. |
what actions should I take? |
Does the 2017 go stale some time? Like 10 years (2027)? |
I think it "goes stale" 70 years after Clark dies :P. |
Mad, I'll be dead then too. Lets just leave it as it is then huh. |
👀 |
Really though, I don't think this matters, and we should probably just close this PR. |
maybe merge? |
Updated the copyright year from 2017 to 2025 in the LICENSE file