Public
- Public
- Network
- Groups
- Featured
- Popular
- People

Conversation

Notices

Embed this notice
nixCraft 🐧 (nixcraft@mastodon.social)'s status on Wednesday, 01-Jan-2025 13:27:28 JST nixCraft 🐧

First commit of the year:
git commit -m "chore: update copyright year to 2025"
😮💨 that is a lot of work. let us have some coffee break.

In conversation about 2 months ago from mastodon.social permalink
- Embed this notice
  Max Mehl (mxmehl@mastodon.social)'s status on Wednesday, 01-Jan-2025 15:28:01 JST Max Mehl
  in reply to
  
  @nixCraft Bumping the copyright year is useless at best. Better stop it and save everyone the time and energy: https://matija.suklje.name/how-and-why-to-properly-write-copyright-statements-in-your-code#why-not-bump-the-year-on-change
  In conversation about 2 months ago permalink
  Attachments
  1. No result found on File_thumbnail lookup.
    
    How and why to properly write copyright statements in your code - … and probably more than what you ever wanted to know about them
    
    from Matija Šuklje
    
    Copyright is automatic, but for compliance and collaboration purposes you should still use copyright statements of good quality. This post explains some copyright myths and inertia, as well as spells out how (and why) to write a copyright/license notice of great quality.

Feeds