blob: 9004b0f30f9b558b5c3a7b7f55e7337430998d4f [file] [log] [blame]
<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1.0, user-scalable=no"/>
<meta name="theme-color" content="#2196F3">
<title>Apache Airavata</title>
<!-- CSS -->
<link href="assets/min/plugin-min.css" type="text/css" rel="stylesheet">
<link href="assets/min/custom-min.css" type="text/css" rel="stylesheet" >
</head>
<body id="top" >
<!-- Pre Loader -->
<div id="loader-wrapper">
<div id="loader"></div>
<div class="loader-section section-left"></div>
<div class="loader-section section-right"></div>
</div>
<!--Navigation-->
<div class="navbar-fixed">
<nav id="nav_f" class="default_color" role="navigation">
<div class="container">
<div class="nav-wrapper">
<a href="index.html" id="logo-container" class="brand-logo">
<img src="assets/img/airavata-brand.png" width="50%" />
</a>
<ul class="right hide-on-med-and-down">
<li ><a href="about.html">About</a></li>
<li ><a href="development.html">Development</a></li>
<li >
<a href="learning.html">Learning</a>
<!--
<ul class="">
<li>Test1</li>
<li>Test1</li>
<li>Test1</li>
</ul>
-->
</li>
<li ><a href="get-involved.html">Get Involved</a></li>
<li ><a href="community.html">Community</a></li>
</ul>
<ul id="nav-mobile" class="side-nav">
<li ><a href="about.html">About</a></li>
<li ><a href="development.html">Development</a></li>
<li ><a href="learning.html">Learning</a></li>
<li ><a href="get-involved.html">Get Involved</a></li>
<li ><a href="community.html">Community</a></li>
</ul>
<a href="#" data-activates="nav-mobile" class="button-collapse"><i class="mdi-navigation-menu"></i></a>
</div>
</div>
</nav>
</div>
<div class="page-content">
<div class="wrapper">
<div class="post">
<header class="post-header">
<h1 class="post-title center">Lazy Consensus</h1>
</header>
<div class="section no-pad-bot">
<main><div class="container">
<p>The concept of "Lazy Consensus" is very important in any apache project. Lazy
Consensus means that when you are convinced that you know what the community
would like to see happen you can simply assume that you already have consensus
and get on with the work. You don't have to insist people discuss and/or
approve your plan, and you certainly don't need to call a vote to get approval.
You just assume you have the community's support unless someone says otherwise.</p>
<p>We have a time machine (Subversion), this means that as long as you commit
(or submit patches) early and often the community has plenty of opportunity
to indicate disapproval. If you believe the community will support your action
you can operate on lazy consensus as long as you are prepared to roll back
any work should a valid objection is raised.</p>
<h2 id="avoiding-unnecessary-discussion">Avoiding Unnecessary Discussion</h2>
<p>The key thing about lazy consensus is that it's easier for people to agree,
by doing nothing, than it is to object, which requires an
alternative to be proposed. This has two effects, firstly people are less
likely to object for the sake of it and secondly it cuts down on the amount
of unnecessary mail traffic and discussion.</p>
<p>Lazy consensus means we can avoid waiting for a community based decision
before proceeding. However, it does require everyone who cares for the health
of the project to watch what is happening, as it is happening. Objecting too
far down the road will cause upset, but objecting (or asking for clarification
of intent) early is likely to be greeted with relief that someone is watching
and cares.</p>
<h2 id="stating-lazy-consensus">Stating Lazy Consensus</h2>
<p>Sometimes a member of the community will believe a specific action is the correct
one for the community but are not sure enough to proceed with the work under the
lazy consensus model. In these circumstances they can state Lazy Consensus is in
operation.</p>
<p>What this means is that they make a proposal and state that they will start
implementing it in 72 hours unless someone objects. 72 hours is chosen because
it accounts for different timezones and non-apache commitments.</p>
<p>In this approach the original proposal is not insisting that there is a discussion
around their proposal, nor are they requesting that the community explicitly
supports their actions. However, this differs from assuming lazy consensus
since it allows space and time to <a href="/community/governance/consensusBuilding.html">express support or objections</a> and corrections to
the proposal before work begins. </p>
<h2 id="silence-is-consent">Silence is consent</h2>
<p>People may choose to indicate their support for the actions taken with a +1
mail - quick and easy to read and reassuring for the implementer. However,
remember, in a lazy consensus world silence is the equivalent to support. This
can take some time to get used to.</p>
<p>&lt;/article&gt;</p>
</article>
</div></main>
</div>
</div>
</div>
<footer id="contact" class="page-footer default_color scrollspy">
<div class="container">
<div class="row" style="margin-bottom: 0;">
<div class="col m5 s12">
<div class="col m4 right-align">
<a href="http://apache.org" target="_blank">
<img src="assets/img/apache-logo.png" width="70%"/>
</a>
</div>
<div class="col m8">
<a href="http://apache.org" target="_blank">
<h5 class="white-text">Apache</h5>
</a>
<ul>
<li><a class="white-text" href="http://apache.org/" target="_blank">Apache Software Foundation</a>
</li>
<li><a class="white-text" href="http://apache.org/foundation/thanks.html"
target="_blank">Thanks</a></li>
<li><a class="white-text" href="http://apache.org/foundation/sponsorship.html" target="_blank">Become
a Sponsor</a></li>
<li><a class="white-text" href="http://apache.org/security/" target="_blank">Security</a></li>
</ul>
</div>
</div>
<div class="col m4 s12">
<h5 class="white-text">Apache Airavata</h5>
<ul>
<li><a class="white-text" href="mailing-list.html">Mailing List</a></li>
<li><a class="white-text" href="development.html#downloads">Downloads</a></li>
<li><a class="white-text" href="learning.html#documentation">Documentation</a></li>
<li><a class="white-text"
href="https://issues.apache.org/jira/browse/airavata/?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel"
target="_blank">Issue Tracking</a></li>
</ul>
</div>
<div class="col m3 s12">
<h5 class="white-text">Get Involved</h5>
<ul>
<li><a class="white-text"
href="get-involved.html#how-to-contribute">Become a
Contributor</a></li>
<li><a class="white-text" href="gsoc.html">Student GSoC Projects</a></li>
</ul>
<a href="https://www.apache.org/events/current-event.html">
<img src="https://www.apache.org/events/current-event-125x125.png" style="padding-top:0.5em;">
</a>
</div>
</div>
<div class="row">
<div class="col-lg-12">
<p class="footer-copyright">Copyright &copy; 2021 The Apache Software Foundation, Licensed under the <a
class="white-text" href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
</p>
<p class="footer-copyright">Apache Airavata, Airavata, Apache, Apache Airavata Logo and the Apache
feather logo are trademarks of The Apache Software Foundation.
</p>
</div>
</div>
</div>
</footer>
</body>
<!-- Scripts-->
<script src="assets/min/plugin-min.js"></script>
<script src="assets/min/custom-min.js"></script>
</html>