EFSP

We identified a hole in our committer agreement process that excluded individuals with a certain employment status from participating in Eclipse Foundation open source specification projects operating under the Eclipse Foundation Specification Process (EFSP). I’ll start by saying that you don’t need to be a committer to contribute to an...

The Eclipse Foundation Development Process (AKA, the Eclipse Development Process or EDP) says nothing about how teams should organize. The EDP defines a committer role: committers are those developers who have the ability to make decisions for the project (e.g., push commits to project Git repositories and configure build servers)...

With the Eclipse Foundation Specification Process (EFSP) a single open source specification project has a dedicated project team of committers to create and maintain one or more specifications. The cycle of creation and maintenance extends across multiple versions of the specification, and so while individual members may come and go...

It’s time to change the specification names… When we first moved the APIs and TCKs for the Java EE specifications over to the Eclipse Foundation under the Jakarta EE banner, we kept the existing names for the specifications in place, and adopted placeholder names for the open source projects that...

The Eclipse Development Process (EDP) requires that a project team engage in a successful progress or release review before creating a formal release. We use progress and release reviews as an opportunity to validate that a project team is following the open source rules of engagement, and are consistently implementing...

Scientific progress goes “boink”? – Hobbes The Eclipse Foundation Specification Process (EFSP) provides a framework and governance model for developers engaged in the process of developing specifications. Specification: A specification is a collection of related artifacts. The EFSP defines a specification as a “collection of Application Programming Interface (API) definitions...

One key difference between Eclipse open source software projects as defined by the Eclipse Development Process (EDP), and open source specification projects as defined by the Eclipse Foundation Specification Process (EFSP) is that specification projects must be aligned with exactly one specification committee. More generally, specification projects are aligned with...

The Eclipse Foundation Specification Process (EFSP) includes an image that provides an overview of what goes into creating a new Specification Project. By creating, we mean the process of taking a Specification from an initial idea or concept through to the point where the necessary resources and permissions are in...

By now most of you are aware already that Oracle has contributed Java EE specification to open source, and into Eclipse Foundation. The Java enterprise community decided to rename the Java EE specification to Jakarta EE. Part of this huge transition to open source is changing the specification process. The...

The Eclipse Foundation Specification Process defines a general framework for developing specifications in open source at the Eclipse Foundation; it extends the Eclipse Development Process (EDP) by adding a few extra checks and balances. In the first installment of this series, we described the EDP; in this second installment, we...