Return-Path: 
 <derby-commits-return-3218-apmail-db-derby-commits-archive=db.apache.org@db.apache.org>
Delivered-To: apmail-db-derby-commits-archive@www.apache.org
Received: (qmail 784 invoked from network); 4 May 2006 16:28:30 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 4 May 2006 16:28:30 -0000
Received: (qmail 12735 invoked by uid 500); 4 May 2006 16:28:27 -0000
Delivered-To: apmail-db-derby-commits-archive@db.apache.org
Received: (qmail 12663 invoked by uid 500); 4 May 2006 16:28:25 -0000
Mailing-List: contact derby-commits-help@db.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:derby-commits-help@db.apache.org>
list-unsubscribe: <mailto:derby-commits-unsubscribe@db.apache.org>
List-Post: <mailto:derby-commits@db.apache.org>
Reply-To: "Derby Development" <derby-dev@db.apache.org>
List-Id: <derby-commits.db.apache.org>
Delivered-To: mailing list derby-commits@db.apache.org
Received: (qmail 12640 invoked by uid 99); 4 May 2006 16:28:25 -0000
Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 04 May 2006 09:28:25 -0700
X-ASF-Spam-Status: No, hits=-9.4 required=10.0
	tests=ALL_TRUSTED,NO_REAL_NAME
X-Spam-Check-By: apache.org
Received: from [209.237.227.194] (HELO minotaur.apache.org) (209.237.227.194)
    by apache.org (qpsmtpd/0.29) with SMTP; Thu, 04 May 2006 09:28:24 -0700
Received: (qmail 444 invoked by uid 65534); 4 May 2006 16:28:03 -0000
Message-ID: <20060504162803.443.qmail@minotaur.apache.org>
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: svn commit: r399752 - in /db/derby/site/trunk:
 build/site/derby_comm.html
 src/documentation/content/xdocs/derby_comm.xml
Date: Thu, 04 May 2006 16:28:03 -0000
To: derby-commits@db.apache.org
From: jta@apache.org
X-Mailer: svnmailer-1.0.8
X-Virus-Checked: Checked by ClamAV on apache.org
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N

Author: jta
Date: Thu May  4 09:27:58 2006
New Revision: 399752

URL: http://svn.apache.org/viewcvs?rev=399752&view=rev
Log:
Added a section on "Understand How Development Works at Apache" to the
Community page. Any committer should feel free to tweak this further.

Modified:
    db/derby/site/trunk/build/site/derby_comm.html
    db/derby/site/trunk/src/documentation/content/xdocs/derby_comm.xml

Modified: db/derby/site/trunk/build/site/derby_comm.html
URL: http://svn.apache.org/viewcvs/db/derby/site/trunk/build/site/derby_comm.html?rev=399752&r1=399751&r2=399752&view=diff
==============================================================================
--- db/derby/site/trunk/build/site/derby_comm.html (original)
+++ db/derby/site/trunk/build/site/derby_comm.html Thu May  4 09:27:58 2006
@@ -107,7 +107,10 @@
 <a href="#Provide+Feedback">Provide Feedback</a>
 </li>
 <li>
-<a href="#Communication+Channels">Communication Channels</a>
+<a href="#Use+the+Derby+Communication+Channels">Use the Derby Communication Channels</a>
+</li>
+<li>
+<a href="#Understand+How+Development+Works+at+Apache">Understand How Development Works at Apache</a>
 </li>
 <li>
 <a href="#Contribute+Code+or+Documentation">Contribute Code or Documentation</a>
@@ -165,8 +168,8 @@
 </div>
 
 
-<a name="N10040"></a><a name="Communication+Channels"></a>
-<h2 class="boxed">Communication Channels</h2>
+<a name="N10040"></a><a name="Use+the+Derby+Communication+Channels"></a>
+<h2 class="boxed">Use the Derby Communication Channels</h2>
 <div class="section">
 <p>
 The primary mechanism for Derby communication is 
@@ -205,7 +208,101 @@
 </div>
 
 
-<a name="N1005B"></a><a name="Contribute+Code+or+Documentation"></a>
+<a name="N1005B"></a><a name="Understand+How+Development+Works+at+Apache"></a>
+<h2 class="boxed">Understand How Development Works at Apache</h2>
+<div class="section">
+<p>
+New users and developers who are familiar with how development occurs
+on commercial products sometimes get confused by open source development 
+at Apache.
+</p>
+<p>
+The first thing to understand is <strong>individuals</strong> 
+volunteer for various tasks. Here are some relevant quotes from the
+<a class="external" href="http://www.apache.org/foundation/how-it-works.html">How the ASF works</a>
+page:
+</p>
+<ul>
+   
+<li>
+<em>"Projects are normally auto governing and driven by the people who
+volunteer for the job. This is sometimes referred to as "do-ocracy"
+-- power of those who do. This functions well for most cases."</em>
+   
+</li>
+
+   
+<li>
+<em>"All of the ASF including the board, the other officers, the
+   committers, and the members, are participating as individuals.
+   That is one strength of the ASF, affiliations do not cloud the
+   personal contributions.<br>
+   Unless they specifically state otherwise, whatever they post on any
+   mailing list is done *as themselves*. It is the individual
+   point-of-view, wearing their personal hat and not as a mouthpiece
+   for whatever company happens to be signing their paychecks right
+   now, and not even as a director of the ASF."</em>
+   
+</li>
+
+</ul>
+<p>
+However, lest it look like everybody is working diligently solely as an
+individual (and possibly at cross purposes with others), 
+community coordination and contribution occurs on the Apache mail lists.
+The 
+<a class="external" href="http://www.apache.org/foundation/how-it-works.html">How the ASF works</a>
+page provides helpful context.
+</p>
+<p>
+So, Derby depends on the community to work together as a whole
+to change the product.
+How can new Derby users and developers actively participate in these changes?
+</p>
+<p>
+First, 
+<a href="http://db.apache.org/derby/DerbyBugGuidelines.html">open Jira issues</a>
+to report problems you have stumbled upon or to request new features. 
+However, remember
+that volunteers fix issues -- a valuable reminder from the ASF
+<a class="external" href="http://www.apache.org/foundation/faq.html#what-is-apache-NOT-about">FAQ</a>
+is below:
+</p>
+<ul>
+  
+<li>
+<em>What is Apache not about?</em>
+   
+<ul>
+
+    
+<li> 
+<em>To </em>[...] 
+          <em>demand someone else to fix your bugs.</em>
+</li>
+   
+</ul>
+   
+</li>
+
+</ul>
+<p>
+Second, vote on Jira issues that you feel strongly should be fixed. 
+</p>
+<p>
+Third, participate even more in the Derby development
+process by subscribing to 
+<a href="derby_mail.html">derby-dev@db.apache.org</a>. That's
+where core development discussions occur and decisions get made.
+</p>
+<p>
+Fourth, if you want to actually start doing development, the
+next section is tailored specifically for you.
+</p>
+</div>
+
+
+<a name="N100B3"></a><a name="Contribute+Code+or+Documentation"></a>
 <h2 class="boxed">Contribute Code or Documentation</h2>
 <div class="section">
 <p>
@@ -429,7 +526,7 @@
 
 <p>
 
-<em>Last updated: March 3, 2006</em>
+<em>Last updated: May 4, 2006</em>
 
 </p>
 

Modified: db/derby/site/trunk/src/documentation/content/xdocs/derby_comm.xml
URL: http://svn.apache.org/viewcvs/db/derby/site/trunk/src/documentation/content/xdocs/derby_comm.xml?rev=399752&r1=399751&r2=399752&view=diff
==============================================================================
--- db/derby/site/trunk/src/documentation/content/xdocs/derby_comm.xml (original)
+++ db/derby/site/trunk/src/documentation/content/xdocs/derby_comm.xml Thu May  4 09:27:58 2006
@@ -52,7 +52,7 @@
 </section>
 
 <section>
-<title>Communication Channels</title>
+<title>Use the Derby Communication Channels</title>
 
 <p>
 The primary mechanism for Derby communication is 
@@ -95,6 +95,94 @@
 </section>
 
 <section>
+<title>Understand How Development Works at Apache</title>
+
+<p>
+New users and developers who are familiar with how development occurs
+on commercial products sometimes get confused by open source development 
+at Apache.
+</p>
+
+<p>
+The first thing to understand is <strong>individuals</strong> 
+volunteer for various tasks. Here are some relevant quotes from the
+<a href="http://www.apache.org/foundation/how-it-works.html">How the ASF works</a>
+page:
+</p>
+
+<ul>
+   <li><em>"Projects are normally auto governing and driven by the people who
+volunteer for the job. This is sometimes referred to as "do-ocracy"
+-- power of those who do. This functions well for most cases."</em>
+   </li>
+
+   <li><em>"All of the ASF including the board, the other officers, the
+   committers, and the members, are participating as individuals.
+   That is one strength of the ASF, affiliations do not cloud the
+   personal contributions.<br/>
+   Unless they specifically state otherwise, whatever they post on any
+   mailing list is done *as themselves*. It is the individual
+   point-of-view, wearing their personal hat and not as a mouthpiece
+   for whatever company happens to be signing their paychecks right
+   now, and not even as a director of the ASF."</em>
+   </li>
+</ul>
+
+<p>
+However, lest it look like everybody is working diligently solely as an
+individual (and possibly at cross purposes with others), 
+community coordination and contribution occurs on the Apache mail lists.
+The 
+<a href="http://www.apache.org/foundation/how-it-works.html">How the ASF works</a>
+page provides helpful context.
+</p>
+
+<p>
+So, Derby depends on the community to work together as a whole
+to change the product.
+How can new Derby users and developers actively participate in these changes?
+</p>
+
+<p>
+First, 
+<a href="http://db.apache.org/derby/DerbyBugGuidelines.html">open Jira issues</a>
+to report problems you have stumbled upon or to request new features. 
+However, remember
+that volunteers fix issues -- a valuable reminder from the ASF
+<a href="http://www.apache.org/foundation/faq.html#what-is-apache-NOT-about">FAQ</a>
+is below:
+</p>
+
+<ul>
+  <li><em>What is Apache not about?</em>
+   <ul>
+
+    <li> <em>To </em>[...] 
+          <em>demand someone else to fix your bugs.</em></li>
+   </ul>
+   </li>
+</ul>
+
+<p>
+Second, vote on Jira issues that you feel strongly should be fixed. 
+</p>
+
+<p>
+Third, participate even more in the Derby development
+process by subscribing to 
+<a href="derby_mail.html">derby-dev@db.apache.org</a>. That's
+where core development discussions occur and decisions get made.
+</p>
+
+<p>
+Fourth, if you want to actually start doing development, the
+next section is tailored specifically for you.
+</p>
+
+
+</section>
+
+<section>
 <title>Contribute Code or Documentation</title>
 
 <p>
@@ -288,7 +376,7 @@
 </section>
 
 <p>
-<em>Last updated: March 3, 2006</em>
+<em>Last updated: May 4, 2006</em>
 </p>
 
 </body>