Director's Pick: Introducing The Eclipse Foundation Specification Process
summary
Eclipse Foundation Specification Process defines a code-first route where a spec is a collection of APIs, semantic rules, data formats and must have at least one open-source TCKs and an open-source implementation that implements all optional parts before the spec can be ratified. It extends the EDP with a spec project flag, a spec committee that requires a supermajority for progress and release reviews, and participant representatives that bind company patents; approved licenses are EPL 2.0, BSD‑3 and Apache, and compatibility requires running the exact TCK binary and posting public results.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:04Background and purpose
- 3:11Guiding principles
- 6:26Eclipse development process
- 11:08Defining a specification
- 16:08Licenses and branding
- 19:18IP and patent considerations
- 21:42Project roles and structure
- 26:42Lifecycle and review process
- 30:15Comparison with JCP
- 34:03Certification and takeaways
related talks
23mManaging the unmanageable: community driven projects at Eclipse Foundation
01h 21mOpen Source Best Practices at Eclipse Foundation
26mWhat is next? Towards Dataspace Interoperability: Open standardisation and implementation
39mRevising the Eclipse Foundation's Intellectual Property Due Diligence Process
16mA Journey of Contribution and Collaboration in Open Source
46mOpening Up Java EE: Panel Discussion with Oracle, IBM, Red Hat, and the Eclipse Foundation
12mBuilding Bridges Between Academia, Industry and Open Source
31mDevelopment Process 101