Summary Under the proposed Cloud and AI Development Act (CADA), the European Commission is required to convene and chair meetings of the Open Source Programme Office (OSPO) Network at least twice a year. As proposed in Article 44(5), these meetings "may be organised online" to ensure broad participation across the Union. The Commission also holds the responsibility to "support and coordinate" the network under Article 44(4), ensuring that public sector bodies can effectively exchange best practices on open-source software licensing, security, and procurement.

Detail

The proposed Cloud and AI Development Act (CADA), COM(2026) 502 final, introduces a comprehensive framework to strengthen Europe's cloud and AI ecosystem. A critical component of this framework is the promotion of open-source solutions to reduce vendor lock-in and enhance technological sovereignty. To operationalise this, Article 44 establishes a dedicated network of Open Source Programme Offices (OSPOs).

Establishment and Scope

Article 44(1) mandates that the Commission "shall establish a network of Open Source Programme Offices ('OSPO Network') to facilitate cooperation on the implementation of the obligations under this Chapter." The network is designed to be inclusive and multi-level. Under Article 44(2), it is open to OSPOs established by public sector bodies at local, regional, or national levels within Member States, as well as those established by Union entities. These bodies may request to join the network from the Commission.

Core Tasks and Objectives

The OSPO Network is not merely a forum for discussion; it has specific, defined tasks under Article 44(3) to advance the EU's open-source strategy. These tasks include:

  • Facilitating Exchange: Promoting the exchange of information, experience, and best practices between Member States and the Commission. This covers common technical, legal, and organisational challenges, including licensing, security, maintenance, and procurement of open-source software.
  • Promoting Reuse: Actively promoting the sharing and reuse of open-source software by public sector bodies.
  • Developing Guidance: Contributing, on a "voluntary and non-binding basis," to the development of guidance, templates, or recommendations on sharing and reusing open-source software.
  • Project Collaboration: Collaborating on and exchanging open-source projects of common interest to Union entities and public sector bodies.

Meeting Frequency and Format

The operational rhythm of the network is explicitly defined to ensure consistency and engagement. Article 44(5) states: "The Commission shall convene and chair a meeting of the members of the OSPO Network at least twice a year." This biannual minimum ensures that the network remains active and responsive to the rapidly evolving open-source landscape.

Crucially, the proposal recognises the logistical challenges of physical gatherings across the EU. Article 44(5) further clarifies that "The meetings of the OSPO Network may be organised online." This provision ensures that participation is not limited by geography or budget, allowing for broader and more inclusive engagement from local and regional bodies.

The Commission's Coordination Role

The Commission acts as the central hub for this network. Article 44(4) explicitly mandates that "The Commission shall support and coordinate the OSPO Network." This role is vital for aligning the network's activities with broader EU digital policies, such as the Interoperable Europe Act and the EU Open Source Strategy. By supporting and coordinating, the Commission ensures that the voluntary guidance and templates developed by the network are consistent, high-quality, and aligned with Union objectives.

Context within the CADA Framework

The OSPO Network functions as the human and institutional bridge for the technical and legal measures in Title IV of CADA. It complements:

  • Article 43: Which requires the Commission to maintain an EU Open Source Solutions Catalogue.
  • Article 42: Which obliges Union entities and public sector bodies to share software developed by or for them in catalogues connected to the central EU OSS Catalogue.
  • Article 41: Which encourages the use of open standards and components released under an open-source licence.

The network ensures that the entities managing these catalogues and implementing these obligations can learn from one another, creating a cohesive ecosystem rather than fragmented national efforts.

What this means for you

For public-sector bodies, procurement officers, and IT strategists, the establishment of the OSPO Network and its mandated schedule offers tangible benefits:

  1. Regular Access to Expertise: With meetings convened at least twice a year, your organisation will have predictable opportunities to access shared guidance on complex issues like open-source licensing, security vulnerabilities, and maintenance strategies. This reduces the risk of reinventing the wheel for every project.
  2. Standardised Tools: The network's voluntary contribution to templates and recommendations (Article 44(3)(c)) means you can expect to receive standardised resources for evaluating and managing open-source software, streamlining compliance with CADA obligations.
  3. Collaborative Procurement: The network facilitates the exchange of projects of common interest. This could allow your organisation to leverage software developed by other Member States or Union entities, significantly reducing development costs and accelerating time-to-market for public services.
  4. Low-Barrier Participation: The explicit allowance for online meetings (Article 44(5)) removes travel barriers. This is particularly beneficial for smaller local or regional bodies that might otherwise lack the resources to attend physical summits, ensuring their voices are heard in EU-wide policy discussions.

To prepare, ensure your organisation has a designated contact or office responsible for open-source strategy. This entity will be the primary point of contact for requesting membership in the OSPO Network and participating in its biannual meetings.

Common misconceptions

  • Misconception: The OSPO Network is a regulatory body that can impose fines or binding rules.
    • Reality: The network is a cooperative and advisory body. As stated in Article 44(3)(c), its contributions to guidance and templates are "voluntary and non-binding." It facilitates best practices rather than enforcing penalties.
  • Misconception: Only large national governments or major agencies can participate.
    • Reality: Article 44(2) explicitly opens the network to OSPOs at "local, regional or national level." This includes smaller public sector bodies, provided they have an established OSPO or equivalent structure.
  • Misconception: Meetings must be held in person in Brussels.
    • Reality: Article 44(5) explicitly states that meetings "may be organised online," facilitating broader and more inclusive participation across the entire EU without the need for travel.
  • Misconception: The Commission only observes the network.
    • Reality: The Commission has an active mandate to "support and coordinate" the network under Article 44(4) and is required to "convene and chair" the meetings under Article 44(5).

Related

This is general information about a draft EU regulation, not legal advice.