Open Stack

On Tue, 2013-05-28 at 15:29 +0200, Thierry Carrez wrote:

> https://wiki.openstack.org/wiki/TC_Membership_Models
> 
> I'd like everyone interested with this discussion to have a look at this
> page. If you see goals that we missed, please suggest them on the thread
> here, along with how well each currently-proposed solution would score
> against it. Same if you think some model was not scored fairly against
> existing stated goals. Finally, if you have an alternate model which
> you'd like to suggest, feel free to do so. I'll keep the wiki page
> updated based on the ML discussion.

And here's an attempt at a completely different model which I don't
expect anyone to like, but might spark some ideas:

"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.

Cheers,
Mark.