Panel Discussion: Driving Automotive...
summary
Automotive companies report concrete shifts: a modern E‑Class already contains 3,000 FOSS components, Toyota establishes an OSPO in January after 15 years of community work, and collaboration projects like AGL and a safe open vehicle core aim to replace vendor lock‑in. Production timelines shrink from multi‑year to nine months from RFQ to production in fast programs, pushing CI/CD, OTA updates, and continuous compliance. Challenges remain around safety certification, CRA supply‑chain transparency, and early-stage open hardware sharing, but several OEMs and suppliers are already making these changes operational.
AI-written summary · about
chapters (14)
- 0:00Panelists and focus
- 1:54Open source shifts in auto
- 6:38Collaboration and antitrust
- 9:29Software evolution and areas
- 12:01Why invest in open source
- 15:52Inner source vs program office
- 17:37Hardware platform challenges
- 20:26Classic cars and longevity
- 23:12Right to repair and standards
- 25:01CRA impact on compliance
- 28:53Continuous compliance and certification
- 30:03Ecosystem consolidation
- 33:10Autonomous driving models
- 35:17Closing remarks
related talks
19mDriving Automotive with Open Source: From Compliance to Collaboration
39mPanel Discussion: Open Source as a Path for a Competitive Automotive Industry
35mDriving the automotive industry into the future with Open Source
43mPanel Discussion: The Automotive OSPO
40mOpen Source in Automotive BoF
33mOpen Source has arrived in Automotive! Open Collaboration for the Automotive Industry
31mPanel Discussion: Open Source Enabling Industrial Innovation
35mAccelerating Software Defined Vehicles Through Open Source Software