Use 'present' for end year in COPYRIGHT.txt

We may not need a copyright lawyer.

https://hynek.me/til/copyright-years/

I learned that copyright statements need only the year of the first publication and no lawyer that I asked contradicted.

[...]

if it’s good enough for Google’s, Microsoft’s, and Netflix’s lawyers, it’s good enough for me.

That’d be my first choice, if it’s legit. Very happy to remove the end year. Thanks for the link!

I can't remember why we even need this in addition to LICENSE.txt, but if we really do, then removing the end year would be great.

Given the blog post in #2, +1 to option A. It's just busy work to update it every year, as evidenced here we have forgotten anyway, and so if we can remove the end year entirely we will be more accurate than we are at the moment.

I also checked Symfony which just uses "2004-present".

Sweet, sounds good. MR coming coon.

Adding parent

Removing related, sorry for the noise.

I’m in favor of backporting this non-code change very far, if possible, since it only makes things more accurate and there’s 0 risk of disruption.

Change seems small and makes sense.

Moving to RTBC but for optionA do we need Needs Lawyer review tag?

I think the blog post covers that. The lawyers of very many large companies think we don’t need an end year. That’s good enough, it seems.

Adding credit and tweaking the title

I did some reading of the links provided in #2 as well as FSF and CC sites. I didn't find anything that supported a specific end date.

Committed to 11.x. I also committed to 10.2.x so that the legal things are up to date. This is certainly not a disruptive change.

Thanks!

Thanks!

Any thoughts on #11? Any objection to backporting this to even older branches? Even if it's not going to be in a tagged release, at least it'll be more accurate in Git for posterity? Moving to 10.1.x, but I'm in favor of even back to 10.0.x and possibly 9.5.x?

Not sure the policy for unsupported branches. But if a tagged release won’t be made does it help?

I'm just thinking for folks doing Git archeology, whatever. To have it right in Git seems better than not, and there's 0 chance for disruption or breaking anything.

Backported to 10.1.x as we still support that branch for security patches. Past that all branches are end of life, and there is no point committing anything more to them.

Automatically closed - issue fixed for 2 weeks with no activity.