Google Git
Sign in
apache / incubator / 766f9906a15ef7548ed922f90c5412e569afbd64 / . / sammydavis / incubation / Incubation_Policy.html
blob: beca8265918b1b67298dd9d77b668cbfa171647d [file] [log] [blame]
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<!--
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
regarding copyright ownership. The ASF licenses this file
to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License. You may obtain a copy of the License at
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 xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<link rel="stylesheet" href="../style/bootstrap-1-3-0-min.css" type="text/css" />
<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>Incubation Policy
- Apache Incubator</title>
</head>
<body>
<div class="container">
<div class="row">
<div class="span12">
<a href="http://www.apache.org/"><img src="http://incubator.apache.org/images/asf_logo_wide_small.png" alt="The Apache Software Foundation" border="0" style="margin-top: 2px" width="62%"/></a>
</div>
<div class="span4">
<a href="http://incubator.apache.org/"><img src="../images/egg-logo2.png" alt="Apache Incubator" border="0"/></a>
</div>
</div>
<div class="row"><div class="span16"><hr noshade="noshade" size="1"/></div></div>
<div class="row">
<div class="span4">
<form action="http://www.google.com/search" method="get">
<input value="incubator.apache.org" name="sitesearch" type="hidden"/>
<input size="20" name="q" id="query" type="text" value="search..."
onclick="if(this.value == 'search...') {this.value = ''}"/>
<input name="Search" value="Go" type="submit"/>
</form>
<div class="menuheader">General</div>
<menu compact="compact">
<li><a href="../index.html">Welcome</a></li>
<li><a href="../incubation/Process_Description.html">Incubation Overview</a></li>
<li><a href="../incubation/Incubation_Policy.html">Incubation Policy</a></li>
<li><a href="../guides/index.html">Incubation Guides</a></li>
<li><a href="../incubation/Roles_and_Responsibilities.html">Roles and Responsibilities</a></li>
<li><a href="../faq.html">General FAQ</a></li>
<li><a href="http://wiki.apache.org/incubator">Incubator Wiki</a></li>
<li><a href="../whoweare.html">Who We Are</a></li>
<li><a href="../sitemap.html">Site Map</a></li>
</menu>
<div class="menuheader">Status</div>
<menu compact="compact">
<li><a href="../projects/index.html">Project List</a></li>
<li><a href="../clutch.html">Clutch Report</a></li>
<li><a href="../ip-clearance/index.html">IP Clearance</a></li>
<li><a href="../history/index.html">Incubator History</a></li>
</menu>
<div class="menuheader">Entry Guides</div>
<menu compact="compact">
<li><a href="../guides/proposal.html">Proposal Guide</a></li>
</menu>
<div class="menuheader">Podling Guides</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/mentor.html">Podling Mentor</a></li>
<li><a href="../guides/releasemanagement.html">Podling Releases</a></li>
<li><a href="../guides/branding.html">Podling Branding/Publicity</a></li>
<li><a href="../guides/sites.html">Podling Websites</a></li>
<li><a href="../guides/graduation.html">Graduation</a></li>
<li><a href="../guides/retirement.html">Retirement</a></li>
</menu>
<div class="menuheader">Other Guides</div>
<menu compact="compact">
<li><a href="../guides/participation.html">Participation</a></li>
<li><a href="../faq.html">General FAQ</a></li>
<li><a href="../guides/pmc.html">Incubator PMC (IPMC)</a></li>
<li><a href="../guides/chair.html">IPMC Chair</a></li>
<li><a href="../guides/lists.html">Mailing Lists</a></li>
<li><a href="../guides/website.html">Incubator Website</a></li>
</menu>
<div class="menuheader">ASF</div>
<menu compact="compact">
<li><a href="http://www.apache.org/foundation/how-it-works.html">How Apache Works</a></li>
<li><a href="http://www.apache.org/dev/">Developer Documentation</a></li>
<li><a href="http://www.apache.org/foundation/">Foundation</a></li>
<li><a href="http://www.apache.org/foundation/sponsorship.html">Sponsor Apache</a></li>
<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
</menu>
<!-- start Ads Server -->
<iframe src="http://www.apache.org/ads/buttonbar.html"
style="border-width:0; float: left" frameborder="0" scrolling="no"
width="135" height="265"></iframe>
<!-- end Ads Server -->
</div>
<div class="span12">
<h2 id='TOC'><img src="../images/redarrow.gif" />Incubation Policy: Table of Contents</h2>
<div class="section-content">
<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>
</div>
<h2 id='Incubation+Policy'><img src="../images/redarrow.gif" />Incubation Policy
</h2>
<div class="section-content">
<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>
<h3 id='About+this+Document'>About this Document
</h3>
<div class="section-content">
<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>
<h4 id='Scope'>Scope
</h4>
<div class="section-content">
<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>
<h4 id='Relationship+to+Other+Documents'>Relationship to Other Documents
</h4>
<div class="section-content">
<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>
</div>
<h3 id='Changing+this+Document'>Changing this Document
</h3>
<div class="section-content">
<p>The contents of this document are formally approved by the Incubator
PMC. All changes must be authorised by the Incubator PMC.
</p>
</div>
<h3 id='Objectives+of+the+Process'>Objectives of the Process
</h3>
<div class="section-content">
<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>
</div>
<h3 id='Overview+of+the+Process'>Overview of the Process
</h3>
<div class="section-content">
<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>
</div>
</div>
<h2 id='Entry+to+Incubation'><img src="../images/redarrow.gif" />Entry to Incubation
</h2>
<div class="section-content">
<p>Please read the <a href="../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>
<h3 id='Proposal'>Proposal
</h3>
<div class="section-content">
<p>To start the approval process, a proposal MUST be submitted to
the Sponsor. Please read the <a href="../guides/proposal.html">Guide For Proposals</a>.
</p>
</div>
<h3 id='Approval+of+Proposal+by+Sponsor'>Approval of Proposal by Sponsor
</h3>
<div class="section-content">
<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>
</div>
<h3 id='Acceptance+By+Incubator'>Acceptance By Incubator</h3>
<div class="section-content">
<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>
<h4 id='Acceptance+of+Mentors'>Acceptance of Mentors</h4>
<div class="section-content">
<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>
</div>
</div>
<h3 id='Creation+of+Podling'>Creation of Podling
</h3>
<div class="section-content">
<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>
</div>
<h2 id='Incubation+Activities'><img src="../images/redarrow.gif" />Incubation Activities
</h2>
<div class="section-content">
<p>The following sections detail the minimum activities that must be
undertaken by the various parties during an Incuabation process.
</p>
<h3 id='Setting+Up+a+New+Podling'>Setting Up a New Podling</h3>
<div class="section-content">
<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="../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="../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>
</div>
<h3 id='Ongoing+Activities'>Ongoing Activities</h3>
<div class="section-content">
<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>
</div>
<h3 id='Review+of+Activity'>Review of Activity
</h3>
<div class="section-content">
<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>
</div>
<h3 id='Disputing+an+Assessment'>Disputing an Assessment
</h3>
<div class="section-content">
<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>
</div>
<h3 id='Continuation'>Continuation
</h3>
<div class="section-content">
<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>
</div>
<h2 id='Podling+Constraints'><img src="../images/redarrow.gif" />Podling Constraints
</h2>
<div class="section-content">
<p>While in Incubation, Podlings are constrained in the actions they can
undertake.
</p>
<h3 id='Branding'>Branding</h3>
<div class="section-content">
<p>Please consult the guide to <a href="../guides/branding.html">Podling Branding</a>.</p>
</div>
<h3 id='Releases'>Releases</h3>
<div class="section-content">
<p>
See the guidelines for <a href="../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>
<h4 id='2013+Alternate+Release+Voting+Process'>
2013 Alternate Release Voting Process
</h4>
<div class="section-content">
<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="../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>
</div>
</div>
<h3 id='Use+of+Apache+Resources'>Use of Apache Resources
</h3>
<div class="section-content">
<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>
<h4 id='Website'>Website</h4>
<div class="section-content">
<p>Please consult the guide to <a href="../guides/sites.html">Podling Websites</a> for the current policies for websites.</p>
</div>
</div>
</div>
<h2 id='Graduating+from+the+Incubator'><img src="../images/redarrow.gif" />Graduating from the Incubator
</h2>
<div class="section-content">
<p>This section describes the requirements and process for graduating from the
Incubator.
</p>
<h3 id='Minimum+Graduation+Requirements'>Minimum Graduation Requirements
</h3>
<div class="section-content">
<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>
</div>
<h3 id='Termination+of+a+Podling'>Termination of a Podling
</h3>
<div class="section-content">
<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>
</div>
<h3 id='Graduation+as+a+Top+Level+Project'>Graduation as a Top Level Project
</h3>
<div class="section-content">
<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>
</div>
<h3 id='Graduation+as+a+sub-project'>Graduation as a sub-project
</h3>
<div class="section-content">
<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>
</div>
<h3 id='Post-Graduation+Check+List'>Post-Graduation Check List
</h3>
<div class="section-content">
<p>See <a href="../guides/graduation.html">Graduation Guide</a>.
</p>
</div>
</div>
<h2 id='Roles+in+the+Incubation+Process'><img src="../images/redarrow.gif" />Roles Defined
</h2>
<div class="section-content">
<p>Definitions of the roles involved in the Incubation process.
</p>
<h3 id='Incubator+Project+Management+Committee+%28PMC%29'>Incubator Project Management Committee (PMC)
</h3>
<div class="section-content">
<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>
</div>
<h3 id='Chair+of+the+Incubator+PMC'>Chair of the Incubator PMC
</h3>
<div class="section-content">
<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>
<h3 id='Candidate'>Candidate
</h3>
<div class="section-content">
<p>A proposal for incubation. Described in detail
<a href="Roles_and_Responsibilities.html#Candidate">here</a>.
</p>
</div>
<h3 id='Champion'>Champion</h3>
<div class="section-content">
<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>
</div>
<h3 id='Sponsor'>Sponsor
</h3>
<div class="section-content">
<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="../incubation/Roles_and_Responsibilities.html#Sponsor">here</a>.
</p>
</div>
<h3 id='Mentor'>Mentor
</h3>
<div class="section-content">
<p>A Podling has one or more Mentors, one of which MUST be an Apache Member.
Mentors are chosen by the Sponsor to actively monitor 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>
</div>
<h3 id='Committers'>Committers
</h3>
<div class="section-content">
<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>
</div>
</div>
</div>
</div>
<div class="row"><div class="span16"><hr noshade="noshade" size="1"/></div></div>
<div class="row">
<div class="span16 footer">
Copyright &#169; 2009-2016 The Apache Software Foundation<br />
Licensed under the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.<br/>
Apache Incubator, Apache, the Apache feather logo, and the Apache Incubator project logo are trademarks of The Apache Software Foundation.
</div>
</div>
</div>
</body>
</html>