community-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From git-site-r...@apache.org
Subject [comdev-site] branch asf-site updated: Updated asf-site from master at c4685dc26d8c9f429da413d3a3c48b4b3360630a using https://ci-builds.apache.org/job/Community%20Development/job/site/job/master/55/
Date Wed, 02 Dec 2020 14:42:53 GMT
This is an automated email from the ASF dual-hosted git repository.

git-site-role pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/comdev-site.git


The following commit(s) were added to refs/heads/asf-site by this push:
     new cd255a3  Updated asf-site from master at c4685dc26d8c9f429da413d3a3c48b4b3360630a
using https://ci-builds.apache.org/job/Community%20Development/job/site/job/master/55/
cd255a3 is described below

commit cd255a329bb5f27fd02d343d93ad1085fe6c6afd
Author: jenkins <builds@apache.org>
AuthorDate: Wed Dec 2 14:42:48 2020 +0000

    Updated asf-site from master at c4685dc26d8c9f429da413d3a3c48b4b3360630a using https://ci-builds.apache.org/job/Community%20Development/job/site/job/master/55/
---
 content/committers/index.xml          |  2 +-
 content/committers/lazyConsensus.html | 65 ++++++++++++++++-------------------
 content/index.xml                     |  2 +-
 content/sitemap.xml                   |  4 +--
 4 files changed, 34 insertions(+), 39 deletions(-)

diff --git a/content/committers/index.xml b/content/committers/index.xml
index 3c96651..880d424 100644
--- a/content/committers/index.xml
+++ b/content/committers/index.xml
@@ -60,7 +60,7 @@ If you have any question about this, feel free to ask on our dev@community.</des
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
       <guid>https://community.apache.org/committers/lazyConsensus.html</guid>
-      <description>The concept of &amp;ldquo;Lazy Consensus&amp;rdquo; is very
important in our 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&amp;rsquo;t have to insist people discuss and/or approve
your plan, and you certainly don&amp;rsquo;t need to call a vote to get approval. You
just assume you have the communities support unle [...]
+      <description>The concept of &amp;ldquo;lazy consensus&amp;rdquo; is very
important in your project. Lazy consensus means that when you are convinced that you know
what the community would like to see happen, you can assume that you have consensus in favor
of the proposed work and and get on with it. You don&amp;rsquo;t have to insist people
discuss and/or approve your plan, and you certainly don&amp;rsquo;t need to call a vote
to get approval.</description>
     </item>
     
     <item>
diff --git a/content/committers/lazyConsensus.html b/content/committers/lazyConsensus.html
index 9cca9fb..46de87b 100644
--- a/content/committers/lazyConsensus.html
+++ b/content/committers/lazyConsensus.html
@@ -7,11 +7,11 @@
   <meta name="keywords" content="apache, apache community, community development, opensource"/>
   <meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1"
/>
   <meta property="og:title" content="Lazy Consensus" />
-<meta property="og:description" content="The concept of &ldquo;Lazy Consensus&rdquo;
is very important in our 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&rsquo;t have to insist people discuss and/or
approve your plan, and you certainly don&rsquo;t need to call a vote to get approval.
You just assume you have the communities suppor [...]
+<meta property="og:description" content="The concept of &ldquo;lazy consensus&rdquo;
is very important in your project. Lazy consensus means that when you are convinced that you
know what the community would like to see happen, you can assume that you have consensus in
favor of the proposed work and and get on with it. You don&rsquo;t have to insist people
discuss and/or approve your plan, and you certainly don&rsquo;t need to call a vote to
get approval." />
 <meta property="og:type" content="article" />
 <meta property="og:url" content="https://community.apache.org/committers/lazyConsensus.html"
/>
 <meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/>
-<meta property="article:modified_time" content="2020-03-24T15:03:46+01:00" /><meta
property="og:site_name" content="Apache Community Development" />
+<meta property="article:modified_time" content="2020-12-02T10:18:35-04:00" /><meta
property="og:site_name" content="Apache Community Development" />
 
 
   <title>Apache Community Development - Lazy Consensus</title>
@@ -189,48 +189,43 @@
 
       <hr>
       
-	<p>The concept of &ldquo;Lazy Consensus&rdquo; is very important in our 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&rsquo;t have to insist people discuss and/or
+	<p>The concept of &ldquo;lazy consensus&rdquo; is very important in your project.
Lazy
+consensus means that when you are convinced that you know what the community
+would like to see happen, you can assume that you have consensus in favor of the proposed
work and
+and get on with it. You don&rsquo;t have to insist people discuss and/or
 approve your plan, and you certainly don&rsquo;t need to call a vote to get approval.
-You just assume you have the communities 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 just assume you have the community&rsquo;s support unless someone says otherwise.</p>
+<p>We have a time machine (Subversion or Git). As long as you commit
+(or submit patches) early and often, the community has plenty of opportunity
+to indicate disapproval or point out issues. 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>
+any work should someone raise a valid objection.</p>
+<h2 id="avoiding-unnecessary-discussion">Avoiding unnecessary discussion</h2>
 <p>The key thing about lazy consensus is that it&rsquo;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
+by doing nothing, than it is to object, which requires them to propose an alternative. This
has two effects: first, people are less
+likely to object for the sake of objecting and, second, it cuts down on the amount
+of unnecessary email traffic and discussion.</p>
+<p>Lazy consensus lets us avoid having to wait for a community-based decision
+before proceeding. However, it does require everyone who cares about 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
+far down the road will cause upset, while 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>
+<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 project but are not sure that there will be consensus. In these
-circumstances they may not wish to proceed with the work without giving the
-community an opportunity to feedback. In these circumstances they can make the
-proposal and 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="/committers/consensusBuilding.html">express
support or objections</a> and corrections to
-the proposal before work begins.</p>
+one for the project but is not sure that there will be consensus. They may not wish to proceed
with the work without giving the
+community an opportunity to provide feedback. In these circumstances they can make the
+proposal and state that lazy consensus is in operation, like this:</p>
+<ul>
+<li>In an email to <code>dev@PROJECT</code>, they state their proposal,
with sufficient supporting material for someone familiar with the project to understand it.</li>
+<li>In the email they indicate that they will start
+implementing the proposal in 72 hours unless someone objects. The time period takes into
account that project members are a) busy and b) in time zones around the world.</li>
+</ul>
+<p>In this approach the the proposer does not insist that the developer community discuss
or explicitly support the proposal. However, it allows space and time to <a href="/committers/consensusBuilding.html">express
support or objections</a> or propose 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
+<p>People may choose to indicate their support for the proposal 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>
+remember, in a lazy consensus world silence is equivalent to support.</p>
 
 
     </div>
diff --git a/content/index.xml b/content/index.xml
index 9ac4149..b397f7e 100644
--- a/content/index.xml
+++ b/content/index.xml
@@ -284,7 +284,7 @@ Here&amp;rsquo;s an example of what your first most might look like:</descriptio
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
       <guid>https://community.apache.org/committers/lazyConsensus.html</guid>
-      <description>The concept of &amp;ldquo;Lazy Consensus&amp;rdquo; is very
important in our 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&amp;rsquo;t have to insist people discuss and/or approve
your plan, and you certainly don&amp;rsquo;t need to call a vote to get approval. You
just assume you have the communities support unle [...]
+      <description>The concept of &amp;ldquo;lazy consensus&amp;rdquo; is very
important in your project. Lazy consensus means that when you are convinced that you know
what the community would like to see happen, you can assume that you have consensus in favor
of the proposed work and and get on with it. You don&amp;rsquo;t have to insist people
discuss and/or approve your plan, and you certainly don&amp;rsquo;t need to call a vote
to get approval.</description>
     </item>
     
     <item>
diff --git a/content/sitemap.xml b/content/sitemap.xml
index ee4b866..5851d8b 100644
--- a/content/sitemap.xml
+++ b/content/sitemap.xml
@@ -89,7 +89,7 @@
   
   <url>
     <loc>https://community.apache.org/committers.html</loc>
-    <lastmod>2020-12-01T10:29:20-04:00</lastmod>
+    <lastmod>2020-12-02T10:18:35-04:00</lastmod>
   </url>
   
   <url>
@@ -169,7 +169,7 @@
   
   <url>
     <loc>https://community.apache.org/committers/lazyConsensus.html</loc>
-    <lastmod>2020-03-24T15:03:46+01:00</lastmod>
+    <lastmod>2020-12-02T10:18:35-04:00</lastmod>
   </url>
   
   <url>


Mime
View raw message