incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cross...@apache.org
Subject svn commit: r348654 - /incubator/public/trunk/site-author/incubation/Incubation_Policy.html
Date Thu, 24 Nov 2005 05:09:18 GMT
Author: crossley
Date: Wed Nov 23 21:09:13 2005
New Revision: 348654

URL: http://svn.apache.org/viewcvs?rev=348654&view=rev
Log:
Clarify the "project status file" and link to howto docs.
Change various CVS to SVN.
Issue: INCUBATOR-5 "status file requirement unclear"

Modified:
    incubator/public/trunk/site-author/incubation/Incubation_Policy.html

Modified: incubator/public/trunk/site-author/incubation/Incubation_Policy.html
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site-author/incubation/Incubation_Policy.html?rev=348654&r1=348653&r2=348654&view=diff
==============================================================================
--- incubator/public/trunk/site-author/incubation/Incubation_Policy.html (original)
+++ incubator/public/trunk/site-author/incubation/Incubation_Policy.html Wed Nov 23 21:09:13
2005
@@ -93,17 +93,22 @@
 </ul>
 <h2>Ongoing Activities&#13;
 </h2>
-<p>The progress of a Podling SHALL be tracked in a STATUS file.  The STATUS file SHALL
be stored in the  <em>incubator</em> module in the ASF CVS repository. </p>
-<p>The STATUS file SHALL include the following minimum content : </p>
+<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>Exitting the Incubator</em> below);
</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 STATUS file is up to date at all times. </p>
+<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>
 <h2>Review of Activity</h2>
 <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 preceeding review period.  It
is RECOMMENDED that the report be based on the STATUS file for the Podling. </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>
@@ -147,7 +152,7 @@
 <p>Podlings websites SHOULD contain the Apache Incubator Project logo as sign of affiliation.
</p>
 <h2>Releases&#13;
 </h2>
-<p>As podlings are not yet fully accepted as part of the Apache Software Foundation,
any software releases (including code held in publically available CVS) made by Podlings will
not be endorsed by the ASF. </p>
+<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>
@@ -160,7 +165,7 @@
 <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>
 <h3>Website</h3>
 <ul>
-<li>every project site sources stay in the project CVS </li>
+<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>
@@ -182,13 +187,11 @@
 </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 CVS.  We don't care how it gets into CVS, or which CVS module it lives in,
but it had better be there. </p>
-<p>People using Maven, ForrestBot, or any other tool still have to address the CVS
publishing requirement that the infrastructure team has laid out.  If that is done, then we
just run "cvs update" in that directory to load the site from CVS. </p>
-<p>The Mentors MUST add the information to the project incubation status file, to descibe
the CVS module and the directory which holds the published site. </p>
-<p>If the project does not want to host the published site in their project CVS, it
has a space under: </p>
-<pre class="code">        incubator-site/build/site/projectname/**&#13;
-</pre>
-<p>The site is automatically updated from CVS once a day. </p>
+<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>
 <h1>Exitting the Incubator</h1>
 <p>This section describes the requirements and process for exitting the Incubator.
</p>
 <h2>Minimum Exit Requirements</h2>
@@ -247,10 +250,10 @@
 <strong>Infrastructure</strong> 
 </li>
 <ul>
-<li>CVS module has been created </li>
+<li>SVN module has been created </li>
 <li>Mailing list(s) have been created </li>
 <li>Mailing lists are being archived </li>
-<li>Bugzilla has been created </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>



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


Mime
View raw message