Open Source and Standards Collaboration
summary
Qualcomm explains how corporate ISPO and OSPO coordinate across 400 standards bodies with 2,000 participants, showing concrete practices: standards groups (OMA, IETF) put specs and issue tracking on GitHub, IETF runs hackathons, CNCF publishes a service white paper as a standardized API. Key internal controls: compulsory open source training, aligned handoffs between open source and standards reviews, and a three-tier review that fast-tracks bug fixes/docs while escalating patent-sensitive work. Recommendations: attach clear IP policy pointers to code and choose royalty-free vs FRAND per R&D risk.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 7:22Open Source and Standards Collaboration
- 9:55Can Open Source Improve Collaboration
- 15:33IP Policy
- 17:53What Can We Do
- 18:36What You Can Learn
- 20:19Industry Standards
- 22:19Qualcomms Collaboration
- 24:45Future Collaboration
- 25:35QA
related talks
31mOpen Source and Standards Collaboration
40mThree Cs to an Open Source Program Office
26mNavigating Open Source: Establishing an OSPO for Organizational Success
49mTowards Open Source-Compatible Standards
28mGoverning Open Source in the Enterprise: OSPO Strategies for Innovation and Compliance
57mOpen Source, Standards Development and Patents in Europe
13mKeynote: Setting the Standard - Safely Operationalizing OSS Contributions
29mOpen Source and IP Departments: Risk Containment and Portfolio Management