cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Noah Slater <>
Subject Incorrect definition of lazy consensus in by-laws
Date Sun, 10 Mar 2013 18:52:46 GMT

I was just reading through the by-laws we voted in (sorry, I am about a
month late in doing this, I know) and it occurred to me that we might have
the wrong definition of lazy consensus.

Specifically, we define it here:

"3.2.1. Lazy Consensus - Lazy consensus requires 3 binding +1 votes and no
binding -1 votes."

My understanding of lazy consensus is that it requires no votes whatsoever.
In fact, there are two modes. The first is to simply do whatever it is you
think is a good idea, and assume someone will speak up if they disagree.
The other is to state your intention, and give 72 hours for people to
object. If you receive no objections, you proceed.

Neither of these situations require any votes. And in fact, the primary
idea behind lazy consensus is that if you hear nothing, you can proceed.

Here's a good page about it:

If you look on the foundation's page[1] on voting, you even see things like

"Unless a vote has been declared as using lazy consensus , three +1 votes
are required for a code-modification proposal to pass."

i.e. Needing three +1 votes is an alternative to lazy consensus.

I think we need to update our by-laws to fix this.




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