incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cross...@apache.org
Subject svn commit: r373695 [5/41] - in /incubator/public/trunk/site-publish: ./ guides/ images/ incubation/ ip-clearance/ learn/ projects/ projects/agila/ projects/geronimo/ style/
Date Tue, 31 Jan 2006 04:09:12 GMT
Modified: incubator/public/trunk/site-publish/incubation/Process_Description.html
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site-publish/incubation/Process_Description.html?rev=373695&r1=373694&r2=373695&view=diff
==============================================================================
--- incubator/public/trunk/site-publish/incubation/Process_Description.html (original)
+++ incubator/public/trunk/site-publish/incubation/Process_Description.html Mon Jan 30 20:07:31 2006
@@ -1,309 +1,422 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+               "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<!--
+Copyright 1999-2005 The Apache Software Foundation
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.
+-->
 <html>
-<head>
-<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<meta content="Apache Forrest" name="Generator">
-<meta name="Forrest-version" content="0.7">
-<meta name="Forrest-skin-name" content="pelt">
-<meta name="generator" content="">
-<meta name="" content="">
-<title>Process Description</title>
-<link type="text/css" href="../skin/basic.css" rel="stylesheet">
-<link media="screen" type="text/css" href="../skin/screen.css" rel="stylesheet">
-<link media="print" type="text/css" href="../skin/print.css" rel="stylesheet">
-<link type="text/css" href="../skin/profile.css" rel="stylesheet">
-<script src="../skin/getBlank.js" language="javascript" type="text/javascript"></script><script src="../skin/getMenu.js" language="javascript" type="text/javascript"></script><script src="../skin/fontsize.js" language="javascript" type="text/javascript"></script>
-<link rel="shortcut icon" href="../">
-</head>
-<body onload="init()">
-<script type="text/javascript">ndeSetTextSize();</script>
-<div id="top">
-<!--+
-    |breadtrail
-    +-->
-<div class="breadtrail">
-<a href="http://www.apache.org/">apache</a> &gt; <a href="http://incubator.apache.org/">incubator</a><script src="../skin/breadcrumbs.js" language="JavaScript" type="text/javascript"></script>
-</div>
-<!--+
-    |header
-    +-->
-<div class="header">
-<!--+
-    |start group logo
-    +-->
-<div class="grouplogo">
-<a href="http://www.apache.org/"><img class="logoImage" alt="The Apache Software Foundation" src="../images/apache-asf-compressed.png"></a>
-</div>
-<!--+
-    |end group logo
-    +-->
-<!--+
-    |start Project Logo
-    +-->
-<div class="projectlogo">
-<a href="http://incubator.apache.org/"><img class="logoImage" alt="Apache Incubator" src="../images/apache-incubator-logo.png" title="Apache Incubator"></a>
-</div>
-<!--+
-    |end Project Logo
-    +-->
-<!--+
-    |start Search
-    +-->
-<div class="searchbox">
-<form action="http://www.google.com/search" method="get" class="roundtopsmall">
-<input value="incubator.apache.org" name="sitesearch" type="hidden"><input onFocus="getBlank (this, 'Search the site with google');" size="25" name="q" id="query" type="text" value="Search the site with google">&nbsp; 
-                    <input attr="value" name="Search" value="Search" type="submit">
-</form>
-</div>
-<!--+
-    |end search
-    +-->
-<!--+
-    |start Tabs
-    +-->
-<ul id="tabs">
-<li class="current">
-<a class="base-selected" href=".././index.html">Home</a>
-</li>
-<li>
-<a class="base-not-selected" href="../projects/index.html">Projects</a>
-</li>
-<li>
-<a class="base-not-selected" href="../learn/index.html">Learn</a>
-</li>
-<li>
-<a class="base-not-selected" href="http://wiki.apache.org/incubator/">Whiteboard</a>
-</li>
-</ul>
-<!--+
-    |end Tabs
-    +-->
-</div>
-</div>
-<div id="main">
-<div id="publishedStrip">
-<!--+
-    |start Subtabs
-    +-->
-<div id="level2tabs"></div>
-<!--+
-    |end Endtabs
-    +-->
-<script type="text/javascript"><!--
-document.write("<text>Last Published:</text> " + document.lastModified);
-//  --></script>
-</div>
-<!--+
-    |breadtrail
-    +-->
-<div class="breadtrail">
-             
-             &nbsp;
-           </div>
-<!--+
-    |start Menu, mainarea
-    +-->
-<!--+
-    |start Menu
-    +-->
-<div id="menu">
-<div onclick="SwitchMenu('menu_1.1', '../skin/')" id="menu_1.1Title" class="menutitle">About</div>
-<div id="menu_1.1" class="menuitemgroup">
-<div class="menuitem">
-<a href="../index.html">Index</a>
-</div>
-<div class="menuitem">
-<a href="../resolution.html">What we do</a>
-</div>
-<div class="menuitem">
-<a href="../howwework.html">How we work</a>
-</div>
-<div class="menuitem">
-<a href="../whoweare.html">Who we are</a>
-</div>
-<div class="menuitem">
-<a href="../howtoparticipate.html">How to participate</a>
-</div>
-<div class="menuitem">
-<a href="../faq.html">FAQ</a>
-</div>
-<div class="menuitem">
-<a href="../ip-clearance/index.html">IP Clearance</a>
-</div>
-</div>
-<div onclick="SwitchMenu('menu_selected_1.2', '../skin/')" id="menu_selected_1.2Title" class="menutitle" style="background-image: url('../skin/images/chapter_open.gif');">Incubation</div>
-<div id="menu_selected_1.2" class="selectedmenuitemgroup" style="display: block;">
-<div class="menuitem">
-<a href="../incubation/Incubation_Policy.html">Incubation Policy</a>
-</div>
-<div class="menupage">
-<div class="menupagetitle">Process Description</div>
-</div>
-<div class="menuitem">
-<a href="../incubation/Roles_and_Responsibilities.html">Roles and Responsibilities</a>
-</div>
-<div class="menuitem">
-<a href="http://www.apache.org/licenses/">Licensing</a>
-</div>
-</div>
-<div onclick="SwitchMenu('menu_1.3', '../skin/')" id="menu_1.3Title" class="menutitle">Guides</div>
-<div id="menu_1.3" class="menuitemgroup">
-<div class="menuitem">
-<a href="../guides/general.html">General</a>
-</div>
-<div class="menuitem">
-<a href="../guides/committer.html">Committers</a>
-</div>
-<div class="menuitem">
-<a href="../guides/chair.html">Chair</a>
-</div>
-<div class="menuitem">
-<a href="../guides/pmc.html">PMC</a>
-</div>
-<div class="menuitem">
-<a href="../guides/projects.html">Projects and Mentors</a>
-</div>
-<div class="menuitem">
-<a href="../guides/website.html">Updating the website</a>
-</div>
-</div>
-<div id="credit"></div>
-<div id="roundbottom">
-<img style="display: none" class="corner" height="15" width="15" alt="" src="../skin/images/rc-b-l-15-1body-2menu-3menu.png"></div>
-<!--+
-  |alternative credits
-  +-->
-<div id="credit2"></div>
-</div>
-<!--+
-    |end Menu
-    +-->
-<!--+
-    |start content
-    +-->
-<div id="content">
-<script language="Javascript" type="text/javascript">
-function printit() {
-  if (window.print) {
-    window.focus();
-    window.print();
-  }
-}
-        </script><script language="Javascript" type="text/javascript">
-var NS = (navigator.appName == "Netscape");
-var VERSION = parseInt(navigator.appVersion);
-if (VERSION > 3) {
-  document.write('<div title="Print this Page" class="printlink">');
-  document.write('  <a class="dida" href="javascript:printit()">');
-  document.write('    <img alt="print - icon" src="../skin/images/printer.gif" class="skin">');
-  document.write('    <br>');
-  document.write('  PRINT</a>');
-  document.write('</div>');
-}
-        </script>
-<div title="Portable Document Format" class="pdflink">
-<a class="dida" href="Process_Description.pdf"><img alt="PDF -icon" src="../skin/images/pdfdoc.gif" class="skin"><br>
-        PDF</a>
-</div>
-<div class="trail">
-<text>Font size:</text> 
-	          &nbsp;<input value="Reset" class="resetfont" title="Reset text" onclick="ndeSetTextSize('reset'); return false;" type="button">      
-	          &nbsp;<input value="-a" class="smallerfont" title="Shrink text" onclick="ndeSetTextSize('decr'); return false;" type="button">
-	          &nbsp;<input value="+a" class="biggerfont" title="Enlarge text" onclick="ndeSetTextSize('incr'); return false;" type="button">
-</div>
-<h1>Process Description</h1>
-<div id="minitoc-area">
-<ul class="minitoc">
-<li>
-<a href="#The+Process+of+Incubation">The Process of Incubation</a>
-<ul class="minitoc">
-<li>
-<a href="#Establishment">Establishment</a>
-</li>
-<li>
-<a href="#Acceptance">Acceptance</a>
-</li>
-<li>
-<a href="#Review">Review</a>
-</li>
-<li>
-<a href="#Termination">Termination</a>
-</li>
-<li>
-<a href="#Continuation">Continuation</a>
+ <head>
+  <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+  <link rel="stylesheet" href="/style/style.css" type="text/css" />
+      <title>Process Description
+ - Apache Incubator</title>
+ </head>
+ <body>        
+  <table border="0" width="100%" cellspacing="0">
+   <tr><!-- SITE BANNER AND PROJECT IMAGE -->
+    <td align="left" valign="top">
+<a href="http://www.apache.org/"><img src="/images/asf_logo_wide.gif" alt="The Apache Software Foundation" border="0"/></a>
+</td>
+<td align="right">
+<a href="http://incubator.apache.org/"><img src="../images/apache-incubator-logo.png" alt="Apache Incubator" border="0"/></a>
+</td>
+   </tr>
+  </table>
+  <table border="0" width="100%" cellspacing="4">
+   <tr><td colspan="3"><hr noshade="noshade" size="1"/></td></tr>
+   <tr>
+    <!-- LEFT SIDE NAVIGATION -->
+    <td valign="top" nowrap="nowrap" class="navleft">
+     
+
+
+      <div class="menuheader">General</div>
+    <menu compact="compact">
+          <li><a href="/index.html">Home</a></li> 
+          <li><a href="http://www.apache.org/">ASF</a></li> 
+          <li><a href="http://www.apache.org/licenses/">Licensing</a></li> 
+          <li><a href="/resolution.html">What We Do</a></li> 
+          <li><a href="/howwework.html">How We Work</a></li> 
+          <li><a href="/whoweare.html">Who We Are</a></li> 
+          <li><a href="/howtoparticipate.html">How To Participate</a></li> 
+          <li><a href="/faq.html">FAQ</a></li> 
+          <li><a href="/mailing.html">Mailing Lists</a></li> 
+          <li><a href="http://wiki.apache.org/incubator">Wiki</a></li> 
+        </menu>
+
+
+
+      <div class="menuheader">Incubation</div>
+    <menu compact="compact">
+          <li><a href="/projects/index.html">Projects</a></li> 
+          <li><a href="/ip-clearance/index.html">IP Clearance</a></li> 
+          <li><a href="/incubation/Incubation_Policy.html">Incubation Policy</a></li> 
+          <li><a href="/incubation/Process_Description.html">Process Description</a></li> 
+          <li><a href="/incubation/Roles_and_Responsibilities.html">Roles/Responsibilies</a></li> 
+        </menu>
+
+
+
+      <div class="menuheader">Guides</div>
+    <menu compact="compact">
+          <li><a href="/guides/general.html">General</a></li> 
+          <li><a href="/guides/committer.html">Committers</a></li> 
+          <li><a href="/guides/chair.html">Chair</a></li> 
+          <li><a href="/guides/pmc.html">PMC</a></li> 
+          <li><a href="/guides/projects.html">Projects and Mentors</a></li> 
+          <li><a href="/guides/website.html">Updating the Website</a></li> 
+        </menu>
+    </td>
+    <!-- CONTENT -->
+    <td align="left" valign="top" class="content">
+                <h2><img src="/images/redarrow.gif" />
+   <a name="The+Process+of+Incubation">The Process of Incubation
+</a>
+</h2>
+<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-process.png" />
+      </p>
+<p>Readers should also review the
+
+        <a href="../incubation/Roles_and_Responsibilities.html">Roles and Responsibilities
+</a>document for a description of the various parties involved in the
+Incubation process.
+
+      </p>
+<h3>
+   <a name="Establishment">Establishment
+</a>
+</h3>
+<div class="section-content">
+
+
+
+
+
+
+<p>The first thing you will want to do is find a
+
+          <strong>Champion
+</strong>for your project. One way to do this is to explore the existing
+
+          <a href="http://www.apache.org/foundation/projects.html">Apache projects
+</a>to find similar projects. Spend some time reading their project web
+pages and mailing lists (follow links at each project website). By
+simply lurking on the project mailing lists (and also the
+
+          <a href="../howtoparticipate.html">general@incubator list
+</a>and other Incubating project lists) you may get ideas about who you
+would like to ask to help you with your project proposal.
+
+        </p>
+<p>However, Champions must either be ASF
+
+          <a href="http://www.apache.org/foundation/members.html">members
+</a>or
+
+          <a href="http://www.apache.org/foundation/index.html">officers
+</a>(see the Champion section later in this document for more on Champion
+criteria and responsibilities). Once you have found an eligible
+person who is willing to act as Champion, you can use this person to
+help you determine if and how your proposal can complement the ASF.
+If you and your Champion are convinced that your candidate project
+would fit with the "Apache Way", your Champion can help you to get it
+established.
+
+        </p>
+<p>The establishment of a candidate involves the preparation of a
+project description (consistent with the candidate description
+detailed below) endorsed by a
+
+          <strong>Champion
+</strong>.
+
+        </p>
+<p>A
+
+          <strong>Candidate
+</strong>project description should be submitted to the relevant mailing
+list(s) of a
+
+          <strong>Sponsor
+</strong>(see the
+
+          <a href="../howtoparticipate.html">Mailing Lists
+</a>section). See the
+
+          <a href="http://jakarta.apache.org/site/newproject.html">Jakarta Guidelines for New Projects
+</a>for a list of issues that should be addressed in your proposal; also
+see
+
+          <a href="http://nagoya.apache.org/wiki/apachewiki.cgi?ASFProposalPages">ASF Proposal Pages
+</a>for other examples. Typically a
+
+          <strong>Candidate
+</strong>is submitted under a message tagged with [[PROPOSAL]. Such a message
+will normally trigger some discussions on the receiving mailing
+list(s). Your Champion will be involved in these discussions acting
+as your advocate.
+
+        </p>
+<p>As a proposer you should consider the feedback and attempt to gauge a
+sense of consensus. Do not be put off by extended threads under your
+initial post that have little or nothing to do with your proposal -
+however, if you feel that your candidate project is not being
+addressed, you may want to specifically request a decision on the
+Candidate by the Sponsor by posting a request to the decision making
+list (usually pmc@project-name.apache.org - see
+
+          <a href="../howtoparticipate.html">Mailing Lists
+</a>section for more details). Sometimes a vote will be announced without
+you asking for it (perhaps you have done some homework and have a PMC
+member assisting you though the process), other times you may need to
+cut through discussions and push your request forward for a decision.
+
+        </p>
+</div>
+<h3>
+   <a name="Acceptance">Acceptance
+</a>
+</h3>
+<div class="section-content">
+
+
+
+
+
+
+<p>The decision to accept a project is taken on a vote by the Sponsor.
+The format of this vote will depend on the rules of the entity in
+question. Here again it helps if you have a PMC Member (or board
+member if the Sponsor is the ASF board) aligned with your project
+(preferably as your Champion) because you stand a better chance of
+getting feedback about what is actually happening. The Sponsor will
+typically take about 7-10 days before announcing a vote result.
+</p>
+<p>If that vote is affirmative, the Sponsor will propose to the
+
+          <strong>Incubator PMC
+</strong>(referencing the voting result e-mail) that your candidate project be
+escalated to
+
+          <strong>Podling
+</strong>status. The Sponsor will assign a
+
+          <strong>Mentor
+</strong>. The Mentor may, or may not, be your original Champion. If not, it
+is expected your Champion will remain involved during the rest of the
+Incubation process, providing as much assistance as possible.
+
+        </p>
+<p>The Mentor is there to protect you, but be warned - the Mentor is
+also holding a big stick. The Mentor is automatically made a member
+of the Incubator PMC, and reports to both the PMC and the Sponsor
+about your overall health and suitability for eventual inclusion
+within the Apache Community (or recommendation to terminate).
+However, the Mentor (with the assistance of the Champion) is also
+looking after you through the incubation.
+</p>
+<p>One of the roles of the Mentor is to keep away the wolves - and in
+the case of incubation the wolf is the Incubator PMC, the policies,
+the process, and inevitable bureaucracy and delays. The Mentor can
+help you by guiding and protecting you from much of this based on
+his/her experience in the process and familiarity with the policy and
+procedures of incubation. In performing their role, the Mentor is
+representing the Sponsor.
+</p>
+<p>Your Sponsor, represented by your Mentor, has specific
+responsibilities towards you and the Incubator PMC. There are a bunch
+of administrative and technical actions to take care of. Your Mentor
+is responsible for ensuring that these things happen quickly and
+efficiently. Also, your Mentor is going to help you out with the
+getting in place of the policies and procedures you use for
+introducing new comitters, decision making, etc. These aspects will
+be watched closely by the Incubator PMC as they provide a good
+indication of community dynamics, health and correlation with Apache
+practices.
+</p>
+</div>
+<h3>
+   <a name="Review">Review
+</a>
+</h3>
+<div class="section-content">
+
+
+
+
+
+
+<p>As your project sorts things out and things stabilize
+(infrastructure, communications, decision making) you will inevitably
+come under an assessment by the Incubator PMC concerning the exit of
+your project from the incubator. Keep in mind that exit can be a good
+things and bad thing. Exit via escalation to a top-level project or
+perhaps a subproject of an existing PMC would typically be viewed as
+a positive exit. On the other-hand, termination is also an exit
+condition that may be considered. With an upcoming assessment it is
+generally a good idea to have your STATUS file right up to-date and
+to ensure that your Mentor is doing his/her job of evangelizing your
+project and has good picture of where you are relative to acceptance
+or the last assessment point. This information will help the
+Incubator PMC to recommend the best action for for your project.
+</p>
+<p>Conclusion of a review process will be a recommendation (to the
+Sponsor) of one of the following:
+</p>
+<ul>
+          <li>termination;
 </li>
-<li>
-<a href="#Escalation">Escalation</a>
+          <li>continuation under incubation with recommendations; or
 </li>
-</ul>
+          <li>exit via escalation into Apache.
 </li>
-</ul>
-</div>
-<a name="N10010"></a><a name="The+Process+of+Incubation"></a>
-<h2 class="underlined_10">The Process of Incubation</h2>
-<div class="section">
-<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-process.png"></p>
-<p>Readers should also review the <a href="../incubation/Roles_and_Responsibilities.html">Roles and Responsibilities</a> document for a description of the various parties involved in the Incubation process.</p>
-<a name="N10020"></a><a name="Establishment"></a>
-<h3 class="underlined_5">Establishment</h3>
-<p>The first thing you will want to do is find a <strong>Champion</strong> for your project. One way to do this is to explore the existing <a href="http://www.apache.org/foundation/projects.html">Apache projects</a> to find similar projects. Spend some time reading their project web pages and mailing lists (follow links at each project website). By simply lurking on the project mailing lists (and also the <a href="../howtoparticipate.html">general@incubator list</a> and other Incubating project lists) you may get ideas about who you would like to ask to help you with your project proposal.</p>
-<p>However, Champions must either be ASF <a href="http://www.apache.org/foundation/members.html">members</a> or <a href="http://www.apache.org/foundation/index.html">officers</a> (see the Champion section later in this document for more on Champion criteria and responsibilities). Once you have found an eligible person who is willing to act as Champion, you can use this person to help you determine if and how your proposal can complement the ASF. If you and your Champion are convinced that your candidate project would fit with the "Apache Way", your Champion can help you to get it established.</p>
-<p>The establishment of a candidate involves the preparation of a project description (consistent with the candidate description detailed below) endorsed by a <strong>Champion</strong> .</p>
-<p>A <strong>Candidate</strong> project description should be submitted to the relevant mailing list(s) of a <strong>Sponsor</strong> (see the <a href="../howtoparticipate.html">Mailing Lists</a> section). See the <a href="http://jakarta.apache.org/site/newproject.html">Jakarta Guidelines for New Projects</a> for a list of issues that should be addressed in your proposal; also see <a href="http://nagoya.apache.org/wiki/apachewiki.cgi?ASFProposalPages">ASF Proposal Pages</a> for other examples. Typically a <strong>Candidate</strong> is submitted under a message tagged with [[PROPOSAL]. Such a message will normally trigger some discussions on the receiving mailing list(s). Your Champion will be involved in these discussions acting as your advocate.</p>
-<p>As a proposer you should consider the feedback and attempt to gauge a sense of consensus. Do not be put off by extended threads under your initial post that have little or nothing to do with your proposal - however, if you feel that your candidate project is not being addressed, you may want to specifically request a decision on the Candidate by the Sponsor by posting a request to the decision making list (usually pmc@project-name.apache.org - see <a href="../howtoparticipate.html">Mailing Lists</a> section for more details). Sometimes a vote will be announced without you asking for it (perhaps you have done some homework and have a PMC member assisting you though the process), other times you may need to cut through discussions and push your request forward for a decision.</p>
-<a name="N1005D"></a><a name="Acceptance"></a>
-<h3 class="underlined_5">Acceptance</h3>
-<p>The decision to accept a project is taken on a vote by the Sponsor. The format of this vote will depend on the rules of the entity in question. Here again it helps if you have a PMC Member (or board member if the Sponsor is the ASF board) aligned with your project (preferably as your Champion) because you stand a better chance of getting feedback about what is actually happening. The Sponsor will typically take about 7-10 days before announcing a vote result.</p>
-<p>If that vote is affirmative, the Sponsor will propose to the <strong>Incubator PMC</strong> (referencing the voting result e-mail) that your candidate project be escalated to <strong>Podling</strong> status. The Sponsor will assign a <strong>Mentor</strong> . The Mentor may, or may not, be your original Champion. If not, it is expected your Champion will remain involved during the rest of the Incubation process, providing as much assistance as possible.</p>
-<p>The Mentor is there to protect you, but be warned - the Mentor is also holding a big stick. The Mentor is automatically made a member of the Incubator PMC, and reports to both the PMC and the Sponsor about your overall health and suitability for eventual inclusion within the Apache Community (or recommendation to terminate). However, the Mentor (with the assistance of the Champion) is also looking after you through the incubation.</p>
-<p>One of the roles of the Mentor is to keep away the wolves - and in the case of incubation the wolf is the Incubator PMC, the policies, the process, and inevitable bureaucracy and delays. The Mentor can help you by guiding and protecting you from much of this based on his/her experience in the process and familiarity with the policy and procedures of incubation. In performing their role, the Mentor is representing the Sponsor.</p>
-<p>Your Sponsor, represented by your Mentor, has specific responsibilities towards you and the Incubator PMC. There are a bunch of administrative and technical actions to take care of. Your Mentor is responsible for ensuring that these things happen quickly and efficiently. Also, your Mentor is going to help you out with the getting in place of the policies and procedures you use for introducing new comitters, decision making, etc. These aspects will be watched closely by the Incubator PMC as they provide a good indication of community dynamics, health and correlation with Apache practices.</p>
-<a name="N10074"></a><a name="Review"></a>
-<h3 class="underlined_5">Review</h3>
-<p>As your project sorts things out and things stabilize (infrastructure, communications, decision making) you will inevitably come under an assessment by the Incubator PMC concerning the exit of your project from the incubator. Keep in mind that exit can be a good things and bad thing. Exit via escalation to a top-level project or perhaps a subproject of an existing PMC would typically be viewed as a positive exit. On the other-hand, termination is also an exit condition that may be considered. With an upcoming assessment it is generally a good idea to have your STATUS file right up to-date and to ensure that your Mentor is doing his/her job of evangelizing your project and has good picture of where you are relative to acceptance or the last assessment point. This information will help the Incubator PMC to recommend the best action for for your project.</p>
-<p>Conclusion of a review process will be a recommendation (to the Sponsor) of one of the following:</p>
-<ul>
-<li>termination;</li>
-<li>continuation under incubation with recommendations; or</li>
-<li>exit via escalation into Apache.</li>
-</ul>
-<p>Note that whilst this is a recommendation, it carries a lot of weight. A Sponsor will only over-ride the recommendation of the Incubator in exceptional circumstances, and even then it is likely that the issue in question would be escalated to the ASF board for their consideration.</p>
-<a name="N10085"></a><a name="Termination"></a>
-<h3 class="underlined_5">Termination</h3>
-<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>
-<a name="N1008B"></a><a name="Continuation"></a>
-<h3 class="underlined_5">Continuation</h3>
-<p>A recommendation by the Incubator PMC for continuation of incubation shall include development recommendations. The Incubator PMC has a responsibility to ensure that the recommended actions are tangible and quantifiable. For example, an assessment could be that your project has not established a sufficient community to be viable, in which case the Incubator PMC is obliged to state specific targets that they consider as viable. This does not necessarily mean that if you meet this target by the next review that you are out of incubation - but it does give you concrete achievements that you can cite. Your Mentor is also specifically accountable to you for ensuring that the recommendations for continuation are usable, substantive and tangible. If this is not the case, you have every right to appeal an Incubator decision to the Apache Board. However, if your Mentor is doing a good job, neither of these scenarios should arise.</p>
-<a name="N10091"></a><a name="Escalation"></a>
-<h3 class="underlined_5">Escalation</h3>
-<p>For Podlings that aim to establish sub-projects or products within existing communities you are almost home-free. The main issues you need to deal with now is migration of your code into the target project, something you should be confident in doing based on the contacts and understanding you gained during initial establishment and incubation.</p>
-<p>For projects aiming to be a Top-Level-Project (TLP), you have an additional obstacle, namely the ASF Board. While the ASF Board might be your Sponsor, this does not mean they have formally accepted you as a TLP. To establish a TLP you need to draft a board motion that identifies the project scope, mission and charter. You can submit the motion to the Board using the board@apache.org email address. Well-prepared projects will have already developed contacts with members of the Board so this should not be a surprise agenda item. Keep in mind that the Board can approve your motion as supplied, amend it, or reject it. If you are rejected then you need to sort this out with the Incubator PMC and allies you have developed during the incubation process. In other words, for a TLP objective the Incubator PMC okay is only half of the story.</p>
-<p>However, in practice, assuming you are building contacts with members in Apache, the Incubator PMC, and the ASF Board, the transition from Podling to TLP should be a smooth and painless process.</p>
-</div>
-</div>
-<!--+
-    |end content
-    +-->
-<div class="clearboth">&nbsp;</div>
-</div>
-<div id="footer">
-<!--+
-    |start bottomstrip
-    +-->
-<div class="lastmodified">
-<script type="text/javascript"><!--
-document.write("<text>Last Published:</text> " + document.lastModified);
-//  --></script>
-</div>
-<div class="copyright">
-        Copyright &copy;
-         2002-2005 <a href="http://www.apache.org/licenses/">The Apache Software Foundation.</a>
-</div>
-<!--+
-    |end bottomstrip
-    +-->
-</div>
-</body>
+        </ul>
+<p>Note that whilst this is a recommendation, it carries a lot of
+weight. A Sponsor will only over-ride the recommendation of the
+Incubator in exceptional circumstances, and even then it is likely
+that the issue in question would be escalated to the ASF board for
+their consideration.
+</p>
+</div>
+<h3>
+   <a name="Termination">Termination
+</a>
+</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>
+   <a name="Continuation">Continuation
+</a>
+</h3>
+<div class="section-content">
+
+
+
+
+
+
+<p>A recommendation by the Incubator PMC for continuation of incubation
+shall include development recommendations. The Incubator PMC has a
+responsibility to ensure that the recommended actions are tangible
+and quantifiable. For example, an assessment could be that your
+project has not established a sufficient community to be viable, in
+which case the Incubator PMC is obliged to state specific targets
+that they consider as viable. This does not necessarily mean that if
+you meet this target by the next review that you are out of
+incubation - but it does give you concrete achievements that you can
+cite. Your Mentor is also specifically accountable to you for
+ensuring that the recommendations for continuation are usable,
+substantive and tangible. If this is not the case, you have every
+right to appeal an Incubator decision to the Apache Board. However,
+if your Mentor is doing a good job, neither of these scenarios should
+arise.
+</p>
+</div>
+<h3>
+   <a name="Escalation">Escalation
+</a>
+</h3>
+<div class="section-content">
+
+
+
+
+
+
+<p>For Podlings that aim to establish sub-projects or products within
+existing communities you are almost home-free. The main issues you
+need to deal with now is migration of your code into the target
+project, something you should be confident in doing based on the
+contacts and understanding you gained during initial establishment
+and incubation.
+</p>
+<p>For projects aiming to be a Top-Level-Project (TLP), you have an
+additional obstacle, namely the ASF Board. While the ASF Board might
+be your Sponsor, this does not mean they have formally accepted you
+as a TLP. To establish a TLP you need to draft a board motion that
+identifies the project scope, mission and charter. You can submit the
+motion to the Board using the board@apache.org email address.
+Well-prepared projects will have already developed contacts with
+members of the Board so this should not be a surprise agenda item.
+Keep in mind that the Board can approve your motion as supplied,
+amend it, or reject it. If you are rejected then you need to sort
+this out with the Incubator PMC and allies you have developed during
+the incubation process. In other words, for a TLP objective the
+Incubator PMC okay is only half of the story.
+</p>
+<p>However, in practice, assuming you are building contacts with members
+in Apache, the Incubator PMC, and the ASF Board, the transition from
+Podling to TLP should be a smooth and painless process.
+</p>
+</div>
+</div>
+         </td>
+    <!-- RIGHT SIDE NAVIGATION -->
+    <td valign="top" nowrap="nowrap" class="navright">
+     
+
+
+      <div class="menuheader"><a 
+href="http://www.apache.org/foundation/">Foundation</a></div>
+    <menu compact="compact">
+        </menu>
+
+     <div class="menuheader">Search apache.org</div>
+     <form action="http://search.apache.org/" method="post">
+    <p><input type="text" name="query" size="10" />
+    <input type="submit" value="Go" /></p>
+</form>
+
+    </td>     
+   </tr>
+   <!-- FOOTER -->
+   <tr><td colspan="3"><hr noshade="noshade" size="1"/></td></tr>
+   <tr><td colspan="3" class="footer">
+         Copyright &#169; 1999-2005, The Apache Software Foundation<br />
+Licensed under the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+       </td>
+   </tr>
+  </table>
+ </body>
 </html>

Modified: incubator/public/trunk/site-publish/incubation/Roles_and_Responsibilities.html
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site-publish/incubation/Roles_and_Responsibilities.html?rev=373695&r1=373694&r2=373695&view=diff
==============================================================================
--- incubator/public/trunk/site-publish/incubation/Roles_and_Responsibilities.html (original)
+++ incubator/public/trunk/site-publish/incubation/Roles_and_Responsibilities.html Mon Jan 30 20:07:31 2006
@@ -1,382 +1,503 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+               "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<!--
+Copyright 1999-2005 The Apache Software Foundation
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.
+-->
 <html>
-<head>
-<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<meta content="Apache Forrest" name="Generator">
-<meta name="Forrest-version" content="0.7">
-<meta name="Forrest-skin-name" content="pelt">
-<meta name="generator" content="">
-<meta name="" content="">
-<title>Roles_and_ Responsibilities</title>
-<link type="text/css" href="../skin/basic.css" rel="stylesheet">
-<link media="screen" type="text/css" href="../skin/screen.css" rel="stylesheet">
-<link media="print" type="text/css" href="../skin/print.css" rel="stylesheet">
-<link type="text/css" href="../skin/profile.css" rel="stylesheet">
-<script src="../skin/getBlank.js" language="javascript" type="text/javascript"></script><script src="../skin/getMenu.js" language="javascript" type="text/javascript"></script><script src="../skin/fontsize.js" language="javascript" type="text/javascript"></script>
-<link rel="shortcut icon" href="../">
-</head>
-<body onload="init()">
-<script type="text/javascript">ndeSetTextSize();</script>
-<div id="top">
-<!--+
-    |breadtrail
-    +-->
-<div class="breadtrail">
-<a href="http://www.apache.org/">apache</a> &gt; <a href="http://incubator.apache.org/">incubator</a><script src="../skin/breadcrumbs.js" language="JavaScript" type="text/javascript"></script>
-</div>
-<!--+
-    |header
-    +-->
-<div class="header">
-<!--+
-    |start group logo
-    +-->
-<div class="grouplogo">
-<a href="http://www.apache.org/"><img class="logoImage" alt="The Apache Software Foundation" src="../images/apache-asf-compressed.png"></a>
-</div>
-<!--+
-    |end group logo
-    +-->
-<!--+
-    |start Project Logo
-    +-->
-<div class="projectlogo">
-<a href="http://incubator.apache.org/"><img class="logoImage" alt="Apache Incubator" src="../images/apache-incubator-logo.png" title="Apache Incubator"></a>
-</div>
-<!--+
-    |end Project Logo
-    +-->
-<!--+
-    |start Search
-    +-->
-<div class="searchbox">
-<form action="http://www.google.com/search" method="get" class="roundtopsmall">
-<input value="incubator.apache.org" name="sitesearch" type="hidden"><input onFocus="getBlank (this, 'Search the site with google');" size="25" name="q" id="query" type="text" value="Search the site with google">&nbsp; 
-                    <input attr="value" name="Search" value="Search" type="submit">
-</form>
-</div>
-<!--+
-    |end search
-    +-->
-<!--+
-    |start Tabs
-    +-->
-<ul id="tabs">
-<li class="current">
-<a class="base-selected" href=".././index.html">Home</a>
-</li>
-<li>
-<a class="base-not-selected" href="../projects/index.html">Projects</a>
-</li>
-<li>
-<a class="base-not-selected" href="../learn/index.html">Learn</a>
-</li>
-<li>
-<a class="base-not-selected" href="http://wiki.apache.org/incubator/">Whiteboard</a>
-</li>
-</ul>
-<!--+
-    |end Tabs
-    +-->
-</div>
-</div>
-<div id="main">
-<div id="publishedStrip">
-<!--+
-    |start Subtabs
-    +-->
-<div id="level2tabs"></div>
-<!--+
-    |end Endtabs
-    +-->
-<script type="text/javascript"><!--
-document.write("<text>Last Published:</text> " + document.lastModified);
-//  --></script>
-</div>
-<!--+
-    |breadtrail
-    +-->
-<div class="breadtrail">
-             
-             &nbsp;
-           </div>
-<!--+
-    |start Menu, mainarea
-    +-->
-<!--+
-    |start Menu
-    +-->
-<div id="menu">
-<div onclick="SwitchMenu('menu_1.1', '../skin/')" id="menu_1.1Title" class="menutitle">About</div>
-<div id="menu_1.1" class="menuitemgroup">
-<div class="menuitem">
-<a href="../index.html">Index</a>
-</div>
-<div class="menuitem">
-<a href="../resolution.html">What we do</a>
-</div>
-<div class="menuitem">
-<a href="../howwework.html">How we work</a>
-</div>
-<div class="menuitem">
-<a href="../whoweare.html">Who we are</a>
-</div>
-<div class="menuitem">
-<a href="../howtoparticipate.html">How to participate</a>
-</div>
-<div class="menuitem">
-<a href="../faq.html">FAQ</a>
-</div>
-<div class="menuitem">
-<a href="../ip-clearance/index.html">IP Clearance</a>
-</div>
-</div>
-<div onclick="SwitchMenu('menu_selected_1.2', '../skin/')" id="menu_selected_1.2Title" class="menutitle" style="background-image: url('../skin/images/chapter_open.gif');">Incubation</div>
-<div id="menu_selected_1.2" class="selectedmenuitemgroup" style="display: block;">
-<div class="menuitem">
-<a href="../incubation/Incubation_Policy.html">Incubation Policy</a>
-</div>
-<div class="menuitem">
-<a href="../incubation/Process_Description.html">Process Description</a>
-</div>
-<div class="menupage">
-<div class="menupagetitle">Roles and Responsibilities</div>
-</div>
-<div class="menuitem">
-<a href="http://www.apache.org/licenses/">Licensing</a>
-</div>
-</div>
-<div onclick="SwitchMenu('menu_1.3', '../skin/')" id="menu_1.3Title" class="menutitle">Guides</div>
-<div id="menu_1.3" class="menuitemgroup">
-<div class="menuitem">
-<a href="../guides/general.html">General</a>
-</div>
-<div class="menuitem">
-<a href="../guides/committer.html">Committers</a>
-</div>
-<div class="menuitem">
-<a href="../guides/chair.html">Chair</a>
-</div>
-<div class="menuitem">
-<a href="../guides/pmc.html">PMC</a>
-</div>
-<div class="menuitem">
-<a href="../guides/projects.html">Projects and Mentors</a>
-</div>
-<div class="menuitem">
-<a href="../guides/website.html">Updating the website</a>
-</div>
-</div>
-<div id="credit"></div>
-<div id="roundbottom">
-<img style="display: none" class="corner" height="15" width="15" alt="" src="../skin/images/rc-b-l-15-1body-2menu-3menu.png"></div>
-<!--+
-  |alternative credits
-  +-->
-<div id="credit2"></div>
-</div>
-<!--+
-    |end Menu
-    +-->
-<!--+
-    |start content
-    +-->
-<div id="content">
-<script language="Javascript" type="text/javascript">
-function printit() {
-  if (window.print) {
-    window.focus();
-    window.print();
-  }
-}
-        </script><script language="Javascript" type="text/javascript">
-var NS = (navigator.appName == "Netscape");
-var VERSION = parseInt(navigator.appVersion);
-if (VERSION > 3) {
-  document.write('<div title="Print this Page" class="printlink">');
-  document.write('  <a class="dida" href="javascript:printit()">');
-  document.write('    <img alt="print - icon" src="../skin/images/printer.gif" class="skin">');
-  document.write('    <br>');
-  document.write('  PRINT</a>');
-  document.write('</div>');
-}
-        </script>
-<div title="Portable Document Format" class="pdflink">
-<a class="dida" href="Roles_and_Responsibilities.pdf"><img alt="PDF -icon" src="../skin/images/pdfdoc.gif" class="skin"><br>
-        PDF</a>
-</div>
-<div class="trail">
-<text>Font size:</text> 
-	          &nbsp;<input value="Reset" class="resetfont" title="Reset text" onclick="ndeSetTextSize('reset'); return false;" type="button">      
-	          &nbsp;<input value="-a" class="smallerfont" title="Shrink text" onclick="ndeSetTextSize('decr'); return false;" type="button">
-	          &nbsp;<input value="+a" class="biggerfont" title="Enlarge text" onclick="ndeSetTextSize('incr'); return false;" type="button">
-</div>
-<h1>Roles_and_ Responsibilities</h1>
-<div id="minitoc-area">
-<ul class="minitoc">
-<li>
-<a href="#Roles+and+Responsibilities">Roles and Responsibilities</a>
-<ul class="minitoc">
-<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>
-<ul class="minitoc">
-<li>
-<a href="#Responsibilities+of+the+Sponsor">Responsibilities of the Sponsor</a>
-</li>
-</ul>
-</li>
-<li>
-<a href="#Mentor">Mentor</a>
-<ul class="minitoc">
-<li>
-<a href="#Responsibilities+towards+Podling+Members">Responsibilities towards Podling Members</a>
-</li>
-<li>
-<a href="#Responsibilities+towards+the+Incubator+PMC">Responsibilities towards the Incubator PMC</a>
-</li>
-<li>
-<a href="#Committers">Committers</a>
-</li>
-</ul>
-</li>
-</ul>
-</li>
-</ul>
-</div>
-<a name="N10010"></a><a name="Roles+and+Responsibilities"></a>
-<h2 class="underlined_10">Roles and Responsibilities</h2>
-<div class="section">
-<p>This document describes the roles (including Sponsor, Contributor, Mentor) and provides an overview of the responsibilities of the different parties involved in an incubation process.</p>
-<a name="N10016"></a><a name="Incubator+Project+Management+Committee+%28PMC%29"></a>
-<h3 class="underlined_5">Incubator Project Management Committee (PMC)</h3>
-<p>(From the resolution that created the Incubator Project - see http://incubator.apache.org/resolution.html)</p>
-<p>The Incubator PMC is responsible for :</p>
+ <head>
+  <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+  <link rel="stylesheet" href="/style/style.css" type="text/css" />
+      <title>Roles_and_ Responsibilities
+ - Apache Incubator</title>
+ </head>
+ <body>        
+  <table border="0" width="100%" cellspacing="0">
+   <tr><!-- SITE BANNER AND PROJECT IMAGE -->
+    <td align="left" valign="top">
+<a href="http://www.apache.org/"><img src="/images/asf_logo_wide.gif" alt="The Apache Software Foundation" border="0"/></a>
+</td>
+<td align="right">
+<a href="http://incubator.apache.org/"><img src="../images/apache-incubator-logo.png" alt="Apache Incubator" border="0"/></a>
+</td>
+   </tr>
+  </table>
+  <table border="0" width="100%" cellspacing="4">
+   <tr><td colspan="3"><hr noshade="noshade" size="1"/></td></tr>
+   <tr>
+    <!-- LEFT SIDE NAVIGATION -->
+    <td valign="top" nowrap="nowrap" class="navleft">
+     
+
+
+      <div class="menuheader">General</div>
+    <menu compact="compact">
+          <li><a href="/index.html">Home</a></li> 
+          <li><a href="http://www.apache.org/">ASF</a></li> 
+          <li><a href="http://www.apache.org/licenses/">Licensing</a></li> 
+          <li><a href="/resolution.html">What We Do</a></li> 
+          <li><a href="/howwework.html">How We Work</a></li> 
+          <li><a href="/whoweare.html">Who We Are</a></li> 
+          <li><a href="/howtoparticipate.html">How To Participate</a></li> 
+          <li><a href="/faq.html">FAQ</a></li> 
+          <li><a href="/mailing.html">Mailing Lists</a></li> 
+          <li><a href="http://wiki.apache.org/incubator">Wiki</a></li> 
+        </menu>
+
+
+
+      <div class="menuheader">Incubation</div>
+    <menu compact="compact">
+          <li><a href="/projects/index.html">Projects</a></li> 
+          <li><a href="/ip-clearance/index.html">IP Clearance</a></li> 
+          <li><a href="/incubation/Incubation_Policy.html">Incubation Policy</a></li> 
+          <li><a href="/incubation/Process_Description.html">Process Description</a></li> 
+          <li><a href="/incubation/Roles_and_Responsibilities.html">Roles/Responsibilies</a></li> 
+        </menu>
+
+
+
+      <div class="menuheader">Guides</div>
+    <menu compact="compact">
+          <li><a href="/guides/general.html">General</a></li> 
+          <li><a href="/guides/committer.html">Committers</a></li> 
+          <li><a href="/guides/chair.html">Chair</a></li> 
+          <li><a href="/guides/pmc.html">PMC</a></li> 
+          <li><a href="/guides/projects.html">Projects and Mentors</a></li> 
+          <li><a href="/guides/website.html">Updating the Website</a></li> 
+        </menu>
+    </td>
+    <!-- CONTENT -->
+    <td align="left" valign="top" class="content">
+                <h2><img src="/images/redarrow.gif" />
+   <a name="Roles+and+Responsibilities">Roles and Responsibilities
+</a>
+</h2>
+<div class="section-content">
+
+
+
+
+
+
+<p>This document describes the roles (including Sponsor, Contributor,
+Mentor) and provides an overview of the responsibilities of the
+different parties involved in an incubation process.
+</p>
+<h3>
+   <a name="Incubator+Project+Management+Committee+%28PMC%29">Incubator Project Management Committee (PMC)
+</a>
+</h3>
+<div class="section-content">
+
+
+
+
+
+
+<p>(From the resolution that created the Incubator Project - see
+http://incubator.apache.org/resolution.html)
+</p>
+<p>The Incubator PMC is responsible for :
+</p>
 <ul>
-<li>acceptance and oversight of candidate projects submitted or proposed to become part of the Foundation;</li>
-<li>providing guidance and ensuring that sub-projects under it's purview develop products according to the Foundation's philosophy and guidelines for collaborative development;</li>
-<li>providing a repository for the storage of incubation history and information;</li>
-<li>assisting a Podling's Mentor in discharging her/his duties;</li>
-<li>regularly evaluating projects under its purview for the purposes of recommending to the Sponsor whether the project should:</li>
-<li style="list-style: none">
-<ul>
-<li>successfully exit incubation;</li>
-<li>continue to receive guidance and support within the Incubator; or</li>
-<li>be terminated.</li>
-</ul>
-</li>
-</ul>
-<p>To enable effective management of the process of incubation from the point of view of the PMC and from the point of view of members of a project under incubation, a set of policies and procedures are described below that identify roles and responsibilities of participants throughout the incubation lifecycle.</p>
-<p>A project going through the Incubator will therefore be required to regularly report to the Incubator PMC. This will help the PMC in its role of reviewing the status of a project under incubation.</p>
-<p>Finally, the Incubator PMC is the ASF body with the greatest level of expertise and experience in the Incubation process. They provide a store of knowledge that can be called on by the Mentor or a Podling during (or even after) the incubation process. In cases where an Incubation is particularly large, or where the Incubator PMC otherwise feels the Mentor needs additional assistance, the Incubator PMC may choose to provide an experienced Mentor to assist the main Mentor in discharging their duty.</p>
-<a name="N10038"></a><a name="Chair+of+the+Incubator+PMC"></a>
-<h3 class="underlined_5">Chair of the Incubator PMC</h3>
-<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>
-<a name="N1003E"></a><a name="Candidate"></a>
-<h3 class="underlined_5">Candidate</h3>
-<p>A Candidate is a project that is proposed for incubation. A Candidate shall meet the following minimum criteria:</p>
+          <li>acceptance and oversight of candidate projects submitted or proposed
+to become part of the Foundation;
+</li>
+          <li>providing guidance and ensuring that sub-projects under it's purview
+develop products according to the Foundation's philosophy and
+guidelines for collaborative development;
+</li>
+          <li>providing a repository for the storage of incubation history and
+information;
+</li>
+          <li>assisting a Podling's Mentor in discharging her/his duties;
+</li>
+          <li>regularly evaluating projects under its purview for the purposes of
+recommending to the Sponsor whether the project should:
+</li>
+          <li style="list-style: none">
+            <ul>
+              <li>successfully exit incubation;
+</li>
+              <li>continue to receive guidance and support within the Incubator; or
+</li>
+              <li>be terminated.
+</li>
+            </ul>
+          </li>
+        </ul>
+<p>To enable effective management of the process of incubation from the
+point of view of the PMC and from the point of view of members of a
+project under incubation, a set of policies and procedures are
+described below that identify roles and responsibilities of
+participants throughout the incubation lifecycle.
+</p>
+<p>A project going through the Incubator will therefore be required to
+regularly report to the Incubator PMC. This will help the PMC in its
+role of reviewing the status of a project under incubation.
+</p>
+<p>Finally, the Incubator PMC is the ASF body with the greatest level of
+expertise and experience in the Incubation process. They provide a
+store of knowledge that can be called on by the Mentor or a Podling
+during (or even after) the incubation process. In cases where an
+Incubation is particularly large, or where the Incubator PMC
+otherwise feels the Mentor needs additional assistance, the Incubator
+PMC may choose to provide an experienced Mentor to assist the main
+Mentor in discharging their duty.
+</p>
+</div>
+<h3>
+   <a name="Chair+of+the+Incubator+PMC">Chair of the Incubator PMC
+</a>
+</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>
+   <a name="Candidate">Candidate
+</a>
+</h3>
+<div class="section-content">
+
+
+
+
+
+
+<p>A Candidate is a project that is proposed for incubation. A Candidate
+shall meet the following minimum criteria:
+</p>
 <ul>
-<li>affiliated with a named *Champion* (an ASF Member or Officer; see below)</li>
-</ul>
-<p>Optionally, a candidate may:</p>
+          <li>affiliated with a named *Champion* (an ASF Member or Officer; see
+below)
+</li>
+        </ul>
+<p>Optionally, a candidate may:
+</p>
 <ul>
-<li>declare an affiliation with an existing Apache Project in which case it is expected that the Champion is a member of the affiliated project, and the project will become the *Sponsor*;</li>
-<li>specify requirements that may be anticipated during incubation; and/or</li>
-<li>provide a summary of the project relationship/dependencies (existing or planned with existing Apache Projects/Products).</li>
-</ul>
-<p>Naturally, projects will need more than this in order to exit incubation status.</p>
-<p>A candidate project compliant with the above criteria may be proposed by the Champion to the Sponsor for acceptance as a Podling. Acceptance of a candidate shall be subject to the formal voting method of the Sponsor. Should that vote be accepted, the Sponsor will request that the Incubator PMC accept the candidate as a Podling under incubation. The Sponsor shall assign a Mentor, who shall be granted membership of the Incubator PMC for the duration of the incubation process.</p>
-<a name="N10054"></a><a name="Champion"></a>
-<h3 class="underlined_5">Champion</h3>
-<p>A candidate project shall be sponsored by an <a href="http://www.apache.org/foundation/index.html">Officer</a> or <a href="http://www.apache.org/foundation/members.html">Member</a> of the Foundation. The Champion assists the candidate on their initial submission to a Sponsor. While private conversations are not generally encouraged within the Apache community, the Champion's relationship with the Candidate should allow for this in order to educate the Candidate about the Apache Way and prepare the project for the questions and issues likely to be raised by the community.</p>
-<p>Where the Champion is not a Member of the Foundation (i.e. is an Officer only), the Champion shall be a member of the PMC of the Sponsor.</p>
-<p>While the Champion has no formal responsibility within the Incubation process (other than to review and comment on a Candidate's proposal within the Sponsor), it is expected that they will play an active role. A lack of interest on the part of a Champion may be seen by the Incubator PMC as a negative indicator during the course of incubation.</p>
-<a name="N10066"></a><a name="Sponsor"></a>
-<h3 class="underlined_5">Sponsor</h3>
-<p>The Sponsor is the entity within the ASF that makes the determination that a candidate would make a worthy addition to the ASF, and agrees to take on the candidate in question (or in the case of the Incubator PMC, assist it in finding a home) should it complete the incubation process.</p>
-<p>A Sponsor will be one of:</p>
+          <li>declare an affiliation with an existing Apache Project in which case
+it is expected that the Champion is a member of the affiliated
+project, and the project will become the *Sponsor*;
+</li>
+          <li>specify requirements that may be anticipated during incubation; and/or
+</li>
+          <li>provide a summary of the project relationship/dependencies (existing
+or planned with existing Apache Projects/Products).
+</li>
+        </ul>
+<p>Naturally, projects will need more than this in order to exit
+incubation status.
+</p>
+<p>A candidate project compliant with the above criteria may be proposed
+by the Champion to the Sponsor for acceptance as a Podling.
+Acceptance of a candidate shall be subject to the formal voting
+method of the Sponsor. Should that vote be accepted, the Sponsor will
+request that the Incubator PMC accept the candidate as a Podling
+under incubation. The Sponsor shall assign a Mentor, who shall be
+granted membership of the Incubator PMC for the duration of the
+incubation process.
+</p>
+</div>
+<h3>
+   <a name="Champion">Champion
+</a>
+</h3>
+<div class="section-content">
+
+
+
+
+
+
+<p>A candidate project shall be sponsored by an
+
+          <a href="http://www.apache.org/foundation/index.html">Officer
+</a>or
+
+          <a href="http://www.apache.org/foundation/members.html">Member
+</a>of the Foundation. The Champion assists the candidate on their
+initial submission to a Sponsor. While private conversations are not
+generally encouraged within the Apache community, the Champion's
+relationship with the Candidate should allow for this in order to
+educate the Candidate about the Apache Way and prepare the project
+for the questions and issues likely to be raised by the community.
+
+        </p>
+<p>Where the Champion is not a Member of the Foundation (i.e. is an
+Officer only), the Champion shall be a member of the PMC of the
+Sponsor.
+</p>
+<p>While the Champion has no formal responsibility within the Incubation
+process (other than to review and comment on a Candidate's proposal
+within the Sponsor), it is expected that they will play an active
+role. A lack of interest on the part of a Champion may be seen by the
+Incubator PMC as a negative indicator during the course of incubation.
+</p>
+</div>
+<h3>
+   <a name="Sponsor">Sponsor
+</a>
+</h3>
+<div class="section-content">
+
+
+
+
+
+
+<p>The Sponsor is the entity within the ASF that makes the determination
+that a candidate would make a worthy addition to the ASF, and agrees
+to take on the candidate in question (or in the case of the Incubator
+PMC, assist it in finding a home) should it complete the incubation
+process.
+</p>
+<p>A Sponsor will be one of:
+</p>
 <ul>
-<li>The Board of the Apache Software Foundation. In this case, it is expected that the candidate would become a TLP on successful completion of Incubation.</li>
-<li>A Top Level Project within the ASF. In this case, the project in question has agreed that the candidate is a good fit for their project, and will take on the candidate as a sub-project upon successful completion of Incubation.</li>
-<li>The Incubator PMC. In this case, the Incubator PMC agrees that the project in question will make a good addition to the ASF, but there is no clear "owner" of the candidate should it successfully complete incubation. An incubation exit requirement for such candidates will be the identification (and successfuly lobbying) of an "owner" entity - either the board (and the candidate will be a TLP) or another project.</li>
-</ul>
-<p>Note that a Sponsor is more than just a final resting place for a candidate that successfully completes incubation. The Sponsor, by taking on a candidate, is indicating that they believe the candidate will make a worthy addition to the ASF, and takes responsibility for assisting the podling through the Incubation process. The Sponsor is therefore expected to be actively involved in the incubation process and assist where necessary, giving the podling the best possible chance of success. In addition, an entity that is a Top Level Project should be involved in the Candidate's incubation in order to educate the Candidate about practices that are specific to that TLP and about other relevant projects within the TLP.</p>
-<p>However, while the Sponsor is expected to be actively involved, it is formally representated by the Mentor. The Mentor is the individual accountable to the Incubator PMC for ensuring the incubation process is correctly followed. In cases where the Mentor is not fulfilling their responsibilities, the Sponsor (in particular its Chair) will be expected to remedy the situation.</p>
-<a name="N10079"></a><a name="Responsibilities+of+the+Sponsor"></a>
-<h4>Responsibilities of the Sponsor</h4>
+          <li>The Board of the Apache Software Foundation. In this case, it is
+expected that the candidate would become a TLP on successful
+completion of Incubation.
+</li>
+          <li>A Top Level Project within the ASF. In this case, the project in
+question has agreed that the candidate is a good fit for their
+project, and will take on the candidate as a sub-project upon
+successful completion of Incubation.
+</li>
+          <li>The Incubator PMC. In this case, the Incubator PMC agrees that the
+project in question will make a good addition to the ASF, but there
+is no clear "owner" of the candidate should it successfully complete
+incubation. An incubation exit requirement for such candidates will
+be the identification (and successfuly lobbying) of an "owner" entity
+- either the board (and the candidate will be a TLP) or another
+project.
+</li>
+        </ul>
+<p>Note that a Sponsor is more than just a final resting place for a
+candidate that successfully completes incubation. The Sponsor, by
+taking on a candidate, is indicating that they believe the candidate
+will make a worthy addition to the ASF, and takes responsibility for
+assisting the podling through the Incubation process. The Sponsor is
+therefore expected to be actively involved in the incubation process
+and assist where necessary, giving the podling the best possible
+chance of success. In addition, an entity that is a Top Level Project
+should be involved in the Candidate's incubation in order to educate
+the Candidate about practices that are specific to that TLP and about
+other relevant projects within the TLP.
+</p>
+<p>However, while the Sponsor is expected to be actively involved, it is
+formally representated by the Mentor. The Mentor is the individual
+accountable to the Incubator PMC for ensuring the incubation process
+is correctly followed. In cases where the Mentor is not fulfilling
+their responsibilities, the Sponsor (in particular its Chair) will be
+expected to remedy the situation.
+</p>
+<h4> 
+   <a name="Responsibilities+of+the+Sponsor">Responsibilities of the Sponsor
+</a> 
+</h4> 
+<div class="section-content">
+
+
+
+
+
+
 <ul>
-<li>to provide initial approval for a Canidate to be accepted as a Podling</li>
-<li>to nominate a Mentor for the incubation process</li>
-</ul>
-<a name="N10082"></a><a name="Mentor"></a>
-<h3 class="underlined_5">Mentor</h3>
-<p>A Mentor is a role undertaken by a permanent member of the Apache Software Foundation and is chosen by the Sponsor to actively lead in the discharge of their duties (listed above). Upon acceptance by the Incubator PMC, the Mentor automatically becomes a member of the Incubator PMC. A Mentor has specific responsibilities towards the Incubator PMC, the Sponsor and towards the members of the assigned Podling.</p>
-<a name="N10088"></a><a name="Responsibilities+towards+Podling+Members"></a>
-<h4>Responsibilities towards Podling Members</h4>
+            <li>to provide initial approval for a Canidate to be accepted as a Podling
+</li>
+            <li>to nominate a Mentor for the incubation process
+</li>
+          </ul>
+</div>
+</div>
+<h3>
+   <a name="Mentor">Mentor
+</a>
+</h3>
+<div class="section-content">
+
+
+
+
+
+
+<p>A Mentor is a role undertaken by a permanent member of the Apache
+Software Foundation and is chosen by the Sponsor to actively lead in
+the discharge of their duties (listed above). Upon acceptance by the
+Incubator PMC, the Mentor automatically becomes a member of the
+Incubator PMC. A Mentor has specific responsibilities towards the
+Incubator PMC, the Sponsor and towards the members of the assigned
+Podling.
+</p>
+<h4> 
+   <a name="Responsibilities+towards+Podling+Members">Responsibilities towards Podling Members
+</a> 
+</h4> 
+<div class="section-content">
+
+
+
+
+
+
 <ul>
-<li>to ensure that Incubator PMC decisions and/or issue are dealt with in a timely manner and ensure that decisions or resolutions effecting the Podling are communicated promptly and expeditiously;</li>
-<li>to represent the interests of the Podling on the Incubator PMC;</li>
-<li>to liaise between the ASF Secretary and the Podling on matters concerning CLA submission and acknowledgments;</li>
-<li>to liaise between the ASF Infrastructure team and the Podling on matters concerning infrastructure support (mailing lists, CVS establishment, account establishment, etc.);</li>
-<li>to assist the Podling on matters concerning the resolution of license transfers, copyright assignments, and/or software grants where applicable; and</li>
-<li>to provide where and as appropriate, guidance on matters concerning Apache policies and practices - including the establishment of its internal steering committee.</li>
-</ul>
-<a name="N10099"></a><a name="Responsibilities+towards+the+Incubator+PMC"></a>
-<h4>Responsibilities towards the Incubator PMC</h4>
+            <li>to ensure that Incubator PMC decisions and/or issue are dealt with in
+a timely manner and ensure that decisions or resolutions effecting
+the Podling are communicated promptly and expeditiously;
+</li>
+            <li>to represent the interests of the Podling on the Incubator PMC;
+</li>
+            <li>to liaise between the ASF Secretary and the Podling on matters
+concerning CLA submission and acknowledgments;
+</li>
+            <li>to liaise between the ASF Infrastructure team and the Podling on
+matters concerning infrastructure support (mailing lists, CVS
+establishment, account establishment, etc.);
+</li>
+            <li>to assist the Podling on matters concerning the resolution of license
+transfers, copyright assignments, and/or software grants where
+applicable; and
+</li>
+            <li>to provide where and as appropriate, guidance on matters concerning
+Apache policies and practices - including the establishment of its
+internal steering committee.
+</li>
+          </ul>
+</div>
+<h4> 
+   <a name="Responsibilities+towards+the+Incubator+PMC">Responsibilities towards the Incubator PMC
+</a> 
+</h4> 
+<div class="section-content">
+
+
+
+
+
+
 <ul>
-<li>monitoring the Podling through the incubation process;</li>
-<li>evaluating the compliance of the Podling with Incubator PMC policies and procedures;</li>
-<li>assessment of the Podling status with respect to continuation/exit strategy;</li>
-<li>to notify the Incubator PMC and Sponsor of the completion of administrative actions; and</li>
-<li>to provide updates to the Incubator PMC and Sponsor on the status of license grants (where and as appropriate) and other relevant legal information pertaining to the Podling.</li>
-</ul>
-<a name="N100A8"></a><a name="Committers"></a>
-<h4>Committers</h4>
-<p>The candidate shall declare an initial set of committers. On acceptance of a candidate project, the assigned Mentor shall be given access to the Podling's cvs repository for the duration of the incubation process. This is to allow the Mentor to perform their incubation duties, and is for administrative purposes only. To be given full committer privileges, such as the right to add new code to the repository, the Mentor must earn them as would any other potential new committer. In some cases, the Mentor may be part of the initial set of declared committers, but this is not a requirement of the Incubation process.</p>
-<p>In association with its Mentor and Champion, a Podling community is largely free to get on with the stuff they want to do (code, architecture, product, solutions, etc.) with minimal disruption related to the incubator process.</p>
-<p>However, you need to make sure of a number of things:</p>
+            <li>monitoring the Podling through the incubation process;
+</li>
+            <li>evaluating the compliance of the Podling with Incubator PMC policies
+and procedures;
+</li>
+            <li>assessment of the Podling status with respect to continuation/exit
+strategy;
+</li>
+            <li>to notify the Incubator PMC and Sponsor of the completion of
+administrative actions; and
+</li>
+            <li>to provide updates to the Incubator PMC and Sponsor on the status of
+license grants (where and as appropriate) and other relevant legal
+information pertaining to the Podling.
+</li>
+          </ul>
+</div>
+<h4> 
+   <a name="Committers">Committers
+</a> 
+</h4> 
+<div class="section-content">
+
+
+
+
+
+
+<p>The candidate shall declare an initial set of committers. On
+acceptance of a candidate project, the assigned Mentor shall be given
+access to the Podling's cvs repository for the duration of the
+incubation process. This is to allow the Mentor to perform their
+incubation duties, and is for administrative purposes only. To be
+given full committer privileges, such as the right to add new code to
+the repository, the Mentor must earn them as would any other
+potential new committer. In some cases, the Mentor may be part of the
+initial set of declared committers, but this is not a requirement of
+the Incubation process.
+</p>
+<p>In association with its Mentor and Champion, a Podling community is
+largely free to get on with the stuff they want to do (code,
+architecture, product, solutions, etc.) with minimal disruption
+related to the incubator process.
+</p>
+<p>However, you need to make sure of a number of things:
+</p>
 <ul>
-<li>keep your Mentor informed - he/she is reporting to the PMC and generally speaking "no news is bad news". Of course, conducting business on the project's mailing lists is one important way to do this.</li>
-<li>make sure your Champion is continuously in-the-loop and has the latest and greatest information about your project</li>
-<li>actively seek and recruit committers to your project - preferably linking you with existing Apache communities</li>
-<li>make sure your decision making process is visible and accountable</li>
-</ul>
-<p>These activities are not unique to projects in the Incubator. For example, existing Apache Projects have regular reports made by their PMC Chair to the ASF Board.</p>
-<p>During the incubation, the committers will be expected to show how, as a group, they are upholding the ideals of the Apache community. In particular, as the Podling evolves it is anticipated that the Podling will establish procedures for the introduction of new committers through a process consistent with established Apache practices. If you are aiming for TLP status you may also want to start on drafting the policy and procedures you aim to put in place once accepted.</p>
-</div>
-</div>
-<!--+
-    |end content
-    +-->
-<div class="clearboth">&nbsp;</div>
-</div>
-<div id="footer">
-<!--+
-    |start bottomstrip
-    +-->
-<div class="lastmodified">
-<script type="text/javascript"><!--
-document.write("<text>Last Published:</text> " + document.lastModified);
-//  --></script>
-</div>
-<div class="copyright">
-        Copyright &copy;
-         2002-2005 <a href="http://www.apache.org/licenses/">The Apache Software Foundation.</a>
-</div>
-<!--+
-    |end bottomstrip
-    +-->
+            <li>keep your Mentor informed - he/she is reporting to the PMC and
+generally speaking "no news is bad news". Of course, conducting
+business on the project's mailing lists is one important way to do
+this.
+</li>
+            <li>make sure your Champion is continuously in-the-loop and has the
+latest and greatest information about your project
+</li>
+            <li>actively seek and recruit committers to your project - preferably
+linking you with existing Apache communities
+</li>
+            <li>make sure your decision making process is visible and accountable
+</li>
+          </ul>
+<p>These activities are not unique to projects in the Incubator. For
+example, existing Apache Projects have regular reports made by their
+PMC Chair to the ASF Board.
+</p>
+<p>During the incubation, the committers will be expected to show how,
+as a group, they are upholding the ideals of the Apache community. In
+particular, as the Podling evolves it is anticipated that the Podling
+will establish procedures for the introduction of new committers
+through a process consistent with established Apache practices. If
+you are aiming for TLP status you may also want to start on drafting
+the policy and procedures you aim to put in place once accepted.
+</p>
 </div>
-</body>
+</div>
+</div>
+         </td>
+    <!-- RIGHT SIDE NAVIGATION -->
+    <td valign="top" nowrap="nowrap" class="navright">
+     
+
+
+      <div class="menuheader"><a 
+href="http://www.apache.org/foundation/">Foundation</a></div>
+    <menu compact="compact">
+        </menu>
+
+     <div class="menuheader">Search apache.org</div>
+     <form action="http://search.apache.org/" method="post">
+    <p><input type="text" name="query" size="10" />
+    <input type="submit" value="Go" /></p>
+</form>
+
+    </td>     
+   </tr>
+   <!-- FOOTER -->
+   <tr><td colspan="3"><hr noshade="noshade" size="1"/></td></tr>
+   <tr><td colspan="3" class="footer">
+         Copyright &#169; 1999-2005, The Apache Software Foundation<br />
+Licensed under the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+       </td>
+   </tr>
+  </table>
+ </body>
 </html>

Modified: incubator/public/trunk/site-publish/incubation/incubation-process.png
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site-publish/incubation/incubation-process.png?rev=373695&r1=373694&r2=373695&view=diff
==============================================================================
Binary files - no diff available.



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


Mime
View raw message