| Re: [jakarta.ee-spec.committee] Default fourteen day ballots |
A ballot is used to seek Specification Committee approval. Unless otherwise stated in this process (or a Working Group-specific derivative of this process), the default period for all Specification Committee ballots is seven (7) days. During that time, any member of a Specification Committee may request that the period be extended to thirty (30) days.
A Specification Committee may opt to increase the length of the ballot period, but may not—under any circumstances—reduce any review period to fewer than seven (7) days.
I think what Kevin suggests would be fine. (Although I'll have to explain to Oracle legal why this is still ok for Jakarta EE since the JESP will specify 14 days.)_______________________________________________
The only reason I can see to keep 14 days in the EFSP is if the Eclipse Foundation believes 14 days is the best choice and wants to strongly encourage derivatives of this process to use 14 days.
Kevin Sutter wrote on 6/12/19 11:34 AM:
Actually, Wayne, I think it just got worse... :-) Now it is saying that the default and minimum review period is 14 days *unless* you have a Working Group derivative of the process. I have to go back to my initial assertion -- what was wrong with the original wording of the 7 day minimum (other than the week vs 7 days thing)? I don't want to make the EFSP more restrictive. Let the derivatives make it more restrictive (like the JESP), not the other way around.
---------------------------------------------------
Kevin Sutter
STSM, MicroProfile and Jakarta EE architect
e-mail: sutter@xxxxxxxxxx Twitter: @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)
LinkedIn: https://www.linkedin.com/in/kevinwsutter
From: Wayne Beaton <wayne.beaton@xxxxxxxxxxxxxxxxxxxxxx>
To: Jakarta specification committee <jakarta.ee-spec.committee@xxxxxxxxxxx>
Date: 06/12/2019 12:39 PM
Subject: [EXTERNAL] [jakarta.ee-spec.committee] Default fourteen day ballots
Sent by: jakarta.ee-spec.committee-bounces@xxxxxxxxxxx
I tweaked the wording.
Specifically, I removed "No ballot period may be shorter than seven (7) days." sentence and added what I think is a clarification to the final sentence (which I believe is just restating the now-removed sentence).
A ballot is used to seek Specification Committee approval. Unless otherwise stated in this process (or a Working Group-specific derivative of this process), the default period for all Specification Committee ballots is fourteen (14) days. During that time, any member of a Specification Committee may request that the period be extended to thirty (30) days. A Specification Committee may opt (via a Working Group-specific derivative of this process or exception) to change the length of a ballot period, but may not--under any circumstances--reduce any review period to fewer than seven (7) days.
I think that this makes the intention clearer: unless otherwise specified, ballots are fourteen days long; and when otherwise specified, that ballot cannot be fewer than seven days long.
Does this work?
Wayne
--Wayne Beaton
Director of Open Source Projects | Eclipse Foundation, Inc._______________________________________________
jakarta.ee-spec.committee mailing list
jakarta.ee-spec.committee@xxxxxxxxxxx
To change your delivery options, retrieve your password, or 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 change your delivery options, retrieve your password, or 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 change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee
Wayne Beaton
Director of Open Source Projects | Eclipse Foundation, Inc.