Software-Defined Vehicles and FOSS
summary
Software-defined vehicles face concrete challenges: cars already run on 100+ ECUs with 6–10k engineers per program, and software stacks reach roughly 150M lines of code that require 10–15 year maintenance cycles. Building a full in-house platform costs on the order of $830M from-scratch (lower upgrades still hit ~€200M), so the push is toward API-first designs, shared open-source maintenance, long-term funded community stewardship, and clear contracts that separate spec from implementation.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:23Software-defined vehicles
- 2:52OEMs' higher abstraction
- 4:21Open platform challenges
- 6:11Trust and legal hurdles
- 7:34SDV technical principles
- 9:00Hardware to software shift
- 10:47Open source ROI
- 13:00From directed to organic open source
- 16:14Governance and collaboration
- 18:45Maintaining open source economics
- 21:17Calendar vs long-term
- 22:40Strategic vs tactical priorities
- 24:38Safety and security
- 27:28Future of software-defined vehicles
related talks
19mDriving Open Source
22mSteering into Tomorrow: Embracing Software-Defined Vehicle in an Open-Source Appro...
39mPanel Discussion: Open Source as a Path for a Competitive Automotive Industry
50mHow To Accelerate Software Defined Vehicle(SDV) With OSS
42mAccelerating Software Defined Vehicles Through Open Source Software
35mAccelerating Software Defined Vehicles Through Open Source Software
39mMobility of the Future and Open Collaboration – A good Idea?
28mThe future of automotive is software defined!