You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Per team discussion, we're going to remove the copyright year (or year range in some cases) from the top of each source file, but leave the copyright notice itself, so the first line just says # Copyright Canonical Ltd..
This blog post notes that various large projects and companies have started doing this (curl, React, Amazon), so there's a good precedent.
As mentioned in the [Curl commit])(curl/curl@2bc1d77), there's no legal need:
they are mostly pointless in all major jurisdictions
many big corporations and projects already don't use them
saves us from pointless churn
git keeps history for us
The text was updated successfully, but these errors were encountered:
FYI, this is the ruff rule I mentioned. I have the feeling we may need to turn it off, because the regex expects a year and can't be customised in ruff. Not 100% sure on that, though.
Hmm, apparently our legal team recommends keeping just the creation year. And as @james-garner-canonical found, the appendix in the Apache license says to use the format "Copyright [yyyy] [name of copyright owner]" with the year. Oh well, let's be safe and change all the files to just the year the file was created (and no ranges).
Per team discussion, we're going to remove the copyright year (or year range in some cases) from the top of each source file, but leave the copyright notice itself, so the first line just says
# Copyright Canonical Ltd.
.This blog post notes that various large projects and companies have started doing this (curl, React, Amazon), so there's a good precedent.
As mentioned in the [Curl commit])(curl/curl@2bc1d77), there's no legal need:
The text was updated successfully, but these errors were encountered: