You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@couchdb.apache.org by GitBox <gi...@apache.org> on 2019/07/02 22:14:05 UTC

[GitHub] [couchdb-www] wohali commented on a change in pull request #31: Nomi/bylaws

wohali commented on a change in pull request #31: Nomi/bylaws
URL: https://github.com/apache/couchdb-www/pull/31#discussion_r299702042
 
 

 ##########
 File path: bylaws.html
 ##########
 @@ -11,99 +11,99 @@ <h1>CouchDB Bylaws</h1>
 <p><em>This document was officially adopted by the CouchDB PMC as of 31 July 2014.</em></p>
 <p>A full changelog is available <a href="https://github.com/apache/couchdb-www/commits/asf-site/bylaws.html">on GitHub</a>.</p>
 
-<h2>Table of Contents</h2>
+<h2>Table of contents</h2>
 
 <div class="toc"></div>
 
 <h2 id="intro">1. Introduction</h2>
 
-<p>This document defines the bylaws under which the Apache CouchDB project operates. It defines the <a href="#roles">roles and responsibilities</a> within the project, who may vote, how <a href="#voting">voting</a> works, how conflicts are resolved, and voting rules for specific <a href="#types">decision types</a>.
+<p>This document defines the bylaws under which the Apache CouchDB project operates. It describes the <a href="#roles">roles and responsibilities</a> within the project, who may vote, how <a href="#voting">voting</a> works, how to resolve conflicts, and specifies voting rules for specific <a href="#types">decision types</a>.
 
-<p>This document is written for anyone who wishes to participate in the project. <strong>If this is your first time through this document, read this introduction, then read all the bolded text for a summary of the bylaws.</strong> Then, as you need more detail, read past the bolded text for an expanded explanation.
+<p>This document is for anyone who wishes to participate in the project. <strong>If this is your first time through this document, read this introduction, then read all the bolded text for a summary of the bylaws.</strong> Then, as you want, read past the bolded text for an expanded explanation.
 
-<p>CouchDB is a project of the <em>Apache Software Foundation</em> (ASF). Apache CouchDB, CouchDB, and the CouchDB logo are trademarks of the ASF. The project resources are licensed to the public under the <a href="http://www.apache.org/licenses/LICENSE-2.0.html">Apache License 2.0</a>. Releases are made in the form of official signed source code archives. The <a href="https://www.apache.org/foundation/faq.html">ASF FAQ</a> explains the operation and background of the Foundation.
+<p>CouchDB is a project of the <em>Apache Software Foundation</em> (ASF). Apache CouchDB, CouchDB, and the CouchDB logo are trademarks of the ASF. We license the project resources to the public under the <a href="http://www.apache.org/licenses/LICENSE-2.0.html">Apache License 2.0</a>. We make releases in the form of officially signed source code archives. The <a href="https://www.apache.org/foundation/faq.html">ASF FAQ</a> explains the operation and background of the foundation.
 
-<p>CouchDB operates under a set of common principles known collectively as <a href="https://www.apache.org/foundation/how-it-works.html">the Apache Way</a>:
+<p>CouchDB operates under a set of shared principles known collectively as <a href="https://www.apache.org/foundation/how-it-works.html"><em>the Apache Way</em></a>:
 
   <ul>
     <li>Collaborative software development
     <li>Commercial-friendly standard license
-    <li>Consistently high quality software
+    <li>Consistently high-quality software
     <li>Respectful, honest, technical-based interaction
     <li>Faithful implementation of standards
     <li>Security as a mandatory feature
   </ul>
 
-<p>We value the community more than the code. A strong and healthy community should be a fun and rewarding place for everyone involved. Code, and everything else that goes with that code, will be produced by a healthy community over time.
+<p>We value the community more than the code. A healthy community should be a fun and rewarding place for everyone involved. A healthy community will produce written code (and everything else) over time. The same is not true in reverse.
 
-<p>The direction of the project and the decisions we make are up to you. If you are participating on <a href="https://couchdb.apache.org/#mailing-lists">the mailing lists</a> you have the right to make decisions. All decisions about the project are taken on the mailing lists. There are no lead developers, nor is there any one person in charge.
+<p>The direction of the project and the decisions we make are up to you. If you are participating on <a href="https://couchdb.apache.org/#mailing-lists">the mailing lists</a>, you have the right to make decisions. We make all decisions about the project on the mailing lists. There are no lead developers, nor is there any one person in charge.
 
-<p>Anyone can subscribe to the public mailing lists, and in fact, you are encouraged to do so. The development mailing list is not just for developers, for instance. It is for anyone who is interested in the development of the project. Everybody's voice is welcome.
+<p>Anyone can subscribe to the public mailing lists, and in fact, you are encouraged to do so. The development mailing list is not just for developers, for instance. It is for anyone interested in the development of the project. Everybody's voice is welcome.
 
-<p>Finally, use of these bylaws to enforce the letter of any rule and not its spirit (also known as "<a href="https://en.wikipedia.org/wiki/Rules_lawyer">rule lawyering</a>") is not acceptable behaviour.
+<p>Finally, the use of these bylaws to enforce the letter of any rule and not its spirit (also known as "<a href="https://en.wikipedia.org/wiki/Rules_lawyer">rule lawyering</a>") is not acceptable behavior.
 
 Review comment:
   -0.5. In general we've preferred the UK spellings in documentation, so we might as well do that here too: behaviour, not behavior.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services