cocoon-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From upayav...@apache.org
Subject svn commit: r164967 [1/3] - in /cocoon/whiteboard/doc-repos/global/src/content/xdocs: ./ OLD-achives/ OLD-committer/ OLD-committers/ OLD-contrib/ OLD-devinfo-merge-to-committer/ OLD-fr-mail-lists/ OLD-francais/ OLD-history/ OLD-hosting/ OLD-incubation/ OLD-index/ OLD-links/ OLD-livesites-1.x/ OLD-livesites-2.0/ OLD-livesites-2.1/ OLD-mail-archives/ OLD-mail-lists/ OLD-news/ OLD-pmc/ OLD-releasing/ OLD-versioning/
Date Wed, 27 Apr 2005 10:07:12 GMT
Author: upayavira
Date: Wed Apr 27 03:07:09 2005
New Revision: 164967

URL: http://svn.apache.org/viewcvs?rev=164967&view=rev
Log:
Adding old 'site', for copying across into new place, just like c21- 
files 
in 2.2 documentation.


Added:
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-achives/
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-achives/comments_en.xml
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-achives/content_en.html
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-achives/meta.xml
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-committer/
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-committer/comments_en.xml
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-committer/content_en.html
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-committer/meta.xml
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-committers/
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-committers/comments_en.xml
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-committers/content_en.html
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-committers/meta.xml
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-contrib/
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-contrib/comments_en.xml
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-contrib/content_en.html
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-contrib/meta.xml
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-devinfo-merge-to-committer/
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-devinfo-merge-to-committer/comments_en.xml
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-devinfo-merge-to-committer/content_en.html
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-devinfo-merge-to-committer/meta.xml
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-fr-mail-lists/
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-fr-mail-lists/comments_en.xml
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-fr-mail-lists/content_en.html
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-fr-mail-lists/meta.xml
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-francais/
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-francais/comments_en.xml
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-francais/content_en.html
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-francais/meta.xml
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-history/
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-history/comments_en.xml
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-history/content_en.html
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-history/meta.xml
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-hosting/
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-hosting/comments_en.xml
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-hosting/content_en.html
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-hosting/meta.xml
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-incubation/
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-incubation/comments_en.xml
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-incubation/content_en.html
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-incubation/meta.xml
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-index/
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-index/comments_en.xml
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-index/content_en.html
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-index/meta.xml
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-links/
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-links/comments_en.xml
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-links/content_en.html
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-links/meta.xml
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-livesites-1.x/
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-livesites-1.x/comments_en.xml
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-livesites-1.x/content_en.html
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-livesites-1.x/meta.xml
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-livesites-2.0/
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-livesites-2.0/comments_en.xml
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-livesites-2.0/content_en.html
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-livesites-2.0/meta.xml
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-livesites-2.1/
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-livesites-2.1/comments_en.xml
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-livesites-2.1/content_en.html
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-livesites-2.1/meta.xml
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-mail-archives/
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-mail-archives/comments_en.xml
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-mail-archives/content_en.html
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-mail-archives/meta.xml
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-mail-lists/
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-mail-lists/comments_en.xml
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-mail-lists/content_en.html
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-mail-lists/meta.xml
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-news/
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-news/comments_en.xml
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-news/content_en.html
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-news/meta.xml
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-pmc/
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-pmc/comments_en.xml
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-pmc/content_en.html
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-pmc/meta.xml
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-releasing/
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-releasing/comments_en.xml
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-releasing/content_en.html
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-releasing/meta.xml
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-versioning/
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-versioning/comments_en.xml
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-versioning/content_en.html
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-versioning/meta.xml
Modified:
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/site.xml
    cocoon/whiteboard/doc-repos/global/src/content/xdocs/tabs.xml

Added: cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-achives/comments_en.xml
URL: http://svn.apache.org/viewcvs/cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-achives/comments_en.xml?rev=164967&view=auto
==============================================================================
--- cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-achives/comments_en.xml (added)
+++ cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-achives/comments_en.xml Wed Apr 27 03:07:09 2005
@@ -0,0 +1,3 @@
+<?xml version="1.0"?>
+<comments>
+</comments>

Added: cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-achives/content_en.html
URL: http://svn.apache.org/viewcvs/cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-achives/content_en.html?rev=164967&view=auto
==============================================================================
--- cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-achives/content_en.html (added)
+++ cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-achives/content_en.html Wed Apr 27 03:07:09 2005
@@ -0,0 +1,165 @@
+<!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>Older News</title>
+<link href="http://purl.org/DC/elements/1.0/" rel="schema.DC">
+</head>
+<body>
+    
+<h1>Released Cocoon 2.1.3 (13 November 2003)</h1>
+      
+      
+<p>Released Cocoon 2.1.3</p>
+    
+    
+<h1>ApacheCon US 2003 (16-19 November 2003)</h1>
+      
+      
+<p>
+        The <a class="external" href="http://apachecon.com/2003/US/index.html">ApacheCon US 2003</a>
+        has taken place from November 16-19 in Las Vegas, Nevada.
+      </p>
+    
+    
+<h1>Cocoon GetTogether (7 October 2003)</h1>
+      
+      
+<p>
+        The 2003 Cocoon GetTogether has taken place October, 7th, in Ghent
+        (Belgium). More information is available on the event's website at
+        <a class="external" href="http://www.orixo.com/events/gt2003/">http://www.orixo.com/events/gt2003/</a>.
+      </p>
+    
+    
+<h1>Released Cocoon 2.1.2 (2 October 2003)</h1>
+      
+      
+<p>Released Cocoon 2.1.3</p>
+    
+    
+<h1>September 2003</h1>
+      
+      
+<p>Released Cocoon 2.1.1 on September, 5th.</p>
+    
+    
+<h1>August 2003</h1>
+      
+      
+<p>
+        The release of the long-awaited 2.1 version of Cocoon on August 13th
+        marks the transition from a publishing-oriented XML/XSLT server engine
+        towards a componentized XML-based web application development framework.
+      </p>
+    
+    
+<h1>July 2003</h1>
+      
+      
+<ul>
+        
+<li>Released Cocoon 2.1 Release Candidate 1 on July, 29th.</li>
+        
+<li>Released Cocoon 2.1 Milestone 3 on July, 4th.</li>
+        
+<li>Changed mailing list names to reflect top level status.</li>
+        
+<li>
+          The developer list has been renamed from
+          <em>cocoon-dev.at.xml.apache.org</em> to <em>dev.at.cocoon.apache.org</em>.
+        </li>
+        
+<li>
+          The users list has been renamed from <em>cocoon-users.at.xml.apache.org</em>
+          to <em>users.at.cocoon.apache.org</em>.
+        </li>
+        
+<li>
+          The doc list has been renamed from <em>cocoon-docs.at.xml.apache.org</em>
+          to <em>docs.at.cocoon.apache.org</em>.
+        </li>
+      
+</ul>
+    
+    
+<h1>June 2003</h1>
+      
+
+      
+<ul>
+        
+<li>New Cocoon website to celebrate start of 2.1 Milestone releases.</li>
+      
+</ul>
+    
+
+    
+<h1>Release Early, Release Often</h1>
+      
+
+      
+<p>We are back on track: with the Milestone 2 Release of 2.1 we follow
+      again the good and old "release early, release often" theme.</p>
+    
+
+    
+<h1>Milestone Release</h1>
+      
+
+      
+<p>We are proud to announce the release of Cocoon 2.1 Milestone 1. As
+      the core and most parts can be regarded as beta, but some other parts
+      only as alpha we decided to title the release with 'milestone'
+      rather than 'beta' or 'alpha'.</p>
+    
+
+    
+<h1>Wiki Moving</h1>
+      
+
+      
+<p>The popular Cocoon Wiki was hosted by <a class="external" href="http://www.cocoondev.org/">http://www.cocoondev.org/</a>
+      
+</p>
+    
+    
+<h1>Cocoon GetTogether</h1>
+        
+        
+<p>Outerthought is organizing the <a class="external" href="http://outerthought.org/cocoon/gettogether/">Cocoon GetTogether</a> on 19 November 2002 (near Ghent in Belgium).</p>
+    
+    
+<h1>Cocoon: Building XML Applications Published</h1>
+      
+        
+<p>
+<strong>July 2002</strong> New Riders has just published <em>Cocoon: Building XML Applications</em> written by our very own Carsten Ziegeler, release coordinator for the Cocoon project, and Matthew Langham, leader of the open-source group at S&amp;N AG of Paderborn, Germany. You can download several <a class="external" href="http://www.newriders.com/books/product.asp?product_id={C3C05052-BE3B-4E06-A60A-13FB40AF58F6}">free chapters</a> at the New Riders web site. Weighing in at over 500 pages, the book is a vital new resource for the Cocoon community. We congratulate and thank Carsten, Matthew, and New Riders for their excellent work!
+        </p>
+    
+    
+<h1>Cocoon Wikis</h1>
+      
+      
+<p>
+          Cocoon has two promising and complementary wiki efforts underway. 
+      </p>
+      
+<ul>
+          
+<li>
+              
+<a class="external" href="http://wiki.apache.org/cocoon/">Cocoon Wiki</a> focuses on content development for the Cocoon project. It is designed to facilitate document development and collaboration from all levels of Cocoon users. Documents include FAQs, snippets, how-tos, tutorials, RTs (random thoughts), dreams, surveys, and more. The preliminary focus of this the wiki is to serve as a documentation "breeding ground," where docs can "grow" until mature enough to become official cvs docs. However, it already represents a lively and valid document resource in its own right.
+          </li>
+          
+<li>
+              
+<a class="external" href="http://www.anyware-tech.com/wikiland/">Wikiland</a> is an ongoing development effort to build a Cocoon-based wiki architecture. Wikiland features a Cocoon dictionary as the pretext to use, test and develop the wiki. The project is seeking Cocoon-oriented developers to further its development. For more information, see the <a class="external" href="http://rossel.free.fr/">Wikiland home page.</a>
+         
+</li>
+      
+</ul>
+    
+	
+</body>
+</html>

Added: cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-achives/meta.xml
URL: http://svn.apache.org/viewcvs/cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-achives/meta.xml?rev=164967&view=auto
==============================================================================
--- cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-achives/meta.xml (added)
+++ cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-achives/meta.xml Wed Apr 27 03:07:09 2005
@@ -0,0 +1,9 @@
+<?xml version="1.0"?>
+<meta>
+  <authors>
+    <author contact="http://cocoon.apache.org">Cocoon Community</author>
+  </authors>
+  <legacy>
+    <original-filename>news/archives.html</original-filename>
+  </legacy>
+</meta>

Added: cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-committer/comments_en.xml
URL: http://svn.apache.org/viewcvs/cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-committer/comments_en.xml?rev=164967&view=auto
==============================================================================
--- cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-committer/comments_en.xml (added)
+++ cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-committer/comments_en.xml Wed Apr 27 03:07:09 2005
@@ -0,0 +1,3 @@
+<?xml version="1.0"?>
+<comments>
+</comments>

Added: cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-committer/content_en.html
URL: http://svn.apache.org/viewcvs/cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-committer/content_en.html?rev=164967&view=auto
==============================================================================
--- cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-committer/content_en.html (added)
+++ cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-committer/content_en.html Wed Apr 27 03:07:09 2005
@@ -0,0 +1,185 @@
+<!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>Tips for committers</title>
+<link href="http://purl.org/DC/elements/1.0/" rel="schema.DC">
+</head>
+<body>
+    
+<h1>Overview</h1>
+      
+      
+<p>
+        These are some tips to help committers to keep our Subversion (SVN) repository clean.
+        See also
+        <a class="external" href="http://www.apache.org/dev/committers.html">Committers FAQ</a>
+        and
+        <a class="external" href="http://www.apache.org/dev/pmc.html">PMC FAQ</a>.
+      </p>
+    
+
+    
+<h1>Coding Style Guidelines</h1>
+      
+      
+<p>
+        We do not want to get too concerned about style, other than a few
+        obvious things such as whitespace. Basically just follow the style
+        that is already used by the files that you are working on.
+        We loosely follow the
+        <a class="external" href="http://java.sun.com/docs/codeconv/">Sun Java Style Guide</a>.
+      </p>
+    
+
+    
+<h1>Consistent whitespace</h1>
+      
+      
+<p>
+        Whitespace can cause big problems with SVN. If it is inconsistent,
+        then diffs are very hard to follow - actual changes become lost in
+        the noise of whitespace changes. Some developers use editors that
+        attempt to automatically format the whitespace. The trouble is
+        that if SVN files are inconsistent, some of those editors just
+        make it worse.
+      </p>
+      
+<p>
+        The solution comes in two parts:
+      </p>
+      
+<p>
+        When a committer adds a new file, they need to ensure that the file 
+        has the correct line endings for their own operating system, and that
+        either their SVN client automatically sets the EOL settings for the 
+        file based upon the file extension, or they must do:
+      </p>
+
+<pre class="code">svn add myfile.txt
+svn propset svn:eol-style native myfile.txt
+
+</pre>
+      
+<p>is that some committers who have a proper editor
+        should occasionally correct the whitespace across all SVN files,
+        applying the following rules.
+      </p>
+
+      
+<p>For all text files:</p>
+
+      
+<ul>
+        
+<li>Replace all tabs with spaces.</li>
+        
+<li>No trailing whitespace.</li>
+        
+<li>No MS-DOS line endings.</li>
+        
+<li>Newline at end-of-file.</li>
+        
+<li>Single whitespace between words.</li>
+      
+</ul>
+
+      
+<p>For all Java source files, as for text files plus:</p>
+
+      
+<ul>
+        
+<li>Use 4-space indentation.</li>
+      
+</ul>
+
+      
+<p>For all XML source files, as for text files plus:</p>
+
+      
+<ul>
+        
+<li>Use 2-space indentation.</li>
+        
+<li>No whitespace at start-of-file.</li>
+        
+<li>No whitespace at end-of-file (except of course a newline).</li>
+      
+</ul>
+    
+
+    
+<h1>dos2unix and other control-characters</h1>
+      
+      
+<p>
+        If you are on a UNIX system, when you receive a patch from a
+        contributor on Windows then do a 'dos2unix'. If you are on a
+        Windows system, then ensure that you have a proper SVN client
+        (it is supposed to convert to UNIX line-endings when you commit).
+      </p>
+
+      
+<p>
+        Here is one UNIX way to find all plain-text files that have DOS
+        line-endings (and maybe mixed line-endings).
+        There seem to be many images and jar archives that contain
+        carriage-returns, so to list only the plain-text files:
+      </p>
+
+      
+<pre class="code">
+find . -type f | xargs grep -l '^M' | xargs file | \
+grep -i -w text | cut -f1 -d:
+
+To add the ^M use "Ctrl-v Ctrl-m" at the command-line.
+Note that copy-and-paste will not work.
+The -w can be omitted, but might then match some extra filenames.
+</pre>
+
+      
+<p>
+        To instead find <em>all</em> files (including images and foreign
+        jar archives) that have DOS line-endings:
+        <span class="codefrag">find . -type f | xargs grep -l '^M'</span>
+      
+</p>
+
+      
+<p>
+        Here is one way to find files that have <em>any</em> hidden control
+        characters:
+        <span class="codefrag">find . -type f | xargs grep -l '[[:cntrl:]]'</span>
+      
+</p>
+    
+
+    
+<h1>Valid XML instances</h1>
+      
+      
+<p>
+        Many of us have wasted time with a broken build due to xml validation
+        errors. Would all committers please either use a proper xml editor or
+        validate their xdocs with one of the following commands:
+      </p>
+      
+<pre class="code">
+onsgmls -c $COCOON_HOME/src/webapp/WEB-INF/entities/catalog \
+-wall -wxml -s mydoc.xml
+      </pre>
+      
+<pre class="code">
+export SGML_CATALOG_FILES=$COCOON_HOME/src/webapp/WEB-INF/entities/catalog
+xmllint --valid --catalogs --noout mydoc.xml
+      </pre>
+      
+<pre class="code">
+forrest validate-xdocs
+      </pre>
+    
+
+  
+</body>
+</html>

Added: cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-committer/meta.xml
URL: http://svn.apache.org/viewcvs/cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-committer/meta.xml?rev=164967&view=auto
==============================================================================
--- cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-committer/meta.xml (added)
+++ cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-committer/meta.xml Wed Apr 27 03:07:09 2005
@@ -0,0 +1,9 @@
+<?xml version="1.0"?>
+<meta>
+  <authors>
+    <author contact="http://cocoon.apache.org">Cocoon Community</author>
+  </authors>
+  <legacy>
+    <original-filename>community/committer.html</original-filename>
+  </legacy>
+</meta>

Added: cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-committers/comments_en.xml
URL: http://svn.apache.org/viewcvs/cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-committers/comments_en.xml?rev=164967&view=auto
==============================================================================
--- cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-committers/comments_en.xml (added)
+++ cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-committers/comments_en.xml Wed Apr 27 03:07:09 2005
@@ -0,0 +1,3 @@
+<?xml version="1.0"?>
+<comments>
+</comments>

Added: cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-committers/content_en.html
URL: http://svn.apache.org/viewcvs/cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-committers/content_en.html?rev=164967&view=auto
==============================================================================
--- cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-committers/content_en.html (added)
+++ cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-committers/content_en.html Wed Apr 27 03:07:09 2005
@@ -0,0 +1,173 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
+<title>The Cocoon Community</title>
+<link href="http://purl.org/DC/elements/1.0/" rel="schema.DC">
+</head>
+<body>
+
+ 
+<h1>Who we are</h1>
+  
+  
+<p>
+    The Apache Cocoon 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>
+  
+  
+<h1>The Community</h1>
+  
+    
+<p>
+    This list contains all past and present committers on the various Cocoon projects
+    in strict alphabetical order. For details of contributors to a specific version of
+    Cocoon, see the relevant version pages 
+    (e.g. <a class="external" href="http://cocoon.apache.org/2.1/who.html">2.1</a>).
+    </p>
+    
+<ul>
+      
+<li>Zvi Avraham (zvia.at.apache.org)</li>
+      
+<li>Donald Ball (balld.at.apache.org)</li>
+      
+<li>Nicola Ken Barozzi (nicolaken.at.apache.org)</li>
+      
+<li>Brian Behlendorf (brian.at.apache.org)</li>
+      
+<li>Ross Burton (rossb.at.apache.org)</li>
+      
+<li>Mark Butler (butlermh.at.apache.org)</li>
+      
+<li>Guido Casper (gcasper.at.apache.org)</li>
+      
+<li>Ugo Cei (ugo.at.apache.org)</li>
+      
+<li>Steven Coffman (gears.at.apache.org)</li>
+      
+<li>Tony Collen (tony.at.apache.org)</li>
+      
+<li>Marcus Crafter (crafterm.at.apache.org)</li>
+      
+<li>David Crossley (crossley.at.apache.org)</li>
+      
+<li>Torsten Curdt (tcurdt.at.apache.org)</li>
+      
+<li>Bertrand Delacr&eacute;taz (bdelacretaz.at.apache.org)</li>
+      
+<li>Peter Donald (donaldp.at.apache.org)</li>
+      
+<li>Bruno Dumon (bruno.at.apache.org)</li>
+      
+<li>Daniel Fagerstr&ouml;m (danielf.at.apache.org)</li>
+      
+<li>Gerhard Froehlich (froehlich.at.apache.org)</li>
+      
+<li>Pier Fumagalli (pier.at.apache.org)</li>
+      
+<li>Antonio Gallardo (antonio.at.apache.org)</li>
+      
+<li>Leszek Gawron (lgawron.at.apache.org)</li>
+      
+<li>Ralph Goers (rgoers.at.apache.org)</li>
+      
+<li>Robin Green (greenrd.at.apache.org)</li>
+      
+<li>Vadim Gritsenko (vgritsenko.at.apache.org)</li>
+      
+<li>Christian Haul (haul.at.apache.org)</li>
+      
+<li>J&ouml;rg Heinicke (joerg.at.apache.org)</li>
+      
+<li>Unico Hommes (unico.at.apache.org)</li>
+      
+<li>Geoff Howard (ghoward.at.apache.org)</li>
+      
+<li>Bernhard Huber (huber.at.apache.org)</li>
+      
+<li>Ivelin Ivanov (ivelin.at.apache.org)</li>
+      
+<li>Matthew Langham (mlangham.at.apache.org)</li>
+      
+<li>Tim Larson (tim.at.apache.org)</li>
+      
+<li>Ben Laurie (ben.at.apache.org)</li>
+      
+<li>Berin Loritsch (bloritsch.at.apache.org)</li>
+      
+<li>Martin Man (mman.at.apache.org)</li>
+      
+<li>Stefano Mazzocchi (stefano.at.apache.org)</li>
+      
+<li>Brett McLaughlin (bmclaugh.at.apache.org)</li>
+      
+<li>Michael Melhem (michaelm.at.apache.org)</li>
+      
+<li>Stephan Michels (stephan.at.apache.org)</li>
+      
+<li>John Morrison (morrijr.at.apache.org)</li>
+      
+<li>Steven Noels (stevenn.at.apache.org)</li>
+      
+<li>Christopher Oliver (coliver.at.apache.org)</li>
+      
+<li>Giacomo Pati (giacomo.at.apache.org)</li>
+      
+<li>Konstantin Piroumian (kpiroumian.at.apache.org)</li>
+      
+<li>Marc Portier (mpo.at.apache.org)</li>
+      
+<li>Reinhard P&ouml;tz(reinhard.at.apache.org)</li>
+      
+<li>Ovidiu Predescu (ovidiu.at.apache.org)</li>
+      
+<li>Jeremy Quinn (jeremy.at.apache.org)</li>
+      
+<li>Gianugo Rabellino (gianugo.at.apache.org)</li>
+      
+<li>Ricardo Rocha (ricardo.at.apache.org)</li>
+      
+<li>Peter Royal (proyal.at.apache.org)</li>
+      
+<li>Sam Ruby (rubys.at.apache.org)</li>
+      
+<li>Paul Russell (prussell.at.apache.org)</li>
+      
+<li>Sebastien Sahuc (ssahuc.at.apache.org)</li>
+      
+<li>Andrew Savory (asavory.at.apache.org)</li>
+      
+<li>Diana Shannon (shannon.at.apache.org)</li>
+      
+<li>Davanum Srinivas (dims.at.apache.org)</li>
+      
+<li>Jeff Turner (jefft.at.apache.org)</li>
+      
+<li>Upayavira (upayavira.at.apache.org)</li>
+      
+<li>Sylvain Wallez (sylvain.at.apache.org)</li>
+      
+<li>Carsten Ziegeler (cziegeler.at.apache.org)</li>
+    
+</ul>
+ 
+
+
+</body>
+</html>

Added: cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-committers/meta.xml
URL: http://svn.apache.org/viewcvs/cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-committers/meta.xml?rev=164967&view=auto
==============================================================================
--- cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-committers/meta.xml (added)
+++ cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-committers/meta.xml Wed Apr 27 03:07:09 2005
@@ -0,0 +1,9 @@
+<?xml version="1.0"?>
+<meta>
+  <authors>
+    <author contact="http://cocoon.apache.org">Cocoon Community</author>
+  </authors>
+  <legacy>
+    <original-filename>community/members.html</original-filename>
+  </legacy>
+</meta>

Added: cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-contrib/comments_en.xml
URL: http://svn.apache.org/viewcvs/cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-contrib/comments_en.xml?rev=164967&view=auto
==============================================================================
--- cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-contrib/comments_en.xml (added)
+++ cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-contrib/comments_en.xml Wed Apr 27 03:07:09 2005
@@ -0,0 +1,3 @@
+<?xml version="1.0"?>
+<comments>
+</comments>

Added: cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-contrib/content_en.html
URL: http://svn.apache.org/viewcvs/cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-contrib/content_en.html?rev=164967&view=auto
==============================================================================
--- cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-contrib/content_en.html (added)
+++ cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-contrib/content_en.html Wed Apr 27 03:07:09 2005
@@ -0,0 +1,583 @@
+<!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>Contribution to Apache Cocoon</title>
+<link href="http://purl.org/DC/elements/1.0/" rel="schema.DC">
+<meta content="Robin Green" name="DC.Creator">
+<meta content="Stefano Mazzocchi" name="DC.Creator">
+</head>
+<body>
+
+ 
+<h1>Introduction</h1>
+
+  
+<p>
+   The Apache Cocoon Project is an <a class="external" href="http://www.opensource.org/">Open Source</a>
+   volunteer project under the auspices of the
+   <a class="external" href="http://www.apache.org/">Apache Software Foundation (ASF)</a>,
+   and, in harmony with the Apache webserver itself, it is released under
+   a very open 
+   <a class="external" href="http://www.apache.org/licenses/">license</a>.
+   This means there are many ways to contribute to the project - either
+   with direct participation (coding, documenting, answering questions,
+   proposing ideas, reporting bugs, suggesting bug-fixes, etc..) or by resource
+   donations (money, time, publicity, hardware, software, conference
+   presentations, speeches, etc...).
+  </p>
+  
+<p>
+   To begin with, we suggest you to subscribe to the
+   <a href="mail-lists.html">Cocoon mailing lists</a>
+   (follow the link for information on how to subscribe and to access the mail
+   list archives). Listen-in for a while, to hear how others make contibutions.
+  </p>
+
+  
+<p>You can get your local working copy of the
+   <a class="external" href="http://svn.apache.org/viewcvs.cgi/cocoon/branches/BRANCH_2_1_X/">current release branch</a>,
+   or the <a class="external" href="http://svn.apache.org/viewcvs.cgi/cocoon/trunk/">latest development branch</a>
+   from Subversion (SVN). 
+   Review the <a class="external" href="http://cocoon.apache.org/2.1/todo.html">todo</a> list, choose a task
+   (or perhaps you have noticed something that needs patching). Make the
+   changes, do the testing, generate a patch, if you need then discuss it on
+   the cocoon-dev mailing list, and add the patch to Bugzilla.
+   (Do not worry - the process is easy and explained below.)
+  </p>
+
+  
+<p>
+   Document writers are usually the most wanted people so if
+   you like to help but you're not familiar with the innermost technical details, don't worry:
+   we have work for you!
+  </p>
+ 
+
+ 
+<h1>Help Wanted Here</h1>
+  
+<p>
+   The rest of this document is mainly about
+   contributing new or improved code and/or documentation, but we would also be glad to have
+   extra help in any of the following areas:
+  </p>
+  
+<ul>
+   
+<li>Answering questions on the <span class="codefrag">cocoon-users</span> mailing list - there is often a problem of
+    having too many questioners and not enough experts to respond to all the questions.</li>
+   
+<li>Testing Cocoon (especially its less-frequently-used features) on various configurations
+    and reporting back.</li>
+   
+<li>Debugging - producing reproduceable test cases and/or finding causes of bugs. Some known bugs are informally listed on
+    <a class="external" href="http://cocoon.apache.org/2.1/todo.html">To Do</a>, and some are recorded in Bugzilla
+    (see <a href="#procedure">explanation below</a>).</li>
+   
+<li>Specifying/analysing/designing new features for Cocoon - and beyond. (If you wish to get involved
+    with this, please join <span class="codefrag">dev@cocoon.apache.org</span>
+    (you may also want to join <span class="codefrag">xsp-dev@xml.apache.org</span>), install and try out Cocoon
+    and read some of the <a href="mail-lists.html">mail archives</a>.
+    You should have a strong "fluency" in XML technologies, Java and a basic understanding of
+    the Cocoon architecture - don't just say "it should have XYZ" without reading anything first -
+    because chances are, someone's already thought of that feature!)</li>
+   
+<li>Packaging easy-to-install packages (such as RPMs) for the myriad of possible configurations out
+    there. (The Cocoon project does not maintain anything but the basic <span class="codefrag">.zip</span> and
+    <span class="codefrag">.tar.gz</span> packages, but anyone is welcome to build their own specific packages and
+    announce them on <span class="codefrag">cocoon-users</span>)</li>
+   
+<li>... and there is just one other thing - don't forget to tell everyone who asks, how great Cocoon is! ;-)
+    The more people that know about and start to use Cocoon, the larger the pool of
+    potential contributors there will be
+    - so, please, help us by placing the Cocoon logo somewhere in your
+    site to indicate that you are using and supporting the Cocoon Project.
+   </li>
+  
+</ul>
+ 
+  
+<p>
+   Thank you very much. 
+  </p>
+ 
+
+ 
+<a name="contrib"></a>
+ 
+<h1>Contributions of Code and Documentation</h1>
+   
+<p>
+     If you have a contribution that you would like to see incorporated into
+     the Cocoon distribution, then please take note of the 
+     <a href="#license">licensing requirements</a> listed below,
+     and then read the section 
+     <a href="#procedure">Procedure for Raising Development Issues</a>.
+   </p>
+
+   
+<p>
+     The Cocoon committers have been granted access by a vote of confidence,
+     so they are assumed to be trustworthy enough to make changes directly in
+     the source repository. Other contributors need to submit a patch via the Cocoon issue
+     tracker, Bugzilla.
+   </p>
+
+   
+<p>
+    Committers must be confident that it would work properly in all operating
+    systems, it must be documented as appropriate, it must be considered
+    sufficiently useful and general to go into Cocoon, and it must meet the
+    Licensing requirements below. Other committers and developers will continue
+    to enhance it, so don't be surprised if changes are made. Also the PMC may
+    decide to remove it, if issues are discovered.
+  </p>
+  
+  
+<h2>Testing Requirements for Cocoon Contrib and Distribution</h2>
+<p>All new code should be tested under at least the following servlet engines:</p>
+<ul>
+    
+<li>Apache Tomcat 3.2.2</li>
+   
+</ul>
+<p>It should also be tested on the following platforms:</p>
+<ul>
+    
+<li>A Windows operating system</li>
+    
+<li>A UNIX-type operating system</li>
+    
+<li>At least JDK version 1.3.x</li>
+   
+</ul>
+<p>And obviously, it should be tested using the current Cocoon source code!</p>
+<p>This testing is designed to iron out the most common kinds of incompatibility
+    problems (Servlet &gt;2.2 requirements; platform-dependent assumptions; JDK &gt;1.2 code).
+    These requirements are, of course, open to review and discussion. Note that
+    the contributor is not required to do the testing - indeed it is probably better
+    if someone else tests it, because the contributor might be tempted to do less
+    than thorough testing!</p>
+
+ 
+<h2>Documentation Requirements for Cocoon Distribution</h2>
+<p>All new features (processor, logicsheets, config options etc.) should be documented
+   appropriately (in XML or in <span class="codefrag">cocoon.xconf</span> in the case of config options).</p>
+<p>Use something like <span class="codefrag">xdocs/contrib.xml</span> as a rough guide, add
+   the new page(s) to <span class="codefrag">xdocs/book.xml</span> to create the menu-link
+   and type <span class="codefrag">build.sh docs</span> or <span class="codefrag">build.bat docs</span> to test the
+   documentation build.
+  </p>
+
+ 
+<a name="license"></a>
+ 
+<h2>Licensing Requirements for the Cocoon Distribution</h2>
+<p>To avoid legal problems, the Apache Project Management Committee (PMC) have agreed on
+   a policy for under what licensing code can be accepted into Apache projects:</p>
+<ul>
+   
+<li>Source code files (which include every file, code and documentation)
+   must be under the
+   <a class="external" href="http://www.apache.org/licenses/">Apache license</a>.
+    and must have copyright assigned to
+    the Apache Software Foundation.</li>
+   
+<li>Jar files need to be released under a license that permits free
+    redistribution (i.e. not any more restrictive than the Apache License).
+    So for example, the GPL and LGPL are not allowed,
+    but MPL and Apache licenses are allowed.</li>
+  
+</ul>
+<p>
+<strong>By submitting a patch, you signify your understanding and acceptance of these
+   conditions</strong> - like most open source projects, 
+   we do not have the resources nor the inclination to obtain signed statements from all
+   contributors!</p>
+ 
+
+ 
+<a name="svnhowto"></a>
+ 
+<h1>Subversion Usage Precis</h1>
+  
+<p>An overview of how to use Subversion to participate in Cocoon development.
+   Do not be afraid - you cannot accidently destroy the actual code repository,
+   because you are working with a local copy as an anonymous user. Therefore,
+   you do not have the system permissions to change anything. You can only 
+   update your local repository and compare your revisions with the real
+   repository.
+  </p>
+
+  
+<p>
+   (Further general Subversion usage information is at
+   <a class="external" href="http://subversion.tigris.org/">subversion.tigris.org</a>. Other resources include 
+   <a class="external" href="http://svnbook.red-bean.com/">"Version Control with Subversion"</a> and
+   <a class="external" href="http://softech.informatik.uni-kl.de/softech/content/einfothek/e2348/e2328/index_ger.html">a fast introduction</a>.
+  </p>
+
+  
+<p>
+   Let us lead by example. We will show you how to establish your local
+   repository, how to keep it up-to-date, and how to generate the differences
+   to create a patch. (The commands are for Linux.)
+  </p>
+
+ 
+<h2>How to Establish your Local Repository</h2>
+<p>
+   Decide whether you want to work with the "release branch" (2.1.X) or with
+   the trunk (2.2). Some developers use both.
+  </p>
+<p>
+   The following procedure will checkout the current copy of the release branch
+   of the master repository and
+   download it to your local disk. It will create a sub-directory called
+   <span class="codefrag">BRANCH_2_1_X</span>
+  
+</p>
+<ol>
+   
+<li>
+<span class="codefrag">cd /usr/local/svn/cocoon</span>
+</li>
+   
+<li>
+<span class="codefrag">svn co http://svn.apache.org/repos/asf/cocoon/branches/BRANCH_2_1_X/</span>
+</li>
+   
+<li>
+<span class="codefrag">cd BRANCH_2_1_X</span>
+</li>
+  
+</ol>
+<p>
+   You now have the release branch of the current source repository
+   for Cocoon on your local system. Go ahead and build and deploy as
+   usual. Make some changes, re-build, and see the effect.
+  </p>
+
+ 
+<h2>How to Keep it Up-to-date</h2>
+<p>
+   Every so often you should synchronise your local copy with the master
+   repository. Note that this definitely does not mean that your changes
+   will be applied to the master. Exactly the opposite will happen - updates
+   from the remote master version are merged into your local repository.
+   New items are automatically added to yours, and changed ones are refreshed.
+   If someone else happened to have submitted patches for the same files while
+   you were away, then changes will be merged with your copy and you will be
+   warned of any conflicts. Easy and automatic ...
+  </p>
+<ol>
+   
+<li>
+<span class="codefrag">cd /usr/local/svn/cocoon/BRANCH_2_1_X</span>
+</li>
+   
+<li>
+<span class="codefrag">svn update</span>
+</li>
+   
+<li>
+<strong>... pay attention to the update messages</strong>
+</li>
+  
+</ol>
+
+ 
+<h2>How to Generate Differences</h2>
+<p>
+   To contribute your modifications, you need to produce a plain-text file
+   containing the differences between the master copy and yours. You will
+   submit this to Bugzilla along with an explanation of why it is required,
+   and perhaps discuss it on the 
+   <span class="codefrag">cocoon-dev</span> mailing list. One of the authorised
+   maintainers of the repository will review the patch and then apply it to the
+   relevant branch.
+  </p>
+<p>
+   We will assume that you are adding some tips to this document
+   <span class="codefrag">xdocs/contrib.xml</span>
+  
+</p>
+<ol>
+   
+<li>Make the desired changes in your local repository, build, test it
+       thoroughly</li>
+   
+<li>
+<span class="codefrag">cd /usr/local/svn/cocoon/BRANCH_2_1_X/xdocs</span>
+</li>
+   
+<li>
+<span class="codefrag">svn diff contrib.xml &gt; $WORK/cocoon/contrib.xml.diff</span>
+</li>
+  
+</ol>
+
+ 
+<h2>How to get other branches</h2>
+<p>Okay, that got the current release branch of Cocoon into your local working copy.
+   If you want some other branch, then find the relevant branch name
+   from ViewCVS
+   <a class="external" href="http://svn.apache.org/viewcvs.cgi/cocoon/">http://svn.apache.org/viewcvs.cgi/cocoon/</a>
+   Then follow the same checkout procedure described above, using this ...
+  </p>
+<ul>
+   
+<li>
+<span class="codefrag">cd /usr/local/svn/cocoon</span>
+</li>
+   
+<li>
+<span class="codefrag">svn co http://svn.apache.org/repos/asf/cocoon/branches/BRANCHNAME</span>
+</li>
+  
+</ul>
+<p>
+   If you want to work with the trunk, then do this to create a local directory
+   called "cocoon-trunk" ...
+  </p>
+<ul>
+   
+<li>
+<span class="codefrag">cd /usr/local/svn/cocoon</span>
+</li>
+   
+<li>
+<span class="codefrag">svn co http://svn.apache.org/repos/asf/cocoon/trunk cocoon-trunk</span>
+</li>
+  
+</ul>
+ 
+
+ 
+<a name="committer"></a>
+ 
+<h1>Committer repository access</h1>
+  
+<p>After a developer has consistently provided contributions (code,
+   documentation and discussion), then the rest of the cocoon-dev community
+   may vote to grant this developer commit access to the repository.   To be able to 
+   commit you will first need to generate a subversion password. To do this, ssh to 
+   minotaur.apache.org and run <span class="codefrag">svnpasswd username</span>.  This will ask 
+   you for a subversion password. This is the user and password you can use when 
+   checking in code.
+   See also
+   <a class="external" href="http://www.apache.org/dev/version-control.html">ASF developer notes</a>
+   about version control.
+   </p>
+ 
+
+ 
+<a name="procedure"></a>
+ 
+<h1>Procedure for Raising Development Issues</h1>
+  
+<p>Documentation contributions can usually be added directly to the
+    issue tracker. First read the 
+    <a href="#contrib">contribution notes</a> above, then follow the
+    <a class="external" href="http://cocoon.apache.org/2.1/howto/index.html#Contribution">howto documents</a>
+    about patching and about using Bugzilla.
+  </p>
+  
+<p>
+   There are two methods for discussing development and submitting patches.
+   So that everyone can be productive, it is important to know which method
+   is appropriate for a certain situation and how to go about it without
+   confusion. This section explains when to use the 
+   <span class="codefrag">cocoon-dev</span> <a href="mail-lists.html">mailing list</a>
+   and when to use
+   <a class="external" href="http://issues.apache.org/bugzilla/">Bugzilla</a>
+   (the Apache Bug Database).
+  </p>
+
+  
+<p>
+   Research your topic thoroughly before beginning to discuss a new
+   development issue. Search and browse through the email archives - your
+   issue may have been discussed before. Prepare your post clearly and
+   concisely.
+  </p>
+
+  
+<p>
+   Most issues will be discovered, resolved, and then patched quickly
+   via the <span class="codefrag">cocoon-dev</span> mailing list. Larger issues, and ones that
+   are not yet fully understood or are hard to solve, are destined for
+   Bugzilla.
+  </p>
+
+  
+<p>
+   Experienced developers use Bugzilla directly, as they are very sure
+   when they have found a bug and when not. However, less experienced users
+   should first discuss it on the user or developer mailing list (as
+   appropriate). Impatient people always enter everything into Bugzilla
+   without caring if it is a bug of Cocoon or their own
+   installation/configuration mistake - please do not do this.
+  </p>
+
+  
+<p>
+   As a rule-of-thumb, discuss an issue on the <span class="codefrag">cocoon-dev</span>
+   mailing list first to work out any details.
+   After it is confirmed to be worthwhile, and you are clear about it,
+   then submit the bug description via Bugzilla.
+  </p>
+
+  
+<p>
+   When you are sure about your proposed patch, then please submit it
+   <a class="external" href="http://cocoon.apache.org/2.1/howto/index.html#Contribution">via Bugzilla</a>,
+   rather than as email to <span class="codefrag">cocoon-dev</span>.
+   Be sure to add [PATCH] to the summary line, as this enables the automatic
+   patch alert system to keep track of it. If you do not follow this procedure,
+   then unfortunately your patch may be over-looked.
+  </p>
+
+  
+<p>
+   When posting discussion topics to the <span class="codefrag">cocoon-dev</span> list,
+   then please be patient.
+   Perhaps you do not get any answer on your first reply, so just post
+   it again until you get one. (But please not every hour - allow a few
+   days for the list to deal with it.) Do not be impatient - remember that
+   the whole world is busy, not just you. Bear in mind that other countries
+   will have holidays at different times to your country and that they are
+   in different time zones. You might also consider re-writing your initial
+   posting - perhaps it was not clear enough
+   and the readers' eyes glazed over.
+  </p>
+ 
+
+ 
+<a name="tips"></a>
+ 
+<h1>Contribution Notes and Tips</h1>
+  
+<p>
+   This is a collection of tips for contributing to the project in a manner
+   that is productive for all parties.
+  </p>
+
+  
+<ul>
+   
+<li>
+    Every contribution is worthwhile. Even if the ensuing discussion
+    proves it to be off-beam, then it may jog ideas for other people.
+   </li>
+   
+<li>
+    Use sensible and concise email subject headings. Search engines, and
+    humans trying to browse a voluminous list, will respond favourably to a
+    descriptive title.
+   </li>
+   
+<li>
+    See <a href="mail-lists.html">Tips</a> for Cocoon mailing lists and 
+    <a class="external" href="http://learn.to/edit_messages/">Message Editing and
+    Quoting Guide (with Examples)</a>.
+   </li>
+   
+<li>Start new threads with new Subject for new topics, rather than
+    re-using the previous Subject line.
+   </li>
+   
+<li>Keep each topic focussed. If some new topic arises then start a new
+    discussion. This leaves the original topic to continue un-cluttered.
+   </li>
+   
+<li>Whenever you decide to start a new topic, then start with a fresh
+    new email message window. Do not use the "Reply to" button,
+    because threaded mail-readers get confused (they utilise the 
+    <span class="codefrag">In-reply-to</span> header). If so, then your new topic will get
+    lost in the previous thread and go un-answered.
+   </li>
+   
+<li>
+    Prepend your email subject line with a marker when that is appropriate,
+    e.g. <span class="codefrag">[Vote]</span>, <span class="codefrag">[Proposal]</span>, 
+    <span class="codefrag">[RT]</span> (Random Thought which quickly blossom into research
+    topics :-), <span class="codefrag">[STATUS]</span> (development status of a certain
+    facility).
+   </li>
+   
+<li>
+    Please follow up with a final posting when your issue is solved. This
+    should summarise your problem and its solution. Add [SUMMARY] to the
+    subject line. This will ease the FAQ generation and searching of the list.
+    Note that some people tend to ignore questions from those that never
+    follow up.
+   </li>
+   
+<li>
+    When making changes to XML documentation, or any XML document for that
+    matter, use a 
+    <a class="external" href="http://www.oasis-open.org/cover/">validating parser</a>
+    (one that is tried and true is
+    <a class="external" href="http://openjade.sourceforge.net/">OpenSP/onsgmls</a>).
+    This procedure will detect errors without having to go through the whole
+    <span class="codefrag">build docs</span> process to find them. Do not expect Cocoon
+    or the build system to detect the validation errors for you - they can
+    do it, but that is not their purpose. (Anyway, onsgmls validation error
+    messages are more informative.)
+   </li>
+   
+<li>
+    Remember that most people are participating in development on a
+    volunteer basis and in their "spare time". These enthusiasts will attempt
+    to respond to issues. It may take a little while to get your answers.
+   </li>
+   
+<li>
+    Research your topic thoroughly before beginning to discuss a new
+    development issue. Search and browse through the email archives - your
+    issue may have been discussed before. Do not just perceive a problem and
+    then rush out with a question - instead, delve.
+   </li>
+   
+<li>
+    Try to at least offer a partial solution and not just a problem statement.
+   </li>
+   
+<li>
+    Take the time to clearly explain your issue and write a concise email
+    message. Less confusion facilitates fast and complete resolution.
+   </li>
+   
+<li>
+    Do not bother to send an email reply that simply says "thanks".
+    When the issue is resolved, that is the finish - end of thread.
+    Reduce clutter.
+   </li>
+   
+<li>
+    When sending a patch, you usually do not need to worry about which
+    branch it should be applied to. The maintainers of the repository will
+    decide and might also apply it to the trunk. Please indicate on the
+    Bugzilla entry which branch you have used to prepare your patch.
+   </li>
+   
+<li>
+    If an issue starts to get bogged down in list discussion, then it may
+    be appropriate to go into private off-list discussion with a few interested
+    other people. Spare the list from the gory details. Report a summary back
+    to the list to finalise the thread.
+   </li>
+   
+<li>
+    Become familiar with the mailing lists. As you browse and search, you will
+    see the way other people do things. Follow the leading examples.
+   </li>
+  
+</ul>
+ 
+
+
+</body>
+</html>

Added: cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-contrib/meta.xml
URL: http://svn.apache.org/viewcvs/cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-contrib/meta.xml?rev=164967&view=auto
==============================================================================
--- cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-contrib/meta.xml (added)
+++ cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-contrib/meta.xml Wed Apr 27 03:07:09 2005
@@ -0,0 +1,9 @@
+<?xml version="1.0"?>
+<meta>
+  <authors>
+    <author contact="http://cocoon.apache.org">Cocoon Community</author>
+  </authors>
+  <legacy>
+    <original-filename>community/contrib.html</original-filename>
+  </legacy>
+</meta>

Added: cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-devinfo-merge-to-committer/comments_en.xml
URL: http://svn.apache.org/viewcvs/cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-devinfo-merge-to-committer/comments_en.xml?rev=164967&view=auto
==============================================================================
--- cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-devinfo-merge-to-committer/comments_en.xml (added)
+++ cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-devinfo-merge-to-committer/comments_en.xml Wed Apr 27 03:07:09 2005
@@ -0,0 +1,3 @@
+<?xml version="1.0"?>
+<comments>
+</comments>

Added: cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-devinfo-merge-to-committer/content_en.html
URL: http://svn.apache.org/viewcvs/cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-devinfo-merge-to-committer/content_en.html?rev=164967&view=auto
==============================================================================
--- cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-devinfo-merge-to-committer/content_en.html (added)
+++ cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-devinfo-merge-to-committer/content_en.html Wed Apr 27 03:07:09 2005
@@ -0,0 +1,66 @@
+<!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>Cocoon Developer Info</title>
+<link href="http://purl.org/DC/elements/1.0/" rel="schema.DC">
+</head>
+<body>
+    
+<h1>Overview</h1>
+      
+      
+<p>
+        This page lists resources and information useful to Apache Cocoon
+        committers. 
+      </p>
+      
+<ul>
+        
+<li>
+<a href="releasing.html">Howto Release Cocoon</a>
+</li>
+      
+</ul>
+    
+    
+<h1>Apache Developer Info</h1>
+      
+      
+<p>
+        Here are some interesting resources and information useful to all
+        Apache committers.  More information can be obtained from the
+        infrastructure@apache.org mailing list.
+      </p>
+      
+<ul>
+        
+<li>
+<a class="external" href="http://www.apache.org/dev">Apache Developer Info</a>
+</li>
+        
+<li>
+<a class="external" href="http://www.apache.org/dev/contributors.html">Contributors Tech Guide</a>
+</li>
+        
+<li>
+<a class="external" href="http://www.apache.org/dev/committers.html">Committers FAQ</a>
+</li>
+        
+<li>
+<a class="external" href="http://www.apache.org/dev/pmc.html">PMC FAQ</a>
+</li>
+        
+<li>
+<a class="external" href="http://www.apache.org/dev/version-control.html">Version Control FAQ</a>
+</li>
+        
+<li>
+<a class="external" href="http://www.apache.org/dev/machines.html">Machines List</a>
+</li>
+      
+</ul>
+    
+  
+</body>
+</html>

Added: cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-devinfo-merge-to-committer/meta.xml
URL: http://svn.apache.org/viewcvs/cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-devinfo-merge-to-committer/meta.xml?rev=164967&view=auto
==============================================================================
--- cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-devinfo-merge-to-committer/meta.xml (added)
+++ cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-devinfo-merge-to-committer/meta.xml Wed Apr 27 03:07:09 2005
@@ -0,0 +1,9 @@
+<?xml version="1.0"?>
+<meta>
+  <authors>
+    <author contact="http://cocoon.apache.org">Cocoon Community</author>
+  </authors>
+  <legacy>
+    <original-filename>devinfo/index.html</original-filename>
+  </legacy>
+</meta>

Added: cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-fr-mail-lists/comments_en.xml
URL: http://svn.apache.org/viewcvs/cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-fr-mail-lists/comments_en.xml?rev=164967&view=auto
==============================================================================
--- cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-fr-mail-lists/comments_en.xml (added)
+++ cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-fr-mail-lists/comments_en.xml Wed Apr 27 03:07:09 2005
@@ -0,0 +1,3 @@
+<?xml version="1.0"?>
+<comments>
+</comments>

Added: cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-fr-mail-lists/content_en.html
URL: http://svn.apache.org/viewcvs/cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-fr-mail-lists/content_en.html?rev=164967&view=auto
==============================================================================
--- cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-fr-mail-lists/content_en.html (added)
+++ cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-fr-mail-lists/content_en.html Wed Apr 27 03:07:09 2005
@@ -0,0 +1,60 @@
+<!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>Liste users-fr</title>
+<link href="http://purl.org/DC/elements/1.0/" rel="schema.DC">
+<meta content="Sylvain Wallez" name="DC.Creator">
+</head>
+<body>
+    
+<h1>Notes pr&eacute;liminaires</h1>
+      
+
+      
+<p>Lors de la discussion qui a abouti &agrave; la cr&eacute;ation de cette liste, certains ont &eacute;voqu&eacute; le risque de partitionnement de la communaut&eacute; des utilisateurs. Le but de cette liste est au contraire de permettre &agrave; ceux que les listes anglophones rebutent, soit par leur trafic important, soit &agrave; cause de difficult&eacute;s &agrave; s'exprimer en anglais, de participer malgr&eacute; tout &agrave; la vie de la communaut&eacute; Cocoon. Ne n&eacute;gligez donc pas les <a href="../community/mail-lists.html">listes anglophones</a>, qui restent le lieu principal d'&eacute;changes.</p>
+
+      
+<p>Avant de poser une question sur la liste de discussion, consultez au pr&eacute;alable les <a href="../community/mail-lists.html">recommentations et r&egrave;gles d'usage</a> (en anglais).</p>
+    
+
+    
+<h1>La liste users-fr</h1>
+      
+      
+<p>C'est une liste g&eacute;n&eacute;rale pour les probl&egrave;mes (et leurs r&eacute;ponses !), demandes de conseils, etc. relatifs &agrave; Cocoon, ainsi que les annonces sp&eacute;cifiques &agrave; la communaut&eacute; francophone.</p>
+
+      
+<p>Apr&egrave;s inscription, &eacute;crivez &agrave; <span class="codefrag">users-fr&lt;at&gt;cocoon.apache.org</span>.</p>
+      
+      
+<p>
+<a href="mailto:users-fr-subscribe.at.cocoon.apache.org">Inscription</a> - <a href="mailto:users-fr-allow-subscribe.at.cocoon.apache.org">Inscription "allow"</a> (vous ne recevez pas les mails, mais vous pouvez poster par exemple depuis gname.org) - 
+        <a href="mailto:users-fr-unsubscribe.at.cocoon.apache.org">D&eacute;sinscription</a>
+</p>
+
+      
+<p>Attention : ce n'est pas une liste pour discuter de questions g&eacute;n&eacute;rales sur XML ou XSLT. La liste <a class="external" href="http://xmlfr.org/listes/xml-tech/">xmlfr-tech</a> est plus adapt&eacute;e pour ces sujets.</p>
+    
+    
+    
+<h1>Archives</h1>
+      
+      
+<p>Les archives de la liste users-fr sont disponibles sur plusieurs sites :</p>
+      
+<ul>
+         
+<li>gmane.org : recherche, consultation par <a class="external" href="http://news.gmane.org/gmane.text.xml.cocoon.french">fil de discussion</a>, <a class="external" href="nntp://news.gmane.org/gmane.text.xml.cocoon.french">newsgroup</a> et <a class="external" href="http://rss.gmane.org/gmane.text.xml.cocoon.french">flux RSS</a>.</li>         
+         
+<li>www.mail-archive.com : recherche, consultation par <a class="external" href="http://www.mail-archive.com/users-fr@cocoon.apache.org/maillist.html">date</a>, <a class="external" href="http://www.mail-archive.com/users-fr@cocoon.apache.org/">fil de discussion</a> et <a class="external" href="http://www.mail-archive.com/users-fr@cocoon.apache.org/maillist.xml">flux RSS</a>.</li>
+         
+<li>cocoon.apache.org : <a class="external" href="http://cocoon.apache.org/mail/users-fr/">archives brutes</a>.</li>
+         
+<li>La liste est aussi en cours d'enregistrement sur <a class="external" href="http://marc.theaimsgroup.com/">Aims Group</a>.</li>
+      
+</ul>
+    
+  
+</body>
+</html>

Added: cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-fr-mail-lists/meta.xml
URL: http://svn.apache.org/viewcvs/cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-fr-mail-lists/meta.xml?rev=164967&view=auto
==============================================================================
--- cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-fr-mail-lists/meta.xml (added)
+++ cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-fr-mail-lists/meta.xml Wed Apr 27 03:07:09 2005
@@ -0,0 +1,9 @@
+<?xml version="1.0"?>
+<meta>
+  <authors>
+    <author contact="http://cocoon.apache.org">Cocoon Community</author>
+  </authors>
+  <legacy>
+    <original-filename>fr/mail-lists.html</original-filename>
+  </legacy>
+</meta>

Added: cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-francais/comments_en.xml
URL: http://svn.apache.org/viewcvs/cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-francais/comments_en.xml?rev=164967&view=auto
==============================================================================
--- cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-francais/comments_en.xml (added)
+++ cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-francais/comments_en.xml Wed Apr 27 03:07:09 2005
@@ -0,0 +1,3 @@
+<?xml version="1.0"?>
+<comments>
+</comments>

Added: cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-francais/content_en.html
URL: http://svn.apache.org/viewcvs/cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-francais/content_en.html?rev=164967&view=auto
==============================================================================
--- cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-francais/content_en.html (added)
+++ cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-francais/content_en.html Wed Apr 27 03:07:09 2005
@@ -0,0 +1,44 @@
+<!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>Le Projet Apache Cocoon</title>
+<link href="http://purl.org/DC/elements/1.0/" rel="schema.DC">
+<meta content="Sylvain Wallez" name="DC.Creator">
+</head>
+<body>
+    
+<h1>Apache Cocoon</h1>
+      
+      
+<p>Apache Cocoon est une plate-forme de d&eacute;veloppement d'applications web fond&eacute;e sur la s&eacute;paration des domaines techniques et l'assemblage de composants.</p>
+      
+      
+<p>Cocoon impl&eacute;mente ces concepts par la notion de "pipelines de composants", chaque composant du pipeline &eacute;tant d&eacute;di&eacute; &agrave; une fonction particuli&egrave;re. Cela permet d'utiliser une approche du type "Lego" pour la construction d'applications web, en assemblant des cha&icirc;nes de composants, sans n&eacute;cessiter de programmation.</p>
+      
+      
+<p>Cocoon est la "colle web" pour vos d&eacute;veloppements d'applications web. C'est une colle qui assemble les diff&eacute;rentes probl&eacute;matiques et permet ainsi l'&eacute;volution parall&egrave;le de tous les aspects de l'application, augmentant de ce fait la rapidit&eacute; de d&eacute;veloppement et r&eacute;duisant les recouvrements entre les intervenants.</p>
+    
+  
+    
+<h1>Le Projet Apache Cocoon</h1>
+      
+      
+<p>Le <em>Projet Apache Cocoon</em> est le groupe open source qui d&eacute;veloppe la plate-forme Apache Cocoon. Dot&eacute; d'un fort ancrage dans les techonologies XML et applications serveur, le Projet Apache Cocoon est compos&eacute; de personnes partageant des valeurs communes de collaboration intense pour d&eacute;velopper du logiciel open source de grande qualit&eacute;. Le Projet Apache Cocoon partage ces valeurs avec l'organisation qui l'h&eacute;berge, la <a class="external" href="http://www.apache.org/foundation/">Fondation Apache</a>.</p>
+    
+  
+    
+<h1>Pourquoi une zone francophone ?</h1>
+      
+      
+<p>Au cours de nombreux contacts avec des utilisateurs de Cocoon en France, soit &agrave; travers des sites francophones tels que <a class="external" href="http://xmlfr.org/">XMLfr</a>, soit directement, <a class="external" href="http://www.apache.org/~sylvain/">je</a> me suis rendu compte que peu d'entre eux &eacute;taient inscrits sur les <a href="../community/mail-lists.html">listes de discussions anglophones</a> et que beaucoup n'&eacute;taient pas conscients de l'importance de la communaut&eacute; dans les projets open source.</p>
+      
+      
+<p>C'est donc pour cela que cette zone a &eacute;t&eacute; cr&eacute;&eacute;e : permettre aux utilisateurs francophones de Cocoon (et pas seulement les fran&ccedil;ais) de rejoindre la grande communaut&eacute; Apache pour &eacute;changer, discuter, et enfin ne plus &ecirc;tre seuls devant les probl&egrave;mes qui surviennent lors de l'utilisation de Cocoon.</p>
+      
+      
+<p>Cette zone restera tr&egrave;s probablement limit&eacute;e &agrave; quelques pages d'introduction g&eacute;n&eacute;rales et &agrave; la <a href="../fr/mail-lists.html">liste de discussion</a>. Traduire l'ensemble de la documentation est une t&acirc;che au long cours que nous ne voulons pas entreprendre, &agrave; moins que des volontaires ne se pr&eacute;sentent !</p>
+    
+  
+</body>
+</html>

Added: cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-francais/meta.xml
URL: http://svn.apache.org/viewcvs/cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-francais/meta.xml?rev=164967&view=auto
==============================================================================
--- cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-francais/meta.xml (added)
+++ cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-francais/meta.xml Wed Apr 27 03:07:09 2005
@@ -0,0 +1,9 @@
+<?xml version="1.0"?>
+<meta>
+  <authors>
+    <author contact="http://cocoon.apache.org">Cocoon Community</author>
+  </authors>
+  <legacy>
+    <original-filename>fr/index.html</original-filename>
+  </legacy>
+</meta>

Added: cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-history/comments_en.xml
URL: http://svn.apache.org/viewcvs/cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-history/comments_en.xml?rev=164967&view=auto
==============================================================================
--- cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-history/comments_en.xml (added)
+++ cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-history/comments_en.xml Wed Apr 27 03:07:09 2005
@@ -0,0 +1,3 @@
+<?xml version="1.0"?>
+<comments>
+</comments>

Added: cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-history/content_en.html
URL: http://svn.apache.org/viewcvs/cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-history/content_en.html?rev=164967&view=auto
==============================================================================
--- cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-history/content_en.html (added)
+++ cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-history/content_en.html Wed Apr 27 03:07:09 2005
@@ -0,0 +1,87 @@
+<!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>History</title>
+<link href="http://purl.org/DC/elements/1.0/" rel="schema.DC">
+<meta content="Stefano Mazzocchi" name="DC.Creator">
+</head>
+<body>
+    
+<p> Cocoon started simply enough. In 1998 Jon Stevens -- of Apache JServ,
+    Turbine, Velocity, Anakia, and Tigris Scarab fame -- and I created scripts
+    that managed the automatic update of the java.apache.org site. The scripts
+    were dead simple: iterate over all the CVS modules that java.apache.org had
+    under the /docs and copy them to the right place.</p>
+    
+<p>The problem was that people were continously messing up the docs. Few
+    people want to write documentation for open source projects; when they do,
+    you thank them and don't complain about coherence of style and stuff like
+    that. Or you won't have any docs at all.</p>
+    
+<p>The solution was obvious: we needed a way to separate style from
+    content. In late 1998 the first XSL working draft was released and IBM
+    made a Java XSL processor, LotusXSL, available. I downloaded both and
+    started to play around with what was later called XSLT. While playing with
+    this stuff, I quickly grew tired of typing a command line, moving to the
+    browser to see the result, over and over. I wanted a less tedious
+    change-transform-reload cycle.</p>
+    
+<p>So I wrote a servlet that handled the tedious bits for me; I could
+    modify the stylesheet, hit reload on the browser, and the servlet would
+    handle everything. This was at the very end of 1998 and Ron Howard's movie
+    Cocoon was playing on the television, which explains the weird name only
+    partially. I believed at the time that these technologies were a key part
+    of the future of the Web, so a cocoon was just what was needed to allow
+    them to incubate and grow stronger.</p>
+    
+<p>Apache Cocoon 1.0 was a servlet, about 100 lines of code, that used
+    XML4J (later Apache Xerces) and LotusXSL (later Apache Xalan) to transform
+    an XML file with an XSL stylesheet. At that time, XSLT, XPath and XSL:FO
+    were still part of one big spec. I didn't think it was very useful for
+    anyone else so I kept it on my disk for a few months. Then, around March
+    1999, on the jserv-dev mail list somebody was asking about XSL, and I said
+    that I'd written a servlet that did all that transformation on the server
+    side. Many people asked for it, so I requested a formal vote and the Apache
+    Cocoon project was started under the java.apache.org umbrella.</p>
+
+	
+<p>The 1.0 version contained very little code, but lots of examples and
+	some simple docs that explained what XSL was and why I thought it	was
+	important to learn it. After its release, people started joining active
+	development, and we turned a small servlet into a full XML-based publishing
+	system, which is now used in many production sites around the world.</p>
+	
+	
+<p>But Cocoon 1.x was designed when the XML world was very young and
+	experience was very small and it was based under several design choices
+	that turned to be very limiting.  So, around November 1999, I expressed the
+	intention to work on the next generation (what people started calling
+	Cocoon2 or simply C2) to solve all those architectural issues.</p>
+	
+	
+<p>It took two years and three different project leaders to finish Cocoon
+	2.0 but we made it.  It's an XML framework that raises the usage of XML and
+	XSLT technologies for server applications to a new level. Designed for
+	performance and scalability around pipelined SAX processing, Cocoon offers
+	a flexible environment based on the separation of concerns between content,
+	logic and style. A centralized configuration system and sophisticated
+	caching enable you to create, deploy, and maintain rock-solid XML server
+	applications.</p>
+	
+	
+<p>Cocoon was designed as an abstract engine that could be connected to
+	almost anything, but it ships with servlet and command line connectors. The
+	servlet connector allows you to call Cocoon from your favorite servlet
+	engine or application server. You can install it beside your existing
+	servlets or JSPs. The command line interface allows you to generate static
+	content as a batch process. It can be useful to pre-generate those parts of
+	your site that are static, some of which may be easier to create by using
+	Cocoon functionalities than directly (say, SVG rasterization or applying
+	stylesheets). For example, the Cocoon documentation and web site are all
+	generated by Cocoon from the command line.</p>
+	
+<p>The history will continue here...</p>
+  
+</body>
+</html>

Added: cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-history/meta.xml
URL: http://svn.apache.org/viewcvs/cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-history/meta.xml?rev=164967&view=auto
==============================================================================
--- cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-history/meta.xml (added)
+++ cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-history/meta.xml Wed Apr 27 03:07:09 2005
@@ -0,0 +1,9 @@
+<?xml version="1.0"?>
+<meta>
+  <authors>
+    <author contact="http://cocoon.apache.org">Cocoon Community</author>
+  </authors>
+  <legacy>
+    <original-filename>history.html</original-filename>
+  </legacy>
+</meta>

Added: cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-hosting/comments_en.xml
URL: http://svn.apache.org/viewcvs/cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-hosting/comments_en.xml?rev=164967&view=auto
==============================================================================
--- cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-hosting/comments_en.xml (added)
+++ cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-hosting/comments_en.xml Wed Apr 27 03:07:09 2005
@@ -0,0 +1,3 @@
+<?xml version="1.0"?>
+<comments>
+</comments>

Added: cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-hosting/content_en.html
URL: http://svn.apache.org/viewcvs/cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-hosting/content_en.html?rev=164967&view=auto
==============================================================================
--- cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-hosting/content_en.html (added)
+++ cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-hosting/content_en.html Wed Apr 27 03:07:09 2005
@@ -0,0 +1,122 @@
+<!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>Cocoon Hosting</title>
+<link href="http://purl.org/DC/elements/1.0/" rel="schema.DC">
+<meta content="Robin Green" name="DC.Creator">
+</head>
+<body>
+  
+<h1>Cocoon Hosting</h1>
+   
+<p>
+    Here is a list of some sites that provide Apache Cocoon web hosting
+    (in no particular order). Version information may not be up-to-date
+    on this list, so always check with the site itself to make sure. Of course,
+    most are commercial providers, yet some have free services.
+   </p>
+
+   
+<ul>
+    
+<li>
+<a class="external" href="http://www.aoindustries.com/">AO Industries</a>
+</li>
+    
+<li>
+<a class="external" href="http://webartists.net/webhosting.html">Webartists</a> (German)</li>
+    
+<li>
+<a class="external" href="http://www.capital-internet.net/">Capital Internet</a> - Cocoon 2 (pre-2.0 support will still be available)</li>
+    
+<li>
+<a class="external" href="http://dev.startcom.org/">MediaHost Developer Accounts</a> - from Cocoon 1.8.2 up to latest Cocoon 2.1</li>
+    
+<li>
+<a class="external" href="http://www.va.com.au/">Virtual Artists Pty Ltd</a> - Cocoon 1 or Cocoon 2</li>
+    
+<li>
+<a class="external" href="http://www.hub.org/">Hub.Org Networking Services</a> - Cocoon 2 or Cocoon 1</li>
+    
+<li>
+<a class="external" href="http://www.dyanet.com/">Dyanet</a> - Cocoon 2</li>
+    
+<li>
+<a class="external" href="http://www.mmaweb.net/">Motivational Marketing Associates, Inc</a> - Cocoon 1.7.4</li>
+    
+<li>
+<a class="external" href="http://www.webappcabaret.com">WebAppCabaret</a> - Cocoon 2.0.2</li>
+    
+<li>
+<a class="external" href="http://www.wisernet.com">Wiserlabz</a> - Cocoon 2.0.3 for commercial projects.</li>
+    
+<li>
+<a class="external" href="http://www.hebergement-pro.com">Hebergement-pro</a> - Cocoon 2.0.2, including cheap starter pack.</li>
+    
+<li>
+<a class="external" href="http://rimuhosting.com">RimuHosting</a> - Java hosting specialists, latest Cocoon on request.</li>
+    
+<li>
+<a class="external" href="http://www.starline-net.de">StarLine Webhosting</a> - with Tomcat and Cocoon 2.1 (Germany).</li>
+    
+<li>
+<a class="external" href="http://dotco.co.za">DOTCO Business Internet Solutions</a>
+</li>
+    
+<li>
+<a class="external" href="http://www.oxxus.net/">Oxxus Hosting</a> - Tomcat 4.1.29, Jetty on request, Cocoon 2.1.3</li>
+    
+<li>
+<a class="external" href="http://www.alacartejava.com">Alacarte Java Hosting</a> - JSP and Servlet hosting (incl. arbitrary Cocoon version)</li>
+    
+<li>
+<a class="external" href="http://www.metawerx.net/">metawerx</a> - Cocooon 2.1 on Tomcat</li>
+    
+<li>
+<a class="external" href="http://jsp-servlet.net/">jsp-servlet.net</a> - JSP and Servlet hosting, supports Cocoon 2.1.3, Tomcat 4 and 5, JBoss 3, etc.</li>
+    
+<li>
+<a class="external" href="http://www.eway.fr/">EWAY Telecom</a> - Tomcat 5, Cocoon 2</li>
+    
+<li>
+<a class="external" href="http://www.jspzone.net/">JSPZone Web Hosting</a> - Tomcat 4/5, Cocoon 2.1</li>
+    
+<li>
+<a class="external" href="http://www.prokmu.com">Prokmu Hosting</a> - Tomcat 5.0.18, Cocoon 2.1.3 (Switzerland)</li>
+   
+</ul>
+
+   
+<p>
+<strong>Free ...</strong>
+</p>
+   
+<ul>
+    
+<li>
+<a class="external" href="http://www.wiserlabz.com">Wiserlabz</a> - free Cocoon, Tomcat and Apache developer accounts.</li>
+   
+</ul>
+  
+
+  
+<h1>How to get listed</h1>
+   
+<p>
+    If you do not find your site here, make sure you
+    <a href="mailto:users.at.cocoon.apache.org?subject=Link Hosting:">tell us</a>.
+    Enter a meaningful title after the words "Link Hosting:"
+    in the subject, provide a short summary of your site and do not forget
+    to tell us the URL.
+    You could also follow the <a href="../community/contrib.html">Contributing</a>
+    page to make it easier for everyone.
+   </p>
+   
+<p>
+    You must have Cocoon up and running and be accepting application forms.
+   </p>
+  
+
+</body>
+</html>

Added: cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-hosting/meta.xml
URL: http://svn.apache.org/viewcvs/cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-hosting/meta.xml?rev=164967&view=auto
==============================================================================
--- cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-hosting/meta.xml (added)
+++ cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-hosting/meta.xml Wed Apr 27 03:07:09 2005
@@ -0,0 +1,9 @@
+<?xml version="1.0"?>
+<meta>
+  <authors>
+    <author contact="http://cocoon.apache.org">Cocoon Community</author>
+  </authors>
+  <legacy>
+    <original-filename>link/hosting.html</original-filename>
+  </legacy>
+</meta>

Added: cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-incubation/comments_en.xml
URL: http://svn.apache.org/viewcvs/cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-incubation/comments_en.xml?rev=164967&view=auto
==============================================================================
--- cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-incubation/comments_en.xml (added)
+++ cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-incubation/comments_en.xml Wed Apr 27 03:07:09 2005
@@ -0,0 +1,3 @@
+<?xml version="1.0"?>
+<comments>
+</comments>

Added: cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-incubation/content_en.html
URL: http://svn.apache.org/viewcvs/cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-incubation/content_en.html?rev=164967&view=auto
==============================================================================
--- cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-incubation/content_en.html (added)
+++ cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-incubation/content_en.html Wed Apr 27 03:07:09 2005
@@ -0,0 +1,153 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
+<title>The meaning of Cocoon sub-project incubation</title>
+<link href="http://purl.org/DC/elements/1.0/" rel="schema.DC">
+</head>
+<body>
+    
+<p>
+    After years of software development and hundreds of developers coming in
+    and out, a concept crystallized around the ASF and it basically says:
+    </p>
+
+    
+<p>
+    
+<strong>A development community is more important than the software
+    that it develops.</strong>
+    
+</p>
+
+    
+<p>
+    The reason for this is simple: Software does not evolve by itself.
+    Since software lives in an environment which is continously changing,
+    then software that is perfect for the job today, might not be so in
+    the future.
+    </p>
+
+    
+<p>
+    The existence of a healthy development community around code guarantees
+    that software evolution will evolve to fit the environmental constraints.
+    </p>
+
+    
+<p>
+    What does make a community "healthy"?
+    </p>
+
+    
+<p>
+    Again, after years of successes and failures, there is general consensus
+    that a development community is healthy if:
+    </p>
+
+    
+<p>
+     1) it exhibits diversity
+    </p>
+
+    
+<p>
+     2) it presents an open attitude toward confrontation, changes, and new
+    committers
+    </p>
+
+    
+<p>
+    Note that the above rules do *NOT* take into consideration technological
+    concepts: the ASF is *very* open to technological differences, so much
+    so, in fact, that technical considerations are left to the users or to
+    the markets, but are not filtered out by the Foundation itself.
+    </p>
+
+    
+<p>
+    The ASF cares *exclusively* about the quality of the communities
+    and the reason is mainly because a healthy community brings back more
+    energy to the foundation than it consumes (positive engine!), while
+    a non-healthy community is very likely to drain more energy from the
+    foundation than it is able to donate back.
+    </p>
+
+    
+<p>
+    The ASF can sustain its growth only if new efforts bring more energy
+    into the system than they use, thus contributing positively to the
+    entire energetic equation.
+    </p>
+
+    
+<p>
+    However building a community takes time and effort, expecially if it was
+    never done before.
+    </p>
+
+    
+<p>
+    For this reason, the ASF created the concept of "incubation" to allow
+    healthy communities to be bootstrapped.
+    </p>
+
+    
+<p>
+    A project under incubation is basically a project that is not yet
+    considered healthy enough to be able to give back to the Foundation
+    more energy that it consumes.
+    </p>
+
+    
+<p>
+    Many times incubation is done because lack of diversity. For example, if
+    one entity (company, group or individual) donates software to the
+    Foundation, but only people belonging to that entity work on it.
+    </p>
+
+    
+<p>
+    Diversity is important because it creates long-term stability. It has
+    happened in the past that, for example, a company goes bankrupt and all
+    the people who worked on the project are gone, leaving the project with
+    no development community. This is unacceptable because a project without
+    a working community drains an incredible amount of human resources and
+    energy from the foundation to fix things and normally much more than the
+    project is able to give back in the short term.
+    </p>
+
+    
+<p>
+    Incubation is a way to protect the ASF from the potential
+    negative impact of social problems happening inside the effort being
+    under incubation.
+    </p>
+
+    
+<p>
+    Projects under incubation can develop the community qualities that will
+    make them exit the incubation period, or can simply die out. In this
+    last case, the effort is simply cancelled or kept there in a limbo until
+    somebody else shows up some interest.
+    </p>
+
+    
+<p>
+    Incubated projects are to be considered not ready from a community
+    perspective. Importantly, this does *NOT* mean any judgement from a
+    technological perspective but only from a community perspective! This is
+    a community of infants that need mentoring by older communities to achieve
+    the long-term stability that is valued by both the ASF and by the users
+    who base their effort on the software the ASF produces.
+    </p>
+
+    
+<p>
+    The Cocoon community will guide these sub-projects through their
+    incubation phase. They leave incubation when they feel that they are
+    ready to defend their exit intentions when needed.
+    </p>
+   
+</body>
+</html>

Added: cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-incubation/meta.xml
URL: http://svn.apache.org/viewcvs/cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-incubation/meta.xml?rev=164967&view=auto
==============================================================================
--- cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-incubation/meta.xml (added)
+++ cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-incubation/meta.xml Wed Apr 27 03:07:09 2005
@@ -0,0 +1,9 @@
+<?xml version="1.0"?>
+<meta>
+  <authors>
+    <author contact="http://cocoon.apache.org">Cocoon Community</author>
+  </authors>
+  <legacy>
+    <original-filename>community/incubation.html</original-filename>
+  </legacy>
+</meta>

Added: cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-index/comments_en.xml
URL: http://svn.apache.org/viewcvs/cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-index/comments_en.xml?rev=164967&view=auto
==============================================================================
--- cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-index/comments_en.xml (added)
+++ cocoon/whiteboard/doc-repos/global/src/content/xdocs/OLD-index/comments_en.xml Wed Apr 27 03:07:09 2005
@@ -0,0 +1,3 @@
+<?xml version="1.0"?>
+<comments>
+</comments>



Mime
View raw message