Conversation

Notices

1. Embed this notice
   tante (tante@tldr.nettime.org)'s status on Monday, 16-Feb-2026 01:26:30 JST tante

   Maybe we should establish a "maintenance.md" practice just like "readme.md" or "LICENSE" where you just clearly outline the amount of maintenance the project/development team are planning to put into the code base and under which conditions.
   I have seen that a few times but maybe it should be more of a standard.

   • GreenSkyOverMe (Monika) and Tim Chambers repeated this.
   • Embed this notice
     tante (tante@tldr.nettime.org)'s status on Monday, 16-Feb-2026 01:26:56 JST tante

     in reply to

     "I will not maintain this code at all. Use fully at your own risk" is valid.

     I think it's just important to make that clear.

   • Embed this notice
     Jens Bannmann (tynstar@nerdculture.de)'s status on Monday, 23-Feb-2026 05:25:38 JST Jens Bannmann

     in reply to

     @tante
     A while back I found an essay titled "Healthy expectations in open source" by @donmccurdy that proposes just such a standard:
     https://www.donmccurdy.com/2023/07/03/expectations-in-open-source/

     I found the classifications well thought out and have started to use it for my own small projects.

     This was the accompanying Fediverse post: https://fosstodon.org/@donmccurdy/110662029314944366