|Re: [jakarta.ee-spec] [External] : Re: [BALLOT] Approve the Jakarta TCK package naming convention ee.jakarta.tck.[spec]|
While I don't intend to speak for the groups, I believe the discussion that was held in several different group meetings (at least Spec. committee and Platform committer team) concluded with advice -- the Specification teams are free to use any name-space other than jakarta (or java or javax). Teams may use ee.jakarta.tck if they choose and likely will. This applies to a relatively small number of newly refactored specifications and, as I understand it, they are prepared to move forward. This was discussed at length and the most recent comments are documented in the Platform Committer team notes.
I understand this may seem at odds with the Proposal statement of the most recent (unapproved) Spec. committee minutes, but I'd note that this is simply listed as a proposal and not minuted as adopted. My recollection (which may certainly be flawed), was that we did not have consensus on the proposal, nor on the timing of a ballot that results in a 'requirement' statement.
Rather than kicking off another ballot, perhaps we can simply
make that position broadly known (choose any namespace you want,
provided the namespace cannot start with 'jakarta.'). I don't
think that we want to force more change than needed until we have
a better and more well understood proposal.
I'll let Emily wrap this up, but it clearly did not pass despite what seems to be agreement.
Most the feedback was around wanting things to be more explicit, information being in links and not understanding context. I've created a new ballot and will post it. Understand the length is in response to these concerns.
On Jan 12, 2022, at 2:22 PM, Emily Jiang via jakarta.ee-spec <jakarta.ee-spec@xxxxxxxxxxx> wrote:
Greetings Jakarta EE Specification Committee.
After a long discussion on the naming convention of the Jakarta TCK namespaces, the Jakarta community chose the package name: ee.jakarta.tck.[spec].
I need your vote to approve the Jakarta TCK package name ee.jakarta.tck.[spec]
Per the process, this will be a seven-day ballot, ending on January 19, 2022, 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
_______________________________________________ jakarta.ee-spec mailing list jakarta.ee-spec@xxxxxxxxxxx To unsubscribe from this list, visit https://urldefense.com/v3/__https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec__;!!ACWV5N9M2RV99hQ!eyhlaBeTkP2l2CwVVBQtjikCLmCeEM1wbUr28mXS3KKZ4njypipw1qyR6JR8f3g$
Back to the top