Who Speaks for the People Who Write Wikipedia?

Photo by visuals on Unsplash

In May the Wikimedia Foundation eliminated its Community Tech team, the small group of engineers who built tools for the volunteers who write Wikipedia. The cuts removed the Foundation’s most influential MediaWiki developer. They also removed several employees at the center of a union drive that had surfaced under the name Wiki Workers United.

Volunteers noticed. Within weeks, a solidarity petition on English Wikipedia carried more than a thousand signatures, dozens of them from administrators, people who had spent years earning the community’s trust and were now spending some of it on a labor dispute that did not directly involve them.

If the people who maintain Wikipedia’s software need a union, what about the people who write the encyclopedia? The answer turns on how much power editors actually hold, and whether they would ever use it together.

The shape of power

Editors occupy a position no union has organized before. The Foundation does not employ them, cannot fire them, and cannot function without them.

Every article and every correction comes from unpaid work, and so does every reason a reader arrives or a donor gives.

Measured that way, editors look like the most powerful labor force in the open world. A staff walkout empties an office. An editor walkout freezes the encyclopedia.

Look closer, however, and much of that power evaporates. Everything editors have ever written is licensed irrevocably under Creative Commons, so the Foundation’s existing content would survive a total collapse of goodwill.

What editors control is future work: the next article, plus the constant maintenance that keeps millions of existing ones accurate. That is real pressure, but it accumulates slowly and doesn’t land as a single blow.

What a union could hold in its own hands is more modest: it could stand visibly with the staff, and with other members.

It could run mutual aid among editors, mental health peer support, and fundraising costs when one of them dies, work no one in the movement currently coordinates.

It could keep a credible voice in the press, something that after the May layoffs assembled itself in about a week, moved the coverage, and then dispersed just as fast.

It could not just act but deter, because a Foundation that knows an organized base exists has to price that base into every decision it makes.

Unions as most people know them rest on employment: certification, bargaining, a contract enforced by law. Volunteers have access to none of it.

What volunteers' can have is the older form the Industrial Workers of the World call solidarity unionism, a voluntary association that builds power through mutual aid and collective pressure, and that asks no one’s permission to exist.

An IWW organizer who looked at the post-layoff moment offered the most useful observation in the whole debate: the solidarity activity already under way, the petition and the coordination around it, arguably meets the IWW’s own definition of a solidarity union. If that reading holds, the thing half-exists, and the founding question becomes whether to name what is already taking shape.

None of this currently has a home. The case for a union rests on the difference between power that is scattered and power that is organized.

Why the question is still open

The official route to community power has already been tried, and it failed in an instructive way. In 2024, after years of drafting, the Wikimedia Movement Charter went to ratification with a Global Council at its center, a body that would have held real authority over movement governance. Individual contributors approved the Charter by about 73 percent, the affiliate groups by about 84.

The Board of Trustees, voting last by design, declined to enact it and substituted time-limited experiments run by the Foundation itself.

The Board broke no rule. The process reserved the final word for the Board, and the Board used it. But mark the sequence: the community took the formal path built for shared governance, won everywhere it was asked to win, and then watched the one body the Charter would have constrained turn the whole thing down. The question of an independent editor union is open because the sanctioned answer was tried in good faith and closed.

The same vote carries a caution for organizers. The Charter was billed as the community’s constitutional moment, and it drew roughly 2,400 individual voters from an active population many times that size. Editors feel grievances deeply; they turn out thinly. Any plan that assumes otherwise is already in trouble.

Mandate or network

The union design decision turns on one choice. Does the body claim to speak for the community, or only for the people in it?

A representative union would hold elections and earn the right to say “editors want this” with turnout numbers behind the sentence. It even has a ready-made electorate: extended-confirmed status, the threshold of thirty days and five hundred edits that Wikipedia already enforces in software wherever disputes run hottest.

The price of a mandate runs high. It demands constant upkeep, it attracts capture, and it can fail in public. Thin turnout threatens to disprove the claim of legitimacy it rests on.

A participatory network gives the mandate up. No membership rolls, no dues; you are an editor who takes part or an editor who does not. Such a body can never say what the community thinks. In exchange it is nearly impossible to capture or split, and it moves without polling anyone first.

It also matches a line the staff union has drawn for itself. Wiki Workers United says it does not speak for the Wikimedia communities. Two organizations that each speak only for their own people make natural allies and poor targets for divide-and-rule.

Of the two, the network is the far easier place to start. It mostly exists already. It costs almost nothing if it stalls. It closes no doors, including the door to a representative body later. The opening move is small enough to look trivial: a coordinating page, an off-wiki channel reserved for labor matters, a short founding statement, one act of help delivered to one actual person.

The response worth planning for

Three Foundation reactions are plausible. It can ignore the effort and bet on entropy to dissolve it.

It can move against organizers, who, unlike employees, have no legal protection, though the reputational price makes this the least likely course.

Or it can do the shrewd thing and announce an official community council that occupies the space before an independent body does, defusing the movement without once opposing it.

Organizers should write their tests for such a council in advance. Binding authority, or an advisory voice? Members chosen independently, or appointed by the Foundation? Its own agenda and budget, or both assigned to it? The power to refuse something and make the refusal hold? Permanence, or another experiment with an expiration date?

A council that fails those tests is a pressure valve with a charter.

A union must respond to the very conditions of voluntary organising. Small volunteer organizations die every day of burnout, drift, and feuding, no malice required.

A serious version of this project plans for its own fragility. It rotates the named roles so none becomes someone’s identity. It writes down how each task is done so anyone can pick it up. And it defines failure in advance, because if a real push produces only a handful of participants, the best course is to stop.

What the moment is worth

A comparison that should worry those involved comes from open source. Maintainers of critical software hold at least as much power as Wikipedia’s editors; large parts of the digital economy run on code they give away.

Collectively, however, they have done almost nothing with it. Power left latent converts itself into nothing, and someone after all has to do the converting.

For Wikipedia’s editors the conditions are well-met, the energy is here now, named and signed, and looking for a structure. The question is: what will editors do with it?