Tackling protocol decay and tech debt

[aschrijver]

In chat there's mention about the huge tech debt on the Fediverse, and how to ensure interop. I'd just like to highlight some docs of the Evolvability, Deployability, & Maintainability (edm) working group at the IETF, that have some guidelines and highlight forces that cause the debt/decay:

• Maintaining Robust Protocols by M. Thomson, D. Schinazi
  • Contains a section on Protocol Decay. Previous version "The Harmful Consequences of the Robustness Principle".
• RFC 9170 Long-Term Viability of Protocol Extension Mechanisms

Can be handy as input for doc guidelines, and also to discuss other specific ways to get rid of the tech debt, and help restrict scope of FediDocs initiative.

[jernst]

I'm not clear how this is "actionable". In other words, what would it take for this issue to be closed as fixed?

[aschrijver]

I posted this as follow-up to discussion on "What will be our scope and work methods?", and that leaning to the existing fediverse and decreasing tech-debt. I do not see that described yet in this repo. Until then I see this as input to "What is our purpose and goal?" and insights from these docs may find their way for guidance and practices for participating in this group.