Gioele Barabucci <[email protected]> writes: > On 11/02/26 19:02, Dominique Dumont wrote: >> Since 2026 is still rather new, you may want to update the >> "debian/*" entry of the debian/copyright file of the package you >> maintain. > > Or maybe this is the right time to reconsider whether updating the > copyright year is a meaningful activity :)
I believe the answer to that depends on if you want to be in a better position to defend your copyright in a court or not. Companies and many open source developers see no point in doing that, because they essentially want their work to be widely used by everyone. People who care about free software aspects and being able to defend against someone using their work to subjugate users may value the ability to defend the copyleft properties of a license in court. Lawyers will give you different advice depending on which starting point you have for this question. My conclusion is that it makes sense for many open source projects to avoid the copyright year bump, and equally that it makes sense for many free software projects to spend time on doing the copyright year bump. The conclusion may also depend on how much OCD you apply to the problem, and the amount of appreciation for doing mechanical modifications. /Simon > https://daniel.haxx.se/blog/2023/01/08/copyright-without-years/
signature.asc
Description: PGP signature
