A well-designed Open Source Program Office (OSPO), when present, is the center of competency for an organization’s open source operations and structure. As described in the OSPO deep dive research report, OSPOs benefit organizations worldwide by:
- Implementing unique and flexible sets of tools that support OSS development models while meeting corporate Information Technology guidelines
- Overseeing the establishment or adaptation of internal policies to better manage open source software (OSS) compliance in fast-moving, dynamic environments
- Helping to bridge the cultural gap between traditional software development practices and the requirements of open source development
- Improving technical mentorship, and compliance-related education and training programming for team members across all levels of the organization
These strategic open source centers can take many shapes. For instance, depending on the size of the organization, its structure can vary from a virtual OSPO with one FTE to a large dedicated team. To learn more, please take a look at the different structures, roles, and responsibilities an organization can choose when builging an OSPO.
Tracking performance metrics is one of the key responsibilities of many OSPOs: OSPOs might use specialized tools to track their organization’s contributions to open source projects, analyze the type of contributions from their organization, identify contribution patterns, and provide recommendations to improve the development impact
Community initiatives do not reflect the same value as organizational efforts. The OSPO Metrics working group aims to advance how organizations understand the value that open source projects can provide as well as the value of these programs / initiatives.
Main objectives include:
- Define useful metrics
- Ease implementation with CHAOSS tooling
- Set up best practices and metrics standards for OSPOs
OSPO Metrics group will develop metrics that, when measured, help make the impact of community work more transparent. It will also help drive the adoption of metrics, implementation of best practices, and tools to adopt community health metrics standards, which OSPO practitioners can engage and contribute.
All contributors are welcome to participate in the Value Working Group. The areas of interest include social value, organizational value, individual value, communal value and academic value.
You can start by joining and introducing yourself on the CHAOSS mailing list explaining your interest.
Further, you are welcome to participate in our video conferences. The details of these meetings can be found here
Read the agenda and meeting minutes to know the discussions of the previous meetings and find out more about the next one. As a contributor, you can help us keep our community open and inclusive. We request you to adhere to the guidelines mentioned in the CHAOSS Community: Code of Conduct
See the CONTRIBUTING.md for more information.
We are compiling dimensions of value that can be used in the following areas of analysis:
| Focus Area | Goal |
|---|---|
| Social Value | Identify the degree to which a project is attentive to improving the lives of people beyond software. |
| Organizational Value | Identify the degree to which a project is monetarily valuable from an organization's perspective. |
| Individual Value | Identify the degree to which a project is valuable to me as an individual user or contributor. |
| Communal Value | Identify the degree to which a project is valuable to its community of users (including downstream projects) or contributors. |
| Academic Value | Identify the degree to which a project is valuable to researchers and academic institutions. |
We are involved in the release of CHAOSS metrics. Check out our published work at https://chaoss.community/metrics/
The translations of these metrics are available at chaoss/translations
Please feel free to contact our chairs in case you require any sort of assistance.
We greatly appreciate our contributors at CHAOSS and look forward to your joining us as well. All CHAOSS Project contributors are listed here
Are you eligible to be on this list? You are if you helped in any capacity, for example: Filed an issue. Created a Pull Request. Gave feedback on our work. The team will try to update this list regularly, but please open an issue or post on the mailing list if we've missed anyone.
CHAOSS OSPO Metrics working group is under the auspices of TODO Group, an open group of OSPO practitioners who aim to create and share knowledge, collaborate on practices and develop tools to run successful and effective Open Source Program Offices.
The documents in this repository are released under the MIT License. See LICENSE file.
Copyright © 2019-2022 - CHAOSS, a Linux Foundation Project