Ideally, we would have preferred to avoid this post. However, the articles and comments published in response to Collabora’s and Michael Meeks’ biased posts compel us to provide this background information on the events that led to the current situation.
Unfortunately, we have to start from the very beginning, but we’ll try to keep it brief. The launch of the LibreOffice project and The Document Foundation was handled with great enthusiasm by the founding group. They were driven by a noble goal, but also by a bit of healthy recklessness. After all, it was impossible to imagine what would happen after September 28, 2010, the date of the announcement.
At the time, nobody could imagine that the companies that had supported OpenOffice.org until then like IBM would create Apache OpenOffice to kill LibreOffice. Also, if the project were to be successful, it would require resources greater than those available, and above all, a deep management experience.
Fortunately, the project grew quite rapidly. However, the founders’ different backgrounds and opinions were at the same time the reason for some bold decisions – many of which right – as well as a few mistakes, which are the root cause of some of the current problems:
- granting free use of the LibreOffice brand only to companies in the ecosystem, to allow them to sell the software in Microsoft and Apple’s online stores;
- awarding contracts for the development of LibreOffice – new features, fixing “legacy” bugs, etc. – to companies whose representatives were on The Document Foundation’s Board of Directors, and who were active throughout the procurement process.
Both of these decisions were found to be incorrect for reasons relating to the non-profit law, to which The Document Foundation must adhere. They violated the law itself. When this fact was brought to the attention of the Board of Directors by the foundation’s legal counsels, the companies that had benefited from these errors sought to maintain the status quo rather than finding a solution. At the time – from the end of 2021 to the middle of 2022 – this could have been achieved swiftly and with minimal difficulty.
This attitude increased tensions within the BoD, adding to pre-existing frictions that began in 2020 when the majority of the new board decided to terminate the plan to transfer many of TDF’s tasks and assets to a parallel organisation called The Document Collective (TDC). Several issues that the current board had to solve stemmed from elements of that project that had been partially executed.
The origins of TDC are controversial. One reason given for setting up the parallel organisation was the “alleged inefficiency” of the TDF team [1], which was expressed by some of the directors. Unfortunately, instead of addressing the supposed problem with a reorganization or some training, the BoD decided to react by creating a new problem: a parallel structure with a supposedly “highly efficient” team that would highlight the alleged inefficiency of the TDF team.
TDC was presented at the LibreOffice Conference in Almería in 2019 without prior notice, raising concerns within the team and the community. This was partly because the parallel organisation’s project envisaged leveraging TDF’s financial resources as startup funds. This attempt resulted in permanent damage to relations between the project’s components, and especially between certain BoD members and the team.
After years of discussions marked by accusations and finger-pointing, during which no real progress was made in resolving the legal issues, the German authorities overlooking non profit foundations requested an audit whose results confirmed that resolving the issues was absolutely necessary to avoid losing non-profit status, with unforeseen consequences.
Unfortunately, the presence of company representatives on the Board of Directors (BoD), who were elected by employees of those same companies that are also TDF members, caused further delays to finding a solution, which has not yet been reached.
Fortunately, the introduction of restrictive measures – such as the decision to forfeit TDF membership status of Collabora employees – and the freezing of tenders, alongside the introduction of a robust procurement policy for development, has resulted in a positive outcome for the third audit [2]. At least, the BoD has demonstrated a willingness to break the deadlock that has persisted since 2022.
The board also reviewed governance issues from the past and set clear rules to minimise the risk of them recurring in future. These rules are set out in the Code of Ethics and Fiduciary Duties, the updated Conflict of Interest Policy and the Community Bylaws.
Of course, if we could rewind the course of history, some of the choices made since 2010 would hopefully be different and no one would repeat the mistakes or the wrong behaviours of the past.
As we said at the beginning, we would gladly have done without this post, but it was necessary to set the record straight and avoid speculation.
TDF has been preparing for some time for Collabora’s announcement, by hiring developers and exploring new partnership opportunities to support a growing interest in LibreOffice on the desktop, still a viable option for many deployments, the cloud and mobile, and in ODF as the preferred document format for governments worldwide.
Thanks to the growing importance of free and open source software, as well as open standards for document formats, the concepts that we have been advocating for over twenty years and have finally reached political institutions and users, The Document Foundation and the LibreOffice project are well positioned for the future.
[1] The Document Foundation’s daily activities are managed by a team of employees and contractors who handle administrative tasks, infrastructure, release management and developer’s mentoring, and coordinate community, quality assurance, UX, documentation, localization and marketing.
[2] The first audit in 2023 raised concerns about the mentioned issues. The second audit in 2024 confirmed the concerns. The third audit in 2025 did not raise concerns.
