Open-source it right (and avoid calling your IP lawyer)!
summary
Checklist for publishing code: determine copyright (often employer-owned), pick a compatible license, and automate checks. Demonstrations show using SPDX metadata plus the REUSAE-style workflow, adding a licenses directory and a reuse.toml file, running a reuse scanner and a GitHub Action that emits a compliance badge, and producing a software bill of materials. Example repositories have surprising mixed licenses (LGPL vs NCSA) and missing copyrights that get fixed before release.
AI-written summary · about
chapters (12)
- 0:00Welcome to open source
- 1:07What is open source licenses
- 2:15Publishing code checklist
- 3:40Choosing the right license
- 5:09License classes and compatibility
- 6:33Best practices for files
- 7:15Managing multiple licenses
- 8:00REUSE framework
- 10:06Implementing REUSE
- 11:11Open source compliance
- 13:00Risk mitigation in open source
- 13:43Q&A
related talks
33mREUSE: Making Free Software Licensing Easier For All
50mRunning a Successful Open Source Project
31mOperationalizing Open Source Projects: When the Rubber Meets the Road
57mWhat You Need to Know About Open Source—Trust Me, I'm a Lawyer
32mOpen Source Contributions in Today’s World
49mLicense to Kill One's Code
45mOpen Source distributions in a cloud-native world: from a technical to a legal point of view
01h 38mOpen Source Licensing: Types, Strategies and Compliance
