Safety Processes
summary
Proposal defines an Eclipse SDV process that makes open source components easier to adopt by OEMs and tiers, not by certifying projects but by making them certification ready through low‑level content quality practices, continuous compliance, and a badge system for compliance claims. References include Linux Foundation ELISA, Zephyr/Safi work, and use of SPDX toolchain to carry safety artifacts; Rust toolchains and ISO 26262/MISRA alignment are evaluated as concrete enablers.
AI-written summary · about
chapters (4)
- 0:00Start
- 1:06Software Defined Vehicle
- 16:38Comparing ctools checks to stock Rust
- 18:29ISO 26262 Part six and Rust
related talks
42mZephyr Functional Safety BOF
20mSecure Software Development Lifecycle
53mBridging Safety and Architecture: Zephyr’s Path To IEC 61508 Complian...
30mFast, Lean, Precise, Controlled: Compliance Automation With OSCAL in Our Open-S...
37mTools and Methodologies to Test Compliance with IEC61508 Standard
41mIs Linux Kernel Development Good Enough to Make Your Life Depend on It?
42mAction and Impact Panel: How OpenSSF and Industry Improve Open Source Security
18mKeynote: Challenges in Industrializing OSS and How Siemens Tackles Them
