incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cross...@apache.org
Subject svn commit: r373682 [19/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-autho...
Date Tue, 31 Jan 2006 03:23:57 GMT
Copied: incubator/public/trunk/site-author/projects/woden.xml (from r373662, incubator/public/trunk/site-author/projects/woden.html)
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site-author/projects/woden.xml?p2=incubator/public/trunk/site-author/projects/woden.xml&p1=incubator/public/trunk/site-author/projects/woden.html&r1=373662&r2=373682&rev=373682&view=diff
==============================================================================
--- incubator/public/trunk/site-author/projects/woden.html (original)
+++ incubator/public/trunk/site-author/projects/woden.xml Mon Jan 30 19:21:03 2006
@@ -1,42 +1,85 @@
-<!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 Woden Incubation Status</title>
-  <link href="http://purl.org/DC/elements/1.0/" rel="schema.DC">
-</head>
-<body>
-<br>
-<h1>Apache Woden Project Incubation Status</h1>
-<p>This page tracks the project status, incubator-wise. For more
-general project status, look on the <a href="http://incubator.apache.org/woden">project website</a>. </p>
-<h1>Description</h1>
-<p>The Apache Woden Project will develop a Java class library for reading, manipulating, creating
-and writing WSDL documents, initially to support WSDL 2.0 but with the
-longer term aim of supporting past, present and future versions of WSDL<br>
-</p>
-<h1>News</h1>
-<ul>
-  <li>2005-12-09 Woden <a href="http://cvs.apache.org/dist/ws/woden/milestones/1.0.0M2-incubating">Milestone 2</a> declared</li>
-  <li>2005-10-02 Woden <a href="http://cvs.apache.org/dist/ws/woden/milestones/M1">Milestone 1</a> declared</li>
-  <li>2005-03-24 Project accepted by the Web services PMC</li>
-  <li>2005-03-24 Project proposed on general@incubator mailing list<br>
-  </li>
-</ul>
-<h1>Project info</h1>
-<table>
-  <tbody>
-    <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/woden/">http://incubator.apache.org/woden/</a></td>
-    </tr>
-    <!-- No project wiki yet
+<?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 Woden Incubation Status
+</title>
+    <link href="http://purl.org/DC/elements/1.0/" rel="schema.DC"/>
+  </properties>
+  <body>
+    <section id="Apache+Woden+Project+Incubation+Status">
+      <title>Apache Woden Project Incubation Status
+</title>
+      <p>This page tracks the project status, incubator-wise. For more general
+project status, look on the
+
+        <a href="http://incubator.apache.org/woden">project website
+</a>.
+
+      </p>
+    </section>
+    <section id="Description">
+      <title>Description
+</title>
+      <p>The Apache Woden Project will develop a Java class library for
+reading, manipulating, creating and writing WSDL documents, initially
+to support WSDL 2.0 but with the longer term aim of supporting past,
+present and future versions of WSDL
+
+        <br/>
+      </p>
+    </section>
+    <section id="News">
+      <title>News
+</title>
+      <ul>
+        <li>2005-12-09 Woden
+
+          <a href="http://cvs.apache.org/dist/ws/woden/milestones/1.0.0M2-incubating">Milestone 2
+</a>declared
+
+        </li>
+        <li>2005-10-02 Woden
+
+          <a href="http://cvs.apache.org/dist/ws/woden/milestones/M1">Milestone 1
+</a>declared
+
+        </li>
+        <li>2005-03-24 Project accepted by the Web services PMC
+</li>
+        <li>2005-03-24 Project proposed on general@incubator mailing list
+
+          <br/>
+        </li>
+      </ul>
+    </section>
+    <section id="Project+info">
+      <title>Project info
+</title>
+      <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/woden/">http://incubator.apache.org/woden/
+</a>
+          </td>
+        </tr><!-- No project wiki yet
     <tr>
       <td>. </td>
       <td>wiki </td>
@@ -44,329 +87,500 @@
       </td>
     </tr>
     -->
-    <tr>
-      <td>Mailing list </td>
-      <td>dev </td>
-      <td><a href="http://incubator.apache.org/woden/mailinglists.html">woden-dev@ws.apache.org</a></td>
-    </tr>
-    <tr>
-      <td>. </td>
-      <td>svn </td>
-      <td><a href="http://incubator.apache.org/woden/mailinglists.html">woden-cvs@incubator.apache.org</a></td>
-    </tr>
-    <tr>
-      <td>Bug tracking</td>
-      <td>JIRA</td>
-      <td><a href="http://nagoya.apache.org/jira/browse/Woden">http://nagoya.apache.org/jira/browse/Woden</a></td>
-    </tr>
-    <tr>
-      <td>Source code</td>
-      <td>svn</td>
-      <td><a href="http://svn.apache.org/repos/asf/incubator/woden/">http://svn.apache.org/repos/asf/incubator/woden/</a></td>
-    </tr>
-    <tr>
-      <td>Mentors </td>
-      <td> <br>
-      </td>
-      <td>Davanum Srinivas (dims at apache.org)<br>
-      </td>
-    </tr>
-    <tr>
-      <td><br>
-      </td>
-      <td> <br>
-      </td>
-      <td>Paul Fremantle (pzf at hursley.ibm.com)<br>
-      </td>
-    </tr>
-    <tr>
-      <td><br>
-      </td>
-      <td><br>
-      </td>
-      <td>Sanjiva Weerawarana (sanjiva at opensource.lk)</td>
-    </tr>
-    <tr>
-      <td>Committers </td>
-      <td> <br>
-      </td>
-      <td>Chathura Herath (chathura at opensource.lk)<br>
-      </td>
-    </tr>
-    <tr>
-      <td><br>
-      </td>
-      <td> <br>
-      </td>
-      <td>Jeremy Hughes (hughesj at apache.org)<br>
-      </td>
-    </tr>
-    <tr>
-      <td><br>
-      </td>
-      <td> <br>
-      </td>
-      <td>John Kaputin (jakaputin at gmail.com)<br>
-      </td>
-    </tr>
-    <tr>
-      <td><br>
-      </td>
-      <td> <br>
-      </td>
-      <td>Lawrence Mandel (lmandel at apache.org)<br>
-      </td>
-    </tr>
-    <tr>
-      <td><br>
-      </td>
-      <td> <br>
-      </td>
-      <td>Arthur Ryman (arthur.ryman at gmail.com)<br>
-      </td>
-    </tr>
-  </tbody>
-</table>
-<h1>Incubation status reports</h1>
-<ul>
-	<li>
-		<h3>Dec. 2005</h3>
-		The milestone plan, originally too ambitious, was updated to reflect Woden's new schedule. 
-		Woden milestone 2 was declared. Milestone 2 contains parsing logic for WSDL 2.0 interface 
-		and binding elements and components, and validation logic for the WSDL 2.0 types element 
-		and interface element and component.
-	</li>
-	<li>
-		<h3>Oct. 2005</h3>
-		We posted a Woden milestone plan in September covering M1 at end-Sept through to M5 in Jan 2006. 
-      	Completion of the initial project objective, full WSDL 2.0 functionality, is targetted for M4 
-      	end-Nov. M1 was release on Mon 3 Oct and included most but not all of the planned scopd. M3 and 
-      	M4 will be busy periods. M5 and future plans will emerge as we approach M4 and start thinking 
-      	about other Woden objectives like WSDL 1.1 conversion and StAX XML parsing for the Axis community. 
-      	We are using the woden-dev mailing list for communication and discussion and recently held our first 
-      	conference call - although not all participants could make the call, it helped confirm the Milestone 
-      	plan and resolve some technical issues. Most of the development is currently being done by 2 
-      	committers and this may continue up to M3/M4, by which time we will have a suitable base for others 
-      	to start building on.
-	</li>
-	<li>
-		<h3>Sept. 2005</h3>
-		Woden incubator progress slower than expected over summer, but plan now agreed with milestone deliverables 
-      	each month to complete WSDL 2.0 functionality by December.
-	</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
-</h3>
-<table>
-  <tbody>
-    <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>N/A <br>
-      </td>
-      <td>If request from an existing Apache project to adopt an
-external package, then ask the Apache project for the cvs module and
-mail address names. </td>
-    </tr>
-    <tr>
-      <td>N/A <br>
-      </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>N/A </td>
-      <td>If request from anywhere to become a stand-alone PMC, then
-assess the fit with the ASF, and create the lists and modules under the
-incubator address/module names if accepted. </td>
-    </tr>
-  </tbody>
-</table>
-<h3>Interim responsibility</h3>
-<table>
-  <tbody>
-    <tr>
-      <th>date </th>
-      <th>item </th>
-    </tr>
-    <tr>
-      <td>2005-12-09</td>
-      <td>Identify all the Mentors for the incubation, by asking all
-that can be Mentors. </td>
-    </tr>
-    <tr>
-      <td>TBD <br>
-      </td>
-      <td>Subscribe all Mentors on the pmc and general lists. </td>
-    </tr>
-    <tr>
-      <td>TBD <br>
-      </td>
-      <td>Give all Mentors access to all incubator CVS modules. (to be
-done by PMC chair) </td>
-    </tr>
-    <tr>
-      <td>2005-12-09<br>
-      </td>
-      <td>Tell Mentors to track progress in the file
-'incubator/projects/woden.html' </td>
-    </tr>
-  </tbody>
-</table>
-<h3>Copyright</h3>
-<table>
-  <tbody>
-    <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>2005-12-09 </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>....-..-.. </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>2005-12-09 </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>
-  </tbody>
-</table>
-<h3>Establish a list of active committers !</h3>
-<table>
-  <tbody>
-    <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>2005-12-09</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
-cvs.apache.org. </td>
-    </tr>
-  </tbody>
-</table>
-<h3>Infrastructure !</h3>
-<table>
-  <tbody>
-    <tr>
-      <th>date </th>
-      <th>item </th>
-    </tr>
-    <tr>
-      <td>2005-12-09</td>
-      <td>Ask infrastructure to create source repository modules and
-grant the committers karma.</td>
-    </tr>
-    <tr>
-      <td>2005-12-09</td>
-      <td>Ask infrastructure to set up and archive Mailing lists. </td>
-    </tr>
-    <tr>
-      <td>2005-12-09 </td>
-      <td>Decide about and then ask infrastructure to setup an
-issuetracking system (Jira). </td>
-    </tr>
-    <tr>
-      <td>2005-12-09 </td>
-      <td>Migrate the project to our infrastructure. </td>
-    </tr>
-  </tbody>
-</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>
+        <tr>
+          <td>Mailing list
+</td>
+          <td>dev
+</td>
+          <td>
+            <a href="http://incubator.apache.org/woden/mailinglists.html">woden-dev@ws.apache.org
+</a>
+          </td>
+        </tr>
+        <tr>
+          <td>.
+</td>
+          <td>svn
+</td>
+          <td>
+            <a href="http://incubator.apache.org/woden/mailinglists.html">woden-cvs@incubator.apache.org
+</a>
+          </td>
+        </tr>
+        <tr>
+          <td>Bug tracking
+</td>
+          <td>JIRA
+</td>
+          <td>
+            <a href="http://nagoya.apache.org/jira/browse/Woden">http://nagoya.apache.org/jira/browse/Woden
+</a>
+          </td>
+        </tr>
+        <tr>
+          <td>Source code
+</td>
+          <td>svn
+</td>
+          <td>
+            <a href="http://svn.apache.org/repos/asf/incubator/woden/">http://svn.apache.org/repos/asf/incubator/woden/
+</a>
+          </td>
+        </tr>
+        <tr>
+          <td>Mentors
+</td>
+          <td>
+            <br/>
+          </td>
+          <td>Davanum Srinivas (dims at apache.org)
+
+            <br/>
+          </td>
+        </tr>
+        <tr>
+          <td>
+            <br/>
+          </td>
+          <td>
+            <br/>
+          </td>
+          <td>Paul Fremantle (pzf at hursley.ibm.com)
+
+            <br/>
+          </td>
+        </tr>
+        <tr>
+          <td>
+            <br/>
+          </td>
+          <td>
+            <br/>
+          </td>
+          <td>Sanjiva Weerawarana (sanjiva at opensource.lk)
+</td>
+        </tr>
+        <tr>
+          <td>Committers
+</td>
+          <td>
+            <br/>
+          </td>
+          <td>Chathura Herath (chathura at opensource.lk)
+
+            <br/>
+          </td>
+        </tr>
+        <tr>
+          <td>
+            <br/>
+          </td>
+          <td>
+            <br/>
+          </td>
+          <td>Jeremy Hughes (hughesj at apache.org)
+
+            <br/>
+          </td>
+        </tr>
+        <tr>
+          <td>
+            <br/>
+          </td>
+          <td>
+            <br/>
+          </td>
+          <td>John Kaputin (jakaputin at gmail.com)
+
+            <br/>
+          </td>
+        </tr>
+        <tr>
+          <td>
+            <br/>
+          </td>
+          <td>
+            <br/>
+          </td>
+          <td>Lawrence Mandel (lmandel at apache.org)
+
+            <br/>
+          </td>
+        </tr>
+        <tr>
+          <td>
+            <br/>
+          </td>
+          <td>
+            <br/>
+          </td>
+          <td>Arthur Ryman (arthur.ryman at gmail.com)
+
+            <br/>
+          </td>
+        </tr>
+      </table>
+    </section>
+    <section id="Incubation+status+reports">
+      <title>Incubation status reports
+</title>
+      <ul>
+        <li>
+          <h3>Dec. 2005
+</h3>The milestone plan, originally too ambitious, was updated to reflect
+Woden's new schedule. Woden milestone 2 was declared. Milestone 2
+contains parsing logic for WSDL 2.0 interface and binding elements
+and components, and validation logic for the WSDL 2.0 types element
+and interface element and component.
+
+        </li>
+        <li>
+          <h3>Oct. 2005
+</h3>We posted a Woden milestone plan in September covering M1 at end-Sept
+through to M5 in Jan 2006. Completion of the initial project
+objective, full WSDL 2.0 functionality, is targetted for M4 end-Nov.
+M1 was release on Mon 3 Oct and included most but not all of the
+planned scopd. M3 and M4 will be busy periods. M5 and future plans
+will emerge as we approach M4 and start thinking about other Woden
+objectives like WSDL 1.1 conversion and StAX XML parsing for the Axis
+community. We are using the woden-dev mailing list for communication
+and discussion and recently held our first conference call - although
+not all participants could make the call, it helped confirm the
+Milestone plan and resolve some technical issues. Most of the
+development is currently being done by 2 committers and this may
+continue up to M3/M4, by which time we will have a suitable base for
+others to start building on.
+
+        </li>
+        <li>
+          <h3>Sept. 2005
+</h3>Woden incubator progress slower than expected over summer, but plan
+now agreed with milestone deliverables each month to complete WSDL
+2.0 functionality by December.
+
+        </li>
+      </ul>
+    </section>
+    <section id="Incubation+work+items">
+      <title>Incubation work items
+</title>
+      <section id="Project+Setup">
+        <title>Project Setup
+</title>
+        <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>
+        <section id="Identify+the+project+to+be+incubated">
+          <title>Identify the project to be incubated
+</title>
+          <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>N/A
+
+                <br/>
+              </td>
+              <td>If request from an existing Apache project to adopt an external
+package, then ask the Apache project for the cvs module and mail
+address names.
+</td>
+            </tr>
+            <tr>
+              <td>N/A
+
+                <br/>
+              </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>N/A
+</td>
+              <td>If request from anywhere to become a stand-alone PMC, then assess the
+fit with the ASF, and create the lists and modules under the
+incubator address/module names if accepted.
+</td>
+            </tr>
+          </table>
+        </section>
+        <section id="Interim+responsibility">
+          <title>Interim responsibility
+</title>
+          <table>
+            <tr>
+              <th>date
+</th>
+              <th>item
+</th>
+            </tr>
+            <tr>
+              <td>2005-12-09
+</td>
+              <td>Identify all the Mentors for the incubation, by asking all that can
+be Mentors.
+</td>
+            </tr>
+            <tr>
+              <td>TBD
+
+                <br/>
+              </td>
+              <td>Subscribe all Mentors on the pmc and general lists.
+</td>
+            </tr>
+            <tr>
+              <td>TBD
+
+                <br/>
+              </td>
+              <td>Give all Mentors access to all incubator CVS modules. (to be done by
+PMC chair)
+</td>
+            </tr>
+            <tr>
+              <td>2005-12-09
+
+                <br/>
+              </td>
+              <td>Tell Mentors to track progress in the file
+'incubator/projects/woden.html'
+</td>
+            </tr>
+          </table>
+        </section>
+        <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>2005-12-09
+</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 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>2005-12-09
+</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>
+        </section>
+        <section id="Establish+a+list+of+active+committers+%21">
+          <title>Establish a list of active committers !
+</title>
+          <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>2005-12-09
+</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 cvs.apache.org.
+</td>
+            </tr>
+          </table>
+        </section>
+        <section id="Infrastructure+%21">
+          <title>Infrastructure !
+</title>
+          <table>
+            <tr>
+              <th>date
+</th>
+              <th>item
+</th>
+            </tr>
+            <tr>
+              <td>2005-12-09
+</td>
+              <td>Ask infrastructure to create source repository modules and grant the
+committers karma.
+</td>
+            </tr>
+            <tr>
+              <td>2005-12-09
+</td>
+              <td>Ask infrastructure to set up and archive Mailing lists.
+</td>
+            </tr>
+            <tr>
+              <td>2005-12-09
+</td>
+              <td>Decide about and then ask infrastructure to setup an issuetracking
+system (Jira).
+</td>
+            </tr>
+            <tr>
+              <td>2005-12-09
+</td>
+              <td>Migrate the project to our infrastructure.
+</td>
+            </tr>
+          </table>
+        </section>
+        <section id="Project+specific">
+          <title>Project specific
+</title>
+          <p>
+            <em>Add project specific tasks here.
+</em>
+          </p>
+        </section>
+      </section>
+      <section id="Incubation">
+        <title>Incubation
+</title>
+        <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>
+        <section id="Collaborative+Development">
+          <title>Collaborative Development
+</title>
+          <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>
+        </section>
+        <section id="Licensing+awareness">
+          <title>Licensing awareness
+</title>
+          <ul>
+            <li>Are all licensing, trademark, credit issues being taken care of and
+acknowleged by all committers?
+</li>
+          </ul>
+        </section>
+        <section id="Project+Specific">
+          <title>Project Specific
+</title>
+          <p>
+            <em>Add project specific tasks here.
+</em>
+          </p>
+        </section>
+      </section>
+      <section id="Exit">
+        <title>Exit
+</title>
+        <p>
+          <em>Things to check for before voting the project out.
+</em>
+        </p>
+        <section id="Organizational+acceptance+of+responsibility+for+the+project">
+          <title>Organizational acceptance of responsibility for the project
+</title>
+          <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>
+        </section>
+        <section id="Incubator+sign-off">
+          <title>Incubator sign-off
+</title>
+          <ul>
+            <li>Has the Incubator decided that the project has accomplished all of
+the above tasks?
+</li>
+          </ul>
+        </section>
+      </section>
+    </section>
+  </body>
+</document>

Copied: incubator/public/trunk/site-author/projects/wsrp4j.xml (from r373662, incubator/public/trunk/site-author/projects/wsrp4j.cwiki)
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site-author/projects/wsrp4j.xml?p2=incubator/public/trunk/site-author/projects/wsrp4j.xml&p1=incubator/public/trunk/site-author/projects/wsrp4j.cwiki&r1=373662&r2=373682&rev=373682&view=diff
==============================================================================
--- incubator/public/trunk/site-author/projects/wsrp4j.cwiki (original)
+++ incubator/public/trunk/site-author/projects/wsrp4j.xml Mon Jan 30 19:21:03 2006
@@ -1,134 +1,569 @@
-!!! WSRP4J Project Incubation Status
-
-This page tracks the project status, incubator-wise.
-For more general project status, look on the project [website|http://portals.apache.org/wsrp4j/].
-
-!!! Description
-
-The WSRP4J Project is an implementation of WSRP 1.0 Producer. WSRP is an OASIS specification that describes a protocol which allows portlets to be accessed remotely using Web Services.
-
-!!! News
-
-	* We developed Google Summer of Code proposal for a chunk of new features we have a	student ready to implement them.
-	* We voted to move to Subversion and Maven.
-	* We have received contributions from outside developers, which we hope grows into more diverse participation.
-	* I (jmacna@apache.org) have met with constituents from higher education that are using WSRP4J and see a strong role for WSRP in their software plans, and I have encouraged them to contribute to the project publicly.  We have seen increased participation from these teams already.
-
-!!! Project info
-
-|| item              || type                  || reference                 
-|  Website           | www                    | [http://portals.apache.org/wsrp4j/|http://portals.apache.org/wsrp4j/]
-|  .                 | wiki                   | [wsrp4j wiki|http://wiki.apache.org/portals/WSRP4J]
-|  Mailing list      | dev                    | [wsrp4j-dev@portals.apache.org|mailto:wsrp4j-dev@portals.apache.org]
-|  .                 | svn                    | [wsrp4j-commits@portals.apache.org|mailto:wsrp4j-commits@portals.apache.org]
-|  Bug tracking      | JIRA                   | [http://issues.apache.org/jira|http://issues.apache.org/jira]
-|  Source code       | SVN                    | portals/wsrp4j
-|  Mentors           | [rubys@apache.org|mailto:rubys@apache.org]           | Sam Ruby
-|  .                 | [dims@apache.org|mailto:dims@apache.org]             | Davanum Srinivas
-|  Committers        | [jacob@apache.org|mailto:jacob@apache.org]           | Richard Jacob
-|  .                 | [taylor@apache.org|mailto:taylor@apache.org]         | David Sean Taylor
-|  .                 | [jmacna@apache.org|mailto:jmacna@apache.org]         | Julie MacNaught
-|  .                 | [behl@apache.org|mailto:behl@apache.org]             | Stefan Behl
-|  .                 | [cziegeler@apache.org|mailto:cziegeler@apache.org]   | Carsten Ziegeler
-|  .                 | [pfisher@apache.org|mailto:pfisher@apache.org]       | Peter Fischer
-|  .                 | [sgala@apache.org|mailto:sgala@apache.org]           | Santiago Gala
-|  .                 | [acoliver@apache.org|mailto:acoliver@apache.org]     | Andrew C. Oliver
-|  .                 | [dims@apache.org|mailto:dims@apache.org]             | Davanum Srinivas
-|  .                 | [sgoldstein@apache.org|mailto:sgoldstein@apache.org] | Scott Goldstein
-|  .                 | [dlouzan@apache.org|mailto:dlouzan@apache.org]       | Diego Louzan Martinez
-|  Extra             | .                      | .
-  
-
-!!! Incubation work items
-
-!! Project Setup
-
-This is the first phase on incubation, needed to start the project at Apache.
-
-'' Item assignment is shown by the Apache id.''
-'' Completed tasks are shown by the completion date (YYYY-MM-dd). ''
-
-! Identify the project to be incubated
-|| date || item
-| 2003-07-25 | 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.
-| N/A        | If request from an existing Apache project to adopt an external package, then ask the Apache project for the cvs module and mail address names.
-| 2003-01-21 | If request from outside Apache to enter an existing Apache project, then post a message to that project for them to decide on acceptance.
-| N/A        | 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.
-
-! Interim responsibility
-
-|| date || item
-| 2003-07-25 | Identify all the Mentors for the incubation, by asking all that can be Mentors. 
-| 2003-09-03 | Subscribe all Mentors on the pmc and general lists. 
-| 2003-09-03 | Give all Mentors access to all incubator CVS modules. (to be done by PMC chair)  
-| 2003-09-03 | Tell Mentors to track progress in the file 'incubator/projects/{project.name}.cwiki' 
-
-! Copyright
-
-|| date || item
-| 2003-09-02 | 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. 
-| 2004-03-09 | Check and make sure that the files that have been donated have been updated to reflect the new ASF copyright. 
-
-! Verify distribution rights
-
-|| date || item
-| 2003-08-.. | 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. 
-| 2003-08-.. | 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.
-
-! Establish a list of active committers
-
-|| date || item
-| 2003-09-03 | Check that all active committers have submitted a contributors agreement. 
-| 2004-01-07 | Add all active committers in the STATUS file. 
-| 2003-09-03 | Ask root for the creation of committers' accounts on cvs.apache.org. 
-
-! Infrastructure
-
-|| date || item
-| 2003-09-03 | Ask infrastructure to create source repository modules and add thecommitters to the avail file. 
-| 2003-09-03 | Ask infrastructure to set up and archive Mailing lists. 
-| 2003-09-03 | Decide about and then ask infrastructure to setup an issuetracking system (Bugzilla, Scarab, Jira). 
-| 2003-09-03 | Migrate the project to our infrastructure. 
-
-! Project specific 
-
-''Add project specific tasks here.''
-
-!! Incubation 
-
-These action items have to be checked for during the whole incubation process.
-
-'' These items are not to be signed as done during incubation, as they may change during incubation.  ''
-'' They are to be looked into and described in the status reports and completed in the request for incubation signoff.  ''
-
-! Collaborative Development 
-
-* Have all of the active long-term volunteers been identified and acknowledged as committers on the project?
-	Yes
-* 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.)
-	Yes.
-* Are project decisions being made in public by the committers?
-    Yes
-* Are the decision-making guidelines published and agreed to by all of the committers?
-
-! Licensing awareness 
-
-* Are all licensing, trademark, credit issues being taken care of and acknowleged by all committers?
-    Yes
-
-! Project Specific 
-
-''Add project specific tasks here.''
-
-!! Exit 
-
-''Things to check for before voting the project out.''
-
-! Organizational acceptance of responsibility for the project 
-
-* If graduating to an existing PMC, has the PMC voted to accept it?
-* If graduating to a new PMC, has the board voted to accept it?
-
-! Incubator sign-off 
-
-* Has the Incubator decided that the project has accomplished all of the above tasks?
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<document>
+  <properties>
+    <title>wsrp4j
+</title>
+  </properties>
+  <body>
+    <section id="WSRP4J+Project+Incubation+Status">
+      <title>WSRP4J Project Incubation Status
+</title>
+      <p>This page tracks the project status, incubator-wise. For more general
+project status, look on the project
+
+        <a href="http://portals.apache.org/wsrp4j/">website
+</a>.
+
+      </p>
+    </section>
+    <section id="Description">
+      <title>Description
+</title>
+      <p>The WSRP4J Project is an implementation of WSRP 1.0 Producer. WSRP is
+an OASIS specification that describes a protocol which allows
+portlets to be accessed remotely using Web Services.
+</p>
+    </section>
+    <section id="News">
+      <title>News
+</title>
+      <ul>
+        <li>We developed Google Summer of Code proposal for a chunk of new
+features we have a student ready to implement them.
+</li>
+        <li>We voted to move to Subversion and Maven.
+</li>
+        <li>We have received contributions from outside developers, which we hope
+grows into more diverse participation.
+</li>
+        <li>I (jmacna@apache.org) have met with constituents from higher
+education that are using WSRP4J and see a strong role for WSRP in
+their software plans, and I have encouraged them to contribute to the
+project publicly. We have seen increased participation from these
+teams already.
+</li>
+      </ul>
+    </section>
+    <section id="Project+info">
+      <title>Project info
+</title>
+      <table>
+        <tr>
+          <th>item
+</th>
+          <th>type
+</th>
+          <th>reference
+</th>
+        </tr>
+        <tr>
+          <td>Website
+</td>
+          <td>www
+</td>
+          <td>
+            <a href="http://portals.apache.org/wsrp4j/">http://portals.apache.org/wsrp4j/
+</a>
+          </td>
+        </tr>
+        <tr>
+          <td>.
+</td>
+          <td>wiki
+</td>
+          <td>
+            <a href="http://wiki.apache.org/portals/WSRP4J">wsrp4j wiki
+</a>
+          </td>
+        </tr>
+        <tr>
+          <td>Mailing list
+</td>
+          <td>dev
+</td>
+          <td>
+            <a href="mailto:wsrp4j-dev@portals.apache.org">wsrp4j-dev@portals.apache.org
+</a>
+          </td>
+        </tr>
+        <tr>
+          <td>.
+</td>
+          <td>svn
+</td>
+          <td>
+            <a href="mailto:wsrp4j-commits@portals.apache.org">wsrp4j-commits@portals.apache.org
+</a>
+          </td>
+        </tr>
+        <tr>
+          <td>Bug tracking
+</td>
+          <td>JIRA
+</td>
+          <td>
+            <a href="http://issues.apache.org/jira">http://issues.apache.org/jira
+</a>
+          </td>
+        </tr>
+        <tr>
+          <td>Source code
+</td>
+          <td>SVN
+</td>
+          <td>portals/wsrp4j
+</td>
+        </tr>
+        <tr>
+          <td>Mentors
+</td>
+          <td>
+            <a href="mailto:rubys@apache.org">rubys@apache.org
+</a>
+          </td>
+          <td>Sam Ruby
+</td>
+        </tr>
+        <tr>
+          <td>.
+</td>
+          <td>
+            <a href="mailto:dims@apache.org">dims@apache.org
+</a>
+          </td>
+          <td>Davanum Srinivas
+</td>
+        </tr>
+        <tr>
+          <td>Committers
+</td>
+          <td>
+            <a href="mailto:jacob@apache.org">jacob@apache.org
+</a>
+          </td>
+          <td>Richard Jacob
+</td>
+        </tr>
+        <tr>
+          <td>.
+</td>
+          <td>
+            <a href="mailto:taylor@apache.org">taylor@apache.org
+</a>
+          </td>
+          <td>David Sean Taylor
+</td>
+        </tr>
+        <tr>
+          <td>.
+</td>
+          <td>
+            <a href="mailto:jmacna@apache.org">jmacna@apache.org
+</a>
+          </td>
+          <td>Julie MacNaught
+</td>
+        </tr>
+        <tr>
+          <td>.
+</td>
+          <td>
+            <a href="mailto:behl@apache.org">behl@apache.org
+</a>
+          </td>
+          <td>Stefan Behl
+</td>
+        </tr>
+        <tr>
+          <td>.
+</td>
+          <td>
+            <a href="mailto:cziegeler@apache.org">cziegeler@apache.org
+</a>
+          </td>
+          <td>Carsten Ziegeler
+</td>
+        </tr>
+        <tr>
+          <td>.
+</td>
+          <td>
+            <a href="mailto:pfisher@apache.org">pfisher@apache.org
+</a>
+          </td>
+          <td>Peter Fischer
+</td>
+        </tr>
+        <tr>
+          <td>.
+</td>
+          <td>
+            <a href="mailto:sgala@apache.org">sgala@apache.org
+</a>
+          </td>
+          <td>Santiago Gala
+</td>
+        </tr>
+        <tr>
+          <td>.
+</td>
+          <td>
+            <a href="mailto:acoliver@apache.org">acoliver@apache.org
+</a>
+          </td>
+          <td>Andrew C. Oliver
+</td>
+        </tr>
+        <tr>
+          <td>.
+</td>
+          <td>
+            <a href="mailto:dims@apache.org">dims@apache.org
+</a>
+          </td>
+          <td>Davanum Srinivas
+</td>
+        </tr>
+        <tr>
+          <td>.
+</td>
+          <td>
+            <a href="mailto:sgoldstein@apache.org">sgoldstein@apache.org
+</a>
+          </td>
+          <td>Scott Goldstein
+</td>
+        </tr>
+        <tr>
+          <td>.
+</td>
+          <td>
+            <a href="mailto:dlouzan@apache.org">dlouzan@apache.org
+</a>
+          </td>
+          <td>Diego Louzan Martinez
+</td>
+        </tr>
+        <tr>
+          <td>Extra
+</td>
+          <td>.
+</td>
+          <td>.
+</td>
+        </tr>
+      </table>
+    </section>
+    <section id="Incubation+work+items">
+      <title>Incubation work items
+</title>
+      <section id="Project+Setup">
+        <title>Project Setup
+</title>
+        <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>
+        <section id="Identify+the+project+to+be+incubated">
+          <title>Identify the project to be incubated
+</title>
+          <table>
+            <tr>
+              <th>date
+</th>
+              <th>item
+</th>
+            </tr>
+            <tr>
+              <td>2003-07-25
+</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>N/A
+</td>
+              <td>If request from an existing Apache project to adopt an external
+package, then ask the Apache project for the cvs module and mail
+address names.
+</td>
+            </tr>
+            <tr>
+              <td>2003-01-21
+</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>N/A
+</td>
+              <td>If request from anywhere to become a stand-alone PMC, then assess the
+fit with the ASF, and create the lists and modules under the
+incubator address/module names if accepted.
+</td>
+            </tr>
+          </table>
+        </section>
+        <section id="Interim+responsibility">
+          <title>Interim responsibility
+</title>
+          <table>
+            <tr>
+              <th>date
+</th>
+              <th>item
+</th>
+            </tr>
+            <tr>
+              <td>2003-07-25
+</td>
+              <td>Identify all the Mentors for the incubation, by asking all that can
+be Mentors.
+</td>
+            </tr>
+            <tr>
+              <td>2003-09-03
+</td>
+              <td>Subscribe all Mentors on the pmc and general lists.
+</td>
+            </tr>
+            <tr>
+              <td>2003-09-03
+</td>
+              <td>Give all Mentors access to all incubator CVS modules. (to be done by
+PMC chair)
+</td>
+            </tr>
+            <tr>
+              <td>2003-09-03
+</td>
+              <td>Tell Mentors to track progress in the file
+'incubator/projects/{project.name}.cwiki'
+</td>
+            </tr>
+          </table>
+        </section>
+        <section id="Copyright">
+          <title>Copyright
+</title>
+          <table>
+            <tr>
+              <th>date
+</th>
+              <th>item
+</th>
+            </tr>
+            <tr>
+              <td>2003-09-02
+</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>2004-03-09
+</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>2003-08-..
+</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>2003-08-..
+</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>
+        </section>
+        <section id="Establish+a+list+of+active+committers">
+          <title>Establish a list of active committers
+</title>
+          <table>
+            <tr>
+              <th>date
+</th>
+              <th>item
+</th>
+            </tr>
+            <tr>
+              <td>2003-09-03
+</td>
+              <td>Check that all active committers have submitted a contributors
+agreement.
+</td>
+            </tr>
+            <tr>
+              <td>2004-01-07
+</td>
+              <td>Add all active committers in the STATUS file.
+</td>
+            </tr>
+            <tr>
+              <td>2003-09-03
+</td>
+              <td>Ask root for the creation of committers' accounts on cvs.apache.org.
+</td>
+            </tr>
+          </table>
+        </section>
+        <section id="Infrastructure">
+          <title>Infrastructure
+</title>
+          <table>
+            <tr>
+              <th>date
+</th>
+              <th>item
+</th>
+            </tr>
+            <tr>
+              <td>2003-09-03
+</td>
+              <td>Ask infrastructure to create source repository modules and add
+thecommitters to the avail file.
+</td>
+            </tr>
+            <tr>
+              <td>2003-09-03
+</td>
+              <td>Ask infrastructure to set up and archive Mailing lists.
+</td>
+            </tr>
+            <tr>
+              <td>2003-09-03
+</td>
+              <td>Decide about and then ask infrastructure to setup an issuetracking
+system (Bugzilla, Scarab, Jira).
+</td>
+            </tr>
+            <tr>
+              <td>2003-09-03
+</td>
+              <td>Migrate the project to our infrastructure.
+</td>
+            </tr>
+          </table>
+        </section>
+        <section id="Project+specific">
+          <title>Project specific
+</title>
+          <p>
+            <em>Add project specific tasks here.
+</em>
+          </p>
+        </section>
+      </section>
+      <section id="Incubation">
+        <title>Incubation
+</title>
+        <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>
+        <section id="Collaborative+Development">
+          <title>Collaborative Development
+</title>
+          <ul>
+            <li>Have all of the active long-term volunteers been identified and
+acknowledged as committers on the project? Yes
+</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.) Yes.
+</li>
+            <li>Are project decisions being made in public by the committers? Yes
+</li>
+            <li>Are the decision-making guidelines published and agreed to by all of
+the committers?
+</li>
+          </ul>
+        </section>
+        <section id="Licensing+awareness">
+          <title>Licensing awareness
+</title>
+          <ul>
+            <li>Are all licensing, trademark, credit issues being taken care of and
+acknowleged by all committers? Yes
+</li>
+          </ul>
+        </section>
+        <section id="Project+Specific">
+          <title>Project Specific
+</title>
+          <p>
+            <em>Add project specific tasks here.
+</em>
+          </p>
+        </section>
+      </section>
+      <section id="Exit">
+        <title>Exit
+</title>
+        <p>
+          <em>Things to check for before voting the project out.
+</em>
+        </p>
+        <section id="Organizational+acceptance+of+responsibility+for+the+project">
+          <title>Organizational acceptance of responsibility for the project
+</title>
+          <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>
+        </section>
+        <section id="Incubator+sign-off">
+          <title>Incubator sign-off
+</title>
+          <ul>
+            <li>Has the Incubator decided that the project has accomplished all of
+the above tasks?
+</li>
+          </ul>
+        </section>
+      </section>
+    </section>
+  </body>
+</document>

Copied: incubator/public/trunk/site-author/projects/xmlbeans.xml (from r373662, incubator/public/trunk/site-author/projects/xmlbeans.cwiki)
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site-author/projects/xmlbeans.xml?p2=incubator/public/trunk/site-author/projects/xmlbeans.xml&p1=incubator/public/trunk/site-author/projects/xmlbeans.cwiki&r1=373662&r2=373682&rev=373682&view=diff
==============================================================================
--- incubator/public/trunk/site-author/projects/xmlbeans.cwiki (original)
+++ incubator/public/trunk/site-author/projects/xmlbeans.xml Mon Jan 30 19:21:03 2006
@@ -1,322 +1,361 @@
-!!!XmlBeans Project Incubation status
-
-----
-
-__NOTE: XMLBeans has graduated from Incubation__ - please see [http://xml.apache.org/xmlbeans/]
-
-----
-
-!!!Tasks completed:
-
-* create STATUS file in incubator-cvs
-* create mailing lists
-* create xml-xmlbeans CVS
-** configure viewcvs
-** commit mails -> xml-xmlbeans-cvs@apache.org
-* setup xmlbeans bugzilla
-* Complete License Grant agreement
-* Have all committers sign CLA's
-** Cezar Andrei
-** David Bau 
-** Patrick Calahan
-** Ken Kress 
-** Laurence Moroney 
-** David Remy 
-** Dutta Satadip
-** Cliff Schmidt 
-** Eric Vasilik 
-** David Waite
-** Scott Ziegler
-* Relicense XML beans files with ASL 2.0
-** add ASF copyright to all files
-** move all packages to org.apache.xmlbeans
-** eliminate all non ASL code and library dependencies
-* mailing list tasks
-** lists-archived:
-*** mbox -> xml.apache.org/mail
-*** Eyebrowse setup
-* setup xmlbeans wiki area and refactor pages to there
-* set up to sign builds
-** committer PGP keys
-** committer keys signed by someone in ASF (probably twl)
-* build xmlbeans website
-* grant some comitters access to xml-site
-* Define incubation exit criteria
-* configure build to match ASF style
-* setup mirroring of builds
-
-----
-
-!!!Exit criteria (put an X next to item when it is complete):
-
-!!Identify the project to be incubated: XMLBeans
-
-  X- 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.
-
-  X- If request from an existing Apache project to adopt an external
-     package, then ask the Apache project for the cvs module and mail
-     address names.
-
-      xml-xmlbeans
-
-      xmlbeans-dev@xml.apache.org
-      xmlbeans-user@xml.apache.org
-      xmlbeans-cvs@xml.apache.org
-
-  X- If request from outside Apache to enter an existing Apache project,
-     then post a message to that project for them to decide on acceptance.
-
-  X- 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.
-
-!!Interim responsibility:
-
-  X- Who has been identified as the shepherd for the incubation?
-
-      Ted Leung <twl@apache.org>
-
-  X- Are they tracking progress in the file
-
-      incubator:site/projects/xmlbeans.cwiki
-
-!!Copyright:
-
-  X- Have 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.
-
-  X- Have the files been updated to reflect the new ASF copyright?
-
-!!Verify distribution rights:
-
-  X- For all code included with the distribution that is not under the
-     Apache license, do we have the right to combine with Apache-licensed
-     code and redistribute?
-
-  X- Is all source code distributed by the project 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?
-
-!!Establish a list of active committers:
-
-  X- Are all active committers in the STATUS file?
-
-  X- Do they have accounts on cvs.apache.org?
-
-  X- Have they submitted a contributors agreement?
-
-!!Infrastructure:
-
-  X- CVS modules created and committers added to avail file?
-
-  X- Mailing lists set up and archived?
-
-  X- Problem tracking system (Jira)?
-
-  X- Has the project migrated to our infrastructure?
-
-!!Collaborative Development:
-
-  X- Have all of the active long-term volunteers been identified
-     and acknowledged as committers on the project?
-
-  X- Are there three or more independent committers?
-
-  X- Are project decisions being made in public by the committers?
-
-  X- Are the decision-making guidelines published and agreed to by
-     all of the committers?
-
-!!Organizational acceptance of responsibility for the project:
-
-  N/A If graduating to an existing PMC, has the PMC voted to accept it?
-
-  X- If graduating to a new PMC, has the board voted to accept it?
-
-!!Incubator sign-off:
-
-  X- Has the Incubator decided that the project has accomplished all
-     of the above tasks?
-
-!!!Incubation Status Reports
-
-!!2004-04-20
-{{{
-- Status report for the Incubator -
-
-Changes since last report in January:
-* Added Dutta Satadip as a committer 
-* Released incubating-xmlbeans-1.0.2 after a thorough legal review
-** after review of license issues: added jaxen to distribution, removed junit, noted W3C XML Schemas
-** applied Apache License 2.0
-* Formed a PPMC; set up mailing list and designed guidelines
-* Moved from bugzilla to JIRA.
-* Set up new wiki pages.
-
-Expectations for next three months:
-* Find two more committers
-* Release one more distribution
-* Improve web site (faq, current info, etc)
-* Exit incubator
-}}}
-
-!!2004-01-17 
-{{{
-
-- Status report for the Incubator -
-
-Overall the xmlbeans project is progressing with good committer
-productivity and a growing user community.  Converting over the Apache
-CVS systems and build process has been accomplished along with various
-other Apache administrative tasks such as setting up the Apache website.
-
-There is some movement towards growth in the development side of the
-community with one contributor (Dutta Satadip) submitting a nice
-enhancement and several other contributors submitting small patches
-related to bugs.
-
-More on each of the bullet points below.
-
-* is the STATUS file up to date? (also post link)
-
-<Cliff Schmidt>
-We need to update the status file with the latest incubator guidelines.
-We're mostly there, but there are a couple things that need to be added.
-I also think the status file needs to be updated in one or two other ways.
-For instance, the tasks completed should now include:
-- build xmlbeans website 
-- grant some committers access to xml-site (Cliff and Remy)
-</Cliff Schmidt>
-
-http://incubator.apache.org/projects/xmlbeans.html
-
-* any legal, cross-project or personal issues
-  that still need to be addressed?
-
-In general it appears xmlbeans is through most of the known issues 
-that existed getting started.  The committers have been able to be 
-productive and there is a lot of code being created in version 2 
-and fixes are being made into version 1.
-
-One issue that we have run into is how best to accommodate commonly 
-used api jars primarily (but not exclusively) JCP related api's from 
-SUN.  We are not sure the appropriate process to determine whether 
-we can use a particular jar and host the jar in the xmlbeans build.  
-examples of api's that we are unsure the appropriate/best way to deal 
-with are:
-
-  * JSR173 api and JSR 173 RI (Streaming API for XML, a.k.a., STAX) - 
-    the JSR173 RI dependency is temporary.  Currently xmlbeans downloads 
-    it from external server during the build process
-  * SAAJ api - we used the saaj-api source code in axis.  
-  * xml commons resolver (Apache jakarta)
-  * jaxen  (jaxen.sourceforge.net - apache-style license, but not apache)
-
-Here are some specific questions on this subject that David Bau posted:
-
-<David Bau>
-- We currently load resolver.jar and jaxen.jar if the user happens to put
-them on the classpath, and throw a runtime exception if the user tries to
-use a resolver- or jaxen- dependent feature without those JARs present.
-This is OK, but it would be nicer for users if resolver and jaxen were just
-included in xbean.jar, but this presents both licensing issues (for jaxen)
-and possible-version-conflict issues (for commons resolver).  A question is:
-is there a nice way we include resolver.jar and jaxen.jar inside xbean.jar,
-or should we stay away from that idea?
-
-- We need the JSR 173 API to run, and this is definitely something that we
-want to be able to distribute either directly inside xbean.jar, or at least
-directly inside Apache since it's so core.  In other words, we can't expect
-users to do anything without this API present.  I've noticed that for other
-APIs, such as SAAJ, Apache seems to have a "clean room" copy of the APIs.
-Should we be making such a copy of the JSR 173 APIs?  What is the right way
-to do this?
-</David Bau>
-
-* what has been done for incubation since the last report?
-
-<David Bau>
-The main thing is that we've been working on the project.  We're getting
-more folks hanging around on the lists; we're getting some of the code that
-we've talked about on the lists and on the wiki actually written and checked
-in.  We've been encouraging the wider community to critique and contribute
-ideas and code. Community-building is a gradual process; we don't have a
-mature community yet, but we've certainly gotten started at building a little
-one.
-</David Bau>
-
- *  source code checkin (was that since last status report?)
- *  build and test ant scripts established
- *  website updated including docs, source code access, etc.
- *  established version 2 effort and modified CVS tree accordingly
- *  proposed (close to implementing I think) branching strategy for 
-    version 1 (by Kevin Krouse)
- *  gump integration (thanks to Robert Burrell Donkin)
-
-
-* plans and expectations for the next period?
-
- * development on v2 will continue incorporating community feedback.
- * continued work on soliciting volunteers for contribution and committership.
- * work on organizing bug tracking and follow up
- * xmlbeans-1.01 distribution (minor bug fixes to v1) 
- * improve process of bug testing and fixing from BugZilla contributions.
-
-* any recommendations for how incubation could run
-   more smoothly for you?
-
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<document>
+  <properties>
+    <title>xmlbeans
+</title>
+  </properties>
+  <body>
+    <section id="XmlBeans+Project+Incubation+status">
+      <title>XmlBeans Project Incubation status
+</title>
+      <p>----------------------------------------------------------------------
+---------
+</p>
+      <p>
+        <strong>NOTE: XMLBeans has graduated from Incubation
+</strong>- please see
+
+        <a href="http://xml.apache.org/xmlbeans/">http://xml.apache.org/xmlbeans/
+</a>
+      </p>
+      <p>----------------------------------------------------------------------
+---------
+</p>
+    </section>
+    <section id="Tasks+completed%3A">
+      <title>Tasks completed:
+</title>
+      <ul>
+        <li>create STATUS file in incubator-cvs
+</li>
+        <li>create mailing lists
+</li>
+        <li>create xml-xmlbeans CVS
+</li>
+        <ul>
+          <li>configure viewcvs
+</li>
+          <li>commit mails -&gt; xml-xmlbeans-cvs@apache.org
+</li>
+        </ul>
+        <li>setup xmlbeans bugzilla
+</li>
+        <li>Complete License Grant agreement
+</li>
+        <li>Have all committers sign CLA's
+</li>
+        <ul>
+          <li>Cezar Andrei
+</li>
+          <li>David Bau
+</li>
+          <li>Patrick Calahan
+</li>
+          <li>Ken Kress
+</li>
+          <li>Laurence Moroney
+</li>
+          <li>David Remy
+</li>
+          <li>Dutta Satadip
+</li>
+          <li>Cliff Schmidt
+</li>
+          <li>Eric Vasilik
+</li>
+          <li>David Waite
+</li>
+          <li>Scott Ziegler
+</li>
+        </ul>
+        <li>Relicense XML beans files with ASL 2.0
+</li>
+        <ul>
+          <li>add ASF copyright to all files
+</li>
+          <li>move all packages to org.apache.xmlbeans
+</li>
+          <li>eliminate all non ASL code and library dependencies
+</li>
+        </ul>
+        <li>mailing list tasks
+</li>
+        <ul>
+          <li>lists-archived:
+</li>
+          <ul>
+            <li>mbox -&gt; xml.apache.org/mail
+</li>
+            <li>Eyebrowse setup
+</li>
+          </ul>
+        </ul>
+        <li>setup xmlbeans wiki area and refactor pages to there
+</li>
+        <li>set up to sign builds
+</li>
+        <ul>
+          <li>committer PGP keys
+</li>
+          <li>committer keys signed by someone in ASF (probably twl)
+</li>
+        </ul>
+        <li>build xmlbeans website
+</li>
+        <li>grant some comitters access to xml-site
+</li>
+        <li>Define incubation exit criteria
+</li>
+        <li>configure build to match ASF style
+</li>
+        <li>setup mirroring of builds
+</li>
+      </ul>
+      <p>----------------------------------------------------------------------
+---------
+</p>
+    </section>
+    <section id="Exit+criteria+%28put+an+X+next+to+item+when+it+is+complete%29%3A">
+      <title>Exit criteria (put an X next to item when it is complete):
+</title>
+      <section id="Identify+the+project+to+be+incubated%3A+XMLBeans">
+        <title>Identify the project to be incubated: XMLBeans
+</title>
+        <p>X- 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.
+</p>
+        <p>X- If request from an existing Apache project to adopt an external
+package, then ask the Apache project for the cvs module and mail
+address names.
+</p>
+        <p>xml-xmlbeans
+</p>
+        <p>xmlbeans-dev@xml.apache.org xmlbeans-user@xml.apache.org
+xmlbeans-cvs@xml.apache.org
+</p>
+        <p>X- If request from outside Apache to enter an existing Apache
+project, then post a message to that project for them to decide on
+acceptance.
+</p>
+        <p>X- 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.
+</p>
+      </section>
+      <section id="Interim+responsibility%3A">
+        <title>Interim responsibility:
+</title>
+        <p>X- Who has been identified as the shepherd for the incubation?
+</p>
+        <p>Ted Leung &lt;twl@apache.org&gt;
+</p>
+        <p>X- Are they tracking progress in the file
+</p>
+        <p>incubator:site/projects/xmlbeans.cwiki
+</p>
+      </section>
+      <section id="Copyright%3A">
+        <title>Copyright:
+</title>
+        <p>X- Have 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.
+</p>
+        <p>X- Have the files been updated to reflect the new ASF copyright?
+</p>
+      </section>
+      <section id="Verify+distribution+rights%3A">
+        <title>Verify distribution rights:
+</title>
+        <p>X- For all code included with the distribution that is not under the
+Apache license, do we have the right to combine with Apache-licensed
+code and redistribute?
+</p>
+        <p>X- Is all source code distributed by the project 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?
+</p>
+      </section>
+      <section id="Establish+a+list+of+active+committers%3A">
+        <title>Establish a list of active committers:
+</title>
+        <p>X- Are all active committers in the STATUS file?
+</p>
+        <p>X- Do they have accounts on cvs.apache.org?
+</p>
+        <p>X- Have they submitted a contributors agreement?
+</p>
+      </section>
+      <section id="Infrastructure%3A">
+        <title>Infrastructure:
+</title>
+        <p>X- CVS modules created and committers added to avail file?
+</p>
+        <p>X- Mailing lists set up and archived?
+</p>
+        <p>X- Problem tracking system (Jira)?
+</p>
+        <p>X- Has the project migrated to our infrastructure?
+</p>
+      </section>
+      <section id="Collaborative+Development%3A">
+        <title>Collaborative Development:
+</title>
+        <p>X- Have all of the active long-term volunteers been identified and
+acknowledged as committers on the project?
+</p>
+        <p>X- Are there three or more independent committers?
+</p>
+        <p>X- Are project decisions being made in public by the committers?
+</p>
+        <p>X- Are the decision-making guidelines published and agreed to by all
+of the committers?
+</p>
+      </section>
+      <section id="Organizational+acceptance+of+responsibility+for+the+project%3A">
+        <title>Organizational acceptance of responsibility for the project:
+</title>
+        <p>N/A If graduating to an existing PMC, has the PMC voted to accept it?
+</p>
+        <p>X- If graduating to a new PMC, has the board voted to accept it?
+</p>
+      </section>
+      <section id="Incubator+sign-off%3A">
+        <title>Incubator sign-off:
+</title>
+        <p>X- Has the Incubator decided that the project has accomplished all of
+the above tasks?
+</p>
+      </section>
+    </section>
+    <section id="Incubation+Status+Reports">
+      <title>Incubation Status Reports
+</title>
+      <section id="2004-04-20">
+        <title>2004-04-20
+</title>
+        <source>- Status report for the Incubator - Changes since last report in
+January: * Added Dutta Satadip as a committer * Released
+incubating-xmlbeans-1.0.2 after a thorough legal review ** after
+review of license issues: added jaxen to distribution, removed junit,
+noted W3C XML Schemas ** applied Apache License 2.0 * Formed a PPMC;
+set up mailing list and designed guidelines * Moved from bugzilla to
+JIRA. * Set up new wiki pages. Expectations for next three months: *
+Find two more committers * Release one more distribution * Improve
+web site (faq, current info, etc) * Exit incubator
+</source>
+      </section>
+      <section id="2004-01-17">
+        <title>2004-01-17
+</title>
+        <source>- Status report for the Incubator - Overall the xmlbeans project is
+progressing with good committer productivity and a growing user
+community. Converting over the Apache CVS systems and build process
+has been accomplished along with various other Apache administrative
+tasks such as setting up the Apache website. There is some movement
+towards growth in the development side of the community with one
+contributor (Dutta Satadip) submitting a nice enhancement and several
+other contributors submitting small patches related to bugs. More on
+each of the bullet points below. * is the STATUS file up to date?
+(also post link) &lt;Cliff Schmidt&gt; We need to update the status file
+with the latest incubator guidelines. We're mostly there, but there
+are a couple things that need to be added. I also think the status
+file needs to be updated in one or two other ways. For instance, the
+tasks completed should now include: - build xmlbeans website - grant
+some committers access to xml-site (Cliff and Remy) &lt;/Cliff Schmidt&gt;
+http://incubator.apache.org/projects/xmlbeans.html * any legal,
+cross-project or personal issues that still need to be addressed? In
+general it appears xmlbeans is through most of the known issues that
+existed getting started. The committers have been able to be
+productive and there is a lot of code being created in version 2 and
+fixes are being made into version 1. One issue that we have run into
+is how best to accommodate commonly used api jars primarily (but not
+exclusively) JCP related api's from SUN. We are not sure the
+appropriate process to determine whether we can use a particular jar
+and host the jar in the xmlbeans build. examples of api's that we are
+unsure the appropriate/best way to deal with are: * JSR173 api and
+JSR 173 RI (Streaming API for XML, a.k.a., STAX) - the JSR173 RI
+dependency is temporary. Currently xmlbeans downloads it from
+external server during the build process * SAAJ api - we used the
+saaj-api source code in axis. * xml commons resolver (Apache jakarta)
+* jaxen (jaxen.sourceforge.net - apache-style license, but not
+apache) Here are some specific questions on this subject that David
+Bau posted: &lt;David Bau&gt; - We currently load resolver.jar and
+jaxen.jar if the user happens to put them on the classpath, and throw
+a runtime exception if the user tries to use a resolver- or jaxen-
+dependent feature without those JARs present. This is OK, but it
+would be nicer for users if resolver and jaxen were just included in
+xbean.jar, but this presents both licensing issues (for jaxen) and
+possible-version-conflict issues (for commons resolver). A question
+is: is there a nice way we include resolver.jar and jaxen.jar inside
+xbean.jar, or should we stay away from that idea? - We need the JSR
+173 API to run, and this is definitely something that we want to be
+able to distribute either directly inside xbean.jar, or at least
+directly inside Apache since it's so core. In other words, we can't
+expect users to do anything without this API present. I've noticed
+that for other APIs, such as SAAJ, Apache seems to have a "clean
+room" copy of the APIs. Should we be making such a copy of the JSR
+173 APIs? What is the right way to do this? &lt;/David Bau&gt; * what has
+been done for incubation since the last report? &lt;David Bau&gt; The main
+thing is that we've been working on the project. We're getting more
+folks hanging around on the lists; we're getting some of the code
+that we've talked about on the lists and on the wiki actually written
+and checked in. We've been encouraging the wider community to
+critique and contribute ideas and code. Community-building is a
+gradual process; we don't have a mature community yet, but we've
+certainly gotten started at building a little one. &lt;/David Bau&gt; *
+source code checkin (was that since last status report?) * build and
+test ant scripts established * website updated including docs, source
+code access, etc. * established version 2 effort and modified CVS
+tree accordingly * proposed (close to implementing I think) branching
+strategy for version 1 (by Kevin Krouse) * gump integration (thanks
+to Robert Burrell Donkin) * plans and expectations for the next
+period? * development on v2 will continue incorporating community
+feedback. * continued work on soliciting volunteers for contribution
+and committership. * work on organizing bug tracking and follow up *
+xmlbeans-1.01 distribution (minor bug fixes to v1) * improve process
+of bug testing and fixing from BugZilla contributions. * any
+recommendations for how incubation could run more smoothly for you?
 Incubation seems to be going well with one, albeit an important one,
-challenge of getting outside committers.  Having a large existing
-codebase in a fairly complicated area makes it challenging.  The growing
-user community and the excellent posts that we are getting on the
-xmbleans-dev list make us optimistic we will make some breakthroughs
-in the next period.
-
-* things that xmlbeans could/will improve on (summary, contributed by Cliff Schmidt)
-
-1. Bug management: http://nagoya.apache.org/bugzilla/buglist.cgi?product=XMLBeans
-(as has already been mentioned by one or two others) 
--- This is just as much related to community as code.  Of the 12 bugs
-entered so far, we haven't done a very good job of keeping them updated
-with status.  We should encourage people to file bugs by showing that
-the committers are actually responding to them (even if the response
-is "need more info to repro" or simply noting the priority).
-
-2. Web site: http://xml.apache.org/xmlbeans/
--- We got this built and running but we need to keep it updated.  For 
-instance, it still shows the ApacheCon advertisement.  
-
-3. Binary download.  
--- We started to get this done, but I don't think we ever finished.  
-Actually, I'd like to try to get this done in the next couple days.
-
-4. PPMC
--- The incubator introduced the idea of a PPMC and we haven't responded
-to this yet.  I'll follow up in a separate post on what needs to be done.
-
-5. Status file
--- We need to update the status file with the latest incubator guidelines.
-We're mostly there, but there are a couple things that need to be added.
-I also think the status file needs to be updated in one or two other ways.
-For instance, the tasks completed should now include:
-- build xmlbeans website 
-- grant some committers access to xml-site (although I forgot who has this;
-I think it is me and Remy)
-
-6. Committer keys 
-Bau and I were both able to make it to ApacheCon and we both participated in
-the key-signing party.  We need to get other committers to make keys and 
-get them signed by me and Bau whenever we run into each other in person 
-again.
-
-7. New Committers
-The biggest issue of all is definitely the new committers, as everyone
-seems to agree.  We really need to find more ways to encourage others to
-contribute.   I think we are all ready and willing to share some of the
-responsibility; we just need to find people who are showing enough interest
-(and action) to be considered for committership.
-
-}}}
+challenge of getting outside committers. Having a large existing
+codebase in a fairly complicated area makes it challenging. The
+growing user community and the excellent posts that we are getting on
+the xmbleans-dev list make us optimistic we will make some
+breakthroughs in the next period. * things that xmlbeans could/will
+improve on (summary, contributed by Cliff Schmidt) 1. Bug management:
+http://nagoya.apache.org/bugzilla/buglist.cgi?product=XMLBeans (as
+has already been mentioned by one or two others) -- This is just as
+much related to community as code. Of the 12 bugs entered so far, we
+haven't done a very good job of keeping them updated with status. We
+should encourage people to file bugs by showing that the committers
+are actually responding to them (even if the response is "need more
+info to repro" or simply noting the priority). 2. Web site:
+http://xml.apache.org/xmlbeans/ -- We got this built and running but
+we need to keep it updated. For instance, it still shows the
+ApacheCon advertisement. 3. Binary download. -- We started to get
+this done, but I don't think we ever finished. Actually, I'd like to
+try to get this done in the next couple days. 4. PPMC -- The
+incubator introduced the idea of a PPMC and we haven't responded to
+this yet. I'll follow up in a separate post on what needs to be done.
+5. Status file -- We need to update the status file with the latest
+incubator guidelines. We're mostly there, but there are a couple
+things that need to be added. I also think the status file needs to
+be updated in one or two other ways. For instance, the tasks
+completed should now include: - build xmlbeans website - grant some
+committers access to xml-site (although I forgot who has this; I
+think it is me and Remy) 6. Committer keys Bau and I were both able
+to make it to ApacheCon and we both participated in the key-signing
+party. We need to get other committers to make keys and get them
+signed by me and Bau whenever we run into each other in person again.
+7. New Committers The biggest issue of all is definitely the new
+committers, as everyone seems to agree. We really need to find more
+ways to encourage others to contribute. I think we are all ready and
+willing to share some of the responsibility; we just need to find
+people who are showing enough interest (and action) to be considered
+for committership.
+</source>
+      </section>
+    </section>
+  </body>
+</document>

Copied: incubator/public/trunk/site-author/resolution.xml (from r373662, incubator/public/trunk/site-author/resolution.html)
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site-author/resolution.xml?p2=incubator/public/trunk/site-author/resolution.xml&p1=incubator/public/trunk/site-author/resolution.html&r1=373662&r2=373682&rev=373682&view=diff
==============================================================================
--- incubator/public/trunk/site-author/resolution.html (original)
+++ incubator/public/trunk/site-author/resolution.xml Mon Jan 30 19:21:03 2006
@@ -1,95 +1,75 @@
-<!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>Incubator Formation Resolution</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>Resolution that Created the Incubator Project</h1>
-      
-      
-<p>Here is the text of the ASF Board resolution that was adopted
-      in October 2002
-      <!--
+<?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>Incubator Formation Resolution
+</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="Resolution+that+Created+the+Incubator+Project">
+      <title>Resolution that Created the Incubator Project
+</title>
+      <p>Here is the text of the ASF Board resolution that was adopted in
+October 2002
+<!--
       (see the
       <link href="http://www.apache.org/foundation/records/minutes/"
         >meeting minutes</link>)
-       -->
-      and thereby created the Incubator project:</p>
-
-<pre class="code">
-        WHEREAS, the Board of Directors deems it to be in the best
-        interests of the Foundation and consistent with the
-        Foundation's purpose to establish a Project Management
-        Committee charged with accepting new products into the
-        Foundation, providing guidance and support to help each new
-        product engender their own collaborative community, educating
-        new developers in the philosophy and guidelines for
-        collaborative development as defined by the members of the
-        Foundation, and proposing to the board the promotion of such
-        products to independent PMC status once their community has
-        reached maturity.
-
-        NOW, THEREFORE, BE IT RESOLVED, that a Project Management
-        Committee (PMC), to be known as the "Apache Incubator PMC", be
-        and hereby is established pursuant to the Bylaws of the
-        Foundation; and be it further
-
-        RESOLVED, that the Apache Incubator PMC be and hereby is
-        responsible for the acceptance and oversight of new products
-        submitted or proposed to become part of the Foundation; and be
-        it further
-
-        RESOLVED, that the Apache Incubator PMC is responsible for
-        providing guidance and ensuring that subprojects under its
-        purview develop products according to the Foundation's
-        philosophy and guidelines for collaborative development; and be
-        it further
-
-        RESOLVED, that the Apache Incubator PMC is responsible for
-        regularly evaluating products under its purview and making the
-        determination in each case of whether the product should be
-        abandoned, continue to receive guidance and support, or
-        proposed to the board for promotion to full project status as
-        part of an existing or new Foundation PMC; and be it further
-
-        RESOLVED, that the office of "Vice President, Apache Incubator"
-        be and hereby is created, the person holding such office to
-        serve at the direction of the Board of Directors as the chair
-        of the Apache Incubator PMC, and to have primary responsibility
-        for management of the subprojects within the scope and
-        responsibility of the Apache Incubator PMC; and be it further
-
-        RESOLVED, that the persons listed immediately below be and
-        hereby are appointed to serve as the initial members of the
-        Apache Incubator PMC:
-        
-          Aaron Bannert
-          Nicola Ken Barozzi
-          Ken Coar
-          Roy T. Fielding
-          B. W. Fitzpatrick
-          Jim Jagielski
-          Greg Stein
-          Sander Striker
-
-        NOW, THEREFORE, BE IT FURTHER RESOLVED, that Jim Jagielski be
-        and hereby is appointed to the office of Vice President, Apache
-        Incubator, to serve in accordance with and subject to the
-        direction of the Board of Directors and the Bylaws of the
-        Foundation until death, resignation, retirement, removal or
-        disqualification, or until a successor is appointed; and be it
-        further
-
-        RESOLVED, that the initial Apache Incubator PMC be and hereby
-        is tasked with the creation of a set of bylaws intended to
-        encourage open development and increased participation in the
-        Apache Incubator Project.
-        </pre>
-    
-  
-</body>
-</html>
+       -->and thereby created the Incubator project:
+</p>
+      <pre class="code">WHEREAS, the Board of Directors deems it to be in the best interests
+of the Foundation and consistent with the Foundation's purpose to
+establish a Project Management Committee charged with accepting new
+products into the Foundation, providing guidance and support to help
+each new product engender their own collaborative community,
+educating new developers in the philosophy and guidelines for
+collaborative development as defined by the members of the
+Foundation, and proposing to the board the promotion of such products
+to independent PMC status once their community has reached maturity.
+NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
+(PMC), to be known as the "Apache Incubator PMC", be and hereby is
+established pursuant to the Bylaws of the Foundation; and be it
+further RESOLVED, that the Apache Incubator PMC be and hereby is
+responsible for the acceptance and oversight of new products
+submitted or proposed to become part of the Foundation; and be it
+further RESOLVED, that the Apache Incubator PMC is responsible for
+providing guidance and ensuring that subprojects under its purview
+develop products according to the Foundation's philosophy and
+guidelines for collaborative development; and be it further RESOLVED,
+that the Apache Incubator PMC is responsible for regularly evaluating
+products under its purview and making the determination in each case
+of whether the product should be abandoned, continue to receive
+guidance and support, or proposed to the board for promotion to full
+project status as part of an existing or new Foundation PMC; and be
+it further RESOLVED, that the office of "Vice President, Apache
+Incubator" be and hereby is created, the person holding such office
+to serve at the direction of the Board of Directors as the chair of
+the Apache Incubator PMC, and to have primary responsibility for
+management of the subprojects within the scope and responsibility of
+the Apache Incubator PMC; and be it further RESOLVED, that the
+persons listed immediately below be and hereby are appointed to serve
+as the initial members of the Apache Incubator PMC: Aaron Bannert
+Nicola Ken Barozzi Ken Coar Roy T. Fielding B. W. Fitzpatrick Jim
+Jagielski Greg Stein Sander Striker NOW, THEREFORE, BE IT FURTHER
+RESOLVED, that Jim Jagielski be and hereby is appointed to the office
+of Vice President, Apache Incubator, to serve in accordance with and
+subject to the direction of the Board of Directors and the Bylaws of
+the Foundation until death, resignation, retirement, removal or
+disqualification, or until a successor is appointed; and be it
+further RESOLVED, that the initial Apache Incubator PMC be and hereby
+is tasked with the creation of a set of bylaws intended to encourage
+open development and increased participation in the Apache Incubator
+Project.
+</pre>
+    </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