According to a study by Tidelift and Sonar, 58% of open source maintainers have either abandoned their projects or considered doing so – 22% have left, 36% have given it some thought.
Another study from Heise records that over three quarters of maintainers receive no financial compensation, and over 48% feel their contributions are undervalued .
Causes of burnout
- Excessive workload and emotional stress
Many remain solely responsible for the project – from development and documentation to community outreach and vulnerability fixes.
- Overload of unresolved issues
The sheer number of unanswered issues and PRs turns work into endless “weeding the wagon”.
- User expectations and pressure
Users are more likely to demand support “right now” – even though the software is free.
- No reliable income
Only 12-13% of maintainers are able to live off their work on open source.
- Loss of interest and shifting priorities
51% of Tidelift respondents admitted that they simply stopped feeling interested in the project.
- Changes in personal life (work, family) inevitably put hobby development on the back burner.
Consequences
- Sudden withdrawal of support. The maintainer may disappear without leaving a successor.
- Vulnerability of projects. It is during burnout periods that malicious changes are often introduced.
- Loss of quality and speed of fixes. PRs remain unresolved, bugs remain unfixed, and documentation remains irrelevant.
How maintainers cope: tips from experience
- Set boundaries; -Regular breaks;
- Engaging the community. It is important to motivate external contributors to help: triage, documentation, tests – everything plays a role.
- Financial support. Even a small payment (Patreon, donations) can have a significant effect.
What companies and the community can do
- Funding through grants, sponsorship – companies that depend on projects should support them.
- A well-known example: FFmpeg and Microsoft, when a formal request was followed only by a one-time payment – and dissatisfaction.
- Simplification of the maintainer’s work – automerge PR, documentation, CI/CD, triage systems.
- Supportive environment – mentoring, peer-review, mental support.
- Succession plans – train replacements in advance, assign roles, create support call centers.
Conclusion
Maintainer burnout is not just a problem for individual enthusiasts. It is a threat to the stability of the entire open source ecosystem on which modern digital infrastructure depends.
Solutions must be comprehensive:
- Personal: learning to set limits, give yourself a break, ask for help.
- Organizational: provide funding, support structure, fair social interaction.
- Community: respect, gratitude, and willingness to help.
As long as projects depend on the efforts of a few volunteers without support, Open Source remains a fragile construct vulnerable to human error.
