| Re: [jakarta.ee-spec.committee] E-mail list for TCK dispute issues |
No debate. Change it to the public mailing list.
---------------------------------------------------
Kevin Sutter
STSM, Jakarta EE and MicroProfile architect @ IBM
e-mail: sutter@xxxxxxxxxx Twitter: @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)
LinkedIn: https://www.linkedin.com/in/kevinwsutter
Part-time schedule: Tue, Wed, Thu (off on Mon and Fri)
From: Scott Stark <sstark@xxxxxxxxxx>
To: Jakarta specification committee <jakarta.ee-spec.committee@xxxxxxxxxxx>
Date: 04/06/2021 11:11
Subject: [EXTERNAL] Re: [jakarta.ee-spec.committee] E-mail list for TCK dispute issues
Sent by: "jakarta.ee-spec.committee" <jakarta.ee-spec.committee-bounces@xxxxxxxxxxx>
They would be public if opened at github issues, so I see no problem with switching to the public list as proposed. On Tue, Apr 6, 2021 at 11:06 AM Ed Bratt <ed.bratt@xxxxxxxxxx> wrote: Hi, Reviewing the TCK user guides, I notice that
They would be public if opened at github issues, so I see no problem with switching to the public list as proposed.
On Tue, Apr 6, 2021 at 11:06 AM Ed Bratt <ed.bratt@xxxxxxxxxx> wrote:
Hi,
Reviewing the TCK user guides, I notice that the e-mail list (in all the TCKs) that is documented for escalating disputes is jakarta.ee-spec.committee@xxxxxxxxxxx. I believe that this is a private committee list and any e-mail sent to this list, not from a committee member, will bounce. I recommend the documented list be updated to jakarta.ee-spec@xxxxxxxxxxx.
This is the current text in the section: 2.3.3, item 4 (from the Annotations User Guide -- this text is used in all TCK user guides in this section):
Rejected Challenges and Remedy.
When a`challenge` issue is rejected, it must be closed with a label of invalidto indicate it has been rejected. There appeal process for challenges rejected on technical terms is outlined in Escalation Appeal. If, however, an implementer feels the TCK challenge process was not followed, an appeal issue should be filed with specification project’s TCK issue tracker using the label challenge-appeal. A project lead should escalate the issue with the Jakarta EE Specification Committee via email (jakarta.ee-spec.committee@xxxxxxxxxxx). The committee will evaluate the matter purely in terms of due process. If the appeal is accepted, the original TCK challenge issue will be reopened and a label of appealed-challengeadded, along with a discussion of the appeal decision, and the challenge-appealissue with be closed. If the appeal is rejected, the challenge-appealissue should closed with a label of invalid.
I propose replacing the e-mail list with jakarta.ee-spec@xxxxxxxxxxx. This does have the impact of making these disputes public. I'm not sure if there are other options that would allow these discussions to be carried out more privately.
I would like to wrap these changes up so I'm hoping we can get quick agreement on this -- maybe in tomorrow's early morning Spec. committee meeting :-). We can also just kick this down the road, if there's debate.
-- Ed_______________________________________________
jakarta.ee-spec.committee mailing list
jakarta.ee-spec.committee@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee_______________________________________________
jakarta.ee-spec.committee mailing list
jakarta.ee-spec.committee@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee
_______________________________________________
jakarta.ee-spec.committee mailing list
jakarta.ee-spec.committee@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee