Re: [jakartaee-platform-dev] "voting" privileges

[Emily Jiang <emijiang6@xxxxxxxxxxxxxx>]

I think we need to go back to answer Kevin's question now.

On our Platform Dev call on Tuesday (minutes soon to be posted here:  https://eclipse-ee4j.github.io/jakartaee-platform/minutes/minutes.html), we discussed who should be eligible to vote on the Jakarta EE 9 content proposals.  We decided that only thecommitters on the Platform projectwould be eligible.

On the call, I thought committers include all EE4J projects. From what you listed here, it only includes the platform project committers, which I think it is a bit light. Personally, I will agree with: One idea is to expand our eligible voting pool to include any committer on any of the EE4J Specification projects.

I think the above idea makes a lot of sense, as the committers will be affected by the voting result and they need to execute the plan accordingly. It is much better to involve the group in the discussion, instead of leaving them out.

Emily

On Thu, Nov 14, 2019 at 4:46 PM Kevin Sutter <sutter@xxxxxxxxxx> wrote:

Hi,
On our Platform Dev call on Tuesday (minutes soon to be posted here:  https://eclipse-ee4j.github.io/jakartaee-platform/minutes/minutes.html), we discussed who should be eligible to vote on the Jakarta EE 9 content proposals.  We decided that only thecommitters on the Platform projectwould be eligible.

But, on second thought, I'm wondering if that's sufficient.  The Jakarta EE 9 roadmap that we're trying to get agreement on affects all of the Jakarta EE components, not just the platform.  I know we discussed that the reps on the Platform should be representing their overall interests (including components) and not just the Platform.  But, is that sufficient?

On yesterday's Jakarta EE Updatecall, there was discussion about how much work it is to Jakarta-ize the Specifications.  And, we talked about the work required to do the javax->jakarta package rename (spec, api, tck, compatible impls, etc).  Markus presented and discussed these topics on how they relate to the JAX-RS effort.  Markus is not directly represented on the Platform project -- that is, he doesn't work for or with any of the committers.  He is driving much of the work for the JAX-RS effort.  How do we ensure that voices (like Markus') from all of the Component features are heard and counted when we make the decisions for Jakarta EE 9?

One idea is to expand our eligible voting pool to include any committer on any of the EE4J Specification projects.  I have no idea on how easy it would be discern or filter the various votes, but that seems to be a more equitable means of voting.

Or, we can fall back to our original premise to trust the committer reps on the Platform project to take into account all of the various component's views when they cast their vote.

Thoughts?

---------------------------------------------------
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
_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev

--

Thanks
Emily