Open Source Program Office Case Study Guidelines

The TODO OSPO Case Study initiative features real-world use cases and the impact OSPO Programs and open source are having on an organization. OSPO Use Cases build narratives around open source organization’s journey that includes Open Source Program Office highlighted activities, organizational structure, best practices, goals, and success stories, showcasing rganizations as leaders in the OSPO and open source management ecosystem.


Who can be featured in an OSPO Case Study?

As a rule, OSPO case studies feature:

All case studies must demonstrate at least one tangible business impact of OSPOs or open source management within the organization and/or the open source ecosystem. Examples from published case studies include:

OSPO Case Study Process

OSPO case studies follow a self-service model with editorial support and guidance provided by TODO Group and the Linux Foundation.

The self-service follows a five-step process:

1. Proposal

Organizations submit a case study proposal via a Github Issue form

IMPORTANT: This form is still in work in progress. Meanwhile, interested participants, please open an issue using the ‘use case’ tag providing a description.

2. Review

3. Creation

Primary contact writes a case study following the required style documented in the case study pack

4. Editing

5. Publishing

6. Promotion

To get started

Propose a case study and send it to the team directly by opening a issue using the use case tag

If you have any questions or feedback about the OSPO Case Study initiative, please send an email to