The Eclipse Development Process for Committers

on YouTube ↗37m

" summary

Explains concrete committer rules: all core content (code, docs, bugs, dev list) must live in Eclipse repos only or approved GitHub orgs, issues must use Bugzilla or GitHub, and examples may be under the EDL. Every contributor must sign the Eclipse Contributor Agreement required and commits must match that email; third‑party code goes through IP vetting. Releases follow milestones → RC → review; a new progress review allows frequent releases (review cycle ~2 weeks, ~30 minutes committer prep). Trademarks and vendor neutrality are enforced.

AI-written summary · about

" chapters (6)

1. 0:00Start
2. 2:34An Eclipse Project. . Conforms to the EDP and Eclipse IP Policy, Calls itself an Eclipse Project and conforms to Eclipse Foundation Branding Guidelines Uses infrastructure provided by the Eclipse Foundation for core content
3. 6:11The Eclipse Intellectual Property Policy The Eclipse IP Policy is concerned with establishing practices to mitigate legal risks associated with building products
4. 9:01Source Code is Core Content Source code must be actively developed on infrastructure provided by the Eclipse Foundation • Official project Git repositories must be the central authority
5. 11:09Documentation is Core Content Documentation is a first-class project resource. - Documentation maintained using the same rules as source . Must be deployed on EF infrastructure
6. 17:14"The Keys" Must be kept Safe Core infrastructure must be immune from domination by any single individual or organization • The EF must hold the keys for core infrastructure - Pick up and carry on Ownership of non-core Infrastructure must be shared . Must be able to survive departures of team members

" related talks

• 31mDevelopment Process 101Wayne Beaton, Maria Teresa Delgado · EclipseCon 2022
• 28mEMO & YOUMaria Teresa Delgado · EclipseCon 2023
• 23mManaging the unmanageable: community driven projects at Eclipse FoundationWayne Beaton · FOSS Backstage 2022
• 01h 21mOpen Source Best Practices at Eclipse FoundationWayne Beaton, Boris Baldassari · OCX Webinar Week 2025
• 21mBecome Part of the ProjectTyler Jewell, Brad Micklea · CheConf 2016
• 15mLet it go! or How to become a free software developer?Melanie Bats · Devoxx Belgium 2017
• 22mThe State of the Eclipse CommunityMike Milinkovich · EclipseCon 2023
• 16mA Journey of Contribution and Collaboration in Open SourceIvar Grimstad · SFSCON 2024