Open Source and Standards Collaboration
summary
Qualcomm reports participation in 400 standards bodies with about 2,000 employees involved and argues SDOs should adopt open-source tools like GitHub for issue tracking and public spec edits; gives IETF and OMA as examples and CNCF’s serverless white paper as a standards-like deliverable. Recommends clear IP policies (royalty‑free vs FRAND), a three-tier contribution process (fast paths for bug fixes/docs, low‑risk approvals, and board review for patent risk), and joint training and handoffs.
AI-written summary · about
chapters (9)
- 0:00Open source and standards intro
- 3:10Open source vs standards
- 7:35Why standards want open source
- 10:04Open source learns from standards
- 18:06Steps for collaboration
- 22:22Qualcomm’s internal collaboration
- 25:29Future of standards and open source
- 25:53Q&A: Contribution review
- 28:45Q&A: Future integration
related talks
31mOpen Source and Standards Collaboration
31mFrom Closed To Collaborative: Perspectives and Lessons From Qualcomm’s Open Development Experience
57mOpen Source, Standards Development and Patents in Europe
26mWhy Open Standards Power Compliance
49mTowards Open Source-Compatible Standards
11mOpen Source Standards: Toward a more diverse and equal internet
17mKeynote: Open Source and Standards: Better Together
22mStandards and Specifications at the Linux Foundation