Conversation

Notices

1. Embed this notice
   Arne Babenhauserheide (arnebab@rollenspiel.social)'s status on Monday, 09-Dec-2024 16:26:28 JST Arne Babenhauserheide

   @zimoun Thanks to you, too!

   And you’re right: it’s not possible to define what’s infrastructure from the project alone. You have to look at its impact.

   Thanks to our discussion I added that to the article now:
   https://www.draketo.de/software/volatile-infrastructure#infrastructure

   • Embed this notice
     bzg (bzg@fosstodon.org)'s status on Monday, 09-Dec-2024 17:15:06 JST bzg

     in reply to

     @ArneBab @zimoun Nice read and discussions.

     Hear hear ! https://bzg.fr/en/the-software-maintainers-pledge/

     It was really UX-oriented because my experience as an Org maintainer exposed me to end users, but any maintainer creating something that others will depend on should think hard about this.

     IMHO, the core difficulty is finding the right trade-off between maintaining an infrastructure (code/data/service) that legally provides no warranty, and the de facto expectations that users have of your code/data/service.

     Arne Babenhauserheide repeated this.
   • Embed this notice
     Arne Babenhauserheide (arnebab@rollenspiel.social)'s status on Monday, 09-Dec-2024 21:02:17 JST Arne Babenhauserheide

     in reply to

     • bzg

     @bzg This is a great wrap up link for the article!

     Though it just blew through the ad-hoc 12 page limit, so I had to do some polishing to save words and duplicate links ☺
     (such polishing tends to improve articles — thank you!)

     And it is a great fit, because the article is written in Org-Mode ☺
     https://hg.sr.ht/~arnebab/draketo/browse/software/volatile-infrastructure.org

     As aside: org-lint saved me when there was breakage to my lecture slides. Without it, I wouldn’t have been able to keep them working and would have had to move to LaTeX.
     @zimoun