You step away from a project for ten years. You come back, hoping things have improved, only to find the exact same suffocating bureaucracy running the exact same playbook. You’ve probably noticed this pattern in tech: the people who build the tools rarely understand the people who use them. But when the tool is Wikipedia, the stakes are a global commons of knowledge.
Right now, the Wikimedia Foundation (WMF) is pushing “Abstract Wikipedia” against fierce, vocal community opposition. To the outside world, it looks like standard innovation friction. But if you’ve ever contributed to an open-source project, you know exactly what this is. A volunteer community is a garden. The Wikimedia Foundation is treating it like a factory floor.
One returning volunteer nailed it perfectly in a recent Request for Comment. After a decade away, they saw the same cycle repeating: the WMF implementing something the contributor community explicitly does not want, just to pad the CVs of managers and developers. LiquidThreads, Flow, and now Abstract Wikipedia. It’s a graveyard of top-down mandates.
Here is the twist most observers miss. This isn’t a simple “management versus volunteers” conflict. The real issue is structural. The WMF’s incentive system rewards shipping shiny new projects to justify budgets and secure grants. It does not reward maintaining the organic, consensus-driven evolution of the community. When a foundation’s incentive structure rewards shipping shiny new projects over maintaining existing trust, it stops being a steward and becomes a parasite.
By forcing projects that no one asked for, the WMF isn’t just ignoring its volunteers—it is actively competing against them. They are draining resources, time, and morale from the people who actually sustain the platform. Every hour spent fighting a bloated, abstract new system is an hour stolen from actual knowledge curation.
If you contribute to any collaborative digital space, watch this space closely. Governance misalignment doesn’t just kill momentum; it kills trust. And once the volunteers realize the foundation views them as an obstacle rather than the engine, the magic evaporates. You can’t code your way out of a trust deficit. You can only earn your way back.
FAQ
Q: Isn't innovation always met with resistance from old-timers?
A: Yes, but good innovation solves actual user problems. Abstract Wikipedia solves a CV-padding problem for WMF managers, not a curation problem for editors.
Q: What does this mean for Wikipedia's future?
A: Expect a continued decline in volunteer retention. When a platform's governing body treats its contributors as friction, the contributors eventually walk away.
Q: Is the WMF actively trying to kill volunteer editing?
A: Not intentionally, but effectively. Their structural incentives make replacing human consensus with automated systems a better career move than supporting human editors.