Open Source Maintainers Are Quitting. Here's Why

The open source burnout wave is real and it is accelerating. In 2026 alone, the leaders of Jellyfin, Pluto.jl, and Arch Linux all stepped down, and the nvim-treesitter project was archived after its maintainer was driven away by an entitled user. These are not isolated incidents; they are the visible surface of a systemic problem (vlad.website, 2026).

Joshua Boniface, who resigned as Jellyfin project leader on July 19, 2026, put it plainly: the types of people who are really good at starting projects are not always the people who are good at guiding a large, stable one. He said the burnout was real and had been brewing for at least two years, slowly building as more and more things piled up (boniface.me, 2026).

Why are maintainers quitting?

The reasons cluster around a few themes. The responsibility of a lead maintainer is overwhelming: community, marketing, engineering, outreach, design, finances, infrastructure, privacy, and security. Financing open source is so hard that maintainers cannot get people to stay. And the ratio of users to contributors is exhausting: hundreds of people benefit, a handful report bugs, and almost nobody opens a pull request (blog.fokuspunk.de, 2026).

The entitled-user problem

The nvim-treesitter case is the clearest example. On April 2, 2026, a user was upset that his requested changes were not being made and angrily told the maintainer to "go switch to something that doesn't require interacting with people." The maintainer, already overwhelmed, archived the repository the next day. The banner now reads: "This repository was archived by the owner on Apr 3, 2026. It is now read-only." (vlad.website, 2026).

We've driven away another person whose contributions we should cherish. Explaining these situations by referring to the faults of any individual person would be a mistake, because the problem is systemic.

— vlad.website

The AI factor

A technological change as fundamental as LLMs is something nearly everyone has strong opinions about, and moderating those discussions is exhausting. Boniface said the LLM conflicts were "another straw on the proverbial camel's back" rather than the main reason for his departure. The Pluto maintainer noted that "most open source work is just communicating via emails and bug reports, with people I never met. Or with robots, even worse!" (boniface.me, 2026).

What can users do?

The best thing you can do is contribute. Maintainers are not asking for perfect code or senior engineering; even small things help. A clear bug report with reproduction steps, a PR that fixes something even if rough, documentation improvements, and helping answer questions in the issue tracker all matter. Open source works best when it is actually collaborative (blog.fokuspunk.de, 2026).

• File a clear bug report with reproduction steps
• Open a PR that fixes something, even if rough
• Improve documentation
• Help answer questions in the issue tracker
• Be patient and kind with maintainers who give their work away free

The bigger picture

Users of open source do not have enough educational resources to understand how to healthily and sustainably engage with the maintainers they rely on. And maintainers do not have the know-how or direct support to care for their mental health in the middle of a deluge of issues and PRs. Miranda Heath's report on burnout in open source documents this, and the Software Stewardship Lab is working on a follow-up study of maintainer mental health (vlad.website, 2026).

Sources and further reading

• Joshua Boniface — On My Resignation as Jellyfin Project Leader
• vlad.website — Open Source Burnout Claims Another Project
• Bastian Machek — Taking a break from open source
• The Great Self-Hosting Boom: Why Everyone Is DIYing
• The npm Registry Breaks: What We Learned From the Outage
• PostgreSQL 19 Ships: The AI Database Era Begins