ross,
@ross@rossabaker.com avatar

I'm starting to see a wave of single-PR users on GitHub submitting updates to copyright dates. There is nothing obviously malicious about them, though they have a metallic whiff of bot. Is there any reason to avoid these?

#GitHub

vascorsd,
@vascorsd@mastodon.social avatar

@ross about copyright years updates, the most exaustive explanation that answered my questions about it and that makes sense for me is all described here - https://matija.suklje.name/how-and-why-to-properly-write-copyright-statements-in-your-code

Tldr: don't update the dates after the initial creation, it's useless.

There's also the school of thought about removing the dates altogether, but this link gives good enough reasons why it matters.

ross,
@ross@rossabaker.com avatar

@vascorsd Many tools -- like sbt-header -- get cranky if the year is not consistent across the project. But I've started putting the project start year there and leaving it alone.

Also: I love SPDX.

vascorsd,
@vascorsd@mastodon.social avatar

@ross yeah, I've seen diffs in scala stuff out there and seen than sbt header plugin thing, but fortunately I never used it personally nor professional.

Usually for work it's all internal stuff so there's not really enforcement around that 😅.

Spdx is the best 😌. I'm really liking the short name for the license, and not having to add huge comments with boilerplate text.

I've been trying / experimenting with using reuse tool to manage these things and it's kinda nice too.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • github
  • Durango
  • DreamBathrooms
  • InstantRegret
  • magazineikmin
  • osvaldo12
  • everett
  • Youngstown
  • khanakhh
  • slotface
  • rosin
  • thenastyranch
  • ngwrru68w68
  • kavyap
  • normalnudes
  • megavids
  • ethstaker
  • GTA5RPClips
  • modclub
  • cisconetworking
  • mdbf
  • tacticalgear
  • cubers
  • provamag3
  • tester
  • anitta
  • Leos
  • JUstTest
  • lostlight
  • All magazines