Arsenal Of Democracy: What Open Source Can Learn From the Motor City
summary
Draws direct parallels between Detroit’s manufacturing history and modern open source, arguing for concrete practices: adopt software bill of materials and make it queryable into dependency graphs, enforce build-time gates with in-toto and Sigstore, and apply kanban-like traceability to component provenance. Cites tooling used (semgrep, kube-audit), wartime scale (Ford River Rouge creates ~100,000 jobs) and outcomes (Detroit’s 2013 bankruptcy) as evidence that single-industry dependence and outsourced, opaque supply chains fail.
AI-written summary · about
chapters (17)
- 0:00Welcome
- 1:45Speaker background
- 2:49Detroit history
- 5:20Motor City rise
- 8:28WWII women workforce
- 9:54Post-war boom
- 10:55Urban decay causes
- 11:59Japanese competition crisis
- 13:2480s and 90s decline
- 14:4921st century recovery
- 16:35Inclusivity lessons
- 17:57Open source democratization
- 18:59Kanban in software
- 22:52Fault detection in dev
- 24:18Standardized builds monitoring
- 26:27Outsourcing risks
- 28:13Summary and call to action
related talks
19mDriving Automotive with Open Source: From Compliance to Collaboration
31mPanel Discussion: Open Source Enabling Industrial Innovation
39mPanel Discussion: Open Source as a Path for a Competitive Automotive Industry
48mLessons Learned from Open Source in Business
08m"Open Manufacturing..."
42mPanel Discussion: Advancing Innovation Through Open Source: Lessons from the Vertical Industries
01h 08m“What is Open Source, and Why Should You Care?"
26mOpen Source Design: A Call to Arms