dwardoric, 1 month ago

@vascorsd Yes, but hard to avoid if plugins for auto updating headers are used.

vascorsd, 1 month ago

@dwardoric the thing is, there should not exist any such kind of updating plugins. It's unneeded. The only thing needed is to check if there's a notice and if it's valid. That's all.

The tool to use to check and keep copyright in files in check is this one https://reuse.software/

There's already many projects using it out there and it's very nice and simple.

vascorsd, 1 month ago

@dwardoric as for best explanation I have around which cleared a lot of things for me since it's so well written is https://liferay.dev/blogs/-/blogs/how-and-why-to-properly-write-copyright-statements-in-your-code#why-keep-the-year

vascorsd, 1 month ago

@dwardoric example software I have around that uses it https://github.com/slint-ui/slint/

dwardoric, 1 month ago

@vascorsd Thanks for the pointer, an interesting read.

vascorsd, 1 month ago

@dwardoric no prob. The toot was bait 🪤.

I obviously also didn't know all these things and always was confused about the copyright years being updated, so I wondered and recently found the reuse tool.

I learned from it, so I'm sharing the bits that I'm aware 😊.

Open source legal stuff is always a deep hole to dig into 😅