Author: bhavanki
Date: Wed Mar 19 16:59:20 2014
New Revision: 1579297
URL: http://svn.apache.org/r1579297
Log:
Fix punctuation and typographical errors
Modified:
accumulo/site/trunk/content/bylaws.mdtext
Modified: accumulo/site/trunk/content/bylaws.mdtext
URL:
http://svn.apache.org/viewvc/accumulo/site/trunk/content/bylaws.mdtext?rev=1579297&r1=1579296&r2=1579297&view=diff
==============================================================================
--- accumulo/site/trunk/content/bylaws.mdtext (original)
+++ accumulo/site/trunk/content/bylaws.mdtext Wed Mar 19 16:59:20 2014
@@ -54,15 +54,15 @@ It is the custom of the Accumulo project
## Project Management Committee
-The role of the PMC from a Foundation perspective is
[oversight](http://apache.org/foundation/how-it-works.html#pmc). The main
-role of the PMC is not code and not coding - but to ensure that all legal
+The role of the PMC, from a Foundation perspective, is
[oversight](http://apache.org/foundation/how-it-works.html#pmc). The main
+role of the PMC is not code and not coding, but to ensure that all legal
issues are addressed, that procedure is followed, and that each and every
release is the product of the community as a whole. That is key to our
litigation protection mechanisms.
-Secondly the role of the PMC is to further the long term development and
+Secondly, the role of the PMC is to further the long-term development and
health of the community as a whole, and to ensure that balanced and wide
-scale peer review and collaboration does happen. Within the ASF we worry
+scale peer review and collaboration does happen. Within the ASF, we worry
about any community which centers around a few individuals who are working
virtually uncontested. We believe that this is detrimental to quality,
stability, and robustness of both code and long term social structures.
@@ -121,14 +121,14 @@ There are the types of approvals that ca
<tr><td>Consensus Approval</td>
<td>A consensus approval vote passes with 3 binding +1 votes and no
binding vetoes.</td>
<tr><td>Majority Approval</td>
- <td>A majority approval vote passes with 3 binding +1 votes and more
binding +1 votes that -1 votes.</td>
+ <td>A majority approval vote passes with 3 binding +1 votes and more
binding +1 votes than -1 votes.</td>
<tr><td>Lazy Approval (or Lazy Consensus)</td>
<td>An action with lazy approval is implicitly allowed unless a -1 vote is
received, at which time, depending on the type of action, either majority
approval or consensus approval must be obtained.</td>
</table>
## Vetoes
-A valid, binding veto cannot be overruled. If a veto is cast, it must be
accompanied by a valid reason explaining the veto. The validity of a veto, if
challenged, can be confirmed by anyone who has a binding vote. This does not
necessarily signify agreement with the veto - merely that the veto is valid.
+A valid, binding veto cannot be overruled. If a veto is cast, it must be
accompanied by a valid reason explaining the veto. The validity of a veto, if
challenged, can be confirmed by anyone who has a binding vote. This does not
necessarily signify agreement with the veto, but merely that the veto is valid.
If you disagree with a valid veto, you must lobby the person casting the veto
to withdraw his or her veto. If a veto is not withdrawn, the action that has
been vetoed must be reversed in a timely manner.
