incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cross...@apache.org
Subject svn commit: r348873 - in /incubator/public/trunk/site-publish: guides/chair.html guides/chair.pdf incubation/Incubation_Policy.html incubation/Incubation_Policy.pdf projects/tobago.html projects/tobago.pdf
Date Fri, 25 Nov 2005 04:49:05 GMT
Author: crossley
Date: Thu Nov 24 20:48:51 2005
New Revision: 348873

URL: http://svn.apache.org/viewcvs?rev=348873&view=rev
Log:
Publish recent changes.

Modified:
    incubator/public/trunk/site-publish/guides/chair.html
    incubator/public/trunk/site-publish/guides/chair.pdf
    incubator/public/trunk/site-publish/incubation/Incubation_Policy.html
    incubator/public/trunk/site-publish/incubation/Incubation_Policy.pdf
    incubator/public/trunk/site-publish/projects/tobago.html
    incubator/public/trunk/site-publish/projects/tobago.pdf

Modified: incubator/public/trunk/site-publish/guides/chair.html
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site-publish/guides/chair.html?rev=348873&r1=348872&r2=348873&view=diff
==============================================================================
--- incubator/public/trunk/site-publish/guides/chair.html (original)
+++ incubator/public/trunk/site-publish/guides/chair.html Thu Nov 24 20:48:51 2005
@@ -313,15 +313,15 @@
    repositories (also of the incubating projects for
    oversight purposes) and are wiki admins
 
- - statuses about Incubating projects are under 
-   incubator/site/projects;  please keep the ones you are 
+ - 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/incubation/
+ - 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/
 

Modified: incubator/public/trunk/site-publish/guides/chair.pdf
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site-publish/guides/chair.pdf?rev=348873&r1=348872&r2=348873&view=diff
==============================================================================
Binary files - no diff available.

Modified: incubator/public/trunk/site-publish/incubation/Incubation_Policy.html
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site-publish/incubation/Incubation_Policy.html?rev=348873&r1=348872&r2=348873&view=diff
==============================================================================
--- incubator/public/trunk/site-publish/incubation/Incubation_Policy.html (original)
+++ incubator/public/trunk/site-publish/incubation/Incubation_Policy.html Thu Nov 24 20:48:51
2005
@@ -428,18 +428,19 @@
 </ul>
 <a name="N100A6"></a><a name="Ongoing+Activities"></a>
 <h3 class="underlined_5">Ongoing Activities&#13;</h3>
-<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>
-<a name="N100BD"></a><a name="Review+of+Activity"></a>
+<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>
+<a name="N100C1"></a><a name="Review+of+Activity"></a>
 <h3 class="underlined_5">Review of Activity</h3>
 <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>
@@ -447,7 +448,7 @@
 <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>
-<a name="N100D0"></a><a name="Disputing+an+Assessment"></a>
+<a name="N100D4"></a><a name="Disputing+an+Assessment"></a>
 <h3 class="underlined_5">Disputing an Assessment&#13;</h3>
 <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>
@@ -465,16 +466,16 @@
 <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>
-<a name="N100EE"></a><a name="Continuation"></a>
+<a name="N100F2"></a><a name="Continuation"></a>
 <h3 class="underlined_5">Continuation&#13;</h3>
 <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>
 </div>
-<a name="N100F6"></a><a name="Podling+Constraints"></a>
+<a name="N100FA"></a><a name="Podling+Constraints"></a>
 <h2 class="underlined_10">Podling Constraints&#13;</h2>
 <div class="section">
 <p>While in Incubation, Podlings are constrained in the actions they can undertake.</p>
-<a name="N100FC"></a><a name="Branding"></a>
+<a name="N10100"></a><a name="Branding"></a>
 <h3 class="underlined_5">Branding&#13;</h3>
 <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>
@@ -483,9 +484,9 @@
 </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>
-<a name="N1010B"></a><a name="Releases"></a>
+<a name="N1010F"></a><a name="Releases"></a>
 <h3 class="underlined_5">Releases&#13;</h3>
-<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>
@@ -494,13 +495,13 @@
 <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>
-<a name="N1011E"></a><a name="Use+of+Apache+Resources"></a>
+<a name="N10122"></a><a name="Use+of+Apache+Resources"></a>
 <h3 class="underlined_5">Use of Apache Resources</h3>
 <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>
-<a name="N10124"></a><a name="Website"></a>
+<a name="N10128"></a><a name="Website"></a>
 <h4>Website</h4>
 <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>
@@ -522,19 +523,15 @@
 </ul>
 <pre class="code">         /www/incubator.apache.org/projectname&#13;
 </pre>
-<p>To create the website, the directory /www/incubator.apache.org/projectname 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 /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>
 </div>
-<a name="N10150"></a><a name="Exitting+the+Incubator"></a>
+<a name="N10151"></a><a name="Exitting+the+Incubator"></a>
 <h2 class="underlined_10">Exitting the Incubator</h2>
 <div class="section">
 <p>This section describes the requirements and process for exitting the Incubator.</p>
-<a name="N10156"></a><a name="Minimum+Exit+Requirements"></a>
+<a name="N10157"></a><a name="Minimum+Exit+Requirements"></a>
 <h3 class="underlined_5">Minimum Exit Requirements</h3>
 <p>Prior to escalation to the ASF, a Podling needs to show that :</p>
 <ul>
@@ -600,10 +597,10 @@
 </li>
 <li style="list-style: none">
 <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>
@@ -612,21 +609,21 @@
 </ul>
 </li>
 </ul>
-<a name="N101C1"></a><a name="Termination+of+a+Podling"></a>
+<a name="N101C2"></a><a name="Termination+of+a+Podling"></a>
 <h3 class="underlined_5">Termination of a Podling</h3>
 <p>If you receive a recommendation for termination then you have a problem. Chances
are that there are either legal or structural problems with your project that in the opinion
of the Incubator PMC are not resolvable within a reasonable time frame. A termination decision
is basically time to close down the project. However, you do have the right to appeal a termination
decision with the Board of Directors and/or your Sponsor. You should be aware that several
Members of the Board are also Members of the Incubator PMC and as such, an appeal is unlikely
to be successful.</p>
-<a name="N101C7"></a><a name="Migration+as+a+Top+Level+Project"></a>
+<a name="N101C8"></a><a name="Migration+as+a+Top+Level+Project"></a>
 <h3 class="underlined_5">Migration as a Top Level Project</h3>
 <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>
-<a name="N101CD"></a><a name="Migration+as+a+sub-project"></a>
+<a name="N101CE"></a><a name="Migration+as+a+sub-project"></a>
 <h3 class="underlined_5">Migration as a sub-project</h3>
 <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>
-<a name="N101D3"></a><a name="Roles+in+the+Incubation+Process"></a>
+<a name="N101D4"></a><a name="Roles+in+the+Incubation+Process"></a>
 <h2 class="underlined_10">Roles in the Incubation Process</h2>
 <div class="section">
 <p>This section describes the roles involved in the Incubation process.</p>
-<a name="N101D9"></a><a name="Incubator+Project+Management+Committee+%28PMC%29"></a>
+<a name="N101DA"></a><a name="Incubator+Project+Management+Committee+%28PMC%29"></a>
 <h3 class="underlined_5">Incubator Project Management Committee (PMC)</h3>
 <p>(From the resolution that created the Incubator Project - see http://incubator.apache.org/resolution.html)</p>
 <p>The Incubator PMC is responsible for :</p>
@@ -644,16 +641,16 @@
 </ul>
 </li>
 </ul>
-<a name="N101F5"></a><a name="Chair+of+the+Incubator+PMC"></a>
+<a name="N101F6"></a><a name="Chair+of+the+Incubator+PMC"></a>
 <h3 class="underlined_5">Chair of the Incubator PMC</h3>
 <p>The person appointed by the Board of Directors to have primary responsibility for
oversight of the Incubator Project, its policies, and policy implementation.</p>
-<a name="N101FB"></a><a name="Candidate"></a>
+<a name="N101FC"></a><a name="Candidate"></a>
 <h3 class="underlined_5">Candidate</h3>
 <p>A project that is proposed for incubation.</p>
-<a name="N10201"></a><a name="Champion"></a>
+<a name="N10202"></a><a name="Champion"></a>
 <h3 class="underlined_5">Champion</h3>
 <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>
-<a name="N10207"></a><a name="Sponsor"></a>
+<a name="N10208"></a><a name="Sponsor"></a>
 <h3 class="underlined_5">Sponsor</h3>
 <p>The Sponsor is the entity within the ASF that makes the determination that a candidate
would make a worthy addition to the ASF, and agrees to take on the candidate in question (or
in the case of the Incubator PMC, assist it in finding a home) should it complete the incubation
process.</p>
 <p>A Sponsor will be one of:</p>
@@ -662,10 +659,10 @@
 <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>
-<a name="N10216"></a><a name="Mentor"></a>
+<a name="N10217"></a><a name="Mentor"></a>
 <h3 class="underlined_5">Mentor</h3>
 <p>A Mentor is a role undertaken by a permanent member of the Apache Software Foundation
and is chosen by the Sponsor to actively lead in the discharge of their duties (listed above).
Upon acceptance by the Incubator PMC, the Mentor automatically becomes a member of the Incubator
PMC. A Mentor has specific responsibilities towards the Incubator PMC, the Sponsor and towards
the members of the assigned Podling.</p>
-<a name="N1021C"></a><a name="Committers"></a>
+<a name="N1021D"></a><a name="Committers"></a>
 <h3 class="underlined_5">Committers</h3>
 <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>
 </div>

Modified: incubator/public/trunk/site-publish/incubation/Incubation_Policy.pdf
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site-publish/incubation/Incubation_Policy.pdf?rev=348873&r1=348872&r2=348873&view=diff
==============================================================================
Binary files - no diff available.

Modified: incubator/public/trunk/site-publish/projects/tobago.html
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site-publish/projects/tobago.html?rev=348873&r1=348872&r2=348873&view=diff
==============================================================================
--- incubator/public/trunk/site-publish/projects/tobago.html (original)
+++ incubator/public/trunk/site-publish/projects/tobago.html Thu Nov 24 20:48:51 2005
@@ -268,7 +268,7 @@
 <a href="#Project+info">Project info</a>
 </li>
 <li>
-<a href="#Incubation+status+reports-N100DB">Incubation status reports</a>
+<a href="#Incubation+status+reports-N100E6">Incubation status reports</a>
 </li>
 <li>
 <a href="#Incubation+work+items">Incubation work items</a>
@@ -375,13 +375,16 @@
 <td>Mailing list</td><td>dev</td><td>dev@myfaces.apache.org</td>
 </tr>
 <tr>
-<td>.</td><td>svn</td><td>svn@myfaces.apache.org</td>
+<td>.</td><td>user</td><td>user@myfaces.apache.org</td>
 </tr>
 <tr>
-<td>Bug tracking</td><td>.</td><td>.</td>
+<td>.</td><td>commits</td><td>commits@myfaces.apache.org</td>
 </tr>
 <tr>
-<td>Source code</td><td>SVN</td><td>incubator-tobago</td>
+<td>Bug tracking</td><td>jira</td><td><a href="http://issues.apache.org/jira/secure/BrowseProject.jspa?id=10600">MyFaces
Jira</a></td>
+</tr>
+<tr>
+<td>Source code</td><td>svn</td><td><a href="http://svn.apache.org/repos/asf/incubator/tobago">http://svn.apache.org/repos/asf/incubator/tobago</a></td>
 </tr>
 <tr>
 <td>Proposal</td><td>wiki</td><td><a href="http://wiki.apache.org/incubator/TobagoProposal">TobagoProposal</a></td>
@@ -424,20 +427,20 @@
 </tr>
 </table>
 </div>
-<a name="N100DB"></a><a name="Incubation+status+reports-N100DB"></a>
+<a name="N100E6"></a><a name="Incubation+status+reports-N100E6"></a>
 <h2 class="underlined_10">Incubation status reports</h2>
 <div class="section">
 <ul>
 <li>none yet</li>
 </ul>
 </div>
-<a name="N100E2"></a><a name="Incubation+work+items"></a>
+<a name="N100ED"></a><a name="Incubation+work+items"></a>
 <h2 class="underlined_10">Incubation work items</h2>
 <div class="section">
-<a name="N100E6"></a><a name="Project+Setup"></a>
+<a name="N100F1"></a><a name="Project+Setup"></a>
 <h3 class="underlined_5">Project Setup</h3>
 <p>This is the first phase on incubation, needed to start the project at Apache.</p>
-<a name="N100EC"></a><a name="Identify+the+project+to+be+incubated"></a>
+<a name="N100F7"></a><a name="Identify+the+project+to+be+incubated"></a>
 <h4>Identify the project to be incubated</h4>
 <table class="ForrestTable" cellspacing="1" cellpadding="4">
 <tr>
@@ -456,7 +459,7 @@
 <td>N/A</td><td>If request from anywhere to become a stand-alone PMC, then
assess the fit with the ASF, and create the lists and modules under the incubator address/module
names if accepted.</td>
 </tr>
 </table>
-<a name="N1010A"></a><a name="Interim+responsibility"></a>
+<a name="N10115"></a><a name="Interim+responsibility"></a>
 <h4>Interim responsibility</h4>
 <table class="ForrestTable" cellspacing="1" cellpadding="4">
 <tr>
@@ -475,7 +478,7 @@
 <td>DONE-2005-11-08</td><td>Tell Mentors to track progress in the file
'incubator/projects/tobago.html'</td>
 </tr>
 </table>
-<a name="N10128"></a><a name="Copyright"></a>
+<a name="N10133"></a><a name="Copyright"></a>
 <h4>Copyright</h4>
 <table class="ForrestTable" cellspacing="1" cellpadding="4">
 <tr>
@@ -485,23 +488,23 @@
 <td>DONE-2005-10-17</td><td>Check and make sure that the papers that transfer
rights to the ASF been received. It is only necessary to transfer rights for the package,
the core code, and any new code produced by the project.</td>
 </tr>
 <tr>
-<td>PENDING idus|mmarinschek</td><td>Check and make sure that the files
that have been donated have been updated to reflect the new ASF copyright.</td>
+<td>DONE-2005-11-24</td><td>Check and make sure that the files that have
been donated have been updated to reflect the new ASF copyright.</td>
 </tr>
 </table>
-<a name="N1013C"></a><a name="Verify+distribution+rights"></a>
+<a name="N10147"></a><a name="Verify+distribution+rights"></a>
 <h4>Verify distribution rights</h4>
 <table class="ForrestTable" cellspacing="1" cellpadding="4">
 <tr>
 <th>date</th><th>item</th>
 </tr>
 <tr>
-<td>PENDING idus|mmarinschek</td><td>Check and make sure that for all code
included with the distribution that is not under the Apache license, we have the right to
combine with Apache-licensed code and redistribute.</td>
+<td>DONE-2005-11-24</td><td>Check and make sure that for all code included
with the distribution that is not under the Apache license, we have the right to combine with
Apache-licensed code and redistribute.</td>
 </tr>
 <tr>
-<td>PENDING idus|mmarinschek</td><td>Check and make sure that all source
code distributed by the project is covered by one or more of the following approved licenses:
Apache, BSD, Artistic, MIT/X, MIT/W3C, MPL 1.1, or something with essentially the same terms.</td>
+<td>DONE-2005-11-24</td><td>Check and make sure that all source code distributed
by the project is covered by one or more of the following approved licenses: Apache, BSD,
Artistic, MIT/X, MIT/W3C, MPL 1.1, or something with essentially the same terms.</td>
 </tr>
 </table>
-<a name="N10150"></a><a name="Establish+a+list+of+active+committers+%21"></a>
+<a name="N1015B"></a><a name="Establish+a+list+of+active+committers+%21"></a>
 <h4>Establish a list of active committers !</h4>
 <table class="ForrestTable" cellspacing="1" cellpadding="4">
 <tr>
@@ -517,7 +520,7 @@
 <td>DONE-....-..-..</td><td>Ask root for the creation of committers' accounts
on cvs.apache.org.</td>
 </tr>
 </table>
-<a name="N10169"></a><a name="Infrastructure+%21"></a>
+<a name="N10174"></a><a name="Infrastructure+%21"></a>
 <h4>Infrastructure !</h4>
 <table class="ForrestTable" cellspacing="1" cellpadding="4">
 <tr>
@@ -530,53 +533,53 @@
 <td>DONE-....-..-..</td><td>Ask infrastructure to set up and archive Mailing
lists.</td>
 </tr>
 <tr>
-<td>Jira DONE-....-..-..</td><td>Decide about and then ask infrastructure
to setup an issuetracking system (Bugzilla, Scarab, Jira).</td>
+<td>DONE-....-..-..</td><td>Decide about and then ask infrastructure to
setup an issuetracking system (Bugzilla, Scarab, Jira).</td>
 </tr>
 <tr>
-<td>PENDING</td><td>Migrate the project to our infrastructure.</td>
+<td>DONE-2005-11-21</td><td>Migrate the project to our infrastructure.</td>
 </tr>
 </table>
-<a name="N10187"></a><a name="Project+specific"></a>
+<a name="N10192"></a><a name="Project+specific"></a>
 <h4>Project specific</h4>
 <p>
 <em>Add project specific tasks here.</em>
 </p>
-<a name="N1018E"></a><a name="Incubation"></a>
+<a name="N10199"></a><a name="Incubation"></a>
 <h3 class="underlined_5">Incubation</h3>
 <p>These action items have to be checked for during the whole incubation process.</p>
 <p>
 <em>These items are not to be signed as done during incubation, as they may change
during incubation.</em> <em>They are to be looked into and described in the status
reports and completed in the request for incubation signoff.</em>
 </p>
-<a name="N1019A"></a><a name="Collaborative+Development"></a>
+<a name="N101A5"></a><a name="Collaborative+Development"></a>
 <h4>Collaborative Development</h4>
 <ul>
 <li>DONE: Have all of the active long-term volunteers been identified and acknowledged
as committers on the project?</li>
 <li>DONE: Are there three or more independent committers? (The legal definition of
independent is long and boring, but basically it means that there is no binding relationship
between the individuals, such as a shared employer, that is capable of overriding their free
will as individuals, directly or indirectly.)</li>
-<li>PENDING: Are project decisions being made in public by the committers?</li>
-<li>PENDING: Are the decision-making guidelines published and agreed to by all of the
committers?</li>
+<li>DONE: Are project decisions being made in public by the committers?</li>
+<li>DONE: Are the decision-making guidelines published and agreed to by all of the
committers?</li>
 </ul>
-<a name="N101A7"></a><a name="Licensing+awareness"></a>
+<a name="N101B2"></a><a name="Licensing+awareness"></a>
 <h4>Licensing awareness</h4>
 <ul>
-<li>PENDING: Are all licensing, trademark, credit issues being taken care of and acknowleged
by all committers?</li>
+<li>DONE: Are all licensing, trademark, credit issues being taken care of and acknowleged
by all committers?</li>
 </ul>
-<a name="N101AE"></a><a name="Project+Specific"></a>
+<a name="N101B9"></a><a name="Project+Specific"></a>
 <h4>Project Specific</h4>
 <p>
 <em>Add project specific tasks here.</em>
 </p>
-<a name="N101B5"></a><a name="Exit"></a>
+<a name="N101C0"></a><a name="Exit"></a>
 <h3 class="underlined_5">Exit</h3>
 <p>
 <em>Things to check for before voting the project out.</em>
 </p>
-<a name="N101BC"></a><a name="Organizational+acceptance+of+responsibility+for+the+project"></a>
+<a name="N101C7"></a><a name="Organizational+acceptance+of+responsibility+for+the+project"></a>
 <h4>Organizational acceptance of responsibility for the project</h4>
 <ul>
 <li>DONE-2005-07-28: If graduating to an existing PMC, has the PMC voted to accept
it?</li>
 <li>N/A: If graduating to a new PMC, has the board voted to accept it?</li>
 </ul>
-<a name="N101C5"></a><a name="Incubator+sign-off"></a>
+<a name="N101D0"></a><a name="Incubator+sign-off"></a>
 <h4>Incubator sign-off</h4>
 <ul>
 <li>Has the Incubator decided that the project has accomplished all of the above tasks?</li>

Modified: incubator/public/trunk/site-publish/projects/tobago.pdf
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site-publish/projects/tobago.pdf?rev=348873&r1=348872&r2=348873&view=diff
==============================================================================
Binary files - no diff available.



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


Mime
View raw message