Brussels / 30 & 31 January 2016


Jeremiah C. Foster

Photo of Jeremiah C. Foster

What is the "safety-critical" domain? What challenges does it present to Free Software with regard to process? Can FOSS become "safety-critical"? What are the implications of using copyleft licenses in safety-critical software? What is the roadmap? What resources to engage in the discussion is available?

I will try and have a short presentation on what safety-critical software is, where its used, and why its important that software freedom is part of the domain. I will discuss some concrete results towards a GNU/Linux software stack that may be a candidate for certification for safety-critical use. Lastly, I'd like very much to engage the audience on the subject matter, particularly on the dynamic of copyleft and how it may provide a greater level of transparency than proprietary software not just into the actual code but in the entire process and supply chain and hardware. Copyleft may be an effective mechanism to ensure a necessary level of transparency as well as adequate protection for source cod e that is expensive to produce and maintain.


Title Day Room Track Start End
Free Software Automotive stack(s) that run on available hardware
with a demo on the Raspberry Pi 2
Saturday UD2.120 (Chavanne) Embedded, Mobile and Automotive 17:00 17:50
Status of safety-critical FOSS Sunday UD2.218A Legal and Policy Issues 14:00 14:25