incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From johndam...@apache.org
Subject svn commit: r1776061 - /incubator/public/branches/policy-rewrite-cleanup-122016/content/incubation/Incubation_Policy.xml
Date Mon, 26 Dec 2016 15:13:24 GMT
Author: johndament
Date: Mon Dec 26 15:13:24 2016
New Revision: 1776061

URL: http://svn.apache.org/viewvc?rev=1776061&view=rev
Log:
Updating incubator policy removing a lot of redundant information.

Modified:
    incubator/public/branches/policy-rewrite-cleanup-122016/content/incubation/Incubation_Policy.xml

Modified: incubator/public/branches/policy-rewrite-cleanup-122016/content/incubation/Incubation_Policy.xml
URL: http://svn.apache.org/viewvc/incubator/public/branches/policy-rewrite-cleanup-122016/content/incubation/Incubation_Policy.xml?rev=1776061&r1=1776060&r2=1776061&view=diff
==============================================================================
--- incubator/public/branches/policy-rewrite-cleanup-122016/content/incubation/Incubation_Policy.xml [utf-8] (original)
+++ incubator/public/branches/policy-rewrite-cleanup-122016/content/incubation/Incubation_Policy.xml [utf-8] Mon Dec 26 15:13:24 2016
@@ -1,840 +1,614 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!-- 
-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. 
---> 
+<!--
+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.
+-->
 
 <!DOCTYPE document
-[
-<!ENTITY root-path   '..'> <!-- The path to the incubator root -->
-]>
+        [
+                <!ENTITY root-path   '..'> <!-- The path to the incubator root -->
+                ]>
 
 <document>
-  <properties><!--
+    <properties><!--
 
     <meta content="HTML Tidy, see www.w3.org" name="generator"/>-->
-<!--
+        <!--
 
-    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type"/>-->
+            <meta content="text/html; charset=UTF-8" http-equiv="Content-Type"/>-->
 
-    <title>Incubation Policy
-</title>
-    <atom url="http://mail-archives.apache.org/mod_mbox/incubator-general/?format=atom">general@incubator.apache.org Archives</atom>
-    <link href="http://purl.org/DC/elements/1.0/" rel="schema.DC"/>
-  </properties>
-  <body>
-<section id="TOC">
- <title>Incubation Policy: Table of Contents</title>
-
-<ul>
-<li><a href="#Incubation+Policy">Incubation Policy</a>
-  <ul>
-    <li><a href="#About+this+Document">About this Document</a></li>
-    <li><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">Overview of the Process</a></li>
-  </ul>
-</li>
-<li><a href="#Entry+to+Incubation">Entry to Incubation</a>
-  <ul>
-    <li><a href="#Proposal">Proposal</a></li>
-    <li><a href="#Approval+of+Proposal+by+Sponsor">Approval of Proposal 
-        by Sponsor</a></li> 
-    <li><a href="#Acceptance+By+Incubator">Acceptance By Incubator</a></li> 
-    <li><a href="#Creation+of+Podling">Creation of Podling</a></li>
-  </ul>
-</li>
-<li><a href="#Incubation+Activities">Incubation Activities</a>
-  <ul>
-    <li><a href="#Setting+Up+a+New+Podling">Setting Up a New Podling</a></li>
-    <li><a href="#Ongoing+Activities">Ongoing Activities</a></li>
-    <li><a href="#Review+of+Activity">Review of Activity</a></li>
-    <li><a href="#Disputing+an+Assessment">Disputing an Assessment</a></li>
-    <li><a href="#Continuation">Continuation</a></li>
-  </ul>
-</li>
-<li><a href="#Podling+Constraints">Podling Constraints</a>
-  <ul>
-    <li><a href="../guides/branding.html">Branding</a></li>
-    <li><a href="#Releases">Releases</a></li>
-    <li><a href="#Use+of+Apache+Resources">Use of Apache Resources</a></li>
-  </ul>
-</li>
-<li><a href="#Graduating+from+the+Incubator">Graduating from the Incubator</a>
-  <ul>
-    <li><a href="#Minimum+Graduation+Requirements">Minimum Graduation Requirements</a></li>
-    <li><a href="#Termination+of+a+Podling">Termination of a Podling</a></li>
-    <li><a href="#Graduation+as+a+Top+Level+Project">Graduation as a Top Level Project</a></li>
-    <li><a href="#Graduation+as+a+sub-project">Graduation as a sub-project</a></li>
-    <li><a href="../guides/graduation.html">Post-Graduation Check List</a></li>
-  </ul>
-</li>
-<li><a href="#Roles+in+the+Incubation+Process">Roles Defined</a>
-  <ul>
-    <li><a href="#Incubator+Project+Management+Committee+%28PMC%29">Incubator
-       Project Management Committee (PMC)</a></li>
-    <li><a href="#Chair+of+the+Incubator+PMC">Chair of the Incubator PMC</a></li>
-    <li><a href="#Candidate">Candidate</a></li>
-    <li><a href="#Champion">Champion</a></li>
-    <li><a href="#Sponsor">Sponsor</a></li>
-    <li><a href="#Mentor">Mentor</a></li>
-    <li><a href="#Committers">Committers</a></li>
-  </ul>
-</li>
-</ul>
-
-</section>
-
-    <section id="Incubation+Policy">
-      <title>Incubation Policy
-</title>
-      <p>In October 2002 the Board of Directors of the Apache Software
-Foundation passed a resolution creating the Apache Incubator PMC
-(referred to as the "Incubator PMC" in this document) charged with
-"accepting new products into the Foundation, providing guidance and
-support to help each new product engender their own collaborative
-community, educating new developers in the philosophy and guidelines
-for collaborative development as defined by the members of the
-Foundation, and proposing to the board the promotion of such products
-to independent PMC status once their community has reached maturity"
-(reference Board Resolution).
-</p>
-      <p>The Incubator was tasked with the following responsibilities
-(reference Board Resolution):
-</p>
-      <ul>
-        <li>the acceptance and oversight of new products submitted or proposed to
-become part of the Foundation;
-</li>
-        <li>providing guidance and ensuring that subprojects under its purview
-develop products according to the Foundation's philosophy and
-guidelines for collaborative development; and
-</li>
-        <li>regularly evaluating products under its purview and making the
-determination in each case of whether the product should be
-abandoned, continue to receive guidance and support, or proposed to
-the board for promotion to full project status as part of an existing
-or new Foundation PMC; and be it further.
-</li>
-      </ul>
-      <section id="About+this+Document">
-        <title>About this Document
-</title>
-        <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
-
-          <a href="http://www.ietf.org/rfc/rfc2119.txt">RFC 2119
-</a>.
-
-        </p>
-        <section id="Scope">
-          <title>Scope
-</title>
-          <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>
+        <title>Incubation Policy
+        </title>
+        <atom url="http://mail-archives.apache.org/mod_mbox/incubator-general/?format=atom">general@incubator.apache.org Archives</atom>
+        <link href="http://purl.org/DC/elements/1.0/" rel="schema.DC"/>
+    </properties>
+    <body>
+
+        <section id="Incubation+Policy">
+            <section id='TOC'><title>Contents</title><toc/></section>
+            <title>Incubation Policy
+            </title>
+            <p>In October 2002 the Board of Directors of the Apache Software
+                Foundation passed a resolution creating the Apache Incubator PMC
+                (referred to as the "Incubator PMC" in this document) charged with
+                "accepting new products into the Foundation, providing guidance and
+                support to help each new product engender their own collaborative
+                community, educating new developers in the philosophy and guidelines
+                for collaborative development as defined by the members of the
+                Foundation, and proposing to the board the promotion of such products
+                to independent PMC status once their community has reached maturity"
+                (reference Board Resolution).
+            </p>
+            <p>The Incubator was tasked with the following responsibilities
+                (reference Board Resolution):
+            </p>
+            <ul>
+                <li>the acceptance and oversight of new products submitted or proposed to
+                    become part of the Foundation;
+                </li>
+                <li>providing guidance and ensuring that subprojects under its purview
+                    develop products according to the Foundation's philosophy and
+                    guidelines for collaborative development; and
+                </li>
+                <li>regularly evaluating products under its purview and making the
+                    determination in each case of whether the product should be
+                    abandoned, continue to receive guidance and support, or proposed to
+                    the board for promotion to full project status as part of an existing
+                    or new Foundation PMC; and be it further.
+                </li>
+            </ul>
+            <section id="About+this+Document">
+                <title>About this Document
+                </title>
+                <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
+
+                    <a href="http://www.ietf.org/rfc/rfc2119.txt">RFC 2119
+                    </a>.
+
+                </p>
+                <section id="Scope">
+                    <title>Scope
+                    </title>
+                    <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>
+                </section>
+                <section id="Relationship+to+Other+Documents">
+                    <title>Relationship to Other Documents
+                    </title>
+                    <p>This document is the normative set of requirements for Incubation.
+                        Where other documents are in conflict, this document should be taken
+                        as correct.  If other pages are in conflict and there is no clear path
+                        based on this page, please feel free to contact the
+                        <a href="howtoparticipate.html#Mailing+lists">general</a> list
+                    </p>
+                </section>
+            </section>
+            <section id="Changing+this+Document">
+                <title>Changing this Document
+                </title>
+                <p>The contents of this document are formally approved by the Incubator
+                    PMC. All changes must be authorised by the Incubator PMC.
+                </p>
+            </section>
+            <section id="Objectives+of+the+Process">
+                <title>Objectives of the Process
+                </title>
+                <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>
+                <ul>
+                    <li>new projects and sub-projects are developing products according to
+                        the ASF's philosophy and guidelines for collaborative development;
+                    </li>
+                    <li>the ownership of any code initially submitted by the project is
+                        formally and legally transferred to the ASF; and
+                    </li>
+                    <li>only those products that meet the Apache's requirements are fully
+                        accepted into the ASF.
+                    </li>
+                </ul>
+            </section>
+            <section id="Overview+of+the+Process">
+                <title>Overview of the Process
+                </title>
+                <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>
+                <p>
+                    <img alt="incubation-process.png" src="/incubation/incubation-process.png"/>
+                </p>
+            </section>
         </section>
-        <section id="Relationship+to+Other+Documents">
-          <title>Relationship to Other Documents
-</title>
-          <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>
+        <section id="Entry+to+Incubation">
+            <title>Entry to Incubation
+            </title>
+            <p>Please read the <a href="&root-path;/guides/entry.html">entry guide</a> to the process
+                in conjunction with this policy.
+            </p>
+            <p>In order to enter the Incubator, a Candidate MUST
+            </p>
+            <ul>
+                <li>be nominated for incubation by a member of the Apache Software
+                    Foundation (<a href='#Champion'>"The Champion"</a>); and
+                </li>
+                <li>be approved by a <a href='#Sponsor'>Sponsor</a>.
+                </li>
+            </ul>
+            <section id="Proposal">
+                <title>Proposal
+                </title>
+                <p>To start the approval process, a proposal MUST be submitted to
+                    the Sponsor. Please read the <a href="&root-path;/guides/proposal.html">Guide For Proposals</a>.
+                </p>
+            </section>
+            <section id="Approval+of+Proposal+by+Sponsor">
+                <title>Approval of Proposal by Sponsor
+                </title>
+                <p>The decision to approve the candidate proposal MUST be taken
+                    on a vote by the Sponsor, in accordance with that Entity's charter.
+                </p>
+            </section>
+            <section id='Acceptance+By+Incubator'>
+                <title>Acceptance By Incubator</title>
+                <p>Upon a successful result, the PMC Chair of the Sponsor SHOULD
+                    request that the Incubator PMC take on the Candidate as a new Podling.
+                </p>
+                <p>
+                    However when the Sponsor is the Incubator PMC, then they were the
+                    group of people who just voted. So the normal vote summary is
+                    sufficient.
+                </p>
+                <p>
+                    Otherwise the Sponsor is an existing top-level project PMC, which now
+                    needs to notify the Incubator PMC. The request,
+                    which should be sent to the Incubator PMC on the
+                    <a href="howtoparticipate.html#Mailing+lists">general</a> list,
+                    MUST contain the following information:
+                </p>
+                <ul>
+                    <li>a reference to the results of the vote (so as to provide an audit
+                        trail for the records);
+                    </li>
+                    <li>a reference to the Candidate's proposal;
+                    </li>
+                    <li>the Mentors, nominated by the Sponsor, who will guide the Candidate
+                        through the Incubation Process. At least one nominated Mentor MUST be
+                        a member of the Apache Software Foundation.
+                    </li>
+                </ul>
+                <p>
+                    Any Incubator PMC member can send an acknowledgement that the request
+                    was received, then a 72 hour waiting period starts.
+                    After this time has elapsed and no Incubator PMC member objects,
+                    the status file may be committed and the podling started.
+                    If any Incubator PMC member says "hold" before the 72 hours are up, a formal
+                    discussion/vote will be conducted.
+                </p>
+                <section id="Acceptance+of+Mentors">
+                    <title>Acceptance of Mentors</title>
+
+                    <p>The nominated Mentors MAY be immediately accepted by the Incubator
+                        PMC. However the Incubator PMC MAY also suggest replacement Mentors.
+                        The Incubator PMC has the final choice of Mentors.  Replacing of mentors
+                        should happen before the podling is voted on.
+                    </p>
+                </section>
+            </section>
+            <section id="Creation+of+Podling">
+                <title>Creation of Podling
+                </title>
+                <p>Upon acceptance by the Incubator PMC, the Candidate becomes a Podling
+                    under the care of the Incubator PMC.
+                </p>
+                <p>ASF Infrastructure is mostly responsible for the creation of a podling now, with some coordination from mentors.
+                    <a href="http://www.apache.org/dev/infra-contact#requesting-podling">This page</a> goes over the tasks required in the order they need to be filled in.</p>
+            </section>
         </section>
-      </section>
-      <section id="Changing+this+Document">
-        <title>Changing this Document
-</title>
-        <p>The contents of this document are formally approved by the Incubator
-PMC. All changes must be authorised by the Incubator PMC.
-</p>
-      </section>
-      <section id="Objectives+of+the+Process">
-        <title>Objectives of the Process
-</title>
-        <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>
-        <ul>
-          <li>new projects and sub-projects are developing products according to
-the ASF's philosophy and guidelines for collaborative development;
-</li>
-          <li>the ownership of any code initially submitted by the project is
-formally and legaly transferred to the ASF; and
-</li>
-          <li>only those products that meet the Apache's requirements are fully
-accepted into the ASF.
-</li>
-        </ul>
-      </section>
-      <section id="Overview+of+the+Process">
-        <title>Overview of the Process
-</title>
-        <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>
-        <p>
-          <img alt="incubation-process.png" src="/incubation/incubation-process.png"/>
-        </p>
-      </section>
-    </section>
-    <section id="Entry+to+Incubation">
-      <title>Entry to Incubation
-</title>
-     <p>Please read the <a href="&root-path;/guides/entry.html">guide</a> to the process
-in conjunction with this policy. 
-</p>
-        <p>In order to enter the Incubator, a Candidate MUST
-</p>
-        <ul>
-          <li>be nominated for incubation by a member of the Apache Software
-Foundation (<a href='#Champion'>"The Champion"</a>); and 
-</li>
-          <li>be approved by a <a href='#Sponsor'>Sponsor</a>.
-</li>
-        </ul>
- <section id="Proposal"> 
- <title>Proposal 
-</title> 
-<p>To start the approval process, a proposal MUST be submitted to 
-the Sponsor. Please read the <a href="&root-path;/guides/proposal.html">Guide For Proposals</a>. 
-</p>
-      </section>
- 	<section id="Approval+of+Proposal+by+Sponsor"> 
-   		<title>Approval of Proposal by Sponsor 
-</title>
-       <p>The decision to approve the candidate proposal MUST be taken 
-on a vote by the Sponsor, in accordance with that Entity's charter. 
-</p>
-	</section> 
- 	<section id='Acceptance+By+Incubator'> 
- 	<title>Acceptance By Incubator</title> 
-        <p>Upon a successful result, the PMC Chair of the Sponsor SHOULD
-          request that the Incubator PMC take on the Candidate as a new Podling.
-        </p>
-        <p>
-          However when the Sponsor is the Incubator PMC, then they were the
-          group of people who just voted. So the normal vote summary is
-          sufficient. 
-        </p>
-        <p>
-          Otherwise the Sponsor is an existing top-level project PMC, which now
-          needs to notify the Incubator PMC. The request,
-which should be sent to the Incubator PMC on the
-<a href="howtoparticipate.html#Mailing+lists">general</a> list,
-MUST contain the following information:
-</p>
-        <ul>
-          <li>a reference to the results of the vote (so as to provide an audit
-trail for the records);
-</li>
-          <li>a reference to the Candidate's proposal;
-</li>
-          <li>the Mentors, nominated by the Sponsor, who will guide the Candidate
-through the Incubation Process. At least one nominated Mentor MUST be
-a member of the Apache Software Foundation.
-</li>
-        </ul>
-<p>
-Any Incubator PMC member can send an acknowledgement that the request
-was received, then a 72 hour waiting period starts.
-After this time has elapsed and no Incubator PMC member objects,
-the status file may be committed and the podling started.
-If any Incubator PMC member says "hold" before the 72 hours are up, a formal
-discussion/vote will be conducted.
-</p>
-        <section id="Acceptance+of+Mentors">
-          <title>Acceptance of Mentors</title>
-
-        <p>The nominated Mentors MAY be immediately accepted by the Incubator
-PMC. However the Incubator PMC MAY also suggest replacement Mentors.
-The Incubator PMC has the final choice of Mentors.
-</p>
+        <section id="Incubation+Activities">
+            <title>Incubation Activities</title>
+            <p>The following sections detail the minimum activities that must be
+                undertaken by the various parties during an Incuabation process.
+            </p>
+            <section id="Setting+Up+a+New+Podling">
+                <title>Setting Up a New Podling</title>
+                <p>
+                    Once a proposal has been <a href='#Acceptance+By+Incubator'>accepted</a>
+                    and the podling <a href='#Creation+of+Podling'>created</a>
+                    a <a href='#Mentor'>Mentor</a> SHOULD initiate the creation of:
+                </p>
+                <ul>
+                    <li>the <a href='&root-path;/guides/mentor.html#Overview'>podling metadata and the reporting schedule</a>;</li>
+                    <li>the <a href='#Ongoing+Activities'>project status</a> page;</li>
+                    <li>the mailing lists;</li>
+                    <li>the repository space;</li>
+                    <li>and any other resources requested by the podling</li>
+                </ul>
+                <p>
+                    Your project's mentors are able to undertake many of the setup
+                    tasks. See <a href="&root-path;/guides/mentor.html">the mentor guide</a>
+                    for guidelines about the setup process.
+                    See notes about how to
+                    <a href="http://www.apache.org/dev/infra-contact">request project resources</a>
+                    such as new committer accounts and new mailing lists.
+                    (Note that a committer account will not be created
+                    <a href="http://www.apache.org/dev/pmc.html#newcommitter">until the
+                        Contributor License Agreement (CLA) has been recorded.</a>)
+                </p>
+                <p>The initial source code to be brought in must pass through one of two gates:
+                    <ul>
+                        <li><a href="../ip-clearance/">IP Clearance</a>, typically for existing open source projects moving to the ASF or for donations to existing Podlings</li>
+                        <li><a href="https://www.apache.org/licenses/software-grant.txt">Software Grant Agreement</a>, typically for newly open sourced projects or corporate backed projects</li>
+                    </ul>
+                </p>
+                <p>
+                    Your project committers/PPMC members need to become familiar with
+                    the <a href="http://www.apache.org/dev/#infrastructure">ASF Infrastructure information</a>
+                    and in particular the
+                    <a href="http://www.apache.org/dev/#pmc">PMC</a> notes.
+                    Also see the <a href="../guides/pmc.html">Incubator PMC Guide</a>.
+                </p>
+            </section>
+            <section id="Ongoing+Activities">
+                <title>Ongoing Activities</title>
+                <p>The progress of a Podling SHALL be tracked in a "project status" document.
+                    This SHALL be stored in
+                    <a href='https://svn.apache.org/repos/asf/incubator/public/trunk/content/projects/'>
+                        https://svn.apache.org/repos/asf/incubator/public/trunk/content/projects/
+                    </a>
+                    and so become available at
+
+                    <a href="http://incubator.apache.org/projects/">http://incubator.apache.org/projects/
+                    </a>
+                </p>
+                <p>The "project status" document SHALL include the following minimum
+                    content :
+                </p>
+                <ul>
+                    <li>status of setup tasks;
+                    </li>
+                    <li>all exit criteria (see
+                        <a href='Exiting+the+Incubator'>Exiting the Incubator</a>);
+
+                    </li>
+                    <li>status of Podling against exit criteria.
+                    </li>
+                </ul>
+                <p>The Mentors MUST ensure that the "project status" document is up to
+                    date at all times. See these
+
+                    <a href="../guides/website.html#Edit+your+project+status+page">instructions
+                    </a>.
+
+                </p>
+            </section>
+            <section id="Quarterly+Reports">
+                <title>Quarterly Reports</title>
+                <p>Each Podling in Incubation SHALL undergo a regular review of progress
+                    by the Incubator PMC. Such reviews SHALL occur quarterly. The
+                    Incubator PMC MAY, at their discretion, request an out of cycle
+                    report from a podling. The Incubator PMC SHALL inform the podling of this request
+                    at least 4 weeks in advance.</p>
+                <p>A podling will be required to report monthly for its first three
+                    months under incubation.  </p>
+                <p>
+                    A podling's report will always take the following form
+                </p>
+                <pre>
+                    <i>Podling Name</i>
+
+                    <i>podling description</i>
+
+                    <i>podling name</i> has been incubating since <i>date</i>.
+
+                    Three most important issues to address in the move towards graduation:
+
+                    <i>List out three issues, that may be blocking the podling from graduating.  </i>
+
+                    Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
+                    aware of?
+
+                    <i>Any issues listed here should also be brought up in public discussions on incubator mailing lists</i>
+
+                    How has the community developed since the last report?
+
+                    <i>Describe changes in the community, may include new committers, improved mailing list activity, code changes, etc.</i>
+
+                    Date of last release:
+
+                    <i>Include the date of the last release</i>
+
+                    When were the last committers or PPMC members elected?
+
+                    <i>Include dates of when the committers or PPMC members were added</i>
+
+                    Signed-off-by:
+
+                    [ ](<i>podling name</i>) <i>Mentor Name</i>
+
+                    Shepherd/Mentor notes:
+
+                    <i>Any notes identified by either a mentor or a shepherd</i>
+                </pre>
+
+                <p>Termination and Graduation are discussed in more detail in section
+                    "Graduating from the Incubator".</p>
+            </section>
         </section>
-      </section>
-      <section id="Creation+of+Podling">
-        <title>Creation of Podling
-</title>
-        <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>
-      </section>
-    </section>
-    <section id="Incubation+Activities">
-      <title>Incubation Activities
-</title>
-      <p>The following sections detail the minimum activities that must be
-undertaken by the various parties during an Incuabation process.
-</p>
-      <section id="Setting+Up+a+New+Podling">
-        <title>Setting Up a New Podling</title>
-<p> 
-Once a proposal has been <a href='#Acceptance+By+Incubator'>accepted</a> 
-and the podling <a href='#Creation+of+Podling'>created</a> 
-a <a href='#Mentor'>Mentor</a> SHOULD initiate the creation of: 
-</p>
-        <ul>
-            <li>the <a href='&root-path;/guides/mentor.html#Overview'>podling metadata and the reporting schedule</a>;</li> 
-            <li>the <a href='#Ongoing+Activities'>project status</a> page;</li> 
-            <li>the mailing lists;</li> 
-            <li>the repository space;</li> 
-        </ul>
-        <p>
-          Your project's mentors are able to undertake many of the setup
-          tasks. See <a href="&root-path;/guides/mentor.html">the mentor guide</a>
-          for guidelines about the setup process. 
-          See notes about how to
-          <a href="http://www.apache.org/dev/infra-contact">request project resources</a>
-          such as new committer accounts and new mailing lists.
-          (Note that a committer account will not be created
-          <a href="http://www.apache.org/dev/pmc.html#newcommitter">until the
-          Contributor License Agreement (CLA) has been recorded.</a>)
-        </p>
-	<p>The source code that comes into the ASF as part of the podling project
-	must pass through the IP clearance process; details are in the mentor
-	guide linked above.
-	</p>
-        <p>
-          Your project committers/PPMC members need to become familiar with
-          the <a href="http://www.apache.org/dev/#infrastructure">ASF Infrastructure information</a>
-          and in particular the
-          <a href="http://www.apache.org/dev/#pmc">PMC</a> notes.
-          Also see the <a href="../guides/pmc.html">Incubator PMC Guide</a>.
-       </p>
-     </section>
-      <section id="Ongoing+Activities">
-        <title>Ongoing Activities</title>
- <p>The progress of a Podling SHALL be tracked in a "project status" document.
-This SHALL be stored in
-<a href='http://svn.apache.org/repos/asf/incubator/public/trunk/content/projects/'>
-http://svn.apache.org/repos/asf/incubator/public/trunk/content/projects/
-</a>
-and so become available at 
-
-          <a href="http://incubator.apache.org/projects/">http://incubator.apache.org/projects/
-</a>
-        </p>
-        <p>The "project status" document SHALL include the following minimum
-content :
-</p>
-        <ul>
-          <li>status of setup tasks;
-</li>
- 		  <li>all exit criteria (see
- <a href='Exiting+the+Incubator'>Exiting the Incubator</a>); 
-
-          </li>
-          <li>status of Podling against exit criteria.
-</li>
-        </ul>
-<p>The Mentors MUST ensure that the "project status" document is up to
-date at all times. See these 
-
-          <a href="../guides/website.html#Edit+your+project+status+page">instructions
-</a>.
-
-        </p>
-      </section>
-      <section id="Review+of+Activity">
-        <title>Review of Activity
-</title>
-        <p>Each Podling in Incubation SHALL undergo a regular review of progress
-by the Incubator PMC. Such reviews SHALL occur at least quarterly. 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>
-        <p>At least one week prior to each review, the Mentor MUST produce a
-report for the Incubator PMC detailing overall progress with a focus
-on the preceding review period. It is RECOMMENDED that the report be
-based on the "project status" document for the Podling.
-</p>
-        <p>After each review, the Incubator PMC SHALL produce an Assessment of
-the project. The Assessment SHALL contain one of three
-recommendations:
-</p>
-        <ul>
-          <li>that the Podling be Terminated;
-</li>
-          <li>that the Podling continue in Incubation; or
-</li>
-          <li>that the Podling be Graduated from Incubation.
-</li>
-        </ul>
-        <p>Termination and Graduation are discussed in more detail in section
-"Graduating from the Incubator".
-</p>
-      </section>
-      <section id="Disputing+an+Assessment">
-        <title>Disputing an Assessment
-</title>
-        <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>
-        <p>Upon receipt of an Assessment Dispute, the Incubator PMC SHALL review
-the request and provide feedback to the Podling and Mentor. Such
-feedback MAY include a change to the original Assessment.
-</p>
-        <p>Should the Podling and/or Mentor still disagree with the contents of
-the report, they MAY appeal to the Board of the Apache Software
-Foundation. Such an appeal MUST include
-</p>
-        <ul>
-          <li>the original assessment;
-</li>
-          <li>the request for review to the Incubator PMC;
-</li>
-          <li>the response from the Incubator PMC; and
-</li>
-          <li>the reason the Podling and/or Mentor still dispute the report.
-</li>
-        </ul>
-        <p>The Board of the Apache Software Foundation MAY, after reviewing the
-appeal, choose to
-</p>
-        <ul>
-          <li>ammend the incubation Assessment;
-</li>
-          <li>validate the assessment of the Incubator PMC; or
-</li>
-          <li>take any other action it deems appropriate to the circumstance.
-</li>
-        </ul>
-        <p>The decision of the Board of the Apache Software Foundation is final.
-</p>
-      </section>
-      <section id="Continuation">
-        <title>Continuation
-</title>
-        <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>
-      </section>
-    </section>
-    <section id="Podling+Constraints">
-      <title>Podling Constraints
-</title>
-      <p>While in Incubation, Podlings are constrained in the actions they can
-undertake.
-</p>
-      <section id="Branding">
-        <title>Branding</title>
-        <p>Please consult the guide to <a href="../guides/branding.html"
-        >Podling Branding</a>.</p>
-      </section>
-      <section id="Releases">
-        <title>Releases</title>
-        <p>
-          See the guidelines for <a href="&root-path;/guides/releasemanagement.html">Podling releases</a>
-          in conjunction with this policy. 
-        </p>
- <p>Podlings are not yet fully accepted as part of the Apache Software
-Foundation. No release made by a Podling will be endorsed by the ASF.
-Unendorsed releases may be made by Podlings subject to the following policy. 
-</p>
-        <p>Podlings in Incubation SHALL NOT perform any releases of software
-without the explicit approval of the Incubator PMC. Such approval
-SHALL be given only after the Incubator PMC has followed the process
-detailed in these guidelines, and SHALL NOT occur until all
-source has been legally transferred to the ASF.
-</p>
-        <p>Therefore, should a Podling decide it wishes to perform a release, 
-the Podling SHALL hold a vote on the Podling's public -dev list. At least
-three +1 votes are required (see the
-<a href="http://www.apache.org/foundation/voting.html">Apache Voting Process</a>
-page).
-If the majority of all votes is positive, then the Podling
-SHALL send a
-summary of that vote to the Incubator's 
-<a href="howtoparticipate.html#Mailing+lists">general</a> 
-list and formally request the
-Incubator PMC approve such a release. Three +1 Incubator PMC votes are
-required.
-Below is an example showing how an incubating project managed this process:
-</p>
-
-<ul>
-   <li><a href="http://mail-archives.apache.org/mod_mbox/incubator-stdcxx-dev/200601.mbox/%3c43C1C0A0.7040401@roguewave.com%3e">Post to the Podling -dev list calling the vote.</a></li>
-   <li><a href="http://mail-archives.apache.org/mod_mbox/incubator-general/200601.mbox/%3c43D7AC9E.30205@roguewave.com%3e">Post to the Incubator's general list
-requesting approval from the Incubator PMC.</a></li>
-</ul>
-
-        <p>Should the Incubator PMC, in accordance with these guidelines
-vote to approve the request, the Podling MAY perform the release
-under the following constraints :
-</p>
-        <ul>
-          <li>the release archive MUST contain the word "incubating" in the
-filename; and
-</li>
-          <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>
-        <p>
-Releases for <em>podling</em> <strong>MUST</strong> be distributed through 
-<code>http://www.apache.org/dist/incubator/<em>podling</em></code>
-In addition, the Podling MAY choose to distribute approved releases through
-other channels like the central Maven repository.
-        </p>
-
-          <section id="2013+Alternate+Release+Voting+Process">
-            <title>
-2013 Alternate Release Voting Process
+        <section id="Podling+Constraints">
+            <title>Podling Constraints
             </title>
-
-            <p>
-Select podlings pre-cleared by a majority vote of the IPMC MAY participate in
-an alternate release voting process:
+            <p>This section describes the key differences, specifically constraints, that a podling has while under incubation.
             </p>
+            <section id="Branding">
+                <title>Branding</title>
+                <p>Please consult the guide to <a href="../guides/branding.html"
+                >Podling Branding</a>.</p>
+                <p>Specifically, the following constraints are placed on the podling from a branding stand point, in addition to all standard ASF Branding policies:</p>
+                <ul>
+                    <li>The podling's website must be referred to as http://&quot;podling-name&quot;.incubator.apache.org/</li>
+                    <li>The podling's website must include the incubating disclaimer</li>
+                    <li>The podling's webiste should include the incubator logo</li>
+
+                </ul>
+            </section>
+            <section id="Releases">
+                <title>Releases</title>
+                <p>
+                    See the <a href="http://www.apache.org/dev/release.html">Apache Software Product Release Policy</a>
+                    in conjunction with this policy.
+                </p>
+                <p>Podlings are not yet fully accepted as part of the Apache Software
+                    Foundation. No release made by a Podling will be endorsed by the ASF.
+                    Unendorsed releases may be made by Podlings subject to the following policy.
+                </p>
+                <p>Podlings are not comprised of PMC members, they are not full projects yet.
+                    The Incubator PMC is responsible for all podling releases.
+                    As such, podlings in Incubation SHALL NOT perform any releases of software
+                    without the explicit approval of the Incubator PMC. Such approval
+                    SHALL be given only after the Incubator PMC has followed the process
+                    detailed in these guidelines, and SHALL NOT occur until all
+                    source has been legally transferred to the ASF.
+                </p>
+                <p>Therefore, should a Podling decide it wishes to perform a release,
+                    the Podling SHALL hold a vote on the Podling's public dev@ list. At least
+                    three +1 votes are required (see the
+                    <a href="http://www.apache.org/foundation/voting.html">Apache Voting Process</a>
+                    page).
+                    If the majority of all votes is positive, then the Podling
+                    SHALL send a
+                    summary of that vote to the Incubator's
+                    <a href="howtoparticipate.html#Mailing+lists">general</a>
+                    list and formally request the
+                    Incubator PMC approve such a release. Three +1 Incubator PMC votes are
+                    required.
+                    Below is an example showing how an incubating project managed this process:
+                </p>
+
+                <ul>
+                    <li><a href="http://mail-archives.apache.org/mod_mbox/incubator-stdcxx-dev/200601.mbox/%3c43C1C0A0.7040401@roguewave.com%3e">Post to the Podling dev list calling the vote.</a></li>
+                    <li><a href="http://mail-archives.apache.org/mod_mbox/incubator-general/200601.mbox/%3c43D7AC9E.30205@roguewave.com%3e">Post to the Incubator's general list
+                        requesting approval from the Incubator PMC.</a></li>
+                </ul>
+
+                <p>In addition to the standard ASF policies for release contents, the Incubator PMC
+                    requires the following additional attributes on a release:
+                </p>
+                <ul>
+                    <li>the release archive MUST contain the word "incubating" in the
+                        filename; and
+                    </li>
+                    <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>
 
-            <p>
-Should a Podling decide it wishes to perform a release, the Podling SHALL hold
-a vote on the Podling's dev list and create a permanently archived Release
-Manifest as described in the
-<a href="&root-path;/guides/release.html">Experimental Release Guide.</a>
-At least three +1 votes from PPMC members are required (see the
-<a href="http://www.apache.org/foundation/voting.html">Apache Voting
-Process</a> page).  If the majority of PPMC votes is positive, then the Podling
-SHALL send a summary of that vote to the Incubator's general list and formally
-request the Incubator PMC approve such a release.
-
-Formal approval requires three binding +1 votes and more positive than
-negative votes.  Votes cast by members of the Incubator PMC are always
-binding.  For all releases after the first, votes cast by members of the PPMC
-are binding if a Mentor approves the Release Manifest.
+                <section id="2013+Alternate+Release+Voting+Process">
+                    <title>
+                        2013 Alternate Release Voting Process
+                    </title>
+
+                    <p>
+                        Select podlings pre-cleared by a majority vote of the IPMC MAY participate in
+                        an alternate release voting process:
+                    </p>
+
+                    <p>
+                        Should a Podling decide it wishes to perform a release, the Podling SHALL hold
+                        a vote on the Podling's dev list and create a permanently archived Release
+                        Manifest as described in the
+                        <a href="&root-path;/guides/release.html">Experimental Release Guide.</a>
+                        At least three +1 votes from PPMC members are required (see the
+                        <a href="http://www.apache.org/foundation/voting.html">Apache Voting
+                            Process</a> page).  If the majority of PPMC votes is positive, then the Podling
+                        SHALL send a summary of that vote to the Incubator's general list and formally
+                        request the Incubator PMC approve such a release.
+
+                        Formal approval requires three binding +1 votes and more positive than
+                        negative votes.  Votes cast by members of the Incubator PMC are always
+                        binding.  For all releases after the first, votes cast by members of the PPMC
+                        are binding if a Mentor approves the Release Manifest.
+                    </p>
+                </section>
+            </section>
+        </section>
+        <section id="Graduating+from+the+Incubator">
+            <title>Graduating from the Incubator
+            </title>
+            <p>This section describes the requirements and process for graduating from the
+                Incubator.
             </p>
-          </section>
-      </section>
-      <section id="Use+of+Apache+Resources">
-        <title>Use of Apache Resources
-</title>
-        <p>The Podling is not yet an Apache project, and it should thus always
-refer to the Incubator Project Resource usage Guidelines, that are as
-follows.
-</p>
-        <section id="Website">
-          <title>Website</title>
-          <p>Please consult the guide to <a href="../guides/sites.html"
-          >Podling Websites</a> for the current policies for websites.</p>
+            <section id="Minimum+Graduation+Requirements">
+                <title>Minimum Graduation Requirements
+                </title>
+                <p>Prior to graduation, a Podling needs to show that :
+                </p>
+                <ul>
+                    <li>it is a worthy and healthy project;
+                    </li>
+                    <li>it truly fits within the ASF framework; and
+                    </li>
+                    <li>it "gets" the Apache Way.
+                    </li>
+                </ul>
+                <p>This is achieved by imposing a set of Graduation Criteria that, when met,
+                    will demonstrate these objectives.
+                </p>
+                <p>Therefore, to successfully graduate from the Incubator
+                    into the ASF, a Podling SHALL meet the minimum requirements
+                    detailed below. The Incubator PMC MAY set additional requirements at
+                    their discretion. Such additional requirements MAY be proposed by the
+                    Mentor or the Sponsor, however only the Incubator PMC is authorised
+                    to formally place such requirements on a Podling.
+                </p>
+                <p>The minimum requirements that a Podling SHALL meet prior to being
+                    graduated to the ASF are :
+                </p>
+                <ul>
+                    <li>
+                        <strong>Legal</strong>
+                    </li>
+                    <li style="list-style: none">
+                        <ul>
+                            <li>All code in compliance with the Apache License, v2.0</li>
+                            <li>The code base must contain only <a href="https://www.apache.org/legal/resolved.html">approved licenses</a></li>
+                            <li>License grant complete</li>
+                            <li>CLAs on file.</li>
+                            <li>Check of <a href="&root-path;/guides/names.html">project name for trademark issue</a>.</li>
+                        </ul>
+                    </li>
+                </ul>
+                <ul>
+                    <li>
+                        <strong>Meritocracy / Community
+                        </strong>
+                    </li>
+                    <li style="list-style: none">
+                        <ul>
+                            <li>Demonstrate an active and diverse development community</li>
+                            <li>The project is not highly dependent on any single contributor
+                                (there are at least 3 legally independent committers and there is no
+                                single company or entity that is vital to the success of the project)</li>
+                            <li>The above implies that new committers are admitted according to ASF
+                                practices</li>
+                            <li>ASF style voting has been adopted and is standard practice</li>
+                            <li>Demonstrate ability to tolerate and resolve conflict within the
+                                community.</li>
+                            <li>Release plans are developed and executed in public by the community.</li>
+                            <li>Engagement by the incubated community with the other ASF communities.</li>
+                            <li>Incubator PMC has voted for graduation recommendation</li>
+                            <li>Destination PMC has voted for final acceptance (if applicable)</li>
+                        </ul>
+                    </li>
+                </ul>
+                <ul>
+                    <li>
+                        <strong>Alignment / Synergy
+                        </strong>
+                    </li>
+                    <li style="list-style: none">
+                        <ul>
+                            <li>Use of other ASF subprojects</li>
+                            <li>Develop synergistic relationship with other ASF projects</li>
+                        </ul>
+                    </li>
+                </ul>
+                <ul>
+                    <li>
+                        <strong>Infrastructure</strong>
+                    </li>
+                    <li style="list-style: none">
+                        <ul>
+                            <li>SVN or git repository(ies) have been created</li>
+                            <li>Mailing list(s) have been created</li>
+                            <li>Mailing lists are being archived</li>
+                            <li>Issue tracker has been created</li>
+                            <li>Project website has been created and complies with the Apache Project Branding Requirements</li>
+                            <li>Project ready to comply with ASF mirroring guidelines</li>
+                            <li>Project is integrated with GUMP if appropriate</li>
+                            <li>Releases are PGP signed by a member of the community</li>
+                            <li>Developers tied into ASF PGP web of trust</li>
+                        </ul>
+                    </li>
+                </ul>
+            </section>
+            <section id="Termination+of+a+Podling">
+                <title>Termination of a Podling
+                </title>
+                <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 Sponsor. 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>
+            </section>
+            <section id="Graduation+as+a+Top+Level+Project">
+                <title>Graduation as a Top Level Project
+                </title>
+                <p>In cases where a Podling has successfully completed Incubation, and
+                    is graduating from the Incubator to become a Top Level Project, the Incubator
+                    PMC SHALL provide a recommendation to the board that the Podling is
+                    ready to gradualate. The recommendation SHALL include a draft
+                    resolution for the board to vote on.
+                </p>
+            </section>
+            <section id="Graduation+as+a+sub-project">
+                <title>Graduation as a sub-project</title>
+                <p>In cases where a Podling has successfully completed Incubation, and
+                    is graduating from 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 graduate.
+                </p>
+            </section>
+            <section id="Post-Graduation+Check+List">
+                <title>Post-Graduation Check List
+                </title>
+                <p>See <a href="&root-path;/guides/graduation.html">Graduation Guide</a>.
+                </p>
+            </section>
         </section>
-      </section>
-    </section>
-    <section id="Graduating+from+the+Incubator">
-      <title>Graduating from the Incubator
-</title>
-      <p>This section describes the requirements and process for graduating from the
-Incubator.
-</p>
-      <section id="Minimum+Graduation+Requirements">
-        <title>Minimum Graduation Requirements
-</title>
-        <p>Prior to graduation, a Podling needs to show that :
-</p>
-        <ul>
-          <li>it is a worthy and healthy project;
-</li>
-          <li>it truly fits within the ASF framework;and
-</li>
-          <li>it "gets" the Apache Way.
-</li>
-        </ul>
-        <p>This is achieved by imposing a set of Graduation Criteria that, when met,
-will demonstrate these objectives.
-</p>
-        <p>Therefore, to successfully graduate from the Incubator
-into the ASF, a Podling SHALL meet the minimum requirements
-detailed below. The Incubator PMC MAY set additional requirements at
-their discretion. Such additional requirements MAY be proposed by the
-Mentor or the Sponsor, however only the Incubator PMC is authorised
-to formally place such requirements on a Podling.
-</p>
-        <p>The minimum requirements that a Podling SHALL meet prior to being
-graduated to the ASF are :
-</p>
-        <ul>
-          <li>
-            <strong>Legal
-</strong>
-          </li>
-          <li style="list-style: none">
-            <ul>
-              <li>All code ASL'ed
-</li>
-              <li>The code base must contain only ASL or ASL-compatible dependencies
-</li>
-              <li>License grant complete
-</li>
-              <li>CLAs on file.
-</li>
-              <li>Check of project name for trademark issues
-</li>
-            </ul>
-          </li>
-        </ul>
-        <ul>
-          <li>
-            <strong>Meritocracy / Community
-</strong>
-          </li>
-          <li style="list-style: none">
-            <ul>
-              <li>Demonstrate an active and diverse development community
-</li>
-              <li>The project is not highly dependent on any single contributor
-(there are at least 3 legally independent committers and there is no
-single company or entity that is vital to the success of the project)
-</li>
-              <li>The above implies that new committers are admitted according to ASF
-practices
-</li>
-              <li>ASF style voting has been adopted and is standard practice
-</li>
-              <li>Demonstrate ability to tolerate and resolve conflict within the
-community.
-</li>
-              <li>Release plans are developed and excuted in public by the community.
-</li>
-              <li style="list-style: none">
-                <ul>
-                  <li>(requirement on minimum number of such releases?)
-</li>
-                  <li>Note: incubator projects are not permitted to issue an official
-Release. Test snapshots (however good the quality) and Release
-
-                    <em>plans
-</em>are OK.
-
-                  </li>
-                </ul>
-              </li>
-              <li>Engagement by the incubated community with the other ASF communities,
-particularly infrastructure@ (this reflects my personal bias that
-projects should pay an nfrastructure "tax").
-</li>
-              <li>Incubator PMC has voted for graduation
-</li>
-              <li>Destination PMC, or ASF Board for a TLP, has voted for final
-acceptance
-</li>
-            </ul>
-          </li>
-        </ul>
-        <ul>
-          <li>
-            <strong>Alignment / Synergy
-</strong>
-          </li>
-          <li style="list-style: none">
-            <ul>
-              <li>Use of other ASF subprojects
-</li>
-              <li>Develop synergistic relationship with other ASF subprojects
-</li>
-            </ul>
-          </li>
-        </ul>
-        <ul>
-          <li>
-            <strong>Infrastructure
-</strong>
-          </li>
-          <li style="list-style: none">
-            <ul>
-              <li>SVN module has been created
-</li>
-              <li>Mailing list(s) have been created
-</li>
-              <li>Mailing lists are being archived
-</li>
-              <li>Issue tracker has been created
-</li>
-              <li>Project website has been created and complies with the Apache Project Branding Requirements
-</li>
-              <li>Project ready to comply with ASF mirroring guidelines
-</li>
-              <li>Project is integrated with GUMP if appropriate
-</li>
-              <li>Releases are PGP signed by a member of the community
-</li>
-              <li>Developers tied into ASF PGP web of trust
-</li>
-            </ul>
-          </li>
-        </ul>
-      </section>
-      <section id="Termination+of+a+Podling">
-        <title>Termination of a Podling
-</title>
-        <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 Sponsor. 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>
-      </section>
-      <section id="Graduation+as+a+Top+Level+Project">
-        <title>Graduation as a Top Level Project
-</title>
-        <p>In cases where a Podling has successfully completed Incubation, and
-is graduating from the Incubator to become a Top Level Project, the Incubator
-PMC SHALL provide a recommendation to the board that the Podling is
-ready to gradualate. The recommendation SHALL include a draft
-resolution for the board to vote on.
-</p>
-      </section>
-      <section id="Graduation+as+a+sub-project">
-        <title>Graduation as a sub-project
-</title>
-        <p>In cases where a Podling has successfully completed Incubation, and
-is graduating from 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 graduate.
-</p>
-      </section>
-      <section id="Post-Graduation+Check+List">
-        <title>Post-Graduation Check List
-</title>
-        <p>See <a href="&root-path;/guides/graduation.html">Graduation Guide</a>.
-          </p>
-      </section>
-    </section>
-    <section id="Roles+in+the+Incubation+Process">
-      <title>Roles Defined
-</title>
-      <p>Definitions of the roles involved in the Incubation process.
-</p>
-      <section id="Incubator+Project+Management+Committee+%28PMC%29">
-        <title>Incubator Project Management Committee (PMC)
-</title>
-        <p>
-The Project Management Committee is responsible to the Board for administering
-the Incubator Project in the manner specified in the founding
-<a href='http://incubator.apache.org/official/resolution.html'>resolution</a>. 
-</p>
-        <p>
-The roles and responsibilities of the PMC are described and discussed
-<a href='Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29'>here</a>.
-</p>
-      </section>
-      <section id="Chair+of+the+Incubator+PMC">
-        <title>Chair of the Incubator PMC
-</title>
-        <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>
-      </section>
-      <section id="Candidate">
-        <title>Candidate
-</title>
-        <p>A proposal for incubation. Described in detail
-<a href='Roles_and_Responsibilities.html#Candidate'>here</a>. 
-</p>
-      </section>
-      <section id="Champion">
-        <title>Champion</title>
-        <p>A Member or Officer of the Apache Software Foundation who supports a Candidate's
-application for Incubation and acts as a liaison between the incoming
-podling and the Incubator in the early stages of incubation.
-</p>
-      </section>
-      <section id="Sponsor">
-        <title>Sponsor
-</title>
-        <p>
-A Sponsor SHALL be either: 
-</p>
-        <ul>
-          <li>the Board of the Apache Software Foundation; 
-</li>
-          <li>a Top Level Project (TLP) within the Apache Software Foundation
-(where the TLP considers the Candidate to be a suitable sub-project);
-or 
-</li>
-          <li>the Incubator PMC.
-</li>
-        </ul>
-<p>
-This role and its responsibilities are discussed
-<a href="&root-path;/incubation/Roles_and_Responsibilities.html#Sponsor">here</a>.
-</p> 
-      </section>
-      <section id="Mentor">
-        <title>Mentor
-</title>
-        <p>A Podling has one or more Mentors, one of which MUST be an Apache Member. 
-Mentors are responsible for actively monitoring the podling, guide the podling in 
-<a href="http://apache.org/foundation/how-it-works.html">the Apache Way</a>,
-and report its status to the Sponsor and the Incubator PMC. All Mentors must 
-be members of the Incubator PMC. A Mentor has
-<a href="Roles_and_Responsibilities.html#Mentor">responsibilities</a>
-toward the Incubator PMC, the Sponsor, and the community of the assigned
-Podling.
-</p>
-      </section>
-      <section id="Committers">
-        <title>Committers
-</title>
-        <p>The candidate shall declare an initial set of committers. On
-acceptance of a candidate project, the assigned Mentors shall be given
-access to the Podling's repository for the duration of the
-incubation process. This is to allow the Mentors 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>
-      </section>
-    </section>
-  </body>
+        <section id="Roles+in+the+Incubation+Process">
+            <title>Roles Defined
+            </title>
+            <p>A full description of Roles during Incubation can be found on
+                the <a href="Roles_And_Responsibilities.html">Roles and Responsibilities</a> page.</p>
+        </section>
+    </body>
 </document>



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


Mime
View raw message