incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bay...@apache.org
Subject svn commit: r320791 - /incubator/public/trunk/site-author/projects/incubation-status-template.html
Date Thu, 13 Oct 2005 16:00:58 GMT
Author: bayard
Date: Thu Oct 13 09:00:55 2005
New Revision: 320791

URL: http://svn.apache.org/viewcvs?rev=320791&view=rev
Log:
nicely formatting with xmllint

Modified:
    incubator/public/trunk/site-author/projects/incubation-status-template.html

Modified: incubator/public/trunk/site-author/projects/incubation-status-template.html
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site-author/projects/incubation-status-template.html?rev=320791&r1=320790&r2=320791&view=diff
==============================================================================
--- incubator/public/trunk/site-author/projects/incubation-status-template.html (original)
+++ incubator/public/trunk/site-author/projects/incubation-status-template.html Thu Oct 13
09:00:55 2005
@@ -1,226 +1,278 @@
+<?xml version="1.0"?>
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
 <html>
-<head>
-<META http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
-<title>Incubation Status Template</title>
-<link href="http://purl.org/DC/elements/1.0/" rel="schema.DC"/>
-</head>
-<body>
-<h1>X Project Incubation Status TEMPLATE</h1>
-<p>This document is the template for project incubation status. </p>
-<p>What to do to set it up: </p>
-<ul>
-<li>copy this file and name it &lt;projectname&gt;.html </li>
-<li>add this page in incubator/site-author/site.xml as for other projects </li>
-<li>add a section in incubator/site-author/projects/index.html </li>
-</ul>
-<p>For this file: </p>
-<ul>
-<li>substitute the XYZ project name with the real one </li>
-<li>fill in the "Description" </li>
-<li>edit "Project info" to contain only effective resources </li>
-<li>start doing "Incubation work items" </li>
-</ul>
-<p>When an "Incubation work item" is done, place the date in the supplied space,  and
if necessary update "Project info" to reflect changes in resources. </p>
-<p>There are also sections where to place project news and incubation status reports.
</p>
-<p>
-<em>On the first edit of this file, please delete this notice.</em> 
-</p>
-<pre> -----8-&lt;---- cut here -------8-&lt;---- cut here -------8-&lt;----
cut here -------8-&lt;----  </pre>
-<h1>XYZ Project Incubation Status</h1>
-<p>This page tracks the project status, incubator-wise. For more general project status,
look on the project website. </p>
-<h1>Description</h1>
-<p>The XYZ Project is a wonderful project that does things and goes places. </p>
-<h1>News</h1>
-<ul>
-<li>none yet </li>
-</ul>
-<h1>Project info</h1>
-<ul>
-<li>link to the main website </li>
-</ul>
-<ul>
-<li>link to the page(s) that tell how to participate (Website,Mailing lists,Bug tracking,Source
code) </li>
-</ul>
-<ul>
-<li>link to the project status file (Committers,non-incubation action items,project
resources, etc) </li>
-</ul>
-<p>If the project website and code repository are not yet setup, use the following
table: </p>
-<table>
-<tr>
-<th>item               </th><th>type      </th><th>reference
                 </th>
-</tr>
-<tr>
-<td>Website            </td><td>www        </td><td><a href="http://incubator.apache.org/X/">http://incubator.apache.org/X/</a></td>
-</tr>
-<tr>
-<td>.                  </td><td>wiki       </td><td>. </td>
-</tr>
-<tr>
-<td>Mailing list       </td><td>dev        </td><td>incubator-dev@incubator.apache.org
</td>
-</tr>
-<tr>
-<td>.                  </td><td>cvs        </td><td>incubator-cvs@apache.org
</td>
-</tr>
-<tr>
-<td>Bug tracking       </td><td>.          </td><td>. </td>
-</tr>
-<tr>
-<td>Source code        </td><td>SVN        </td><td>incubator-X
</td>
-</tr>
-<tr>
-<td>Mentors            </td><td>id1        </td><td>Name1 Surname1
</td>
-</tr>
-<tr>
-<td>.                  </td><td>id2        </td><td>Name2 Surname2
</td>
-</tr>
-<tr>
-<td>Committers         </td><td>.          </td><td>. </td>
-</tr>
-<tr>
-<td>Extra              </td><td>.          </td><td>. </td>
-</tr>
-</table>
-<h1>Incubation status reports</h1>
-<ul>
-<li>none yet </li>
-</ul>
-<h1>Incubation work items</h1>
-<h2>Project Setup</h2>
-<p>This is the first phase on incubation, needed to start the project at Apache. </p>
-<p>
-<em>Item assignment is shown by the Apache id.</em> <em>Completed tasks
are shown by the completion date (YYYY-MM-dd). </em> 
-</p>
-<h3>Identify the project to be incubated&#13;
+  <head>
+    <META http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+    <title>Incubation Status Template</title>
+    <link href="http://purl.org/DC/elements/1.0/" rel="schema.DC"/>
+  </head>
+  <body>
+    <h1>X Project Incubation Status TEMPLATE</h1>
+    <p>This document is the template for project incubation status. </p>
+    <p>What to do to set it up: </p>
+    <ul>
+      <li>copy this file and name it &lt;projectname&gt;.html </li>
+      <li>add this page in incubator/site-author/site.xml as for other projects </li>
+      <li>add a section in incubator/site-author/projects/index.html </li>
+    </ul>
+    <p>For this file: </p>
+    <ul>
+      <li>substitute the XYZ project name with the real one </li>
+      <li>fill in the "Description" </li>
+      <li>edit "Project info" to contain only effective resources </li>
+      <li>start doing "Incubation work items" </li>
+    </ul>
+    <p>When an "Incubation work item" is done, place the date in the supplied space,
 and if necessary update "Project info" to reflect changes in resources. </p>
+    <p>There are also sections where to place project news and incubation status reports.
</p>
+    <p>
+      <em>On the first edit of this file, please delete this notice.</em>
+    </p>
+    <pre> -----8-&lt;---- cut here -------8-&lt;---- cut here -------8-&lt;----
cut here -------8-&lt;----  </pre>
+    <h1>XYZ Project Incubation Status</h1>
+    <p>This page tracks the project status, incubator-wise. For more general project
status, look on the project website. </p>
+    <h1>Description</h1>
+    <p>The XYZ Project is a wonderful project that does things and goes places. </p>
+    <h1>News</h1>
+    <ul>
+      <li>none yet </li>
+    </ul>
+    <h1>Project info</h1>
+    <ul>
+      <li>link to the main website </li>
+    </ul>
+    <ul>
+      <li>link to the page(s) that tell how to participate (Website,Mailing lists,Bug
tracking,Source code) </li>
+    </ul>
+    <ul>
+      <li>link to the project status file (Committers,non-incubation action items,project
resources, etc) </li>
+    </ul>
+    <p>If the project website and code repository are not yet setup, use the following
table: </p>
+    <table>
+      <tr>
+        <th>item               </th>
+        <th>type      </th>
+        <th>reference                  </th>
+      </tr>
+      <tr>
+        <td>Website            </td>
+        <td>www        </td>
+        <td>
+          <a href="http://incubator.apache.org/X/">http://incubator.apache.org/X/</a>
+        </td>
+      </tr>
+      <tr>
+        <td>.                  </td>
+        <td>wiki       </td>
+        <td>. </td>
+      </tr>
+      <tr>
+        <td>Mailing list       </td>
+        <td>dev        </td>
+        <td>incubator-dev@incubator.apache.org </td>
+      </tr>
+      <tr>
+        <td>.                  </td>
+        <td>cvs        </td>
+        <td>incubator-cvs@apache.org </td>
+      </tr>
+      <tr>
+        <td>Bug tracking       </td>
+        <td>.          </td>
+        <td>. </td>
+      </tr>
+      <tr>
+        <td>Source code        </td>
+        <td>SVN        </td>
+        <td>incubator-X </td>
+      </tr>
+      <tr>
+        <td>Mentors            </td>
+        <td>id1        </td>
+        <td>Name1 Surname1 </td>
+      </tr>
+      <tr>
+        <td>.                  </td>
+        <td>id2        </td>
+        <td>Name2 Surname2 </td>
+      </tr>
+      <tr>
+        <td>Committers         </td>
+        <td>.          </td>
+        <td>. </td>
+      </tr>
+      <tr>
+        <td>Extra              </td>
+        <td>.          </td>
+        <td>. </td>
+      </tr>
+    </table>
+    <h1>Incubation status reports</h1>
+    <ul>
+      <li>none yet </li>
+    </ul>
+    <h1>Incubation work items</h1>
+    <h2>Project Setup</h2>
+    <p>This is the first phase on incubation, needed to start the project at Apache.
</p>
+    <p>
+      <em>Item assignment is shown by the Apache id.</em>
+      <em>Completed tasks are shown by the completion date (YYYY-MM-dd). </em>
+    </p>
+    <h3>Identify the project to be incubated&#xD;
 </h3>
-<table>
-<tr>
-<th>date  </th><th>item </th>
-</tr>
-<tr>
-<td>....-..-..  </td><td>Make sure that the requested project name does
not already exist and check www.nameprotect.com to be sure that the name is not already trademarked
for an existing software product. </td>
-</tr>
-<tr>
-<td>....-..-..  </td><td>If request from an existing Apache project to
adopt an external package, then ask the Apache project for the SVN module and mail address
names. </td>
-</tr>
-<tr>
-<td>....-..-..  </td><td>If request from outside Apache to enter an existing
Apache project, then post a message to that project for them to decide on acceptance. </td>
-</tr>
-<tr>
-<td>....-..-..  </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>
-<h3>Interim responsibility</h3>
-<table>
-<tr>
-<th>date  </th><th>item </th>
-</tr>
-<tr>
-<td>....-..-..  </td><td>Identify all the Mentors for the incubation, by
asking all that can be Mentors.  </td>
-</tr>
-<tr>
-<td>....-..-..  </td><td>Subscribe all Mentors on the pmc and general lists.
 </td>
-</tr>
-<tr>
-<td>....-..-..  </td><td>Give all Mentors access to all incubator CVS modules.
(to be done by PMC chair)   </td>
-</tr>
-<tr>
-<td>....-..-..  </td><td>Tell Mentors to track progress in the file 'incubator/projects/{project.name}.html'
 </td>
-</tr>
-</table>
-<h3>Copyright</h3>
-<table>
-<tr>
-<th>date  </th><th>item </th>
-</tr>
-<tr>
-<td>....-..-..  </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>....-..-..  </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>
-<h3>Verify distribution rights</h3>
-<table>
-<tr>
-<th>date  </th><th>item </th>
-</tr>
-<tr>
-<td>....-..-..  </td><td>Check and make sure that for all code included
with the distribution that is not under the Apache license, e have the right to combine with
Apache-licensed code and redistribute.  </td>
-</tr>
-<tr>
-<td>....-..-..  </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>
-<h3>Establish a list of active committers</h3>
-<table>
-<tr>
-<th>date  </th><th>item </th>
-</tr>
-<tr>
-<td>....-..-..  </td><td>Check that all active committers have submitted
a contributors agreement.  </td>
-</tr>
-<tr>
-<td>....-..-..  </td><td>Add all active committers in the STATUS file.
 </td>
-</tr>
-<tr>
-<td>....-..-..  </td><td>Ask root for the creation of committers' accounts
on people.apache.org.  </td>
-</tr>
-</table>
-<h3>Infrastructure</h3>
-<table>
-<tr>
-<th>date  </th><th>item </th>
-</tr>
-<tr>
-<td>....-..-..  </td><td>Ask infrastructure to create source repository
modules and grant the committers karma.  </td>
-</tr>
-<tr>
-<td>....-..-..  </td><td>Ask infrastructure to set up and archive Mailing
lists.  </td>
-</tr>
-<tr>
-<td>....-..-..  </td><td>Decide about and then ask infrastructure to setup
an issuetracking system (Bugzilla, Scarab, Jira).  </td>
-</tr>
-<tr>
-<td>....-..-..  </td><td>Migrate the project to our infrastructure.  </td>
-</tr>
-</table>
-<h3>Project specific </h3>
-<p>
-<em>Add project specific tasks here.</em> 
-</p>
-<h2>Incubation </h2>
-<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>
-<h3>Collaborative Development </h3>
-<ul>
-<li>Have all of the active long-term volunteers been identified and acknowledged as
committers on the project? </li>
-<li>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>Are project decisions being made in public by the committers? </li>
-<li>Are the decision-making guidelines published and agreed to by all of the committers?
</li>
-</ul>
-<h3>Licensing awareness </h3>
-<ul>
-<li>Are all licensing, trademark, credit issues being taken care of and acknowleged
by all committers? </li>
-</ul>
-<h3>Project Specific </h3>
-<p>
-<em>Add project specific tasks here.</em> 
-</p>
-<h2>Exit </h2>
-<p>
-<em>Things to check for before voting the project out.</em> 
-</p>
-<h3>Organizational acceptance of responsibility for the project </h3>
-<ul>
-<li>If graduating to an existing PMC, has the PMC voted to accept it? </li>
-<li>If graduating to a new PMC, has the board voted to accept it? </li>
-</ul>
-<h3>Incubator sign-off </h3>
-<ul>
-<li>Has the Incubator decided that the project has accomplished all of the above tasks?
</li>
-</ul>
-</body>
+    <table>
+      <tr>
+        <th>date  </th>
+        <th>item </th>
+      </tr>
+      <tr>
+        <td>....-..-..  </td>
+        <td>Make sure that the requested project name does not already exist and check
www.nameprotect.com to be sure that the name is not already trademarked for an existing software
product. </td>
+      </tr>
+      <tr>
+        <td>....-..-..  </td>
+        <td>If request from an existing Apache project to adopt an external package,
then ask the Apache project for the SVN module and mail address names. </td>
+      </tr>
+      <tr>
+        <td>....-..-..  </td>
+        <td>If request from outside Apache to enter an existing Apache project, then
post a message to that project for them to decide on acceptance. </td>
+      </tr>
+      <tr>
+        <td>....-..-..  </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>
+    <h3>Interim responsibility</h3>
+    <table>
+      <tr>
+        <th>date  </th>
+        <th>item </th>
+      </tr>
+      <tr>
+        <td>....-..-..  </td>
+        <td>Identify all the Mentors for the incubation, by asking all that can be
Mentors.  </td>
+      </tr>
+      <tr>
+        <td>....-..-..  </td>
+        <td>Subscribe all Mentors on the pmc and general lists.  </td>
+      </tr>
+      <tr>
+        <td>....-..-..  </td>
+        <td>Give all Mentors access to all incubator CVS modules. (to be done by PMC
chair)   </td>
+      </tr>
+      <tr>
+        <td>....-..-..  </td>
+        <td>Tell Mentors to track progress in the file 'incubator/projects/{project.name}.html'
 </td>
+      </tr>
+    </table>
+    <h3>Copyright</h3>
+    <table>
+      <tr>
+        <th>date  </th>
+        <th>item </th>
+      </tr>
+      <tr>
+        <td>....-..-..  </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>....-..-..  </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>
+    <h3>Verify distribution rights</h3>
+    <table>
+      <tr>
+        <th>date  </th>
+        <th>item </th>
+      </tr>
+      <tr>
+        <td>....-..-..  </td>
+        <td>Check and make sure that for all code included with the distribution that
is not under the Apache license, e have the right to combine with Apache-licensed code and
redistribute.  </td>
+      </tr>
+      <tr>
+        <td>....-..-..  </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>
+    <h3>Establish a list of active committers</h3>
+    <table>
+      <tr>
+        <th>date  </th>
+        <th>item </th>
+      </tr>
+      <tr>
+        <td>....-..-..  </td>
+        <td>Check that all active committers have submitted a contributors agreement.
 </td>
+      </tr>
+      <tr>
+        <td>....-..-..  </td>
+        <td>Add all active committers in the STATUS file.  </td>
+      </tr>
+      <tr>
+        <td>....-..-..  </td>
+        <td>Ask root for the creation of committers' accounts on people.apache.org.
 </td>
+      </tr>
+    </table>
+    <h3>Infrastructure</h3>
+    <table>
+      <tr>
+        <th>date  </th>
+        <th>item </th>
+      </tr>
+      <tr>
+        <td>....-..-..  </td>
+        <td>Ask infrastructure to create source repository modules and grant the committers
karma.  </td>
+      </tr>
+      <tr>
+        <td>....-..-..  </td>
+        <td>Ask infrastructure to set up and archive Mailing lists.  </td>
+      </tr>
+      <tr>
+        <td>....-..-..  </td>
+        <td>Decide about and then ask infrastructure to setup an issuetracking system
(Bugzilla, Scarab, Jira).  </td>
+      </tr>
+      <tr>
+        <td>....-..-..  </td>
+        <td>Migrate the project to our infrastructure.  </td>
+      </tr>
+    </table>
+    <h3>Project specific </h3>
+    <p>
+      <em>Add project specific tasks here.</em>
+    </p>
+    <h2>Incubation </h2>
+    <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>
+    <h3>Collaborative Development </h3>
+    <ul>
+      <li>Have all of the active long-term volunteers been identified and acknowledged
as committers on the project? </li>
+      <li>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>Are project decisions being made in public by the committers? </li>
+      <li>Are the decision-making guidelines published and agreed to by all of the
committers? </li>
+    </ul>
+    <h3>Licensing awareness </h3>
+    <ul>
+      <li>Are all licensing, trademark, credit issues being taken care of and acknowleged
by all committers? </li>
+    </ul>
+    <h3>Project Specific </h3>
+    <p>
+      <em>Add project specific tasks here.</em>
+    </p>
+    <h2>Exit </h2>
+    <p>
+      <em>Things to check for before voting the project out.</em>
+    </p>
+    <h3>Organizational acceptance of responsibility for the project </h3>
+    <ul>
+      <li>If graduating to an existing PMC, has the PMC voted to accept it? </li>
+      <li>If graduating to a new PMC, has the board voted to accept it? </li>
+    </ul>
+    <h3>Incubator sign-off </h3>
+    <ul>
+      <li>Has the Incubator decided that the project has accomplished all of the above
tasks? </li>
+    </ul>
+  </body>
 </html>



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


Mime
View raw message