Comment about Collabora blog post

Many people have asked The Document Foundation for its official position on what Collabora announced in a blog post.

This is not the first announcement of this kind in FLOSS environments, nor will it be the last. Collabora feels that it has to invest in a specific product that differs from traditional, full-featured office suites such as LibreOffice. They are, of course, free to take this approach based on the MPL licence.

However, Collabora has framed this as a direct consequence of the Membership Committee’s decision to remove Collabora employees from TDF membership based on the recently approved Community Bylaws.

The Community Bylaws require that employees of companies involved in legal disputes with The Document Foundation be removed from TDF membership because, in the past, people made decisions in the interest of their employers rather than in the interest of The Document Foundation.

We would prefer to avoid further discussion about who is responsible for what, as this would lead to endless debates that would not benefit the project as a whole (i.e. The Document Foundation, its ecosystem companies, and its volunteer contributors).

Unfortunately, a series of wrong decisions in the past have turned into an ongoing problem which has grown to the point of posing a significant risk to the project. The Document Foundation could have lost its charitable status, which would have had unforeseen consequences.

This risk remains, but thanks to hard rules such as those included in the Community Bylaws, whose enforcement is unpleasant for everyone, it is being significantly reduced and hopefully avoided.

The project welcomes contributions from true believers in open source. As the majority of people at Collabora are such believers, we expect them to continue contributing when the time comes.

Also, removal from membership does not mean removal from community. Anyone is welcome to contribute and participate.

On the other hand, The Document Foundation is hiring developers and donations are growing, which will allow for further developer and team member recruitment.

In the current environment, the project’s focus should be on leveraging the opportunity presented by growing interest in true FLOSS solutions that support digital sovereignty — or, if you prefer, the freedom to own and control your infrastructure, applications, and documents.

The 14th Anniversary of Our Foundation

17 February 2026 marks the 14th anniversary of The Document Foundation’s recognition as a non-profit organisation under German law. The foundation is focused on developing free and open-source software for individual productivity.

This focus has guided the development of LibreOffice and the software tools for liberating proprietary formats released by the Document Liberation Project. These tools are used by LibreOffice and other open-source and proprietary software.

This growth would never have been possible without the invaluable contributions of the many individuals and companies that have been involved over the years. Today, we celebrate this important milestone and prepare for further growth.

Indeed, given the current geopolitical situation and the push towards digital sovereignty — or independence from major US technology companies — the educational function of LibreOffice and the Open Document Format standard is more important and relevant than ever.

The open-source engine of LibreOffice, known as LibreOffice Technology, is now the only development platform for software solutions — desktop, mobile, or cloud — that can guarantee users true independence from companies and total control over their content, now and forever.

This is all thanks to the principles that have guided The Document Foundation since day one and will continue to provide a reference point for the project’s future evolution.

Version 1 of TDF Community Bylaws

TDF logo and words Implementation of Community Bylaws

The Document Foundation (TDF) is the non-profit entity behind the LibreOffice project. It collects donations from users, and employs a small team to support and coordinate the worldwide community that makes the software. In TDF there are various bodies including the Board of Directors, Membership Committee, and the Board of Trustees:

Diagram of structure of TDF bodies

These foundation bodies are guided by a set of policies, and as part of recent governance updates, the Board of Directors voted on a Code of Ethics and Fiduciary Duties and Updated Conflict of Interest Policy. Now the Board has voted to Adopt version 1 of the Community Bylaws, based on feedback from the community. The Bylaws…

define the internal organisation, regulations and procedures of The Document Foundation. These regulations interpret, clarify, and extend the Foundation’s Statutes without modifying or replacing their binding rules.

Click here for the full Community Bylaws

Updated Conflict of Interest Policy for TDF’s Board of Directors

TDF logo and words Conflict of Interest Policy

The Document Foundation (TDF) is the non-profit entity behind the LibreOffice project. It collects donations from users, and employs a small team to support and coordinate the worldwide community that makes the software. In TDF there are various bodies including the Board of Directors, Membership Committee, and the Board of Trustees:

Diagram of structure of TDF bodies

These foundation bodies are guided by a set of policies, and now the Board of Directors has voted on an updated Conflict of Interest Policy. The purpose of the policy is to protect any of The Document Foundation’s interests against the risk that derives from overlapping loyalties of a person. See here for the results of the vote.

Click here for the full updated Conflict of Interest Policy

Welcome Dan Williams, new LibreOffice Developer focusing on UI/UX

Photo of Dan Williams

The Document Foundation is the small non-profit entity behind LibreOffice. It oversees the project and community, and is now expanding with new developer roles. So let’s say hello to Dan Williams, who joins the team to work on design and user interface (UI) improvements, with an initial focus on macOS:

Tell us a bit about yourself!

I’m from the USA, have lived on both US coasts at various times, and now live back in the “midwest” where I grew up.

I was previously a software engineer, team lead, and manager at Red Hat for more than 20 years. In that time I’ve worked on a large variety of projects, from local networking to cloud networking to desktop software. I spent two years helping build the One Laptop Per Child software stack which was an eye-opening experience from a UI and design perspective. I believe passionately in free and open-source software; all the code I’ve written so far in my career is open-source.

Oddly enough, I’m not new to the LibreOffice community; I was an OpenOffice contributor and co-founded the NeoOffice port to Mac OS X (now called macOS). That led to being hired by Red Hat to package and improve OpenOffice for Fedora and Red Hat Enterprise Linux, where I helped start the 64-bit port and realize the Native Widget Framework that’s still used in LibreOffice today. I eventually handed my Red Hat OpenOffice duties over to Caolán McNamara (now at Collabora) and moved on to networking. I still recognize quite a few of our community members who I worked with before!

Outside of office software I’m the maintainer of the ModemManager WWAN software stack and I seem to have developed a hobby of collecting LTE and 5G base stations. I enjoy playing with hardware (especially if it runs Linux), baking and cooking, building large structures out of wood, and occasionally brewing beer in my basement.

What’s your new role at TDF, and what will you be working on?

A significant part of my new role will echo my early OpenOffice contributions: Mac! I’ll convert the last bits of Carbon API into modern Cocoa ones. This old code involves some pretty core functionality like popup menus and key modifier detection so it’s going to be tricky but we need to do it. Nobody knows how much longer Apple’s going to support HIToolbox but I’d like to be prepared. I’m also going to improve general Mac usability and experience; I’ve been using LibreOffice on macOS since the beginning so I’m familiar with its rough edges.

LibreOffice screenshot, running on macOPS

But the Mac isn’t the only platform so I’ll be driving user interface improvements and fixing annoying bugs everywhere else too, regardless of platform or visual backend. I also look forward to working with the LibreOffice Design community to try out new ideas and see what sticks.

I enjoy the challenge of working throughout the entire codebase, from the depths of VCL/SAL up to the UI logic and layout in the applications at the top. I’m also a big believer in automated testing and continuous integration (CI) and I hope to improve our reliability and reduce regressions. It’s often a pain to write tests for a small bug fix or any other change, but I think they’re necessary for a healthy project.

How can all users of LibreOffice help out?

What are the most annoying interface and interaction bugs, for the Mac or otherwise? Make sure they’re in Bugzilla! I need help prioritizing issues – so here’s your chance to get your favorite bug looked at.

If you’re interested in LibreOffice’s user interface and visual identity, join the Design team.

Do you have Cocoa experience on the Mac and a bit of extra time? Help me out with bugs! I’d be happy to get you started.

Code of Ethics and Fiduciary Duties for TDF’s Board of Directors

TDF logo and words Code of Ethics

The Document Foundation (TDF) is the non-profit entity behind the LibreOffice project. It collects donations from users, and employs a small team to support and coordinate the worldwide community that makes the software. In TDF there are various bodies including the Board of Directors, Membership Committee, and the Board of Trustees:

Diagram of structure of TDF bodies

These foundation bodies are guided by a set of policies, and now the Board of Directors has voted on a Code of Ethics and Fiduciary Duties. The code ensures that members of the Board of Directors “strive to speak and act with the mission and effectiveness and the best interest, and only the interest, of the foundation in mind.” See here for the results of the vote.

Click here for the full Code of Ethics and Fiduciary Duties