|Re: [jakarta.ee-spec] [BALLOT] Approval to update the Jakarta EE Specification Process (JESP)|
_______________________________________________Greetings Jakarta EE Specification Committee.
I need your vote to approve the following change to the JESP to accomodate the need to tighten up the language around the usage of the 'jakarta' namespace.
The JESP/EFSP requires a successful ballot of the Specification Committee in order to approve changes to the JESP.
The relevant materials are available here:- Text added:"Use of the `jakarta` namespace is limited to API artifacts (all API jars, javadoc, and schema namespaces). It must not be used for any deployment, including applications, TCKs, tools, libraries, or any other assets produced by Specification Projects."
Per the process, this will be a seven-day ballot, ending on 2022-03-01 that requires a Super-majority positive vote of the Specification Committee members (note that there is no veto). Community input is welcome, but only votes cast by Specification Committee Representatives will be counted.
The Specification Committee is composed of representatives of the Jakarta EE Working Group Member Companies (Fujitsu, IBM, Oracle, Payara, Tomitribe, Primeton, and Shandong Cvicse Middleware Co.), along with individuals who represent the EE4J PMC, Participant Members, and Committer Members.
Specification Committee representatives, your vote is hereby requested. Please respond with +1 (positive), 0 (abstain), or -1 (reject). Any feedback that you can provide to support your vote will be appreciated.--
jakarta.ee-spec mailing list
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec
Back to the top