Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Lazy Consensus"

(New page: Lazy Consensus is a useful technique to make decisions. When you don't anticipate any objections, for decisions of low impact or decisions that can be revised easily, you can post somethin...)
 
 
Line 1: Line 1:
 
Lazy Consensus is a useful technique to make decisions. When you don't anticipate any objections, for decisions of low impact or decisions that can be revised easily, you can post something like the following on a mailing list (or some other communication channel):
 
Lazy Consensus is a useful technique to make decisions. When you don't anticipate any objections, for decisions of low impact or decisions that can be revised easily, you can post something like the following on a mailing list (or some other communication channel):
  
  "I am going to assume lazy consensus if there are no objections within the next three days."
+
  "I am going to assume lazy consensus if there are no objections within the next seven days."
  
You may want to wait longer (one week), and you should make it clear what the consensus decision will be if noone objects.
+
Also, you should make it clear what the consensus decision will be if no one objects.
  
 
This technique is used in the Apache community, see [http://www.apache.org/foundation/glossary.html#LazyConsensus].
 
This technique is used in the Apache community, see [http://www.apache.org/foundation/glossary.html#LazyConsensus].

Latest revision as of 11:57, 5 July 2011

Lazy Consensus is a useful technique to make decisions. When you don't anticipate any objections, for decisions of low impact or decisions that can be revised easily, you can post something like the following on a mailing list (or some other communication channel):

"I am going to assume lazy consensus if there are no objections within the next seven days."

Also, you should make it clear what the consensus decision will be if no one objects.

This technique is used in the Apache community, see [1].

Back to the top