Open Stack

Mark McLoughlin wrote:
> "Rough Consensus, Veto Triggers Plebiscite"
> 
> All ATCs are members of the Technical Committee. Technical Committee
> meetings become a forum to bring together people across the project
> interested in specific topics. The detailed discussions happen over the
> mailing list. Project leaders use their influence to help drive
> consensus. Any ATC who feels that a proposal is being forced through and
> doesn't reflect a rough consensus can veto the proposal and trigger an
> immediate plebiscite of members present. If a vote is triggered, the
> proposal requires a two thirds majority to pass. We build a culture of
> empowering people to JFDI with a - hopefully rarely used - safety valve.

Ew. I've been part of such open source communities in the past and you
always end up spending your time voting on everything. You'd be
surprised how many people like to be consulted on every question. It
makes up a very brittle community that is easy to disrupt... Commit
once, veto and trigger plebiscites on every topic for one year.

You need leadership in a project to make hard calls and go somewhere. If
you make sure that leadership is representative of your contributors,
you end up with a pretty efficient combination.

-- 
Thierry Carrez (ttx)
Release Manager, OpenStack