Join the LibreOffice team as a Marketing and Communication Professional (full-time, remote, m/f/d)

TDF team photo

Love LibreOffice? Got a passion for marketing, media, public relations and creating great campaigns? We are The Document Foundation (TDF), the non-profit entity behind LibreOffice. We’re passionate about free software, the open source culture, and bringing new people with fresh ideas into our project.

To help to raise awareness of LibreOffice and support the marketing community with its work, we are looking for a Marketing and Communication Professional, to start as soon as possible.

Here’s what you’ll do

  • Work with our graphics design agencies and create content showcasing new and updated features in LibreOffice (blog posts, social media posts, videos, website pages…)
  • Draft and edit press releases and cross-channel content
  • Work directly with the senior communications lead on the strategic side: media relations, campaigns, and texts that carry TDF’s positioning
  • Improve media relations with EU and policy press, along with the FOSS and technology press
  • Maintain the press-contact database and mailing lists
  • Media monitoring, coverage tracking, and basic reporting
  • Edit contributed and translated texts from our wider marketing community
  • Track the effects and results of marketing campaigns on downloads and donations
  • Logistical coordination of event communication

What we want from you

The role is built around a two-year trajectory: full operational ownership from the start, and a growing share of strategic work as the senior lead reduces involvement through 2028. The person we are looking for is reliable and largely self-directed on operational work; collaborative and open on the strategic side, where TDF’s positioning is developed jointly during the transition. Someone who genuinely wants to grow into a strategic communications role, and is content to build toward it steadily rather than assume it on arrival.

  • Excellent communication skills, especially in written English
  • Working fluency in at least one other major European language; more is a clear advantage
  • A journalistic or public-relations instinct: a feel for what makes news, an ear for what a reporter will actually use, and either an existing network of press contacts or the demonstrated ability to build one
  • The ability to adapt communications across different channels: the TDF blog, social media, Reddit etc. – while maintaining a consistent style and tone
  • Good team-playing abilities

Familiarity with free software, open standards, and the digital-sovereignty debate is welcome, but not essential. This can be learned in the role, and genuine curiosity about it matters more than prior expertise. Also beneficial is experience in a non-profit, foundation, or other mission-driven organisation.

As always, TDF will give some preference to individuals who have previously shown a commitment to TDF, including but not limited to members of TDF. Not being a member does not exclude any applicants from consideration.

Join us!

All jobs at The Document Foundation are remote jobs, where you can work from your home office or a co-working space. The work time during the day is flexible, apart from a few fixed meetings. The role is offered as full-time (ideally 40 hours per week). While we prefer full-time for the role, part-time applications, or proposals to grow the hours over time, will be considered. Candidates that are resident in Germany will be employed directly by TDF. Otherwise, external payroll services will be used if available in the candidate’s country of residence.

Are you interested? Get in touch!

TDF welcomes applications from all suitably qualified persons regardless of their race, sex, gender, disability, religion/belief, sexual orientation or age. Don’t be afraid to be different, and stay true to yourself. We like you that way! 😊

We’re looking forward to receiving your application, including information about you (your resume), when you are available for the job, and of course your financial expectations. Please provide details about your experience and send us an e-mail to marketingjob@documentfoundation.org no later than August 31, 2026 (end of day, Berlin time). If you haven’t received feedback by September 30, your application could not be considered.

Also note: we only accept applications from the applicant, and not from any intermediary. We do not accept agency resumes. Please do not forward resumes to any recruiting alias or employee.

Welcome to our new TDF members!

Welcome banner, with people celebrating

Members – more formally known as the “Board of Trustees” – are a crucial part of The Document Foundation, the non-profit entity behind LibreOffice. They are people from across the globe who contribute time, effort and skills, whether on a voluntary or paid basis. Members can vote for the Board of Directors (BoD) and the Membership Committee (MC), and also nominate themselves for a position in the BoD and the MC. Oh, and they get @libreoffice.org email addresses as well!

Let’s welcome our new members:

  • Aleksi Kallio
  • Brandon Evangelista
  • Damiano Perri
  • Karl-Heinz Gruner
  • Mihai Alexandru Vasiliu
  • Neil Roberts
  • Robert Pearson
  • Rohan Singh

Glad to have you on board, and thanks for being in the project 😊 Everyone who contributes in the LibreOffice and Document Liberation projects can apply to be a member too. Join us!

LibreOffice State of the Project (July 2025 – June 2026)

We are releasing the quarterly updated State of the Project Slide Deck, based on data from July 1st, 2025, to June 30, 2026, extracted from the LibreOffice dashboard and the Matomo repository.

During the 12 months 309 developers worked on the source code, adding 11.464 new commits (Git): 238 volunteer developers (77%) provided 2.028 commits (18%); 11 developers from The Document Foundation (4%) provided 4.501 commits (39%), and 60 developers from 8 ecosystem companies (19%) provided 4.935 commits (47%).

The slide deck is also a tribute to the 20 top Git committers, the 20 top Gerrit committers, the top 20 Bugzilla issue submitters, the top 20 people answering on Discourse, and the top 20 translator on Weblate. To all of them and to all the other contributors, thank you.

Looking at donations and downloads, the trend during the first six months of 2026 confirms the positive trend started in early 2025. Donation figures refer to the number of transactions and not to their amount, which is available via the ledgers published on The Document Foundation website.

You are invited to look at the slides, and download the file to compare it with the previous slide deck published in January and April. The next slide deck which will be available in October and will cover the 12 months between October 1st, 2025, and September 30, 2026.

We have started to publish these slide decks in January 2026, to provide a transparent overview about the progress of the project through some of the most significant measures of development, downloads and donations data collected by the marketing team at TDF.

 

Download the Slide Deck in English

How proprietary formats have become Microsoft’s main tool for lock-in

In the previous article, we explored the importance of standards: how the unspoken agreements governing electrical sockets, paper sizes and file formats form the foundations of a world in which choices remain open and power is not concentrated in the hands of a single player. We concluded with a question: if open standards are so beneficial, why aren’t they universally adopted?

The answer, in the case of document formats, lies in a single page produced by Microsoft Office. Getting rid of it is harder than it seems.

A file is never just a file

When you save a document on your computer, you are choosing a format — that is, the language in which your document is written in a way that the computer can understand: the set of rules that determines how words, tables, images and formatting instructions are stored and, consequently, how they can be retrieved, shared and read in the future.

For decades, the dominant format for office documents has been that produced by Microsoft Office. Initially as binary files with extensions such as DOC and XLS, then as XML-based formats introduced with Office 2007: DOCX, XLSX and PPTX. These formats are used by hundreds of millions of people. They are the lingua franca of offices, schools, public administrations and courts around the world.

Furthermore, in significant and decisive ways, they are proprietary — meaning they belong to Microsoft, are controlled by Microsoft and serve Microsoft’s interests in ways that may not align with the interests of users.

Understanding how all this works — and why it matters far beyond mere matters of software preference — is the aim of this article.

The architecture of dependency

Proprietary formats create dependency through a mechanism that is simple in principle and extraordinarily effective in practice: they make the data contained in a document inseparable from the software used to create it.

This is not a law of physics, but a design choice.

An open format — a format whose specifications are published, freely available and implementable by any software without restrictions — stores information in such a way that any compliant application can read, write and reproduce it faithfully.

A proprietary format, by contrast, may contain undocumented features, private extensions or behaviours that only the original software implements correctly. The document may be opened by other applications, but it cannot always be reproduced faithfully.

The practical consequence is familiar to anyone who has tried to open a Microsoft Office document in another application: the formatting becomes distorted, bullet points shift, tables lose their proportions, and headings appear different.

A presentation that looked polished in PowerPoint seems slapdash in a different viewer: the content is all there, whilst the document, strictly speaking, is not.

This is “lock-in”: it is not a padlock, it is not a technical ban, it is not a contractual restriction, but a silent and persistent friction that makes any work outside the Microsoft ecosystem seem slightly off, slightly unreliable, slightly unprofessional — and ensures that the easiest route is to return to the tools that produce documents with the expected appearance.

The standard that isn’t a standard

Microsoft formats have been submitted to international standardisation bodies and approved. This has been used, time and again, to argue that concerns about “lock-in” are exaggerated — that OOXML, the Office Open XML format, is as open a standard as any other, and that the playing field is level.

The reality is considerably more complicated.

The standardisation of OOXML was one of the most contested processes in the history of ISO: national standardisation bodies reported procedural irregularities, and the votes were contested. The process has left an indelible mark on the credibility of international standards, and has resulted in a specification of extraordinary length and complexity — running to thousands of pages — which did not describe a format designed for interoperability, but rather the existing behaviour of Microsoft Office, including legacy behaviours, undocumented features and implementation details specific to Microsoft’s source code.

No other software could fully implement the format, yet it was required to do so out of respect for its users, who needed to exchange documents with Microsoft users.

The version of OOXML that was standardised — OOXML Transitional — initially co-existed with a stricter variant, OOXML Strict, which eliminated most of the problematic legacy elements, but not all. Moreover, Microsoft Office has always used OOXML Transitional as the default format, and has relegated OOXML Strict to the bottom of the options (to prevent it from being used).

The practical effect is that the format used daily by hundreds of millions of people is the one that only Microsoft’s own software implements correctly, whilst the cleaner variant — which other software could actually support — is not used, and has now even disappeared from some versions.

A standard that only one implementation fully supports is, from a functional point of view, a proprietary format with a standardisation certificate.

Lock-in, from the individual to the institution

Dependence on document formats is the main mechanism of lock-in, but it is not the only one. We discussed the layering of dependencies at length in a previous article, so we will not revisit the subject here. Levels of dependence vary depending on the importance of the documents involved and the size of the organisation producing them.

For an individual user, a document with altered layout is simply an inconvenience. For a law firm, it may mean that a contract submitted to court does not match the version in the client’s file. For a hospital, it may mean that a clinical form is printed incorrectly. For a government department, it may mean that a document appears differently depending on the software used: a silent and unintended form of unequal access to public information.

At the level of public administration, this dependency takes on a dimension that goes beyond operational efficiency. A government that archives official documents in a format controlled by a private company has, strictly speaking, delegated the custody of its institutional memory to that company. Today, documents are readable because Microsoft continues to support the format, but whether they can be read in twenty years’ time will depend on the company’s decisions, for reasons that have nothing to do with the public interest.

This is not a hypothetical risk: formats are phased out, software versions change, and features present in one version of Office may behave differently — or not work at all — in another.

The history of digital documents is littered with files that cannot be opened because the software with which they were created no longer exists or no longer works on modern systems. Proprietary formats accelerate this risk by concentrating the knowledge needed to interpret them within an organisation whose commercial interests may, at any time, diverge from the interests of those who depend on access to their own documents.

What true sovereignty requires

A truly independent document — one that displays identically on any system, in any country, for any user, regardless of the software used — requires informed choices at every stage of its creation.

At the format level, it requires an open standard such as the Open Document Format (ODF), whose specifications are published, freely implementable and managed by a body independent of any single vendor. ODF is an international ISO standard that has undergone a legitimate standardisation process and whose specifications can be fully implemented by any software that chooses to do so. LibreOffice, the leading open-source office suite, uses ODF natively. The same should apply to any other self-respecting open-source office application.

In terms of fonts, it requires open fonts, the designs of which are published under licences that allow any software to implement them and any user to install them without cost or restrictions. Open font repositories offer a wide range of high-quality options that have no proprietary dependencies.

In terms of templates and workflows, it requires institutional policies that specify open formats and open fonts as the default for all official documents — not as an aesthetic preference, but as a governance requirement, in the same way that a public administration might specify accessibility standards or data protection requirements.

At the archiving level, this requires a commitment to formats specifically designed for long-term preservation — such as PDF/A for documents intended for permanent archiving — whose specifications are public and whose readability does not depend on the commercial decisions of a single supplier.

None of this is technically complex, but it requires a conscious decision by someone with the authority to do so.

A document is never innocent

A document is an argument made visible. It is also, always, a set of dependencies made invisible.

When an institution sends a letter formatted with a proprietary font, embedded in a proprietary format, produced by proprietary software, it is not communicating information but perpetuating a dependency — in workflows, in the expectations of correspondents, in staff memory and in the implicit message to recipients — that this is precisely how documents work, that there are no alternatives, that the infrastructure of written communication belongs to someone else, and that it has always been this way.

Digital sovereignty begins with the recognition that this is a choice: the file format is a choice, the font on the page is a choice, and the software is a choice. And choices, unlike facts, can vary.

That document, which continues to be regarded as a “seemingly” innocent piece of paper, is in reality no longer a piece of paper — and hasn’t been for some time — but an executable file that is interpreted by software, and as such is no longer innocent but, in many cases, the insidious tool of lock-in.

Microsoft Office Icons: Ms Office Icon Vectors by Vecteezy
Protest against OOXML: Techrights
Innocent piece of paper: The Mazloom Law Firm, LLC

Financials and Budget – TDF Annual Report 2025

TDF Annual Report 2025 banner

This is part of the Annual Report 2025 from The Document Foundation, the non-profit that coordinates the LibreOffice project and community.

TDF exists because of a large, dynamic global community — volunteers, ecosystem companies and committed end users who support our work with donations of both time and money. The 2025 accounts tell a clear story: a foundation that grew significantly, while keeping its finances transparent and its spending tied to its mission.

A year of strong growth in income

Total income for 2025 reached € 2,175,997, a substantial increase on the € 1,387,589 recorded in 2024. The growth came from three distinct sources, and it is worth being precise about each.

The largest share, € 1,976,825, came from donations — overwhelmingly from individual users and small businesses, mostly in Europe. This was the fifth consecutive year in which donations exceeded one million euro, and the highest figure to date. Part of this increase was organic, reflecting the continued strength of LibreOffice downloads. A further part can be attributed to a concrete change: in mid-2025 we introduced a new in-product update notification on Windows, which periodically — after every major release and selected minor ones — informs users that an update is available, presents the new features, and invites them to support the project with a donation. The effect was immediately visible as a step-up in donations from the moment it was deployed, and it is keeping donations at a higher level into 2026. We mention this openly, because transparency about *why* the numbers move is as important as the numbers themselves.

The second source was income from the sale of LibreOffice through online stores, sponsoring and related commercial activity, which together generated € 168,975. The Apple App Store (€ 118,942) and the Microsoft Store (€ 35,393) accounted for most of this. The third source was € 30,197 in income from securities held under the foundation’s asset management.

How the money was spent

Total expenditure for 2025 was € 1,457,343. The breakdown by category shows where donor money goes.

  • Staff and operations remained by far the largest commitment, at € 1,091,032. This covers salaries (€ 406,736), statutory social security contributions (€ 93,244) and freelancers (€ 591,052) — the people who keep infrastructure, communication, administration and project coordination running, in order to share knowledge, support the community in its activities, and enable contributors to do their work.
  • Tenders. As in 2024, no development tenders were funded in 2025. Tenders related to LibreOffice development remain on hold, and will be resumed based on the development strategy currently under discussion according to the new Procurement Policy.
  • Events and community support amounted to roughly € 87,000, including the LibreOffice Conference (developer conference, € 51,184), community projects (€ 15,014) and student scholarships (€ 17,368), together with marketing initiatives. These funds support the events and local activities that hold the global community together, and help us to share knowledge around the world.
  • Infrastructure and hosting came to € 51,420, covering the hosting, virtual machines, services and domains that underpin the project’s technical independence — a foundational asset we continue to prioritise.
  • Legal and administrative expenses totalled roughly € 92,000, including accounting and the preparation of financial statements (€ 34,164), legal advice and counselling (€ 36,597 across project and general legal work), and insurances (€ 4,626).
  • Cost of fundraising. Receiving donations is not free. In 2025, payment-processing and banking fees came to roughly € 98,000 — Stripe fees of € 46,446 and bank transfer and money-transfer fees of € 51,190. These are simply the cost of doing business: they scale with the volume of donations we receive. It is worth adding that these figures do not capture the full picture, because PayPal’s currency-conversion costs are embedded in the transactions and not separately visible — though they are comparable in scale to the Stripe fees. We report this plainly so that no reader underestimates what it costs to collect the donations that fund our work.

Results and transparency

After expenses, the charitable entity closed the year with a result of € 554,476, asset management contributed € 21,263, and the commercial business operations returned a profit of € 142,916.

Transparency remains one of TDF’s defining characteristics — towards our donors, contributors, community and users. Our accounting is handled by a professional accountant, and our complete ledgers, listing all income and spending broken down by project, are published on our public wiki at https://wiki.documentfoundation.org/TDF/Ledgers, with only a few items obfuscated for privacy. As in previous years, and given the scale the foundation has reached, our books have been audited, and the Board continues to work with the authorities in Berlin to implement the improvements the audit recommended.

To everyone who contributed time, skills, resources and money in 2025: thank you. The foundation’s strength is your achievement.

Note: The expense categories above are indicative groupings drawn from the foundation’s accounts. They exclude VAT flows and certain material costs that the ledger handles separately, so the categories are not intended to reconcile arithmetically with the per-sphere annual results. The authoritative, fully itemised figures are published in the ledgers.

Like what we do? Support the LibreOffice project and The Document Foundation – make a donation, or get involved and help our volunteers. Thank you!

What We Owe Each Other, in Millimetres and Volts

You arrive in a city you have never visited before. You are tired. You find your room, open your suitcase, pull out a charger, and plug it into the wall. The small green light comes on. You think nothing of it, because nothing happened. You moved between two countries, two electrical grids, two regulatory regimes, and the machine in your hand simply continued to work.

Behind that uneventful moment sits more than a century of meetings, arguments, technical drawings, and compromises between people who will never meet you. The plug fits because somebody, somewhere, decided that it should – and decided further that the decision should be written down, made public, and not owned by anyone. We almost never notice this kind of work. We only notice it when it fails: the adapter that does not fit, the document that does not open, the part that cannot be replaced. Standards are the infrastructure we live inside, and like most infrastructure, they are invisible until they are not.

The public agreement

A standard is a public agreement about how things should fit together. Two words in that sentence carry the weight: public and agreement. Public, because the rules are written down and anyone can read them. Agreement, because nobody imposes them alone; they are negotiated between parties who accept that the shared space is more valuable than any individual advantage within it.

This distinguishes a standard from two things it is often confused with. It is not a law, because no state enforces it directly. And it is not a product, because no company owns it. A standard sits in a peculiar middle ground – it is something that belongs to everyone and to no one, maintained by institutions whose only task is to keep it coherent and accessible. The metric system is a standard. So is the size of a sheet of A4 paper, the shape of a stop sign, the gauge of a railway track, the dimensions of a shipping container. None of these things were inevitable. Each of them was once contested, and each of them was resolved not by conquest but by convention.

A civic act, not a technical one

It is tempting to treat standards as a matter for engineers. They are not. Or rather, they are only incidentally so. The engineering is the easy part. The hard part is the decision that the rules of a shared space should not belong to any single actor – that the measurement of length, the width of a road, the voltage in a socket should be held in common rather than owned.

The history of standards is, almost without exception, a history of fragmentation followed by painful consolidation. In the nineteenth century, European railways had dozens of incompatible track gauges, because each company built its own. Goods had to be unloaded and reloaded at every border, and sometimes at every regional boundary. The loss was enormous, and it was eventually resolved not because engineers invented a better track but because societies decided that the common good of interoperability was worth more than the private advantage of incompatibility. The same story repeats with screw threads, with time zones, with paper sizes, with electrical systems. Each consolidation was a political act dressed in technical clothing.

When we say a standard is public, then, we are saying something quite radical. We are saying that a certain category of rules – the ones that govern how we connect to each other – must be held outside the market, because if the market owns them, the market can charge rent on the simple act of cooperation.

What standards give us

From the point of view of the person who uses them – which is to say, all of us, every day – open standards provide three things that are easy to take for granted until they are gone.

The first is interchangeability. Because the rules are public, anyone can build to them. If the lamp you bought five years ago breaks, you can replace the bulb with one from any manufacturer. If your supplier raises prices unreasonably, you can switch to another. If a company goes out of business, its customers are not stranded. You are not captured by the choices you made in the past, because the choices were made against a common framework rather than inside a private one.

The second is continuity. What works today will still work tomorrow, and what was made yesterday still works today. This is a quieter gift, but it may be the most important one. A standard that is public and stable means that your past remains legible to you. The documents you wrote twenty years ago, the tools your grandfather used, the measurements recorded in an old building plan – all of these remain available, because the rules that governed them are still available. Continuity is how a society talks to itself across time. It is how we remain connected to what we have done and what has been done for us.

The third is shared ground. Standards let people who have made different choices still cooperate. You and I do not need to use the same brand, the same supplier, the same tool. We only need to agree on the interface between us. A standard is, in this sense, a kind of peace treaty – a recognition that a common format for exchange matters more than uniformity of preference. It is the opposite of a monoculture. It is the condition that makes plurality possible without chaos.

When the rules become private property

Now consider what happens when the rules of a shared space are privately owned.

Imagine that the thread on every screw in your country belonged to a single company, and that using a screw at all required permission from that company. Imagine that the gauge of the railway tracks was the property of one firm, and that every other operator had to pay to run trains on lines they did not own. Imagine that the voltage of the electrical grid was licensed, and that plugs from any other manufacturer simply did not fit.

The three goods we just described begin to erode. Interchangeability disappears, because you cannot replace one part with another without the owner’s permission. Continuity depends on the corporate survival of a single actor: if the company changes its terms, raises its prices, or goes bankrupt, you lose access not just to a product but to the entire category of things that depended on it. Shared ground shrinks until it includes only the people who have paid the same licence as you have. Cooperation becomes a privilege extended by a third party, rather than a right held between equals.

This sounds absurd when we imagine it happening to physical infrastructure. We would never accept it for screws or rails or electricity. And yet the history of standards is also the history of attempts to do exactly this, resisted successfully in some domains and less successfully in others. The reason we have open standards for physical infrastructure is not that anyone thought them obviously good. It is that societies fought, sometimes for decades, to keep them out of private hands.

The ancestor question

There is a useful way to think about all of this, which is to ask what kind of ancestor we want to be.

Every time we accept an open standard, we are making a small bet on behalf of people who do not yet exist. We are saying that the thing we are building – the document, the product, the system – should remain accessible to them, even though we will not be here to help them open it. We are choosing to be hospitable to a future we cannot see. And every time we accept a closed one, we are making the opposite bet. We are saying that our successors will have to rely on the continued goodwill of a private actor to reach back to what we have made. We are outsourcing their access to our own lives.

This is not a technical question. It is a civic one, and it is also a moral one. Standards are how a society decides whether its own infrastructure should be owned or shared, whether its past should be accessible or licensed, whether its future should be open or gated. They look like engineering. They are really a quiet, continuous answer to the question of what we owe each other, and what we owe to those who come after us.

So the next time you plug something into a wall and it simply works – the next time a door handle fits, a page prints cleanly, a part slots into place without thought – consider for a moment what had to be true for that to happen. Consider who refused to own it. And ask yourself what kind of ancestor a closed standard lets you be.