incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ge...@apache.org
Subject svn commit: r360480 [6/7] - in /incubator/public/trunk/site: ./ docs/ docs/images/ docs/ipclearance/ lib/ lib/jdom-1.0/ lib/jdom-1.0/build/ xdocs/ xdocs/images/ xdocs/ipclearance/ xdocs/stylesheets/
Date Sun, 01 Jan 2006 08:35:39 GMT
Added: incubator/public/trunk/site/xdocs/how_to_participate.xml
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site/xdocs/how_to_participate.xml?rev=360480&view=auto
==============================================================================
--- incubator/public/trunk/site/xdocs/how_to_participate.xml (added)
+++ incubator/public/trunk/site/xdocs/how_to_participate.xml Sun Jan  1 00:35:15 2006
@@ -0,0 +1,108 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+
+<document>
+
+ <properties>
+  <title>Apache Incubator</title>
+  <author email="general@incubator.apache.org">Incubator Documentation Team</author>
+ </properties>
+
+ <body>
+
+<section name="How To Participate">
+
+      
+<subsection 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, feel free to post them on general@incubator.apache.org</p> 
+          
+<p>If you want to help in the development of a specific <a href="site:projects">Incubated Project</a>
+            refer to its development mailing list. The Incubator mailing lists are for project
+            incubation, not for project development.</p>
+            
+<p>In case of generic Project development questions, there is projects@incubator.apache.org</p>
+               
+      
+</subsection>
+
+<subsection name="Incubator Project Resources">
+         
+         
+<div class="fixme">fixme:
+      Check that all Incubator project resources are listed.</div>
+         
+<strong>Mailing lists</strong>
+
+<p>
+As with everything else in Apache, most of what goes on happens or is discussed 
+on electronic mailing lists. 
+You can find information on Incubator mailing lists <a href="mailing.html">here</a>.
+</p>
+
+<strong>Project-specific resources</strong>
+
+<p>
+<a href="/projects.html">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>
+         
+<strong>Project Website Howto</strong>
+
+<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>
+
+<strong>Updating the top-level website</strong>
+<p>How to maintain the top-level <a href="index.html">Incubator website</a>
+ (including the project status reports). See the <a href="site:guides/website">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>
+</subsection>
+</section>
+
+ </body>
+ </document>

Added: incubator/public/trunk/site/xdocs/how_we_work.xml
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site/xdocs/how_we_work.xml?rev=360480&view=auto
==============================================================================
--- incubator/public/trunk/site/xdocs/how_we_work.xml (added)
+++ incubator/public/trunk/site/xdocs/how_we_work.xml Sun Jan  1 00:35:15 2006
@@ -0,0 +1,47 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+
+<document>
+
+ <properties>
+  <title>Apache Incubator</title>
+  <author email="general@incubator.apache.org">Incubator Documentation Team</author>
+ </properties>
+
+ <body>
+
+<section 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 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
+</p>
+</subsection>
+</section>
+
+ </body>
+ </document>
+
+

Added: incubator/public/trunk/site/xdocs/images/apache-incubator-logo.png
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site/xdocs/images/apache-incubator-logo.png?rev=360480&view=auto
==============================================================================
Binary file - no diff available.

Propchange: incubator/public/trunk/site/xdocs/images/apache-incubator-logo.png
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: incubator/public/trunk/site/xdocs/incubation_policy.xml
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site/xdocs/incubation_policy.xml?rev=360480&view=auto
==============================================================================
--- incubator/public/trunk/site/xdocs/incubation_policy.xml (added)
+++ incubator/public/trunk/site/xdocs/incubation_policy.xml Sun Jan  1 00:35:15 2006
@@ -0,0 +1,434 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+
+<document>
+
+ <properties>
+  <title>Apache Incubator</title>
+  <author email="general@incubator.apache.org">Incubator Documentation Team</author>
+ </properties>
+
+ <body>
+
+<section 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 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 class="external" href="http://www.ietf.org/rfc/rfc2119.txt">RFC 2119</a>. </p>
+
+</subsection>
+<subsection 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 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 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 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 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>
+
+<strong>Entry to Incubation</strong>
+
+<p>Entry to Incubation requires a number of hurdles be passed. </p>
+
+<strong>Proposal</strong>
+
+<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>
+<strong>Acceptance of Proposal by Sponsor</strong>
+
+<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>
+
+<strong>Creation of Podling</strong>
+
+<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>
+<subsection name="Incubation Activities">
+
+<p>The following sections detail the minimum activities that must be undertaken by the various parties during an Incuabation process. </p>
+
+<strong>Setting Up a New Podling</strong>
+
+<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>
+<strong>Ongoing Activities</strong>
+
+<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>
+
+<strong>Review of Activity</strong>
+
+<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 "Exitting the Incubator". </p>
+
+<strong>Disputing an Assessment</strong>
+
+<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>
+
+<strong>Continuation</strong>
+
+<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>
+<subsection name="Podling Constraints">
+
+<p>While in Incubation, Podlings are constrained in the actions they can undertake. </p>
+
+<strong>Branding</strong>
+
+<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>
+
+<strong>Releases</strong>
+
+<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>
+
+<strong>Use of Apache Resources</strong>
+
+<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>
+
+<strong>Website</strong>
+
+<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/&#13;
+</pre>
+<ul>
+<li>every project has an incubation status file under </li>
+</ul>
+<pre class="code">        http://incubator.apache.org/projects/projectname.html&#13;
+</pre>
+<ul>
+<li>every project has eventual extra incubation docs under: </li>
+</ul>
+<pre class="code">        http://incubator.apache.org/projects/projectname/**&#13;
+</pre>
+<ul>
+<li>The website is live in directory on www.apache.org: </li>
+</ul>
+<pre class="code">         /www/incubator.apache.org/projectname&#13;
+</pre>
+<p>To create the website, the directory  <span class="codefrag">/www/incubator.apache.org/projectname</span> 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 name=">Exiting the Incubator">
+
+<p>This section describes the requirements and process for exitting the Incubator. </p>
+
+<strong>Minimum Exit Requirements</strong>
+
+<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>
+<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>
+</ul>
+<ul>
+<li>
+<strong>Meritocracy / Community</strong> 
+</li>
+<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>
+<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>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>
+</ul>
+<ul>
+<li>
+<strong>Alignment / Synergy</strong> 
+</li>
+<ul>
+<li>Use of other ASF subprojects </li>
+<li>Develop synergistic relationship with other ASF subprojects </li>
+</ul>
+</ul>
+<ul>
+<li>
+<strong>Infrastructure</strong> 
+</li>
+<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>
+</ul>
+
+</subsection>
+<subsection 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 name="Migration as a Top Level Project">
+
+<p>In cases where a Podling has successfully completed Incubation, and is exitting the Incubator to become a Top Level Project, the Incubator PMC SHALL provide a recommendation to the board that the Podling is ready to escalate.  The recommendation SHALL include a draft resolution for the board to vote on. </p>
+
+</subsection>
+<subsection name="Migration as a sub-project">
+
+<p>In cases where a Podling has successfully completed Incubation, and is exitting the Incubator to become a sub-project within an already existing Top Level Project, the Incubator PMC SHALL provide a recommendation to the TLP that the Podling is ready to escalate. </p>
+
+</subsection>
+<subsection 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/.htaccess .</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>
+</ul>
+
+</subsection>
+<subsection name="Roles in the Incubation Process">
+
+<p>This section describes the roles involved in the Incubation process. </p>
+
+<strong>Incubator Project Management Committee (PMC)</strong>
+
+<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>
+<ul>
+<li>successfully exit incubation; </li>
+<li>continue to receive guidance and support within the Incubator; or </li>
+<li>be terminated. </li>
+</ul>
+</ul>
+<strong>Chair of the Incubator PMC</strong>
+<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>
+
+<strong>>Candidate</strong>
+<p>A project that is proposed for incubation. </p>
+<strong>Champion</strong>
+<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>
+<strong>Sponsor</strong>
+<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>
+<strong>Mentor</strong>
+<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>
+<strong>Committers</strong>
+<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>

Added: incubator/public/trunk/site/xdocs/index.xml
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site/xdocs/index.xml?rev=360480&view=auto
==============================================================================
--- incubator/public/trunk/site/xdocs/index.xml (added)
+++ incubator/public/trunk/site/xdocs/index.xml Sun Jan  1 00:35:15 2006
@@ -0,0 +1,63 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+
+<document>
+
+ <properties>
+  <title>Apache Incubator</title>
+  <author email="general@incubator.apache.org">Incubator Documentation Team</author>
+ </properties>
+
+ <body>
+
+<section name="Welcome to Apache Incubator">
+
+<p>
+The Incubator project was created in October of 2002 to provide an 
+entry path to the Apache Software Foundation for projects and codebases 
+wishing to become part of the Foundation's efforts. Code donations from 
+external organisations and existing external projects wishing to move to 
+Apache will enter through the Incubator.
+</p>
+
+<p>
+A large part of the Incubator's effort will be devoted to providing 
+documentation on how the Foundation works, and how to get things done 
+within its framework. As a consequence, it is expected that the Incubator 
+will also become a reference for new contributors to any of the Apache projects.
+</p>
+
+<p>
+Since the Incubator project is one of the primary gateways into Apache 
+involvement, a lot of the documentation about the structural and 
+philosophical details of the Foundation will probably be prototyped 
+and developed right here. When they seem to accurately reflect reality 
+and cover the information they should, they'll probably be moved up to 
+the Foundation's main Web site.
+</p>
+</section>
+
+<section name="Incubator News">
+
+
+
+<p>
+    <strong>Flooga Wagie Foo Foo</strong>
+    <blockquote>
+       Blargh flopbie apsod  asod a sd ap3=0gsd sdpfo 
+      (<i>2005-11-08</i>)
+    </blockquote>
+</p>
+
+<p>
+<i>Archived articles are <a href="newshistory.html">here</a></i>.
+</p>
+
+ </section>
+
+ </body>
+ </document>
+
+
+
+
+

Added: incubator/public/trunk/site/xdocs/ipclearance/index.xml
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site/xdocs/ipclearance/index.xml?rev=360480&view=auto
==============================================================================
--- incubator/public/trunk/site/xdocs/ipclearance/index.xml (added)
+++ incubator/public/trunk/site/xdocs/ipclearance/index.xml Sun Jan  1 00:35:15 2006
@@ -0,0 +1,117 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+
+<document>
+
+ <properties>
+  <title>Apache Incubator</title>
+  <author email="general@incubator.apache.org">Incubator Documentation Team</author>
+ </properties>
+
+ <body>
+
+<section name="Intellectual Property Clearance">
+
+<p>
+One of the Incubator's roles is to ensure that proper attention is paid
+to intellectual property.  From time to time, an external codebase is brought
+into the ASF that is not a separate
+<a href="/projects.html">incubating project</a>
+but still represents a
+substantial contribution that was not developed within the ASF's source
+control system.  This is a short form of the Incubation checklist, designed
+to allow code to be imported with alacrity while still providing for oversight. 
+</p>
+
+<p>
+This form is not for new projects.  The intent is to simply help to ensure,
+and record, that due diligence (Software Grant, CLA, Corp CLA, license and
+dependencies) has been paid to the incoming code, so that it can be merged
+into an existing project/module. 
+</p>
+
+<p>
+The receiving PMC is responsible for doing the work.  The Incubator is
+simply the repository of the needed information.  Once a PMC directly
+checks-in a filled-out short form, everything is done. 
+</p>
+
+<p>
+All PMCs must handle incoming code in this way.  Any code that was
+developed outside of the ASF SVN/CVS repository must be processed like this,
+even if the external developer is an ASF committer. 
+</p>
+
+<p>
+For new situations, use the
+<a href="/ipclearance/iptemplate.html">template</a>
+and follow its instructions.
+</p>
+
+<table>
+    <tr>
+      <th colspan="1" rowspan="1">Clearance document</th>
+      <th colspan="1" rowspan="1">Receiving PMC</th>
+      <th colspan="1" rowspan="1">Date recorded</th>
+    </tr>
+    <tr>
+      <td colspan="1" rowspan="1">
+        <a href="myfaces-tobago.html">myfaces-tobago</a>
+      </td>
+      <td colspan="1" rowspan="1">Apache MyFaces</td>
+      <td colspan="1" rowspan="1">2005-12-20</td>
+    </tr>
+    <tr>
+      <td colspan="1" rowspan="1">
+        <a href="geronimo-1111-trifork-initial.html">geronimo-1111-trifork-initial</a>
+      </td>
+      <td colspan="1" rowspan="1">Apache Geronimo</td>
+      <td colspan="1" rowspan="1">2005-10-27</td>
+    </tr>
+    <tr>
+      <td colspan="1" rowspan="1">
+        <a href="geronimo-1016-ibm-daytrader.html">geronimo-1016-ibm-daytrader</a>
+      </td>
+      <td colspan="1" rowspan="1">Apache Geronimo</td>
+      <td colspan="1" rowspan="1">2005-09-20</td>
+    </tr>
+    <tr>
+      <td colspan="1" rowspan="1">
+        <a href="geronimo-875-ibm-eclipse.html">geronimo-875-ibm-eclipse</a>
+      </td>
+      <td colspan="1" rowspan="1">Apache Geronimo</td>
+      <td colspan="1" rowspan="1">2005-08-16</td>
+    </tr>
+    <tr>
+      <td colspan="1" rowspan="1">
+        <a href="geronimo-762-ibm-console.html">geronimo-762-ibm-console</a>
+      </td>
+      <td colspan="1" rowspan="1">Apache Geronimo</td>
+      <td colspan="1" rowspan="1">2005-07-14</td>
+    </tr>
+    <tr>
+      <td colspan="1" rowspan="1">
+        <a href="geronimo-iiop.html">geronimo-iiop</a>
+      </td>
+      <td colspan="1" rowspan="1">Apache Geronimo</td>
+      <td colspan="1" rowspan="1">2005-01-15</td>
+    </tr>
+    <tr>
+      <td colspan="1" rowspan="1">
+        <a href="apr-jlibtool.html">apr-jlibtool</a>
+      </td>
+      <td colspan="1" rowspan="1">Apache Portable Runtime (APR)</td>
+      <td colspan="1" rowspan="1">2004-07-08</td>
+    </tr>
+    <tr>
+      <td colspan="1" rowspan="1">
+        <a href="portals-gluecode-jetspeed.html">portals-gluecode-jetspeed</a>
+      </td>
+      <td colspan="1" rowspan="1">Apache Portals</td>
+      <td colspan="1" rowspan="1">2004-06-27</td>
+    </tr>
+</table>
+
+</section>
+
+ </body>
+ </document>

Added: incubator/public/trunk/site/xdocs/license.xml
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site/xdocs/license.xml?rev=360480&view=auto
==============================================================================
--- incubator/public/trunk/site/xdocs/license.xml (added)
+++ incubator/public/trunk/site/xdocs/license.xml Sun Jan  1 00:35:15 2006
@@ -0,0 +1,225 @@
+<?xml version="1.0"?>
+
+<document>
+ <properties>
+  <title>Apache License</title>
+  <author email="harmony-dev@incubator.apache.org">
+     Harmony Documentation Team</author>
+ </properties>
+
+<body>
+<section name="Apache License v2.0">
+
+<source test=""><![CDATA[
+
+
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   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.
+
+
+ ]]></source>
+
+</section>
+</body>
+</document>
+

Added: incubator/public/trunk/site/xdocs/mailing.xml
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site/xdocs/mailing.xml?rev=360480&view=auto
==============================================================================
--- incubator/public/trunk/site/xdocs/mailing.xml (added)
+++ incubator/public/trunk/site/xdocs/mailing.xml Sun Jan  1 00:35:15 2006
@@ -0,0 +1,96 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+
+<!--
+
+    Copyright 2004 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.
+-->
+
+<document>
+
+ <properties>
+  <title>Apache Incubator Mailing Lists</title>
+  <author email="genreal@incubator.apache.org">Incubator Documentation Team</author>
+ </properties>
+
+<body>
+<section name="Apache Incubator Mailling Lists">
+
+<p>
+Apache Incubator mailing lists operate under the following terms :
+</p>
+
+<blockquote>
+This forum has been created for public communication about projects
+of The Apache Software Foundation (the "Foundation"), a Delaware
+nonprofit corporation classified as a public charity under 501(c)(3).
+All communication intentionally submitted to the Foundation on this
+forum is considered a Contribution to the Foundation unless otherwise
+noted in the communication. The terms and conditions that apply to
+your Contributions are defined by either a contributor license
+agreement (CLA) signed by you and/or your employer or, if no such CLA
+is on file at the Foundation, by the terms and conditions of
+Contributions as defined by the Apache License, Version 2.0.
+</blockquote>
+>
+ 
+<p>
+Further :
+</p>
+
+<blockquote>
+<ul>
+<li>
+If you do not wish your post to be a Contribution, we would prefer that you do not post it.  However, in the
+event that you do, please mark as "NOT A CONTRIBUTION" at the top of the posting.
+</li>
+<li>
+Do not post any code that is not your original work, or code that you do not have 
+clear authorization to contribute.
+</li>
+</ul>
+</blockquote>
+<p>
+There is currently one publicly available mailing list for Incubator :
+</p>
+
+<subsection name="General Mailing List">
+
+<p>This is where general and public discussion of things about the project 
+                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><a href="mailto:general-subscribe@incubator.apache.org">Subscribe</a> to general@incubator.apache.org</li>
+  <li><a href="mailto:general-unsubscribe@incubator.apache.org">Unsubscribe</a> from genral@incubator.apache.org</li>
+  <li><a href="mailto:general-digest-subscribe@incubator.apache.org">Digest Subscribe</a>
+       to the digest of genral@incubator.apache.org</li>
+  <li>View the <a href="http://mail-archives.apache.org/mod_mbox/incubator-general/">general@incubator.apache.org archives</a></li>
+</ul>
+
+</subsection>
+
+<subsection name="Other Mailing Lists">
+
+<p>The Incubator PMC has a mailing list to resolve any administrative issues,
+This list is limited to PMC members.</p>
+
+</subsection>
+</section>
+</body>
+</document>
+

Added: incubator/public/trunk/site/xdocs/newshistory.xml
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site/xdocs/newshistory.xml?rev=360480&view=auto
==============================================================================
--- incubator/public/trunk/site/xdocs/newshistory.xml (added)
+++ incubator/public/trunk/site/xdocs/newshistory.xml Sun Jan  1 00:35:15 2006
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+
+<document>
+
+ <properties>
+  <title>Apache Harmony</title>
+  <author email="harmony-dev@incubtaor.apache.org">Harmony Documentation Team</author>
+ </properties>
+
+ <body>
+
+<section name="Older Harmony News">
+
+ </section>
+
+ </body>
+ </document>
+
+
+
+
+

Added: incubator/public/trunk/site/xdocs/pmc_guide.xml
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site/xdocs/pmc_guide.xml?rev=360480&view=auto
==============================================================================
--- incubator/public/trunk/site/xdocs/pmc_guide.xml (added)
+++ incubator/public/trunk/site/xdocs/pmc_guide.xml Sun Jan  1 00:35:15 2006
@@ -0,0 +1,73 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+
+<document>
+
+ <properties>
+  <title>Apache Incubator</title>
+  <author email="general@incubator.apache.org">Incubator Documentation Team</author>
+ </properties>
+
+ <body>
+
+<section name="PMC Guide">
+
+<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="site:howtoparticipate">how to participate</a>. </p>
+<p>For further information, see the  <a href="ext:apache/dev/pmc">Apache FAQ for PMC members</a>
+</p>
+
+<subsection 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|incubator,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="site:guides/website">instructions</a> for updating the
+website.
+</p>
+<ul>
+<li>
+<a href="site:incubator/statustemplate">incubator/site-author/projects/incubation-status-template.html</a>
+</li>
+</ul>
+<p>3. Make sure the  <a href="site:guides/chair">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 name="IP Clearance template">
+
+<p>
+<a href="/ipclearance/iptemplate.html">incubator/site-author/ip-clearance/ip-clearance-template.html</a>
+</p>
+<p>
+See list of other
+<a href="/ipclearance/index.html">IP Clearance documents</a>.
+</p>
+
+</subsection>
+</section>
+
+</body>
+</document>

Added: incubator/public/trunk/site/xdocs/process_description.xml
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site/xdocs/process_description.xml?rev=360480&view=auto
==============================================================================
--- incubator/public/trunk/site/xdocs/process_description.xml (added)
+++ incubator/public/trunk/site/xdocs/process_description.xml Sun Jan  1 00:35:15 2006
@@ -0,0 +1,71 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+
+<document>
+
+ <properties>
+  <title>Apache Incubator</title>
+  <author email="general@incubator.apache.org">Incubator Documentation Team</author>
+ </properties>
+
+ <body>
+
+<section name="Process Description">
+
+<subsection 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="site:incubation/rolesandersponsibilities">Roles and Responsibilities </a>document for a description of the various parties involved in the Incubation process. </p>
+
+</subsection>
+<subsection 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 Apache site to find similar projects.  Spend some time reading both the projects' web pages and mailing lists.  By simply lurking on the mailing lists (see Mailing Lists section  in this document), you may get ideas about who you would like to ask to help you with your project proposal.  However, Champions must either be ASF   <a href="ext:apache/foundation/members">members </a>or  <a href="ext:apache/foundation/officers">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 establi
 shed. </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 Mailing Lists section in this document).  See the  <a class="external" 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 class="external" 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 (either pmc@{project-name}.apache.org or board@apache.org; see Mailing List 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 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 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 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 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 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>



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


Mime
View raw message