A public participation channel looks free until somebody has to answer it.
Issue trackers, forums, support queues, pull requests, mailing lists, moderation inboxes, and community chat rooms all create obligations for the people maintaining them.
The software may be open twenty-four hours a day.
The volunteer is not.
GitHub’s own maintainer guidance describes the maintenance load plainly: maintainers write code, respond to issues, review pull requests, moderate discussions, document behavior, and help contributors. GitHub has repeatedly framed burnout as a major risk to open-source sustainability. See Elevating open source contributors to open source maintainers and its 2026 discussion of maintainer burden.
Open doors generate work
A public issue tracker allows anyone to report a bug.
That is useful.
It also allows duplicate reports, vague reports, demands disguised as bug reports, abandoned pull requests, support questions posted in the wrong place, and arguments over decisions that were already made three years ago.
As a project becomes more popular, incoming attention can grow faster than the maintainer team.
Open Source Guides explicitly advises maintainers that it is acceptable to pause, take breaks, set boundaries, and protect the conditions that make continued maintenance possible. See Maintaining Balance for Open Source Maintainers and Best Practices for Maintainers.
That advice exists because the alternative is not theoretical.
Maintainers do burn out and leave.
Closing a channel can be maintenance
When volunteers cannot sustain an open participation surface, they may reduce it.
A project can make a forum read-only. Restrict new issues to bug reports. Close feature requests. Require a template. Move support elsewhere. Limit contributor access. Archive an abandoned repository. Or simply state that the maintainers no longer have the capacity to answer general questions.
Those actions reduce visible public participation.
They may also be what keeps the underlying project alive.
The distinction matters.
A closed issue tracker does not necessarily mean development stopped. A read-only forum does not prove the community vanished. The people involved may have shifted to a smaller contributor group, private coordination, scheduled releases, or a deliberately narrower support model.
Public infrastructure needs human fuel
Dead Internet Theory often focuses on missing users.
Sometimes the missing component is the unpaid person who used to sweep the floor.
Public participation systems create enormous value because strangers can walk in and contribute. They also externalize work onto whoever has to review what those strangers bring through the door.
When that labor becomes unsustainable, the door may close before the project does.
The public channel disappeared.
The volunteer was trying not to.