Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakarta.ee-spec] BALLOT: Creation Review for Jakarta Config

+1

Werner

 

Gesendet von Mail für Windows

 

Von: Ivar Grimstad
Gesendet: Donnerstag, 7. Oktober 2021 11:42
An: Jakarta specification discussions
Betreff: Re: [jakarta.ee-spec] BALLOT: Creation Review for Jakarta Config

 

+1, PMC

 

On Thu, Oct 7, 2021 at 11:04 AM Dmitry Kornilov <dmitry.kornilov@xxxxxxxxxx> wrote:

Greetings Jakarta EE Specification Committee,

 

I need your vote to approve the Creation Review of Jakarta Config. It’s the second ballot. The first ballot was improperly held because of the patent license issues. The project got an exception from the Steering Committee to use Compatible Patent License (CPL).

 

The relevant materials are here:

https://github.com/jakartaee/specifications/pull/384

https://projects.eclipse.org/proposals/jakarta-config

 

Per the process, this will be a seven-day ballot, ending on the October 14th, 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, Red Hat, Tomitribe, and Primeton), 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.

 

Thanks,

Dmitry

_______________________________________________
jakarta.ee-spec mailing list
jakarta.ee-spec@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec


 

--

Ivar Grimstad

Jakarta EE Developer Advocate | Eclipse Foundation Eclipse Foundation - Community. Code. Collaboration. 

 


Back to the top