EDP

While it’s true that most Eclipse projects use the Eclipse Public License, many Eclipse open source projects use alternative licenses either alone or in combination. The chart below shows the relative use of various license schemes by Eclipse open source projects: Note that we use SPDX expression. In SPDX, license...

The Eclipse Foundation is in the process of making a major update to our Intellectual Property Policy. A big part of this update is a change in the way that we will manage third party content. In the context of the Eclipse IP Policy, “third party content” is content that...

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...

The Eclipse Development Process has a notion of phases. Two of those phases are Incubation and Mature. While in both of these phases, an Eclipse open source project operates in basically the same manner: only committers can push content, committers are brought on board by election, committers accept contributions, and...

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)...

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...

On December 7/2018, the Eclipse Foundation’s Board of Directors approved a new edition of the Eclipse Development Process (EDP) which introduces one particularly significant change, along with a small number of other useful changes. We rolled this new edition out on December 14/2018. Note that project teams who are familiar...

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...