blautenb    2003/10/05 04:52:12

  Modified:    build/site/drafts Incubation_Policy.pdf
                        Incubation_Policy.html
  Log:
  Fixed reference to RFC2119 - As per comment from Noel Bergman + removed 
trailing ==
  
  Revision  Changes    Path
  1.2       +302 -283  incubator-site/build/site/drafts/Incubation_Policy.pdf
  
        <<Binary file>>
  
  
  1.2       +52 -52    incubator-site/build/site/drafts/Incubation_Policy.html
  
  Index: Incubation_Policy.html
  ===================================================================
  RCS file: /home/cvs/incubator-site/build/site/drafts/Incubation_Policy.html,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- Incubation_Policy.html    4 Oct 2003 12:58:23 -0000       1.1
  +++ Incubation_Policy.html    5 Oct 2003 11:52:12 -0000       1.2
  @@ -226,13 +226,13 @@
   <a href="#Relationship+to+Other+Documents">Relationship to Other 
Documents</a>
   </li>
   <li>
  -<a href="#Changing+this+Document+%3D%3D%3D">Changing this Document ===</a>
  +<a href="#Changing+this+Document">Changing this Document</a>
   </li>
   <li>
   <a href="#Objectives+of+the+Process">Objectives of the Process</a>
   </li>
   <li>
  -<a href="#Overview+of+the+Process+%3D%3D">Overview of the Process ==</a>
  +<a href="#Overview+of+the+Process">Overview of the Process</a>
   </li>
   <li>
   <a href="#Entry+to+Incubation">Entry to Incubation</a>
  @@ -338,32 +338,32 @@
   <div style="margin-left: 0 ; border: 2px">
   <p>This document is the normative reference for the policies and procedures 
put in place by the Incubator PMC for the Incubation process, which is used by 
the Incubator PMC to discharge their duties as described above.</p>
   <p>It contains the minimum requirements that all new products and projects 
must meet before they will be fully accepted into the Apache Software 
Foundation.</p>
  -<p>The document makes use of the terms MUST, MUST NOT, REQUIRED, SHALL, 
SHALL NOT, SHOULD, SHOULD NOT, RECOMMENDED, MAY and OPTIONAL.  Where 
capitalised, these terms are to be used as per the definitions found in RFC 
2119 (Reference).</p>
  +<p>The document makes use of the terms MUST, MUST NOT, REQUIRED, SHALL, 
SHALL NOT, SHOULD, SHOULD NOT, RECOMMENDED, MAY and OPTIONAL.  Where 
capitalised, these terms are to be used as per the definitions found in <a 
href="http://www.ietf.org/rfc/rfc2119.txt";>RFC 2119</a>.</p>
   </div>
  -<a name="N10023"></a><a name="Status"></a>
  +<a name="N10027"></a><a name="Status"></a>
   <h3>Status</h3>
   <div style="margin-left: 0 ; border: 2px">
   <p>
   <strong>This document is currently a working draft, with no formal 
status.</strong>
   </p>
   </div>
  -<a name="N1002A"></a><a name="Scope"></a>
  +<a name="N1002E"></a><a name="Scope"></a>
   <h3>Scope</h3>
   <div style="margin-left: 0 ; border: 2px">
   <p>This document contains the minimum requirements and processes that must 
be met by products and projects wishing to become part of the Apache Software 
Foundation.</p>
   <p>This document does not apply outside the process of Incubation.  Policies 
and processes that need to be met by products under incubation are not mandated 
(by this document) for other projects and sub-projects within the ASF.</p>
   </div>
  -<a name="N10032"></a><a name="Relationship+to+Other+Documents"></a>
  +<a name="N10036"></a><a name="Relationship+to+Other+Documents"></a>
   <h3>Relationship to Other Documents</h3>
   <div style="margin-left: 0 ; border: 2px">
   <p>This document is the normative set of requirements for Incubation.  Where 
other documents are in conflict, this document should be taken as correct.</p>
   </div>
  -<a name="N10038"></a><a name="Changing+this+Document+%3D%3D%3D"></a>
  -<h3>Changing this Document ===</h3>
  +<a name="N1003C"></a><a name="Changing+this+Document"></a>
  +<h3>Changing this Document</h3>
   <div style="margin-left: 0 ; border: 2px">
   <p>The contents of this document are formally approved by the Incubator PMC. 
 All changes must be authorised by the Incubator PMC.</p>
   </div>
  -<a name="N1003E"></a><a name="Objectives+of+the+Process"></a>
  +<a name="N10042"></a><a name="Objectives+of+the+Process"></a>
   <h3>Objectives of the Process</h3>
   <div style="margin-left: 0 ; border: 2px">
   <p>To provide a clear path for potential projects and sub-projects within 
the ASF to move from proposal stage through to fully membership in such as way 
as to ensure :</p>
  @@ -373,31 +373,31 @@
   <li>only those products that meet the Apache's requirements are fully 
accepted into the ASF.</li>
   </ul>
   </div>
  -<a name="N1004B"></a><a name="Overview+of+the+Process+%3D%3D"></a>
  -<h3>Overview of the Process ==</h3>
  +<a name="N1004F"></a><a name="Overview+of+the+Process"></a>
  +<h3>Overview of the Process</h3>
   <div style="margin-left: 0 ; border: 2px">
   <p>The incubation process covers the establishment of a candidate, 
acceptance (or rejection) of a candidate leading to the potential establishment 
of a Podling and associated incubation process, which ultimately leads to the 
establishment or a new Apache Top-Level-Project (TLP) or sub-project within an 
existing Apache Project.</p>
  -<pre class="code">
  -
  -
  - establishment   |------------|  acceptance   |----------|   engagement   
|----------|
  ----------------&gt; | Candidate  |-------------&gt; | Podling  
|---------------&gt;| Project  |
  -                 |------------|               |----------|--|             
|----------|
  -                      |                         |  ^        |
  -                      |                         |  |        | continuation
  -                      V                         |  |--------|
  -                   rejection                    |     
  -                                                V
  -                                           termination
  -  
  +<pre class="code">&#13;
  +&#13;
  +&#13;
  + establishment   |------------|  acceptance   |----------|   engagement   
|----------|&#13;
  +---------------&gt; | Candidate  |-------------&gt; | Podling  
|---------------&gt;| Project  |&#13;
  +                 |------------|               |----------|--|             
|----------|&#13;
  +                      |                         |  ^        |&#13;
  +                      |                         |  |        | 
continuation&#13;
  +                      V                         |  |--------|&#13;
  +                   rejection                    |     &#13;
  +                                                V&#13;
  +                                           termination&#13;
  +  &#13;
   </pre>
   </div>
  -<a name="N10053"></a><a name="Entry+to+Incubation"></a>
  +<a name="N10057"></a><a name="Entry+to+Incubation"></a>
   <h3>Entry to Incubation</h3>
   <div style="margin-left: 0 ; border: 2px">
   <p>Entry to Incubation requires a number of hurdles be passed.</p>
   </div>
  -<a name="N10059"></a><a name="Proposal"></a>
  +<a name="N1005D"></a><a name="Proposal"></a>
   <h3>Proposal</h3>
   <div style="margin-left: 0 ; border: 2px">
   <p>In order to enter the Incubator, a Candidate MUST </p>
  @@ -416,7 +416,7 @@
   <strong>Need to provide a short list</strong>
   </p>
   </div>
  -<a name="N10072"></a><a 
name="Acceptance+of+Proposal+by+Sponsoring+Entity"></a>
  +<a name="N10076"></a><a 
name="Acceptance+of+Proposal+by+Sponsoring+Entity"></a>
   <h3>Acceptance of Proposal by Sponsoring Entity</h3>
   <div style="margin-left: 0 ; border: 2px">
   <p>The decision to accept a project MUST be taken on a vote by the 
Sponsoring Entity, in accordance with that Entity's charter.  </p>
  @@ -429,18 +429,18 @@
   <p>The Incubator PMC MAY immediately accept the Candidate, or may (at the 
discretion of the Incubator PMC) require a successful VOTE by the Incubator 
PMC.</p>
   <p>The nominated Mentor MAY be immediately accepted by the Incubator PMC.  
However the Incubator PMC MAY also suggest a replacement Mentor.  The Incubator 
PMC has the final choice of Mentor.</p>
   </div>
  -<a name="N10085"></a><a name="Creation+of+Podling"></a>
  +<a name="N10089"></a><a name="Creation+of+Podling"></a>
   <h3>Creation of Podling</h3>
   <div style="margin-left: 0 ; border: 2px">
   <p>Upon acceptance by the Incubator PMC, the Candidate becomes a Podling 
under the care of the Incubator PMC.  </p>
   <p>Upon acceptance by the Incubator PMC, the Podling's Mentor becomes a 
member of the Incubator PMC (should they not already be one).</p>
   </div>
  -<a name="N1008D"></a><a name="Incubation+Activities"></a>
  +<a name="N10091"></a><a name="Incubation+Activities"></a>
   <h3>Incubation Activities</h3>
   <div style="margin-left: 0 ; border: 2px">
   <p>The following sections detail the minimum activities that must be 
undertaken by the various parties during an Incuabation process.</p>
   </div>
  -<a name="N10093"></a><a name="Setting+Up+a+New+Podling"></a>
  +<a name="N10097"></a><a name="Setting+Up+a+New+Podling"></a>
   <h3>Setting Up a New Podling</h3>
   <div style="margin-left: 0 ; border: 2px">
   <p>Once the Podling and Mentor have been accepted by the Incubator PMC, the 
following activities SHOULD take place :</p>
  @@ -452,7 +452,7 @@
   <li>Incubator PMC mandating a helper Mentor</li>
   </ul>
   </div>
  -<a name="N100A1"></a><a name="Ongoing+Activities"></a>
  +<a name="N100A5"></a><a name="Ongoing+Activities"></a>
   <h3>Ongoing Activities</h3>
   <div style="margin-left: 0 ; border: 2px">
   <p>The progress of a Podling SHALL be tracked in a STATUS file.  The STATUS 
file SHALL be stored in the <em>incubator</em>module in the ASF CVS 
repository.</p>
  @@ -468,7 +468,7 @@
   </ul>
   <p>The Mentor MUST ensure that the STATUS file is up to date at all 
times.</p>
   </div>
  -<a name="N100BA"></a><a name="Review+of+Activity"></a>
  +<a name="N100BE"></a><a name="Review+of+Activity"></a>
   <h3>Review of Activity</h3>
   <div style="margin-left: 0 ; border: 2px">
   <p>Each Podling in Incubation SHALL undergo a regular review of progress by 
the Incubator PMC.  Such reviews SHALL occur at least quaterly.  The Incubator 
PMC MAY, at their discretion, choose to review individual Podlings with greater 
frequency.  The Incubator PMC SHALL inform Podlings of review dates at least 4 
weeks in advance.</p>
  @@ -481,7 +481,7 @@
   </ul>
   <p>Termination and Escalation are discussed in more detail in section 
"Exitting the Incubator".</p>
   </div>
  -<a name="N100CD"></a><a name="Disputing+an+Assessment"></a>
  +<a name="N100D1"></a><a name="Disputing+an+Assessment"></a>
   <h3>Disputing an Assessment</h3>
   <div style="margin-left: 0 ; border: 2px">
   <p>If the Podling or Mentor disagree with an assessment, they MAY request 
the Incubator PMC review the report.  Such a request MUST include a details of 
what the Podling and/or Mentor is disputing, and their reasons for doing so.</p>
  @@ -501,18 +501,18 @@
   </ul>
   <p>The decision of the Board of the Apache Software Foundation is final.</p>
   </div>
  -<a name="N100EB"></a><a name="Continuation"></a>
  +<a name="N100EF"></a><a name="Continuation"></a>
   <h3>Continuation</h3>
   <div style="margin-left: 0 ; border: 2px">
   <p>A recommendation by the Incubator PMC for continuation of incubation 
SHALL include development recommendations. The Incubator PMC SHALL ensure that 
the recommended actions are tangible and quantifiable.  </p>
   <p>The Mentor SHALL review the contents of the continuation recommendation 
and ensure that the development recommendations are carried out over the 
following review period.</p>
   </div>
  -<a name="N100F3"></a><a name="Podling+Constraints"></a>
  +<a name="N100F7"></a><a name="Podling+Constraints"></a>
   <h3>Podling Constraints</h3>
   <div style="margin-left: 0 ; border: 2px">
   <p>While in Incubation, Podlings are constrained in the actions they can 
undertake.</p>
   </div>
  -<a name="N100F9"></a><a name="Branding"></a>
  +<a name="N100FD"></a><a name="Branding"></a>
   <h3>Branding</h3>
   <div style="margin-left: 0 ; border: 2px">
   <p>Podlings are, by definition, not yet fully accepted as part of the Apache 
Software Foundation.  Podling web sites MUST include a clear disclaimer on 
their website and in all documentation stating that they are in incubation.</p>
  @@ -522,7 +522,7 @@
   </p>
   <p>Podlings wishing to use a different disclaimer message MUST have the 
disclaimer approved by the Incubator PMC prior to use.</p>
   </div>
  -<a name="N10106"></a><a name="Releases"></a>
  +<a name="N1010A"></a><a name="Releases"></a>
   <h3>Releases</h3>
   <div style="margin-left: 0 ; border: 2px">
   <p>As podlings are not yet fully accepted as part of the Apache Software 
Foundation, any software releases (including code held in publically available 
CVS) made by Podlings will not be endorsed by the ASF.</p>
  @@ -535,19 +535,19 @@
   <li>the release archive MUST contain an Incubation disclaimer (as described 
in the previous section), clearly visible in the main documentation or README 
file.</li>
   </ul>
   </div>
  -<a name="N10119"></a><a name="Use+of+Apache+Resources"></a>
  +<a name="N1011D"></a><a name="Use+of+Apache+Resources"></a>
   <h3>Use of Apache Resources</h3>
   <div style="margin-left: 0 ; border: 2px">
   <p>
   <strong>Is this required?</strong>
   </p>
   </div>
  -<a name="N10120"></a><a name="Exitting+the+Incubator"></a>
  +<a name="N10124"></a><a name="Exitting+the+Incubator"></a>
   <h3>Exitting the Incubator</h3>
   <div style="margin-left: 0 ; border: 2px">
   <p>This section describes the requirements and process for exitting the 
Incubator.</p>
   </div>
  -<a name="N10126"></a><a name="Minimum+Exit+Requirements"></a>
  +<a name="N1012A"></a><a name="Minimum+Exit+Requirements"></a>
   <h3>Minimum Exit Requirements</h3>
   <div style="margin-left: 0 ; border: 2px">
   <p>Prior to escalation to the ASF, a Podling needs to show that :</p>
  @@ -611,27 +611,27 @@
   <li>Developers tied into ASF PGP web of trust</li>
   </ul>
   </div>
  -<a name="N10184"></a><a name="Termination+of+a+Podling"></a>
  +<a name="N10188"></a><a name="Termination+of+a+Podling"></a>
   <h3>Termination of a Podling</h3>
   <div style="margin-left: 0 ; border: 2px">
   <p>If you receive a recommendation for termination then you have a problem.  
Chances are that there are either legal or structural problems with your 
project that in the opinion of the Incubator PMC are not resolvable within a 
reasonable time frame.  A termination decision is basically time to close down 
the project. However, you do have the right to appeal a termination decision 
with the Board of Directors and/or your Sponsoring Entity.  You should be aware 
that several Members of the Board are also Members of the Incubator PMC and as 
such, an appeal is unlikely to be successful. </p>
   </div>
  -<a name="N1018A"></a><a name="Migration+as+a+Top+Level+Project"></a>
  +<a name="N1018E"></a><a name="Migration+as+a+Top+Level+Project"></a>
   <h3>Migration as a Top Level Project</h3>
   <div style="margin-left: 0 ; border: 2px">
   <p>In cases where a Podling has successfully completed Incubation, and is 
exitting the Incubator to become a Top Level Project, the Incubator PMC SHALL 
provide a recommendation to the board that the Podling is ready to escalate.  
The recommendation SHALL include a draft resolution for the board to vote 
on.</p>
   </div>
  -<a name="N10190"></a><a name="Migration+as+a+sub-project"></a>
  +<a name="N10194"></a><a name="Migration+as+a+sub-project"></a>
   <h3>Migration as a sub-project</h3>
   <div style="margin-left: 0 ; border: 2px">
   <p>In cases where a Podling has successfully completed Incubation, and is 
exitting the Incubator to become a sub-project within an already existing Top 
Level Project, the Incubator PMC SHALL provide a recommendation to the TLP that 
the Podling is ready to escalate.</p>
   </div>
  -<a name="N10196"></a><a name="Roles+in+the+Incubation+Process"></a>
  +<a name="N1019A"></a><a name="Roles+in+the+Incubation+Process"></a>
   <h3>Roles in the Incubation Process</h3>
   <div style="margin-left: 0 ; border: 2px">
   <p>This section describes the roles involved in the Incubation process.</p>
   </div>
  -<a name="N1019C"></a><a 
name="Incubator+Project+Management+Committee+%28PMC%29"></a>
  +<a name="N101A0"></a><a 
name="Incubator+Project+Management+Committee+%28PMC%29"></a>
   <h3>Incubator Project Management Committee (PMC)</h3>
   <div style="margin-left: 0 ; border: 2px">
   <p>(From the resolution that created the Incubator Project - see 
http://incubator.apache.org/resolution.html)</p>
  @@ -647,22 +647,22 @@
   <li>be terminated.</li>
   </ul>
   </div>
  -<a name="N101B5"></a><a name="Chair+of+the+Incubator+PMC"></a>
  +<a name="N101B9"></a><a name="Chair+of+the+Incubator+PMC"></a>
   <h3>Chair of the Incubator PMC</h3>
   <div style="margin-left: 0 ; border: 2px">
   <p>The person appointed by the Board of Directors to have primary 
responsibility for oversight of the Incubator Project, its policies, and policy 
implementation.</p>
   </div>
  -<a name="N101BB"></a><a name="Candidate"></a>
  +<a name="N101BF"></a><a name="Candidate"></a>
   <h3>Candidate</h3>
   <div style="margin-left: 0 ; border: 2px">
   <p>A project that is proposed for incubation.</p>
   </div>
  -<a name="N101C1"></a><a name="Sponsor"></a>
  +<a name="N101C5"></a><a name="Sponsor"></a>
   <h3>Sponsor</h3>
   <div style="margin-left: 0 ; border: 2px">
   <p>A Member of the Apache Software Foundation who supports a Candidate's 
application for Incubation and who supports and assists the Podling through the 
Incubation process.</p>
   </div>
  -<a name="N101C7"></a><a name="Sponsoring+Entity"></a>
  +<a name="N101CB"></a><a name="Sponsoring+Entity"></a>
   <h3>Sponsoring Entity</h3>
   <div style="margin-left: 0 ; border: 2px">
   <p>The Sponsoring Entity is the entity within the ASF that makes the 
determination that a candidate would make a worthy addition to the ASF, and 
agrees to take on the candidate in question (or in the case of the Incubator 
PMC, assist it in finding a home) should it complete the incubation process.</p>
  @@ -673,17 +673,17 @@
   <li>The Incubator PMC.  In this case, the Incubator PMC agrees that the 
project in question will make a good addition to the ASF, but there is no clear 
"owner" of the candidate should it successfully complete incubation.  An 
incubation exit requirement for such candidates will be the identification (and 
successfuly lobbying) of an "owner" entity - either the board (and the 
candidate will be a TLP) or another project.</li>
   </ul>
   </div>
  -<a name="N101D6"></a><a name="Mentor"></a>
  +<a name="N101DA"></a><a name="Mentor"></a>
   <h3>Mentor</h3>
   <div style="margin-left: 0 ; border: 2px">
   <p>A Mentor is a role undertaken by a permanent member of the Apache 
Software Foundation and is chosen by the Sponsoring Entity to actively lead in 
the discharge of their duties (listed above).  Upon acceptance by the Incubator 
PMC, the Mentor automatically becomes a member of the Incubator PMC.  A Mentor 
has specific responsibilities towards the Incubator PMC, the Sponsoring Entity 
and towards the members of the assigned Podling.</p>
   </div>
  -<a name="N101DC"></a><a name="Committers"></a>
  +<a name="N101E0"></a><a name="Committers"></a>
   <h3>Committers</h3>
   <div style="margin-left: 0 ; border: 2px">
   <p>The candidate shall declare an initial set of committers.  On acceptance 
of a candidate project, the assigned Mentor shall be given access to the 
Podling's cvs repository for the duration of the incubation process.  This is 
to allow the Mentor to perform their incubation duties, and is for 
administrative purposes only.  To be given full committer privileges, such as 
the right to add new code to the repository, the Mentor must earn them as would 
any other potential new committer.  In some cases, the Mentor may be part of 
the initial set of declared committers, but this is not a requirement of the 
Incubation process.</p>
   </div>
  -<a name="N101E2"></a><a name="Appendix+A+-+Glossary"></a>
  +<a name="N101E6"></a><a name="Appendix+A+-+Glossary"></a>
   <h3>Appendix A - Glossary</h3>
   <div style="margin-left: 0 ; border: 2px">
   <p>
  
  
  

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to