How to manage maintainer burnout and project sustainability
sustainable maintenance practices, triaging vs fixing, closing issues defensively, bus factor, onboarding new maintainers, GitHub Sponsors and Open Collective, project archiving
Sustainability Is a Technical Problem
The leading cause of open source project death is maintainer burnout. Planning for sustainability from the start is as important as architecture decisions.
Triage Over Fix
Not every issue needs to be fixed by you. Close issues that are out of scope with a clear explanation. Use labels to communicate priority. Labels like wontfix, needs-more-info, and good-first-issue are management tools, not just tags.
Reducing Bus Factor
If you are the only person who can release the project or review security patches, the project depends entirely on your availability. Document your release process. Add a co-maintainer. Grant merge access to trusted contributors before you need to.
Funding Models
GitHub Sponsors -- Individual or corporate sponsorship directly through GitHub. Low overhead. Open Collective -- Fiscal host for transparent funding. Used by many large open source orgs. Tidelift -- Enterprise subscription model for open source maintenance.
Archiving Gracefully
If you need to step away, archive the repo rather than abandoning it. Set the repository to archived mode in Settings -- it becomes read-only, PRs and issues are closed, and a banner tells visitors the project is no longer maintained. This is better than silence.