incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cross...@apache.org
Subject cvs commit: incubator-site/build/site/incubation Incubation_Policy.html Incubation_Policy.pdf
Date Sat, 11 Sep 2004 06:34:34 GMT
crossley    2004/09/10 23:34:34

  Modified:    build/site/incubation Incubation_Policy.html
                        Incubation_Policy.pdf
  Log:
  Enhance the website production instructions.
  
  Revision  Changes    Path
  1.14      +18 -19    incubator-site/build/site/incubation/Incubation_Policy.html
  
  Index: Incubation_Policy.html
  ===================================================================
  RCS file: /home/cvs/incubator-site/build/site/incubation/Incubation_Policy.html,v
  retrieving revision 1.13
  retrieving revision 1.14
  diff -u -r1.13 -r1.14
  --- Incubation_Policy.html	3 Sep 2004 04:12:56 -0000	1.13
  +++ Incubation_Policy.html	11 Sep 2004 06:34:34 -0000	1.14
  @@ -641,22 +641,21 @@
   </ul>
   <pre class="code">         /www/incubator.apache.org/projectname
   </pre>
  -<p>
  -<span class="codefrag">/www/incubator.apache.org/projectname</span> has to
be 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 up in that directory to load the site from CVS. </p>
  -<p>The Mentors MUST add the information about the CVS module and dir where the published
site is, in the project incubation status file. </p>
  -<p>If the project does not want to host the published site in their CVS, it has a
space under: </p>
  +<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/**
   </pre>
  -<p>The site is automatically updated from there once a day. </p>
  +<p>The site is automatically updated from CVS once a day. </p>
   </div>
   </div>
   </div>
  -<a name="N10149"></a><a name="Exitting+the+Incubator"></a>
  +<a name="N1014A"></a><a name="Exitting+the+Incubator"></a>
   <h3>Exitting the Incubator</h3>
   <div style="margin-left: 0 ; border: 2px">
   <p>This section describes the requirements and process for exitting the Incubator.
</p>
  -<a name="N1014F"></a><a name="Minimum+Exit+Requirements"></a>
  +<a name="N10150"></a><a name="Minimum+Exit+Requirements"></a>
   <h4>Minimum Exit Requirements</h4>
   <div style="margin-left: 0 ; border: 2px">
   <p>Prior to escalation to the ASF, a Podling needs to show that : </p>
  @@ -726,27 +725,27 @@
   </ul>
   </ul>
   </div>
  -<a name="N101B4"></a><a name="Termination+of+a+Podling"></a>
  +<a name="N101B5"></a><a name="Termination+of+a+Podling"></a>
   <h4>Termination of a Podling</h4>
   <div style="margin-left: 0 ; border: 2px">
   <p>If you receive a recommendation for termination then you have a problem.  Chances
are that there are either legal or structural problems with your project that in the opinion
of the Incubator PMC are not resolvable within a reasonable time frame.  A termination decision
is basically time to close down the project. However, you do have the right to appeal a termination
decision with the Board of Directors and/or your Sponsor.  You should be aware that several
Members of the Board are also Members of the Incubator PMC and as such, an appeal is unlikely
to be successful.  </p>
   </div>
  -<a name="N101BA"></a><a name="Migration+as+a+Top+Level+Project"></a>
  +<a name="N101BB"></a><a name="Migration+as+a+Top+Level+Project"></a>
   <h4>Migration as a Top Level Project</h4>
   <div style="margin-left: 0 ; border: 2px">
   <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>
   </div>
  -<a name="N101C0"></a><a name="Migration+as+a+sub-project"></a>
  +<a name="N101C1"></a><a name="Migration+as+a+sub-project"></a>
   <h4>Migration as a sub-project</h4>
   <div style="margin-left: 0 ; border: 2px">
   <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>
   </div>
   </div>
  -<a name="N101C6"></a><a name="Roles+in+the+Incubation+Process"></a>
  +<a name="N101C7"></a><a name="Roles+in+the+Incubation+Process"></a>
   <h3>Roles in the Incubation Process</h3>
   <div style="margin-left: 0 ; border: 2px">
   <p>This section describes the roles involved in the Incubation process. </p>
  -<a name="N101CC"></a><a name="Incubator+Project+Management+Committee+%28PMC%29"></a>
  +<a name="N101CD"></a><a name="Incubator+Project+Management+Committee+%28PMC%29"></a>
   <h4>Incubator Project Management Committee (PMC)</h4>
   <div style="margin-left: 0 ; border: 2px">
   <p>(From the resolution that created the Incubator Project - see http://incubator.apache.org/resolution.html)
</p>
  @@ -764,22 +763,22 @@
   </ul>
   </ul>
   </div>
  -<a name="N101E6"></a><a name="Chair+of+the+Incubator+PMC"></a>
  +<a name="N101E7"></a><a name="Chair+of+the+Incubator+PMC"></a>
   <h4>Chair of the Incubator PMC</h4>
   <div style="margin-left: 0 ; border: 2px">
   <p>The person appointed by the Board of Directors to have primary responsibility
for oversight of the Incubator Project, its policies, and policy implementation. </p>
   </div>
  -<a name="N101EC"></a><a name="Candidate"></a>
  +<a name="N101ED"></a><a name="Candidate"></a>
   <h4>Candidate</h4>
   <div style="margin-left: 0 ; border: 2px">
   <p>A project that is proposed for incubation. </p>
   </div>
  -<a name="N101F2"></a><a name="Champion"></a>
  +<a name="N101F3"></a><a name="Champion"></a>
   <h4>Champion</h4>
   <div style="margin-left: 0 ; border: 2px">
   <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>
   </div>
  -<a name="N101F8"></a><a name="Sponsor"></a>
  +<a name="N101F9"></a><a name="Sponsor"></a>
   <h4>Sponsor</h4>
   <div style="margin-left: 0 ; border: 2px">
   <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>
  @@ -790,12 +789,12 @@
   <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>
   </div>
  -<a name="N10207"></a><a name="Mentor"></a>
  +<a name="N10208"></a><a name="Mentor"></a>
   <h4>Mentor</h4>
   <div style="margin-left: 0 ; border: 2px">
   <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>
   </div>
  -<a name="N1020D"></a><a name="Committers"></a>
  +<a name="N1020E"></a><a name="Committers"></a>
   <h4>Committers</h4>
   <div style="margin-left: 0 ; border: 2px">
   <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>
  
  
  
  1.10      +110 -110  incubator-site/build/site/incubation/Incubation_Policy.pdf
  
  	<<Binary file>>
  
  

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


Mime
View raw message