Policy Work Today and the New International Context
summary
Explains how regulators now treat software as infrastructure, using the Cyber Resilience Act (CRA) and AI Act as concrete pressures that change licensing into market rules; cites Jeep’s faulty update as why governments list essential services and audit software. Details left for implementation include voluntary attestation, category definitions and standards that create a presumption of compliance, and a 2027 date when CRA fines become applicable. Argues for project-foundation-company coordination, mutual recognition agreements, and the open regulatory compliance working group to reduce fragmentation.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 0:53Digital sovereignty and new context
- 5:09Cyber Resilience Act shift
- 9:45Need for policy expertise
- 12:38International coordination
- 21:10FOSS in legislation challenges
- 25:51Conflicting global regulations
- 30:23Making CRA a success
- 33:15Open compliance working group
related talks
39mFrom Policy Enthusiast to Legislators' Contact Point
42mPanel Discussion: The Impact of the CRA on the Open Source Ecosystem
34mHow Community Collaboration is Fixing the Future of Tech Regulation
24mThe CRA Challenge: Can Open Source and IoT Stay Agile Under Regulation?
14mThe CRA: an Open Source Sustainability law?
15mCRA & PLD Liability rules and Software Freedom
33mImplementing the EU Cyber Resilience Act (CRA)
25mSecure or Sorry: Your software is now a European Product