Open Source in Safety Critical Applications: the Next Frontier
summary
Argument: open source can meet safety needs but only with concrete tracing, scope-definitions and hardened subsets. Demonstrations include an OpenAPS Raspberry Pi loop that already controls insulin for users, Zephyr’s plan to freeze an LTS, extract and harden a small subset toward certification (target: ready by the next LTS in ~2 years), and a 50K‑LOC Xen hypervisor effort estimating 5–10 man‑years. ELISA coordinates weekly work and quarterly workshops, uses OpenAPS and autonomous driving as reference systems, and tracks Linux churn (tip ~9 changes/hour, stable ~1/hour).
AI-written summary · about
chapters (9)
- 0:00Safety critical software
- 1:25Historical lessons
- 3:21Modern case studies
- 5:09The culture clash
- 7:16Bridging the gap
- 10:48The Zephyr project
- 16:08The Xen hypervisor
- 17:55The ELISA project
- 26:04Conclusion and Q&A
related talks
32mDeveloping Open Source for Safety and Security
32mDeveloping Open Source for Safety and Security
40mBOF: Open Source Projects in Safety Critical Applications
05mKeynote: Evolution of Open Source for Safe Usage in Critical Systems
48mThe ELISA Project – Enabling Open Source in Safety-Critical Applications
48mDeveloping Open-Source Software RTOS with Functional Safety in Mind
45mSafety Certifying an Open Source Project: The Example of Xen- 05mKeynote: Evolution of Open Source for Safe Usage in Critical Systems