LibreOffice Urges EU Commission to Follow Its Own Guidelines

LibreOffice Challenges the European Commission on Open Source Compliance

Learn more about gen z cannabis vape shift: market strategy insights

The Document Foundation, the organization behind LibreOffice, recently issued a formal request to the European Commission. The request asks the EU to practice what it preaches when it comes to open-source software adoption. This development highlights a growing tension between stated policy goals and actual implementation within EU institutions.

The European Commission has long championed open-source software, digital sovereignty, and vendor-neutral technology standards. Yet internal procurement practices tell a different story. LibreOffice's intervention exposes a critical disconnect that affects software choices and broader questions about technological independence and public spending.

Does EU Policy Match Procurement Practice?

The European Commission has published multiple guidelines promoting open-source software adoption. These documents explicitly encourage EU institutions to prioritize open standards, avoid vendor lock-in, and support interoperable solutions. The Commission's own "Open Source Software Strategy" emphasizes these principles as fundamental to digital transformation.

LibreOffice representatives note that proprietary office suites continue to dominate Commission infrastructure. The Document Foundation points to procurement decisions that favor closed-source alternatives despite the availability of capable open-source options. This pattern contradicts the Commission's stated commitment to open standards and digital independence.

The request specifically references the Commission's 2020 Open Source Software Strategy. This document commits EU institutions to "think Open Source first" when developing or procuring software solutions. Actual procurement practices have not reflected this commitment in meaningful ways, according to The Document Foundation.

Why Does Digital Sovereignty Matter?

Digital sovereignty has become a strategic priority for European institutions. The concept encompasses control over data, infrastructure, and the software systems that process critical information. Reliance on proprietary software from non-EU vendors creates dependencies that undermine this sovereignty.

Open-source solutions like LibreOffice offer genuine alternatives. The software is developed transparently, auditable by anyone, and not controlled by a single corporate entity. For government institutions handling sensitive data, these characteristics provide significant security and independence advantages.

The financial implications are substantial. EU institutions collectively spend millions of euros annually on software licensing. Shifting to open-source alternatives could redirect these funds toward development, customization, and support services that create value within European economies. Large organizations can reduce software costs by 40-60% through strategic open-source adoption, according to industry estimates.

What Do European Commission Guidelines Actually Say?

The Commission's official guidance documents contain clear directives. The 2020 Open Source Software Strategy states that EU institutions should "systematically assess whether developing or procuring open source software could be a viable option." The strategy emphasizes several key principles:

• Interoperability: Systems should work together regardless of vendor
• Transparency: Code should be auditable and modifiable
• Vendor neutrality: Avoid dependencies on single suppliers
• Long-term sustainability: Choose solutions with viable maintenance paths

For a deep dive on cloud benchmarks 2026: performance standards you need, see our full guide

The European Interoperability Framework reinforces these points. It explicitly recommends using open standards and considering open-source software for public sector applications. These formalized policy positions should guide procurement decisions, not serve as mere suggestions.

The Commission's Digital Strategy emphasizes technological sovereignty. The strategy acknowledges that dependence on non-EU technology providers creates strategic vulnerabilities. Open-source software represents a pathway to reduce these dependencies while maintaining technical capabilities.

For a deep dive on how yoghurt delivery women combat digital exclusion, see our full guide

Which Governments Successfully Use Open Source?

Several European governments have successfully implemented LibreOffice at scale. These examples demonstrate that open-source office suites can meet demanding institutional requirements.

The Italian Ministry of Defense completed one of Europe's largest LibreOffice deployments. The ministry migrated 100,000 workstations to the open-source suite, achieving significant cost savings while maintaining full functionality. The project demonstrated that even security-sensitive organizations can rely on open-source solutions for critical operations.

France's Gendarmerie Nationale provides another compelling case study. The national police force transitioned 72,000 computers to LibreOffice and open-source alternatives. The migration saved approximately 2 million euros annually while improving document compatibility and reducing security vulnerabilities, according to official reports. The organization reported no significant productivity losses during the transition.

The city of Munich's experience offers valuable lessons. The city initially migrated 15,000 workstations to LibreOffice and Linux-based systems. Although political changes later reversed some decisions, the technical implementation succeeded. The project proved that large-scale migrations are feasible when properly planned and executed.

How Does LibreOffice Compare Technically?

LibreOffice has evolved significantly since its 2010 fork from OpenOffice. The suite now offers comprehensive functionality that matches or exceeds proprietary alternatives in many areas. Understanding these capabilities helps contextualize why The Document Foundation considers EU institutions' software choices problematic.

The suite includes six core applications: Writer (word processing), Calc (spreadsheets), Impress (presentations), Draw (vector graphics), Base (databases), and Math (formula editing). Each application supports industry-standard file formats, including Microsoft Office formats, ensuring compatibility with existing workflows.

Document interoperability represents a critical strength. LibreOffice natively supports the Open Document Format (ODF), an ISO-standardized format that ensures long-term accessibility. Unlike proprietary formats that can become obsolete, ODF documents remain readable regardless of software vendor changes. This characteristic aligns perfectly with EU guidelines on data preservation and accessibility.

Security features have improved substantially in recent versions. LibreOffice includes document signing capabilities, encryption options, and privacy-focused defaults. The open-source nature allows security teams to audit code and verify that no hidden vulnerabilities or backdoors exist. For institutions handling sensitive information, this transparency provides assurance that proprietary alternatives cannot match.

Why Do Institutions Resist Open Source Change?

Institutional resistance to open-source adoption persists despite clear policy guidance and technical capabilities. Several factors contribute to this pattern, though none fully justify ignoring official guidelines.

Training costs represent a common concern. Staff familiar with proprietary software may require time to adjust to different interfaces and workflows. Studies consistently show that productivity returns to baseline within weeks for most users. The French Gendarmerie reported that comprehensive training programs effectively addressed this challenge.

Perceived compatibility issues also create hesitation. Decision-makers worry that document exchange with external partners might suffer. Modern LibreOffice versions handle Microsoft Office formats with high fidelity, though complex documents occasionally require adjustments. Organizations that standardize on open formats eliminate these concerns entirely.

Vendor relationships and existing contracts create inertia. Long-term licensing agreements and established support relationships make switching appear risky or complicated. Yet these arrangements often perpetuate the vendor lock-in that EU guidelines explicitly warn against.

What Actions Should the European Commission Take?

The Document Foundation's request implicitly calls for concrete actions. Addressing the policy-practice gap requires systematic changes to procurement processes and institutional culture.

The Commission should conduct a comprehensive audit of current software usage. This assessment would identify where proprietary solutions dominate and evaluate whether open-source alternatives could fulfill those needs. Transparency about current practices would demonstrate commitment to stated principles.

Procurement guidelines need enforcement mechanisms. Requiring justification when choosing proprietary over open-source options would ensure decision-makers consider alternatives seriously. This approach mirrors practices in some member states that mandate open-source evaluation.

Investment in transition support would address legitimate concerns. Allocating resources for training, migration planning, and technical assistance would remove barriers that currently discourage open-source adoption. The savings from reduced licensing costs could fund these initiatives.

The Commission should lead by example. High-profile migrations to open-source solutions would signal genuine commitment and provide templates for other institutions. Success stories from within EU institutions would carry more weight than external examples.

What Are the Broader Policy Implications?

This situation extends beyond LibreOffice or office suites. The disconnect between EU policy and practice affects the entire open-source ecosystem and Europe's technology strategy.

When EU institutions ignore their own guidelines, they undermine policy credibility. Member states, regional governments, and public sector organizations look to Commission practices as models. Inconsistency at the top level creates confusion and justifies non-compliance elsewhere.

The economic impact deserves consideration. European open-source projects depend on adoption and contribution from public institutions. When the Commission chooses proprietary alternatives, it diverts resources away from European software development. This pattern contradicts goals of building technological capacity within the EU.

Geopolitical considerations add another dimension. As technological competition intensifies globally, software dependencies create strategic vulnerabilities. The EU's digital sovereignty agenda recognizes this reality. Failing to implement open-source policies weakens Europe's position in an increasingly contested technology landscape.

What Can Other Organizations Learn?

The LibreOffice-Commission situation offers lessons for any organization considering open-source adoption. Understanding these takeaways helps avoid common pitfalls and implement successful transitions.

Policy commitments require accountability structures. Simply declaring support for open-source principles accomplishes little without mechanisms that translate words into actions. Organizations should establish clear evaluation criteria that give open-source options fair consideration during procurement.

Change management matters as much as technology. Successful migrations depend on comprehensive planning, stakeholder engagement, and adequate support resources. The technical capabilities of open-source software are rarely the limiting factor; organizational readiness determines outcomes.

Long-term thinking produces better results than short-term convenience. Initial switching costs may seem daunting, but vendor lock-in creates permanent dependencies that grow more expensive over time. Strategic planning that prioritizes independence and sustainability ultimately serves organizational interests better.

Frequently Asked Questions

What specific guidelines is LibreOffice asking the European Commission to follow?

LibreOffice references the European Commission's 2020 Open Source Software Strategy, which commits EU institutions to "think Open Source first" when procuring or developing software. The strategy emphasizes open standards, interoperability, and vendor neutrality as core principles. The European Interoperability Framework provides additional guidance recommending open-source consideration for public sector applications.

These documents collectively establish clear expectations that current procurement practices allegedly contradict. The Document Foundation argues that the Commission should implement the policies it has formally adopted.

Can LibreOffice really handle the complex needs of large institutions?

Multiple large-scale deployments demonstrate LibreOffice's institutional capabilities. The Italian Ministry of Defense successfully migrated 100,000 workstations, while France's Gendarmerie Nationale transitioned 72,000 computers. These organizations handle security-sensitive operations and complex document workflows.

LibreOffice supports all major file formats, offers comprehensive functionality across six applications, and provides enterprise support options through certified partners. Technical capabilities rarely limit successful adoption; organizational planning and change management determine outcomes.

Why do EU institutions continue using proprietary software despite official policies?

Several factors contribute to this pattern. Existing vendor relationships and long-term contracts create inertia that resists change. Decision-makers often perceive switching costs and training requirements as barriers, even when long-term savings justify transitions.

Institutional culture and individual familiarity with specific tools also play roles. Procurement processes may not include mechanisms that enforce policy compliance or require justification for choosing proprietary options over open-source alternatives.

What are the financial benefits of switching to LibreOffice?

Organizations typically reduce software licensing costs by 40-60% through strategic open-source adoption. The French Gendarmerie reported saving approximately 2 million euros annually after migrating to LibreOffice. These savings come from eliminated licensing fees, reduced vendor dependencies, and lower upgrade costs.

Continue learning: Next, explore apple's 512gb mac studio vanishes: what it means for you

Organizations can redirect these funds toward customization, training, and support