The move of enterprise and cloud-native specifications and technologies to the Eclipse Foundation under the Jakarta brand brings along with it the need to define a process for creating and evolving code-first specifications in open source. While specifications manifest as a collection of artifacts (a specification is a collection of APIs, descriptions of semantic behavior, data formats, and/or protocols intended to enable the development of independent compatible implementations), it's not quite as simple as dropping them into our existing Eclipse Development Process (EDP).
With help from the Jakarta EE Working Group, the Eclipse Foundation has defined the Eclipse Foundation Specification Process (EFSP) as an extension to the EDP. Join us as we talk about the issues and how the EFSP addresses them as we start this brave new adventure for the Eclipse Community.