DOC update copyright year forever #19463
Conversation
|
Legally, that does not work: the year assigned here is the year that the setup.py is executed, and not the last year that the code was written. |
|
Right, but the alternative seems to be to update that manually each year, and forget to do it on time half the time. If we are talking about scikit-learn.org that |
|
I'm not convinced that year range has any weight in any case legally speaking. Say you forget to update the end year, that does not change in any way how to the LICENSE or copyright applies to the software, as far as I can tell. Unless we are talking about copyright expiration date, if it applies. |
|
Unless we are talking about copyright expiration date, if it applies.
That's the reason why it's there.
|
|
OK, then doesn't copyright expiration takes place in 70+ years from the creation date https://www.copyright.gov/help/faq/faq-duration.html ? Following that logic we don't need to update those years on a 10 year time scale... |
|
What worries me here is that we are casting doubt on the rigor of our
copyright tracing, and this is not something that I like too much.
We aren't doing formal copyright assignment, or signing contributor
agreements. Our process is already quite light.
|
|
OK, let's revert then. |
Instead of updating every year, let's use Python.