Sustainable operating model

Problem

The extension is maintained through ad-hoc heroics: one or two engineers handle all support questions, triage is informal, release timing is opportunistic, and there is no on-call rotation or escalation path. This works at small scale but becomes unsustainable as the user base grows post-launch. Without a documented operating model covering support channels, triage cadence, release process, on-call responsibilities, and contributor onboarding, the extension will either burn out its maintainers or suffer from neglect as attention shifts to new features. A v1.0 product needs operational maturity, not just code maturity.

Context

Possible Solutions

Plan

Implementation Progress

Review Feedback

• Review cleared