Why EU Policy Making matters to everyone in the Open Source Ecosystem
summary
EU laws like the Cyber Resilience Act, AI Act and Product Liability Directive change liability for software companies by treating placed-on-market software as a regulated product, with recital 10 explicitly mentioning free and open source software and creating a real risk that FOSS becomes an unintended casualty. Negotiations are fast, implementation windows discuss 36–48 months, and technical detail moves into standards via selc. Recommended responses: fund OSBA/Appel, build OSPOs, hire policy professionals, join standardization workstreams to influence how obligations are defined.
AI-written summary · about
chapters (14)
- 0:00Introduction to EU policy impact
- 2:19Why EU policy matters now
- 6:13Open source as inherently political
- 8:41Cyber Resilience Act and AI Act explained
- 13:16Ecosystem-level effects of regulations
- 16:53New era of software governance
- 20:26Building EU-wide open source institutions
- 23:04Positive vision for open source future
- 25:14Q&A: CRA timeline and impact
- 28:46Q&A: How open source becomes a casualty
- 33:48Q&A: Communicating open source complexity
- 37:19Q&A: Politicians' understanding of open source
- 40:16Q&A: Breaking the zero-start cycle
- 44:53Closing and thank you
related talks
39mAll your code belongs to Policy Makers, Politicians and the Law
01h 03mHow EU regulations affect OSPOs work and why you should care
54mSpeaking Up For FOSS Now Everyone Uses It
33mEU cybersecurity regulation and Open Source governance
39mFrom Policy Enthusiast to Legislators' Contact Point
18mOpen Source in EU Policy
36mDoes EU regulation care about ethics?
37mEUs Efforts to Secure Open Source Software