Based on our discussion on Discord and the resulting decision to remove the year from our in-file copyright notices (see link).
Summary:
There's unclarity on whether the copyright year refers to the date of file creation, last change, or the current year.
Date of creation is hard to track and loses meaning in the light of code changes, moves, or copies.
Current year introduces maintenance overhead, especially for small maintainer groups such as ours.
Many organizations started removing the year from the in-file copyright notices.
Apache License requires us to include a LICENSE and a NOTICE file and to maintain file-level copyright notices.
It doesn't object to changing file-level copyright notices, for instance, removing the year.
Based on our discussion on Discord and the resulting decision to remove the year from our in-file copyright notices (see link).
Summary:
There's unclarity on whether the copyright year refers to the date of file creation, last change, or the current year. Date of creation is hard to track and loses meaning in the light of code changes, moves, or copies. Current year introduces maintenance overhead, especially for small maintainer groups such as ours. Many organizations started removing the year from the in-file copyright notices.
Apache License requires us to include a
LICENSE
and aNOTICE
file and to maintain file-level copyright notices. It doesn't object to changing file-level copyright notices, for instance, removing the year.