Software Reuse through Open Source Software in the Public Sector
summary
Research for the Danish Agency compiles 16-country survey case studies and finds two decisive policy splits: an internal vs external focus (government consumption vs industrial promotion) and inbound vs outbound rules (procurement reuse vs publishing code). Concrete outcomes include national catalogs and hosted GitLab instances, community stewards like OS2 with 80–90 municipalities and 25–30 projects, Italy’s 2012 law only enforced after 2020 procurement guidelines, and adoption of publiccode.yml metadata to make public software findable.
AI-written summary · about
chapters (19)
- 0:00Open source in public sector
- 3:53Research background
- 7:25Internal vs external policy
- 10:15Inbound vs outbound policies
- 12:01Policy prescriptiveness
- 16:59Economic arguments for OSS
- 21:37Digital sovereignty
- 25:20Policy adoption cycles
- 27:50Open source program offices
- 31:21Policy to practice
- 34:14Software catalogs
- 37:45Sustainable maintenance
- 40:16OSS for policy goals
- 43:27Public sector contributions
- 45:15Industrial policy & ecosystems
- 48:31Research gaps & future
- 50:00Q&A: Free software
- 58:08Q&A: OSS security
- 1:01:02Q&A: OSS adoption in Global South
related talks
27mOpen Source in Local Governments: Lessons from across the EU
42mPanel: Open Source in the Dutch (Semi) Public Sector: Strategies, Challenges & Digital Sovereignty
30mOpen Source and Public Policy
42mHow Development and Collaboration is Done in Public Sector Open Source Software Projects
27mOpen Source at the European Commission
23mPanel Discussion: Public & Private Support of the Open Source Ecosystem
27mProgress and trends in the national open source policies
13mOpen Source Collaboration by Public Sector Stakeholders