Revising the Eclipse Foundation's Intellectual Property Due Diligence Process
summary
Eclipse Foundation retires IPzilla (deprecation announced Sept 30, 2022) and replaces it with a GitLab-based IP Lab using ORT that automatically scans repos with ScanCode, produces SPDX/CycloneDX SBOMs and drives reviews; a Dash License Tool automates checks against the Foundation DB and ClearlyDefined and files IP lab records; builds still require release reviews and any PR >1,000 lines triggers provenance checks; automation cuts routine work (target ~80% clean runs) while hard license compatibility and native build cases remain manual.
AI-written summary · about
chapters (15)
- 0:00Updated IP due diligence process
- 1:09Eclipse IP due diligence history
- 3:18Shift to license compliance
- 5:23Automation in IP due diligence
- 9:24IP policy update impacts
- 13:12IP lab as new repository
- 17:06Code contributions and repo changes
- 20:39Committer challenges and solutions
- 24:13Eclipse Dash License Tool
- 26:20OSS Review Toolkit overview
- 30:36License compatibility hard cases
- 33:27Standards and community collaboration
- 35:15License scanning and SPDX adoption
- 36:39REUSE for tracking licenses
- 38:48Q&A
related talks
39mIntellectual Property Due Diligence @ Eclipse – Past, Present, & Future
46mEclipse Foundation IP Process Primer
28mEMO & YOU
01h 21mOpen Source Best Practices at Eclipse Foundation
50mEclipse Apoapsis - Open Source based Software Composition Analysis at scale
37mThe Eclipse Development Process for Committers
47mPolicing Open-Source Projects at Scale
43mEclipse Oniro compliance toolchain