3 ms·
Surely it’s straightforward to use templating and always pull the year from a date library. No changes to source control needed. Edit: as the article mentions
by rocketbop 4y ago
Surely it’s straightforward to use templating and always pull the year from a date library. No changes to source control needed.
Edit: as the article mentions open source documentation it’s possible the repo itself is what needs the year, and there’s no way around hardcoding it in the included licence.
- JohnFen 4y agoThat's how I've always done it. I'll probably continue to include copyright notices and years regardless of legal necessity, but I've never lost sleep over it or put a lot of effort into it. It just seems like a "does no harm, and may clarify things" sort of deal. This is pretty much the advice of my attorney. "It's not legally required, but I can imagine situations where it could be useful anyway. If it doesn't cost you anything, why not include it?"