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. On May 26, 2026, Jake Orlowitz, a former WMF staffer who founded the Wikipedia Library, published a Medium essay titled “Big Tech’s Anti-Labor Playbook Has Come for Wikipedia” calling it what it looks like: union busting. [Updated June 2026: the Foundation has since denied that the layoffs were connected to unionizing.]
The firings, one week apart
Vibber was the Foundation’s first full-time hire. She had led MediaWiki development since 2003 and served as CTO from 2005 to 2009, occupying 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 Foundation’s account
The Foundation rejects the union-busting reading. In a statement to The Register at the end of May, a spokesperson said: “The decision to disband the Community Tech team is not in any way connected to discussions about unionizing, nor have we terminated any staff for their participation in those discussions.” [Updated June 2026.] The Foundation also said the affected staff were not immediately let go: they remained employed, could apply for other internal roles, and those not placed would leave the following month with severance. As of June 20, 2026, the Foundation had not published a dedicated rebuttal; its position lives only in statements given to reporters.
Two facts complicate both sides. The cut landed under a new chief executive: Bernadette Meehan took office on January 20, 2026, succeeding Maryana Iskander, so this is the first major restructuring of her tenure rather than a continuation of long-standing policy. [Updated June 2026.] And the denial is narrow. It addresses motive, not effect. Even granting that no one was fired for organizing, the result is the same one Orlowitz describes: the staff most active in the union and the team that gave editors a say over product direction are both gone, and the burden of explaining the timing now sits with management.
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 reaching for the standard Big Tech anti-labor script, firing the people organizing a union, and drawing explicit parallels to restructuring patterns at major platform companies. Gigazine’s account of the episode characterized the moves as “union-busting tactics typical of large IT companies,” the framing the firings invite.
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 undisclosed terms invite assumptions of windfall money, so it is worth grounding the figure. Wikimedia Enterprise is still a small line item. The Foundation’s FY2024-2025 financial report put Enterprise revenue at about $8.3 million, up 148 percent year over year, roughly 4 percent of total revenue. [Updated June 2026.] Against the Foundation’s $208.6 million in total FY2024-2025 revenue, the AI licensing program is a fast-growing but minor contributor, not the budget. That cuts against the crude story that licensing cash bought the layoffs, and it sharpens the structural one: the dispute is about institutional posture toward contributors and AI buyers, not about a single revenue line large enough to drive a restructuring on its own.
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.
Why the AI deals exist at all: scrapers were already running up the bill
The licensing program did not appear in a vacuum. AI companies were taking the data whether or not anyone paid, and the cost showed up in Wikimedia’s own infrastructure. In an April 2025 engineering post, the Foundation reported that bandwidth for multimedia downloads had risen about 50 percent since January 2024, driven mostly by automated scrapers feeding AI training pipelines rather than by human readers. [Updated June 2026.] The skew was sharp: bots accounted for roughly 65 percent of the most expensive “core datacenter” traffic while generating only about 35 percent of pageviews, because crawlers hit obscure pages that human-optimized caching never warms. The Foundation set a goal to cut scraper traffic by 20 percent in request rate and 30 percent in bandwidth.
That is the backdrop the Enterprise deals answer. A paid, rate-limited API that serves machine clients a clean dump is cheaper to run than absorbing an open-ended crawl, and it converts a cost center into a revenue line. The same dynamic is playing out across the web, where infrastructure providers now meter and price crawler access rather than eat it: whether the bot-traffic surge is even being measured honestly is its own dispute, since the classifiers that flag “bots” also flag privacy browsers. For Wikimedia the deals are defensible engineering. The problem Orlowitz raises is what happens to the humans inside the institution while it optimizes its relationship with the machines outside it.
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 convergence shows up most clearly in how institutions route contributor output to AI buyers. The pattern is rarely a lawsuit or a loud announcement: it is a default setting. When Atlassian switched on AI-training data collection by default for Jira and Confluence, the content users had created for their own work started flowing into model training unless they found the opt-out. Wikimedia’s posture is more defensible, since its content is already openly licensed and the Enterprise deals are negotiated rather than silent, but the structural move is the same: the entity that hosts the contributors’ work decides how that work is monetized for AI, and the contributors learn the terms after the fact. The difference Orlowitz presses is governance. A for-profit can set defaults unilaterally and call it a product decision. A nonprofit that exists to steward a commons is supposed to answer to the people who build it.
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. Within roughly a week it had drawn hundreds of signatures, including dozens of administrators, with the text affirming a willingness to escalate “up to and including staging an editorial strike.” [Updated June 2026.] Reporting in the weeks after the cuts described editors openly discussing harder measures: pausing anti-vandalism work, replacing the donation banners that fund the Foundation, and in some cases resigning administrator tools in protest. Those are pressure tactics, not yet actions, but they target exactly the volunteer labor the Foundation cannot replace with a hire.
The Foundation has denied that the layoffs were retaliation for organizing, as covered above, but it has not, as of June 20, 2026, addressed the union’s specific demands or the broader charge that it is compressing community control. [Updated June 2026.] No formal union recognition, NLRB petition, or staff vote had been reported as of that date; Wiki Workers United has said it is pursuing US legal formation first.
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?
Wiki Workers United lists several focus areas predating the May firings. Among them: management transparency to staff and community, effective staff input on annual plans before decisions are finalized, consistent hiring and promotion practices, the ability to safely express dissent, and mental health support for employees handling community-facing work. [Updated June 2026: the group’s published list runs to roughly seven items, including pay and benefits equity; the demands above are a subset.] The Foundation has not publicly addressed them point by point.
What did Wales mean by citing Grokipedia?
Grokipedia, xAI’s AI-generated encyclopedia, launched in October 2025 pulling from uncurated web sources, and it quickly surfaced inaccurate and conspiratorial content, some of it forked from Wikipedia itself. [Updated June 2026.] Wales was unbothered by it as a competitor, calling it a “cartoon imitation” of Wikipedia and arguing that current language models are not good enough to write quality reference material on their own. He used it to make the case 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. That overlap puts Wikipedia in the same bind facing maintainers across open source, where the unpaid work that feeds AI systems is straining the people who do it faster than institutions are adjusting, a tension visible in the debate over whether AI-generated pull requests are wearing down open-source projects.
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.