incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cross...@apache.org
Subject svn commit: r373682 [5/20] - in /incubator/public/trunk: ./ lib/ site-author/ site-author/guides/ site-author/images/ site-author/incubation/ site-author/ip-clearance/ site-author/learn/ site-author/projects/ site-author/projects/TEMP_HTML/ site-author...
Date Tue, 31 Jan 2006 03:23:57 GMT
Copied: incubator/public/trunk/site-author/ip-clearance/ip-clearance-template.xml (from r373662, incubator/public/trunk/site-author/ip-clearance/ip-clearance-template.html)
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site-author/ip-clearance/ip-clearance-template.xml?p2=incubator/public/trunk/site-author/ip-clearance/ip-clearance-template.xml&p1=incubator/public/trunk/site-author/ip-clearance/ip-clearance-template.html&r1=373662&r2=373682&rev=373682&view=diff
==============================================================================
--- incubator/public/trunk/site-author/ip-clearance/ip-clearance-template.html (original)
+++ incubator/public/trunk/site-author/ip-clearance/ip-clearance-template.xml Mon Jan 30 19:21:03 2006
@@ -1,100 +1,214 @@
-<!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>XYZ Codebase Intellectual Property (IP) Clearance Status</title>
-<link href="http://purl.org/DC/elements/1.0/" rel="schema.DC">
-</head>
-<body>
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<document>
+  <properties><!--
 
-<!-- Start of instruction notice -->
-<h1>Codebase IP Clearance TEMPLATE</h1>
-<p>This document is the template for recording IP clearance on new codebases.
-Please store the completed document in this Incubator repository
-using a filename that reflects your project.
-</p>
-<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 project, 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 repository must be processed like this, even if the external developer is an ASF committer. </p>
-<p>What to do to set it up: </p>
-<ul>
-<li>copy this file and re-name it according to incubator/site-author/ip-clearance/${project-codebase}.html </li>
-<li>add a row to the table at incubator/site-author/ip-clearance/index.html </li>
-<li>make a snapshot of the source code available for review </li>
-</ul>
-<p>This file should not last long in place before it is moved to the successful incubation area.  The sole purpose is to ensure that IP is cleared so that the codebase can be merged into the ASF SVN. </p>
-<p>For this file: </p>
-<ul>
-<li>substitute the XYZ name with the real one </li>
-<li>fill in the description </li>
-<li>fill in the work items </li>
-<li>remove this notice</li>
-<li>set a proper "title" element for the html page</li>
-</ul>
-<p>When a work item is done, place the date in the supplied space. </p>
-<p>
-<em>On the first edit of this file, please delete this notice.</em> 
-</p>
-<!-- End of instruction notice -->
-<pre> -----8-&lt;---- cut here -------8-&lt;---- cut here -------8-&lt;---- cut here -------8-&lt;----  </pre>
+    <meta content="HTML Tidy, see www.w3.org" name="generator"/>-->
+<!--
+
+    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type"/>-->
 
-<h1>XYZ Codebase Intellectual Property (IP) Clearance Status</h1>
-<h1>Description</h1>
-<p>Describe the incoming codebase, including whether it is a large set of patches, new functional modules, etc. </p>
-<h1>Project info</h1>
-<ul>
-<li>Which PMC will be responsible for the code </li>
-</ul>
-<ul>
-<li>Into which existing project/module </li>
-</ul>
-<p>
-<em>Completed tasks are shown by the completion date (YYYY-MM-dd). </em> 
-</p>
-<h2>Identify the codebase</h2>
-<table>
-<tr>
-<th>date  </th><th>item </th>
-</tr>
-<tr>
-<td>....-..-..  </td><td>If applicable, make sure that any associated 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>
-</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 that all active committers have a signed CLA on record.  </td>
-</tr>
-<tr>
-<td>....-..-..  </td><td>Remind active committers that they are responsible for ensuring that a Corporate CLA is recorded if such is is required to authorize their contributions under their individual CLA. </td>
-</tr>
-<tr>
-<td>....-..-..  </td><td>Check and make sure that for all items 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>....-..-..  </td><td>Check and make sure that all items depended upon 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>
-<p>Generally, the result of checking off these items will be a Software Grant, CLA, and Corporate CLA for ASF licensed code, which must have no dependencies upon items whose licenses that are incompatible with the Apache License. </p>
-<h2>Organizational acceptance of responsibility for the project </h2>
-<ul>
-<li>Has the receiving PMC voted to accept it? </li>
-</ul>
-</body>
-</html>
+    <title>XYZ Codebase Intellectual Property (IP) Clearance Status
+</title>
+    <link href="http://purl.org/DC/elements/1.0/" rel="schema.DC"/>
+  </properties>
+  <body>
+    <section id="Codebase+IP+Clearance+TEMPLATE">
+      <title>Codebase IP Clearance TEMPLATE
+</title>
+      <p>This document is the template for recording IP clearance on new
+codebases. Please store the completed document in this Incubator
+repository using a filename that reflects your project.
+</p>
+      <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 project, 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 repository must be processed like
+this, even if the external developer is an ASF committer.
+</p>
+      <p>What to do to set it up:
+</p>
+      <ul>
+        <li>copy this file and re-name it according to
+incubator/site-author/ip-clearance/${project-codebase}.html
+</li>
+        <li>add a row to the table at
+incubator/site-author/ip-clearance/index.html
+</li>
+        <li>make a snapshot of the source code available for review
+</li>
+      </ul>
+      <p>This file should not last long in place before it is moved to the
+successful incubation area. The sole purpose is to ensure that IP is
+cleared so that the codebase can be merged into the ASF SVN.
+</p>
+      <p>For this file:
+</p>
+      <ul>
+        <li>substitute the XYZ name with the real one
+</li>
+        <li>fill in the description
+</li>
+        <li>fill in the work items
+</li>
+        <li>remove this notice
+</li>
+        <li>set a proper "title" element for the html page
+</li>
+      </ul>
+      <p>When a work item is done, place the date in the supplied space.
+</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>
+    </section>
+    <section id="XYZ+Codebase+Intellectual+Property+%28IP%29+Clearance+Status">
+      <title>XYZ Codebase Intellectual Property (IP) Clearance Status
+</title>
+    </section>
+    <section id="Description">
+      <title>Description
+</title>
+      <p>Describe the incoming codebase, including whether it is a large set
+of patches, new functional modules, etc.
+</p>
+    </section>
+    <section id="Project+info">
+      <title>Project info
+</title>
+      <ul>
+        <li>Which PMC will be responsible for the code
+</li>
+      </ul>
+      <ul>
+        <li>Into which existing project/module
+</li>
+      </ul>
+      <p>
+        <em>Completed tasks are shown by the completion date (YYYY-MM-dd).
+</em>
+      </p>
+      <section id="Identify+the+codebase">
+        <title>Identify the codebase
+</title>
+        <table>
+          <tr>
+            <th>date
+</th>
+            <th>item
+</th>
+          </tr>
+          <tr>
+            <td>....-..-..
+</td>
+            <td>If applicable, make sure that any associated 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>
+        </table>
+        <section id="Copyright">
+          <title>Copyright
+</title>
+          <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>
+        </section>
+        <section id="Verify+distribution+rights">
+          <title>Verify distribution rights
+</title>
+          <table>
+            <tr>
+              <th>date
+</th>
+              <th>item
+</th>
+            </tr>
+            <tr>
+              <td>....-..-..
+</td>
+              <td>Check that all active committers have a signed CLA on record.
+</td>
+            </tr>
+            <tr>
+              <td>....-..-..
+</td>
+              <td>Remind active committers that they are responsible for ensuring that
+a Corporate CLA is recorded if such is is required to authorize their
+contributions under their individual CLA.
+</td>
+            </tr>
+            <tr>
+              <td>....-..-..
+</td>
+              <td>Check and make sure that for all items 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>....-..-..
+</td>
+              <td>Check and make sure that all items depended upon 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>
+          <p>Generally, the result of checking off these items will be a Software
+Grant, CLA, and Corporate CLA for ASF licensed code, which must have
+no dependencies upon items whose licenses that are incompatible with
+the Apache License.
+</p>
+        </section>
+      </section>
+      <section id="Organizational+acceptance+of+responsibility+for+the+project">
+        <title>Organizational acceptance of responsibility for the project
+</title>
+        <ul>
+          <li>Has the receiving PMC voted to accept it?
+</li>
+        </ul>
+      </section>
+    </section>
+  </body>
+</document>

Copied: incubator/public/trunk/site-author/ip-clearance/myfaces-tobago.xml (from r373662, incubator/public/trunk/site-author/ip-clearance/myfaces-tobago.html)
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site-author/ip-clearance/myfaces-tobago.xml?p2=incubator/public/trunk/site-author/ip-clearance/myfaces-tobago.xml&p1=incubator/public/trunk/site-author/ip-clearance/myfaces-tobago.html&r1=373662&r2=373682&rev=373682&view=diff
==============================================================================
--- incubator/public/trunk/site-author/ip-clearance/myfaces-tobago.html (original)
+++ incubator/public/trunk/site-author/ip-clearance/myfaces-tobago.xml Mon Jan 30 19:21:03 2006
@@ -1,84 +1,147 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head>
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<document>
+  <properties><!--
 
+    <meta content="HTML Tidy, see www.w3.org" name="generator"/>-->
+<!--
 
-<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>MyFaces Tobago Codebase Intellectual Property (IP) Clearance Status</title>
+    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type"/>-->
 
-<link href="http://purl.org/DC/elements/1.0/" rel="schema.DC"></head><body>
-
-<h1>MyFaces Tobago Codebase Intellectual Property (IP) Clearance Status</h1>
-<h1>Description</h1>
-<p>Tobago is a JSF based web development architecture consisting of a well
-designed set of user interface components that will become part of MyFaces.</p>
-<h1>Project info</h1>
-<ul>
-<li>Which PMC will be responsible for the code: Apache MyFaces PMC </li>
-</ul>
-<ul>
-<li>Into which existing project/module: Apache MyFaces </li>
-</ul>
-<p>
-<em>Completed tasks are shown by the completion date (YYYY-MM-dd). </em> 
+    <title>MyFaces Tobago Codebase Intellectual Property (IP) Clearance Status
+</title>
+    <link href="http://purl.org/DC/elements/1.0/" rel="schema.DC"/>
+  </properties>
+  <body>
+    <section id="MyFaces+Tobago+Codebase+Intellectual+Property+%28IP%29+Clearance+Status">
+      <title>MyFaces Tobago Codebase Intellectual Property (IP) Clearance Status
+</title>
+    </section>
+    <section id="Description">
+      <title>Description
+</title>
+      <p>Tobago is a JSF based web development architecture consisting of a
+well designed set of user interface components that will become part
+of MyFaces.
 </p>
-<h2>Identify the codebase</h2>
-<table>
-<tbody><tr>
-<th>date  </th><th>item </th>
-</tr>
-<tr>
-<td>DONE  </td><td>If applicable, make sure that any associated
-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>
-</tbody></table>
-<h3>Copyright</h3>
-<table>
-<tbody><tr>
-<th>date  </th><th>item </th>
-</tr>
-<tr>
-<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>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>
-</tbody></table>
-<h3>Verify distribution rights</h3>
-<table>
-<tbody><tr>
-<th>date  </th><th>item </th>
-</tr>
-<tr>
-<td>DONE-2005-10-17  </td><td>Check that all active committers have a signed CLA on record.  </td>
-</tr>
-<tr>
-<td>N/A  </td><td>Remind active committers that they are
-responsible for ensuring that a Corporate CLA is recorded if such is is
-required to authorize their contributions under their individual CLA. </td>
-</tr>
-<tr>
-<td>DONE-2005-11-24  </td><td>Check and make sure that for all items
-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>DONE-2005-11-24  </td><td>Check and make sure that all items depended
-upon 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>
-</tbody></table>
-<p>Generally, the result of checking off these items will be a Software
-Grant, CLA, and Corporate CLA for ASF licensed code, which must have no
-dependencies upon items whose licenses that are incompatible with the
-Apache License. </p>
-<h2>Organizational acceptance of responsibility for the project </h2>
-<ul>
-<li>Has the receiving PMC voted to accept it? DONE-2005-07-28</li>
-</ul>
-
-</body></html>
+    </section>
+    <section id="Project+info">
+      <title>Project info
+</title>
+      <ul>
+        <li>Which PMC will be responsible for the code: Apache MyFaces PMC
+</li>
+      </ul>
+      <ul>
+        <li>Into which existing project/module: Apache MyFaces
+</li>
+      </ul>
+      <p>
+        <em>Completed tasks are shown by the completion date (YYYY-MM-dd).
+</em>
+      </p>
+      <section id="Identify+the+codebase">
+        <title>Identify the codebase
+</title>
+        <table>
+          <tr>
+            <th>date
+</th>
+            <th>item
+</th>
+          </tr>
+          <tr>
+            <td>DONE
+</td>
+            <td>If applicable, make sure that any associated 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>
+        </table>
+        <section id="Copyright">
+          <title>Copyright
+</title>
+          <table>
+            <tr>
+              <th>date
+</th>
+              <th>item
+</th>
+            </tr>
+            <tr>
+              <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>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>
+        </section>
+        <section id="Verify+distribution+rights">
+          <title>Verify distribution rights
+</title>
+          <table>
+            <tr>
+              <th>date
+</th>
+              <th>item
+</th>
+            </tr>
+            <tr>
+              <td>DONE-2005-10-17
+</td>
+              <td>Check that all active committers have a signed CLA on record.
+</td>
+            </tr>
+            <tr>
+              <td>N/A
+</td>
+              <td>Remind active committers that they are responsible for ensuring that
+a Corporate CLA is recorded if such is is required to authorize their
+contributions under their individual CLA.
+</td>
+            </tr>
+            <tr>
+              <td>DONE-2005-11-24
+</td>
+              <td>Check and make sure that for all items 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>DONE-2005-11-24
+</td>
+              <td>Check and make sure that all items depended upon 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>
+          <p>Generally, the result of checking off these items will be a Software
+Grant, CLA, and Corporate CLA for ASF licensed code, which must have
+no dependencies upon items whose licenses that are incompatible with
+the Apache License.
+</p>
+        </section>
+      </section>
+      <section id="Organizational+acceptance+of+responsibility+for+the+project">
+        <title>Organizational acceptance of responsibility for the project
+</title>
+        <ul>
+          <li>Has the receiving PMC voted to accept it? DONE-2005-07-28
+</li>
+        </ul>
+      </section>
+    </section>
+  </body>
+</document>

Copied: incubator/public/trunk/site-author/ip-clearance/portals-gluecode-jetspeed.xml (from r373662, incubator/public/trunk/site-author/ip-clearance/portals-gluecode-jetspeed.cwiki)
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site-author/ip-clearance/portals-gluecode-jetspeed.xml?p2=incubator/public/trunk/site-author/ip-clearance/portals-gluecode-jetspeed.xml&p1=incubator/public/trunk/site-author/ip-clearance/portals-gluecode-jetspeed.cwiki&r1=373662&r2=373682&rev=373682&view=diff
==============================================================================
--- incubator/public/trunk/site-author/ip-clearance/portals-gluecode-jetspeed.cwiki (original)
+++ incubator/public/trunk/site-author/ip-clearance/portals-gluecode-jetspeed.xml Mon Jan 30 19:21:03 2006
@@ -1,51 +1,149 @@
-!!! XYZ Codebase IP Clearance Status
-
-!!! Description
-
-The incoming code was contributed by Gluecode Software.
-It is contributing to the Jetspeed codebase as a patch.
-The patch is installed in the jakarta-jetspeed CVS, under the directory 'fusion'.
-Fusion is an optional feature for Jetspeed-1. It provides support for 'JSR-168' Portlets in Jetspeed-1.
-This feature allows for portlets to be deployed in a standard Portlet Application to Jetspeed-1, and 
-run inside a Java Portlet API-compliant portlet container. 
-Fusion leverages Jetspeed-2 components and pipelines embedded in the Jetspeed-1 server.
-Fusion was written by a Jetspeed contributor for hire, David S Taylor.
-
-!!! Project info
-
-* Which PMC will be responsible for the code
-
-Apache Portals PMC
-
-* Into which existing project/module
-
-Jetspeed (Jetspeed-1)
-  
-'' Completed tasks are shown by the completion date (YYYY-MM-dd). ''
-
-!! Identify the codebase
-
-|| date || item
-| 2004-06-27 | Codebase is a patch to jetspeed CVS.
-
-!! Copyright
-
-|| date || item
-| 2004-06-25 | Software Grant form received by Geir Magnusson Jr
-| 2004-06-25 | Files that have been donated have been updated to reflect the new ASF copyright.
-
-!! Verify distribution rights
-
-|| date || item
-| 2004-06-25 | Check that all active committers have a signed CLA on record
-| 2004-06-25 | Remind active committers that they are responsible for ensuring that a Corporate CLA is recorded if such is is required to authorize their contributions under their individual CLA.
-| 2004-06-25 | Check and make sure that for all items included with the distribution that is not under the Apache license, we have the right to combine with Apache-licensed code and redistribute. 
-| 2004-06-25 | Check and make sure that all items depended upon 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.
-
-Generally, the result of checking off these items will be a Software Grant, CLA, and Corporate CLA for ASF licensed code, which must have no dependencies upon items whose licenses that are incompatible with the Apache License.
-
-!!! Organizational acceptance of responsibility for the project 
-
-* Has the receiving PMC voted to accept it?
-
-No
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<document>
+  <properties>
+    <title>portals-gluecode-jetspeed
+</title>
+  </properties>
+  <body>
+    <section id="XYZ+Codebase+IP+Clearance+Status">
+      <title>XYZ Codebase IP Clearance Status
+</title>
+    </section>
+    <section id="Description">
+      <title>Description
+</title>
+      <p>The incoming code was contributed by Gluecode Software. It is
+contributing to the Jetspeed codebase as a patch. The patch is
+installed in the jakarta-jetspeed CVS, under the directory 'fusion'.
+Fusion is an optional feature for Jetspeed-1. It provides support for
+'JSR-168' Portlets in Jetspeed-1. This feature allows for portlets to
+be deployed in a standard Portlet Application to Jetspeed-1, and run
+inside a Java Portlet API-compliant portlet container. Fusion
+leverages Jetspeed-2 components and pipelines embedded in the
+Jetspeed-1 server. Fusion was written by a Jetspeed contributor for
+hire, David S Taylor.
+</p>
+    </section>
+    <section id="Project+info">
+      <title>Project info
+</title>
+      <ul>
+        <li>Which PMC will be responsible for the code
+</li>
+      </ul>
+      <p>Apache Portals PMC
+</p>
+      <ul>
+        <li>Into which existing project/module
+</li>
+      </ul>
+      <p>Jetspeed (Jetspeed-1)
+</p>
+      <p>
+        <em>Completed tasks are shown by the completion date (YYYY-MM-dd).
+</em>
+      </p>
+      <section id="Identify+the+codebase">
+        <title>Identify the codebase
+</title>
+        <table>
+          <tr>
+            <th>date
+</th>
+            <th>item
+</th>
+          </tr>
+          <tr>
+            <td>2004-06-27
+</td>
+            <td>Codebase is a patch to jetspeed CVS.
+</td>
+          </tr>
+        </table>
+      </section>
+      <section id="Copyright">
+        <title>Copyright
+</title>
+        <table>
+          <tr>
+            <th>date
+</th>
+            <th>item
+</th>
+          </tr>
+          <tr>
+            <td>2004-06-25
+</td>
+            <td>Software Grant form received by Geir Magnusson Jr
+</td>
+          </tr>
+          <tr>
+            <td>2004-06-25
+</td>
+            <td>Files that have been donated have been updated to reflect the new ASF
+copyright.
+</td>
+          </tr>
+        </table>
+      </section>
+      <section id="Verify+distribution+rights">
+        <title>Verify distribution rights
+</title>
+        <table>
+          <tr>
+            <th>date
+</th>
+            <th>item
+</th>
+          </tr>
+          <tr>
+            <td>2004-06-25
+</td>
+            <td>Check that all active committers have a signed CLA on record
+</td>
+          </tr>
+          <tr>
+            <td>2004-06-25
+</td>
+            <td>Remind active committers that they are responsible for ensuring that
+a Corporate CLA is recorded if such is is required to authorize their
+contributions under their individual CLA.
+</td>
+          </tr>
+          <tr>
+            <td>2004-06-25
+</td>
+            <td>Check and make sure that for all items 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>2004-06-25
+</td>
+            <td>Check and make sure that all items depended upon 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>
+        <p>Generally, the result of checking off these items will be a Software
+Grant, CLA, and Corporate CLA for ASF licensed code, which must have
+no dependencies upon items whose licenses that are incompatible with
+the Apache License.
+</p>
+      </section>
+    </section>
+    <section id="Organizational+acceptance+of+responsibility+for+the+project">
+      <title>Organizational acceptance of responsibility for the project
+</title>
+      <ul>
+        <li>Has the receiving PMC voted to accept it?
+</li>
+      </ul>
+      <p>No
+</p>
+    </section>
+  </body>
+</document>

Copied: incubator/public/trunk/site-author/ip-clearance/ws-sandesha.xml (from r373662, incubator/public/trunk/site-author/ip-clearance/ws-sandesha.cwiki)
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site-author/ip-clearance/ws-sandesha.xml?p2=incubator/public/trunk/site-author/ip-clearance/ws-sandesha.xml&p1=incubator/public/trunk/site-author/ip-clearance/ws-sandesha.cwiki&r1=373662&r2=373682&rev=373682&view=diff
==============================================================================
--- incubator/public/trunk/site-author/ip-clearance/ws-sandesha.cwiki (original)
+++ incubator/public/trunk/site-author/ip-clearance/ws-sandesha.xml Mon Jan 30 19:21:03 2006
@@ -1,43 +1,135 @@
-!!! Sandesha Codebase IP Clearance Status
-
-!!! Description
-
-The incoming code was contributed by University of Moratun. The code is currently in ws-fx/sandesha CVS. It implements WS-ReliableMessaging standard for use with Apache Axis.
-
-!!! Project info
-
-* Which PMC will be responsible for the code
-
-Apache Web Services PMC
-
-* Into which existing project/module
-
-WS-FX
-  
-'' Completed tasks are shown by the completion date (YYYY-MM-dd). ''
-
-!! Identify the codebase
-
-|| date || item
-| 2004-05-02 | Codebase has been checked into WS-FX/Sandesha CVS.
-
-!! Copyright
-
-|| date || item
-| 2004-01-23 | Software Grant form received by Jim
-
-!! Verify distribution rights
-
-|| date || item
-| 2004-01-23 | Software Grant form received by Jim
-| 2004-07-23 | Remind active committers that they are responsible for ensuring that a Corporate CLA is recorded if such is is required to authorize their contributions under their individual CLA.
-| 2004-07-23 | Check and make sure that for all items included with the distribution that is not under the Apache license, we have the right to combine with Apache-licensed code and redistribute. 
-| 2004-07-23 | Check and make sure that all items depended upon 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.
-
-Generally, the result of checking off these items will be a Software Grant, CLA, and Corporate CLA for ASF licensed code, which must have no dependencies upon items whose licenses that are incompatible with the Apache License.
-
-!!! Organizational acceptance of responsibility for the project 
-
-* Has the receiving PMC voted to accept it?
-
-YES
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<document>
+  <properties>
+    <title>ws-sandesha
+</title>
+  </properties>
+  <body>
+    <section id="Sandesha+Codebase+IP+Clearance+Status">
+      <title>Sandesha Codebase IP Clearance Status
+</title>
+    </section>
+    <section id="Description">
+      <title>Description
+</title>
+      <p>The incoming code was contributed by University of Moratun. The code
+is currently in ws-fx/sandesha CVS. It implements
+WS-ReliableMessaging standard for use with Apache Axis.
+</p>
+    </section>
+    <section id="Project+info">
+      <title>Project info
+</title>
+      <ul>
+        <li>Which PMC will be responsible for the code
+</li>
+      </ul>
+      <p>Apache Web Services PMC
+</p>
+      <ul>
+        <li>Into which existing project/module
+</li>
+      </ul>
+      <p>WS-FX
+</p>
+      <p>
+        <em>Completed tasks are shown by the completion date (YYYY-MM-dd).
+</em>
+      </p>
+      <section id="Identify+the+codebase">
+        <title>Identify the codebase
+</title>
+        <table>
+          <tr>
+            <th>date
+</th>
+            <th>item
+</th>
+          </tr>
+          <tr>
+            <td>2004-05-02
+</td>
+            <td>Codebase has been checked into WS-FX/Sandesha CVS.
+</td>
+          </tr>
+        </table>
+      </section>
+      <section id="Copyright">
+        <title>Copyright
+</title>
+        <table>
+          <tr>
+            <th>date
+</th>
+            <th>item
+</th>
+          </tr>
+          <tr>
+            <td>2004-01-23
+</td>
+            <td>Software Grant form received by Jim
+</td>
+          </tr>
+        </table>
+      </section>
+      <section id="Verify+distribution+rights">
+        <title>Verify distribution rights
+</title>
+        <table>
+          <tr>
+            <th>date
+</th>
+            <th>item
+</th>
+          </tr>
+          <tr>
+            <td>2004-01-23
+</td>
+            <td>Software Grant form received by Jim
+</td>
+          </tr>
+          <tr>
+            <td>2004-07-23
+</td>
+            <td>Remind active committers that they are responsible for ensuring that
+a Corporate CLA is recorded if such is is required to authorize their
+contributions under their individual CLA.
+</td>
+          </tr>
+          <tr>
+            <td>2004-07-23
+</td>
+            <td>Check and make sure that for all items 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>2004-07-23
+</td>
+            <td>Check and make sure that all items depended upon 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>
+        <p>Generally, the result of checking off these items will be a Software
+Grant, CLA, and Corporate CLA for ASF licensed code, which must have
+no dependencies upon items whose licenses that are incompatible with
+the Apache License.
+</p>
+      </section>
+    </section>
+    <section id="Organizational+acceptance+of+responsibility+for+the+project">
+      <title>Organizational acceptance of responsibility for the project
+</title>
+      <ul>
+        <li>Has the receiving PMC voted to accept it?
+</li>
+      </ul>
+      <p>YES
+</p>
+    </section>
+  </body>
+</document>

Copied: incubator/public/trunk/site-author/ip-clearance/ws-wss4j.xml (from r373662, incubator/public/trunk/site-author/ip-clearance/ws-wss4j.cwiki)
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site-author/ip-clearance/ws-wss4j.xml?p2=incubator/public/trunk/site-author/ip-clearance/ws-wss4j.xml&p1=incubator/public/trunk/site-author/ip-clearance/ws-wss4j.cwiki&r1=373662&r2=373682&rev=373682&view=diff
==============================================================================
--- incubator/public/trunk/site-author/ip-clearance/ws-wss4j.cwiki (original)
+++ incubator/public/trunk/site-author/ip-clearance/ws-wss4j.xml Mon Jan 30 19:21:03 2006
@@ -1,43 +1,136 @@
-!!! WSS4J Codebase IP Clearance Status
-
-!!! Description
-
-The incoming code was contributed by Werner Dittmann and Davanum Srinivas. The code is currently in ws-fx/wss4j CVS. It implements several standards defined by OASIS Web Services Security TC for use with Apache Axis.
-
-!!! Project info
-
-* Which PMC will be responsible for the code
-
-Apache Web Services PMC
-
-* Into which existing project/module
-
-WS-FX
-  
-'' Completed tasks are shown by the completion date (YYYY-MM-dd). ''
-
-!! Identify the codebase
-
-|| date || item
-| 2004-02-24 | Codebase has been checked into WS-FX/wss4j CVS.
-
-!! Copyright
-
-|| date || item
-| 2004-02-23 | Software Grant form received by Jim
-
-!! Verify distribution rights
-
-|| date || item
-| 2004-02-24 | Software Grant form received by Jim
-| 2004-07-23 | Remind active committers that they are responsible for ensuring that a Corporate CLA is recorded if such is is required to authorize their contributions under their individual CLA.
-| 2004-07-23 | Check and make sure that for all items included with the distribution that is not under the Apache license, we have the right to combine with Apache-licensed code and redistribute. 
-| 2004-07-23 | Check and make sure that all items depended upon 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.
-
-Generally, the result of checking off these items will be a Software Grant, CLA, and Corporate CLA for ASF licensed code, which must have no dependencies upon items whose licenses that are incompatible with the Apache License.
-
-!!! Organizational acceptance of responsibility for the project 
-
-* Has the receiving PMC voted to accept it?
-
-YES
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<document>
+  <properties>
+    <title>ws-wss4j
+</title>
+  </properties>
+  <body>
+    <section id="WSS4J+Codebase+IP+Clearance+Status">
+      <title>WSS4J Codebase IP Clearance Status
+</title>
+    </section>
+    <section id="Description">
+      <title>Description
+</title>
+      <p>The incoming code was contributed by Werner Dittmann and Davanum
+Srinivas. The code is currently in ws-fx/wss4j CVS. It implements
+several standards defined by OASIS Web Services Security TC for use
+with Apache Axis.
+</p>
+    </section>
+    <section id="Project+info">
+      <title>Project info
+</title>
+      <ul>
+        <li>Which PMC will be responsible for the code
+</li>
+      </ul>
+      <p>Apache Web Services PMC
+</p>
+      <ul>
+        <li>Into which existing project/module
+</li>
+      </ul>
+      <p>WS-FX
+</p>
+      <p>
+        <em>Completed tasks are shown by the completion date (YYYY-MM-dd).
+</em>
+      </p>
+      <section id="Identify+the+codebase">
+        <title>Identify the codebase
+</title>
+        <table>
+          <tr>
+            <th>date
+</th>
+            <th>item
+</th>
+          </tr>
+          <tr>
+            <td>2004-02-24
+</td>
+            <td>Codebase has been checked into WS-FX/wss4j CVS.
+</td>
+          </tr>
+        </table>
+      </section>
+      <section id="Copyright">
+        <title>Copyright
+</title>
+        <table>
+          <tr>
+            <th>date
+</th>
+            <th>item
+</th>
+          </tr>
+          <tr>
+            <td>2004-02-23
+</td>
+            <td>Software Grant form received by Jim
+</td>
+          </tr>
+        </table>
+      </section>
+      <section id="Verify+distribution+rights">
+        <title>Verify distribution rights
+</title>
+        <table>
+          <tr>
+            <th>date
+</th>
+            <th>item
+</th>
+          </tr>
+          <tr>
+            <td>2004-02-24
+</td>
+            <td>Software Grant form received by Jim
+</td>
+          </tr>
+          <tr>
+            <td>2004-07-23
+</td>
+            <td>Remind active committers that they are responsible for ensuring that
+a Corporate CLA is recorded if such is is required to authorize their
+contributions under their individual CLA.
+</td>
+          </tr>
+          <tr>
+            <td>2004-07-23
+</td>
+            <td>Check and make sure that for all items 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>2004-07-23
+</td>
+            <td>Check and make sure that all items depended upon 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>
+        <p>Generally, the result of checking off these items will be a Software
+Grant, CLA, and Corporate CLA for ASF licensed code, which must have
+no dependencies upon items whose licenses that are incompatible with
+the Apache License.
+</p>
+      </section>
+    </section>
+    <section id="Organizational+acceptance+of+responsibility+for+the+project">
+      <title>Organizational acceptance of responsibility for the project
+</title>
+      <ul>
+        <li>Has the receiving PMC voted to accept it?
+</li>
+      </ul>
+      <p>YES
+</p>
+    </section>
+  </body>
+</document>

Copied: incubator/public/trunk/site-author/learn/index.xml (from r373662, incubator/public/trunk/site-author/learn/index.html)
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site-author/learn/index.xml?p2=incubator/public/trunk/site-author/learn/index.xml&p1=incubator/public/trunk/site-author/learn/index.html&r1=373662&r2=373682&rev=373682&view=diff
==============================================================================
--- incubator/public/trunk/site-author/learn/index.html (original)
+++ incubator/public/trunk/site-author/learn/index.xml Mon Jan 30 19:21:03 2006
@@ -1,37 +1,53 @@
-<!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>Apache Incubator Project</title>
-<link href="http://purl.org/DC/elements/1.0/" rel="schema.DC">
-<meta content="The Apache Incubator Project" name="DC.Creator">
-<meta content="Documentation which is under development." name="DC.Description">
-</head>
-<body>
-    
-<h1>Prototype Documentation Under Development</h1>
-      
-      
-<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 will be moved up to the Foundation's
-      main Web site.</p>
-
-<p>See the main documentation at
-  <a href="ext:apache/dev">http://www.apache.org/dev/</a>
-  which is generally directed at all committers and PMCs, including
-  those in Incubation. There is also relevant information at
-  <a href="ext:apache/foundation">http://www.apache.org/foundation/</a>
-  especially 
-  <a href="ext:how-it-works">ASF: How it works</a>.
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<document>
+  <properties><!--
+
+    <meta content="HTML Tidy, see www.w3.org" name="generator"/>-->
+<!--
+
+    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type"/>-->
+
+    <title>Apache Incubator Project
+</title>
+    <link href="http://purl.org/DC/elements/1.0/" rel="schema.DC"/><!--
+
+    <meta content="The Apache Incubator Project" name="DC.Creator"/>-->
+<!--
+
+    <meta content="Documentation which is under development." name="DC.Description"/>-->
+
+  </properties>
+  <body>
+    <section id="Prototype+Documentation+Under+Development">
+      <title>Prototype Documentation Under Development
+</title>
+      <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 will be
+moved up to the Foundation's main Web site.
 </p>
+      <p>See the main documentation at
+
+        <a href="http://www.apache.org/dev/">http://www.apache.org/dev/
+</a>which is generally directed at all committers and PMCs, including
+those in Incubation. There is also relevant information at
+
+        <a href="http://www.apache.org/foundation/">http://www.apache.org/foundation/
+</a>especially
+
+        <a href="http://www.apache.org/foundation/how-it-works.html">ASF: How it works
+</a>.
+
+      </p>
+      <p>See
 
-<p>See <a href="site:about/howtoparticipate">Updating the
-        Documentation</a> for instructions on how to submit
-      modifications to this Incubator site.</p>
+        <a href="../howtoparticipate.html">Updating the Documentation
+</a>for instructions on how to submit modifications to this Incubator
+site.
 
-</body>
-</html>
+      </p>
+    </section>
+  </body>
+</document>

Copied: incubator/public/trunk/site-author/learn/mailing-lists.xml (from r373662, incubator/public/trunk/site-author/learn/mailing-lists.html)
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site-author/learn/mailing-lists.xml?p2=incubator/public/trunk/site-author/learn/mailing-lists.xml&p1=incubator/public/trunk/site-author/learn/mailing-lists.html&r1=373662&r2=373682&rev=373682&view=diff
==============================================================================
--- incubator/public/trunk/site-author/learn/mailing-lists.html (original)
+++ incubator/public/trunk/site-author/learn/mailing-lists.xml Mon Jan 30 19:21:03 2006
@@ -1,44 +1,65 @@
-<!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>Apache Mailing Lists</title>
-<link href="http://purl.org/DC/elements/1.0/" rel="schema.DC">
-<meta content="The Apache Incubator Project" name="DC.Creator">
-</head>
-<body>
-    
-<h1>Apache-Wide Mailing Lists</h1>
-      
-      
-<p>Everything -- but <em>everything</em> -- inside the Apache
-      world occurs or is reflected in email.  As some people say,
-      'If it isn't in my email, it didn't happen.'  In addition to
-      the <em>per</em>-project and special-group mailing lists,
-      there are a few that cross all boundaries:</p>
-      
-<ul>
-        
-<li>
-<strong>committers</strong>: sends important messages to all Apache committers; 
-           it's not used for discussions</li>
-        
-<li>
-<strong>community</strong>: where all Apache committers can discuss 
-            things that are about Apache;</li>
-        
-<li>
-<strong>infrastucture</strong>: where the roots and the infrastructure team
-            discuss and work on the Apache infrastructure needs;</li>
-        
-<li>
-<strong>repository</strong>: discussions about the Apache artifact repository</li>
-        
-<li>
-<strong>party</strong>: where people plan about how to have fun :-)</li>
-      
-</ul>
-    
-  
-</body>
-</html>
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<document>
+  <properties><!--
+
+    <meta content="HTML Tidy, see www.w3.org" name="generator"/>-->
+<!--
+
+    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type"/>-->
+
+    <title>Apache Mailing Lists
+</title>
+    <link href="http://purl.org/DC/elements/1.0/" rel="schema.DC"/><!--
+
+    <meta content="The Apache Incubator Project" name="DC.Creator"/>-->
+
+  </properties>
+  <body>
+    <section id="Apache-Wide+Mailing+Lists">
+      <title>Apache-Wide Mailing Lists
+</title>
+      <p>Everything -- but
+
+        <em>everything
+</em>-- inside the Apache world occurs or is reflected in email. As some
+people say, 'If it isn't in my email, it didn't happen.' In addition
+to the
+
+        <em>per
+</em>-project and special-group mailing lists, there are a few that cross
+all boundaries:
+
+      </p>
+      <ul>
+        <li>
+          <strong>committers
+</strong>: sends important messages to all Apache committers; it's not used
+for discussions
+
+        </li>
+        <li>
+          <strong>community
+</strong>: where all Apache committers can discuss things that are about
+Apache;
+
+        </li>
+        <li>
+          <strong>infrastucture
+</strong>: where the roots and the infrastructure team discuss and work on the
+Apache infrastructure needs;
+
+        </li>
+        <li>
+          <strong>repository
+</strong>: discussions about the Apache artifact repository
+
+        </li>
+        <li>
+          <strong>party
+</strong>: where people plan about how to have fun :-)
+
+        </li>
+      </ul>
+    </section>
+  </body>
+</document>

Copied: incubator/public/trunk/site-author/learn/newcommitters.xml (from r373662, incubator/public/trunk/site-author/learn/newcommitters.html)
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site-author/learn/newcommitters.xml?p2=incubator/public/trunk/site-author/learn/newcommitters.xml&p1=incubator/public/trunk/site-author/learn/newcommitters.html&r1=373662&r2=373682&rev=373682&view=diff
==============================================================================
--- incubator/public/trunk/site-author/learn/newcommitters.html (original)
+++ incubator/public/trunk/site-author/learn/newcommitters.xml Mon Jan 30 19:21:03 2006
@@ -1,55 +1,71 @@
-<!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>Apache Incubator: Voting in a new committer</title>
-</head>
-<body>
-
-<h1>Voting in a new committer</h1>
-
-<p>
-  If a developer has contributed a signicant number of high-quality
-  patches, is interested in continuing the contribution, has
-  demonstrated the ability to work well with others under the
-  Apache guidelines, it may be proposed to grant that developer
-  <a href="http://www.apache.org/foundation/glossary.html#CommitAccess">commit access</a>.
-  See also the ASF How it Works document which explains
-  <a href="http://www.apache.org/foundation/how-it-works.html#roles">meritocracy</a>
-  and
-  <a href="http://www.apache.org/foundation/how-it-works.html#roles">roles</a>.
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<document>
+  <properties><!--
+
+    <meta content="HTML Tidy, see www.w3.org" name="generator"/>-->
+<!--
+
+    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type"/>-->
+
+    <title>Apache Incubator: Voting in a new committer
+</title>
+  </properties>
+  <body>
+    <section id="Voting+in+a+new+committer">
+      <title>Voting in a new committer
+</title>
+      <p>If a developer has contributed a signicant number of high-quality
+patches, is interested in continuing the contribution, has
+demonstrated the ability to work well with others under the Apache
+guidelines, it may be proposed to grant that developer
+
+        <a href="http://www.apache.org/foundation/glossary.html#CommitAccess">commit access
+</a>. See also the ASF How it Works document which explains
+
+        <a href="http://www.apache.org/foundation/how-it-works.html#roles">meritocracy
+</a>and
+
+        <a href="http://www.apache.org/foundation/how-it-works.html#roles">roles
+</a>.
+
+      </p>
+      <p>Discussion of a potential new committer should take place on the
+project's PPMC list (normally, it would take place on a project's PMC
+list). After vetting the new candidate, the vote can take place
+either on the PPMC list (with notice posted to the Incubator PMC
+list) or on the developer list (with a notice posted to the
+Incubator's general list). The latter practice of a private
+discussion followed by a public, pro-forma, vote is re-emerging as a
+Best Practice for ASF projects.
 </p>
-
-<p>
-  Discussion of a potential new committer should take place on the project's
-  PPMC list (normally, it would take place on a project's PMC list).
-  After vetting the new candidate, the vote can take place either on the
-  PPMC list (with notice posted to the Incubator PMC list) or on the developer
-  list (with a notice posted to the Incubator's general list).  The latter
-  practice of a private discussion followed by a public, pro-forma, vote
-  is re-emerging as a Best Practice for ASF projects.
-</p>
-
-<h1>Welcome!</h1>
-
-<p>
-  If the vote (only votes cast by PMC/PPMC members are binding) is positive,
-  the contributor formally becomes an Apache
-  <a href="http://www.apache.org/foundation/glossary.html#Committer">committer</a>.
-  A (P)PMC member should then follow the
-  <a href="http://www.apache.org/dev/pmc.html">documented procedures**</a>
-  to complete the process.
-</p>
-
-<p><i>** Please CC both the Incubator PMC and the PPMC when sending the necessary
-  e-mails to root.</i>
-</p>
-
-<p>Also, please direct the new committer to the
-  <a href="http://www.apache.org/dev/">Apache developer's pages</a> and to the
-  <a href="http://incubator.apache.org/">Apache Incubator site</a>
-  for important additional information.
-</p>
-
-</body>
-</html>
+    </section>
+    <section id="Welcome%21">
+      <title>Welcome!
+</title>
+      <p>If the vote (only votes cast by PMC/PPMC members are binding) is
+positive, the contributor formally becomes an Apache
+
+        <a href="http://www.apache.org/foundation/glossary.html#Committer">committer
+</a>. A (P)PMC member should then follow the
+
+        <a href="http://www.apache.org/dev/pmc.html">documented procedures**
+</a>to complete the process.
+
+      </p>
+      <p>
+        <em>** Please CC both the Incubator PMC and the PPMC when sending the
+necessary e-mails to root.
+</em>
+      </p>
+      <p>Also, please direct the new committer to the
+
+        <a href="http://www.apache.org/dev/">Apache developer's pages
+</a>and to the
+
+        <a href="http://incubator.apache.org/">Apache Incubator site
+</a>for important additional information.
+
+      </p>
+    </section>
+  </body>
+</document>

Modified: incubator/public/trunk/site-author/learn/rules-for-revolutionaries.xml
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site-author/learn/rules-for-revolutionaries.xml?rev=373682&r1=373681&r2=373682&view=diff
==============================================================================
--- incubator/public/trunk/site-author/learn/rules-for-revolutionaries.xml (original)
+++ incubator/public/trunk/site-author/learn/rules-for-revolutionaries.xml Mon Jan 30 19:21:03 2006
@@ -1,182 +1,135 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE document PUBLIC
-  "-//APACHE//DTD Documentation V1.1//EN"
-  "document-v11.dtd">
+<?xml version="1.0" encoding="ISO-8859-1"?>
 <document>
-  <header>
-    <title>Apache Archive: Rules for Revolutionaries</title>
-
+  <properties>
+    <title>Apache Archive: Rules for Revolutionaries
+</title>
     <authors>
-      <person name="James Duncan Davidson" email="duncan@x180.com" />
+      <person email="duncan@x180.com" name="James Duncan Davidson"/>
     </authors>
-
-    <notice>This document is a WIP (Work In Progress).</notice>
-
-    <abstract>Archival copy of Duncan's 'Rules for Revolutionaries.'</abstract>
-  </header>
-
+    <notice>This document is a WIP (Work In Progress).
+</notice>
+    <abstract>Archival copy of Duncan's 'Rules for Revolutionaries.'
+</abstract>
+  </properties>
   <body>
-
-    <section>
-      <title>rules for revolutionaries</title>
+    <section id="rules+for+revolutionaries">
+      <title>rules for revolutionaries
+</title>
       <note>
-        <strong>As Sent on 13 Jan 2000.</strong>
-        &copy; 1995-2002, James Duncan Davidson.
+        <strong>As Sent on 13 Jan 2000.
+</strong>© 1995-2002, James Duncan Davidson.
+
         <br/>
-        <em>Note: This message was written at a specific place and time
-        in response to a specific situtation. It does not address
-        several important issues like what happens when revolutions
-        do not totally succeed. It also doesn't address the issues of
-        responsiblity. The Apache Jakarta PMC has responsiblities 
-        that aren't detailed here. With that said...</em>
+        <em>Note: This message was written at a specific place and time in
+response to a specific situtation. It does not address several
+important issues like what happens when revolutions do not totally
+succeed. It also doesn't address the issues of responsiblity. The
+Apache Jakarta PMC has responsiblities that aren't detailed here.
+With that said...
+</em>
       </note>
-      <source>
-<strong>Date:</strong>    Thu, 13 Jan 2000 15:46:41 -0800
-<strong>Subject:</strong> RESET: Proposal for Revolutionaries and Evolutionaries
-<strong>From:</strong>    James Duncan Davidson &lt;james.davidson@eng.sun.com&gt;
-<strong>To:</strong>      &lt;general@jakarta.apache.org&gt;
-<strong>CC:</strong>      &lt;tomcat-dev@jakarta.apache.org&gt;
-
-  Ok, the logical place for this is general@jakarta, but I'm
-  including tomcat-dev@jakarta so that the people who are
-  there and not on general can see it. Please do not discuss
-  on tomcat-dev, please only discuss on general.
-
-  In a closed source project where you've got a set team,
-  you make decisions about where the entire team goes and
-  somebody takes the lead of deciding what gets done
-  when. In the discussions about Craig's long term plan,
-  this metric was applied by several of us in thoughts about
-  where to go next.
-
-  After pondering this for a while, it's (re)become obvious
-  to me that there's no way that anybody can expect an open
-  source organization to work the same way that a team in a
-  corporate setting can. Ok, so this is pretty freaking
-  obvious, but I've been watching people that are not from
-  Sun and who have been doing open source for a while
-  talking and proposing things that come from this line of
-  thought as well.  Its not just people from Sun or people
-  from any particular entity.
-
-  So -- in any software development project there is a
-  natural tension between revolution and evolution. In a
-  closed source environment, you make the call at any
-  particular time on whether you are in revolutionary mode or
-  evolutionary mode. For example, JSDK was in evolutionary
-  mode for years. Then in Nov 98, We made a decision to go
-  revolutionary. Of course, at the time the project team was
-  composed of 1 person -- me, so it was an easy decision.
-  After that revolution was over in Jan 99, Tomcat was in
-  evolutionary mode getting JSP bolted in and working with
-  J2EE. We (Sun folks) could do that because that was what
-  suited the goals best at the time.
-
-  However, Open source is chaotic.  With its special magic
-  comes a different reality. This is:
-
-    1) People work on their own time (even people paid by a
-    company can be considered to be working on their own
-    time in this situtation as each company is going to have
-    different cycles and things they want)
-
-    2) People work on what they want to. If you are working
-    on your own time, you are going to do what you want or
-    you do something else.
-
-    3) Some people are evolutionaries, other are
-    revolutionaries, and some are both at different times.
-
-    4) Both approaches are important and need to be
-    cultured.
-
-    5) You really can't afford to alienate any part of your
-    developer community. Innovation can come from anywhere.
-
-  To allow this to happen, to allow revolutionaries to
-  co-exist with evolutionaries, I'm proposing the following
-  as official Jakarta policy:
-
-    1) Any committer has the right to go start a
-    revolution. They can establish a branch or seperate
-    whiteboard directory in which to go experiment with new
-    code seperate from the main trunk. The only
-    responsibility a committer has when they do this is to
-    inform the developer group what their intent is, to keep
-    the group updated on their progress, and allowing others
-    who want to help out to do so.  The committer, and the
-    group of people who he/she has a attracted are free to
-    take any approaches they want to free of interference.
-
-    2) When a revolution is ready for prime time, the
-    committer proposes a merge to the -dev list. At that
-    time, the overall community evaluates whether or not the
-    code is ready to become part of, or to potentially
-    replace the, trunk. Suggestions may be made, changes may
-    be required. Once all issues have been taken care of and
-    the merge is approved, the new code becomes the trunk.
-
-    3) A revolution branch is unversioned.  It doesn't have
-    any official version standing. This allows several
-    parallel tracks of development to occur with the final
-    authority of what eventually ends up on the trunk laying
-    with the entire community of committers.
-
-    4) The trunk is the official versioned line of the
-    project. All evolutionary minded people are welcome to
-    work on it to improve it. Evolutionary work is important
-    and should not stop as it is always unclear when any
-    particular revolution will be ready for prime time or
-    whether it will be officially accepted.
-
-  What does this mean?
-
-  In practice, this means that Craig and Hans and anybody
-  else that wants to run with that revolution is welcome to
-  do so. The only change is that it's not called Tomcat.next
-  -- it's the RED branch or GOOGLE branch or whatever they
-  want to call it.
-
-  Whenever Craig (or anybody else working on that codebase)
-  wants to bring stuff into the trunk, they propose it here
-  and we evaluate it on it's merits.
-
-  If somebody disagrees with Craig's approach (for the sake
-  of argument here), they are free to create a BLUE
-  whiteboard and work out what they think is a good
-  solution. At that point, the community will have to
-  evaluate both approaches. But since this is a populist
-  society, with such a structure it is hoped that it becomes
-  clear which is the preferred approach by the community by
-  their participation and voting. Or maybe the best solution
-  is something in the middle and the two parties work
-  together to merge. Irregardless, the point is to allow
-  solutions to happen without being stalled out in the
-  formative stages.
-
-  An important point is that no one revolution is declared
-  to be the official .next until it's ready to be accepted
-  for that. There is the side effect that we could
-  potentially end up with too many revolutions happening,
-  but I'd rather rely upon the natural inclination of
-  developers to gravitate towards one solution to control
-  this than to try to control it through any policy
-  statement.
-
-  When would this be official?
-
-  Well, if this is well recieved, we'd want to word it up
-  and make it a bylaw (with approval by the PMC -- this is
-  one of the areas in which the PMC has authority).
-  Hopefully soon.
-
-  Comments? Suggestions?
-
-  James Davidson duncan@eng.sun.com
-  Java + XML / Portable Code + Portable Data
-  !try; do()
+      <source xml:space="preserve">
+        <strong>Date:
+</strong>Thu, 13 Jan 2000 15:46:41 -0800
+
+        <strong>Subject:
+</strong>RESET: Proposal for Revolutionaries and Evolutionaries
+
+        <strong>From:
+</strong>James Duncan Davidson &lt;james.davidson@eng.sun.com&gt;
+
+        <strong>To:
+</strong>&lt;general@jakarta.apache.org&gt;
+
+        <strong>CC:
+</strong>&lt;tomcat-dev@jakarta.apache.org&gt; Ok, the logical place for this is
+general@jakarta, but I'm including tomcat-dev@jakarta so that the
+people who are there and not on general can see it. Please do not
+discuss on tomcat-dev, please only discuss on general. In a closed
+source project where you've got a set team, you make decisions about
+where the entire team goes and somebody takes the lead of deciding
+what gets done when. In the discussions about Craig's long term plan,
+this metric was applied by several of us in thoughts about where to
+go next. After pondering this for a while, it's (re)become obvious to
+me that there's no way that anybody can expect an open source
+organization to work the same way that a team in a corporate setting
+can. Ok, so this is pretty freaking obvious, but I've been watching
+people that are not from Sun and who have been doing open source for
+a while talking and proposing things that come from this line of
+thought as well. Its not just people from Sun or people from any
+particular entity. So -- in any software development project there is
+a natural tension between revolution and evolution. In a closed
+source environment, you make the call at any particular time on
+whether you are in revolutionary mode or evolutionary mode. For
+example, JSDK was in evolutionary mode for years. Then in Nov 98, We
+made a decision to go revolutionary. Of course, at the time the
+project team was composed of 1 person -- me, so it was an easy
+decision. After that revolution was over in Jan 99, Tomcat was in
+evolutionary mode getting JSP bolted in and working with J2EE. We
+(Sun folks) could do that because that was what suited the goals best
+at the time. However, Open source is chaotic. With its special magic
+comes a different reality. This is: 1) People work on their own time
+(even people paid by a company can be considered to be working on
+their own time in this situtation as each company is going to have
+different cycles and things they want) 2) People work on what they
+want to. If you are working on your own time, you are going to do
+what you want or you do something else. 3) Some people are
+evolutionaries, other are revolutionaries, and some are both at
+different times. 4) Both approaches are important and need to be
+cultured. 5) You really can't afford to alienate any part of your
+developer community. Innovation can come from anywhere. To allow this
+to happen, to allow revolutionaries to co-exist with evolutionaries,
+I'm proposing the following as official Jakarta policy: 1) Any
+committer has the right to go start a revolution. They can establish
+a branch or seperate whiteboard directory in which to go experiment
+with new code seperate from the main trunk. The only responsibility a
+committer has when they do this is to inform the developer group what
+their intent is, to keep the group updated on their progress, and
+allowing others who want to help out to do so. The committer, and the
+group of people who he/she has a attracted are free to take any
+approaches they want to free of interference. 2) When a revolution is
+ready for prime time, the committer proposes a merge to the -dev
+list. At that time, the overall community evaluates whether or not
+the code is ready to become part of, or to potentially replace the,
+trunk. Suggestions may be made, changes may be required. Once all
+issues have been taken care of and the merge is approved, the new
+code becomes the trunk. 3) A revolution branch is unversioned. It
+doesn't have any official version standing. This allows several
+parallel tracks of development to occur with the final authority of
+what eventually ends up on the trunk laying with the entire community
+of committers. 4) The trunk is the official versioned line of the
+project. All evolutionary minded people are welcome to work on it to
+improve it. Evolutionary work is important and should not stop as it
+is always unclear when any particular revolution will be ready for
+prime time or whether it will be officially accepted. What does this
+mean? In practice, this means that Craig and Hans and anybody else
+that wants to run with that revolution is welcome to do so. The only
+change is that it's not called Tomcat.next -- it's the RED branch or
+GOOGLE branch or whatever they want to call it. Whenever Craig (or
+anybody else working on that codebase) wants to bring stuff into the
+trunk, they propose it here and we evaluate it on it's merits. If
+somebody disagrees with Craig's approach (for the sake of argument
+here), they are free to create a BLUE whiteboard and work out what
+they think is a good solution. At that point, the community will have
+to evaluate both approaches. But since this is a populist society,
+with such a structure it is hoped that it becomes clear which is the
+preferred approach by the community by their participation and
+voting. Or maybe the best solution is something in the middle and the
+two parties work together to merge. Irregardless, the point is to
+allow solutions to happen without being stalled out in the formative
+stages. An important point is that no one revolution is declared to
+be the official .next until it's ready to be accepted for that. There
+is the side effect that we could potentially end up with too many
+revolutions happening, but I'd rather rely upon the natural
+inclination of developers to gravitate towards one solution to
+control this than to try to control it through any policy statement.
+When would this be official? Well, if this is well recieved, we'd
+want to word it up and make it a bylaw (with approval by the PMC --
+this is one of the areas in which the PMC has authority). Hopefully
+soon. Comments? Suggestions? James Davidson duncan@eng.sun.com Java +
+XML / Portable Code + Portable Data !try; do()
+
       </source>
     </section>
-
   </body>
 </document>

Copied: incubator/public/trunk/site-author/learn/theapacheway.xml (from r373662, incubator/public/trunk/site-author/learn/theapacheway.html)
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site-author/learn/theapacheway.xml?p2=incubator/public/trunk/site-author/learn/theapacheway.xml&p1=incubator/public/trunk/site-author/learn/theapacheway.html&r1=373662&r2=373682&rev=373682&view=diff
==============================================================================
--- incubator/public/trunk/site-author/learn/theapacheway.html (original)
+++ incubator/public/trunk/site-author/learn/theapacheway.xml Mon Jan 30 19:21:03 2006
@@ -1,431 +1,134 @@
-<!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>The Apache Way</title>
-<link href="http://purl.org/DC/elements/1.0/" rel="schema.DC">
-<meta content="The Apache Incubator Project" name="DC.Creator">
-<meta content="Apache is a special opensource entity, that values people and communities
-                over code and licensing. It has created a unique social ecosystem, that
-                is here described." name="DC.Description">
-</head>
-<body>
-
-<h1>Warning</h1> 
-<p>
-This document is a Work in Progress, and reflects the ongiong effort of the authors 
-to describe Apache guidelines.</p>
-
-<h1>Purpose of this document</h1>
-          
-        
-<p>
-           Apache has a particular way of dealing with projects which is usually summed up as 
-           <strong>the Apache Way</strong>.<br>
-
-           The purpose of this document is to aggergate and integrate all information about how Apache operates both 
-           technically and socially.
-           
-           It's a live document, and as such it tries to reflect the current situation at Apache, 
-           but keep in mind that reality is much more dynamic and changes continuously, so it will be
-           probable that there are some inconsistencies with what you will see.<br>
-           
-           Apache is also about helping each other, so if you find errors or omissions, please tell us
-           at our mailing list, where we will be more than happy to hear from you.
-         </p>
-         
-<h2>Note</h2>   <p>        
-           If you are a committer on Apache, there is a very special mailing list created for all Apache
-           committers, where we all gather to discuss about our present and future: 
-           <a href="mailto:community.at.apache.org">community@apache.org</a>.<br>
-          
-           To subscribe, send a mail to 
-           <a href="mailto:community-subscribe.at.apache.org">community-subscribe@apache.org</a>.</p>
-     
-
-    
-<h1>About Apache</h1>
-      
-        
-<ul>
-          
-<li>
-<a class="external" href="http://apache.org/foundation/">The Apache Software Foundation</a>
-</li>
-          
-<li>
-<a href="../whoweare.html">The apache.org volunteers</a>
-</li>
-        
-</ul>
-          
-<h2>A bit of history</h2>
-<ul>
-             
-<li>
-<a class="external" href="http://www.mail-archive.com/general@jakarta.apache.org/msg02778.html">Brief History of Jakarta and the ASF</a>
-</li>
-             
-<li>
-<a class="external" href="http://httpd.apache.org/ABOUT_APACHE.html">The original Apache HTTPD Project</a>
-</li>
-             
-<li>
-<a class="external" href="http://java.apache.org/main/constitution.html">The java.apache.org Constitution</a>
-</li>
-            
-</ul>
-          
-<h2>Mission</h2>
-<ul>        
-              
-<li>
-<a class="external" href="http://jakarta.apache.org/site/mission.html"> Mission</a>  
-</li> 
-              
-<li>
-<a class="external" href="http://apache.org/foundation/faq.html#why">The ASF Mission</a>
-</li>
-            
-</ul>
-          
-<h2>Projects</h2>
-<ul>
-              
-<li>
-<a class="external" href="http://apache.org/foundation/projects.html">Projects - The Apache Software Foundation</a>
-</li>
-            
-</ul>
-          
-<h2>Roles and Responsibilities</h2>
-<ul>
-              
-<li>
-<a class="external" href="http://jakarta.apache.org/site/roles.html">Roles and Responsibilities</a>
-</li>
-            
-</ul>
-       
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<document>
+  <properties><!--
+
+    <meta content="HTML Tidy, see www.w3.org" name="generator"/>-->
+<!--
+
+    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type"/>-->
+
+    <title>The Apache Way
+</title>
+    <link href="http://purl.org/DC/elements/1.0/" rel="schema.DC"/><!--
+
+    <meta content="The Apache Incubator Project" name="DC.Creator"/>-->
 <!--
 
-     <section>
-       
-       Project proposal</section>
-  <p>
-  Proposal stage, committers needed, community.
-  </p>
-  <p>
-  <link href="http://jakarta.apache.org/site/getinvolved.html">Community</link><br/>
-  <link href="http://jakarta.apache.org/site/newproject.html">Proposals for new projects</link>
-  </p>
-  </li>
-
-  <li><section>Our Methodology</section>
-  <p>
-  Who gets to vote what.<br/>
-  Voting rules, valid votes, +1/+0/0/-0/-1.
-  </p>
-
-  <p>
-  <link href="http://jakarta.apache.org/site/roles.html">Project roles</link><br/>
-  <link href="http://jakarta.apache.org/site/decisions.html">Who votes what</link><br/>
-  <link href="http://jakarta.apache.org/site/proposal.html">Proposed guideline clarifications</link><br/>
-  <link href="http://xml.apache.org/roles.html">xml.apache.org roles</link><br/>
-  <link href="http://xml.apache.org/decisions.html">xml.apache.org decisions</link><br/>
-  <link href="http://cvs.apache.org/viewcvs.cgi/xml-admin/charter.txt">xml.apache.org charter</link>
-  </p>
-  </li>
-  
-  <li><section>Code organization and repositories</section>
-  <p>
-  Naming of packages, repositories, what to find in them.<br/>
-  Who touches what.
-  </p>
-
-  <p>
-  <link href="http://jakarta.apache.org/site/dirlayout.html">Directory layout</link><br/>
-  <link href="http://jakarta.apache.org/site/guidelines.html">Project guidelines</link><br/>
-  <link href="http://jakarta.apache.org/site/agreement.html">Committer agreement</link>
-  </p>
-  </li>
-
-  <li><section>Code quality</section>
-  <p>
-  Add copyright notice, add authors.<br/>
-  Follow product conventions for new code.<br/>
-  Otherwise, "Adhere to the style of the original".
-  </p>
-
-  <p>
-  <link href="http://jakarta.apache.org/site/agreement.html">Committer agreement</link><br/>
-  <link href="http://xml.apache.org/source.html">xml.apache.org source code</link><br/>
-  <link href="faqs.html#Coding Conventions and Standards">Product Coding standards</link>
-  </p>
-  </li>
-
-  <li><section>Testing</section>
-  <p>
-  Adding test cases.<br/>
-  Solving bugs, errors, showstoppers.<br/>
-  Security problems.
-  </p>
-
-  <p>
-  <link href="http://httpd.apache.org/security_report.html">httpd security problems</link>
-  </p>
-  </li>
-
-  <li><section>Build system</section>
-  <p>
-  Use Ant, use Ant, use Ant.<br/>
-  Use Gump.<br/>
-  Use Scarab.
-  </p>
-
-  <p>
-  Not done yet.
-  </p>
-  </li>
-
-  <li><section>Dependencies</section>
-
-  <p>
-  <link href="http://jakarta.apache.org/site/jars.html">What jar's to use
-  and what to avoid.</link>
-  </p>
-  </li>
-
-  <li><section>Documentation</section>
-  <p>
-  Where to look for it.<br/>
-  What to expect, what not to expect.
-  </p>
-
-  <p>
-  Not done yet.
-  </p>
-  </li>
-
-  <li><section>Releases</section>
-  <p>
-  When to release, what to release.<br/>
-  Release process.
-  </p>
-
-  <p>
-  <link href="http://jakarta.apache.org/site/binindex.html">Release flavors</link>
-  </p>
-  </li>
-
-  <li><section>Support</section>
-  Whom you should ask, what you should figure out yourself.
-
-  <p>
-  <link href="http://jakarta.apache.org/site/mail.html">Mail guidelines</link><br/>
-  <link href="http://xml.apache.org/mail.html">xml.apache.org guidelines</link>
-  </p>
-  </li>
-
-  <li><section>Licensing and guarantee</section>
-  <p>
-  Why you should use Apache license, and what's wrong with other licenses.<br/>
-  What you can do with Apache products. Giving credit.<br/>
-  All that implied warranty things.
-  </p>
-
-  <p>
-  <link href="http://www.apache.org/foundation/licence-FAQ.html">The Apache license FAQ</link><br/>
-  <link href="http://xml.apache.org/dist/LICENSE.txt">The Apache license</link>
-  </p>
-  </li>
-
-</ul>
-<p> </p>
-
-</section>
-
-
-
-
-<section>User Guide</section>
-<ul>
-  <li><link href="http://jakarta.apache.org/">Welcome to the Jakarta Project</link></li>
-  <li><link href="http://jakarta.apache.org/site/roles.html"> Roles and Responsibilities</link>
-    <ul>
-      <li>XML <link href="http://xml.apache.org/roles.html">Roles and Responsibilities</link></li>
-    </ul>
-  </li>
-  <li><link href="http://jakarta.apache.org/site/cvsindex.html"> CVS Repository</link></li>
-  <li>Licensing
-    <ul>
-      <li>                                 What you can do with Apache products.</li>
-      <li>All that implied warranty things. </li>
-    </ul>
-  </li>
-  <li>Support
-    <ul>
-      <li>Whom you should ask, what you should figure out yourself. </li>
-    </ul>
-  </li>
-  <li><link href="http://jakarta.apache.org/site/communication.html"> Communication</link></li>
-  <li>Documentation
-    <ul>
-      <li>Where to look for it.</li>
-      <li>                                 What to expect, what not to expect. </li>
-    </ul>
-  </li>
-  <li><link href="http://jakarta.apache.org/site/bugs.html">Bugzilla</link>
-    <ul>
-      <li><link href="http://scarab.tigris.org/">Scarab</link></li>
-    </ul>
-  </li>
-  <li><link href="http://jakarta.apache.org/site/mail.html"> Mailing Lists</link>
-    <ul>
-      <li>XML <link href="http://xml.apache.org/mail.html">Mailing Lists</link></li>
-    </ul>
-  </li>
-  <li><link href="http://jakarta.apache.org/site/library.html">Reference Library</link></li>
-  <li><link href="http://jakarta.apache.org/site/faqs.html">FAQs</link></li>
-  <li><link href="http://search.apache.org/">Search Apache</link>
-    <ul>
-      <li>with Google</li>
-    </ul>
-  </li>
-  <li><link href="http://jakarta.apache.org/site/contact.html"> Contact Information</link></li>
-  <li><link href="http://jakarta.apache.org/site/getinvolved.html"> Get Involved</link></li>
-</ul>
-
-<section>Moderator's Guide</section>
-<p>What mailing list moderators need to know.</p>
-<section>Developer's Guide</section>
-<ul>
-  <li><link href="http://www.apache.org/foundation/licence-FAQ.html">Apache License and Distribution FAQ</link>
-    <ul>
-      <li>Retaining credit</li>
-      <li>Copyright notices</li>
-    </ul>
-  </li>
-  <li><link href="http://jakarta.apache.org/site/source.html"> Source Repositories</link>
-    <ul>
-      <li><link href="http://jakarta.apache.org/site/faqs.html#Coding Conventions and Standards">Product Coding Conventions</link></li>
-      <li>                                 Follow product conventions for new code.</li>
-      <li>Otherwise, &quot;Adhere to the style of the original.&quot; </li>
-      <li>XML <link href="http://xml.apache.org/source.html">Source Repositories</link></li>
-    </ul>
-  </li>
-  <li>Building
-    <ul>
-      <li>Ant</li>
-      <li>Scarab</li>
-      <li>Gump</li>
-    </ul>
-  </li>
-  <li>Unit Testing
-    <ul>
-      <li><link href="http://jakarta.apache.org/gump">Gump</link></li>
-    </ul>
-  </li>
-</ul>
-<p><link href="http://httpd.apache.org/security_report.html">Reporting Security Problems with Apache</link></p>
-<p><link href="http://jakarta.apache.org/site/agreement.html"> Contributor License Agreement</link></p>
-<p><link href="http://jakarta.apache.org/site/decisions.html">Decision Making</link> (XML <link href="http://xml.apache.org/decisions.html">Decision Making</link>)</p>
-
-<section>Committer's Guide</section>
-<ul>
-  <li><link href="http://jakarta.apache.org/site/cvsonunix.html"> CVS Access on Unix</link></li>
-  <li><link href="http://jakarta.apache.org/site/cvsonwin32.html"> CVS Access on Windows</link></li>
-  <li><link href="http://jakarta.apache.org/site/jars.html"> JARs under CVS</link></li>
-  <li><link href="http://www.x180.net/Mutterings/OpenSource/RulesForRevEmail.html">Rules for Revolutionaries</link></li>
-  <li><link href="http://jakarta.apache.org/site/proposal.html"> Proposed Changes - Jakarta Project Guidelines</link></li>
-</ul>
-
-<section>Release Manager's Guide</section>
-<ul>
-  <li>When to release, what to release.</li>
-  <li>                                 Release process. </li>
-  <li><link href="http://jakarta.apache.org/site/binindex.html">Release Flavors</link></li>
-  <li><link href="http://jakarta.apache.org/site/jakarta-site2.html">About This Site</link></li>
-</ul>
-
-<section>Founder's Guide</section>
-<ul>
-  <li>Licensing
-    <ul>
-      <li>Why the Apache License</li>
-    </ul>
-  </li>
-  <li><link href="http://jakarta.apache.org/site/newproject.html">Jakarta Sub-Project Proposals</link></li>
-  <li><link href="http://jakarta.apache.org/site/dirlayout.html"> Jakarta Directory Layout</link></li>
-  <li><link href="http://www.apache.org/dev/project-creation.html">Procedures for Creating an ASF Project </link></li>
-</ul>
-
-<section>Project Manager's Guide</section>
-<ul>
-  <li><link href="http://jakarta.apache.org/site/management.html"> Project Management Committee Bylaws</link></li>
-  <li><link href="http://jakarta.apache.org/site/pmc/index.html"> PMC Meeting Archive</link></li>
-</ul>
-
-<section>System Administrator's Guide</section>
-<ul>
-  <li>CVS</li>
-  <li>ezmlm</li>
-  <li>Bugzilla | Scarab</li>
-  <li>Eyebrowse</li>
-</ul>
-
-</section>
-
-   
-   
-   
-      <section>
-         <title>The Apache Way</title>
-
-         .</p>
-
-         <p>The project guidelines sum up much of it.</p>
-
-         <ul>
-            <li>
-               <link href="http://jakarta.apache.org/site/guidelines.html">Jakarta Project guidelines</link>
-            </li>
-
-            <li>
-               <link href="http://xml.apache.org/guidelines.html">Xml Project guidelines</link>
-            </li>
-         </ul>
-
-         <p>Important is also the 
-         <link src="http://www.apache.org/LICENSE.txt">License.</link>
-
-         and the 
-         <link src="http://www.apache.org/foundation/faq.html">FAQ</link>
-         </p>
-
-         <p>You can find some notes about community dynamics with 
-         <link href="http://krysalis.org/cgi-bin/krywiki.pl?CoPDoC">CoPDoC</link>
-         </p>
+    <meta content="Apache is a special opensource entity, that values people and communities over code and licensing. It has created a unique social ecosystem, that is here described." name="DC.Description"/>-->
+
+  </properties>
+  <body>
+    <section id="Warning">
+      <title>Warning
+</title>
+      <p>This document is a Work in Progress, and reflects the ongiong effort
+of the authors to describe Apache guidelines.
+</p>
+    </section>
+    <section id="Purpose+of+this+document">
+      <title>Purpose of this document
+</title>
+      <p>Apache has a particular way of dealing with projects which is usually
+summed up as
+
+        <strong>the Apache Way
+</strong>.
+
+        <br/>The purpose of this document is to aggergate and integrate all
+information about how Apache operates both technically and socially.
+It's a live document, and as such it tries to reflect the current
+situation at Apache, but keep in mind that reality is much more
+dynamic and changes continuously, so it will be probable that there
+are some inconsistencies with what you will see.
+
+        <br/>Apache is also about helping each other, so if you find errors or
+omissions, please tell us at our mailing list, where we will be more
+than happy to hear from you.
+
+      </p>
+      <section id="Note">
+        <title>Note
+</title>
+        <p>If you are a committer on Apache, there is a very special mailing
+list created for all Apache committers, where we all gather to
+discuss about our present and future:
+
+          <a href="mailto:community.at.apache.org">community@apache.org
+</a>.
 
-         <fixme>Need to complete this page.</fixme>
+          <br/>To subscribe, send a mail to
+
+          <a href="mailto:community-subscribe.at.apache.org">community-subscribe@apache.org
+</a>.
+
+        </p>
+      </section>
+    </section>
+    <section id="About+Apache">
+      <title>About Apache
+</title>
+      <ul>
+        <li>
+          <a href="http://apache.org/foundation/">The Apache Software Foundation
+</a>
+        </li>
+        <li>
+          <a href="../whoweare.html">The apache.org volunteers
+</a>
+        </li>
+      </ul>
+      <section id="A+bit+of+history">
+        <title>A bit of history
+</title>
+        <ul>
+          <li>
+            <a href="http://www.mail-archive.com/general@jakarta.apache.org/msg02778.html">Brief History of Jakarta and the ASF
+</a>
+          </li>
+          <li>
+            <a href="http://httpd.apache.org/ABOUT_APACHE.html">The original Apache HTTPD Project
+</a>
+          </li>
+          <li>
+            <a href="http://java.apache.org/main/constitution.html">The java.apache.org Constitution
+</a>
+          </li>
+        </ul>
+      </section>
+      <section id="Mission">
+        <title>Mission
+</title>
+        <ul>
+          <li>
+            <a href="http://jakarta.apache.org/site/mission.html">Mission
+</a>
+          </li>
+          <li>
+            <a href="http://apache.org/foundation/faq.html#why">The ASF Mission
+</a>
+          </li>
+        </ul>
+      </section>
+      <section id="Projects">
+        <title>Projects
+</title>
+        <ul>
+          <li>
+            <a href="http://apache.org/foundation/projects.html">Projects - The Apache Software Foundation
+</a>
+          </li>
+        </ul>
+      </section>
+      <section id="Roles+and+Responsibilities">
+        <title>Roles and Responsibilities
+</title>
+        <ul>
+          <li>
+            <a href="http://jakarta.apache.org/site/roles.html">Roles and Responsibilities
+</a>
+          </li>
+        </ul>
       </section>
-          <section>
-            <title>Notes...</title>
-          <source>
- Some core notes should be:
-
-  1. The Apache License
-  2. A reference to our infrastructure (how projects are setup, like
-     pmc@..., dev@..., etc...)
-  3. A flow of the normal incubation process:
-      a. Concept
-      b. "Proposal"
-      c. Setup
-      d. Growth
-      e. Graduation
-  4. WHY the ASF ( this should be easy :) )</source>
-            </section>
-            -->
-   
-</body>
-</html>
+    </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