community-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r985397 - in /websites/staging/community/trunk/content: ./ contributors/etiquette.html
Date Mon, 11 Apr 2016 17:58:41 GMT
Author: buildbot
Date: Mon Apr 11 17:58:41 2016
New Revision: 985397

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 Mon Apr 11 17:58:41 2016
@@ -1 +1 @@

Added: websites/staging/community/trunk/content/contributors/etiquette.html
--- websites/staging/community/trunk/content/contributors/etiquette.html (added)
+++ websites/staging/community/trunk/content/contributors/etiquette.html Mon Apr 11 17:58:41
@@ -0,0 +1,287 @@
+<!DOCTYPE html>
+    Licensed to the Apache Software Foundation (ASF) under one or more
+    contributor license agreements.  See the NOTICE file distributed with
+    this work for additional information regarding copyright ownership.
+    The ASF licenses this file to You under the Apache License, Version 2.0
+    (the "License"); you may not use this file except in compliance with
+    the License.  You may obtain a copy of the License at
+    Unless required by applicable law or agreed to in writing, software
+    distributed under the License is distributed on an "AS IS" BASIS,
+    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+    See the License for the specific language governing permissions and
+    limitations under the License.
+  <META name="description" content="Apache Community Development"/>
+  <META name="keywords" content="apache, apache community, community development, opensource"/>
+  <META http-equiv="Content-Type" content="text/html; charset=utf-8">
+  <link href="/css/bootstrap.min.css" rel="stylesheet" media="screen">
+  <link href="/css/bootstrap-responsive.css" rel="stylesheet">
+  <style type="text/css">
+      body {
+        padding-top: 60px;
+        padding-bottom: 40px;
+      }
+	  /* Google Search box customizations */
+	   .gsc-search-box input.gsc-input, .gcse-search-box input.gsc-input:focus { -webkit-box-shadow:none;
box-shadow:none; -moz-box-shadow:none; border-radius:0px; }
+		/* On tablets, the wrapped menu is hiding the search box, adding a margin to push down
+		 .container { margin-top:5px; }
+  </style>
+  <LINK rel="SHORTCUT ICON" href="images/favicon.ico">   
+  <TITLE>Apache Community Development - Apache Community Etiquette Guidelines</TITLE>
+    <div class="navbar navbar-inverse navbar-fixed-top">
+      <div class="navbar-inner">
+        <div class="container">
+          <button type="button" class="btn btn-navbar" data-toggle="collapse" data-target=".nav-collapse">
+            <span class="icon-bar"></span>
+            <span class="icon-bar"></span>
+            <span class="icon-bar"></span>
+          </button>
+          <!-- <a class="brand" href="#">Apache Community Development Project</a>
+          <div class="nav-collapse collapse">
+            <ul class="nav">
+              <li><a href="/">Home</a></li>
+              <li class="dropdown">
+                <a href="#" class="dropdown-toggle" data-toggle="dropdown">GSoC <b
+                <ul class="dropdown-menu">
+                  <li><a href="gsoc.html">Google Summer Of Code Information</a></li>
+                  <li><a href="mentee-ranking-process.html">Mentee Ranking Process</a></li>
+                  <li><a href="mentoring/experiences.html">Past GSoC Experiences</a></li>
+                  <li class="divider"></li>
+                  <li class="nav-header">Additional GSoC Resources</li>
+                  <li><a href="/links.html">Links to additional material</a></li>
+                  <li><a href="guide-to-being-a-mentor.html">Guide to being a
+                  <li><a href="use-the-comdev-issue-tracker-for-gsoc-tasks.html">Using
ComDev's JIRA for GSoC Ideas</a></li>
+                  <li><a href="gsoc-admin-tasks.html">Tasks of a GSoC Admin at
the ASF</a></li>
+                </ul>
+              </li>
+              <li class="dropdown">
+                <a href="#" class="dropdown-toggle" data-toggle="dropdown">General
Information <b class="caret"></b></a>
+                <ul class="dropdown-menu">
+                  <li><a href="/newbiefaq.html">Frequently Asked Questions</a></li>
+                  <li><a href="/projectIndependence.html">Apache Project Independence</a></li>
+                  <li><a href="/apache-way/apache-project-maturity-model.html">Apache
Project Maturity Model</a></li>
+                  <li><a href="/contactpoints.html">Contact Points Within the
+                  <li class="divider"></li>
+                  <li class="nav-header">Additional Resources</li>
+                  <li><a href="/comdevboardresolution.html">ComDev Original Board
+                  <li><a href="/comdevboardreports.html">ComDev Board Reports</a></li>
+                </ul>
+              </li>
+              <li class="dropdown">
+                <a href="#" class="dropdown-toggle" data-toggle="dropdown">For Contributors
<b class="caret"></b></a>
+                <ul class="dropdown-menu">
+                  <li><a href="/newcomers/">Newcomers</a></li>
+                  <li><a href="/gettingStarted/101.html">Getting Started</a></li>
+                  <li><a href="/contributors/">Finding Your Way Around The Apache
Software Foundation</a></li>
+				  <li><a href="">Technical Developer FAQs</a></li>
+                </ul>
+              </li>
+              <li class="dropdown">
+                <a href="#" class="dropdown-toggle" data-toggle="dropdown">For Committers/PMCs
<b class="caret"></b></a>
+                <ul class="dropdown-menu">
+                  <li><a href="/boardreport.html">Board Report Template</a></li>
+                  <li><a href="/newcommitter.html">Recruiting New Committers</a></li>
+                  <li><a href="/committers/">Useful Information for Committers</a></li>
+                  <li><a href="/committers/lazyConsensus.html">Lazy Consensus</a></li>
+                  <li><a href="/committers/consensusBuilding.html">Consensus
+                  <li><a href="/committers/decisionMaking.html">Decision Making</a></li>
+                  <li><a href="/committers/voting.html">Voting</a></li>
+                  <li><a href="/committers/funding-disclaimer.html">Funding Campaign
+                </ul>
+              </li>
+              <li class="dropdown">
+                <a href="#" class="dropdown-toggle" data-toggle="dropdown">Mentoring
<b class="caret"></b></a>
+                <ul class="dropdown-menu">
+                  <li><a href="/mentoringprogramme.html">Mentoring Program</a></li>
+                  <li><a href="/mentorprogrammeformaleducation.html">Mentoring
in Formal Education</a></li>
+                  <li><a href="/mentorprogrammeapplication.html">Applying for
the Mentoring Program</a></li>
+                  <li class="divider"></li>
+                  <li class="nav-header">Additional Resources</li>
+                  <li><a href="guide-to-being-a-mentor.html">Guide to being a
+                  <li><a href="mentor-request-mail.html">Mentor Request Email
+                  <li><a href="localmentors.html">Mentors Near You</a></li>
+                </ul>
+              </li>
+              <li class="dropdown">
+                <a href="#" class="dropdown-toggle" data-toggle="dropdown">Speakers
<b class="caret"></b></a>
+                <ul class="dropdown-menu">
+                  <li><a href="/speakers/">Speaker Information</a></li>
+                  <li><a href="/speakers/speakers.html">Finding Speakers / Listing
Yourself as a Speaker</a></li>
+                  <li><a href="/speakers/slides.html">Apache-related Slides</a></li>
+                </ul>
+              </li>
+              <li class="dropdown">
+                <a href="#" class="dropdown-toggle" data-toggle="dropdown">Calendars
<b class="caret"></b></a>
+                <ul class="dropdown-menu">
+                  <li><a href="/calendars/">Calendars</a></li>
+                  <li><a href="/calendars/conferences.html">Conferences</a></li>
+                </ul>
+              </li>
+              <li><a href="/lists.html">Mailing List</a></li>
+            </ul>
+          </div><!--/.nav-collapse -->
+        </div>
+      </div>
+    </div>
+  <div class="container">
+    <section id="content" class="row">
+      <div class="span9">
+        <h3 class="muted">The Apache Software Foundation</h3>
+      </div>
+      <div class="span3 pull-right">
+        <div class="gcse-search"></div>
+  	  </div>
+      <div class="span12"><h4 class="muted">Meritocracy in Action.</h4></div>
+    </section>
+    <ul class="breadcrumb">
+<li><a href="/">Home</a> <span class="divider">/</span></li>
+<li><a href="/contributors">Contributors</a> <span class="divider">/</span></li>
+<li><a href="/contributors/etiquette.html">Apache Community Etiquette Guidelines</a></li>
+   <hr>
+    <style type="text/css">
+/* The following code is added by
+   It was originally lifted from */
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+  visibility: hidden;
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover
> .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink
{ visibility: visible }</style>
+<p>The Apache Software Foundation (ASF) and our many Apache projects welcome all 
+participants who are willing to respect our community guidelines.  There are 
+many behavior or etiquette guides for online communities out there; we have a few 
+Apache-specific tips below.</p>
+<h1 id="coc">Code of Conduct<a class="headerlink" href="#coc" title="Permanent link">&para;</a></h1>
+<p>The ASF has adopted a <a href="">Code
of Conduct</a> which covers interactions in 
+all the online spaces that Apache projects use - email, issue trackers, wikis, 
+websites, IRC, and the like.  Apache projects are made up of volunteers, and 
+we work to ensure that all productive contributions are welcomed.  Every 
+Apache PMC is expected to ensure their project's lists show 
+proper behavior.</p>
+<h1 id="worldwide">Distributed, Archived, Worldwide Online Communities<a class="headerlink"
href="#worldwide" title="Permanent link">&para;</a></h1>
+<p>Apache projects are made up of communities of volunteers from around the 
+world.  When you are sending email to an Apache project mailing list, there may 
+be software developers in this country, marketing managers in that country, and 
+homemakers in another country reading your email.  They will be reading your 
+mail at all hours of the day, and both at work, at home, and on the go.  If you 
+want a response to your questions or suggestions, be sure to be polite and 
+sensible when writing.</p>
+<p>There are many amazing people helping out on Apache project mailing 
+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

+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>
+<p>Assume that the other party agrees more than disagrees with you. We
+tend to leave out agreements and focus on differences. Sometime this is
+forgotten and escalation becomes absurd for no rational reason.</p>
+<p>When in doubt, assume that you are interpreting the message wrongly
+and kindly ask for verification that you understood a particular topic well.</p>
+<p>When writing, assume that every sentence will be misinterpreted.
+Review and try to reformulate to be as clear as possible.</p>
+<p>Use a submissive tone in all writing. Instead of the strong "In my
+opinion, we must..." or the quite neutral "I think we should...", try to
+use "Maybe we should consider..." or "Another idea that we could..."</p>
+<p>If you disagree strongly with an email sent, tag it Important, then
+put it aside. Read it half a day later again. Put it aside. Read it again
+next day, and then it is easier to write a balanced and inviting response,
+instead of the initial vitriol that flows through us when we get upset. I
+found that sometimes a response wouldn't be necessary, as the importance
+was actually much lower than originally perceived, and I would be able to
+work "with", instead of "against", a given change.</p>
+<p>Be forgiving and accept different priorities. The other person is not
+out to get you or attack your work. More often than not, it is one of the
+above (a-d) that are failing, or that the other person prioritize some
+aspect higher than you do. Sometimes, this requires compromises, sometimes
+not and the different priorities can co-exist.</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
+passion, is both the source of tension, but it is also what unites the
+people within the community. It is easy to forget the vast amount of
+agreement that exists, and get upset over relatively small disagreements.
+Ability to put that aside, or downplay the importance, will ensure a
+harmonious project.</p>
+<p><strong>Face-to-Face</strong> is excellent way to eliminate disagreements,
but that is often
+not practical. Consider Skype or Google Hangout, just for the social aspect
+of being part of this community. It should not be formal, and the
+invitation should go out to everyone, perhaps someone want to make a short
+presentation of what he/she is doing, to have some "structure", but that
+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 />
+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>
+<h1 id="other">Other Apache Etiquette Guidelines<a class="headerlink" href="#other"
title="Permanent link">&para;</a></h1>
+<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>
+  </div>
+  <footer class="footer" align="center">
+    <div class="container">
+      <p>
+        Copyright &copy; 2013-2015 The Apache Software Foundation, Licensed under
+        the <a href="">Apache License, Version
+        <br />
+        Apache and the Apache feather logos are trademarks of The Apache Software Foundation.
+      </p>
+    </div>
+  </footer>
+  <script src="/js/jquery-1.9.1.min.js"></script>
+  <script src="/js/bootstrap.min.js"></script>
+  <script>
+    (function() {
+      var cx = '012254517474945470291:vhsfv7eokdc';
+      var gcse = document.createElement('script');
+      gcse.type = 'text/javascript';
+      gcse.async = true;
+      gcse.src = (document.location.protocol == 'https:' ? 'https:' : 'http:') +
+          '//' + cx;
+      var s = document.getElementsByTagName('script')[0];
+      s.parentNode.insertBefore(gcse, s);
+    })();
+  </script>

View raw message