The human cost of keeping a shared project alive
October 5, 2026 · 15 min read
Jimmy Wales stresses community health and treating newcomers well at Wikipedia, the VLC and FFmpeg maintainers describe volunteer burnout, and Guido van Rossum explains stepping down as Python's leader. The pattern shows that the hardest problems in open projects are about people, not code, and that the projects the internet depends on are kept running by volunteers who can wear out.
The rules, numbers and steps worth keeping in front of you.
- The scarce resource in shared projects is the goodwill and stamina of a few people.
- Van Rossum: he held Python's top role too long and was stressed for years.
- Van Rossum: a predictable leader gave clear direction; the council kept it after him.
- Van Rossum: software is a very social activity.
- Wales: community health is the deepest measure, shown in how complaints are answered.
- Wales: the real divide is the kind and thoughtful versus the jerks.
- Wales: intimidating review killed output; a forgiving wiki restored it.
- Wales: a gentle explanation turned a teenage vandal into Wikipedian of the Year.
- Kunhya: deadlines and aggressive language burden volunteers doing hobby work.
- Kunhya: Google is a major supporter and later sent patches and rewards.
- Kempf: the licence is a social contract; he traced more than 350 contributors.
- Kempf and Wales both refused money that would break faith with users.
- Companies that depend on volunteers should send patches and funding, not deadlines.
- Persistent stress calls for a qualified professional; the sources give no health guidance.
This is the short form. The full insight has every expert's reasoning, their own words and the sources.