Connecting Open Source Projects with Public Institutions
summary
Proposes creating formal channels so open source projects and public institutions share roadmaps and bug reports, run joint code reviews, and announce who uses what. Uses the widely deployed Spring Framework as an example and cites the city of Munich sabbatical that produces upstream contributions. Claims projects now lack visibility into public-sector users, leading to missed fixes and non‑idiomatic apps, and shows that structured exchange yields faster security patches, practical guidance, and reusable public‑sector code.
AI-written summary · about
related talks
21mScaling Internal Collaboration with Open Source Operating Models
58mOpen source ecosystem and the public sector, toward mature collaboration
32mMunicipal collaboration on open source software - Why is it so hard?
42mPanel Discussion: Advancing Innovation Through Open Source: Lessons from the Vertical Industries
42mHow Development and Collaboration is Done in Public Sector Open Source Software Projects
45mInnerSource and OSPOs: Institutionalizing Open Source Culture Change
13mOpen Source Collaboration by Public Sector Stakeholders
15mApplying Open Source Principles to Federal Government