5 Feb
2021
5 Feb
'21
7:37 p.m.
On Fri, 05 Feb 2021 08:47:38 +0100 Sven Eckelmann wrote:
On Thursday, 4 February 2021 20:58:36 CET Jakub
Kicinski wrote:
Interesting! In my own code I do option 1, copyright protection is
longer than the code I write is relevant :S
3 seems to be what US lawyers like but frankly in the git era they are
probably overly lazy^W cautious.
Option 4 seems nice as well - it's really up to you(r lawyer).
Back when I was working for a vendor I had a
script which used git to
find files touched in current year and then a bit of sed to update the
dates. Instead of running your current script every Jan, you can run
that one every Dec.
Just as an additional anecdote: Just had the situation that a vendor
complained that the user visible copyright notice was still 2020 for a project
published in 2021 but developed and tested 2020 (and thus tagged + packaged in
2020).
Now to something more relevant: what do you think about dropping the copyright
year [1]?