In mid-May 2026, the Wikimedia Foundation fired Brooke Vibber, its first full-time employee and former CTO. One week later, it dissolved the six-person Community Technical Team. Vibber and many of the team’s engineers were union organizers. Jake Orlowitz, a former WMF staffer who founded the Wikipedia Library, published a Medium essay in May 2026 calling it what it looks like: union busting.
The firings, one week apart
Vibber was the Foundation’s first full-time hire. As CTO from 2005 to 2009, and as the lead developer of MediaWiki, Vibber occupied a role the Foundation itself described as “one of the very few people in the world who have a deep understanding of the system’s technical foundations,” according to Gigazine’s summary of the episode. That description appeared in Foundation communications before the firing; it was not walked back afterward.
Seven days later, the Foundation dissolved its Community Technical Team: five engineers and one manager, gone in a single cut. The team’s job was to take volunteer editor requests submitted through the Community Wishlist and turn them into shipped product changes. Orlowitz described it as “effectively the only project where the volunteer community managed the product.” Dissolving it removes the primary channel through which editors could direct Foundation engineering resources toward their own priorities.
Vibber’s departure message was blunt. “Every worker has the right to have their voice heard in how the workplace is run, and every workplace needs a union,” Vibber wrote, calling on all WMF employees to join the unionization effort. Vibber also stated an intention to continue as a volunteer and develop the open-source portion of MediaWiki, which is a commitment that will be tested the next time a production outage requires institutional knowledge that no longer exists on staff.
The critic
Orlowitz is not a random agitator. He joined the Wikimedia Foundation staff in 2014 and founded the Wikipedia Library, which partnered with JSTOR, Oxford University Press, and Elsevier to give editors access to paywalled reference material. He also built The Wikipedia Adventure, an onboarding game for new editors. His political-theory background (Wesleyan) shows in the way he frames the dispute: not as a personnel grievance but as a structural failure of institutional governance.
His argument is that the Wikimedia Foundation has been making top-down decisions and deploying what he describes as “union-busting tactics typical of large IT companies,” drawing explicit parallels to restructuring patterns at major platform companies.
The comparison is pointed because it is accurate at the level of tactics. Firing the people who both understand legacy systems and advocate for worker governance is a well-documented pattern in platform-company restructuring. The difference is that those companies sell ads and cloud contracts. The Wikimedia Foundation runs on small-donor fundraising banners and, increasingly, AI licensing revenue.
The AI licensing backdrop
In January 2026, the Wikimedia Foundation signed AI training deals with Amazon, Microsoft, Meta, Perplexity, and Mistral AI through its Enterprise program, which provides high-volume, high-speed access to over 65 million articles. Google had signed a similar deal in 2022. Financial terms were not disclosed.
Jimmy Wales acknowledged the tension directly: “They’re not donating in order to subsidize these huge AI companies.” He supported the deals on quality grounds, telling the AP he was “very happy personally that AI models are training on Wikipedia data because it’s human curated.”
The deals are not the cause of the firings. Orlowitz does not present direct evidence that licensing revenue drove the dismissals. But the timing is hard to ignore: the Foundation is collecting undisclosed sums from five of the largest AI companies on earth, while simultaneously eliminating the team that gave volunteer editors their only lever over product direction, and firing the CTO-era engineer who was organizing a union. Whether or not there is a causal line between the revenue and the layoffs, the optics are the same structural pattern Orlowitz describes: institutional monetization compresses contributor agency.
The structural problem: the Wishlist was the last community-managed product
The Community Technical Team was not a support function. It was the only Foundation engineering group where the volunteer community set priorities through a structured process. Editors submitted requests to the Community Wishlist. The team evaluated, prioritized, and shipped them. Orlowitz’s description of it as “the only project where the volunteer community managed the product” is the kind of claim that is either true or trivially falsifiable, and no source contradicts it.
Dissolving the team does not just eliminate six jobs. It eliminates the mechanism by which the people who produce Wikipedia’s content, without pay, could direct the Foundation’s technical resources. The editors write the articles. The Foundation collects the donations and, now, the licensing fees. The Wishlist was the one channel where editorial labor translated into institutional response. That channel is gone.
This is the same dynamic that Ford et al. (2024) identified in their research manifesto on Wikimedia as public knowledge infrastructure: AI tools have made Wikimedia content foundational to circulating knowledge, raising questions about contributor agency and the outcomes of their unpaid labor. The manifesto framed this as an emerging research question. The firings are an empirical data point.
The nonprofit-platform convergence
Orlowitz’s core claim is that the Wikimedia Foundation’s 20-year messaging, “we are different from other technology companies,” is being tested by its behavior.
The fact that baseline workplace governance requires a union campaign to advance inside a donate-funded nonprofit is itself the signal Orlowitz is pointing at.
The second-order risk is specific to Wikipedia’s production model. For-profit platforms that degrade worker conditions face churn, quality decline, and eventual competitive pressure. The workers leave. For Wikipedia, the workers are unpaid volunteers who contribute because they believe in the project’s mission. If the institution that administers that mission loses their trust, the contributors do not leave for a competitor. They stop contributing. The commons degrades. The AI companies that just paid for access to a curated knowledge base find that the curation is deteriorating, because the institution that was supposed to support the curators chose to eliminate the one team that listened to them.
What happens now
Wikipedia editors have created a solidarity page (“Wikipedia:Wiki Workers United solidarity”) and started a petition supporting the WMF labor union. The Foundation has not, as of this writing, publicly responded to the union-busting characterization.
The structural question is not whether the Foundation had the legal right to restructure. Organizations restructure. The question is whether a nonprofit whose sole asset is the unpaid labor of roughly 277,000 active volunteers can afford to treat its staff the way for-profit platforms treat theirs, and whether the Enterprise revenue stream creates the same institutional incentives that degrade contributor trust at every other platform company that has walked this path. Orlowitz’s argument is that the answer is already visible in the pattern. The burden of proof has shifted.
Frequently Asked Questions
What specific changes is the WMF staff union demanding?
Five demands were formalized before the May firings: management transparency to staff and community, staff input on annual plans before finalization, consistent hiring and promotion practices, the right to challenge safety decisions, and mental health support for employees handling community-facing work. None have been publicly addressed by the Foundation.
What did Wales mean by citing Grokipedia as a cautionary example?
Grok’s encyclopedia feature pulled from uncurated web sources and quickly surfaced inaccurate and conspiratorial content. Wales used it to argue that AI models require human-curated training data, which is exactly what the Enterprise licensing deals sell access to. The structural problem is that the Foundation is monetizing curation while simultaneously removing the team that let curators direct technical improvements to the platform producing that curation.
Are the fired employees also Wikipedia volunteers?
Vibber stated an intention to keep contributing as a volunteer and to continue developing the open-source portion of MediaWiki. The Community Technical Team’s engineers occupied a similar dual role: their paid work involved implementing volunteer requests, and several were active editors. The dispute is nominally about staff conditions, but the people affected are also contributors to the commons the Foundation administers.
What does Orlowitz think the Foundation should do instead?
Orlowitz argues that a competent CEO would welcome the union and sign generous contracts now, specifically to prepare for ‘difficult decisions in the coming age of AI.’ His position is that AI revenue pressure will force harder tradeoffs between mission and monetization, and that a unionized workforce with formal bargaining power is a structural asset for navigating those tradeoffs rather than an obstacle to be neutralized.