The Document Foundation Expels Over 30 Collabora Developers From LibreOffice Governance in a Governance Showdown Years in the Making
TDF removed 30+ Collabora staff from membership—including 7 of the project's top 10 core committers—citing a legal dispute clause in newly adopted bylaws, prompting Collabora to announce a separate development track.
Overview
The Document Foundation (TDF), the German non-profit that stewards LibreOffice, removed more than 30 Collabora staff and partners from TDF membership on April 1, 2026, stripping them of voting rights and any formal say in the project’s governance. The purge included seven of LibreOffice’s ten most prolific all-time core committers, among them project co-founder Michael Meeks. Collabora, the Cambridge-based company that has supplied the majority of LibreOffice’s paid developers for over a decade, responded by announcing it would pursue its own separate development infrastructure and product line, raising questions about whether the world’s most widely deployed open-source office suite can sustain the split.
What We Know
The immediate trigger was a clause added to TDF’s newly adopted Community Bylaws requiring members to forfeit their membership if the company they work for enters an active legal dispute with TDF. According to TDF’s official statement, the measure followed two consecutive failed financial audits in 2023 and 2024 that documented governance violations: preferential trademark licensing to ecosystem companies for app store distribution, and development contracts awarded to firms whose representatives held seats on TDF’s own board. When legal counsel flagged these as threats to TDF’s non-profit status, the affected companies — primarily Collabora — allegedly sought to preserve the status quo rather than accept corrective measures. German nonprofit authorities, which oversee TDF’s charitable registration, reportedly requested an audit confirming that action was necessary to protect the foundation’s legal standing.
The removal affected over 30 individuals, as reported by Slashdot, and reached deep into LibreOffice’s core contributor base. Among those stripped of membership are Thorsten Behrens, Jan Holesovsky, Rene Engelhard, Caolan McNamara, Michael Meeks, Cor Nouws, and Italo Vignoli — several of whom were involved in LibreOffice’s founding when the project forked from OpenOffice.org in 2010.
The governance clash did not emerge in isolation. As The Register reported in March, tensions escalated significantly in late 2025 and early 2026. In November 2025, Collabora released Collabora Office for Desktop (CODA), a standalone application built on the same codebase as its cloud product — a direct entry into the desktop market that TDF has traditionally occupied. TDF responded in March 2026 by voting to revive LibreOffice Online, the cloud version it had shelved in 2020 and moved to its “attic” of retired projects. Meeks opposed the revival publicly, and told The Register the decision was “extraordinary,” asking: “It is unclear what more we could give to try to help them recognize our value.” TDF board member Paolo Vecchi countered that the move was governance correction, not competitive escalation, saying: “They are fixing the governance, and saying let’s get the community on a level playing field.”
TDF emphasized in its subsequent Q&A post that membership revocation is not the same as a ban from contributing. The foundation cited Git data showing that over the past twelve months, eight TDF-employed developers contributed 4,077 patches (37 percent of total commits), 47 Collabora employees contributed 4,763 patches (43 percent), and 221 volunteer developers contributed 1,871 patches (17 percent). TDF acknowledged that Collabora’s removed developers are technically free to continue submitting code under the Mozilla Public License and said it is “looking into hiring further developers” to compensate for any capacity reduction.
Collabora disputes that characterization. In its official blog post, Meeks characterized the ejections as based on “unproven legal concerns and guilt by association” and said the action was rooted in “retrospective rule-making by a political faction.” Collabora announced it would launch its own Gerrit code review infrastructure rather than continue using TDF’s, and would develop a new, streamlined Collabora Office product with a cleaner codebase and web-based toolkit, while maintaining long-term support for its Classic product. Meeks wrote that “it clearly no longer makes much sense to continue investing heavily in building what remains of TDF’s community.”
TDF published an open letter on April 11 addressed to the suspended Collabora developers, acknowledging that their “personal conduct was not the issue” and praising their technical contributions. The letter affirmed that “The Document Foundation and the LibreOffice project are open by definition and principle to all developers” and that the suspension was a structural consequence of fixing governance vulnerabilities rather than a judgment of individual character or competence.
What We Don’t Know
The most consequential open questions are practical: whether Collabora will actually stop contributing to the shared LibreOffice codebase, or whether — as TDF anticipates — it will continue submitting patches despite losing governance rights. The two projects share a Mozilla Public License codebase, meaning either party can fork or contribute without permission from the other, but a sustained reduction in Collabora’s contributions could meaningfully slow LibreOffice’s development velocity given how much of the recent commit activity came from Collabora engineers.
It is also unclear whether other commercial contributors and ecosystem partners will be swept up by the bylaws clause, or whether the dispute will remain bilateral. The legal dispute between TDF and Collabora that triggered the clause has not been publicly detailed; TDF has not disclosed what specific litigation is underway or what the financial stakes are.
The long-term trajectory of both Collabora Office and TDF’s revived LibreOffice Online remains to be seen. If Collabora builds a genuinely competitive desktop and cloud product on the shared codebase while reducing its upstream contributions, the practical effect could be a de facto fork even without a formal license split.
Analysis
The conflict illustrates a structural tension endemic to open-source projects sustained by commercial contributors. LibreOffice depends on Collabora for a substantial share of its active development, yet TDF must govern the project in ways that maintain its non-profit standing and protect it from capture by any single commercial interest. When those needs collide, the outcome is a governance crisis that neither side can resolve without cost.
The situation has parallels to the 2010 founding moment itself: LibreOffice emerged when Oracle’s acquisition of Sun Microsystems left the future of OpenOffice.org uncertain, and a group of contributors — many of whom are now at the center of this dispute — chose to fork and build an independent foundation. That history makes the current split particularly pointed: TDF is now applying to its own founding contributors the same logic Oracle once used to justify its control.
For the millions of users, public institutions, and European governments that have standardized on LibreOffice as a cornerstone of digital sovereignty strategy, the governance upheaval is a reminder that the long-term viability of open-source infrastructure depends on more than licensing terms. It requires organizational stability and sustainable contributor economics that are genuinely difficult to maintain as commercial interests grow alongside community ambitions.