Managing the unmanageable: community driven projects at Eclipse Foundation
summary
Eclipse Foundation runs a 17‑year old EU non‑profit hosting 450+ projects across 18 working groups with ~320 member organizations, offering git repos, issue trackers, IP management, CVE support and builds; project committers hold decision authority under a meritocratic invitations process, and projects have no private channels so everything is public. Working groups fund program managers, the Eclipse Marketplace, contractors for specific tasks, and coordinate multi‑project outputs via the simultaneous release and planning councils (example: Jakarta EE specs and GlassFish TCKs).
AI-written summary · about
chapters (13)
- 0:00Introduction and speaker intro
- 1:07Eclipse Foundation success definition
- 2:10Open source project structures
- 3:13Open source rules of engagement
- 5:20Committers as decision makers
- 7:25Project participation rules
- 8:48Working groups overview
- 10:13Working groups and projects collaboration
- 13:00Eclipse IDE Working Group example
- 16:35Jakarta EE Working Group example
- 19:24Working group benefits and activities
- 20:48Open participation and meritocracy
- 22:33Summary and resources
related talks
16mA Journey of Contribution and Collaboration in Open Source
30mEffective Vulnerability Management for Over 400 Projects at the Eclipse Foundation
01h 21mOpen Source Best Practices at Eclipse Foundation
27mOpen Source Health - A Crisis of Expectations
37mThe Eclipse Development Process for Committers
22mState of the Eclipse Foundation
22mThe State of the Eclipse Community
47mPolicing Open-Source Projects at Scale