community-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r998435 - in /websites/staging/community/trunk/content: ./ contributors/etiquette.html
Date Wed, 28 Sep 2016 01:22:26 GMT
Author: buildbot
Date: Wed Sep 28 01:22:26 2016
New Revision: 998435

Staging update by buildbot for community

    websites/staging/community/trunk/content/   (props changed)

Propchange: websites/staging/community/trunk/content/
--- cms:source-revision (original)
+++ cms:source-revision Wed Sep 28 01:22:26 2016
@@ -1 +1 @@

Modified: websites/staging/community/trunk/content/contributors/etiquette.html
--- websites/staging/community/trunk/content/contributors/etiquette.html (original)
+++ websites/staging/community/trunk/content/contributors/etiquette.html Wed Sep 28 01:22:26
@@ -190,11 +190,11 @@ sensible when writing.</p>
 lists - but they are all volunteers.  Being respectful of the time and 
 culture of others on the list is a key start to making productive contributions.</p>
 <h1 id="member">One Member's Participation Guidelines<a class="headerlink" href="#member"
title="Permanent link">&para;</a></h1>
-<p>The ASF is run by several hundred Members, who have deep and lasting experience

+<p>The ASF as a corporation is run by several hundred Members, who have deep and lasting
 in helping to build and run long-term successful open source projects here 
 at Apache.  This is just one member's take on how to approach 
-communicating in an Apache project.</p>
-<p><strong>First a few general guidelines</strong></p>
+communicating in any particular Apache project.</p>
+<p><strong>Some General Guidelines</strong></p>
 <p>Assume that the other party agrees more than disagrees with you. We
@@ -230,6 +230,11 @@ above (a-d) that are failing, or that th
 aspect higher than you do. Sometimes, this requires compromises, sometimes
 not and the different priorities can co-exist.</p>
+<p>Remember that everyone works on Apache projects as a volunteer.
+People have jobs and lives outside of their Apache projects, and may need 
+more time to even read messages on the list or respond.  Be patient.</p>
 <p><strong>Most communities at Apache consists of level-headed, reasonable people</strong>,
 have a strong vested interest in their Apache project. This interest, often
@@ -246,13 +251,16 @@ presentation of what he/she is doing, to
 might not be needed either. Once we have a face to the words, and a general
 idea how that person is socially, we are much more capable to interact by
-<p>Note that project <em>decisions</em> should always be made on mailing
lists.<br />
+<p><strong>Project decisions must always be made on mailing lists</strong>.<br
 It's great to have a synchronous online chat to work through some questions, but 
 be sure to bring the results of the chat - and any proposals for the 
 project community to consider - back to the mailing list.  People who 
-weren't able to attend the chat or call might also have ideas on the topic.</p>
+weren't able to attend the chat or call might also have ideas on the topic.
+Be sure to allow at least 72 hours for others to read the proposals and 
+comment before closing out the issue.</p>
 <h1 id="other">Other Apache Etiquette Guidelines<a class="headerlink" href="#other"
title="Permanent link">&para;</a></h1>
+<li><a href="">Official
Apache-wide Code of Conduct</a></li>
 <li><a href="">Email Etiquette Guidelines
- writing good emails</a></li>
 <li><a href="">How To Ask Smart
 <li><a href="">Building
Consensus in a community</a></li>

View raw message