incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rdon...@apache.org
Subject svn commit: r426873 - in /incubator/public/trunk: site-author/guides/entry.xml site-author/guides/participation.xml site-author/guides/proposal.xml site-publish/guides/entry.html site-publish/guides/participation.html site-publish/guides/proposal.html
Date Sun, 30 Jul 2006 08:22:35 GMT
Author: rdonkin
Date: Sun Jul 30 01:22:34 2006
New Revision: 426873

URL: http://svn.apache.org/viewvc?rev=426873&view=rev
Log:
Content related to issue of piling on. Not particularly satisfied with the prose but hope
that the organisation is clear enough.

Added:
    incubator/public/trunk/site-author/guides/participation.xml
    incubator/public/trunk/site-publish/guides/participation.html
Modified:
    incubator/public/trunk/site-author/guides/entry.xml
    incubator/public/trunk/site-author/guides/proposal.xml
    incubator/public/trunk/site-publish/guides/entry.html
    incubator/public/trunk/site-publish/guides/proposal.html

Modified: incubator/public/trunk/site-author/guides/entry.xml
URL: http://svn.apache.org/viewvc/incubator/public/trunk/site-author/guides/entry.xml?rev=426873&r1=426872&r2=426873&view=diff
==============================================================================
--- incubator/public/trunk/site-author/guides/entry.xml (original)
+++ incubator/public/trunk/site-author/guides/entry.xml Sun Jul 30 01:22:34 2006
@@ -37,5 +37,64 @@
           </p>
         </section>
     </section>
+    <section id='understanding'><title>Understanding The Acceptance Process</title>
+            <p>
+The acceptance process is simple in theory but complex in practice.
+        </p>
+            <p>
+The theory is that candidates are accepted or rejected by a vote on a mailing lists. 
+Anyone can vote (and are <a href='participation.html#general-list'>encouraged</a>
to do so)
+but only eligable votes are binding on Apache. For candidates 
+<a href='/incubation/Roles_and_Responsibilities.html#Spondor'>Sponsored</a> 
+by the <code>Incubator</code> this means members of the 
+<a href='/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29'>Incubator
PMC</a>.
+        </p>
+            <p>
+In practice, the process is more complex for candidates who want to give themselves 
+the best chance of being accepted. 
+        </p>
+            <p>
+Apache policy is set by the Board either directly or through it's special committees. 
+The incubation PMC is responsible to the board and so it is the duty of each PMC member
+to vote against a proposal that does not adhere to this policy.
+        </p>
+            <p>
+<a href='/incubation/Incubation_Policy.html'>Incubation Policy</a> state clearly
when a . 
+All policy is decided by PMC vote and so represents an active consensus. Though PMC members
+are free to vote in whatever way they choose, it is reasonable to expect PMC members
+to vote against a proposal that does not satisfy policy. 
+        </p>
+            <p>
+However, satisfying current policy is not sufficient. Acceptance is a democractic process
+requiring positive approval by the electorate. The guides and other documentation are not
+policy. They are approved only through lazy consensus. 
+        </p>
+            <p>
+See:
+        </p>
+<ul><li>[links to posts and threads]</li></ul>
+    </section>
+    <section id='note'><title>Notes On The Process</title>
+        <section id='proposal'><title>The Proposal</title>
+            <p>
+        </p>
+    </section>
+        <section id='vote'><title>The Vote</title>
+            <p>
+When the proposal seems finished and some sort of consensus has emerged, the
+proposal can be put to the vote. 
+        </p>
+            <p>
+The right time is a matter for judgement. Ask the 
+<a href='/incubator/Roles_and_Responsibilites.html#Champion'>Champion</a> for
advice
+or ask on the mailing list. It is usually best to ensure that the discussions 
+and debates surrounding the proposal are complete before moving to a vote. This may 
+mean move discussions which are not about the proposal to separate threads.
+        </p>
+            <p>
+The right duration for the vote is also a matter for judgement [link]. 
+        </p>
+    </section>
+ </section>   
   </body>
 </document>

Added: incubator/public/trunk/site-author/guides/participation.xml
URL: http://svn.apache.org/viewvc/incubator/public/trunk/site-author/guides/participation.xml?rev=426873&view=auto
==============================================================================
--- incubator/public/trunk/site-author/guides/participation.xml (added)
+++ incubator/public/trunk/site-author/guides/participation.xml Sun Jul 30 01:22:34 2006
@@ -0,0 +1,121 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<document>
+  <properties>
+    <title>A Guide To Participation (DRAFT)</title>
+    <atom url="http://mail-archives.apache.org/mod_mbox/incubator-general/?format=atom">general@incubator.apache.org
Archives</atom>
+  </properties>
+  <body>
+      <section id="preamble">
+        <title>A Guide To Participation (DRAFT)</title>
+        <section id="status">
+          <title>Status - DRAFT</title>
+          <p>
+This document is under <a href='#help-wanted'>development</a>. This is the first

+draft intended to allow public review. 
+          </p>
+        </section>
+        <section id="abstract">
+            <title>Abstract</title>
+            <p>
+This document is descriptive not normative. It aims to help those who are new 
+to the Incubator learn it's ways and netiquette.
+          </p>
+        </section>
+            <section><title>General Netiquette</title>
+                <p>
+The incubator is a public meeting place with a diverse and ever changing community. 
+Creating social bonds and establishing a reputation is important. Please be polite, 
+courteous and diplomatic. 
+            </p>
+                <p>
+When in doubt - ask on <code>general.AT.incubator.apache.org</code>.
+            </p>
+                <p>
+The usual advice applies. If you are not familiar with the way mailing lists
+work at Apache, read <a href='http://jakarta.apache.org/site/mail.html'>this</a>.
+            </p>
+        </section>
+                <section id="help-wanted">
+          <title>Help Wanted!</title>
+          <p>
+Help to improve the system by posting a patch for this document to the
+incubator section of JIRA or a comment to the general list at incubator.
+          </p>
+        </section>
+    </section>
+        <section id='ways'><title>Ways To Participate</title>
+            <section id='developer'><title>As A Developer</title>
+                [link to jakarta document?]
+                <p>
+If you are interested in development and Apache does not have a 
+<a href='http://www.apache.org/licenses/icla.txt'>Contributor License Agreement</a>
(CLA) on file it will save time if 
+you <a href='http://www.apache.org/licenses/#clas'>submit</a> one now. 
+            </p>
+            [link to roles and responsibilities]
+        </section>
+            <section id='committer'><title>As A Committer</title>
+                <p>
+Once a podling has been bootstrapped, <a href='#developer'>developers</a> are
nominated
+and elected in the usual way.
+            </p>
+                <p>
+When a proposal is just a candidate, there are two possible approaches.
+            </p>
+                <p>
+The proposal typically 
+<a href='proposal.html#template-initial-committers'>contains</a> a list of initial
committers.
+When a podling is bootstrapped, this list is used by the mentors to set up initial accounts.
+So, one way to become a committer for a podling is to be listed on the proposal as an initial
+committer.
+[link to roles and responsibilities]
+            </p>
+                <p>
+Piling onto a proposal by adding your own name as an initial committer is impolite.
+Read 
+<a href='http://mail-archives.apache.org/mod_mbox/incubator-general/200607.mbox/%3cC73C6D24-3216-4EB4-8846-1218B38CC594@gbiv.com%3e'>this
thread</a>.
+The right way to express interest is by a post to the list.
+            </p>
+                <p>
+A podling needs to learn how to recruit new committers from its developers. So,
+another way is to show up on the list and start helping with the development.
+This path will help the podling more than adding your name to the list of initial committers.
+            </p>
+        </section>
+            <section id='mentors'><title>As A Mentor</title>
+                <p>
+Anyone with knowledge of open source or Apache can participate as a informal mentor
+for a podling. Development is open and anyone with an interest is encouraged to 
+subscribe to the podling lists. 
+            </p>
+                <p>
+Eligibility to act as a formal 
+<a href='/incubation/Roles_And_Responsibilities.html#Mentor'>Mentor</a> is 
+<a href='/incubation/Incubation_Policy'>limited</a>. The best way for an eligable

+individuals to become a Mentors for a Podling is to post a note introducing themselves 
+and volunteering their services to <code>general.AT.incubator.apache.org</code>

+during the development of the <a href='proposal.html'>proposal</a>.
+            </p>
+        </section>
+            <section id='general-list'><title>On The General Mailing List</title>
+                <p>
+The <code>general.AT.incubator.apache.org</code> is an public list with open
subscription.
+All are encuraged to subscribe, read and post their opinions in the usual way. 
+[link to foundation documentation on list netiquette] 
+            </p>
+                <p>
+Anyone can influence the decision making process by their comments and may vote on VOTE
+threads. However (as is usual) only the votes of those on the incubator PMC are binding on
Apache.
+            </p>
+        </section>
+            <section id='pmcer'><title>On The Incubator PMC</title>
+                <p>
+Apache Members are encouraged to join the Incubator PMC.
+            </p>
+                <p>
+Those who aren't members may be elected in the usual Apache fashion after a history
+of contribution.
+            </p>
+        </section>
+    </section>
+  </body>
+</document>
\ No newline at end of file

Modified: incubator/public/trunk/site-author/guides/proposal.xml
URL: http://svn.apache.org/viewvc/incubator/public/trunk/site-author/guides/proposal.xml?rev=426873&r1=426872&r2=426873&view=diff
==============================================================================
--- incubator/public/trunk/site-author/guides/proposal.xml (original)
+++ incubator/public/trunk/site-author/guides/proposal.xml Sun Jul 30 01:22:34 2006
@@ -45,8 +45,8 @@
           </p>
         </section>
     </section>
-    <section id="formulating">
-      <title>Formulating A Proposal</title>
+    <section id="formulating"><title>Formulating A Proposal</title>
+        <section id='preparation'><title>Preparation</title>
       <p>
 Start by RTFM. The Entry To The incubator is a good place to start this
 process.
@@ -70,23 +70,53 @@
 proposal to
 the incubator. Think about goals and about the reasons for coming to apache.
        </p>
-       <p>
+    </section>   
+       <section id='presentation'><title>Presentation</title>
+            <p>
 Once the preparatory work is done, the proposal should be presented to the
 incubator.  This is done by posting the proposal
 in plain text in a email whose subject is prefixed with [PROPOSAL].
-       </p>
-       <p>
+        </p>
+            <p>
+If there is interest in the proposal, expect a lively debate to begin
+about the proposal. Approval is an open and democractic 
+<a href='entry.html#understanding'>process</a>
+so discussion is an important part of opinion forming. Every proposal
+will require development if it is to gain the maximum level of support from the
+electorate.
+        </p>
+    </section>
+        <section id='developing'><title>Developing The Proposal</title>
+            <p>
 Expect to work on improving the template on list after presenting it. The
 wiki is an excellent way to develop a proposal. Consider creating a wiki
 page containing the same content and supplying a link. Interested parties
 may wish to add themselves to the watch list for the page so that received
 email notifications when the page is changed.
        </p>
-       <p>
-When the proposal seems finish and some sort of consensus has emerged, the
-proposal can be put to the vote.
-      </p>
+            <p>
+Developing the proposal on the wiki allows easy collaboration. This has disadvantages
+as well as advantages. The wiki is just a tool to assist the easy development of the 
+final proposal (the one that will be voted upon). Not every change improves a proposal
+and there is no requirement that any change is accepted. Note that the incubator 
+asks all participants to abide by appopriate <a href='participation.html'>netiquette</a>.
+        </p>
+            <p>
+Effective management of this development is an exercise in community building. 
+The wiki is not an appropriate forum for debating changing. Discussion should be
+gently moved onto the appropriate mailing list.
+        </p>
+    </section>
+        <section id='vote'><title>The Vote</title>
+            <p>
+When the proposal seems finished and some sort of consensus has emerged, the
+proposal can be put to the vote. If the wiki is used to develop the proposal,
+please ensure that the wiki matches the final proposal then add a notice to 
+the wiki that development of the document is now complete. 
+See <a href='entry.html#'>this</a>.
+        </p>
     </section>
+</section>
     <section id="proposal-template">
       <title>Proposal Template</title>
       <p>
@@ -454,15 +484,22 @@
         </section>
         <section id='template-initial-committers'><title>Initial Committers</title>
             <blockquote>
-<p>
-        List of committers used to bootstrap the community. Note which have
-submitted CLAs.
-</p>
-<p>
+                <p>
+        List of committers used to bootstrap the community. Those which have
+submitted CLAs should be marked. 
+            </p>
+                <p>
         It is a good idea to submit CLAs at the same time as proposal and
 before acceptance. There is nothing lost by having a CLA on file at Apache
 but they do take some time to process.
-</p>
+            </p>
+                <p>
+Note <a href='#developing'>this</a> and 
+<a href='participation.html#committer'>this</a>. Consider creating a separate

+section where interested developers can express an interest (and possibly leave
+a brief introduction).
+            </p>
+    
 <pre>
 Examples:
 </pre>
@@ -503,18 +540,27 @@
                 </p>
                 </blockquote>
             </section>
-            <section id='template-mentors'><title>Mentors</title>
+            <section id='template-mentors'><title>Nominated Mentors</title>
                 <blockquote>
                     <p>
 [needs improvements?]
-            The list of mentors may well be established during development
-of the proposal. The absolute minimum is a single mentor but the current
-consensus is that (at least) three mentors will make things go more
-smoothly. Three mentors gives a quorum and allows the project more autonomy.
+A list of <a href='/incubation/Incubation_Policy.html#Mentor'>eligable</a>  
+individuals nominated as <a href='/incubation/Roles_and_Responsibilities.html#Mentor'>mentors</a>

+[<a href='/incubation/Incubation_Policy.html#Mentor'>definition</a>] for the
candidate 
+would are willing to serve.
                 </p>
-                <p>
+                    <p>
+The absolute minimum is a single mentor but the current consensus is that (at least) 
+three mentors will make things go more smoothly. Three mentors gives a quorum and allows

+the project more autonomy.
+                </p>
+                    <p>
 The number of mentors a podling can have is limited only by the
 energy and interest of those eligable to mentor.
+                </p>
+                    <p>
+It is common for mentors to <a href='partication.html#mentor'>volunteer</a> their
services
+during the development process. 
                 </p>
                 </blockquote>
             </section>

Modified: incubator/public/trunk/site-publish/guides/entry.html
URL: http://svn.apache.org/viewvc/incubator/public/trunk/site-publish/guides/entry.html?rev=426873&r1=426872&r2=426873&view=diff
==============================================================================
--- incubator/public/trunk/site-publish/guides/entry.html (original)
+++ incubator/public/trunk/site-publish/guides/entry.html Sun Jul 30 01:22:34 2006
@@ -119,6 +119,77 @@
           </p>
 </div>
 </div>
+           <h2><img src="/images/redarrow.gif" />
+   <a name="understanding">Understanding The Acceptance Process</a>
+</h2>
+<div class="section-content">
+<p>
+The acceptance process is simple in theory but complex in practice.
+        </p>
+<p>
+The theory is that candidates are accepted or rejected by a vote on a mailing lists. 
+Anyone can vote (and are <a href="participation.html#general-list">encouraged</a>
to do so)
+but only eligable votes are binding on Apache. For candidates 
+<a href="/incubation/Roles_and_Responsibilities.html#Spondor">Sponsored</a> 
+by the <code>Incubator</code> this means members of the 
+<a href="/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29">Incubator
PMC</a>.
+        </p>
+<p>
+In practice, the process is more complex for candidates who want to give themselves 
+the best chance of being accepted. 
+        </p>
+<p>
+Apache policy is set by the Board either directly or through it's special committees. 
+The incubation PMC is responsible to the board and so it is the duty of each PMC member
+to vote against a proposal that does not adhere to this policy.
+        </p>
+<p>
+<a href="/incubation/Incubation_Policy.html">Incubation Policy</a> state clearly
when a . 
+All policy is decided by PMC vote and so represents an active consensus. Though PMC members
+are free to vote in whatever way they choose, it is reasonable to expect PMC members
+to vote against a proposal that does not satisfy policy. 
+        </p>
+<p>
+However, satisfying current policy is not sufficient. Acceptance is a democractic process
+requiring positive approval by the electorate. The guides and other documentation are not
+policy. They are approved only through lazy consensus. 
+        </p>
+<p>
+See:
+        </p>
+<ul><li>[links to posts and threads]</li></ul>
+</div>
+           <h2><img src="/images/redarrow.gif" />
+   <a name="note">Notes On The Process</a>
+</h2>
+<div class="section-content">
+<h3>
+   <a name="proposal">The Proposal</a>
+</h3>
+<div class="section-content">
+<p>
+        </p>
+</div>
+<h3>
+   <a name="vote">The Vote</a>
+</h3>
+<div class="section-content">
+<p>
+When the proposal seems finished and some sort of consensus has emerged, the
+proposal can be put to the vote. 
+        </p>
+<p>
+The right time is a matter for judgement. Ask the 
+<a href="/incubator/Roles_and_Responsibilites.html#Champion">Champion</a> for
advice
+or ask on the mailing list. It is usually best to ensure that the discussions 
+and debates surrounding the proposal are complete before moving to a vote. This may 
+mean move discussions which are not about the proposal to separate threads.
+        </p>
+<p>
+The right duration for the vote is also a matter for judgement [link]. 
+        </p>
+</div>
+</div>
          </td>
     <!-- RIGHT SIDE NAVIGATION -->
     <td valign="top" nowrap="nowrap" class="navright">

Added: incubator/public/trunk/site-publish/guides/participation.html
URL: http://svn.apache.org/viewvc/incubator/public/trunk/site-publish/guides/participation.html?rev=426873&view=auto
==============================================================================
--- incubator/public/trunk/site-publish/guides/participation.html (added)
+++ incubator/public/trunk/site-publish/guides/participation.html Sun Jul 30 01:22:34 2006
@@ -0,0 +1,277 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+               "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<!--
+Copyright 1999-2006 The Apache Software Foundation
+Licensed 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
+
+http://www.apache.org/licenses/LICENSE-2.0
+
+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.
+-->
+<html>
+ <head>
+  <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+  <link rel="stylesheet" href="/style/style.css" type="text/css" />
+    <link rel="alternate" title="general@incubator.apache.org Archives" type="application/atom+xml"
href="http://mail-archives.apache.org/mod_mbox/incubator-general/?format=atom" />
+    <title>A Guide To Participation (DRAFT) - Apache Incubator</title>
+ </head>
+ <body>        
+  <table border="0" width="100%" cellspacing="0">
+   <tr><!-- SITE BANNER AND PROJECT IMAGE -->
+    <td align="left" valign="top">
+<a href="http://www.apache.org/"><img src="/images/asf_logo_wide.gif" alt="The Apache
Software Foundation" border="0"/></a>
+</td>
+<td align="right">
+<a href="http://incubator.apache.org/"><img src="../images/apache-incubator-logo.png"
alt="Apache Incubator" border="0"/></a>
+</td>
+   </tr>
+  </table>
+  <table border="0" width="100%" cellspacing="4">
+   <tr><td colspan="3"><hr noshade="noshade" size="1"/></td></tr>
+   <tr>
+    <!-- LEFT SIDE NAVIGATION -->
+    <td valign="top" nowrap="nowrap" class="navleft">
+           <div class="menuheader"><a 
+href="http://www.apache.org/foundation/glossary.html#Podling">Podlings (What's that?)</a></div>

+    <menu compact="compact">
+          <li><a href="/incubation/Incubation_Policy.html">How? (Policy)</a></li>

+          <li><a href="/incubation/Roles_and_Responsibilities.html">Who? (Roles)</a></li>

+          <li><a href="/incubation/Process_Description.html">When? (Process)</a></li>

+            </menu>
+      <div class="menuheader"><a 
+href="/guides/index.html">Podling Guides</a></div> 
+    <menu compact="compact">
+          <li><a href="/guides/committer.html">Podling Committers</a></li>

+          <li><a href="/guides/ppmc.html">Podling PMC (PPMC)</a></li>

+          <li><a href="/guides/projects.html">Podling Mentor</a></li>

+          <li><a href="/guides/releasemanagement.html">Podling Releases</a></li>

+          <li><a href="/guides/branding.html">Podling Branding</a></li>

+          <li><a href="/guides/sites.html">Podling Websites</a></li>

+            </menu>
+      <div class="menuheader"><a 
+href="/ip-clearance/index.html">IP Clearance</a></div> 
+    <menu compact="compact">
+            </menu>
+      <div class="menuheader"><a 
+href="/whoweare.html">Who We Are</a></div> 
+    <menu compact="compact">
+            </menu>
+      <div class="menuheader">Other Guides</div>
+    <menu compact="compact">
+          <li><a href="/faq.html">General FAQ</a></li> 
+          <li><a href="/guides/pmc.html">PMC</a> (<a href="/guides/chair.html">Chair</a>)</li>

+          <li><a href="/guides/lists.html">Mailing Lists</a></li>

+          <li><a href="/guides/website.html">Website</a></li> 
+            </menu>
+      <div class="menuheader"><a 
+href="http://wiki.apache.org/incubator">Wiki</a></div> 
+    <menu compact="compact">
+            </menu>
+
+     <!--#include virtual="/ads/bannerbar.html" -->    </td>
+    <!-- CONTENT -->
+    <td align="left" valign="top" class="content">
+                <h2><img src="/images/redarrow.gif" />
+   <a name="preamble">A Guide To Participation (DRAFT)</a>
+</h2>
+<div class="section-content">
+<h3>
+   <a name="status">Status - DRAFT</a>
+</h3>
+<div class="section-content">
+<p>
+This document is under <a href="#help-wanted">development</a>. This is the first

+draft intended to allow public review. 
+          </p>
+</div>
+<h3>
+   <a name="abstract">Abstract</a>
+</h3>
+<div class="section-content">
+<p>
+This document is descriptive not normative. It aims to help those who are new 
+to the Incubator learn it's ways and netiquette.
+          </p>
+</div>
+<h3>
+   General Netiquette
+</h3>
+<div class="section-content">
+<p>
+The incubator is a public meeting place with a diverse and ever changing community. 
+Creating social bonds and establishing a reputation is important. Please be polite, 
+courteous and diplomatic. 
+            </p>
+<p>
+When in doubt - ask on <code>general.AT.incubator.apache.org</code>.
+            </p>
+<p>
+The usual advice applies. If you are not familiar with the way mailing lists
+work at Apache, read <a href="http://jakarta.apache.org/site/mail.html">this</a>.
+            </p>
+</div>
+<h3>
+   <a name="help-wanted">Help Wanted!</a>
+</h3>
+<div class="section-content">
+<p>
+Help to improve the system by posting a patch for this document to the
+incubator section of JIRA or a comment to the general list at incubator.
+          </p>
+</div>
+</div>
+           <h2><img src="/images/redarrow.gif" />
+   <a name="ways">Ways To Participate</a>
+</h2>
+<div class="section-content">
+<h3>
+   <a name="developer">As A Developer</a>
+</h3>
+<div class="section-content">
+<p>
+If you are interested in development and Apache does not have a 
+<a href="http://www.apache.org/licenses/icla.txt">Contributor License Agreement</a>
(CLA) on file it will save time if 
+you <a href="http://www.apache.org/licenses/#clas">submit</a> one now. 
+            </p>
+</div>
+<h3>
+   <a name="committer">As A Committer</a>
+</h3>
+<div class="section-content">
+<p>
+Once a podling has been bootstrapped, <a href="#developer">developers</a> are
nominated
+and elected in the usual way.
+            </p>
+<p>
+When a proposal is just a candidate, there are two possible approaches.
+            </p>
+<p>
+The proposal typically 
+<a href="proposal.html#template-initial-committers">contains</a> a list of initial
committers.
+When a podling is bootstrapped, this list is used by the mentors to set up initial accounts.
+So, one way to become a committer for a podling is to be listed on the proposal as an initial
+committer.
+[link to roles and responsibilities]
+            </p>
+<p>
+Piling onto a proposal by adding your own name as an initial committer is impolite.
+Read 
+<a href="http://mail-archives.apache.org/mod_mbox/incubator-general/200607.mbox/%3cC73C6D24-3216-4EB4-8846-1218B38CC594@gbiv.com%3e">this
thread</a>.
+The right way to express interest is by a post to the list.
+            </p>
+<p>
+A podling needs to learn how to recruit new committers from its developers. So,
+another way is to show up on the list and start helping with the development.
+This path will help the podling more than adding your name to the list of initial committers.
+            </p>
+</div>
+<h3>
+   <a name="mentors">As A Mentor</a>
+</h3>
+<div class="section-content">
+<p>
+Anyone with knowledge of open source or Apache can participate as a informal mentor
+for a podling. Development is open and anyone with an interest is encouraged to 
+subscribe to the podling lists. 
+            </p>
+<p>
+Eligibility to act as a formal 
+<a href="/incubation/Roles_And_Responsibilities.html#Mentor">Mentor</a> is 
+<a href="/incubation/Incubation_Policy">limited</a>. The best way for an eligable

+individuals to become a Mentors for a Podling is to post a note introducing themselves 
+and volunteering their services to <code>general.AT.incubator.apache.org</code>

+during the development of the <a href="proposal.html">proposal</a>.
+            </p>
+</div>
+<h3>
+   <a name="general-list">On The General Mailing List</a>
+</h3>
+<div class="section-content">
+<p>
+The <code>general.AT.incubator.apache.org</code> is an public list with open
subscription.
+All are encuraged to subscribe, read and post their opinions in the usual way. 
+[link to foundation documentation on list netiquette] 
+            </p>
+<p>
+Anyone can influence the decision making process by their comments and may vote on VOTE
+threads. However (as is usual) only the votes of those on the incubator PMC are binding on
Apache.
+            </p>
+</div>
+<h3>
+   <a name="pmcer">On The Incubator PMC</a>
+</h3>
+<div class="section-content">
+<p>
+Apache Members are encouraged to join the Incubator PMC.
+            </p>
+<p>
+Those who aren't members may be elected in the usual Apache fashion after a history
+of contribution.
+            </p>
+</div>
+</div>
+         </td>
+    <!-- RIGHT SIDE NAVIGATION -->
+    <td valign="top" nowrap="nowrap" class="navright">
+           <div class="menuheader"><a 
+href="/projects/index.html">Projects</a></div>
+    <menu compact="compact">
+          <li><a href="/projects/abdera.html">Abdera</a></li> 
+          <li><a href="/projects/activemq.html">ActiveMQ</a></li>

+          <li><a href="/projects/adffaces.html">ADF Faces</a></li>

+          <li><a href="/projects/agila.html">Agila</a></li> 
+          <li><a href="/projects/altrmi.html">AltRMI</a></li> 
+          <li><a href="/projects/cayenne.html">Cayenne</a></li> 
+          <li><a href="/projects/felix.html">Felix</a></li> 
+          <li><a href="/projects/ftpserver.html">FtpServer</a></li>

+          <li><a href="/projects/graffito.html">Graffito</a></li>

+          <li><a href="/projects/harmony.html">Harmony</a></li> 
+          <li><a href="/projects/juice.html">JuiCE</a></li> 
+          <li><a href="/projects/log4net.html">log4net</a></li> 
+          <li><a href="/projects/log4php.html">log4php</a></li> 
+          <li><a href="/projects/lokahi.html">Lokahi</a></li> 
+          <li><a href="/projects/lucene4c.html">Lucene4c</a></li>

+          <li><a href="/projects/lucene.net.html">Lucene.Net</a></li>

+          <li><a href="/projects/mod_ftp.html">mod_ftp</a></li> 
+          <li><a href="/projects/ode.html">Ode</a></li> 
+          <li><a href="/projects/ofbiz.html">OFBiz</a></li> 
+          <li><a href="/projects/openejb.html">OpenEJB</a></li> 
+          <li><a href="/projects/openjpa.html">OpenJPA</a></li> 
+          <li><a href="/projects/roller.html">Roller</a></li> 
+          <li><a href="/projects/servicemix.html">ServiceMix</a></li>

+          <li><a href="/projects/solr.html">Solr</a></li> 
+          <li><a href="/projects/stdcxx.html">stdcxx</a></li> 
+          <li><a href="/projects/synapse.html">Synapse</a></li> 
+          <li><a href="/projects/tsik.html">TSIK</a></li> 
+          <li><a href="/projects/tuscany.html">Tuscany</a></li> 
+          <li><a href="/projects/wadi.html">wadi</a></li> 
+          <li><a href="/projects/woden.html">Woden</a></li> 
+          <li><a href="/projects/wsrp4j.html">WSRP4J</a></li> 
+          <li><a href="/projects/xap.html">XAP</a></li> 
+          <li><a href="/projects/yoko.html">Yoko</a></li> 
+        </menu>
+
+<form action="http://www.google.com/search" method="get">
+    <input value="incubator.apache.org" name="sitesearch" type="hidden"/>
+    <input size="8" name="q" id="query" type="text" value="search..."
+        onclick="if(this.value == 'search...') {this.value = ''}"/>
+    <input name="Search" value="Go" type="submit"/>
+</form>
+    </td>     
+   </tr>
+   <!-- FOOTER -->
+   <tr><td colspan="3"><hr noshade="noshade" size="1"/></td></tr>
+   <tr><td colspan="3" class="footer">
+         Copyright &#169; 1999-2006, The Apache Software Foundation<br />
+Licensed under the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License,
Version 2.0</a>.
+       </td>
+   </tr>
+  </table>
+ </body>
+</html>

Modified: incubator/public/trunk/site-publish/guides/proposal.html
URL: http://svn.apache.org/viewvc/incubator/public/trunk/site-publish/guides/proposal.html?rev=426873&r1=426872&r2=426873&view=diff
==============================================================================
--- incubator/public/trunk/site-publish/guides/proposal.html (original)
+++ incubator/public/trunk/site-publish/guides/proposal.html Sun Jul 30 01:22:34 2006
@@ -131,6 +131,10 @@
    <a name="formulating">Formulating A Proposal</a>
 </h2>
 <div class="section-content">
+<h3>
+   <a name="preparation">Preparation</a>
+</h3>
+<div class="section-content">
 <p>
 Start by RTFM. The Entry To The incubator is a good place to start this
 process.
@@ -154,11 +158,29 @@
 proposal to
 the incubator. Think about goals and about the reasons for coming to apache.
        </p>
+</div>
+<h3>
+   <a name="presentation">Presentation</a>
+</h3>
+<div class="section-content">
 <p>
 Once the preparatory work is done, the proposal should be presented to the
 incubator.  This is done by posting the proposal
 in plain text in a email whose subject is prefixed with [PROPOSAL].
-       </p>
+        </p>
+<p>
+If there is interest in the proposal, expect a lively debate to begin
+about the proposal. Approval is an open and democractic 
+<a href="entry.html#understanding">process</a>
+so discussion is an important part of opinion forming. Every proposal
+will require development if it is to gain the maximum level of support from the
+electorate.
+        </p>
+</div>
+<h3>
+   <a name="developing">Developing The Proposal</a>
+</h3>
+<div class="section-content">
 <p>
 Expect to work on improving the template on list after presenting it. The
 wiki is an excellent way to develop a proposal. Consider creating a wiki
@@ -167,9 +189,30 @@
 email notifications when the page is changed.
        </p>
 <p>
-When the proposal seems finish and some sort of consensus has emerged, the
-proposal can be put to the vote.
-      </p>
+Developing the proposal on the wiki allows easy collaboration. This has disadvantages
+as well as advantages. The wiki is just a tool to assist the easy development of the 
+final proposal (the one that will be voted upon). Not every change improves a proposal
+and there is no requirement that any change is accepted. Note that the incubator 
+asks all participants to abide by appopriate <a href="participation.html">netiquette</a>.
+        </p>
+<p>
+Effective management of this development is an exercise in community building. 
+The wiki is not an appropriate forum for debating changing. Discussion should be
+gently moved onto the appropriate mailing list.
+        </p>
+</div>
+<h3>
+   <a name="vote">The Vote</a>
+</h3>
+<div class="section-content">
+<p>
+When the proposal seems finished and some sort of consensus has emerged, the
+proposal can be put to the vote. If the wiki is used to develop the proposal,
+please ensure that the wiki matches the final proposal then add a notice to 
+the wiki that development of the document is now complete. 
+See <a href="entry.html#">this</a>.
+        </p>
+</div>
 </div>
            <h2><img src="/images/redarrow.gif" />
    <a name="proposal-template">Proposal Template</a>
@@ -626,15 +669,22 @@
 </h4>
 <div class="section-content">
 <blockquote>
-<p>
-        List of committers used to bootstrap the community. Note which have
-submitted CLAs.
-</p>
-<p>
+                <p>
+        List of committers used to bootstrap the community. Those which have
+submitted CLAs should be marked. 
+            </p>
+                <p>
         It is a good idea to submit CLAs at the same time as proposal and
 before acceptance. There is nothing lost by having a CLA on file at Apache
 but they do take some time to process.
-</p>
+            </p>
+                <p>
+Note <a href="#developing">this</a> and 
+<a href="participation.html#committer">this</a>. Consider creating a separate

+section where interested developers can express an interest (and possibly leave
+a brief introduction).
+            </p>
+    
 <pre>
 Examples:
 </pre>
@@ -685,20 +735,29 @@
                 </blockquote>
 </div>
 <h5> 
-   <a name="template-mentors">Mentors</a> 
+   <a name="template-mentors">Nominated Mentors</a> 
 </h5> 
 <div class="section-content">
 <blockquote>
                     <p>
 [needs improvements?]
-            The list of mentors may well be established during development
-of the proposal. The absolute minimum is a single mentor but the current
-consensus is that (at least) three mentors will make things go more
-smoothly. Three mentors gives a quorum and allows the project more autonomy.
+A list of <a href="/incubation/Incubation_Policy.html#Mentor">eligable</a>  
+individuals nominated as <a href="/incubation/Roles_and_Responsibilities.html#Mentor">mentors</a>

+[<a href="/incubation/Incubation_Policy.html#Mentor">definition</a>] for the
candidate 
+would are willing to serve.
                 </p>
-                <p>
+                    <p>
+The absolute minimum is a single mentor but the current consensus is that (at least) 
+three mentors will make things go more smoothly. Three mentors gives a quorum and allows

+the project more autonomy.
+                </p>
+                    <p>
 The number of mentors a podling can have is limited only by the
 energy and interest of those eligable to mentor.
+                </p>
+                    <p>
+It is common for mentors to <a href="partication.html#mentor">volunteer</a> their
services
+during the development process. 
                 </p>
                 </blockquote>
 </div>



---------------------------------------------------------------------
To unsubscribe, e-mail: cvs-unsubscribe@incubator.apache.org
For additional commands, e-mail: cvs-help@incubator.apache.org


Mime
View raw message