An Open Source Program Office (OSPO) is a department formed by subject-matter experts involved in free and open software. This team may also oversee the operation of open standards and Digital public goods. It often includes an understanding of legal compliance issues and risk management, but is not limited to this. OSPOs can also play a role in culture change within an organization.

Details

Numerous companies have OSPOs, such as Yahoo!,[1] Goldman Sachs,[2] Bloomberg L.P., Comcast or Porsche,[3] and universities like Trinity College Dublin,[4] the University of Vermont,[5] or Johns Hopkins University.[6] The US Government's Centers for Medicare & Medicaid Services has also established an OSPO to help them improve organizational effectiveness.[7][8]

The tasks of an OSPO include both business oriented goals:

and technical and legal compliance issues such as:

  • Technical support of projects
  • Maintenance of public and private repositories on GitHub and GitLab for version control.[12][13]
  • Release for use of free software
  • Documentation of dependencies in used or included free software to prevent vulnerability or software license violations from third-party software.
  • Creation and monitoring of license compliance policies of free-software licenses in deployed applications or published products[11][9][3][14][15]

References

  1. ^ "The Open Source Program Office". Open Source Guide. Archived from the original on 2023-05-17. Retrieved 2023-05-17.
  2. ^ Goldman Sachs' Open Source Program Office, One Year In
  3. ^ a b c "The Evolution of the Open Source Program Office (OSPO)". www.linuxfoundation.org. Archived from the original on 2023-04-29. Retrieved 2023-05-17.
  4. ^ "Open Source Program Office - Trinity Innovation - Trinity College Dublin". www.tcd.ie.
  5. ^ "About". VERSO. Retrieved 2025-01-16.
  6. ^ "Open Source Programs Office (OSPO)". Archived from the original on 2023-05-29. Retrieved 2023-05-17.
  7. ^ "Open Source Program Office | CMS". www.cms.gov. Retrieved 2025-01-22.
  8. ^ "How one federal agency worked to release open source software responsibly". www.usdigitalresponse.org. Retrieved 2025-01-22.
  9. ^ a b "Why have an open source program office?". www.redhat.com. Archived from the original on 2023-05-04. Retrieved 2023-05-17.
  10. ^ Executive Mosaic (2023-10-26). Inside CMS’s Ground-Breaking Open Source Program Office [e-session]. Retrieved 2025-01-22 – via YouTube.
  11. ^ a b c github.com/todogroup/ospodefinition.org Archived 2023-04-30 at the Wayback Machine Open Source Program Office (OSPO) definition of todogroup
  12. ^ The Linux Foundation (2024-04-26). Repository Cohorts: How OSPOs... - James Siri, Natalia Luzuriaga, Remy DeCausemaker & Isaac Milarsky. Retrieved 2025-01-22 – via YouTube.
  13. ^ The Linux Foundation (2024-04-26). Establishing a Baseline: Repo Metrics, Ma... - Natalia Luzuriaga, Remy DeCausemaker & Isaac Milarsky. Retrieved 2025-01-22 – via YouTube.
  14. ^ Project, CHAOSS. "Managing Federal CHAOSS at CMS.gov". CHAOSScast. Retrieved 2025-01-22.
  15. ^ Archived 2023-04-30 at the Wayback Machine
No tags for this post.