Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakarta.ee-spec.committee] JESP finalization review

To my eye, the whole #4 bullet feels out of place, worded incorrectly (it says 30 days notice, but doesn't actually talk about the duration of an actual ballot), and too tightly coupled with a specific communication channels. 

Independent of that, do we believe that thirty days is required? As was mentioned in a separate thread, we're talking about a ballot of the same people who actually author the document. That seems excessive and unnecessary. One week seems like plenty of time.

Proposal #1: we strike out bullet #4 and add bullet #2f with this text: "JESP Update: 7 calendar days"

Additionally, the Steering Committee has no formal role in either process itself or the adoption of the process. I'm thinking that we can implicate them indirectly in a manner similar to how we do profile designations.

Proposal #2: change bullet #1 to: "Any modification to or revision of this Jakarta EE Specification Process, including the adoption of a new version of the EFSP, must be approved by a Super-majority of the Specification Committee, including a Super-majority of Strategic Members of the Jakarta EE Working Group, in addition to any other ballot requirements set forth in the EFSP.

What do you think?


Thanks,

Wayne

On Wed, Mar 20, 2019 at 4:06 PM Bill Shannon <bill.shannon@xxxxxxxxxx> wrote:
In the future, if/when we update the JESP, we require a 30 day review
before the updated version is approved, during which the updated draft
JESP will not change.

Do we expect to do the same for the first version?
_______________________________________________
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.


Back to the top