Eclipse Foundation IP Process Primer
summary
Eclipse Foundation runs IP checks to keep commercial adoption low-risk: project names and domains (GlassFish) become Foundation trademarks, contributor/committer agreements clarify ownership, and code contributions over 1,000 lines trigger a review. Third‑party content follows two tracks—Type A for quick, license-only clears and Type B for provenance and deeper scans—plus fast‑tracks for semantic patch releases. Analysts use tooling like mighty Silla and scancode/encode scans, maintain a CQ backlog, and convert Type A projects to Type B when more assurance is required.
AI-written summary · about
chapters (9)
- 0:00Intellectual property basics
- 2:04Trademarks and legal records
- 7:07Committer agreements
- 11:17Due diligence and tooling
- 18:47Review types and processes
- 25:01Contribution requirements
- 28:43Managing dependencies
- 33:48Optimizing approval timelines
- 39:03Best practices and resources
related talks
39mIntellectual Property Due Diligence @ Eclipse – Past, Present, & Future
39mRevising the Eclipse Foundation's Intellectual Property Due Diligence Process
23mManaging the unmanageable: community driven projects at Eclipse Foundation
28mEMO & YOU
22mWelcome Message
01h 21mOpen Source Best Practices at Eclipse Foundation
16mA Journey of Contribution and Collaboration in Open Source
31mDevelopment Process 101