Added: lenya/sandbox/pubs/docu/content/authoring/76b537c0-8730-11dc-ae46-9e7b5d14892d/en.1195221900856.bak
URL: http://svn.apache.org/viewvc/lenya/sandbox/pubs/docu/content/authoring/76b537c0-8730-11dc-ae46-9e7b5d14892d/en.1195221900856.bak?rev=595691&view=auto
==============================================================================
--- lenya/sandbox/pubs/docu/content/authoring/76b537c0-8730-11dc-ae46-9e7b5d14892d/en.1195221900856.bak (added)
+++ lenya/sandbox/pubs/docu/content/authoring/76b537c0-8730-11dc-ae46-9e7b5d14892d/en.1195221900856.bak Fri Nov 16 07:11:58 2007
@@ -0,0 +1,138 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!--
+ Copyright 2002-2006 The Apache Software Foundation
+
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+--><!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "http://forrest.apache.org/dtd/document-v20.dtd">
+
+<document>
+ <header>
+ <title>Notes for lenya.zones.apache.org.</title>
+ </header>
+ <body>
+ <section>
+ <title>Overview</title>
+ <p> The server <a href="ext:lenya-zone">lenya.zones.apache.org</a>
+ provides our testing and demonstration area. It is managed by Apache
+ Lenya committers. </p>
+ </section>
+ <section id="configuration">
+ <title>Configuration</title>
+ <warning> We are not finished setting up our zone server (better said
+ still in a very early stage), if something is not working it is maybe
+ because it is not set up yet. ;-) Besides the directory structure may
+ change. </warning>
+ <p> Bin files and site structure are stored in SVN at
+ <code>https://svn.apache.org/repos/asf/lenya/zone</code>. Please make
+ sure you have a local copy which you can edit. You should not edit our
+ zone files directly on the server. To update them just do <code>svn
+ update</code>. For more information about the scripts please read the
+ source code.</p>
+ <note>Till now we only had one user <code>lenya</code>. Further to
+ understand what is going on read the source code.</note>
+ <p> <strong>bin</strong> - svn-checkout@zone: /export/home/lenya/bin </p>
+ <dl>
+ <dt>killer</dt>
+ <dd>kill all processes containing specified strings.</dd>
+ <dt>lenya-for-forrest.sh</dt>
+ <dd>Will update, build clean, build and start the forrest docu instance
+ (not in use ATM)</dd>
+ <dt>mycrons.cron</dt>
+ <dd>Shows the currently configured schedule. If you change it, make
+ sure to as well apply it (see <a href="#tips">tips and tricks)</a>.</dd>
+ <dt>nightlies.sh</dt>
+ <dd>This script will build lenya trunk
+ http://lenya.zones.apache.org:9999/index.html and lenya-1.2.x
+ http://lenya.zones.apache.org:8888/index.html Further you can
+ invoke/prevent "svn update" and the building of cocoon/lenya. FIXME:
+ I will split this script apart for each lenya version.</dd>
+ <dt>setenv*.sh</dt>
+ <dd>set the environment (NOTE: Till now it is a non verified copy from
+ forrest)</dd>
+ </dl>
+ <p> <strong>htdocs</strong> - svn-checkout@zone:
+ /export/home/lenya/htdocs </p>
+ <p>Containing src and build of our zones website. Here you can find
+ various forrestbot configuration files (publish-website-preview.xml and
+ publish-zone.xml) which are deploying the zones site and the lenya
+ staging docu.</p>
+ <p>All files are owned in the group "other" so any one of us can
+ edit/update. Make sure that your 'umask' is set properly so that new
+ files have group write permissions. See the <a href="#admin-user">notes</a> about user administration. FIXME: Add a
+ proper group. </p>
+ </section>
+ <section id="software">
+ <title>Software</title>
+ <p> Global zone software is as described in <a href="http://www.apache.org/dev/solaris-zones.html">zone
+ administration</a>. </p>
+ <p> Various local software is installed in <code>/export/opt/</code> (not
+ managed with SVN) ... </p>
+ <p>Till now we have installed all additional software in <code>
+ /export/home/lenya/src</code>. They are mostly svn checkouts of lenya,
+ cocoon and forrest.</p>
+ <fixme author="thorsten">Add more information.</fixme>
+ </section>
+ <section id="admin">
+ <title>Administration</title>
+ <p> See the general notes for the <a href="http://www.apache.org/dev/solaris-zones.html">zone
+ administration</a>. </p>
+ <p> The project chair is the root user. Committers can ask on the dev
+ list to get a user account added or modified. </p>
+ <p> Follow Leo's config ideas at <a href="http://wiki.apache.org/gump/GumpZonesConfig">GumpZonesConfig</a>.
+ </p>
+ <p> FIXME: Start apache2 on boot (using new Solaris init.d replacement
+ called smf). At the moment we need to realise that it is down and
+ manually restart as per http://www.apache.org/dev/solaris-zones.html
+ Also it seems that /var/run/apache2 is wiped out on reboot, so need to
+ mkdir again. </p>
+ <section id="admin-user">
+ <title>User administration</title>
+ <p>After receiving your account, please be sure to configure it
+ properly.</p>
+ <p>See some notes at <a href="http://www.apache.org/dev/solaris-zones.html">zone
+ administration</a> and the general notes for <a href="http://www.apache.org/dev/new-committers-guide.html#shell">new
+ committers</a> (especially the part about 'umask'). </p>
+ <p> Look at the setup of some other users on our zone. </p>
+ </section>
+ <section id="tips">
+ <title>Tips and tricks</title>
+ <p>
+<strong>lenya user</strong> - Till now we have used only the user
+ <code>lenya</code> to start all scripts and manage the cronjobs.
+ Doing the following you are save to do your work.</p>
+ <source xml:space="preserve">su lenya
+Password: (like sended to you)</source>
+ <p>
+<strong>restarting services</strong> - You should not restart
+ manually the instances, it is better to use
+ <code>/export/home/lenya/bin/nightlies.sh</code>. If you do please store the pid in
+ <code>/export/home/lenya/bin</code> in one of the following files:</p>
+ <source xml:space="preserve">lenya-1_2.pid
+lenya-for-forrest.pid
+lenya-trunk.pid
+ </source>
+ <p>
+<strong>cron</strong> - The user <code>lenya</code> is owner of
+ all cron jobs running on zones. If you want to add another cron
+ please edit mycrons.cron (zone/bin) - follow the <a href="http://www.scrounge.org/linux/cron.html">useful
+ reference</a>. Then commit and ssh to the server:</p>
+ <source xml:space="preserve">ssh -l lenya lenya.zones.apache.org
+-bash-3.00$ cd bin/
+-bash-3.00$ svn up
+-bash-3.00$ crontab mycrons.cron #loads the actual cron jobs
+-bash-3.00$ crontab -l #check to see if it was loaded
+ </source>
+ </section>
+ </section>
+ </body>
+</document>
Added: lenya/sandbox/pubs/docu/content/authoring/76b537c0-8730-11dc-ae46-9e7b5d14892d/en.meta.1195221900856.bak
URL: http://svn.apache.org/viewvc/lenya/sandbox/pubs/docu/content/authoring/76b537c0-8730-11dc-ae46-9e7b5d14892d/en.meta.1195221900856.bak?rev=595691&view=auto
==============================================================================
--- lenya/sandbox/pubs/docu/content/authoring/76b537c0-8730-11dc-ae46-9e7b5d14892d/en.meta.1195221900856.bak (added)
+++ lenya/sandbox/pubs/docu/content/authoring/76b537c0-8730-11dc-ae46-9e7b5d14892d/en.meta.1195221900856.bak Fri Nov 16 07:11:58 2007
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<metadata xmlns="http://apache.org/lenya/metadata/1.0">
+<element-set namespace="http://purl.org/dc/elements/1.1/">
+<element key="title">
+<value>Zone notes</value>
+</element>
+</element-set>
+<element-set namespace="http://apache.org/lenya/metadata/document/1.0">
+<element key="extension">
+<value>xml</value>
+</element>
+<element key="mimeType">
+<value>application/xml</value>
+</element>
+<element key="resourceType">
+<value>forrestDocument20</value>
+</element>
+<element key="contentType">
+<value>xml</value>
+</element>
+</element-set>
+</metadata>
Modified: lenya/sandbox/pubs/docu/content/authoring/76b537c0-8730-11dc-ae46-9e7b5d14892d/en.rcml
URL: http://svn.apache.org/viewvc/lenya/sandbox/pubs/docu/content/authoring/76b537c0-8730-11dc-ae46-9e7b5d14892d/en.rcml?rev=595691&r1=595690&r2=595691&view=diff
==============================================================================
--- lenya/sandbox/pubs/docu/content/authoring/76b537c0-8730-11dc-ae46-9e7b5d14892d/en.rcml (original)
+++ lenya/sandbox/pubs/docu/content/authoring/76b537c0-8730-11dc-ae46-9e7b5d14892d/en.rcml Fri Nov 16 07:11:58 2007
@@ -1,5 +1,7 @@
<?xml version="1.0" encoding="UTF-8"?>
<XPSRevisionControl xmlns="">
+<CheckIn backup="true" identity="lenya" session="fde084c0-944b-11dc-8f2e-e6c0ff9903ab" time="1195221900856" version="3"/>
+<CheckOut identity="lenya" session="fde084c0-944b-11dc-8f2e-e6c0ff9903ab" time="1195221891026"/>
<CheckIn backup="true" identity="lenya" session="1f12dc80-8860-11dc-ba66-cfbbb816bd0d" time="1193910787453" version="2"/>
<CheckOut identity="lenya" session="1f12dc80-8860-11dc-ba66-cfbbb816bd0d" time="1193910771459"/>
<CheckIn backup="true" identity="lenya" session="60798970-8730-11dc-ae46-9e7b5d14892d" time="1193781621000" version="1"/>
Added: lenya/sandbox/pubs/docu/content/authoring/7805fab0-8730-11dc-ae46-9e7b5d14892d/en.1195221899906.bak
URL: http://svn.apache.org/viewvc/lenya/sandbox/pubs/docu/content/authoring/7805fab0-8730-11dc-ae46-9e7b5d14892d/en.1195221899906.bak?rev=595691&view=auto
==============================================================================
--- lenya/sandbox/pubs/docu/content/authoring/7805fab0-8730-11dc-ae46-9e7b5d14892d/en.1195221899906.bak (added)
+++ lenya/sandbox/pubs/docu/content/authoring/7805fab0-8730-11dc-ae46-9e7b5d14892d/en.1195221899906.bak Fri Nov 16 07:11:58 2007
@@ -0,0 +1,99 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!--
+ Copyright 1999-2004 The Apache Software Foundation
+
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+<!-- $Id: license.xml 55543 2004-10-26 00:14:59Z gregor $ --><!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "http://forrest.apache.org/dtd/document-v20.dtd">
+
+<document>
+ <header>
+ <title>Resolution for the creation of the Apache Lenya Project</title>
+ </header>
+ <body>
+<p>
+WHEREAS, the Board of Directors deems it to be in the best
+interests of the Foundation and consistent with the
+Foundation's purpose to establish a Project Management
+Committee charged with the creation and maintenance of
+open-source software related to content management, for
+distribution at no charge to the public.
+</p>
+<p>
+NOW, THEREFORE, BE IT RESOLVED, that a Project Management
+Committee (PMC), to be known as the "Apache Lenya PMC", be and hereby
+is established pursuant to Bylaws of the Foundation; and be it
+further
+</p>
+<p>
+RESOLVED, that the Apache Lenya PMC be and hereby is responsible for
+the creation and maintenance of software related to content
+management, based on software licensed to the Foundation;
+and be it further
+</p>
+<p>
+RESOLVED, that the office of "Vice President, Apache Lenya" be and
+hereby is created, the person holding such office to serve at
+the direction of the Board of Directors as the chair of the
+Apache Lenya PMC, and to have primary responsibility for management of
+the projects within the scope of responsibility of the Apache Lenya
+PMC; and be it further
+</p>
+<p>
+RESOLVED, that the persons listed immediately below be and
+hereby are appointed to serve as the initial members of the
+Apache Lenya PMC:
+</p>
+<ul>
+ <li>Edith Chevier ([email protected])</li>
+ <li>Dale Christ ([email protected])</li>
+ <li>Christian Egli ([email protected])</li>
+ <li>Andreas Hartmann ([email protected])</li>
+ <li>Rolf Kulemann ([email protected])</li>
+ <li>Stefano Mazzocchi ([email protected])</li>
+ <li>Steven Noels ([email protected])</li>
+ <li>Gregor J. Rothfuss ([email protected])</li>
+ <li>Thorsten Scherler ([email protected])</li>
+ <li>Michael Wechner ([email protected])</li>
+</ul>
+<p>
+NOW, THEREFORE, BE IT FURTHER RESOLVED, that
+</p>
+<p>
+Rolf Kulemann
+</p>
+<p>
+ be and hereby is appointed to the office of Vice President, Apache Lenya,
+to serve in accordance with and subject to the direction of the
+Board of Directors and the Bylaws of the Foundation until
+death, resignation, retirement, removal or disqualification, or
+until a successor is appointed; and be it further
+</p>
+<p>
+RESOLVED, that the initial Apache Lenya PMC be and hereby is tasked
+with the creation of a set of bylaws intended to encourage open
+development and increased participation in the Lenya Project;
+and be it further
+</p>
+<p>
+RESOLVED, that the initial Apache Lenya PMC be and hereby is tasked
+with the migration and rationalization of the incubating PMC
+Apache Lenya project; and be it further
+</p>
+<p>
+RESOLVED, that all responsibility pertaining to the incubating
+Apache Lenya project encumbered upon the incubator PMC
+be hereafter discharged.
+</p>
+ </body>
+</document>
Added: lenya/sandbox/pubs/docu/content/authoring/7805fab0-8730-11dc-ae46-9e7b5d14892d/en.meta.1195221899906.bak
URL: http://svn.apache.org/viewvc/lenya/sandbox/pubs/docu/content/authoring/7805fab0-8730-11dc-ae46-9e7b5d14892d/en.meta.1195221899906.bak?rev=595691&view=auto
==============================================================================
--- lenya/sandbox/pubs/docu/content/authoring/7805fab0-8730-11dc-ae46-9e7b5d14892d/en.meta.1195221899906.bak (added)
+++ lenya/sandbox/pubs/docu/content/authoring/7805fab0-8730-11dc-ae46-9e7b5d14892d/en.meta.1195221899906.bak Fri Nov 16 07:11:58 2007
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<metadata xmlns="http://apache.org/lenya/metadata/1.0">
+<element-set namespace="http://purl.org/dc/elements/1.1/">
+<element key="title">
+<value>Resolution</value>
+</element>
+</element-set>
+<element-set namespace="http://apache.org/lenya/metadata/document/1.0">
+<element key="extension">
+<value>xml</value>
+</element>
+<element key="mimeType">
+<value>application/xml</value>
+</element>
+<element key="resourceType">
+<value>forrestDocument20</value>
+</element>
+<element key="contentType">
+<value>xml</value>
+</element>
+</element-set>
+</metadata>
Modified: lenya/sandbox/pubs/docu/content/authoring/7805fab0-8730-11dc-ae46-9e7b5d14892d/en.rcml
URL: http://svn.apache.org/viewvc/lenya/sandbox/pubs/docu/content/authoring/7805fab0-8730-11dc-ae46-9e7b5d14892d/en.rcml?rev=595691&r1=595690&r2=595691&view=diff
==============================================================================
--- lenya/sandbox/pubs/docu/content/authoring/7805fab0-8730-11dc-ae46-9e7b5d14892d/en.rcml (original)
+++ lenya/sandbox/pubs/docu/content/authoring/7805fab0-8730-11dc-ae46-9e7b5d14892d/en.rcml Fri Nov 16 07:11:58 2007
@@ -1,5 +1,7 @@
<?xml version="1.0" encoding="UTF-8"?>
<XPSRevisionControl xmlns="">
+<CheckIn backup="true" identity="lenya" session="fde084c0-944b-11dc-8f2e-e6c0ff9903ab" time="1195221899906" version="3"/>
+<CheckOut identity="lenya" session="fde084c0-944b-11dc-8f2e-e6c0ff9903ab" time="1195221890019"/>
<CheckIn backup="true" identity="lenya" session="1f12dc80-8860-11dc-ba66-cfbbb816bd0d" time="1193910793767" version="2"/>
<CheckOut identity="lenya" session="1f12dc80-8860-11dc-ba66-cfbbb816bd0d" time="1193910766323"/>
<CheckIn backup="true" identity="lenya" session="60798970-8730-11dc-ae46-9e7b5d14892d" time="1193781625400" version="1"/>
Added: lenya/sandbox/pubs/docu/content/authoring/79536240-8730-11dc-ae46-9e7b5d14892d/en.1195221899244.bak
URL: http://svn.apache.org/viewvc/lenya/sandbox/pubs/docu/content/authoring/79536240-8730-11dc-ae46-9e7b5d14892d/en.1195221899244.bak?rev=595691&view=auto
==============================================================================
--- lenya/sandbox/pubs/docu/content/authoring/79536240-8730-11dc-ae46-9e7b5d14892d/en.1195221899244.bak (added)
+++ lenya/sandbox/pubs/docu/content/authoring/79536240-8730-11dc-ae46-9e7b5d14892d/en.1195221899244.bak Fri Nov 16 07:11:58 2007
@@ -0,0 +1,50 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!--
+ Copyright 1999-2004 The Apache Software Foundation
+
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+<!-- $Id: license.xml 55543 2004-10-26 00:14:59Z gregor $ --><!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "http://forrest.apache.org/dtd/document-v20.dtd">
+
+<document>
+ <header>
+ <title>Apache Lenya Project Charter</title>
+
+
+
+ </header>
+ <body>
+<p>
+The Apache Lenya Project is a community project developing open source content management solutions.
+</p>
+<p>
+With strong foundations in XML-based server-side web application frameworks,
+like Apache Cocoon, the Apache Lenya Project consists of a group of people
+that share common values on collaboration-intensive and community-based
+quality open source development.
+</p>
+<p>
+</p>
+<p>
+The Apache Lenya Project is proud to share these values with its parent organization:
+The Apache Software Foundation. The mission of the Apache Lenya Project project is:</p>
+<p>
+</p>
+<ul>
+ <li>to provide commercial-quality, high-performance, well-tested,
+standards-based XML editing environments that are developed in an open and collaborative fashion.</li>
+ <li>to add user-oriented functionality on top of the Cocoon framework and other Apache projects.</li>
+ <li>to advance the state of the art of content management and structured text editing.</li>
+</ul>
+ </body>
+</document>
Added: lenya/sandbox/pubs/docu/content/authoring/79536240-8730-11dc-ae46-9e7b5d14892d/en.meta.1195221899244.bak
URL: http://svn.apache.org/viewvc/lenya/sandbox/pubs/docu/content/authoring/79536240-8730-11dc-ae46-9e7b5d14892d/en.meta.1195221899244.bak?rev=595691&view=auto
==============================================================================
--- lenya/sandbox/pubs/docu/content/authoring/79536240-8730-11dc-ae46-9e7b5d14892d/en.meta.1195221899244.bak (added)
+++ lenya/sandbox/pubs/docu/content/authoring/79536240-8730-11dc-ae46-9e7b5d14892d/en.meta.1195221899244.bak Fri Nov 16 07:11:58 2007
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<metadata xmlns="http://apache.org/lenya/metadata/1.0">
+<element-set namespace="http://purl.org/dc/elements/1.1/">
+<element key="title">
+<value>Charter</value>
+</element>
+</element-set>
+<element-set namespace="http://apache.org/lenya/metadata/document/1.0">
+<element key="extension">
+<value>xml</value>
+</element>
+<element key="mimeType">
+<value>application/xml</value>
+</element>
+<element key="resourceType">
+<value>forrestDocument20</value>
+</element>
+<element key="contentType">
+<value>xml</value>
+</element>
+</element-set>
+</metadata>
Modified: lenya/sandbox/pubs/docu/content/authoring/79536240-8730-11dc-ae46-9e7b5d14892d/en.rcml
URL: http://svn.apache.org/viewvc/lenya/sandbox/pubs/docu/content/authoring/79536240-8730-11dc-ae46-9e7b5d14892d/en.rcml?rev=595691&r1=595690&r2=595691&view=diff
==============================================================================
--- lenya/sandbox/pubs/docu/content/authoring/79536240-8730-11dc-ae46-9e7b5d14892d/en.rcml (original)
+++ lenya/sandbox/pubs/docu/content/authoring/79536240-8730-11dc-ae46-9e7b5d14892d/en.rcml Fri Nov 16 07:11:58 2007
@@ -1,5 +1,7 @@
<?xml version="1.0" encoding="UTF-8"?>
<XPSRevisionControl xmlns="">
+<CheckIn backup="true" identity="lenya" session="fde084c0-944b-11dc-8f2e-e6c0ff9903ab" time="1195221899244" version="3"/>
+<CheckOut identity="lenya" session="fde084c0-944b-11dc-8f2e-e6c0ff9903ab" time="1195221888822"/>
<CheckIn backup="true" identity="lenya" session="1f12dc80-8860-11dc-ba66-cfbbb816bd0d" time="1193910789958" version="2"/>
<CheckOut identity="lenya" session="1f12dc80-8860-11dc-ba66-cfbbb816bd0d" time="1193910763477"/>
<CheckIn backup="true" identity="lenya" session="60798970-8730-11dc-ae46-9e7b5d14892d" time="1193781621900" version="1"/>
Added: lenya/sandbox/pubs/docu/content/authoring/7af356a0-8730-11dc-ae46-9e7b5d14892d/en.1195221911726.bak
URL: http://svn.apache.org/viewvc/lenya/sandbox/pubs/docu/content/authoring/7af356a0-8730-11dc-ae46-9e7b5d14892d/en.1195221911726.bak?rev=595691&view=auto
==============================================================================
--- lenya/sandbox/pubs/docu/content/authoring/7af356a0-8730-11dc-ae46-9e7b5d14892d/en.1195221911726.bak (added)
+++ lenya/sandbox/pubs/docu/content/authoring/7af356a0-8730-11dc-ae46-9e7b5d14892d/en.1195221911726.bak Fri Nov 16 07:11:58 2007
@@ -0,0 +1,806 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!--
+Copyright 2002-2007 The Apache Software Foundation or its licensors,
+as applicable.
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.
+--><!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "http://forrest.apache.org/dtd/document-v13.dtd">
+
+<document>
+<header>
+ <title>Apache Lenya project guidelines</title>
+</header>
+<body>
+ <p>
+ This document provides the guidelines under which the Apache Lenya
+ project operates. It defines the roles and responsibilities, who may vote,
+ how voting works, how conflicts are resolved, etc.
+ Apache Lenya is a project of The Apache Software Foundation
+ (<link href="http://www.apache.org/foundation/">ASF</link>) which is a
+ non-profit corporation. As with all such organisations there are some
+ procedures to be followed.
+ The ASF website explains the
+ operation and background of the ASF. These project guidelines supplement that
+ ASF documentation. Normally these guidelines are not needed - the project
+ just gets on with its day-to-day operation - but they enable
+ all people to understand how the project operates.
+ </p>
+
+ <section id="mission">
+ <title>The mission of Apache Lenya</title>
+ <p>
+ The generation of open source content management solutions,
+ maintaining a separation of content and presentation.
+ </p>
+ </section>
+
+ <section id="way">
+ <title>Open development</title>
+ <p>
+ Lenya is typical of Apache projects, in that it operates under a set of
+ principles that encourage open development. There is no clear definition
+ (perhaps that is part of it) and it is ever-evolving. Each ASF project is different
+ in its own way - there is healthy diversity rather than uniformity across all projects.
+ The main principles are to facilitate open collaborative development, with respect for
+ others; to ensure that there is a healthy community (even to give community issues
+ higher priority than code issues); to use a consensus-based approach;
+ to ensure that each
+ <link href="#contribution">contributor</link> is recognised and
+ feels a productive part of the community; to encourage diversity; to make the project a nice place to be.
+ </p>
+ <p>
+ Each project, as part of the
+ <link href="http://www.apache.org/foundation/records/minutes/2004/board_minutes_2004_05_26.txt">resolution</link>
+ that formed its Project Management Committee (<link href="#pmc">PMC</link>),
+ creates its set of project guidelines intended to encourage open development and
+ increased participation. These facilitate the project to conduct its main charge,
+ which is the creation and maintenance of open-source software for distribution at no
+ charge to the public with the purpose of its
+ <link href="#mission">mission</link>.
+ </p>
+ <p>
+ For more information about the way that Apache projects operate, please refer to
+ the
+ <link href="http://www.apache.org/foundation/">ASF foundation</link>
+ and
+ <link href="http://www.apache.org/dev/">ASF developer</link> sections
+ of the ASF website, including the
+ <link href="http://www.apache.org/foundation/bylaws.html">ASF ByLaws</link>
+ and the
+ <link href="ext:how-it-works">How it works</link> document,
+ the
+ <link href="http://www.apache.org/foundation/faq.html">FAQs</link>
+ about the Foundation, and the
+ <link href="http://incubator.apache.org/">Incubator project</link>.
+ </p>
+ </section>
+
+ <section id="roles">
+ <title>Roles and responsibilities</title>
+ <p>The meritocracy enables various roles as defined in the
+ <link href="ext:how-it-works">How it works</link> document.
+ </p>
+ <p>
+ <link href="http://www.apache.org/foundation/how-it-works.html#users">user</link> |
+ <link href="http://www.apache.org/foundation/how-it-works.html#developers">developer</link> |
+ <link href="http://www.apache.org/foundation/how-it-works.html#committers">committer</link> |
+ <link href="http://www.apache.org/foundation/how-it-works.html#pmc-members">PMC member</link> |
+ <link href="http://www.apache.org/foundation/how-it-works.html#asf-members">ASF member</link>
+ </p>
+ <p>The current Apache Lenya committers and PMC members are
+ <link href="lenya-document:699ba420-8730-11dc-ae46-9e7b5d14892d">listed</link>. The Lenya PMC has additionally granted commit access
+ to committers from its sister projects Apache Cocoon and Apache Forrest.
+ </p>
+ </section>
+
+ <section id="pmc">
+ <title>Project Management Committee (PMC)</title>
+ <p>The Apache Lenya project was established in spring 2003 and became a
+ top-level project in September 2004.
+ The Project Management Committee (PMC) was created by a
+ <link href="http://www.apache.org/foundation/records/minutes/2004/board_minutes_2004_09_22.txt">resolution</link>
+ of the board of the Apache Software Foundation.
+ See explanation of the role of the PMC in that resolution and also the
+ <link href="http://www.apache.org/foundation/bylaws.html">ASF Bylaws</link>
+ and
+ <link href="http://www.apache.org/foundation/how-it-works.html#pmc">How-it-works</link>.
+ </p>
+ <p>The responsibilities of the PMC include:</p>
+ <ul>
+ <li>Be familiar with these project guidelines, and the
+ ASF Bylaws, and with the ASF documentation and procedures
+ in general.</li>
+ <li>Keep oversight of the commit log messages and ensure that
+ the codebase does not have copyright and license issues.</li>
+ <li>Resolve license disputes regarding products of the project,
+ including other supporting software that is re-distributed.</li>
+ <li>Decide what is distributed as products of the project.
+ In particular all releases must be approved by the PMC.</li>
+ <li>Guide the direction of the project.</li>
+ <li>Strive for and help to facilitate a harmonious productive community.</li>
+ <li>Nominate new PMC members and committers.</li>
+ <li>Maintain the project's shared resources, including the
+ codebase repository, mailing lists, websites.</li>
+ <li>Speak on behalf of the project.</li>
+ <li>Maintain these and other guidelines of the project.</li>
+ </ul>
+ <p>
+ The PMC does have a private mailing list on which it can discuss
+ certain issues. However this list is rarely used and every effort
+ is made to conduct all discussion on the public mailing lists.
+ </p>
+
+ <p>
+ Membership of the PMC is by invitation only and must receive
+ consensus approval of the active PMC members.
+ </p>
+ <p>
+ A PMC member is considered
+ "emeritus" by their own declaration or by not contributing in
+ any form to the project for over six months. An emeritus member may
+ request reinstatement to the PMC. Such reinstatement is subject to
+ consensus approval of the active PMC members. Membership of the PMC can be
+ revoked by unanimous consensus of all active PMC members (other than
+ the member in question).
+ </p>
+
+ <p>
+ The chair of the PMC is appointed by the Board and is an officer of
+ the ASF (Vice President). The chair has primary responsibility to the
+ Board, and has the power to establish rules and procedures for the
+ day-to-day management of the communities for which the PMC is
+ responsible, including the composition of the PMC itself.
+ The chair reports to the board every three months about the status of the
+ project. The PMC may consider the position of PMC chair annually and
+ may recommend a new chair to the board.
+ Ultimately, however, it is the board's responsibility who it chooses
+ to appoint as the PMC chair.
+ See further explanation of the role of the chair in the
+ <link href="http://www.apache.org/foundation/bylaws.html">ASF Bylaws</link>
+ and the
+ <link href="http://www.apache.org/dev/pmc.html#chair">PMC FAQ</link>
+ </p>
+
+ <section id="report">
+ <title>Quarterly reports to ASF Board</title>
+ <p>
+ Every three months, it is the responsibility of our PMC chair to
+ send a report to the ASF Board. This is mainly concerned with the
+ status of our community, but can also include the technical progress.
+ Further details are in the "committers" SVN in the /board/ directory.
+ </p>
+ <p>
+ The minutes are available for each
+ <link href="http://www.apache.org/foundation/board/calendar.html">
+ board meeting</link>. Our reporting schedule is: Feb, May, Aug, Nov.
+ </p>
+ </section>
+
+ <section id="elect">
+ <title>Electing new committers and PMC members</title>
+ <p> We conduct committer/PMC member proposals on the private PMC mailing list to enable
+ a frank discussion. The vote for committership will be conducted on the lenya dev
+ list, if no concerns are aired prior on the private PMC list. This is out of for
+ historical reasons. We inherited that from cocoon: it shows people that we
+ appreciate them in a ceremonial way. The vote for a new PMC member however will be
+ conducted on the private list and later announced on the dev list. </p>
+ </section>
+ </section>
+
+ <section id="decision">
+ <title>Decision making</title>
+ <p>
+ Different types of decisions require different
+ forms of approval. For example, the previous section describes
+ several decisions which require "consensus approval". This
+ section defines how voting is performed, the types of approval, and which
+ types of decision require which type of approval.
+ </p>
+
+ <p>
+ Most day-to-day operations do not require explicit voting - just get on
+ and do the work. See the "Lazy approval" type described below.
+ </p>
+
+ <section id="voting">
+ <title>Voting</title>
+ <p>
+ Certain actions and decisions regarding the project are made by votes
+ on the project development mailing list. Where necessary,
+ PMC voting may take place on the private PMC mailing list.
+ </p>
+ <p>
+ Votes are clearly indicated by subject line starting with [VOTE].
+ Discussion and proposal should have happened prior to the vote.
+ Voting is carried out by replying to the vote mail.
+ See <link href="#procedure">voting procedure</link> below.
+ Votes are expressed using one of the following symbols:
+ </p>
+
+ <table>
+ <tr>
+ <td colspan="1" rowspan="1">
+<strong>+1</strong>
+</td>
+ <td colspan="1" rowspan="1">
+ "Yes," "Agree," or "the action should be
+ performed." In general, this vote also indicates a willingness
+ on the behalf of the voter to assist with "making it happen".
+ </td>
+ </tr>
+
+ <tr>
+ <td colspan="1" rowspan="1">
+<strong>+0</strong>
+</td>
+ <td colspan="1" rowspan="1">
+ This vote indicates a willingness for the action under
+ consideration to go ahead. The voter, however will not be able
+ to help.
+ </td>
+ </tr>
+
+ <tr>
+ <td colspan="1" rowspan="1">
+<strong>-0</strong>
+</td>
+ <td colspan="1" rowspan="1">
+ This vote indicates that the voter does not, in general, agree with
+ the proposed action but is not concerned enough to prevent the
+ action going ahead.
+ </td>
+ </tr>
+
+ <tr>
+ <td colspan="1" rowspan="1">
+<strong>-1</strong>
+</td>
+ <td colspan="1" rowspan="1">
+ This is a negative vote. On issues where consensus is required,
+ this vote counts as a <link href="#veto">veto</link>.
+ All vetoes must
+ contain an explanation of why the veto is appropriate. Vetoes with
+ no explanation are void. It may also be appropriate for a -1 vote
+ to include an alternative course of action.
+ </td>
+ </tr>
+
+ <tr>
+ <td colspan="1" rowspan="1">
+<strong>abstain</strong>
+</td>
+ <td colspan="1" rowspan="1">People can abstain from voting. They can either remain
+ silent or express their reason.
+ </td>
+ </tr>
+ </table>
+
+ <p>
+ All participants in the project are encouraged to show their
+ preference for a particular action by voting. When the votes are
+ tallied, only the votes of PMC members are binding. Non-binding
+ votes are still useful to enable everyone to understand the
+ perception of an action by the wider community.
+ </p>
+
+ <p>
+ Voting can also be applied to changes made to the project codebase. These
+ typically take the form of a veto (-1) in reply to the commit message
+ sent when the commit is made.
+ </p>
+ </section>
+
+ <section id="approvals">
+ <title>Types of approval</title>
+ <p>
+ Different actions require different types of approval:
+ </p>
+
+ <table>
+ <tr>
+ <td colspan="1" rowspan="1">
+<strong>Consensus approval</strong>
+</td>
+ <td colspan="1" rowspan="1">
+ Consensus approval requires 3 binding +1 votes and no binding vetoes.
+ </td>
+ </tr>
+
+ <tr>
+ <td colspan="1" rowspan="1">
+<strong>Lazy majority</strong>
+</td>
+ <td colspan="1" rowspan="1">
+ A lazy majority vote requires 3 binding +1 votes and more binding +1
+ votes than -1 votes.
+ </td>
+ </tr>
+
+ <tr>
+ <td colspan="1" rowspan="1">
+<strong>Lazy approval</strong>
+</td>
+ <td colspan="1" rowspan="1">
+ An action with lazy approval is implicitly allowed unless a -1 vote
+ is received, at which time, depending on the type of action, either
+ lazy majority or consensus approval must be obtained.
+ </td>
+ </tr>
+
+ <tr>
+ <td colspan="1" rowspan="1">
+<strong>2/3 majority</strong>
+</td>
+ <td colspan="1" rowspan="1">
+ Some actions require a 2/3 majority of active PMC members.
+ Such actions typically affect the foundation
+ of the project (e.g. adopting a new codebase to replace an existing
+ product). The higher threshold is designed to ensure such changes
+ are strongly supported. To pass this vote requires at least 2/3 of
+ binding vote holders to vote +1
+ </td>
+ </tr>
+
+ <tr>
+ <td colspan="1" rowspan="1">
+<strong>Unanimous consensus</strong>
+</td>
+ <td colspan="1" rowspan="1">
+ All voters with binding votes must vote and there
+ can be no binding vetoes (-1).
+ </td>
+ </tr>
+ </table>
+ </section>
+
+ <section id="veto">
+ <title>Vetoes</title>
+ <p>
+ A valid veto cannot be over-ruled, it can only be withdrawn by its issuer.
+ Any veto must be accompanied by reasoning and be prepared to defend it.
+ </p>
+
+ <p>
+ The validity of a veto, if challenged, can be confirmed by anyone who
+ has a binding vote. This does not necessarily signify agreement with the
+ veto - merely that the veto is valid. In case of disputes about whether
+ a veto is valid, then opinion of the PMC chair is final.
+ </p>
+
+ <p>
+ If you disagree with a valid veto, then you must engage the person
+ casting the veto to further discuss the issues. The vetoer is obliged
+ to vote early and to then work with the community to resolve
+ the matter.
+ </p>
+
+ <p>
+ If a veto is not withdrawn, the action that has been vetoed must
+ be reversed in a timely manner.
+ </p>
+ </section>
+
+ <section id="actions">
+ <title>Actions</title>
+ <p>
+ This section describes the various actions which are undertaken within
+ the project, the corresponding approval required for that action, and
+ those who have binding votes over the action.
+ </p>
+
+ <table>
+ <tr>
+ <th colspan="1" rowspan="1">Action</th>
+ <th colspan="1" rowspan="1">Description</th>
+ <th colspan="1" rowspan="1">Approval</th>
+ <th colspan="1" rowspan="1">Binding Votes</th>
+ </tr>
+ <tr>
+ <td colspan="1" rowspan="1">
+<strong>Code change</strong>
+</td>
+ <td colspan="1" rowspan="1">
+ A change made to a codebase of the project by a committer.
+ This includes source code, documentation, website content, etc.
+ </td>
+ <td colspan="1" rowspan="1">
+ Lazy approval for trunk, lazy majority for the release branch.
+ </td>
+ <td colspan="1" rowspan="1">
+ Active PMC members
+ </td>
+ </tr>
+ <tr>
+ <td colspan="1" rowspan="1">
+<strong>Opening / Closing a branch</strong>
+</td>
+ <td colspan="1" rowspan="1">
+ When a commiter wants to open a new branch in SVN, or close an existing branch, a vote
+ is required.
+ </td>
+ <td colspan="1" rowspan="1">
+ Lazy majority
+ </td>
+ <td colspan="1" rowspan="1">
+ Active PMC members
+ </td>
+ </tr>
+ <tr>
+ <td colspan="1" rowspan="1">
+<strong>Release plan</strong>
+</td>
+ <td colspan="1" rowspan="1">
+ Defines the timetable and actions for a release.
+ </td>
+ <td colspan="1" rowspan="1">
+ Lazy majority
+ </td>
+ <td colspan="1" rowspan="1">
+ Active PMC members
+ </td>
+ </tr>
+ <tr>
+ <td colspan="1" rowspan="1">
+<strong>Product release</strong>
+</td>
+ <td colspan="1" rowspan="1">
+ When a release of one of the project's products is ready, a vote is
+ required to accept the release as an official release of the
+ project.
+ </td>
+ <td colspan="1" rowspan="1">
+ Lazy majority
+ </td>
+ <td colspan="1" rowspan="1">
+ Active PMC members
+ </td>
+ </tr>
+ <tr>
+ <td colspan="1" rowspan="1">
+<strong>Adoption of new codebase</strong>
+</td>
+ <td colspan="1" rowspan="1">
+ When the codebase for an existing, released product is to be
+ replaced with an alternative codebase. If such a vote fails to
+ gain approval, the existing code base will continue.
+ This also covers the creation of new sub-projects
+ within the project.
+ </td>
+ <td colspan="1" rowspan="1">
+ 2/3 majority
+ </td>
+ <td colspan="1" rowspan="1">
+ Active PMC members
+ </td>
+ </tr>
+ <tr>
+ <td colspan="1" rowspan="1">
+<strong>New committer</strong>
+</td>
+ <td colspan="1" rowspan="1">
+ When a new committer is proposed for the project.
+ </td>
+ <td colspan="1" rowspan="1">
+ Consensus approval
+ </td>
+ <td colspan="1" rowspan="1">
+ Active PMC members
+ </td>
+ </tr>
+ <tr>
+ <td colspan="1" rowspan="1">
+<strong>New PMC member</strong>
+</td>
+ <td colspan="1" rowspan="1">
+ When a new member is proposed for the PMC.
+ </td>
+ <td colspan="1" rowspan="1">
+ Consensus approval
+ </td>
+ <td colspan="1" rowspan="1">
+ Active PMC members
+ </td>
+ </tr>
+ <tr>
+ <td colspan="1" rowspan="1">
+<strong>Reinstate emeritus member</strong>
+</td>
+ <td colspan="1" rowspan="1">
+ An emeritus PMC member can be reinstated.
+ </td>
+ <td colspan="1" rowspan="1">
+ Consensus approval
+ </td>
+ <td colspan="1" rowspan="1">
+ Active PMC members (excluding the member in question)
+ </td>
+ </tr>
+ <tr>
+ <td colspan="1" rowspan="1">
+<strong>Committer removal</strong>
+</td>
+ <td colspan="1" rowspan="1">
+ When removal of commit privileges is sought.
+ </td>
+ <td colspan="1" rowspan="1">
+ Unanimous consensus
+ </td>
+ <td colspan="1" rowspan="1">
+ Active PMC members (excluding the committer in question if a
+ member of the PMC)
+ </td>
+ </tr>
+ <tr>
+ <td colspan="1" rowspan="1">
+<strong>PMC member removal</strong>
+</td>
+ <td colspan="1" rowspan="1">
+ When removal of a PMC member is sought.
+ See also section 6.5 of the ASF Bylaws whereby the ASF Board may
+ remove a PMC member.
+ </td>
+ <td colspan="1" rowspan="1">
+ Unanimous consensus
+ </td>
+ <td colspan="1" rowspan="1">
+ Active PMC members (excluding the member in question)
+ </td>
+ </tr>
+ </table>
+ </section>
+
+ <section id="timeframe">
+ <title>Voting timeframes</title>
+ <p>
+ Votes are normally open for a period of one week to allow all active voters
+ time to consider the vote. If the vote has not achieved a quorum,
+ then it can be extended for another week. If still no quorum, then
+ the vote fails, and would need to be raised again later.
+ Votes relating to code changes are not subject to a strict timetable,
+ but should be made as timely as possible.
+ </p>
+ </section>
+
+ <section id="procedure">
+ <title>Voting procedure</title>
+ <p>
+ Discussion about the topic would have already happened in a [Proposal]
+ email thread to express the issues and opinions. The [Vote] thread is
+ to ratify the proposal.
+ </p>
+ <p>
+ The instigator sends the Vote email to the dev mailing list.
+ Describe the issue with no ambiguity and in a positive sense.
+ Define the date and time for the end of the vote period.
+ </p>
+ <p>
+ Votes are expressed by replying email using the
+ <link href="#voting">voting symbols</link> defined above.
+ Voters can change their vote during the timeframe.
+ At the end of the vote period, the instigator tallies the number of
+ final votes and reports the results.
+ </p>
+ </section>
+
+ <section id="ultimatum">
+ <title>Ultimatum and breakdown</title>
+ <p>
+ For breakdown situations and those requiring unanimous consensus,
+ if this consensus cannot be reached within the extended timeframe,
+ then the Board expects the chair to act as the officer of the
+ Foundation and make the ultimate decision.
+ </p>
+ </section>
+ </section>
+
+ <section id="communication">
+ <title>Communication channels</title>
+ <p>
+ The primary mechanism for communication is the mailing lists.
+ Anyone can participate, no matter what their time zone.
+ A reliable searchable archive of past discussion is built.
+ Oversight is enabled. Many eyes ensures that the project evolves
+ in a consistent direction.
+ </p>
+ <p>
+ All decisions are made on the "dev" mailing list.
+ </p>
+ <p>
+ The main channel for user support is the "user" mailing list.
+ As is usual with mailing lists, be prepared to wait for an answer.
+ </p>
+ <p>
+ Occasionally we will use other communication channels such as IRC.
+ These are used only for a specific purpose and are not permanently
+ available. This policy ensures that solutions are available in the
+ mailing list archives and enables people to respond at whatever time
+ that they choose. Permanent IRC channels are poor from a community-building
+ point-of-view, as they tend to create time-zone based cliques.
+ So we don't.
+ </p>
+ <p>
+ Similarly, private discussions are discouraged. The rest of the community
+ would not benefit from the understanding that is developed.
+ Off-list discussions put too much load on overworked volunteers.
+ </p>
+ </section>
+
+ <section id="code">
+ <title>Code management</title>
+
+ <p>Development on the Lenya codebase happens on the trunk, unless a vote to create a branch
+ has passed. Experimental code not immediately intended for merging into trunk may
+ be commited to the sandbox. In order to prevent a code graveyard, sandbox contents will
+ be reviewed every 6 months and either merged into trunk, promoted to their own top-level directory,
+ or deleted. At any one time, the Lenya project maintains one release branch. At appropriate
+ times, the Lenya project may cut a new release branch from trunk, and retire the previous one.
+ Old release branches are kept in SVN, but are clearly marked as unmaintained both in SVN and on the web site.
+ </p>
+
+ <p>
+ The term "patch" has two meanings: Developers provide a set of changes
+ via our <link href="site:community/index_com">issue tracker</link> marked for inclusion,
+ which will be applied by a committer. Committers apply their own work
+ directly, but it is still essentially a patch.
+ </p>
+
+ <p>
+ We use the
+ <link href="http://www.apache.org/foundation/glossary.html#CommitThenReview">Commit-then-review</link>
+ method for decision-making about code changes by commiters on trunk, and <link href="http://www.apache.org/foundation/glossary.html#ReviewThenCommit">Review-then-Commit</link>
+ on the release branch. Please refer to that
+ glossary definition. Note that it does not preclude the committer
+ from making changes to patches prior to their commit, nor mean that the
+ committer can be careless. Rather it is a policy for decision-making.
+ Patches from non-commiters are applied according to the same rules by a commiter.
+ </p>
+
+ <p>
+ There is an important issue where both developers and committers need
+ to pay special attention: "licenses". We must not introduce licensing
+ conditions that go beyond the terms of the <link href="ext:asl">Apache License</link>.
+ If such issues do creep in to our repository, then we must work as
+ quickly as possible to address it and definitely before the next release.
+ </p>
+
+ <p>
+ There are some other problem areas:
+ What should a committer do if the patch is sloppy, containing inconsistent
+ whitespace and other code formatting, which mean that actual changes are not
+ easily visible in the svn diff messages. What if there is poorly constructed
+ (yet working) xml or java code? What if the new functionality is beyond the
+ scope of the project? What if there is a better way to do the task? What if
+ the patch will break the build, thereby preventing other developers from
+ working and causing an unstable trunk?
+ </p>
+
+ <p>
+ The committer has various options: ask the developer to resubmit the patch;
+ change the patch to fix the problems prior to committing; discuss the
+ issues on the dev list; commit it and then draw attention to the
+ issues so that the rest of the community can review and fix it.
+ A combination of these options would appear to be the best approach.
+ Please aim to not break the build, or introduce license problems, or make
+ noisy changes that obscure the real differences.
+ </p>
+
+ <p>
+ Committers should not be afraid to add changes that still need attention.
+ This enables prompt patch application and eases the load on the individual
+ committer. An interesting side-effect is that it encourages community growth.
+ </p>
+
+ </section>
+
+ <section id="contribution">
+ <title>Contribution and acknowledgement</title>
+ <p>
+ Some <link href="#way">principles</link> of open development at ASF are to ensure that each
+ contributor is recognised and feels a productive part of the community, and to
+ encourage diversity, respect, and equality.
+ Key to this is the recognition of contributions from individuals
+ in a manner that also recognises the community effort that made it all
+ possible. It is important to remember that there is no concept of
+ individual leadership. See the discussion of
+ <link href="http://www.apache.org/foundation/how-it-works.html#meritocracy">meritocracy</link>
+ and other sections of the
+ <link href="http://www.apache.org/foundation/how-it-works.html">How the ASF works</link> document.
+ </p>
+ <p>
+ In an Open Source Project, or more importantly, a project developed
+ using an open process, such as Apache Lenya, most contributions of actual
+ code are supported by, or at least *should* be supported by, design
+ discussion, oversight, testing, documentation, bug fixes and much more.
+ No code contribution is an independent unit of work (or should not be).
+ It is therefore impossible to credit individual contributors, it is
+ simply unmanageable, even if it is possible to identify each part of a
+ contribution.
+ </p>
+ <p>
+ At Apache Lenya we use the following method to provide recognition:
+ </p>
+ <ul>
+ <li>
+ All developers encourage other developers to participate on the
+ mailing lists, treat each other with respect, and openly collaborate.
+ This enables the contributors to feel a part of the project and shows
+ that their discussion and ideas are valuable. These replies enhance
+ the presence of their name in the email archives and search engines.
+ </li>
+ <li>
+ Encourage contributors to add patches via the
+ <link href="site:community/index_com">issue tracker</link>. This also enables clear
+ tracking of the issue and by default specifically shows who was the
+ contributor.
+ </li>
+ <li>
+ When committers apply the patch, they refer to the issue number
+ and the contributor's name. This enables linkage between the issue
+ tracker and the Subversion history. It adds the contributor's name
+ to the mail archives.
+ </li>
+ <li>
+ Committers apply patches as soon as possible. This keeps the contributor
+ enthused and shows them that their work is valuable. Plus, it reduces the risk of bit rot,
+ ie, patches that no longer cleanly apply due to unrelated code changes.
+ </li>
+ <li>
+ Committers write descriptive commit messages, which are then aggregated into
+ a top-level changes document. This enables linkage
+ to the relevant issue and shows the contributor's name. It also shows
+ the name of the committer who did the work to add the patch.
+ </li>
+ <li>
+ The existing PMC will notice new contributors who are committed. It eventually
+ <link href="#elect">invites</link> them to become new committers/PMC members. See the
+ <link href="ext:forrest.committed">forrest notes</link> about this topic.
+ </li>
+ <li>
+ Committers/PMC members are
+ <link href="lenya-document:699ba420-8730-11dc-ae46-9e7b5d14892d">listed</link>.
+ </li>
+ </ul>
+ <p>
+ As discussed above, there is no specific documentation which lists each
+ contributor and their work. For those who are interested there are various
+ mechanisms: Use general internet search services; use search services provided
+ by various third-party mail archives; search the "svn" mailing list using
+ committer IDs and using contributor names; browse the
+ changes pages; use 'svn log' and 'svn blame'.
+ </p>
+ </section>
+
+ <section id="develop">
+ <title>Development procedure</title>
+
+<note>
+ This section is still under development. The issues have been discussed
+ on the mailing list. Decisions need to be put into words, so that we do
+ not need to revisit the topic.
+</note>
+
+ <p>Development work is done on the trunk of SVN. If a commiter determines a need for a new branch,
+ he discusses the rationale on the developer list, and the decision is made by a vote.</p>
+
+ </section>
+
+<!-- FIXME:
+
+Mention the "Contributer License Agreement".
+Who needs to send it? ... is it committers plus major contributers?
+
+==================
+
+-->
+</body>
+</document>
Added: lenya/sandbox/pubs/docu/content/authoring/7af356a0-8730-11dc-ae46-9e7b5d14892d/en.meta.1195221911726.bak
URL: http://svn.apache.org/viewvc/lenya/sandbox/pubs/docu/content/authoring/7af356a0-8730-11dc-ae46-9e7b5d14892d/en.meta.1195221911726.bak?rev=595691&view=auto
==============================================================================
--- lenya/sandbox/pubs/docu/content/authoring/7af356a0-8730-11dc-ae46-9e7b5d14892d/en.meta.1195221911726.bak (added)
+++ lenya/sandbox/pubs/docu/content/authoring/7af356a0-8730-11dc-ae46-9e7b5d14892d/en.meta.1195221911726.bak Fri Nov 16 07:11:58 2007
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<metadata xmlns="http://apache.org/lenya/metadata/1.0">
+<element-set namespace="http://purl.org/dc/elements/1.1/">
+<element key="title">
+<value>Project guidelines</value>
+</element>
+</element-set>
+<element-set namespace="http://apache.org/lenya/metadata/document/1.0">
+<element key="extension">
+<value>xml</value>
+</element>
+<element key="mimeType">
+<value>application/xml</value>
+</element>
+<element key="resourceType">
+<value>forrestDocument20</value>
+</element>
+<element key="contentType">
+<value>xml</value>
+</element>
+</element-set>
+</metadata>
Modified: lenya/sandbox/pubs/docu/content/authoring/7af356a0-8730-11dc-ae46-9e7b5d14892d/en.rcml
URL: http://svn.apache.org/viewvc/lenya/sandbox/pubs/docu/content/authoring/7af356a0-8730-11dc-ae46-9e7b5d14892d/en.rcml?rev=595691&r1=595690&r2=595691&view=diff
==============================================================================
--- lenya/sandbox/pubs/docu/content/authoring/7af356a0-8730-11dc-ae46-9e7b5d14892d/en.rcml (original)
+++ lenya/sandbox/pubs/docu/content/authoring/7af356a0-8730-11dc-ae46-9e7b5d14892d/en.rcml Fri Nov 16 07:11:58 2007
@@ -1,5 +1,7 @@
<?xml version="1.0" encoding="UTF-8"?>
<XPSRevisionControl xmlns="">
+<CheckIn backup="true" identity="lenya" session="fde084c0-944b-11dc-8f2e-e6c0ff9903ab" time="1195221911726" version="3"/>
+<CheckOut identity="lenya" session="fde084c0-944b-11dc-8f2e-e6c0ff9903ab" time="1195221891718"/>
<CheckIn backup="true" identity="lenya" session="1f12dc80-8860-11dc-ba66-cfbbb816bd0d" time="1193910778634" version="2"/>
<CheckOut identity="lenya" session="1f12dc80-8860-11dc-ba66-cfbbb816bd0d" time="1193910764796"/>
<CheckIn backup="true" identity="lenya" session="60798970-8730-11dc-ae46-9e7b5d14892d" time="1193781627488" version="1"/>
Added: lenya/sandbox/pubs/docu/content/authoring/7c4cf330-8730-11dc-ae46-9e7b5d14892d/en.1195221905485.bak
URL: http://svn.apache.org/viewvc/lenya/sandbox/pubs/docu/content/authoring/7c4cf330-8730-11dc-ae46-9e7b5d14892d/en.1195221905485.bak?rev=595691&view=auto
==============================================================================
--- lenya/sandbox/pubs/docu/content/authoring/7c4cf330-8730-11dc-ae46-9e7b5d14892d/en.1195221905485.bak (added)
+++ lenya/sandbox/pubs/docu/content/authoring/7c4cf330-8730-11dc-ae46-9e7b5d14892d/en.1195221905485.bak Fri Nov 16 07:11:58 2007
@@ -0,0 +1,96 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!--
+ Copyright 1999-2004 The Apache Software Foundation
+
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+<!-- $Id: index.xml 55543 2004-10-26 00:14:59Z gregor $ --><!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "http://forrest.apache.org/dtd/document-v20.dtd">
+
+<document>
+ <header>
+ <title>Apache Lenya 2.0 Documentation</title>
+ </header>
+ <body>
+ <warning>
+ Apache Lenya 2.0 is still under development and should not be used for production
+ yet. A code freeze has been announced, and the release should be
+ imminent.
+ </warning>
+ <note label="Help wanted!"> Since 2.0 is new and provides many
+ enhancements and new features, please help to document them with us.
+ Send documentation patches and use the Wiki. Thanks in advance :)</note>
+ <p>
+ More documentation (work in progress) can be found at the <a href="site:wiki/lenya/">Apache Lenya
+ Wiki</a>. Please treat the Wiki with care for now, as much of the
+ information there is outdated.
+ </p>
+
+ <section>
+ <title>What's New in Lenya 2.0</title>
+ <dl>
+ <dt>
+<a href="lenya-document:a624c5c0-8730-11dc-ae46-9e7b5d14892d">Modularization</a>
+</dt>
+ <dd>
+ The monolithic architecture has been replaced by a small generic core and
+ various modules for specific purposes.
+ </dd>
+ <dt>
+<a href="lenya-document:35e35370-8731-11dc-ae46-9e7b5d14892d">Improved Repository Access</a>
+</dt>
+ <dd>
+ The refactored and extended repository API and new protocols make it easier
+ to access and manipulate documents.
+ </dd>
+ <dt>
+<a href="lenya-document:b0364980-8730-11dc-ae46-9e7b5d14892d">UUIDs for Internal Links</a>
+</dt>
+ <dd>
+ Documents are now identified and referenced using
+ <acronym title="Universally Unique Identifier">UUID</acronym>s.
+ Static link rewriting is not necessary anymore.
+ </dd>
+ <dt>
+<a href="lenya-document:9e75ea20-8730-11dc-ae46-9e7b5d14892d">Improved Access Control</a>
+</dt>
+ <dd>It is now possible to explicitly deny permissions on specific pages.</dd>
+ <dt>
+<a href="lenya-document:a7ac0200-8730-11dc-ae46-9e7b5d14892d">Configurable Meta Data</a>
+</dt>
+ <dd>
+ It is now possible to declare custom sets of meta data.
+ </dd>
+ <dt>
+<a href="lenya-document:a3a1c460-8730-11dc-ae46-9e7b5d14892d">Publication Templating</a>
+</dt>
+ <dd>
+ Publication templating allows to re-use common functionality in multiple publications.
+ </dd>
+ <dt>
+<a href="lenya-document:9ffa4030-8730-11dc-ae46-9e7b5d14892d">Usecase Framework</a>
+</dt>
+ <dd>
+ The usecase framework simplifies the implementation of user interaction functionality.
+ </dd>
+ <dt>
+<a href="lenya-document:db42f290-8730-11dc-ae46-9e7b5d14892d">Simplified Notification, Inboxes</a>
+</dt>
+ <dd>
+ It is now easier to trigger notification messages. Each user has a personal
+ inbox to read and send messages.
+ </dd>
+ </dl>
+ </section>
+
+ </body>
+</document>
Added: lenya/sandbox/pubs/docu/content/authoring/7c4cf330-8730-11dc-ae46-9e7b5d14892d/en.meta.1195221905485.bak
URL: http://svn.apache.org/viewvc/lenya/sandbox/pubs/docu/content/authoring/7c4cf330-8730-11dc-ae46-9e7b5d14892d/en.meta.1195221905485.bak?rev=595691&view=auto
==============================================================================
--- lenya/sandbox/pubs/docu/content/authoring/7c4cf330-8730-11dc-ae46-9e7b5d14892d/en.meta.1195221905485.bak (added)
+++ lenya/sandbox/pubs/docu/content/authoring/7c4cf330-8730-11dc-ae46-9e7b5d14892d/en.meta.1195221905485.bak Fri Nov 16 07:11:58 2007
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<metadata xmlns="http://apache.org/lenya/metadata/1.0">
+<element-set namespace="http://purl.org/dc/elements/1.1/">
+<element key="title">
+<value>Index</value>
+</element>
+</element-set>
+<element-set namespace="http://apache.org/lenya/metadata/document/1.0">
+<element key="extension">
+<value>xml</value>
+</element>
+<element key="mimeType">
+<value>application/xml</value>
+</element>
+<element key="resourceType">
+<value>forrestDocument20</value>
+</element>
+<element key="contentType">
+<value>xml</value>
+</element>
+</element-set>
+</metadata>
Modified: lenya/sandbox/pubs/docu/content/authoring/7c4cf330-8730-11dc-ae46-9e7b5d14892d/en.rcml
URL: http://svn.apache.org/viewvc/lenya/sandbox/pubs/docu/content/authoring/7c4cf330-8730-11dc-ae46-9e7b5d14892d/en.rcml?rev=595691&r1=595690&r2=595691&view=diff
==============================================================================
--- lenya/sandbox/pubs/docu/content/authoring/7c4cf330-8730-11dc-ae46-9e7b5d14892d/en.rcml (original)
+++ lenya/sandbox/pubs/docu/content/authoring/7c4cf330-8730-11dc-ae46-9e7b5d14892d/en.rcml Fri Nov 16 07:11:58 2007
@@ -1,5 +1,7 @@
<?xml version="1.0" encoding="UTF-8"?>
<XPSRevisionControl xmlns="">
+<CheckIn backup="true" identity="lenya" session="fde084c0-944b-11dc-8f2e-e6c0ff9903ab" time="1195221905485" version="3"/>
+<CheckOut identity="lenya" session="fde084c0-944b-11dc-8f2e-e6c0ff9903ab" time="1195221884477"/>
<CheckIn backup="true" identity="lenya" session="1f12dc80-8860-11dc-ba66-cfbbb816bd0d" time="1193910780786" version="2"/>
<CheckOut identity="lenya" session="1f12dc80-8860-11dc-ba66-cfbbb816bd0d" time="1193910766078"/>
<CheckIn backup="true" identity="lenya" session="60798970-8730-11dc-ae46-9e7b5d14892d" time="1193781622886" version="1"/>
Added: lenya/sandbox/pubs/docu/content/authoring/7f2fa0c0-8730-11dc-ae46-9e7b5d14892d/en.1195221896497.bak
URL: http://svn.apache.org/viewvc/lenya/sandbox/pubs/docu/content/authoring/7f2fa0c0-8730-11dc-ae46-9e7b5d14892d/en.1195221896497.bak?rev=595691&view=auto
==============================================================================
--- lenya/sandbox/pubs/docu/content/authoring/7f2fa0c0-8730-11dc-ae46-9e7b5d14892d/en.1195221896497.bak (added)
+++ lenya/sandbox/pubs/docu/content/authoring/7f2fa0c0-8730-11dc-ae46-9e7b5d14892d/en.1195221896497.bak Fri Nov 16 07:11:58 2007
@@ -0,0 +1,38 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!--
+ Copyright 1999-2004 The Apache Software Foundation
+
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+<!-- $Id: index.xml 47563 2004-09-30 07:19:08Z michi $ --><!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "http://forrest.apache.org/dtd/document-v20.dtd">
+
+<document>
+ <header>
+ <title>Downloading and Installing Apache Lenya 2.0</title>
+ </header>
+ <body>
+ <warning> Apache Lenya 2.0 is still under heavy development and should not
+ be used for production yet. </warning>
+ <ul>
+ <li> Download Apache Lenya 2.0 <ul> <li>
+<a href="subversion.html">Subversion</a>
+</li> </ul> <p> During the
+ development of Apache Lenya 2.0, only source versions will be released.
+ </p> <!--The Apache Software Foundation has <a href="http://people.apache.org/~henkp/cgi-bin/md5.cgi">more information on ASC Signatures and MD5 checksums</a>.-->
+ </li>
+ <li> Install Apache Lenya 2.0 <ul> <li>
+<a href="source_version.html">Source Version</a>
+</li> </ul> </li>
+ </ul>
+ </body>
+</document>
Added: lenya/sandbox/pubs/docu/content/authoring/7f2fa0c0-8730-11dc-ae46-9e7b5d14892d/en.meta.1195221896497.bak
URL: http://svn.apache.org/viewvc/lenya/sandbox/pubs/docu/content/authoring/7f2fa0c0-8730-11dc-ae46-9e7b5d14892d/en.meta.1195221896497.bak?rev=595691&view=auto
==============================================================================
--- lenya/sandbox/pubs/docu/content/authoring/7f2fa0c0-8730-11dc-ae46-9e7b5d14892d/en.meta.1195221896497.bak (added)
+++ lenya/sandbox/pubs/docu/content/authoring/7f2fa0c0-8730-11dc-ae46-9e7b5d14892d/en.meta.1195221896497.bak Fri Nov 16 07:11:58 2007
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<metadata xmlns="http://apache.org/lenya/metadata/1.0">
+<element-set namespace="http://purl.org/dc/elements/1.1/">
+<element key="title">
+<value>Download</value>
+</element>
+</element-set>
+<element-set namespace="http://apache.org/lenya/metadata/document/1.0">
+<element key="extension">
+<value>xml</value>
+</element>
+<element key="mimeType">
+<value>application/xml</value>
+</element>
+<element key="resourceType">
+<value>forrestDocument20</value>
+</element>
+<element key="contentType">
+<value>xml</value>
+</element>
+</element-set>
+</metadata>
Modified: lenya/sandbox/pubs/docu/content/authoring/7f2fa0c0-8730-11dc-ae46-9e7b5d14892d/en.rcml
URL: http://svn.apache.org/viewvc/lenya/sandbox/pubs/docu/content/authoring/7f2fa0c0-8730-11dc-ae46-9e7b5d14892d/en.rcml?rev=595691&r1=595690&r2=595691&view=diff
==============================================================================
--- lenya/sandbox/pubs/docu/content/authoring/7f2fa0c0-8730-11dc-ae46-9e7b5d14892d/en.rcml (original)
+++ lenya/sandbox/pubs/docu/content/authoring/7f2fa0c0-8730-11dc-ae46-9e7b5d14892d/en.rcml Fri Nov 16 07:11:58 2007
@@ -1,5 +1,7 @@
<?xml version="1.0" encoding="UTF-8"?>
<XPSRevisionControl xmlns="">
+<CheckIn backup="true" identity="lenya" session="fde084c0-944b-11dc-8f2e-e6c0ff9903ab" time="1195221896497" version="3"/>
+<CheckOut identity="lenya" session="fde084c0-944b-11dc-8f2e-e6c0ff9903ab" time="1195221884022"/>
<CheckIn backup="true" identity="lenya" session="1f12dc80-8860-11dc-ba66-cfbbb816bd0d" time="1193910796657" version="2"/>
<CheckOut identity="lenya" session="1f12dc80-8860-11dc-ba66-cfbbb816bd0d" time="1193910768103"/>
<CheckIn backup="true" identity="lenya" session="60798970-8730-11dc-ae46-9e7b5d14892d" time="1193781627659" version="1"/>
Added: lenya/sandbox/pubs/docu/content/authoring/80a5ed10-8730-11dc-ae46-9e7b5d14892d/en.1195221905199.bak
URL: http://svn.apache.org/viewvc/lenya/sandbox/pubs/docu/content/authoring/80a5ed10-8730-11dc-ae46-9e7b5d14892d/en.1195221905199.bak?rev=595691&view=auto
==============================================================================
--- lenya/sandbox/pubs/docu/content/authoring/80a5ed10-8730-11dc-ae46-9e7b5d14892d/en.1195221905199.bak (added)
+++ lenya/sandbox/pubs/docu/content/authoring/80a5ed10-8730-11dc-ae46-9e7b5d14892d/en.1195221905199.bak Fri Nov 16 07:11:58 2007
@@ -0,0 +1,78 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!--
+ Copyright 1999-2004 The Apache Software Foundation
+
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+<!-- $Id: cvs.xml 43104 2004-07-01 23:59:25Z thorsten $ --><!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "http://forrest.apache.org/dtd/document-v20.dtd">
+
+<document>
+
+<header>
+ <title>Lenya 2.0 Subversion Guide</title>
+
+
+
+</header>
+<body>
+
+<section>
+<title>For the public</title>
+<p>
+Start the shell of your choice and enter:
+</p>
+<source xml:space="preserve">
+svn co http://svn.apache.org/repos/asf/lenya/trunk lenya-2.0.x
+</source>
+</section>
+
+<section>
+<title>For committers</title>
+<p>
+Start the shell of your choice and enter:
+</p>
+<source xml:space="preserve">
+svn co https://svn.apache.org/repos/asf/lenya/trunk lenya-2.0.x
+ssh -l username svn.apache.org
+svnpasswd username
+exit
+</source>
+</section>
+
+<section>
+<title>View Subversion</title>
+<p>
+<a href="http://svn.apache.org/viewcvs.cgi/lenya/#dirlist">http://svn.apache.org/viewcvs.cgi/lenya/#dirlist</a>
+</p>
+</section>
+
+<section>
+ <title>Subversion Tips</title>
+
+<p>
+Installing the SVN client with SSL enabled on Debian Woody:
+</p>
+<source xml:space="preserve">
+apt-get install openssl
+apt-get install libssl-dev (Important Header Files)
+
+./configure --with-ssl
+make
+make install (su)
+svn --version
+</source>
+
+</section>
+
+</body>
+</document>
Added: lenya/sandbox/pubs/docu/content/authoring/80a5ed10-8730-11dc-ae46-9e7b5d14892d/en.meta.1195221905199.bak
URL: http://svn.apache.org/viewvc/lenya/sandbox/pubs/docu/content/authoring/80a5ed10-8730-11dc-ae46-9e7b5d14892d/en.meta.1195221905199.bak?rev=595691&view=auto
==============================================================================
--- lenya/sandbox/pubs/docu/content/authoring/80a5ed10-8730-11dc-ae46-9e7b5d14892d/en.meta.1195221905199.bak (added)
+++ lenya/sandbox/pubs/docu/content/authoring/80a5ed10-8730-11dc-ae46-9e7b5d14892d/en.meta.1195221905199.bak Fri Nov 16 07:11:58 2007
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<metadata xmlns="http://apache.org/lenya/metadata/1.0">
+<element-set namespace="http://purl.org/dc/elements/1.1/">
+<element key="title">
+<value>Subversion Access</value>
+</element>
+</element-set>
+<element-set namespace="http://apache.org/lenya/metadata/document/1.0">
+<element key="extension">
+<value>xml</value>
+</element>
+<element key="mimeType">
+<value>application/xml</value>
+</element>
+<element key="resourceType">
+<value>forrestDocument20</value>
+</element>
+<element key="contentType">
+<value>xml</value>
+</element>
+</element-set>
+</metadata>
Modified: lenya/sandbox/pubs/docu/content/authoring/80a5ed10-8730-11dc-ae46-9e7b5d14892d/en.rcml
URL: http://svn.apache.org/viewvc/lenya/sandbox/pubs/docu/content/authoring/80a5ed10-8730-11dc-ae46-9e7b5d14892d/en.rcml?rev=595691&r1=595690&r2=595691&view=diff
==============================================================================
--- lenya/sandbox/pubs/docu/content/authoring/80a5ed10-8730-11dc-ae46-9e7b5d14892d/en.rcml (original)
+++ lenya/sandbox/pubs/docu/content/authoring/80a5ed10-8730-11dc-ae46-9e7b5d14892d/en.rcml Fri Nov 16 07:11:58 2007
@@ -1,5 +1,7 @@
<?xml version="1.0" encoding="UTF-8"?>
<XPSRevisionControl xmlns="">
+<CheckIn backup="true" identity="lenya" session="fde084c0-944b-11dc-8f2e-e6c0ff9903ab" time="1195221905199" version="3"/>
+<CheckOut identity="lenya" session="fde084c0-944b-11dc-8f2e-e6c0ff9903ab" time="1195221884374"/>
<CheckIn backup="true" identity="lenya" session="1f12dc80-8860-11dc-ba66-cfbbb816bd0d" time="1193910798114" version="2"/>
<CheckOut identity="lenya" session="1f12dc80-8860-11dc-ba66-cfbbb816bd0d" time="1193910769219"/>
<CheckIn backup="true" identity="lenya" session="60798970-8730-11dc-ae46-9e7b5d14892d" time="1193781627052" version="1"/>
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.