chore: Update the copyright notice

[honzajavorek]

You may want to update this number unless the project is inactive. It's a small thing, but AFAIK (IANAL tho), the year marks a start of the period after which the work becomes public domain.

[B4nan]

Last time we were discussing this, someone (was it @jirimoravcik? maybe it was even in a different company 🙃) said it's actually a good thing to have the old number there, as it represents when the project started.

Personally, I never update this number, and I recall some frameworks used to do that and stopped as well, as it only adds clutter without any value.

So if we want to change this, I would be rather in favor of removing the number completely (or keeping the old value which represents the start). Checked a few larger projects and none of them had the year in their license file.

Thoughts @jancurn @mtrunkat?

[jancurn]

This is really a legal question cc @mnmkng

[honzajavorek]

as it represents when the project started

I've also seen things like Copyright 2018-2024 Apify Technologies s.r.o. And I'm sorry for summoning this bikeshedding demon upon you! I'm going through the tutorials and Crawlee claims to be open source, forever, so being a curious person, in light of recent re-licensing of Redis etc., I've checked what kind of license you're using. Then I spotted the number, recalled my good old Oracle times (spent way too much time with licenses) and couldn't restrain myself to this little update.

[B4nan]

From what I read, it should note the start of the copyright notice, the license itself does not require a year at all.

https://opensource.stackexchange.com/questions/5778/why-do-licenses-such-as-the-mit-license-specify-a-single-year

And, on a different page, I found that copyright is valid till the author dies (plus a few years), so this is not really important nowadays (but pretty much everybody starts those answers with "if I understood this right..." 🙃).