Open Source Contributions in Today’s World
summary
Outlines specific legal changes — Cyber Resilience Act and Product Liability Directive — and how “distribution” now triggers license duties; recommends concrete repo files: notice file, SBOM and an authors file, plus embedding legal docs into artifacts (Meta-INF) for package managers. Advises automated scanning of transitive dependencies (suggested cadence: monthly) using OD or scan scan code or Black Duck, scanning every Docker layer before publishing to Docker Hub, avoiding needless image publication, and running snippet scanners on AI-generated code to prevent license leakage.
AI-written summary · about
chapters (7)
- 0:00Introduction and welcome
- 4:19Why license compliance matters
- 12:32Legal steps for contributions
- 18:59Building and distributing artifacts
- 21:27Docker images and compliance
- 25:44Cloud distribution and AI code
- 28:56Q&A and EU regulations
related talks
45mOpen Source distributions in a cloud-native world: from a technical to a legal point of view
25mOpen Source Compliance
19mDocker and Legal Compliance: Navigating the Containerized World
52mRisk management: best practices for people with legal compliance to ship open source
01h 38mOpen Source Licensing: Types, Strategies and Compliance
16mOpen Source Consumption/ Adoption Manifesto
14mOpen-source it right (and avoid calling your IP lawyer)!
31mOperationalizing Open Source Projects: When the Rubber Meets the Road