Copyright Statement Years

[Richard Laager]

https://blog.ntpsec.org/2020/02/15/copyright-year.html

"There is no need to include the year in a copyright declaration
statement. And related, there is no need to update the year statement,
add new year statements, manage year range statements, or any of that
stuff. It is tedious, boring, adds no value, and prevents no risks.

"Several large legally sophisticated companies, include Amazon, Google,
Microsoft, and Facebook, are now publishing open source code with
copyright statements without a year."

Can you cite some examples of those large companies publishing open
source code without a year? Do you have any legal analysis on this you
can share, publicly or privately?

I'm asking for three reasons:
1) My own curiosity
2) Wearing my Debian packager hat, in case this comes up with Debian
   when I bring in the next NTPsec release with all the years scrubbed
   and update debian/copyright to match.
3) Because I'd like to convince others of this point, so I can stop
   having to maintain copyright statements all over the place.

-- 
Richard

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <https://lists.ntpsec.org/pipermail/devel/attachments/20200218/0b127d50/attachment.bin>