A-Typical but Fruitful Public Sector Collaborations Through OSPO's
summary
Two Dutch OSPOs pair a public tax agency with a semi‑public grid operator and grow a national network from two to 18 organizations through biweekly working groups, shared GitHub knowledge bases and a public site. They build SBOM pipelines (prototype → production), pick CycloneDX SBOMs for standardization work and run an OSPO code scanner and scorecards to audit projects. Automation and an open‑source checklist accelerate publishing; a government index already lists about 2700 repositories and a national SBOM standard request is filed.
AI-written summary · about
chapters (8)
- 0:00Welcome
- 1:51Collaboration origins
- 10:04Alander versus Dutch Tax
- 18:13Growing public sector OS community
- 27:45Standardizing software bills of materials in the Netherlands
- 34:30Call to action
- 44:15Vendor requirements
- 50:23Open sourcing government projects
related talks
37mBuilding an OSPO: The Alliander Experiences
30mBuilding OSPOs in Practice...
13mOpen Source Collaboration by Public Sector Stakeholders
43mRise of the OSPO in Industry, Academia & Municipal Gov.
29mPanel Discussion: The Rise of OSPOs in Grid Operations: Insights and Lessons From Hydro-Québec...
36mThe Evolution of OSPOs
32mOSPOs in the public sector
34mThe Role of OSPO Manager for the Organization’s Success
