Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakarta.ee-spec.committee] Topics for today

My sense is that the vote is a "belts and suspenders" sort of thing. We don't need it (we have tacit approval by virtue of the various agreements that the Committers are required to sign or have signed on their behalf), but many among us feel that it's better if we have explicit approval.

I'm concerned that this adds complexity to the process and we're going to get hammered by the community. IMHO, we should only include this if there is a real (legal) necessity to do so.

Perhaps we can turn this around and grant Participants the ability to put on the brakes (i.e. compel the project to revert into an earlier state, or something) if there's a problem (probably as part of the grievance handling process). I recall that there was some concern on the call that putting the onus on the Participants in this way would make it hard for a Participant to step forward and shut things down. 

Wayne

On Wed, Sep 12, 2018 at 11:17 PM, Bill Shannon <bill.shannon@xxxxxxxxxx> wrote:
What you say is true, but it doesn't change my opinion.

Clearly the Spec Project Lead should have the support of the Participants on the project, but I don't think it's necessary to require a formal vote.


Wayne Beaton wrote on 09/12/2018 07:50 PM:
I would probably help if tried communicating in English :-/

I was trying to express that the subset of the members on the Specification Committee is different from the subset of members that Participate in any particular project. Getting approval from the members on the Specification Committee is not the same (and is certainly not a superset) as getting approval from the members who participate in a particular project.

At one point, I had envisioned that all members were represented on the Specification Committee. This notion is, in retrospect, silly.

Wayne

On Wed, Sep 12, 2018 at 6:19 PM, Bill Shannon <bill.shannon@xxxxxxxxxx> wrote:
Wayne Beaton wrote on 09/12/18 01:49 PM:
 

Note that approvals are already covered in the document: e.g. the Specification Committee must approve new project proposals, scope changes, release plans, and reviews by super majority. 

We noted that all Member Companies are not represented on the Specification Committee, so representation on the committee does not meet the requirements of the stated rationale for requiring a Participant vote.
Sorry, I don't understand that.




--
Wayne Beaton
Director of Open Source Projects
The Eclipse Foundation




--
Wayne Beaton
Director of Open Source Projects
The Eclipse Foundation

Back to the top