About this initiative
Open Source Program Offices have emerged in the private sector as a way for companies to increase their use and production of Free and Open Source software. Recently, several public sector organizations around the world have established their own OSPOs to embrace FLOSS principles and participate in this ecosystem.
How many public sector OSPOs are there? What are their FLOSS policies? Do they produce significant Free Software? How can you get in touch with them? We are a group of volunteers willing to build this list of public sector OSPOs, promote their achievements and create opportunities for them to work together.
The OSPO Alliance serves as an umbrella for this project, currently maintained by Boris Baldassari (Eclipse Foundation), Philippe Bareille (City of Paris) and Bastien Guerry (DINUM, France). We welcome more maintainers! Just send us an email.
Using the list
The list of public sector Open Source Program Offices (OSPOs) is available for download here.
It is published under the Creative Commons CC0 license, allowing for unrestricted reuse and distribution.
Adding your organisation
This list is built from a set of YAML files that can be found in our git repository. If the organisation sent us a URL to fetch the file from, we update it regularly and store it.
There are three options to have your organisation listed here.
- Sending the YAML file to us. The YAML file can either be hand-crafted, as long as it follows the schema described below, or it can be generated from the OSPOMeta YAML generator. This tool is developed and maintained at OSPOMeta.
- If the YAML file is maintained in your own repository, you can send us the link to the file in the git repository, and it will be automatically fetched and treated on a regular basis.
- By directly submitting a MR in our repository, if you feel comfortable doing so.
About the YAML file
We reuse in this initiative the YAML format defined by OSPOMeta. See their repository to contribute, discuss or learn more.
[URL of the OSPO]:
name: the name of the OSPO
description:
en: One-sentence description of the OSPO and its context.
email: (optional) OSPO generic email address
created: the creation date of the OSPO, e.g. 2022-06-01
floss_policy: (optional) link to the FLOSS policy published by the OSPO
country: FR|DE|DK...
code: (optional)
- https://code1
resources: (optional)
- https://presentation1
We welcome contributions in the form of PRs. If you have any question, please send us a message!