[openstack-dev] What should openstack-specs review approval rules be ?

Morgan Fainberg morgan.fainberg at gmail.com
Wed Jan 28 16:13:04 UTC 2015

I am of the opinion that the +1/-1 from non tc members can be valuable, but
similarly it would be easy to get just comments. The TC is the body I
expect to help determine the direction of cross project initiatives such as
the logging guidelines. As a PTL I feel confident the TC is the right body
to do the voting and the same rules as the governance repo (with chair +1
workflow) seems to be a great idea. Communicating the topics via the ML and
the cross project meeting should help to get the PTLs and CPLs involved in
the process, which is highly important. The ML can help to bring in other

I would rather trust the TC (who has not shown any reason to question their
ability to determine community consensus) to help make sure we don't stall
on these specs than have endless waiting. I like the proposal to use the TC
voting rules.


On Wednesday, January 28, 2015, Thierry Carrez <thierry at openstack.org>

> Hi everyone,
> When we first introduced the cross-project specs (specs for things that
> may potentially affect all OpenStack projects, or where more convergence
> is desirable), we defaulted to rather simple rules for approval:
> - discuss the spec in a cross-project meeting
> - let everyone +1/-1 and seek consensus
> - wait for the affected PTLs to vote
> - wait even more
> - tally the votes (and agree a consensus is reached) during a TC meeting
> - give +2/Worflow+1 to all TC members to let them push the Go button
> However, the recent approval of the Log guidelines
> (https://review.openstack.org/#/c/132552/) revealed that those may not
> be the rules we are looking for.
> Sean suggested that only the TC chair should be able to workflow+1 to
> avoid accidental approval.
> Doug suggested that we should use the TC voting rules (7 YES, or at
> least 5 YES and more YES than NO) on those.
> In yesterday's meeting, Sean suggested that TC members should still have
> a -2-like veto (if there is no TC consensus on the fact that community
> consensus is reached, there probably is no real consensus).
> There was little time to discuss this more in yesterday's TC meeting, so
> I took the action to push that discussion to the ML.
> So what is it we actually want for that repository ? In a world where
> Gerrit can do anything, what would you like to have ?
> Personally, I want our technical community in general, and our PTLs/CPLs
> in particular, to be able to record their opinion on the proposed
> cross-project spec. Then, if consensus is reached, the spec should be
> approved.
> This /could/ be implemented in Gerrit by giving +1/-1 to everyone to
> express technical opinion and +2/-2 to TC members to evaluate consensus
> (with Workflow+1 to the TC chair to mark when all votes are collected
> and consensus is indeed reached).
> Other personal opinions on how you'd like this repository reviews to be
> run ?
> --
> Thierry Carrez (ttx)
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150128/253b05bf/attachment.html>

More information about the OpenStack-dev mailing list