Copyright years (and minimizing the burden on developers and maintainers)

[Toni Asensi Esteve]

Dear KDE community,

Recently, on planet KDE 
(https://ervin.ipsquad.net/blog/2023/01/27/web-review-week-2023-04/) 
Kevin Ottens wrote about reducing the maintenance and development burden 
of a project by not periodically changing every copyright year. For 
example, Curl:
     - https://daniel.haxx.se/blog/2023/01/08/copyright-without-years/
     - 
https://github.com/curl/curl/commit/2bc1d775f510196154283374284f98d3eae03544

That's also supported by Steve Winslow [^1] : 
https://www.linuxfoundation.org/blog/blog/copyright-notices-in-open-source-software-projects

[^1]: Steve Winslow runs the Linux Foundation’s license scanning and 
analysis service, advising projects about licenses identified in their 
source code and dependencies. Steve is also involved with projects 
including SPDX, FOSSology and the Community Data License Agreement; 
manages The Linux Foundation’s trademark program; and assists on other 
legal matters. Previously, Steve was Vice President of Technology Law at 
Intralinks and an associate at Choate, Hall and Stewart in Boston. Steve 
graduated from Georgetown University Law Center and majored in computer 
science at Williams College.
         -- 
https://events.linuxfoundation.org/mentorship-session-os-licensing/

Do you think that changing and reviewing too many changes every year is 
worth it? What do you think that would be better?