The Document Foundation Removes Dozens of Collabora Developers

April 5, 2026
aisecurityopen-source
A peaceful cemetery scene with a gravestone marked 'Woodward' and a cross necklace hanging in sunlight.
Photo by RDNE Stock project on Pexels

What happened

It has been reported that The Document Foundation (TDF) has removed dozens of developers who are employed by Collabora from its list of recognized contributors or membership. Details remain sparse and TDF has not published a full explanation; the move was first picked up in community channels and then amplified by tech outlets. For many users and contributors, it felt sudden — a sharp break in a project that has long relied on both volunteers and corporate contributors.

Context and tensions

Tension between Collabora and parts of the LibreOffice community was already simmering. It has been reported that Michael Meeks, now general manager of Collabora Productivity and a long-time GNOME/OpenOffice.org/LibreOffice contributor, publicly complained when LibreOffice decided to revive its LibreOffice Online project — an effort that had been dormant since 2022, according to Neowin. So, was this administrative action about project governance? About code ownership? Or something messier, a clash between corporate priorities and community norms? Allegedly, all of the above.

Why it matters

This is more than a personnel squabble. LibreOffice is one of the largest independent open-source office suites, and its health depends on a delicate balance between volunteer maintainers and paid contributors from companies like Collabora. When that balance tips, the user base notices. Who gets to steer the roadmap — volunteers, foundations, or companies with commercial stakes? That's the question now echoing through mailing lists and IRC channels.

Fallout and next steps

Collabora and TDF have not, as of publication, offered detailed public statements explaining next steps or a path to reconciliation. Community moderators are calling for clarity; downstream users want stability. Expect more conversations, maybe even formal governance proposals, as the project tries to patch the rift. Open-source communities survive these bruises, but they rarely forget them.

Sources: itsfoss.com, Slashdot