chore: License year update

[kehiy]

Description

just update 2020 to 2023.

[codecov]

Codecov Report

Merging #570 (d6d2579) into main (2dd2f3b) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #570   +/-   ##
=======================================
  Coverage   83.50%   83.50%           
=======================================
  Files         154      154           
  Lines        7249     7249           
=======================================
  Hits         6053     6053           
  Misses        916      916           
  Partials      280      280           

[amirvalhalla]

@kehiy thanks

[b00f]

@kehiy @amirvalhalla

I am going to revert this change. Because, I checked some MIT projects like NodeJS, Angular, curl. Also asked ChatGPT:

In MIT license, what should be the year?

In the MIT License, the year should be the year that the work was published or created. The license is typically included when the software is published, so the year would be when the software was first made available to the public.

What we know that the year should be the year that the project is published. Clearly here is 2020.

Some projects follow this pattern: <Publish year> - <This year>: like 2000 - 2023. I found this post on curl project. However, following this style would also require us to update the license every year, which could be inconvenient.

[amirvalhalla]

@b00f thanks.

[kehiy]

@kehiy @amirvalhalla

I am going to revert this change. Because, I checked some MIT projects like NodeJS, Angular, curl. Also asked ChatGPT:

In MIT license, what should be the year?
In the MIT License, the year should be the year that the work was published or created. The license is typically included when the software is published, so the year would be when the software was first made available to the public.

What we know that the year should be the year that the project is published. Clearly here is 2020.

Some projects follow this pattern: <Publish year> - <This year>: like 2000 - 2023. I found this post on curl project. However, following this style would also require us to update the license every year, which could be inconvenient.

sure, we should follow the best way.