incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John D. Ament" <>
Subject Re: Podling release vote terminology
Date Tue, 09 May 2017 22:42:54 GMT

If you have a case to site, it may make it easier to follow how it would be

One area where I do see consistent confusion on are the votes that count.
I personally want to see a more fluid vote policy, but it should be clearer
which votes were cast and which votes are binding.

At one point, I updated [1] to reflect the binding part, but the struggle



On Tue, May 9, 2017 at 2:00 PM Craig Russell <> wrote:

> I've seen a few (recent) incubator votes that imply that there are two
> separate, distinct votes: one in the podling and one in the incubator
> general. And lots of questions about binding votes and carried-over votes
> and whose votes are counted.
> I'd like to suggest:
> There is one vote for a podling release candidate. The first phase of the
> vote takes place on the podling dev list. Anyone can vote. An affirmative
> vote by three PPMC members (including mentors) is sufficient to start the
> second phase, which takes place on the incubator general list. An
> individual's vote can be changed any time during either phase until the
> final vote is tallied.
> All votes are counted. Only IPMC member votes are binding. The final tally
> counts affirmative, neutral, and negative votes from both phases combined
> and affirmative, neutral and negative binding votes from both phases
> combined.
> This terminology answers questions about:
> Whether PPMC votes are binding. They are not.
> Whether IPMC member votes on the first phase of voting carry over to the
> second phase. They do.
> Whether public votes in either phase count. They do.
> Whether public votes in either phase are binding. They are not.
> If we agree on the terminology, I'll see what documents need to be updated.
> Craig L Russell
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message