[comdev-site] branch master updated: Update consensusBuilding.md

[rb...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

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


The following commit(s) were added to refs/heads/master by this push:
     new 5ec9e6f  Update consensusBuilding.md
     new 3a91f7c  Merge pull request #27 from cottage14/patch-12
5ec9e6f is described below

commit 5ec9e6faca9e9000419da6f9445b8908062ce7b1
Author: Andrew Wetmore <an...@cottage14.com>
AuthorDate: Wed Dec 2 09:52:19 2020 -0400

    Update consensusBuilding.md
    
    Minor edits to improve clarity and readability
---
 source/committers/consensusBuilding.md | 31 ++++++++++++++-----------------
 1 file changed, 14 insertions(+), 17 deletions(-)

diff --git a/source/committers/consensusBuilding.md b/source/committers/consensusBuilding.md
index 406b7c1..e8cdfc1 100644
--- a/source/committers/consensusBuilding.md
+++ b/source/committers/consensusBuilding.md
@@ -3,18 +3,16 @@ title: Consensus Building
 ---
 
 In some cases there is no obvious path to take, or you might be a new community, 
-or a new member of an existing community. In these cases people will often 
+or a new member of an existing community. In these cases people often 
 need to build consensus by making proposals and eliciting responses.
 
-We want to avoid unnecessary discussion and the creation of significant
-amounts of unnecessary mail that everyone in the community needs to read. 
-That is not to say that we want to avoid constructive discussion. This is 
-the lifeblood of a successful project. However, many ASF projects adopt a 
+Constructive discussion is the lifeblood of a successful project. However, we want to avoid unnecessary discussion and significant
+amounts of unnecessary mail that everyone in the community needs to read. so many ASF projects adopt a 
 shorthand notation for showing support, or otherwise, for a proposal.
 
 ## Expressing support (or otherwise)
 
-First of all, it is important to understand that everyone is invited to express 
+It is important to understand that everyone is invited to express 
 their opinion of any given action or proposal. Apache projects are community 
 projects in which no single individual has more power than any other single 
 individual (except in a very few procedural situations).
@@ -31,27 +29,26 @@ my opinion is not that important"
   - -1 means "I don't agree and I am offering an alternative that I am able 
 to help implement"
 
-Many people will use fractions to indicate the strength of their feelings,
- e.g. "+0.5". Some will even indicate this is a "no brainer" with something 
+Many people use fractions to indicate the strength of their feelings,
+ e.g. "+0.5". Some will even indicate their opinion that the proposal is a "no brainer" with something 
 like "+1000".
 
-The important thing is that this is not an exact science. It's just a shorthand 
+This notation is not an exact science. It's just a shorthand 
 way of communicating strength of feeling.
 
-## Consensus Building is Not Voting
+## Consensus building is not voting
 
-The confusing thing about this notation is that it is the same notation
+A confusing thing about this notation is that it is the same notation
 used in a formal vote. Knowing when something is a vote and when it is a 
-preference is important. It's easy to tell though, if the subject does not have 
-"[Vote]" at the start then it's just an opinion. We try not to call votes,
+preference is important. It's easy to tell, though: if the subject line of the email thread does not have 
+"[Vote]" at the start then it's just an opinion. We try not to call votes;
 consensus building is much more inclusive.
 
 The reasons for this notation being common is that when someone wants to
 summarise a discussion thread they can mentally 
-add up the strength of feeling of the community and decide if there is consensus
-or not.
+add up the strength of feeling of the community and decide whether there is consensus.
 
-Once there is a clear consensus members of the community can proceed with 
+If there is clear consensus in favor of a proposal, members of the community can proceed with 
 the work under the [lazy consensus][1] model.
 
-  [1]: /committers/lazyConsensus.html
\ No newline at end of file
+  [1]: /committers/lazyConsensus.html