6 ms·
This might be specific to software, based on what the GNU project has to say about it[0], I think you should do it like this: Copyright 2014, 2016, 2017-2020
by 1f60c 6y ago
This might be specific to software, based on what the GNU project has to say about it[0], I think you should do it like this:
Copyright 2014, 2016, 2017-2020
(Meaning the work was completed in 2014, a change was made to it in 2016 and every year from 2017 to 2020 was a "copyrightable year".)
[0]: https://www.gnu.org/licenses/gpl-howto.html#:~:text=The%20copyright%20notice https://www.gnu.org/licenses/gpl-howto.html#:~:text=The%20co...
- truetaurus 6y agoI feel there is a little product idea in this haha. Like copyright generator based on git pushes/deployments.
- bavell 6y agoSounds much more like a feature, not a whole product IMO.
- finnthehuman 6y agoThat's a hard sale to make around source control. I've written that script a half dozen times over the years, it's a few hours of work and the vast majority of the effort is in tailoring it to the particulars of the project. Maybe it'd work as a plugin to a content management system.
- Aeolun 6y agoCan just put [first publish]-[now] and save yourself the trouble.
- sameerds 6y agoThat depends on whether each year until [now] had "copyrightable" improvements. For large open source projects, the copyright notice is placed on each file separately, and it is common to see some files not changing (or changing negligibly) over long periods of time.
- postnihilism 6y agoI know someone who submits PRs to large open source projects at the beginning of the year to update forgotten copyright values in their codebases in order to get listed as a contributor on github. It's a bit tongue in cheek but on first glance their open source contributions look pretty impressive...