Intellectual Property Due Diligence @ Eclipse – Past, Present, & Future
summary
Eclipse Foundation describes a concrete IP workflow: replacing IPZilla with a GitLab-based IPLab that integrates the Dash License Tool plus ScanCode and Fossology to scan source, and targets about 80% automation of approvals so the IP team focuses on the remaining 20%. Contributions require signed ECAs and committer agreements, projects must publish accurate metadata or CycloneDX SBOMs, and generated code is currently discouraged until legal and licensing questions are resolved.
AI-written summary · about
chapters (10)
- 0:00IP due diligence at Eclipse
- 2:15Eclipse’s IP process
- 4:01Eclipse’s IP review evolution
- 6:25AI in IP due diligence
- 8:52Source code requirements
- 12:10Contributor agreements
- 16:24Licensing and copyright
- 23:27Dash License Tool
- 30:51Automated IP approval
- 34:04AI-generated content in open source
related talks
39mRevising the Eclipse Foundation's Intellectual Property Due Diligence Process
46mEclipse Foundation IP Process Primer
31mDevelopment Process 101
01h 21mOpen Source Best Practices at Eclipse Foundation
37mThe Eclipse Development Process for Committers
50mEclipse Apoapsis - Open Source based Software Composition Analysis at scale
22mWelcome Message
47mPolicing Open-Source Projects at Scale