Fix Copyright Year

[ghost]

Consider removing the year (saw it in several repos)

Alternatively, update the year:

https://github.com/algorandfoundation/algokit-cli/blob/main/LICENSE#L3

[robdmoore]

I don't believe that's necessary. My understanding is you generally only need to include the first year of publish.

https://www.copyrightlaws.com/copyright-symbol-notice-year/ Seems to indicate that's the case too.

[ghost]

@robdmoore , you simply do not close issues that fast, based on an "understanding" that you have.

Maybe reopen, so we can wait for further feedback until this is 100% clear?

[ghost]

To use your resource ( https://www.copyrightlaws.com/copyright-symbol-notice-year/) :

WHAT ABOUT BLOGS AND WEBSITES? New versions or editions of works should contain the publication date of the new version or edition. For constantly evolving websites and blogs that contain works published over several years, the notice may include a range of years (e.g., 2011–2023), starting from the date of the oldest published elements and ending with the date of the newest published elements.

[ghost]

• https://softwareengineering.stackexchange.com/questions/210472/is-renewal-of-mit-license-needed-on-github-at-the-beginning-of-each-year
• 2015 - present (Microsoft VS Code)
• no year (curl)

=> If you use copyright year, you need to mention every year where a change was released (or a year range, if continuous, like 2020-2023)

[robdmoore]

It's optional to include multiple years, you can just include the first publication date, but there's also no harm in including multiple years so I accepted your suggested change.