incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cross...@apache.org
Subject svn commit: r370716 [1/11] - in /incubator/public/trunk/site/xdocs2: ./ guides/ incubation/ ip-clearance/ learn/ projects/ projects/agila/ projects/geronimo/
Date Fri, 20 Jan 2006 03:11:54 GMT
Author: crossley
Date: Thu Jan 19 19:10:36 2006
New Revision: 370716

URL: http://svn.apache.org/viewcvs?rev=370716&view=rev
Log:
Add xdocs2 directory which contains the result of the Forrest export
to Anakia xdoc.

Added:
    incubator/public/trunk/site/xdocs2/
    incubator/public/trunk/site/xdocs2/faq.xml   (with props)
    incubator/public/trunk/site/xdocs2/guides/
    incubator/public/trunk/site/xdocs2/guides/chair.xml   (with props)
    incubator/public/trunk/site/xdocs2/guides/general.xml   (with props)
    incubator/public/trunk/site/xdocs2/guides/pmc.xml   (with props)
    incubator/public/trunk/site/xdocs2/guides/projects.xml   (with props)
    incubator/public/trunk/site/xdocs2/guides/website.xml   (with props)
    incubator/public/trunk/site/xdocs2/howtoparticipate.xml   (with props)
    incubator/public/trunk/site/xdocs2/howwework.xml   (with props)
    incubator/public/trunk/site/xdocs2/incubation/
    incubator/public/trunk/site/xdocs2/incubation/Incubation_Policy.xml   (with props)
    incubator/public/trunk/site/xdocs2/incubation/Process_Description.xml   (with props)
    incubator/public/trunk/site/xdocs2/incubation/Roles_and_Responsibilities.xml   (with props)
    incubator/public/trunk/site/xdocs2/index.xml   (with props)
    incubator/public/trunk/site/xdocs2/ip-clearance/
    incubator/public/trunk/site/xdocs2/ip-clearance/apr-jlibtool.xml   (with props)
    incubator/public/trunk/site/xdocs2/ip-clearance/geronimo-1016-ibm-daytrader.xml   (with props)
    incubator/public/trunk/site/xdocs2/ip-clearance/geronimo-1111-trifork-initial.xml   (with props)
    incubator/public/trunk/site/xdocs2/ip-clearance/geronimo-762-ibm-console.xml   (with props)
    incubator/public/trunk/site/xdocs2/ip-clearance/geronimo-875-ibm-eclipse.xml   (with props)
    incubator/public/trunk/site/xdocs2/ip-clearance/geronimo-iiop.xml   (with props)
    incubator/public/trunk/site/xdocs2/ip-clearance/index.xml   (with props)
    incubator/public/trunk/site/xdocs2/ip-clearance/ip-clearance-template.xml   (with props)
    incubator/public/trunk/site/xdocs2/ip-clearance/myfaces-tobago.xml   (with props)
    incubator/public/trunk/site/xdocs2/ip-clearance/portals-gluecode-jetspeed.xml   (with props)
    incubator/public/trunk/site/xdocs2/learn/
    incubator/public/trunk/site/xdocs2/learn/index.xml   (with props)
    incubator/public/trunk/site/xdocs2/learn/mailing-lists.xml   (with props)
    incubator/public/trunk/site/xdocs2/learn/newcommitters.xml   (with props)
    incubator/public/trunk/site/xdocs2/learn/rules-for-revolutionaries.xml   (with props)
    incubator/public/trunk/site/xdocs2/learn/theapacheway.xml   (with props)
    incubator/public/trunk/site/xdocs2/linkmap.xml   (with props)
    incubator/public/trunk/site/xdocs2/projects/
    incubator/public/trunk/site/xdocs2/projects/activemq.xml   (with props)
    incubator/public/trunk/site/xdocs2/projects/agila/
    incubator/public/trunk/site/xdocs2/projects/agila.xml   (with props)
    incubator/public/trunk/site/xdocs2/projects/agila/index.xml   (with props)
    incubator/public/trunk/site/xdocs2/projects/altrmi.xml   (with props)
    incubator/public/trunk/site/xdocs2/projects/apollo.xml   (with props)
    incubator/public/trunk/site/xdocs2/projects/axion.xml   (with props)
    incubator/public/trunk/site/xdocs2/projects/beehive.xml   (with props)
    incubator/public/trunk/site/xdocs2/projects/depot.xml   (with props)
    incubator/public/trunk/site/xdocs2/projects/derby.xml   (with props)
    incubator/public/trunk/site/xdocs2/projects/directory.xml   (with props)
    incubator/public/trunk/site/xdocs2/projects/felix.xml   (with props)
    incubator/public/trunk/site/xdocs2/projects/ftpserver.xml   (with props)
    incubator/public/trunk/site/xdocs2/projects/geronimo/
    incubator/public/trunk/site/xdocs2/projects/geronimo.xml   (with props)
    incubator/public/trunk/site/xdocs2/projects/geronimo/geronimo-proposal.xml   (with props)
    incubator/public/trunk/site/xdocs2/projects/geronimo/index.xml   (with props)
    incubator/public/trunk/site/xdocs2/projects/graffito.xml   (with props)
    incubator/public/trunk/site/xdocs2/projects/harmony.xml   (with props)
    incubator/public/trunk/site/xdocs2/projects/hermes.xml   (with props)
    incubator/public/trunk/site/xdocs2/projects/httpd-cli.xml   (with props)
    incubator/public/trunk/site/xdocs2/projects/ibatis.xml   (with props)
    incubator/public/trunk/site/xdocs2/projects/incubation-status-template.xml   (with props)
    incubator/public/trunk/site/xdocs2/projects/index.xml   (with props)
    incubator/public/trunk/site/xdocs2/projects/jackrabbit.xml   (with props)
    incubator/public/trunk/site/xdocs2/projects/jaxme.xml   (with props)
    incubator/public/trunk/site/xdocs2/projects/jdo.xml   (with props)
    incubator/public/trunk/site/xdocs2/projects/juddi.xml   (with props)
    incubator/public/trunk/site/xdocs2/projects/juice.xml   (with props)
    incubator/public/trunk/site/xdocs2/projects/lenya.xml   (with props)
    incubator/public/trunk/site/xdocs2/projects/log4cxx.xml   (with props)
    incubator/public/trunk/site/xdocs2/projects/log4net.xml   (with props)
    incubator/public/trunk/site/xdocs2/projects/log4php.xml   (with props)
    incubator/public/trunk/site/xdocs2/projects/lucene4c.xml   (with props)
    incubator/public/trunk/site/xdocs2/projects/merlin-developer.xml   (with props)
    incubator/public/trunk/site/xdocs2/projects/mod_ftp.xml   (with props)
    incubator/public/trunk/site/xdocs2/projects/muse.xml   (with props)
    incubator/public/trunk/site/xdocs2/projects/myfaces.xml   (with props)
    incubator/public/trunk/site/xdocs2/projects/nutch.xml   (with props)
    incubator/public/trunk/site/xdocs2/projects/pluto.xml   (with props)
    incubator/public/trunk/site/xdocs2/projects/roller.xml   (with props)
    incubator/public/trunk/site/xdocs2/projects/servicemix.xml   (with props)
    incubator/public/trunk/site/xdocs2/projects/spamassassin.xml   (with props)
    incubator/public/trunk/site/xdocs2/projects/stdcxx.xml   (with props)
    incubator/public/trunk/site/xdocs2/projects/synapse.xml   (with props)
    incubator/public/trunk/site/xdocs2/projects/tobago.xml   (with props)
    incubator/public/trunk/site/xdocs2/projects/tsik.xml   (with props)
    incubator/public/trunk/site/xdocs2/projects/tuscany.xml   (with props)
    incubator/public/trunk/site/xdocs2/projects/wadi.xml   (with props)
    incubator/public/trunk/site/xdocs2/projects/woden.xml   (with props)
    incubator/public/trunk/site/xdocs2/projects/wsrp4j.xml   (with props)
    incubator/public/trunk/site/xdocs2/projects/xmlbeans.xml   (with props)
    incubator/public/trunk/site/xdocs2/resolution.xml   (with props)
    incubator/public/trunk/site/xdocs2/whoweare.xml   (with props)

Added: incubator/public/trunk/site/xdocs2/faq.xml
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site/xdocs2/faq.xml?rev=370716&view=auto
==============================================================================
--- incubator/public/trunk/site/xdocs2/faq.xml (added)
+++ incubator/public/trunk/site/xdocs2/faq.xml Thu Jan 19 19:10:36 2006
@@ -0,0 +1,135 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<document>
+  <properties>
+    <title>Frequently Asked Questions
+</title>
+  </properties>
+  <body>
+    <section id="Questions" name="Questions">
+      <subsection id="incubator" name="1. Incubator">
+        <subsection id="does_project_X_really_need_Incubation" name="1.1. Does the X Project really have to go in the Incubator to get to Apache?">
+          <p>Yes.
+</p>
+          <p>Code that has existed outside the asf can
+
+            <strong>only
+</strong>enter the ASF through the Incubator. There is no other option.
+
+          </p>
+          <p>The Incubator, among other thingsm is where the due-diligence of
+making sure the licence is correct, the copyright is assigned, and
+all of the initial developers submit their clas.
+</p>
+        </subsection>
+        <subsection id="can_Incubation_be_skipped" name="1.2. I'm the mentor of this project, and I think that I'm able to do it by myself. The Incubator doesn't add anything, can it be skipped?">
+          <p>No.
+</p>
+          <p>Do it right, do it well, and add something in the process.
+</p>
+          <p>Incubation is not about handing it over to some other group and
+seeing what happens. The Incubator is simply the name of the place
+that governs your actions when you process a new project into Apache.
+It moves at the same rate you do, and achieves whatever you achieve
+-- the only difference is that we have a permanent record in
+
+            <strong>one
+</strong>place that we can go back to if there are later IP problems, and
+there is a gate that must be passed through before the project is
+given the right to release software on behalf of the ASF. That gate
+will not be ignored or bypassed just because one group or another
+feels they have earned the right to bypass it; allowing that kind of
+exception destroys the potential to build a tradition of effective
+oversight, which is the reason we created incubator.
+
+          </p>
+        </subsection>
+        <subsection id="project_XXX_makes_no_mention_of_Incubator" name="1.3. Project XXX makes no mention of the Incubator for accepting new projects, but the Incubator site says that all projects entering Apache must pass the Incubator. What do we need to do, to move to the Apache XXX project?">
+          <p>The incubation process, WRT responsibilities, is roughly as follows:
+</p>
+          <ol>
+            <li>Any Apache PMC (project management commitee) or the Apache board
+approves the entrance of a project at Apache. They are the Sponsor.
+</li>
+            <li>The Incubator is from that moment on responsible for the project,
+which will remain so till the Incubator votes for it to be
+"graduated" to the PMC that asked for it. If the PMC was the
+Incubator itself or the board, the project will have its own PMC.
+</li>
+            <li>Incubation complete.
+</li>
+          </ol>
+          <p>So, since you would like to have a place under the XXX Project, ask
+there to vote for acceptance. After that vote, you will automatically
+be under the Incubator, and incubation will take place.
+</p>
+        </subsection>
+        <subsection id="proposed_new_codebase" name="1.4. Someone has proposed that their code/project be donated to project X within the ASF for continued development. What do we need to do to accept the code?">
+          <p>The Incubator will only accept code for incubation if a PMC (project
+management committee) or the Apache board has voted to accept it. So
+when a proposal for the donation of code occurs, the project in
+question should discuss the proposal internally, leading to a
+decision by that project's PMC on whether or not to accept the code
+(and potentially the project surrounding it) into the fold.
+</p>
+          <p>If the PMC agrees, then the incubator can be approached, and the code
+accepted for incubation. The grant needs to be recorded by following
+the procedure outlined at the
+
+            <a href="http://www.apache.org/licenses/">Software Grants
+</a>section of the ASF Licenses page.
+
+          </p>
+        </subsection>
+      </subsection>
+      <subsection id="how_to_participate" name="2. How to participate">
+        <subsection id="site" name="2.1. How can I update the site?">
+          <p>Refer to
+
+            <a href="howtoparticipate.html#website">How to Participate
+</a>page. If you are not a committer on the Incubator project, then you
+can still send patches for the source documents.
+
+          </p>
+        </subsection>
+        <subsection id="projectstatus" name="2.2. How do I update the incubation status of a project?">
+          <p>Look in the incubator SVN module, under
+site-author/projects/projectname.html (Note: Some projects still use
+old *.cwiki as the input format - not recommended.)
+</p>
+          <p>See the
+
+            <a href="guides/website.html">instructions
+</a>for updating the website.
+
+          </p>
+        </subsection>
+        <subsection id="why_not_issue_tracking_for_incubation_tracking" name="2.3. Why don't we use an issue tracking system to track incubation process?">
+          <p>AFAIK, issue trackers do not authenticate that the person entering
+the status information has the authority to do so, which is what we
+get with the Subversion source control process.
+</p>
+          <p>Note that how the actual day to day tracking is done is not relevant,
+and any means, even an issue tracker can be used.
+</p>
+          <p>Nevertheless, SVN is our only authorative and formal tracking system
+for incubation status.
+</p>
+        </subsection>
+        <subsection id="updating_the_project_website" name="2.4. How do I update the site of an incubating project?">
+          <p>First of all, read our
+
+            <a href="incubation/Incubation_Policy.html">Incubation Policy
+</a>.
+
+          </p>
+          <p>Refer to
+
+            <a href="howtoparticipate.html#project-website">How to Participate
+</a>page.
+
+          </p>
+        </subsection>
+      </subsection>
+    </section>
+  </body>
+</document>

Propchange: incubator/public/trunk/site/xdocs2/faq.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/public/trunk/site/xdocs2/guides/chair.xml
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site/xdocs2/guides/chair.xml?rev=370716&view=auto
==============================================================================
--- incubator/public/trunk/site/xdocs2/guides/chair.xml (added)
+++ incubator/public/trunk/site/xdocs2/guides/chair.xml Thu Jan 19 19:10:36 2006
@@ -0,0 +1,127 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<document>
+  <properties><!--
+
+    <meta content="HTML Tidy, see www.w3.org" name="generator"/>-->
+<!--
+
+    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type"/>-->
+
+    <title>Chair
+</title>
+    <link href="http://purl.org/DC/elements/1.0/" rel="schema.DC"/>
+  </properties>
+  <body>
+    <section id="Incubator+Chair+Guides" name="Incubator Chair Guides">
+      <p>Some things can only be done by the Incubator Chair.
+</p>
+      <subsection id="Adding+a+new+PMC+member" name="Adding a new PMC member">
+        <p>1. Be sure that the person you're adding has been voted by the PMC or
+is one of the designated Mentors for a project
+</p>
+        <p>2. Send this mail:
+</p>
+        <pre>To: board@apache.org CC: pmc@incubator.apache.org CC: address(es) of
+the new pmc member(s) Subject: [PLEASE ACK] New Incubator PMC
+member(s): Member1, Member2, ... Body: The Incubator PMC is adding
+(a) new member(s): Member1 &lt;member1@apache.org&gt; (ProjectX Mentor)
+Member2 &lt;member2@apache.org&gt; (voted...) Please ACK. Explanation of
+the process --------------------------- A chair can add a new PMC
+member, but it must notify the board first. 72 hours after a board
+member has ACKed this request, and no other from the board objects,
+the person is officially part of the PMC. For the new member(s)
+--------------------------- general-subscribe@incubator.apache.org
+pmc-subscribe@incubator.apache.org
+</pre>
+        <p>If he is a Mentor, coming in with a project, you may want to add this
+to the mail:
+</p>
+        <pre>Note about adding Mentors --------------------------- I note that he
+has not been voted in with a "[VOTE] Name Surmane as PMC member" but
+has nevertheless been accepted as being the Mentor of a project, that
+*has* been accepted.
+</pre>
+        <p>3. Add the person to the incubator CVS avail
+</p>
+        <p>3. Wait 72 hours after the ACK of a board member
+</p>
+        <p>4. After 72 hours without problems, add the person to:
+</p>
+        <ul>
+          <li>http://cvs.apache.org/viewcvs.cgi/incubator/site/whoweare.cwiki?view=m
+rkup
+</li>
+          <li>apachecvs/committers/board/committee-info.txt 5. Mail the new member
+this welcome message.
+</li>
+        </ul>
+        <pre>Welcome in the Apache Incubator Project. Here is some information to
+get you started as a PMC member. - please subscribe to the incubator
+mailing lists: - general-subscribe@incubator.apache.org -
+pmc-subscribe@incubator.apache.org -
+incubator-cvs-subscribe@apache.org - ADD OTHER LISTS HERE
+(optionally) - incubator-site-cvs-subscribe@apache.org - the
+incubator CVS modules are: - incubator - incubator-site - ADD OTHER
+CVS MODULES HERE - all the public information, rules and policies
+about the Apache Incubator is in the 'incubator' CVS module under
+site/**, and thus published on http://incubator.apache.org/ - the
+incubator/site/whoweare.wiki page lists all project members, as is
+also registered in the CVS module 'committers' under
+board/committee-info.txt - the Incubator website is published by
+committing the Forrest-generated docs in the 'incubator-site' CVS
+module http://incubator.apache.org/howtoparticipate.html#website -
+all private information for the Incubator PMC is ADD PRIVATE
+RESOURCES HERE - all Incubator PMC members have full access to all
+CVS repositories (also of the incubating projects for oversight
+purposes) and are wiki admins - status documents about Incubating
+projects are under incubator/site-author/project/ directory; please
+keep the ones you are mentoring updated - all committers on all
+incubating projects have access to the 'incubator' and
+'incubator-site' CVS modules, so they can participate in the general
+Incubator Project as committers - please read our work documents
+under incubator/site-author/incubation/ for more information about
+the incubation process; they are published under
+http://incubator.apache.org/incubation/ Thanks for helping us :-)
+</pre>
+      </subsection>
+      <subsection id="Making+the+Board+Report" name="Making the Board Report">
+        <p>The Chair must remember to send the board a status report of the
+Incubator Project.
+</p>
+        <p>The dates of the meetings and the months in which to send in a report
+can be found in the committers CVS module under board/ .
+</p>
+        <p>It's
+
+          <em>important
+</em>that the report is sent
+
+          <em>at least
+</em>two days before the scheduled meeting.
+
+        </p>
+        <p>The Chair should also ensure that the Incubating projects have prior
+notice of this so that they can send in their Incubation Report. It's
+advisable to ask them at least 3 weeks prior the meeting, so that the
+Incubator Project can review and discuss them.
+</p>
+        <p>Here is a board report boilerplate:
+</p>
+        <pre>Status report for the Apache Incubator Project * Noteable happening's
+in the Incubator * what code releases have been made? [since the last
+report] * any new projects in process of being accepted? * any legal
+issues to bring to the board? * any cross-project issues that need to
+be addressed? * any problems with committers, members, etc? * plans
+and expectations for the next period?
+</pre>
+      </subsection>
+      <subsection id="Asking+for+Incubation+Reports" name="Asking for Incubation Reports">
+        <p>At least when there is a board report due, or when it seemes needed,
+the Chair can ask a project for an Incubation Report. This helps in
+assessing the status of the project and eventually vote for the exit
+from incubation.
+</p>
+      </subsection>
+    </section>
+  </body>
+</document>

Propchange: incubator/public/trunk/site/xdocs2/guides/chair.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/public/trunk/site/xdocs2/guides/general.xml
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site/xdocs2/guides/general.xml?rev=370716&view=auto
==============================================================================
--- incubator/public/trunk/site/xdocs2/guides/general.xml (added)
+++ incubator/public/trunk/site/xdocs2/guides/general.xml Thu Jan 19 19:10:36 2006
@@ -0,0 +1,24 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<document>
+  <properties><!--
+
+    <meta content="HTML Tidy, see www.w3.org" name="generator"/>-->
+<!--
+
+    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type"/>-->
+
+    <title>Incubator Guides
+</title>
+    <link href="http://purl.org/DC/elements/1.0/" rel="schema.DC"/>
+  </properties>
+  <body>
+    <section id="General" name="General">
+      <p>If you don't know how to do something in the Incubator, look here
+first, and hopefully you'll find it.
+</p>
+      <p>If not, please ask on general@incubator.apache.org, and then add it
+here, so others after you can find it right away next time.
+</p>
+    </section>
+  </body>
+</document>

Propchange: incubator/public/trunk/site/xdocs2/guides/general.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/public/trunk/site/xdocs2/guides/pmc.xml
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site/xdocs2/guides/pmc.xml?rev=370716&view=auto
==============================================================================
--- incubator/public/trunk/site/xdocs2/guides/pmc.xml (added)
+++ incubator/public/trunk/site/xdocs2/guides/pmc.xml Thu Jan 19 19:10:36 2006
@@ -0,0 +1,115 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<document>
+  <properties><!--
+
+    <meta content="HTML Tidy, see www.w3.org" name="generator"/>-->
+<!--
+
+    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type"/>-->
+
+    <title>PMC
+</title>
+    <link href="http://purl.org/DC/elements/1.0/" rel="schema.DC"/>
+  </properties>
+  <body>
+    <section id="Incubator+PMC+Guides" name="Incubator PMC Guides">
+      <p>This document is targeted at Incubator PMC members. A project PMC is
+responsible for managing a project. If you are not a member of a PMC,
+you'll find this document totally useless since all information
+presented here assumes that you are a member of the PMC.
+</p>
+      <p>So, if you are not a PMCer, but wish to become one, start with the
+instructions on
+
+        <a href="../howtoparticipate.html">how to participate
+</a>.
+
+      </p>
+      <p>For further information, see the
+
+        <a href="http://www.apache.org/dev/pmc.html">Apache FAQ for PMC members
+</a>
+      </p>
+      <subsection id="Starting+a+new+Project" name="Starting a new Project">
+        <p>After a project has been accepted by Apache by a positive vote of a
+PMC, it can start incubation. Here are the initial steps.
+</p>
+        <p>1. Give the initial committers that are already Apache committers
+commit privileges to the "incubator" SVN modules, so that they can
+start helping with the project ASAP.
+</p>
+        <p>This can be done by the Incubator Chair (preferred as it's usually
+the fastest way), by infrastructure@apache.org or anyone else that
+has the privs to do it. We are talking about adding people that are
+already in Apache and should not have any problem in gaining access
+to these public repositories.
+</p>
+        <p>Example with project Axion:
+</p>
+        <p>In the Apache CVSROOT avail file (FIXME: these notes need to be
+updated for SVN) search for the following line:
+</p>
+        <pre>#Incubating projects (should not be here if the project has graduated)
+</pre>
+        <p>add the projectname at the end of the next line
+</p>
+        <pre>#@see
+ws-juddi,ws-jaxme,ws-wsrp4j,xml-xmlbeans,cocoon-lenya,(depot),(axion)
+^^^^^^^^^^
+</pre>
+        <p>add a line like this
+</p>
+        <pre>avail|dlr,dsale,geirm,jstrachan,jvanzyl,morgand,mpoeschl,rwaldhoff|inc
+bator,incubator-site
+</pre>
+        <p>2. Add the status page template for the project and publish the site.
+</p>
+        <p>Copy the following status template to
+site-author/projects/${project}.html and add an entry to the
+site-author/site.xml and site-author/projects/index.html files. See
+the full
+
+          <a href="../guides/website.html">instructions
+</a>for updating the website.
+
+        </p>
+        <ul>
+          <li>
+            <a href="http://svn.apache.org/viewcvs.cgi/*checkout*/incubator/public/trunk/site-author/projects/incubation-status-template.html">incubator/site-author/projects/incubation-status-template.html
+</a>
+          </li>
+        </ul>
+        <p>3. Make sure the
+
+          <a href="../guides/chair.html">Chair
+</a>adds the Mentor(s) to the PMC.
+
+        </p>
+        <p>4. Send a mail to general@incubator.apache.org telling that the above
+things have been done and invite the project members to start working
+with the status page items.
+</p>
+        <p>In particular you may want to cite this:
+</p>
+        <ul>
+          <li>
+            <a href="../faq.html#can_Incubation_be_skipped">http://incubator.apache.org/faq.html#can_Incubation_be_skipped
+</a>
+          </li>
+        </ul>
+      </subsection>
+      <subsection id="IP+Clearance+template" name="IP Clearance template">
+        <p>
+          <a href="http://svn.apache.org/viewcvs.cgi/*checkout*/incubator/public/trunk/site-author/ip-clearance/ip-clearance-template.html">incubator/site-author/ip-clearance/ip-clearance-template.html
+</a>
+        </p>
+        <p>See list of other
+
+          <a href="../ip-clearance/index.html">IP Clearance documents
+</a>.
+
+        </p>
+      </subsection>
+    </section>
+  </body>
+</document>

Propchange: incubator/public/trunk/site/xdocs2/guides/pmc.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/public/trunk/site/xdocs2/guides/projects.xml
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site/xdocs2/guides/projects.xml?rev=370716&view=auto
==============================================================================
--- incubator/public/trunk/site/xdocs2/guides/projects.xml (added)
+++ incubator/public/trunk/site/xdocs2/guides/projects.xml Thu Jan 19 19:10:36 2006
@@ -0,0 +1,52 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<document>
+  <properties><!--
+
+    <meta content="HTML Tidy, see www.w3.org" name="generator"/>-->
+<!--
+
+    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type"/>-->
+
+    <title>Projects
+</title>
+    <link href="http://purl.org/DC/elements/1.0/" rel="schema.DC"/>
+  </properties>
+  <body>
+    <section id="Incubating+Project+and+Mentor+Guides" name="Incubating Project and Mentor Guides">
+      <p>This document is targeted at any Incubating Project member, but
+specially to Mentors, that have to ensure that some things get done.
+</p>
+      <subsection id="Sending+in+an+Incubation+Report" name="Sending in an Incubation Report">
+        <p>On a regular basis, reports from each incubating project are
+aggregated and sent to the ASF Board. Watch the general@incubator
+mailing list for when these become due.
+</p>
+        <p>The report of Incubating Projects can be done by anyone on the
+project, not necessarily by Mentors, but it must be something that is
+generally agreed upon by the community.
+</p>
+        <p>If Mentors disagree with the posted report, they should say so, else
+we will assume that it speaks for the community, regardless the
+person who posted it.
+</p>
+        <p>It should be posted on the main Incubator list:
+general@incubator.apache.org
+</p>
+        <p>Here are the points to be addressed:
+</p>
+        <pre>Report for the Incubator * is the project's Incubation
+
+          <a href="../projects/index.html">Status
+</a>file up to date? (also provide the URL) * any legal, cross-project or
+personal issues that still need to be addressed? * what has been
+done, apart from the items listed in the Incubation Status file, for
+incubation since the last report? * plans and expectations for the
+next period? * any recommendations for how incubation could run more
+smoothly for you? * etc (your own thoughts on what is important would
+be helpful!)
+
+        </pre>
+      </subsection>
+    </section>
+  </body>
+</document>

Propchange: incubator/public/trunk/site/xdocs2/guides/projects.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/public/trunk/site/xdocs2/guides/website.xml
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site/xdocs2/guides/website.xml?rev=370716&view=auto
==============================================================================
--- incubator/public/trunk/site/xdocs2/guides/website.xml (added)
+++ incubator/public/trunk/site/xdocs2/guides/website.xml Thu Jan 19 19:10:36 2006
@@ -0,0 +1,135 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<document>
+  <properties><!--
+
+    <meta content="HTML Tidy, see www.w3.org" name="generator"/>-->
+
+    <title>Updating the top-level website
+</title>
+  </properties>
+  <body>
+    <section id="Overview+of+the+Incubator+site" name="Overview of the Incubator site">
+      <p>The top-level Incubator website is currently generated by
+
+        <a href="http://forrest.apache.org/">Apache Forrest
+</a>.
+
+      </p>
+      <p>The source documents are kept in the "incubator" SVN repository at
+"site-author". Most documents are in site-author/*.html format. The
+status reports for each project are in site-author/project/*.html
+</p>
+      <p>The production documents are kept in the "incubator" SVN repository
+at "site-publish". That directory is then checked-out on the server
+to re-create the website.
+</p>
+    </section>
+    <section id="Edit+the+content" name="Edit the content">
+      <p>People with commit access to the "incubator" SVN can edit the source
+documents in the "site-author/" directory. Anyone else can send
+patches to those documents.
+</p>
+      <subsection id="Checkout+the+Incubator+SVN" name="Checkout the Incubator SVN">
+        <pre>cd /usr/local/svn svn co
+https://svn.apache.org/repos/asf/incubator/public/trunk incubator cd
+incubator
+</pre>
+      </subsection>
+      <subsection id="Edit+the+source+documents" name="Edit the source documents">
+        <p>The source content is in html format at "site-author" directory.
+Please edit it and view the html document directly in your web
+browser. Looks okay? Then do your normal svn procedure 'svn diff, svn
+commit' etc. Done.
+</p>
+        <p>Later someone will generate the documents with Forrest (see below).
+</p>
+      </subsection>
+      <subsection id="Add+a+new+document" name="Add a new document">
+        <p>Add new documents in the site-author directory, then do 'svn add'.
+Add a new entry to the menu structure by editing site-author/site.xml
+</p>
+      </subsection>
+      <subsection id="Edit+your+project+status+report" name="Edit your project status report">
+        <p>The sources for the status reports are in site-author/projects/*.html
+</p>
+        <p>Add a new one by copying the template from
+site-author/projects/incubation-status-template.html to
+site-author/projects/${project}.html and follow the instructions
+above for adding a new document. Also add an entry to the table at
+site-author/projects/index.html
+</p>
+      </subsection>
+    </section>
+    <section id="Generating+the+top-level+website" name="Generating the top-level website">
+      <p>
+        <strong>Note:
+</strong>You can just commit the source changes and leave it to someone else
+to generate the website.
+
+      </p>
+      <subsection id="Using+a+local+Forrest+installation" name="Using a local Forrest installation">
+        <p>Install this specific release of
+
+          <a href="http://forrest.apache.org/">Apache Forrest
+</a>(SVN branch "forrest_07_branch") ...
+
+        </p>
+        <pre>cd /usr/local/svn svn co
+http://svn.apache.org/repos/asf/forrest/branches/forrest_07_branch
+forrest_07_branch cd forrest_07_branch/main ./build.sh
+</pre>
+        <p>Set the JAVA_HOME environment variable (1.4+). For convenience, you
+can also set the FORREST_HOME environment variable to be the
+top-level of the distribution, and add $FORREST_HOME/bin to your
+$PATH.
+</p>
+        <p>Here is a quick tour:
+</p>
+        <ul>
+          <li>cd into the local "incubator" SVN directory.
+</li>
+          <li>Do 'forrest run'.
+</li>
+          <li>Browser http://localhost:8888/ to review the site.
+</li>
+          <li>Edit the source docs in place at site-author/*.* and see changes in
+the browser by re-loading the page.
+</li>
+        </ul>
+        <p>When you are satisifed, you will rebuild the whole site and add the
+changed documents to the "site-publish" directory ...
+</p>
+        <p>In the top-level "incubator" SVN directory, do 'forrest site' (or
+just plain 'forrest') to render the HTML and PDF files into the
+"site-publish" directory. If the site built without errors, then do
+the usual SVN stuff: 'svn status' 'svn add' 'svn diff' 'svn commit'.
+</p>
+        <p>To update the website, the "incubator/site-publish" SVN directory is
+checked-out on the server.
+</p>
+        <pre class="code">ssh people.apache.org cd /www/incubator.apache.org svn update
+</pre>
+      </subsection>
+    </section>
+    <section id="other" name="Other notes">
+      <p>Make sure that your subversion client is properly
+
+        <a href="http://www.apache.org/dev/version-control.html#https-svn">configured
+</a>. This vastly reduces the amount of traffic on the svn email commits,
+e.g. *.pdf
+
+      </p>
+      <p>See other notes for maintenance of
+
+        <a href="http://www.apache.org/dev/project-site.html">project websites
+</a>.
+
+      </p>
+      <p>Note: temporary links to cause templates to be generated as xdoc ...
+
+        <a href="../projects/incubation-status-template.html"/>
+        <a href="../ip-clearance/ip-clearance-template.html"/>
+      </p>
+    </section>
+  </body>
+</document>

Propchange: incubator/public/trunk/site/xdocs2/guides/website.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/public/trunk/site/xdocs2/howtoparticipate.xml
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site/xdocs2/howtoparticipate.xml?rev=370716&view=auto
==============================================================================
--- incubator/public/trunk/site/xdocs2/howtoparticipate.xml (added)
+++ incubator/public/trunk/site/xdocs2/howtoparticipate.xml Thu Jan 19 19:10:36 2006
@@ -0,0 +1,186 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<document>
+  <properties><!--
+
+    <meta content="HTML Tidy, see www.w3.org" name="generator"/>-->
+<!--
+
+    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type"/>-->
+
+    <title>How to Participate
+</title>
+    <link href="http://purl.org/DC/elements/1.0/" rel="schema.DC"/>
+  </properties>
+  <body>
+    <section id="Check+this+first" name="Check this first">
+      <p>Before doing anything, we encourage you to read the incubator website
+and in particular our "About" documents.
+</p>
+      <p>If you have other questions about any aspect of the incubation
+process, feel free to post them on general@incubator.apache.org
+</p>
+      <p>To find a Sponsor project and Mentors, then investigate existing
+Apache project mailing lists as described in the
+
+        <a href="incubation/Process_Description.html#Establishment">Establishment
+</a>section. Follow links at each of the
+
+        <a href="http://www.apache.org/foundation/projects.html">Apache projects
+</a>.
+
+      </p>
+      <p>If you want to assist with the development of a specific
+
+        <a href="projects/">Incubating Project
+</a>refer to its development mailing list. The Incubator mailing lists
+are for project incubation, not for project development.
+
+      </p>
+      <p>See general mail information and other
+
+        <a href="http://www.apache.org/foundation/mailinglists.html">foundation-wide lists
+</a>.
+
+      </p>
+    </section>
+    <section id="Incubator+Project+resources" name="Incubator Project resources">
+      <div class="fixme">fixme: Check that all Incubator project resources are listed.
+</div>
+      <subsection id="Mailing+lists" name="Mailing lists">
+        <p>As with everything else in Apache, most of what goes on happens or is
+discussed on electronic mailing lists. Here are the lists associated
+with the Incubator, and their purposes.
+</p>
+        <subsection id="general%40incubator.apache.org" name="general@incubator.apache.org">
+          <p>This is where general and public discussion of things about the
+Incubator take place. It's also where follow-up messages sent in
+reply to cvs commit reports get sent (see the next list). There is a
+'digest' form of this list, which collects individual messages and
+sends the collection when enough have accumulated or a given amount
+of time has passed since the last digest. Anyone may subscribe; only
+subscribers may post.
+</p>
+          <ul>
+            <li>To subscribe, send a message to general-subscribe@incubator.apache.org
+</li>
+            <li>To subscribe to the digest, send a message to
+general-digest-subscribe@incubator.apache.org
+</li>
+            <li>To unsubscribe, send a message to
+general-unsubscribe@incubator.apache.org
+</li>
+          </ul>
+        </subsection>
+        <subsection id="projects%40incubator.apache.org" name="projects@incubator.apache.org">
+          <p>This is the development mailing list for some of the older projects
+in incubation. These days all incubating projects have their own
+lists. This projects@ list might be used for generic project
+development questions (so far not much traffic). Anyone may
+subscribe; only subscribers may post.
+</p>
+          <ul>
+            <li>To subscribe, send a message to
+projects-subscribe@incubator.apache.org
+</li>
+            <li>To unsubscribe, send a message to
+projects-unsubscribe@incubator.apache.org
+</li>
+          </ul>
+        </subsection>
+        <subsection id="cvs%40incubator.apache.org" name="cvs@incubator.apache.org">
+          <p>When changes are made to the code repository, the details are
+automatically sent to this list. Its Reply-To is set to the 'general'
+list, so if you reply to a cvs message that's where your reply is
+going to end up. Anyone may subscribe; only subscribers may post.
+</p>
+          <ul>
+            <li>To subscribe, send a message to cvs-subscribe@incubator.apache.org
+</li>
+            <li>To unsubscribe, send a message to cvs-unsubscribe@incubator.apache.org
+</li>
+          </ul>
+        </subsection>
+        <subsection id="announce%40incubator.apache.org" name="announce@incubator.apache.org">
+          <p>This is the list to which you should be subscribed if you want to be
+kept apprised of significant events or milestones in the project's
+activities, but don't want to track the full traffic in the 'general'
+list. Anyone may subscribe; all posts are moderated.
+</p>
+          <ul>
+            <li>To subscribe, send a message to
+announce-subscribe@incubator.apache.org
+</li>
+            <li>To unsubscribe, send a message to
+announce-unsubscribe@incubator.apache.org
+</li>
+          </ul>
+        </subsection>
+        <subsection id="pmc%40incubator.apache.org" name="pmc@incubator.apache.org">
+          <ul>
+            <li>This is a private list for the project management committee. It is
+not open to general subscription.
+</li>
+          </ul>
+        </subsection>
+      </subsection>
+    </section>
+    <section id="Project-specific+resources" name="Project-specific resources">
+      <p>Some
+
+        <a href="projects/">projects
+</a>under incubation have their own mailing lists, or their development
+discussion occurs on the mailing list of another project. Check out
+the project websites to be sure what mailing list is the right one.
+
+      </p>
+      <subsection id="Project+Website+Howto" name="Project Website Howto">
+        <p>Each project can use whatever documentation system that it chooses.
+Perhaps use a fancy documentation management system like Forrest or
+Maven, or just use simple raw html pages.
+</p>
+        <p>Keep your source documents in your project Version Control System
+under http://svn.apache.org/repos/asf/incubator/${project}/trunk/
+</p>
+        <p>To publish your site, simply "commit" your final generated documents
+to your project "site" module at
+http://svn.apache.org/repos/asf/incubator/${project}/site/
+</p>
+        <p>To update the website, your project "site" SVN module is checked-out
+on the server. Your project committers can do this step manually, or
+perhaps automate it with cron.
+</p>
+        <pre class="code">ssh people.apache.org cd /www/incubator.apache.org/${project-name}
+svn update
+</pre>
+        <p>Make sure that your subversion client is properly
+
+          <a href="http://www.apache.org/dev/version-control.html#https-svn">configured
+</a>. This vastly reduces the amount of traffic on the svn email commits,
+e.g. *.pdf
+
+        </p>
+        <p>See other notes for maintenance of
+
+          <a href="http://www.apache.org/dev/project-site.html">project websites
+</a>.
+
+        </p>
+      </subsection>
+    </section>
+    <section id="www" name="Updating the top-level website">
+      <p>How to maintain the top-level Incubator website (including the
+project status reports). See the
+
+        <a href="guides/website.html">website guide
+</a>.
+
+      </p>
+      <p>For actual project websites, see the
+
+        <a href="#project-website">Project Website Howto
+</a>above. However, this section is still relevant for projects.
+
+      </p>
+    </section>
+  </body>
+</document>

Propchange: incubator/public/trunk/site/xdocs2/howtoparticipate.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/public/trunk/site/xdocs2/howwework.xml
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site/xdocs2/howwework.xml?rev=370716&view=auto
==============================================================================
--- incubator/public/trunk/site/xdocs2/howwework.xml (added)
+++ incubator/public/trunk/site/xdocs2/howwework.xml Thu Jan 19 19:10:36 2006
@@ -0,0 +1,37 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<document>
+  <properties><!--
+
+    <meta content="HTML Tidy, see www.w3.org" name="generator"/>-->
+<!--
+
+    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type"/>-->
+
+    <title>How we work
+</title>
+    <link href="http://purl.org/DC/elements/1.0/" rel="schema.DC"/>
+  </properties>
+  <body>
+    <section id="How+we+work" name="How we work">
+      <p>Here are some notes about how we have decided to make decisions and
+changes to the way we work.
+</p>
+      <subsection id="How+we+make+decision+on+our+incubation+policies" name="How we make decision on our incubation policies">
+        <p>Apache projects usually make releases, and have deliverables. The
+code they put in is managed through lazy consensus and voting only
+when it's deemed to be required or requested.
+</p>
+        <p>Incubator releases are basically Incubated Projects' release to the
+Sponsor PMC. So how incubation is done is our "code".
+</p>
+        <p>Hence there is no need to "ratify" such rules if there seems to be
+consensus, as it's much easier to manage.
+</p>
+        <p>Because of this, we do not have the "draft" status on our policy docs
+and simply use them as our guide, that will change in need without
+having to go through tedious votes when there is good consensus.
+</p>
+      </subsection>
+    </section>
+  </body>
+</document>

Propchange: incubator/public/trunk/site/xdocs2/howwework.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/public/trunk/site/xdocs2/incubation/Incubation_Policy.xml
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site/xdocs2/incubation/Incubation_Policy.xml?rev=370716&view=auto
==============================================================================
--- incubator/public/trunk/site/xdocs2/incubation/Incubation_Policy.xml (added)
+++ incubator/public/trunk/site/xdocs2/incubation/Incubation_Policy.xml Thu Jan 19 19:10:36 2006
@@ -0,0 +1,825 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<document>
+  <properties><!--
+
+    <meta content="HTML Tidy, see www.w3.org" name="generator"/>-->
+<!--
+
+    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type"/>-->
+
+    <title>Incubation Policy
+</title>
+    <link href="http://purl.org/DC/elements/1.0/" rel="schema.DC"/>
+  </properties>
+  <body>
+    <section id="Incubation+Policy" name="Incubation Policy">
+      <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>
+      <subsection id="About+this+Document" name="About this Document">
+        <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>
+        <subsection id="Scope" name="Scope">
+          <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>
+        </subsection>
+        <subsection id="Relationship+to+Other+Documents" name="Relationship to Other Documents">
+          <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>
+        </subsection>
+      </subsection>
+      <subsection id="Changing+this+Document" name="Changing this Document">
+        <p>The contents of this document are formally approved by the Incubator
+PMC. All changes must be authorised by the Incubator PMC.
+</p>
+      </subsection>
+      <subsection id="Objectives+of+the+Process" name="Objectives of the Process">
+        <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 philophy 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>
+      </subsection>
+      <subsection id="Overview+of+the+Process" name="Overview of the Process">
+        <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>
+      </subsection>
+    </section>
+    <section id="Entry+to+Incubation" name="Entry to Incubation">
+      <p>Entry to Incubation requires a number of hurdles be passed.
+</p>
+      <subsection id="Proposal" name="Proposal">
+        <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 ("The Champion"); and
+</li>
+          <li>be approved by a Sponsor.
+</li>
+        </ul>
+        <p>Approval by a Sponsor will generally occur only after a vote within
+the Entity, and will require that the Entity be convinced that the
+Candidate is appropriate for Incubation. A Sponsor may be one of:
+</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>To start this process, a Candidate SHOULD submit a proposal to a
+Sponsor. The Proposal SHOULD, at minimum, detail the following areas :
+</p>
+        <p>
+          <strong>Need to provide a short list
+</strong>
+        </p>
+      </subsection>
+      <subsection id="Acceptance+of+Proposal+by+Sponsor" name="Acceptance of Proposal by Sponsor">
+        <p>The decision to accept a project MUST be taken on a vote by the
+Sponsor, in accordance with that Entity's charter.
+</p>
+        <p>Upon a successful result, the Sponsor SHOULD request the Incubator
+PMC take on the Candidate as a new Podling. The request to the
+Incubator PMC 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>The Incubator PMC MAY immediately accept the Candidate, or may (at
+the discretion of the Incubator PMC) require a successful VOTE by the
+Incubator PMC.
+</p>
+        <p>The nominated 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>
+      </subsection>
+      <subsection id="Creation+of+Podling" name="Creation of Podling">
+        <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>
+      </subsection>
+    </section>
+    <section id="Incubation+Activities" name="Incubation Activities">
+      <p>The following sections detail the minimum activities that must be
+undertaken by the various parties during an Incuabation process.
+</p>
+      <subsection id="Setting+Up+a+New+Podling" name="Setting Up a New Podling">
+        <p>Once the Podling and Mentor have been accepted by the Incubator PMC,
+the following activities SHOULD take place :
+</p>
+        <ul>
+          <li>creation of lists;
+</li>
+          <li>creation of cvs;
+</li>
+        </ul>
+        <ul>
+          <li>Incubator PMC mandating a helper Mentor
+</li>
+        </ul>
+      </subsection>
+      <subsection id="Ongoing+Activities" name="Ongoing Activities">
+        <p>The progress of a Podling SHALL be tracked in a "project status" file
+which SHALL be stored in the incubator/site-author/projects/
+repository 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 section
+
+            <em>Exiting the Incubator
+</em>below);
+
+          </li>
+          <li>status of Podling against exit criteria.
+</li>
+        </ul>
+        <p>The Mentor MUST ensure that the "project status" document is up to
+date at all times. See
+
+          <a href="../guides/website.html#Edit+your+project+status+report">instructions
+</a>.
+
+        </p>
+      </subsection>
+      <subsection id="Review+of+Activity" name="Review of Activity">
+        <p>Each Podling in Incubation SHALL undergo a regular review of progress
+by the Incubator PMC. Such reviews SHALL occur at least quaterly. The
+Incubator PMC MAY, at their discretion, choose to review individual
+Podlings with greater frequency. The Incubator PMC SHALL inform
+Podlings of review dates at least 4 weeks in advance.
+</p>
+        <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 escalated out of the Incubator.
+</li>
+        </ul>
+        <p>Termination and Escalation are discussed in more detail in section
+"Exiting the Incubator".
+</p>
+      </subsection>
+      <subsection id="Disputing+an+Assessment" name="Disputing an Assessment">
+        <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>
+      </subsection>
+      <subsection id="Continuation" name="Continuation">
+        <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>
+      </subsection>
+    </section>
+    <section id="Podling+Constraints" name="Podling Constraints">
+      <p>While in Incubation, Podlings are constrained in the actions they can
+undertake.
+</p>
+      <subsection id="Branding" name="Branding">
+        <p>Podlings are, by definition, not yet fully accepted as part of the
+Apache Software Foundation. Podling web sites MUST include a clear
+disclaimer on their website and in all documentation stating that
+they are in incubation.
+</p>
+        <p>Podlings SHOULD use the following text for all disclaimers :
+</p>
+        <p>
+          <em>&lt;project name&gt; is an effort undergoing incubation at the Apache
+Software Foundation (ASF), sponsored by the &lt;name of sponsor&gt;.
+Incubation is required of all newly accepted projects until a further
+review indicates that the infrastructure, communications, and
+decision making process have stabilized in a manner consistent with
+other successful ASF projects. While incubation status is not
+necessarily a reflection of the completeness or stability of the
+code, it does indicate that the project has yet to be fully endorsed
+by the ASF.
+</em>
+        </p>
+        <p>Podlings wishing to use a different disclaimer message MUST have the
+disclaimer approved by the Incubator PMC prior to use.
+</p>
+        <p>Podlings websites SHOULD contain the Apache Incubator Project logo as
+sign of affiliation.
+</p>
+      </subsection>
+      <subsection id="Releases" name="Releases">
+        <p>As podlings are not yet fully accepted as part of the Apache Software
+Foundation, any software releases (including code held in publically
+available SVN) made by Podlings will not be endorsed by the ASF.
+</p>
+        <p>However, as software releases are an important part of any software
+project, they are permitted in certain circumstances, as follows.
+</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 (Reference to Charter), 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 formally request the Incubator PMC approve such a
+release. The request SHALL have the endorsement of the Mentor.
+</p>
+        <p>Should the Incubator PMC, in accordance with (Reference to Charter)
+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>
+      </subsection>
+      <subsection id="Use+of+Apache+Resources" name="Use of Apache Resources">
+        <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>
+        <subsection id="Website" name="Website">
+          <ul>
+            <li>every project site sources stay in the project SVN
+</li>
+          </ul>
+          <ul>
+            <li>every project has this URL space where to publish the site:
+</li>
+          </ul>
+          <pre class="code">http://incubator.apache.org/projectname/
+</pre>
+          <ul>
+            <li>every project has an incubation status file under
+</li>
+          </ul>
+          <pre class="code">http://incubator.apache.org/projects/projectname.html
+</pre>
+          <ul>
+            <li>every project has eventual extra incubation docs under:
+</li>
+          </ul>
+          <pre class="code">http://incubator.apache.org/projects/projectname/**
+</pre>
+          <ul>
+            <li>The website is live in directory on www.apache.org:
+</li>
+          </ul>
+          <pre class="code">/www/incubator.apache.org/projectname
+</pre>
+          <p>To create the website, the directory
+/www/incubator.apache.org/projectname is checked out of SVN. We don't
+care how it gets into SVN, or which SVN module it lives in, but it
+had better be there. See instructions for
+
+            <a href="../howtoparticipate.html#Project+Website+Howto">project website
+</a>.
+
+          </p>
+          <p>People using Maven, ForrestBot, or any other tool still have to
+address the SVN publishing requirement that the infrastructure team
+has laid out. If that is done, then we just run "svn update" in that
+directory to load the site from SVN.
+</p>
+          <p>The Mentors MUST add the information to the project incubation status
+file, to describe the SVN module and the directory which holds the
+published site.
+</p>
+        </subsection>
+      </subsection>
+    </section>
+    <section id="Exiting+the+Incubator" name="Exiting the Incubator">
+      <p>This section describes the requirements and process for exiting the
+Incubator.
+</p>
+      <subsection id="Minimum+Exit+Requirements" name="Minimum Exit Requirements">
+        <p>Prior to escalation to the ASF, 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 Exit Criteria that, when met,
+will demonstrate these objectives.
+</p>
+        <p>Therefore, to successfully exit the Incubator and be escalated fully
+into the ASF, a Podling SHALL meet the minimum exit 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
+successfully escalated to the ASF are :
+</p>
+        <ul>
+          <li>
+            <strong>Legal
+</strong>
+          </li>
+          <li style="list-style: none">
+            <ul>
+              <li>All code ASL'ed
+</li>
+              <li>No non ASL or ASL compatbile dependencies in the code base
+</li>
+              <li>License grant complate
+</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's 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>(requriment 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
+</li>
+              <li>Project ready to comply with ASF mirroring guidlines
+</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>
+      </subsection>
+      <subsection id="Termination+of+a+Podling" name="Termination of a Podling">
+        <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>
+      </subsection>
+      <subsection id="Migration+as+a+Top+Level+Project" name="Migration as a Top Level Project">
+        <p>In cases where a Podling has successfully completed Incubation, and
+is exiting the Incubator to become a Top Level Project, the Incubator
+PMC SHALL provide a recommendation to the board that the Podling is
+ready to escalate. The recommendation SHALL include a draft
+resolution for the board to vote on.
+</p>
+      </subsection>
+      <subsection id="Migration+as+a+sub-project" name="Migration as a sub-project">
+        <p>In cases where a Podling has successfully completed Incubation, and
+is exiting the Incubator to become a sub-project within an already
+existing Top Level Project, the Incubator PMC SHALL provide a
+recommendation to the TLP that the Podling is ready to escalate.
+</p>
+      </subsection>
+      <subsection id="Post-Graduation+Check+List" name="Post-Graduation Check List">
+        <p>The list below summarizes steps a project needs to perform after
+graduation to move out of the Incubator.
+
+          <strong>PPMC
+</strong>refers to the old PPMC for the graduating project,
+
+          <strong>PMC
+</strong>refers to the new PMC under which the graduating project falls (this
+might be the former PPMC for a new TLP), and
+
+          <strong>Project
+</strong>refers to the committers on the graduating project.
+
+        </p>
+        <ul>
+          <li>Move svn repository from incubator to new location
+
+            <ul>
+              <li>PMC sends email to infrastructure@ and opens a JIRA issue requesting
+that infrastructure move the svn repository.
+</li>
+              <li>PMC updates the svn-authorization files to provide committers access
+to the newly-named repositories.
+</li>
+              <li>Project verifies all committers have commit access.
+</li>
+              <li>Project removes incubator disclaimer notices.
+</li>
+            </ul>
+          </li>
+          <li>Move web site
+
+            <ul>
+              <li>PMC emails root@ and opens a JIRA issue requesting UNIX karma for
+committers to access new location on people.apache.org.
+</li>
+              <li>Project verifies all committers know how to and have karma to update
+the new web site.
+</li>
+              <li>Project checks out/deploys the files in the new location.
+</li>
+              <li>PPMC redirects old incubator URL to the new one by editing
+https://svn.apache.org/repos/asf/incubator/public/trunk/site-publish/.
+taccess .
+</li>
+              <li>Project verifies the redirect works, then deletes old stuff at
+/www/incubator.apache.org/${PROJECT} .
+</li>
+              <li>PPMC updates http://incubator.apache.org/projects/projectname.html
+with graduation status and link to new website location.
+</li>
+            </ul>
+          </li>
+          <li>Cleanup incubator
+
+            <ul>
+              <li>PPMC updates http://incubator.apache.org/projects/index.html project
+from "Currently Incubating" to "Successfully Incubated" table.
+</li>
+            </ul>
+          </li>
+          <li>Update JIRA/Bugzilla
+
+            <ul>
+              <li>PMC emails infrastructure@ requesting that information for the
+project be updated.
+</li>
+            </ul>
+          </li>
+          <li>Move mail lists:
+
+            <ul>
+              <li>PMC sends email to infrastructure@ and opens a JIRA issue requesting
+that the mailing lists and archives be moved.
+</li>
+            </ul>
+          </li>
+          <li>If the graduating project wants to send out a press release, it must
+be cleared with the PRC.
+</li>
+        </ul>
+        <p>Additional steps for a TLP include:
+</p>
+        <ul>
+          <li>A new TLP needs board approval. The PPMC creates a proposal including
+a proposed PMC chair and sends that to the board.
+</li>
+          <li>The ASF Chairman sends out an official notice that the board has
+approved a new TLP.
+</li>
+          <li>PMC may then notify infrastructure@ about the new TLP so they can add
+DNS entries (and anything else).
+</li>
+          <li>The mentor or other member updates www.apache.org to add a link to
+the new TLP web site.
+</li>
+          <li>The mentor or other member adds the new PMC to the board reporting
+schedule (update the committee.txt file).
+</li>
+          <li>The new TLP must send monthly board reports for three months after
+approval.
+</li>
+        </ul>
+        <p>Resources include:
+</p>
+        <ul>
+          <li>
+            <a href="http://www.apache.org/dev/pmc.html">http://www.apache.org/dev/pmc.html
+</a>
+          </li>
+          <li>
+            <a href="http://www.apache.org/dev/#pmc">http://www.apache.org/dev/#pmc
+</a>
+          </li>
+        </ul>
+      </subsection>
+    </section>
+    <section id="Roles+in+the+Incubation+Process" name="Roles in the Incubation Process">
+      <p>This section describes the roles involved in the Incubation process.
+</p>
+      <subsection id="Incubator+Project+Management+Committee+%28PMC%29" name="Incubator Project Management Committee (PMC)">
+        <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>
+      </subsection>
+      <subsection id="Chair+of+the+Incubator+PMC" name="Chair of the Incubator PMC">
+        <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>
+      </subsection>
+      <subsection id="Candidate" name="Candidate">
+        <p>A project that is proposed for incubation.
+</p>
+      </subsection>
+      <subsection id="Champion" name="Champion">
+        <p>A Member of the Apache Software Foundation who supports a Candidate's
+application for Incubation and who supports and assists the Podling
+through the Incubation process.
+</p>
+      </subsection>
+      <subsection id="Sponsor" name="Sponsor">
+        <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>
+      </subsection>
+      <subsection id="Mentor" name="Mentor">
+        <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>
+      </subsection>
+      <subsection id="Committers" name="Committers">
+        <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>
+      </subsection>
+    </section>
+  </body>
+</document>

Propchange: incubator/public/trunk/site/xdocs2/incubation/Incubation_Policy.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/public/trunk/site/xdocs2/incubation/Process_Description.xml
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site/xdocs2/incubation/Process_Description.xml?rev=370716&view=auto
==============================================================================
--- incubator/public/trunk/site/xdocs2/incubation/Process_Description.xml (added)
+++ incubator/public/trunk/site/xdocs2/incubation/Process_Description.xml Thu Jan 19 19:10:36 2006
@@ -0,0 +1,258 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<document>
+  <properties><!--
+
+    <meta content="HTML Tidy, see www.w3.org" name="generator"/>-->
+<!--
+
+    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type"/>-->
+
+    <title>Process Description
+</title>
+    <link href="http://purl.org/DC/elements/1.0/" rel="schema.DC"/>
+  </properties>
+  <body>
+    <section id="The+Process+of+Incubation" name="The Process of Incubation">
+      <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>
+      <subsection id="Establishment" name="Establishment">
+        <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>
+      </subsection>
+      <subsection id="Acceptance" name="Acceptance">
+        <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>
+      </subsection>
+      <subsection id="Review" name="Review">
+        <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>
+      </subsection>
+      <subsection id="Termination" name="Termination">
+        <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>
+      </subsection>
+      <subsection id="Continuation" name="Continuation">
+        <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>
+      </subsection>
+      <subsection id="Escalation" name="Escalation">
+        <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>
+      </subsection>
+    </section>
+  </body>
+</document>

Propchange: incubator/public/trunk/site/xdocs2/incubation/Process_Description.xml
------------------------------------------------------------------------------
    svn:eol-style = native



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


Mime
View raw message