Update license for 2024

[meili-bot]

This PR is auto-generated.

[curquiza]

bors merge

[meili-bors]

Timed out.

[curquiza]

bors merge

[norkunas]

@curquiza why not making -present to avoid updates each year? :)

[curquiza]

@curquiza why not making -present to avoid updates each year? :)

As far as I know, even if a lot of people do it, it's not allowed to do this and will make the license not "usable"

[norkunas]

@curquiza why not making -present to avoid updates each year? :)

As far as I know, even if a lot of people do it, it's not allowed to do this and will make the license not "usable"

Do you know a source where it states that it must be this way?
Because now it looks like that in the time gap until the new year appears in the code, the code is not licensed? 😁

[meili-bors]

Timed out.

[curquiza]

Sorry I used the wrong words to explain this.
To be fully transparent, the year on the license is not really important, and we can even put only a year and not a range of years. You cannot accidentally remove or invalidate your copyright by incorrectly marking your copyright.
However, putting the range of year removes any doubt. Since we are an opensource company we want to do things properly (especially because it does not take a lot of time to update them), and having a range in our license seemed a better fit. It shows new work has been done during the year on the project.
But -present is not a valid range since a YEAR is expected for the copyright. But don't worry, it would not make the code unlicensed if we do it wrongly.

[curquiza]

I merge the PR because bors seems to give up its job

[norkunas]

I merge the PR because bors seems to give up its job

Too many times bors already failed to do his artificial intelligence job