How to Accelerate Contribution in Auto...
summary
Automotive firms show up in few Linux kernel contributor rankings despite heavy OSS use, so concrete fixes include create an OSPO with contribution rules, scan codebase for heavy-use projects and quantify people and funding needs, set clear clearance lanes for low‑IP areas, and fund upstreaming of BSP/GPU drivers rather than shipping long‑lived binaries. Local community hubs (OpenChain Japan, AGL local meetings) and measurable KPIs — number of upstream patches, maintainers funded, and avoided IP incidents — prove value and lower risk.
AI-written summary · about
chapters (20)
- 0:00Accelerating automotive contributions
- 1:06Introduction
- 7:10Open source in automotive
- 8:14Open source contribution challenges
- 10:24Cultural and process barriers
- 13:35Open source in Japan
- 15:47License compliance and risk
- 17:54Mentoring and community
- 19:02Panasonic's open source strategy
- 20:52Upstream development shifts
- 21:36Language and cultural gaps
- 23:50Business value of open source
- 26:42Compliance and cost benefits
- 28:04Hiring and innovation
- 29:29Contributor perspectives
- 32:23Hardware dependency issues
- 34:28Upstreaming proprietary modules
- 37:01OEM supplier contributions
- 38:50Mindset shifts and policy
- 39:12Closing remarks
related talks
32mAsymmetries in Open Source: What Can Research Tell Us about Closing the Consumption-contribution Gap to Improve the Sustainability of OSS?
42mDoes Your OSPO Help or Hinder Contributions?
41mHow Your Company Can Help Sustain Open Source
39mOSPOs in Energy, Transport, Automotive & Public Sector
27mOpen Source: Supporting, Contributing and Evangelising
23mMaking the Business Case for Contributing to Open Source
23mOpen Source Contribution Policies that Don't Suck
11mContributing to Open Source