🠄 Back to blog

The Two Faces of a Public-Sector OSPO

2024-02-13

Open Source Program Offices (OSPOs) have emerged as crucial entities within organizations aiming to harness the power of open source software. While the concept has been established in the private sector for the last 10 years or so, the role of an OSPO within the public sector is still evolving and carries unique responsibilities.

We argue that a public-sector OSPO operates with a dual mandate, encompassing both internal and external-facing functions. This duality reflects the public sector's commitment to not only leveraging open source for internal efficiency and innovation but also to actively contributing to and shaping the broader open source ecosystem (public services, businesses, non-profits, individuals...) for the public good.

This document outlines what we believe should be the core responsibilities of a public-sector OSPO, highlighting the distinct yet interconnected nature of its internal and external mandates.

Internal mandate

  1. Lead the development of a strategic vision for open source software within the State: Develop an internal policy that encompasses digital sovereignty, ethical and responsible digital technology, and sustainable economic development.

  2. Communicate the strategy within the State and to public bodies: Ensure that the open source vision and objectives are well understood and integrated within the various government departments.

  3. Own and oversee the execution of the strategy: Prioritise and oversee internal projects that maximise the impact of using open source.

  4. Facilitate the effective use of open source software in the State's digital services: Optimise the adoption of open source in administrative procedures and other internal digital services.

  5. Create and lead communities of users and producers of open source software within the administration: Encourage an open source culture among government employees.

  6. Train staff involved in implementing the strategy: Develop the internal skills needed to support and promote the use of open source software.

  7. Provide or connect with the necessary expertise: Ensure access to the technical, legal and organisational resources and knowledge required to implement the open source strategy.

  8. Carry out inventories of open source software used and produced by the State: Monitor and evaluate the use of open source software in order to better steer the strategy.

External mandate

  1. Engage with ecosystems that produce open source software: Collaborate with publishers, developer communities and the academic world to support and contribute to external open source projects.

  2. Coordinate with OSPOs in other entities: Work with OSPOs in the European Commission, Member States, local and regional authorities, and businesses to strengthen the wider open source ecosystem.

  3. Coordinate with organisations representing open source companies: Strengthen the competitiveness of the open source sector by working with publishers and service providers.

  4. Ensure that open source software used and produced meets security requirements: Coordinate with security agencies to guarantee the security of adopted and contributed open source software.

  5. Participate in the stabilisation and sustainability of open source software: Get involved in open source software markets to support the sustainability of the ecosystem.

These distinctions between internal and external mandates underline OSPO's holistic approach, highlighting the need for a strong internal strategy while actively engaging with and contributing to the wider open source community.