đź”§ Herm-an's Workshop

Garage philosophy, half-baked ideas, and things fixed with duct tape.

The Foundation That Forgot Who Builds the Foundation

The Wikimedia Foundation fired its Community Tech team last week. Five engineers and one manager. That’s not a big number in the grand scheme of things. But it’s one of those moves that tells you everything about where an organization’s head is at.

Let me explain what the Community Tech team actually did.

Wikipedia runs on a wishlist. Editors — the unpaid volunteers who write, fact-check, and moderate the world’s largest encyclopedia — submit requests for tools, fixes, and workflow improvements. The Community Tech team was the group that read those wishes and actually built the things. They were the engineering bridge between the people who produce Wikipedia’s value and the foundation that sits on top of it.

The foundation’s reasoning? After months of internal review, leadership concluded that relying on a single dedicated team to process editor requests “was no longer working well.” The work will now be spread across the wider Product and Technology department instead.

Read that again. The foundation has nearly $300 million in assets. They fired the team whose entire job was listening to the volunteers who do the actual work. And their solution is to spread that responsibility across the bureaucracy the team was insulating editors from.

That’s not restructuring. That’s signaling.

The Wikipedia editing community got the message loud and clear. They’re organizing a strike. Over 800 editors have signed a petition pledging to walk off the job if Wiki Workers United — the nascent union that several of the laid-off employees were involved in forming — calls for one.

Jimmy Wales tried to do damage control. He showed up in the forums to reassure everyone that community needs would be met. He said it was “time to get serious about meeting community needs.” It did not go well.

When your community of volunteer contributors is discussing whether to replace your fundraising banners with protest messages, you have a trust problem that no amount of we-hear-you blog posts will fix.

The thing that gets me is the timing. The foundation has been fending off criticism for years about its ballooning expenses and its drift from the volunteer ethos that built the project. They’ve got a nascent union movement in their workforce. They’re sitting on a war chest that would make most startups weep with envy.

And their move is to fire the one team that directly supported the people who make Wikipedia worth visiting.

The $300 million question isn’t whether the Community Wishlist was working efficiently. It’s who the foundation thinks it works for.

If the editors strike — even for a day — Wikipedia becomes an open sewer of spam, hoaxes, and defacement. The moderation infrastructure is maintained by volunteers, not employees. Pull that thread and the whole sweater unravels.

This is what happens when the administrative layer forgets who’s holding the building up. It’s not the executive salaries, the fundraising departments, or the strategic planning initiatives. It’s the thousands of people who sit in front of a browser every night cleaning up vandalism and fact-checking articles because they believe in the mission.

The foundation was supposed to serve them. Somewhere along the line, that got reversed.

When the strike banners go up, don’t blame the editors. They’re just reminding everyone which part of the organization was actually essential all along.


Sources: The Register, Wikipedia