An Inside and Outside Look at the Government’s Ongoing Journey with Open Source Tech
summary
Government programs report ~86–90% of projects include open source, run 1,600 nightly rebuilt images through Iron Bank, and require signed SBOMs plus CVE triage rather than blind “zero CVE” goals. Examples: a failed fork of Rocket.Chat consumed 18 months of effort; a successful SBIR-funded project zarf delivers air‑gapped deployments and now sees NATO users. Practical advice: assess license and maintainer diversity, pick a release cadence that matches your change-control, and invest in relationships to upstream fixes and buy long‑term support.
AI-written summary · about
chapters (8)
- 0:00Introduction and speakers
- 2:50Government software vocabulary
- 7:41Open source licensing models
- 13:56Mission risk and innovation
- 18:52Open sourcing after project
- 23:46Government funding open source
- 26:55Key takeaways and advice
- 31:50Q&A and resources
related talks
15mApplying Open Source Principles to Federal Government
38mOpen Source in the Federal Government
39mSOS: Sustainable Open Source
23mPublic Sector: Stories to Getting Started
41mArchitecting for the Long Haul: Technical Strategies for Sustainable Open-Source Support Models
49mTrustworthy Open Source: The Consequences of Success
47m11,000 Voices: Experts Shed Light on 4-Year Open Source & AppSec Survey
41mBack to Security Basics: Evaluating, Consuming, and Contributing Open Source...