incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From nicola...@apache.org
Subject svn commit: r111799 - incubator/public/branches/move2html4forrest/site-author
Date Tue, 14 Dec 2004 09:48:24 GMT
Author: nicolaken
Date: Tue Dec 14 01:48:20 2004
New Revision: 111799

URL: http://svn.apache.org/viewcvs?view=rev&rev=111799
Log:
Top level dir, except FAQ that uses a specific FAQ DTD, has all html source files.
Added:
   incubator/public/branches/move2html4forrest/site-author/howtoparticipate.html
      - copied, changed from r111794, incubator/public/branches/move2html4forrest/site-author/howtoparticipate.xml
   incubator/public/branches/move2html4forrest/site-author/howwework.html
      - copied, changed from r111794, incubator/public/branches/move2html4forrest/site-author/howwework.cwiki
   incubator/public/branches/move2html4forrest/site-author/whoweare.html
      - copied, changed from r111794, incubator/public/branches/move2html4forrest/site-author/whoweare.cwiki
Removed:
   incubator/public/branches/move2html4forrest/site-author/howtoparticipate.xml
   incubator/public/branches/move2html4forrest/site-author/howwework.cwiki
   incubator/public/branches/move2html4forrest/site-author/whoweare.cwiki

Copied: incubator/public/branches/move2html4forrest/site-author/howtoparticipate.html (from
r111794, incubator/public/branches/move2html4forrest/site-author/howtoparticipate.xml)
Url: http://svn.apache.org/viewcvs/incubator/public/branches/move2html4forrest/site-author/howtoparticipate.html?view=diff&rev=111799&p1=incubator/public/branches/move2html4forrest/site-author/howtoparticipate.xml&r1=111794&p2=incubator/public/branches/move2html4forrest/site-author/howtoparticipate.html&r2=111799
==============================================================================
--- incubator/public/branches/move2html4forrest/site-author/howtoparticipate.xml	(original)
+++ incubator/public/branches/move2html4forrest/site-author/howtoparticipate.html	Tue Dec
14 01:48:20 2004
@@ -1,143 +1,144 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN" "document-v11.dtd">
-<document>
-   <header>
-      <title>How to Participate</title>
-   </header>
-
-   <body>
-      <section>
-         <title>Check this first</title>
-         <p>Before doing anything, we encourage you to read the incubator website and
in particular
+<!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>How to Participate</title>
+<link href="http://purl.org/DC/elements/1.0/" rel="schema.DC">
+</head>
+<body>
+      
+<h1>Check this first</h1>
+         
+         
+<p>Before doing anything, we encourage you to read the incubator website and in particular
             our "About" documents.</p>
-            <p>If you have other questions, feel free to post them on general@incubator.apache.org</p>

-          <p>If you want to help in the development of a specific <link href="site:projects">Incubated
Project</link>
+            
+<p>If you have other questions, feel free to post them on general@incubator.apache.org</p>

+          
+<p>If you want to help in the development of a specific <a href="site:projects">Incubated
Project</a>
             refer to its development mailing list. The Incubator mailing lists are for project
             incubation, not for project development.</p>
-            <p>In case of generic Project development questions, there is projects@incubator.apache.org</p>
-      </section>         
-      <section>
-         <title>Incubator Project resources</title>
-         <fixme author="nicolaken">Check that all Incubator project resources are listed.</fixme>
-         <section>
-           <title>Mailing lists</title>
-           <p>As with everything else in Apache, most of what goes on happens or is
discussed 
+            
+<p>In case of generic Project development questions, there is projects@incubator.apache.org</p>
+               
+      
+<h1>Incubator Project resources</h1>
+         
+         
+<div class="fixme">nicolaken:
+      Check that all Incubator project resources are listed.</div>
+         
+<h2>Mailing lists</h2>
+<p>As with everything else in Apache, most of what goes on happens or is discussed

               on electronic mailing lists. Here are the lists associated with this project,

               and their purposes.</p>
-
-           <section>
-             <title>general@incubator.apache.org</title>
-             <p>This is where general and public discussion of things about the project

+<h3>general@incubator.apache.org</h3>
+<p>This is where general and public discussion of things about the project 
                 take place. It's also where follow-up messages sent in reply to cvs commit

                 reports get sent (see the next list). There is a 'digest' form of this list,

                 which collects individual messages and sends the collection when enough have

                 accumulated or a given amount of time has passed since the last digest. 
                 Anyone may subscribe; only subscribers may post.</p>
-
-              <ul>
-                <li>To subscribe, send a message to general-subscribe@incubator.apache.org</li>
-                <li>To subscribe to the digest, send a message to general-digest-subscribe@incubator.apache.org</li>
-                <li>To unsubscribe, send a message to general-unsubscribe@incubator.apache.org</li>
-             </ul>
-           </section>
-  
-	      <section>
-	         <title>projects@incubator.apache.org</title>
-	         <p>This is the development mailing list for some of the projects in incubation.

+<ul>
+                
+<li>To subscribe, send a message to general-subscribe@incubator.apache.org</li>
+                
+<li>To subscribe to the digest, send a message to general-digest-subscribe@incubator.apache.org</li>
+                
+<li>To unsubscribe, send a message to general-unsubscribe@incubator.apache.org</li>
+             
+</ul>
+<h3>projects@incubator.apache.org</h3>
+<p>This is the development mailing list for some of the projects in incubation. 
 	            Anyone may subscribe; only subscribers may post.</p>
-	         <ul>
-	            <li>To subscribe, send a message to projects-subscribe@incubator.apache.org</li>
-	            <li>To unsubscribe, send a message to projects-unsubscribe@incubator.apache.org</li>
-	         </ul>
-	      </section>
-
-	      <section>
-	         <title>cvs@incubator.apache.org</title>
-	         <p>When changes are made to the code repository, the details are automatically
sent to this list. Its Reply-To is set to the 'general' list, so if you reply to a cvs message
that's where your reply is going to end up. Anyone may subscribe; only subscribers may post.</p>
-	         <ul>
-	            <li>To subscribe, send a message to cvs-subscribe@incubator.apache.org</li>
-	            <li>To unsubscribe, send a message to cvs-unsubscribe@incubator.apache.org</li>
-	         </ul>
-	      </section>
-	
-	      <section>
-	         <title>announce@incubator.apache.org</title>
-	         <p>This is the list to which you should be subscribed if you want to be kept

+<ul>
+	            
+<li>To subscribe, send a message to projects-subscribe@incubator.apache.org</li>
+	            
+<li>To unsubscribe, send a message to projects-unsubscribe@incubator.apache.org</li>
+	         
+</ul>
+<h3>cvs@incubator.apache.org</h3>
+<p>When changes are made to the code repository, the details are automatically sent
to this list. Its Reply-To is set to the 'general' list, so if you reply to a cvs message
that's where your reply is going to end up. Anyone may subscribe; only subscribers may post.</p>
+<ul>
+	            
+<li>To subscribe, send a message to cvs-subscribe@incubator.apache.org</li>
+	            
+<li>To unsubscribe, send a message to cvs-unsubscribe@incubator.apache.org</li>
+	         
+</ul>
+<h3>announce@incubator.apache.org</h3>
+<p>This is the list to which you should be subscribed if you want to be kept 
 	            apprised of significant events or milestones in the project's activities, but

 	            don't want to track the full traffic in the 'general' list. Anyone may subscribe;

 	            all posts are moderated.</p>
-	         <ul>
-	            <li>To subscribe, send a message to announce-subscribe@incubator.apache.org</li>
-	            <li>To unsubscribe, send a message to announce-unsubscribe@incubator.apache.org</li>
-	         </ul>
-	      </section>
-
-	      <section>
-	         <title>pmc@incubator.apache.org</title>
-	         <ul>
-	            <li>This is a private list for the project management committee. It is
not open to general subscription.</li>
-	         </ul>
-	      </section>
-        </section>
-
-        <section id="website">
-          <title>Updating the site</title>
-          <p>This section describes how to maintain the top-level Incubator
+<ul>
+	            
+<li>To subscribe, send a message to announce-subscribe@incubator.apache.org</li>
+	            
+<li>To unsubscribe, send a message to announce-unsubscribe@incubator.apache.org</li>
+	         
+</ul>
+<h3>pmc@incubator.apache.org</h3>
+<ul>
+	            
+<li>This is a private list for the project management committee. It is not open to
general subscription.</li>
+	         
+</ul>
+
+        
+<h2>Updating the site</h2>
+<p>This section describes how to maintain the top-level Incubator
             website (including the project status reports).
             For actual project websites see the
-            <link href="#project-website">Project Website Howto</link> below.
+            <a href="#project-website">Project Website Howto</a> below.
             However, this section is still relevant for projects.
           </p>
-
-	        <section id="website-overview">
-	          <title>Overview</title>
-            <p>The top-level Incubator website is currently generated by
-              <link href="ext:apache/projects/forrest">Apache Forrest</link>.
+<h3>Overview</h3>
+<p>The top-level Incubator website is currently generated by
+              <a href="ext:apache/projects/forrest">Apache Forrest</a>.
             </p>
-            <p>The source documents are kept in the "incubator" SVN repository
+<p>The source documents are kept in the "incubator" SVN repository
             at "site-author".
-            Most documents are in site-author/*.xml format.
-            The status reports for each project are in site-author/project/*.cwiki
-            (this is the simple JSPWiki format).
+            Most documents are in site-author/*.html format.
+            The status reports for each project are in site-author/project/*.html.
             </p>
-            <p>
+<p>
             The production documents are kept in the "incubator" SVN repository
             at "site-publish".
             That directory is then checked-out on the server to re-create the website.
             </p>
-	        </section>
-
-	        <section id="website-edit">
-	          <title>Edit the content</title>
-            <p>People with commit access to the "incubator" SVN can edit the
+<h3>Edit the content</h3>
+<p>People with commit access to the "incubator" SVN can edit the
             source documents in the "site-author/" directory. Anyone else can send
             patches to those documents.</p>
-            <p>When editing the xml source, please ensure xml validation.
+            <p>It's <b>strongly</b> suggested to use plain HTML for the
source files. 
+               Forrest understands them even if malformed, and generates the site
+               in any case. Use any HTML editor that you prefer, as long as it 
+               doesn't mess up too much with the source tags.</p>
+<p>When editing the xml source, please ensure xml validation.
             When editing the simple JSPWiki source, please take care to use
             the correct syntax.
 	          Here are examples of the document structures:
-	          <link href="http://forrest.apache.org/docs/document-v12.html">xml format</link>
+	          <a href="http://forrest.apache.org/docs/document-v12.html">xml format</a>
 	          and 
-	          <link href="http://forrest.apache.org/docs/wiki-sample.html">JSPWiki format</link>.</p>
-            <p>You can just commit the source changes and leave it to someone
+	          <a href="http://forrest.apache.org/docs/wiki-sample.html">JSPWiki format</a>.</p>
+<p>You can just commit the source changes and leave it to someone
             else to generate the website.
             </p>
-	        </section>
-
-	        <section id="website-generate">
-	          <title>Generate the production documents</title>
-            <p>Either install Apache Forrest locally so that you can edit and
+<h3>Generate the production documents</h3>
+<p>Either install Apache Forrest locally so that you can edit and
             review documents immediately, or use the production system on
             the server to generate and copy to a staging site to view them.
             In the future there will be automated generation and staging systems.
             </p>
-            <p>Lets explain the server-side method first, then go on to explain
+<p>Lets explain the server-side method first, then go on to explain
              how to set up a local Forrest system.
             </p>
-            <p>People with access to the server can use an installation of
+<p>People with access to the server can use an installation of
               Forrest on minotaur ...
             </p>
-<source><![CDATA[ssh www.apache.org
+<pre class="code">ssh www.apache.org
 cd ~crossley/incubator-site
 bash
 bin/stage incubator
@@ -147,7 +148,7 @@
 ... This will copy the production to your committer webspace for viewing.
 
 diff -rq staging/incubator.apache.org modules/incubator/site-publish \
- | grep -v "\.svn" > diff
+ | grep -v "\.svn" &gt; diff
 vi diff
 ... Ensure that the differences are what you expect.
 
@@ -156,61 +157,56 @@
 
 cd /www/incubator.apache.org
 svn update
-]]></source>
-	        </section>
-
-	        <section id="forrest">
-	          <title>Using a local Forrest installation</title>
-            <p>
+</pre>
+<h3>Using a local Forrest installation</h3>
+<p>
               Install the current release of
-              <link href="ext:apache/projects/forrest">Apache Forrest</link>
+              <a class="external" href="ext:apache/projects/forrest">Apache Forrest</a>
               (v0.6 release or SVN branch "forrest_06_branch")
               by following the instructions at the index.html in the
               distribution, to set the environment variables
               $FORREST_HOME and $PATH.
             </p>
-            <p>
+<p>
               Checkout the incubator SVN repository. The site source files are kept
               in the "incubator" SVN at "site-author/". The final website contents are
               kept in the "incubator" SVN at "site-publish/".
             </p>
-           
-	         <p>Edit the docs in the <code>site-author</code> directory.</p>
-	
-	         <p>Here are examples of the document structures:
-	         <link href="http://forrest.apache.org/docs/document-v12.html">xml format</link>
+<p>Edit the docs in the <span class="codefrag">site-author</span> directory.</p>
+<p>Here are examples of the document structures:
+	         <a href="http://forrest.apache.org/docs/document-v12.html">xml format</a>
 	         and 
-	         <link href="http://forrest.apache.org/docs/wiki-sample.html">JSPWiki format</link>.</p>
-	
-	         <p>If you add a new page or change a page's name, update 
+	         <a href="http://forrest.apache.org/docs/wiki-sample.html">JSPWiki format</a>.</p>
+<p>If you add a new page or change a page's name, update 
 	         <code>site-author/site.xml</code> from which the menu is generated.
            More details can be found in the 
-	         <link href="http://forrest.apache.org/docs/">Forrest documentation</link>.</p>
-
-	         <p>Here is a quick tour:</p>
-	         <ul>
-	 	       <li>cd into the local "incubator" SVN directory.</li>
- 	         <li>Do 'forrest run'.</li>
- 	         <li>Browser http://localhost:8888/ to review the site.</li>
- 	         <li>Edit the docs <strong>in place</strong> at <code>site-author/*.*</code>
+	         <a href="http://forrest.apache.org/docs/">Forrest documentation</a>.</p>
+<p>Here is a quick tour:</p>
+<ul>
+	 	       
+<li>cd into the local "incubator" SVN directory.</li>
+ 	         
+<li>Do 'forrest run'.</li>
+ 	         
+<li>Browser http://localhost:8888/ to review the site.</li>
+ 	         
+<li>Edit the docs <strong>in place</strong> at <span class="codefrag">site-author/*.*</span>
            and see changes in the browser by re-loading the page.</li>
- 	         </ul>
-
-           <p>When you are satisifed, you will rebuild the whole site and
+ 	         
+</ul>
+<p>When you are satisifed, you will rebuild the whole site and
            add the changed documents to the "site-publish" directory ...
            </p>
-
-	         <p>In the top-level "<code>incubator</code>" SVN directory,
+<p>In the top-level "<span class="codefrag">incubator</span>" SVN directory,
            do 'forrest' to
-           render the HTML and PDF files into "<code>build/site</code>".
+           render the HTML and PDF files into "<span class="codefrag">build/site</span>".
            Forrest validates the XML, so will catch any syntax errors.
 	         You can also simply validate the source xdocs without rendering
            by doing 'forrest validate'.</p>
-
-	         <p>If the site built without errors, you now need to synch the
-           <code>incubator/build/site</code> directory with the
-           <code>incubator/site-publish</code> directory.</p>
-           <source>
+<p>If the site built without errors, you now need to synch the
+           <span class="codefrag">incubator/build/site</span> directory with
the
+           <span class="codefrag">incubator/site-publish</span> directory.</p>
+<pre class="code">
 cd incubator
 svn update
 diff -rq build/site site-publish | grep -v "\.svn"
@@ -218,54 +214,52 @@
 
 cp -Rf build/site/* site-publish
 ... Now do the usual SVN stuff: 'svn status' 'svn add' 'svn diff' 'svn commit'
-           </source>
-
-	         <p>If you are not an Incubator committer, then you can now make a
+           </pre>
+<p>If you are not an Incubator committer, then you can now make a
            patch with the command 
-	         '<code>svn diff &gt; incubator-site.diff</code>' in the
-           "<code>incubator/site-author/</code>" directory, and submit it to
the
-           mailing list, starting with '<code>[PATCH]</code>' in the email
+	         '<span class="codefrag">svn diff &gt; incubator-site.diff</span>'
in the
+           "<span class="codefrag">incubator/site-author/</span>" directory,
and submit it to the
+           mailing list, starting with '<span class="codefrag">[PATCH]</span>'
in the email
            subject.</p>
-	
-	         <p>To update the website, the "incubator/site-publish"
+<p>To update the website, the "incubator/site-publish"
              SVN directory is checked-out on the server.
            </p>
-           <source>
+<pre class="code">
 ssh www.apache.org
 cd /www/incubator.apache.org
 svn update
-           </source>
-	      </section>
-        </section>
-      </section>
+           </pre>
+      
 
-      <section id="project">
-         <title>Project-specific resources</title>
-         <p>Some <link href="site:projects">projects</link> under incubation
have their own mailing lists, 
+      
+<h1>Project-specific resources</h1>
+         
+         
+<p>Some <a href="site:projects">projects</a> under incubation have their
own mailing lists, 
          or their development discussion occurs on the mailing list of another project. Check
out 
          the project websites to be sure what mailing list is the right one.</p>
-         <section id="project-website">
-           <title>Project Website Howto</title>
-           <p>Each project can use whatever documentation system that it
+         
+<h2>Project Website Howto</h2>
+<p>Each project can use whatever documentation system that it
              chooses. Perhaps use a fancy documentation management
              system like Forrest or Maven, or just use simple raw html pages.
            </p>
-           <p>
+<p>
              Keep your source documents in your project CVS. To publish
              your site, simply "cvs commit" your final generated documents
              to your project "site" module.
            </p>
-           <p>
+<p>
              To update the website, the project "site" CVS module is
              checked-out on the server. PMC members can do this step manually,
              or perhaps automate it with cron.
            </p>
-           <source>
+<pre class="code">
 ssh www.apache.org
 cd /www/incubator.apache.org/${project-name}
 cvs update -Pd
-           </source>
-         </section>
-      </section>
-   </body>
-</document>
+           </pre>
+      
+   
+</body>
+</html>

Deleted: /incubator/public/branches/move2html4forrest/site-author/howtoparticipate.xml
Url: http://svn.apache.org/viewcvs/incubator/public/branches/move2html4forrest/site-author/howtoparticipate.xml?view=auto&rev=111798
==============================================================================

Deleted: /incubator/public/branches/move2html4forrest/site-author/howwework.cwiki
Url: http://svn.apache.org/viewcvs/incubator/public/branches/move2html4forrest/site-author/howwework.cwiki?view=auto&rev=111798
==============================================================================

Copied: incubator/public/branches/move2html4forrest/site-author/howwework.html (from r111794,
incubator/public/branches/move2html4forrest/site-author/howwework.cwiki)
Url: http://svn.apache.org/viewcvs/incubator/public/branches/move2html4forrest/site-author/howwework.html?view=diff&rev=111799&p1=incubator/public/branches/move2html4forrest/site-author/howwework.cwiki&r1=111794&p2=incubator/public/branches/move2html4forrest/site-author/howwework.html&r2=111799
==============================================================================
--- incubator/public/branches/move2html4forrest/site-author/howwework.cwiki	(original)
+++ incubator/public/branches/move2html4forrest/site-author/howwework.html	Tue Dec 14 01:48:20
2004
@@ -1,20 +1,17 @@
-!!!How we work
-
-Here are some notes about how we have decided to make decisions and
-changes to the way we work.
-
-!!How we make decision on our incubation policies
-
-Apache projects usually make releases, and have deliverables. The code 
-they put in is managed through lazy consensus and voting only when it's 
-deemed to be required or requested.
-
-Incubator releases are basically Incubated Projects' release to the 
-Sponsor PMC. So how incubation is done is our "code".
-
-Hence there is no need to "ratify" such rules if there seems to be
-consensus, as it's much easier to manage.
-
-Because of this, we do not have the "draft" status on our policy docs 
-and simply use them as our guide, that will change in need without 
-having to go through tedious votes when there is good consensus.
\ No newline at end of file
+<!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>How we work</title>
+<link href="http://purl.org/DC/elements/1.0/" rel="schema.DC">
+</head>
+<body>
+<h1>How we work</h1>
+<p>Here are some notes about how we have decided to make decisions and changes to the
way we work. </p>
+<h2>How we make decision on our incubation policies</h2>
+<p>Apache projects usually make releases, and have deliverables. The code  they put
in is managed through lazy consensus and voting only when it's  deemed to be required or requested.
</p>
+<p>Incubator releases are basically Incubated Projects' release to the  Sponsor PMC.
So how incubation is done is our "code". </p>
+<p>Hence there is no need to "ratify" such rules if there seems to be consensus, as
it's much easier to manage. </p>
+<p>Because of this, we do not have the "draft" status on our policy docs  and simply
use them as our guide, that will change in need without  having to go through tedious votes
when there is good consensus. </p>
+</body>
+</html>

Deleted: /incubator/public/branches/move2html4forrest/site-author/whoweare.cwiki
Url: http://svn.apache.org/viewcvs/incubator/public/branches/move2html4forrest/site-author/whoweare.cwiki?view=auto&rev=111798
==============================================================================

Copied: incubator/public/branches/move2html4forrest/site-author/whoweare.html (from r111794,
incubator/public/branches/move2html4forrest/site-author/whoweare.cwiki)
Url: http://svn.apache.org/viewcvs/incubator/public/branches/move2html4forrest/site-author/whoweare.html?view=diff&rev=111799&p1=incubator/public/branches/move2html4forrest/site-author/whoweare.cwiki&r1=111794&p2=incubator/public/branches/move2html4forrest/site-author/whoweare.html&r2=111799
==============================================================================
--- incubator/public/branches/move2html4forrest/site-author/whoweare.cwiki	(original)
+++ incubator/public/branches/move2html4forrest/site-author/whoweare.html	Tue Dec 14 01:48:20
2004
@@ -1,75 +1,80 @@
-!!!Incubator Project members
-
-Every Apache Project operates on a meritocracy: the more you do, the more 
-responsibility you will obtain. This page lists all of the people who have 
-gone the extra mile and are Committers. If you would like to get involved, 
-the first step is to join the mailing lists. 
-
-We ask that you please do not send us emails privately asking for support. 
-We are non-paid volunteers who help out with the project and we do not 
-necessarily have the time or energy to help people on an individual basis. 
-Instead, we have setup mailing lists which often contain hundreds of 
-individuals who will help answer detailed requests for help. The benefit of 
-using mailing lists over private communication is that it is a shared 
-resource where others can also learn from common mistakes and as a 
-community we all grow together.
-
-!!PMC (Project Management Commitee)
-
-This list contains all currently active PMC members in alphabetical 
-order.
-{{{
-    Aaron Bannert <aaron@apache.org>
-    Noel Bergman <noel@apache.org>
-    Nicola Ken Barozzi <nicolaken@apache.org>
-    Ken Coar <coar@apache.org>
-    Morgan Delegrange <morgand@apache.org>
-    Roy T. Fielding <fielding@apache.org>
-    Ceki Gulcu <ceki@apache.org>
-    Paul Hammant <hammant@apache.org>
-    Jim Jagielski <jim@apache.org>
-    Berin Lautenbach <blautenb@apache.org>
-    Ted Leung <twl@apache.org>
-    Geir Magnusson Jr. <geirm@apache.org>
-    Stefano Mazzocchi <stefano@apache.org>
-    Steven Noels <stevenn@apache.org>
-    Sam Ruby <rubys@apache.org>
-    Cliff Schmidt <cliffs@apache.org>
-    Leo Simons <leosimons@apache.org>
-    Greg Stein <gstein@lyra.org>
-    Davanum Srinivas <dims@apache.org>
-    James Strachan <jstrachan@apache.org>
-    Sander Striker <striker@apache.org>
-}}}
-!! Committers 
-
-This list defines all current incubator project committers.
-
-* all PMC members 
-
-''PMC members also have commit access on every incubated project; unless they are listed
on the project status page, it does not mean that they are part of that project but must nevertheless
retain commit access for oversight purposes.''
-
-* all incubating project members 
-
-''The incubating project committers are listed on each incubating projects' status page.''
-
-!!Inactive
-
-This list contains all inactive committers in strict alphabetical order.
-They do not consider themselves active currently, but are still 
-somewhat involved in this project and hope to return active again soon.
-
-{{{
+<!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>Who we are</title>
+<link href="http://purl.org/DC/elements/1.0/" rel="schema.DC">
+</head>
+<body>
+<h1>Incubator Project members</h1>
+<p>Every Apache Project operates on a meritocracy: the more you do, 
+  the more  responsibility you will obtain. This page lists all of 
+  the people who have  gone the extra mile and are Committers. 
+  If you would like to get involved,  the first step is to join the 
+  mailing lists.  </p>
+<p>We ask that you please do not send us emails privately asking for 
+support.  We are non-paid volunteers who help out with the project
+and we do not  necessarily have the time or energy to help people 
+on an individual basis.  Instead, we have setup mailing lists which 
+often contain hundreds of  individuals who will help answer detailed 
+requests for help. The benefit of  using mailing lists over private 
+communication is that it is a shared  resource where others can also 
+learn from common mistakes and as a  community we all grow together. </p>
+<h2>PMC (Project Management Commitee)</h2>
+<p>This list contains all currently active PMC members in alphabetical  
+  order. </p>
+<pre class="code">
+    Aaron Bannert &lt;aaron@apache.org&gt;
+    Noel Bergman &lt;noel@apache.org&gt;
+    Nicola Ken Barozzi &lt;nicolaken@apache.org&gt;
+    Ken Coar &lt;coar@apache.org&gt;
+    Morgan Delegrange &lt;morgand@apache.org&gt;
+    Roy T. Fielding &lt;fielding@apache.org&gt;
+    Ceki Gulcu &lt;ceki@apache.org&gt;
+    Paul Hammant &lt;hammant@apache.org&gt;
+    Jim Jagielski &lt;jim@apache.org&gt;
+    Berin Lautenbach &lt;blautenb@apache.org&gt;
+    Ted Leung &lt;twl@apache.org&gt;
+    Geir Magnusson Jr. &lt;geirm@apache.org&gt;
+    Stefano Mazzocchi &lt;stefano@apache.org&gt;
+    Steven Noels &lt;stevenn@apache.org&gt;
+    Sam Ruby &lt;rubys@apache.org&gt;
+    Cliff Schmidt &lt;cliffs@apache.org&gt;
+    Leo Simons &lt;leosimons@apache.org&gt;
+    Greg Stein &lt;gstein@lyra.org&gt;
+    Davanum Srinivas &lt;dims@apache.org&gt;
+    James Strachan &lt;jstrachan@apache.org&gt;
+    Sander Striker &lt;striker@apache.org&gt;
+</pre>
+<h2>Committers </h2>
+<p>This list defines all current incubator project committers. </p>
+<ul>
+<li>all PMC members  <ul>
+<li>
+<em>PMC members also have commit access on every incubated project; 
+    unless they are listed on the project status page, it does not 
+    mean that they are part of that project but must nevertheless 
+    retain commit access for oversight purposes</em> </li>
+    </ul></li>
+    </ul>
+<ul>
+<li>all incubating project members  
+ <ul>
+<li><em>The incubating project committers are listed on each 
+      incubating projects' status page</em></ul></li></li>
+</ul>
+
+<h2>Inactive</h2>
+<p>This list contains all inactive committers in strict alphabetical order. They do
not consider themselves active currently, but are still  somewhat involved in this project
and hope to return active again soon. </p>
+<pre class="code">
     nobody considers himself inactive
-}}}
-
-!!Emeritus
-
-This list contains all emeritus committers in strict alphabetical order.
-hey have not committed anything for some time, and consider themselves 
-retired from active duty. 
-We wish them well and hope to see them return.
-
-{{{
-    Brian W. Fitzpatrick <fitz@red-bean.com>
-}}}
\ No newline at end of file
+</pre>
+<h2>Emeritus</h2>
+<p>This list contains all emeritus committers in strict alphabetical order. 
+   They have not committed anything for some time, and consider themselves  
+   retired from active duty.  We wish them well and hope to see them return. </p>
+<pre class="code">
+    Brian W. Fitzpatrick &lt;fitz@red-bean.com&gt;
+</pre>
+</body>
+</html>

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


Mime
View raw message