Conversation

Notices

1. Ross Burton (ross@hachyderm.io)'s status on Tuesday, 03-Jan-2023 03:07:59 JST Ross Burton

   PSA for any developers that are about to touch every file in their code to add “2023” to the copyright statements: don’t. https://hynek.me/til/copyright-years/

   • Adrian Cochrane (alcinnz@floss.social)'s status on Tuesday, 03-Jan-2023 03:07:58 JST Adrian Cochrane

     in reply to

     • James Henstridge

     @jamesh @ross That's what I tend to do... Listing all modification years!

   • James Henstridge (jamesh@aus.social)'s status on Tuesday, 03-Jan-2023 03:08:06 JST James Henstridge

     in reply to

     @ross If people are still likely to receive the software in tarballs rather than a git clone, it may still be worth updating copyright notices, but only when copyrightable changes have been made to the file (since copyright on those new changes would run from when they were committed).

     Changing the copyright date without any other creative changes doesn't make sense though: you haven't made any change that would push out when the contents becomes public domain.