The Document Foundation just detonated a bomb inside the open-source world, and the shrapnel is still flying.
On April 5, 2026, the nonprofit organization that stewards LibreOffice — the free office suite used by hundreds of millions worldwide — published a blog post titled “Let’s Put an End to the Speculation” on its official website. The post, written on behalf of the Board of Directors, was meant to quell a firestorm of rumors, accusations, and anxiety that had engulfed the LibreOffice community for weeks. It didn’t. If anything, it poured gasoline on a blaze that now threatens to split one of the most consequential open-source projects in history.
The crisis centers on something that sounds bureaucratic but is anything but: the expulsion of several longtime contributors, including core engineers who wrote large portions of the LibreOffice codebase, from The Document Foundation’s membership rolls. These aren’t casual volunteers. They are people who, in many cases, have spent more than a decade building the software from its bones. And now they’ve been told they’re no longer welcome in the organization that governs it.
As WebProNews reported in its earlier coverage, the expelled members include engineers affiliated with Allotropia and Collabora, two of the most prolific corporate contributors to LibreOffice development. These companies employ developers who handle a staggering share of the project’s actual code commits — bug fixes, feature development, format compatibility improvements, the daily grind that keeps a complex office suite functional and competitive. Removing their people from TDF’s membership doesn’t strip them of the right to contribute code under the open-source license. But it does strip them of any say in how the project is governed, how funds are allocated, and what strategic direction LibreOffice takes.
That distinction matters enormously.
The Document Foundation’s April 5 blog post attempted to frame the expulsions as routine governance housekeeping. The post argued that TDF’s statutes require members to act in the foundation’s interest, not in the interest of their employers, and that certain members had repeatedly placed corporate priorities above the community’s needs. The board characterized its actions as a necessary defense of TDF’s independence — a move to ensure that no single corporate interest could capture the foundation’s decision-making apparatus.
“We understand that some of these decisions have caused concern,” the post read, in characteristically measured language. It went on to assert that every expelled member had been given the opportunity to respond to the allegations against them and that due process, as defined by TDF’s own bylaws, had been followed. The board emphasized that LibreOffice remains a community project, that contributions from all sources are welcome, and that the expulsions were about governance participation, not code contribution.
The community wasn’t buying it. Not entirely.
On mailing lists, forums, and social media, reactions ranged from cautious support to outright fury. Critics pointed out that the expelled engineers weren’t just any members — they were among the most technically knowledgeable people in the organization. Removing them from governance, the argument went, is like a hospital board firing its best surgeons and then insisting the quality of care won’t suffer. Supporters of the board countered that technical contribution doesn’t automatically entitle anyone to governance power, especially if that power is being wielded to benefit a specific company rather than the broader community.
This is where the story gets complicated, because both sides have a point.
Open-source governance has always been an awkward dance between idealism and economics. Projects like LibreOffice depend on corporate sponsors to fund full-time development. Collabora, for instance, sells a commercially supported version of LibreOffice optimized for enterprise and cloud deployment. Allotropia similarly builds products and services on top of the LibreOffice codebase. These companies have legitimate business reasons to want influence over the project’s direction. They’re not charities. They employ developers, pay salaries, and need the software to evolve in ways that serve their customers.
But The Document Foundation exists precisely to prevent any single commercial interest from controlling LibreOffice the way Oracle once controlled — and then effectively abandoned — OpenOffice.org, the predecessor project from which LibreOffice was forked in 2010. TDF was born out of that trauma. Its entire reason for being is to ensure that the office suite remains independent, community-governed, and free from corporate capture. So when the board sees members voting in blocs that align suspiciously well with their employers’ business strategies, alarm bells ring.
The tension isn’t new. It’s been simmering for years.
As WebProNews detailed, previous board elections had already exposed fault lines between corporate-affiliated members and independent community contributors. Accusations of block voting, backroom coordination, and conflicts of interest had surfaced repeatedly. What changed is that the current board decided to act on those concerns — decisively and, critics say, heavy-handedly.
The timing is particularly fraught. LibreOffice faces genuine competitive pressure from multiple directions. Microsoft 365 dominates the enterprise market. Google Docs owns the lightweight collaboration space. OnlyOffice and other open-source alternatives are gaining traction. LibreOffice’s relevance depends on sustained, high-quality development — the kind that requires significant engineering resources. And those resources come overwhelmingly from the very companies whose employees just got expelled from governance.
So here’s the question nobody in the community can dodge: What happens if Collabora and Allotropia decide the juice isn’t worth the squeeze?
They could, in theory, fork LibreOffice entirely. The code is licensed under the Mozilla Public License v2.0 and the GNU Lesser General Public License. Anyone can take it, modify it, and distribute it. A fork led by the engineers who actually write most of the code would be technically formidable from day one. It would also be devastating to TDF, which would retain the brand name and the governance structure but lose the people who know the codebase best.
This isn’t hypothetical musing. It’s exactly what happened with OpenOffice.org in 2010, when frustration with Oracle’s stewardship led to the creation of LibreOffice and TDF in the first place. The community moved, the code moved, and OpenOffice was left as a slowly decaying shell that Apache eventually picked up but never restored to its former vitality. History rhymes.
The Document Foundation’s blog post seemed to anticipate this concern, if obliquely. It stressed that TDF “remains committed to working with all ecosystem partners” and that “the door is always open for constructive engagement.” But the post also contained language that many read as a warning: members who prioritize external interests over the foundation’s mission will continue to face scrutiny.
Translation: we’ll do this again if we have to.
The broader open-source community is watching closely because the LibreOffice situation isn’t unique — it’s just unusually visible. Dozens of major open-source projects grapple with the same fundamental tension between volunteer governance and corporate contribution. The Linux kernel manages it through Linus Torvalds’ singular authority and a culture of rough consensus. The Apache Software Foundation manages it through a rigid meritocratic structure and a strong emphasis on individual merit over corporate affiliation. Mozilla manages it through a hybrid nonprofit-corporation model. None of these approaches is perfect. All of them involve tradeoffs.
TDF chose a democratic membership model, which works beautifully when the membership is genuinely diverse and independent. It works less well when a significant fraction of voting members happen to share an employer — or when the board interprets coordinated behavior as evidence of bad faith rather than shared technical judgment.
And that’s the crux of the dispute. The expelled members and their allies argue that they weren’t engaging in corporate capture. They were voting their technical convictions, which happened to align because they work on the same codebase every day and see the same problems. The board argues that the pattern of behavior — consistent bloc voting, resistance to certain governance reforms, prioritization of features that benefit specific commercial products — crossed a line from coincidence into coordination.
Neither side has produced a smoking gun. No leaked emails showing explicit vote-rigging. No corporate memos directing employees how to vote at TDF meetings. The evidence, such as it is, is circumstantial: voting patterns, meeting behavior, public statements that the board interpreted as putting corporate interests first. Whether that’s enough to justify expulsion is a question that reasonable people disagree on — vehemently.
The legal dimension adds another layer of complexity. TDF is incorporated in Germany, where nonprofit governance law is specific and enforceable. Expelled members could, in principle, challenge their removal in German courts. Whether any of them will remains to be seen, but the possibility hangs over the situation like a storm cloud. A court challenge would be expensive, time-consuming, and deeply damaging to the project’s public image regardless of outcome.
Meanwhile, the code keeps shipping. LibreOffice 25.2 was released earlier this year with significant improvements to Microsoft Office format compatibility, performance optimizations, and new features across Writer, Calc, and Impress. The software itself remains excellent — a testament to the engineering talent that, ironically, is now at the center of the governance crisis. Users who simply download and use LibreOffice may never notice anything amiss. But the people who build it know that something fundamental has shifted.
Several prominent open-source commentators have weighed in on social media platforms including X, with opinions splitting roughly along predictable lines. Those who prioritize community independence tend to support the board’s actions, arguing that painful decisions now prevent worse outcomes later. Those who prioritize development velocity and technical excellence tend to side with the expelled engineers, arguing that governance purity means nothing if the software stagnates.
Both camps claim to be defending LibreOffice’s future. Both may be right about the risks they identify. And both may be wrong about the solutions they propose.
What’s clear is that The Document Foundation’s attempt to end the speculation has, so far, only intensified it. The blog post provided the board’s perspective but didn’t include direct responses from the expelled members, didn’t release the specific evidence underlying the expulsion decisions, and didn’t articulate a clear path forward for rebuilding trust with the corporate contributors whose engineering labor the project desperately needs.
That’s not a recipe for resolution. It’s a recipe for escalation.
The next few months will be telling. If Collabora and Allotropia continue contributing code at their current pace despite the governance exclusion, the board’s gamble will look shrewd — it will have reasserted community control without losing engineering capacity. If those companies pull back, redirect resources, or initiate a fork, the board will have won a governance battle while losing the development war. And if legal challenges materialize, everyone loses except the lawyers.
For the millions of people and organizations that depend on LibreOffice — governments, schools, nonprofits, businesses in developing nations that can’t afford Microsoft licenses — the stakes are real and immediate. This isn’t an abstract debate about open-source philosophy. It’s about whether the software they rely on every day will continue to improve, remain competitive, and stay free.
I’ve been watching open-source politics for a long time, and I’ve seen projects survive worse. But I’ve also seen projects that looked indestructible collapse with shocking speed once the people doing the actual work decided to walk away. The code doesn’t care about bylaws. The code goes where the developers go.
The Document Foundation says it wants to end the speculation. Here’s what would actually accomplish that: transparency about the evidence, a credible process for expelled members to appeal, and a frank public conversation about how TDF intends to maintain development momentum without the governance participation of its most prolific engineering contributors. Anything less is just a press release dressed up as a peace offering.
LibreOffice deserves better than a civil war. Whether it gets better depends on whether the adults in the room — on all sides — decide that the project matters more than the argument.
WebProNews is an iEntry Publication