directory-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From elecha...@apache.org
Subject svn commit: r578163 [1/2] - in /directory/project/trunk: ./ site/src/site/oldxdocs/ site/src/site/xdoc/ site/src/site/xdoc/community/process/ site/src/site/xdoc/community/who/ site/src/site/xdoc/projects/sitedocs/
Date Fri, 21 Sep 2007 15:10:09 GMT
Author: elecharny
Date: Fri Sep 21 08:10:08 2007
New Revision: 578163

URL: http://svn.apache.org/viewvc?rev=578163&view=rev
Log:
Removed all the ^M from the files

Modified:
    directory/project/trunk/LICENSE.txt
    directory/project/trunk/NOTICE.txt
    directory/project/trunk/site/src/site/oldxdocs/doc-template.xml
    directory/project/trunk/site/src/site/oldxdocs/irc.xml
    directory/project/trunk/site/src/site/oldxdocs/license.xml
    directory/project/trunk/site/src/site/oldxdocs/mailing-lists.xml
    directory/project/trunk/site/src/site/oldxdocs/project-proposal.html
    directory/project/trunk/site/src/site/xdoc/community/process/pmc.xml
    directory/project/trunk/site/src/site/xdoc/community/who/akarasulu.xml
    directory/project/trunk/site/src/site/xdoc/community/who/index.xml
    directory/project/trunk/site/src/site/xdoc/community/who/jmachols.xml
    directory/project/trunk/site/src/site/xdoc/community/who/mcconnell.xml
    directory/project/trunk/site/src/site/xdoc/community/who/psteitz.xml
    directory/project/trunk/site/src/site/xdoc/community/who/szoerner.xml
    directory/project/trunk/site/src/site/xdoc/community/who/trustin.xml
    directory/project/trunk/site/src/site/xdoc/index.xml
    directory/project/trunk/site/src/site/xdoc/projects/sitedocs/hyperlink-management.xml
    directory/project/trunk/site/src/site/xdoc/projects/sitedocs/maven-changes.xml
    directory/project/trunk/site/src/site/xdoc/projects/sitedocs/nav-template.txt
    directory/project/trunk/site/src/site/xdoc/projects/sitedocs/sitedoc-deployment.xml

Modified: directory/project/trunk/LICENSE.txt
URL: http://svn.apache.org/viewvc/directory/project/trunk/LICENSE.txt?rev=578163&r1=578162&r2=578163&view=diff
==============================================================================
--- directory/project/trunk/LICENSE.txt (original)
+++ directory/project/trunk/LICENSE.txt Fri Sep 21 08:10:08 2007
@@ -1,202 +1,202 @@
-                                 Apache License
-                           Version 2.0, January 2004
-                        http://www.apache.org/licenses/
-
-   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
-   1. Definitions.
-
-      "License" shall mean the terms and conditions for use, reproduction,
-      and distribution as defined by Sections 1 through 9 of this document.
-
-      "Licensor" shall mean the copyright owner or entity authorized by
-      the copyright owner that is granting the License.
-
-      "Legal Entity" shall mean the union of the acting entity and all
-      other entities that control, are controlled by, or are under common
-      control with that entity. For the purposes of this definition,
-      "control" means (i) the power, direct or indirect, to cause the
-      direction or management of such entity, whether by contract or
-      otherwise, or (ii) ownership of fifty percent (50%) or more of the
-      outstanding shares, or (iii) beneficial ownership of such entity.
-
-      "You" (or "Your") shall mean an individual or Legal Entity
-      exercising permissions granted by this License.
-
-      "Source" form shall mean the preferred form for making modifications,
-      including but not limited to software source code, documentation
-      source, and configuration files.
-
-      "Object" form shall mean any form resulting from mechanical
-      transformation or translation of a Source form, including but
-      not limited to compiled object code, generated documentation,
-      and conversions to other media types.
-
-      "Work" shall mean the work of authorship, whether in Source or
-      Object form, made available under the License, as indicated by a
-      copyright notice that is included in or attached to the work
-      (an example is provided in the Appendix below).
-
-      "Derivative Works" shall mean any work, whether in Source or Object
-      form, that is based on (or derived from) the Work and for which the
-      editorial revisions, annotations, elaborations, or other modifications
-      represent, as a whole, an original work of authorship. For the purposes
-      of this License, Derivative Works shall not include works that remain
-      separable from, or merely link (or bind by name) to the interfaces of,
-      the Work and Derivative Works thereof.
-
-      "Contribution" shall mean any work of authorship, including
-      the original version of the Work and any modifications or additions
-      to that Work or Derivative Works thereof, that is intentionally
-      submitted to Licensor for inclusion in the Work by the copyright owner
-      or by an individual or Legal Entity authorized to submit on behalf of
-      the copyright owner. For the purposes of this definition, "submitted"
-      means any form of electronic, verbal, or written communication sent
-      to the Licensor or its representatives, including but not limited to
-      communication on electronic mailing lists, source code control systems,
-      and issue tracking systems that are managed by, or on behalf of, the
-      Licensor for the purpose of discussing and improving the Work, but
-      excluding communication that is conspicuously marked or otherwise
-      designated in writing by the copyright owner as "Not a Contribution."
-
-      "Contributor" shall mean Licensor and any individual or Legal Entity
-      on behalf of whom a Contribution has been received by Licensor and
-      subsequently incorporated within the Work.
-
-   2. Grant of Copyright License. Subject to the terms and conditions of
-      this License, each Contributor hereby grants to You a perpetual,
-      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-      copyright license to reproduce, prepare Derivative Works of,
-      publicly display, publicly perform, sublicense, and distribute the
-      Work and such Derivative Works in Source or Object form.
-
-   3. Grant of Patent License. Subject to the terms and conditions of
-      this License, each Contributor hereby grants to You a perpetual,
-      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-      (except as stated in this section) patent license to make, have made,
-      use, offer to sell, sell, import, and otherwise transfer the Work,
-      where such license applies only to those patent claims licensable
-      by such Contributor that are necessarily infringed by their
-      Contribution(s) alone or by combination of their Contribution(s)
-      with the Work to which such Contribution(s) was submitted. If You
-      institute patent litigation against any entity (including a
-      cross-claim or counterclaim in a lawsuit) alleging that the Work
-      or a Contribution incorporated within the Work constitutes direct
-      or contributory patent infringement, then any patent licenses
-      granted to You under this License for that Work shall terminate
-      as of the date such litigation is filed.
-
-   4. Redistribution. You may reproduce and distribute copies of the
-      Work or Derivative Works thereof in any medium, with or without
-      modifications, and in Source or Object form, provided that You
-      meet the following conditions:
-
-      (a) You must give any other recipients of the Work or
-          Derivative Works a copy of this License; and
-
-      (b) You must cause any modified files to carry prominent notices
-          stating that You changed the files; and
-
-      (c) You must retain, in the Source form of any Derivative Works
-          that You distribute, all copyright, patent, trademark, and
-          attribution notices from the Source form of the Work,
-          excluding those notices that do not pertain to any part of
-          the Derivative Works; and
-
-      (d) If the Work includes a "NOTICE" text file as part of its
-          distribution, then any Derivative Works that You distribute must
-          include a readable copy of the attribution notices contained
-          within such NOTICE file, excluding those notices that do not
-          pertain to any part of the Derivative Works, in at least one
-          of the following places: within a NOTICE text file distributed
-          as part of the Derivative Works; within the Source form or
-          documentation, if provided along with the Derivative Works; or,
-          within a display generated by the Derivative Works, if and
-          wherever such third-party notices normally appear. The contents
-          of the NOTICE file are for informational purposes only and
-          do not modify the License. You may add Your own attribution
-          notices within Derivative Works that You distribute, alongside
-          or as an addendum to the NOTICE text from the Work, provided
-          that such additional attribution notices cannot be construed
-          as modifying the License.
-
-      You may add Your own copyright statement to Your modifications and
-      may provide additional or different license terms and conditions
-      for use, reproduction, or distribution of Your modifications, or
-      for any such Derivative Works as a whole, provided Your use,
-      reproduction, and distribution of the Work otherwise complies with
-      the conditions stated in this License.
-
-   5. Submission of Contributions. Unless You explicitly state otherwise,
-      any Contribution intentionally submitted for inclusion in the Work
-      by You to the Licensor shall be under the terms and conditions of
-      this License, without any additional terms or conditions.
-      Notwithstanding the above, nothing herein shall supersede or modify
-      the terms of any separate license agreement you may have executed
-      with Licensor regarding such Contributions.
-
-   6. Trademarks. This License does not grant permission to use the trade
-      names, trademarks, service marks, or product names of the Licensor,
-      except as required for reasonable and customary use in describing the
-      origin of the Work and reproducing the content of the NOTICE file.
-
-   7. Disclaimer of Warranty. Unless required by applicable law or
-      agreed to in writing, Licensor provides the Work (and each
-      Contributor provides its Contributions) on an "AS IS" BASIS,
-      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
-      implied, including, without limitation, any warranties or conditions
-      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
-      PARTICULAR PURPOSE. You are solely responsible for determining the
-      appropriateness of using or redistributing the Work and assume any
-      risks associated with Your exercise of permissions under this License.
-
-   8. Limitation of Liability. In no event and under no legal theory,
-      whether in tort (including negligence), contract, or otherwise,
-      unless required by applicable law (such as deliberate and grossly
-      negligent acts) or agreed to in writing, shall any Contributor be
-      liable to You for damages, including any direct, indirect, special,
-      incidental, or consequential damages of any character arising as a
-      result of this License or out of the use or inability to use the
-      Work (including but not limited to damages for loss of goodwill,
-      work stoppage, computer failure or malfunction, or any and all
-      other commercial damages or losses), even if such Contributor
-      has been advised of the possibility of such damages.
-
-   9. Accepting Warranty or Additional Liability. While redistributing
-      the Work or Derivative Works thereof, You may choose to offer,
-      and charge a fee for, acceptance of support, warranty, indemnity,
-      or other liability obligations and/or rights consistent with this
-      License. However, in accepting such obligations, You may act only
-      on Your own behalf and on Your sole responsibility, not on behalf
-      of any other Contributor, and only if You agree to indemnify,
-      defend, and hold each Contributor harmless for any liability
-      incurred by, or claims asserted against, such Contributor by reason
-      of your accepting any such warranty or additional liability.
-
-   END OF TERMS AND CONDITIONS
-
-   APPENDIX: How to apply the Apache License to your work.
-
-      To apply the Apache License to your work, attach the following
-      boilerplate notice, with the fields enclosed by brackets "[]"
-      replaced with your own identifying information. (Don't include
-      the brackets!)  The text should be enclosed in the appropriate
-      comment syntax for the file format. We also recommend that a
-      file or class name and description of purpose be included on the
-      same "printed page" as the copyright notice for easier
-      identification within third-party archives.
-
-   Copyright [yyyy] [name of copyright owner]
-
-   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.
-
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   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.
+

Modified: directory/project/trunk/NOTICE.txt
URL: http://svn.apache.org/viewvc/directory/project/trunk/NOTICE.txt?rev=578163&r1=578162&r2=578163&view=diff
==============================================================================
--- directory/project/trunk/NOTICE.txt (original)
+++ directory/project/trunk/NOTICE.txt Fri Sep 21 08:10:08 2007
@@ -1,2 +1,2 @@
-This product includes software developed by
-The Apache Software Foundation (http://www.apache.org/).
+This product includes software developed by
+The Apache Software Foundation (http://www.apache.org/).

Modified: directory/project/trunk/site/src/site/oldxdocs/doc-template.xml
URL: http://svn.apache.org/viewvc/directory/project/trunk/site/src/site/oldxdocs/doc-template.xml?rev=578163&r1=578162&r2=578163&view=diff
==============================================================================
--- directory/project/trunk/site/src/site/oldxdocs/doc-template.xml (original)
+++ directory/project/trunk/site/src/site/oldxdocs/doc-template.xml Fri Sep 21 08:10:08 2007
@@ -1,32 +1,32 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<document>
-  <properties>
-    <author email="akarasulu@apache.org">Alex Karasulu</author>
-    <title></title>
-  </properties> 
-  
-  <body>
-    <section name="">
-
-      <subsection name="">
-        <p>
-        </p>
-        <p>
-        </p>
-      </subsection>
-
-      <subsection name="">
-        <p>
-        </p>
-        
-        <table>
-          <tr>
-            <th>Topic</th>
-            <th>Description</th>
-          </tr>
-        </table>
-      </subsection>
-
-    </section>
-  </body>
-</document>
+<?xml version="1.0" encoding="UTF-8"?>
+<document>
+  <properties>
+    <author email="akarasulu@apache.org">Alex Karasulu</author>
+    <title></title>
+  </properties> 
+  
+  <body>
+    <section name="">
+
+      <subsection name="">
+        <p>
+        </p>
+        <p>
+        </p>
+      </subsection>
+
+      <subsection name="">
+        <p>
+        </p>
+        
+        <table>
+          <tr>
+            <th>Topic</th>
+            <th>Description</th>
+          </tr>
+        </table>
+      </subsection>
+
+    </section>
+  </body>
+</document>

Modified: directory/project/trunk/site/src/site/oldxdocs/irc.xml
URL: http://svn.apache.org/viewvc/directory/project/trunk/site/src/site/oldxdocs/irc.xml?rev=578163&r1=578162&r2=578163&view=diff
==============================================================================
--- directory/project/trunk/site/src/site/oldxdocs/irc.xml (original)
+++ directory/project/trunk/site/src/site/oldxdocs/irc.xml Fri Sep 21 08:10:08 2007
@@ -13,7 +13,7 @@
         <p>
           The perferred medium of communication is by email on the mailing lists
           however we have two IRC channels we use to track live get togethers,
-          and conversations.
+          and conversations.
         </p>
         <p>
           For the sake of history and tracking conversations we are logging both

Modified: directory/project/trunk/site/src/site/oldxdocs/license.xml
URL: http://svn.apache.org/viewvc/directory/project/trunk/site/src/site/oldxdocs/license.xml?rev=578163&r1=578162&r2=578163&view=diff
==============================================================================
--- directory/project/trunk/site/src/site/oldxdocs/license.xml (original)
+++ directory/project/trunk/site/src/site/oldxdocs/license.xml Fri Sep 21 08:10:08 2007
@@ -215,7 +215,7 @@
 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.
-        
+        
       </source>
       
       <p>
@@ -223,7 +223,7 @@
         copyright notice can be used in the boilerplate
       </p>
       <source>
-        Copyright 2004 The Apache Software Foundation
+        Copyright 2004 The Apache Software Foundation
       </source>
     </section>
     

Modified: directory/project/trunk/site/src/site/oldxdocs/mailing-lists.xml
URL: http://svn.apache.org/viewvc/directory/project/trunk/site/src/site/oldxdocs/mailing-lists.xml?rev=578163&r1=578162&r2=578163&view=diff
==============================================================================
--- directory/project/trunk/site/src/site/oldxdocs/mailing-lists.xml (original)
+++ directory/project/trunk/site/src/site/oldxdocs/mailing-lists.xml Fri Sep 21 08:10:08 2007
@@ -22,7 +22,7 @@
       <p>
         All mail and concerns are managed via one list per incubator project. 
         Although we left the incubator we're not discriminating between users and developers yet. 
-        As long a traffic is not extremely high, we will keep it as is.
+        As long a traffic is not extremely high, we will keep it as is.
       </p>      
       <p>
 	<em>Light Traffic</em>
@@ -36,7 +36,7 @@
       <p>
         This is kind of a misnomer.  We use subversion but the change 
         notification still uses cvs since we were originally going to use CVS
-        but switched to SVN.
+        but switched to SVN.
       </p>
       <p>
 	<em>Medium Traffic</em> 

Modified: directory/project/trunk/site/src/site/oldxdocs/project-proposal.html
URL: http://svn.apache.org/viewvc/directory/project/trunk/site/src/site/oldxdocs/project-proposal.html?rev=578163&r1=578162&r2=578163&view=diff
==============================================================================
--- directory/project/trunk/site/src/site/oldxdocs/project-proposal.html (original)
+++ directory/project/trunk/site/src/site/oldxdocs/project-proposal.html Fri Sep 21 08:10:08 2007
@@ -1,360 +1,360 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<!-- saved from url=(0067)http://nagoya.apache.org/wiki/apachewiki.cgi?ApacheDirectoryProject -->
-<HTML><HEAD><TITLE>Apache Wiki: ApacheDirectoryProject</TITLE>
-<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
-<META content="MSHTML 6.00.2800.1276" name=GENERATOR></HEAD>
-<BODY text=black vLink=purple link=blue bgColor=white>
-<H1><A href="http://nagoya.apache.org/wiki/apachewiki.cgi?HomePage"><IMG 
-alt=[Home] src="./images/asf_logo_wide.gif" border=0></A><A 
-href="http://nagoya.apache.org/wiki/apachewiki.cgi?search=ApacheDirectoryProject">ApacheDirectoryProject</A></H1><A 
-href="http://nagoya.apache.org/wiki/apachewiki.cgi?HomePage">HomePage</A> | <A 
-href="http://nagoya.apache.org/wiki/apachewiki.cgi?RecentChanges">RecentChanges</A> 
-| <A 
-href="http://nagoya.apache.org/wiki/apachewiki.cgi?action=editprefs">Preferences</A><BR>
-<HR>
-
-<H1>Proposal for an Apache Directory Project</H1><EM>10 Sept 2003, Alex Karasulu 
-(aok123@bellsouth.net) LDAPd Group Founder</EM> 
-<HR>
-
-<P>
-<P>
-<P><STRONG>Section 0 : Rationale</STRONG> 
-<P>The geometric growth of networks, services, distributed systems, and their 
-components has brought about a revival of interest in directories. Directories 
-are no longer considered commodity products used to store a phone book or list 
-of users. Directories and LDAP have grown into a critical technology that will 
-inevitably become a cornerstone of distributed systems. Several software giants 
-like BEA, SUN, and Microsoft have already demonstrated their belief in this 
-outcome by heavily integrating their products with directories. Directory and 
-naming systems are being used in everything from a simplified form for J2EE 
-configuration to full-blown enterprise directories, within identity management 
-systems and distributed computing platforms like JINI. 
-<P>
-<P>The overhead of managing several copies of relatively static information 
-across systems and enterprises is daunting and introduces the potential for data 
-inconsistency. The frequently replicated user and group tables in almost every 
-database driven application alone is a testament to this fact. When multiple 
-systems have to inter operate, they must share access to common information, and 
-directories are the best storage paradigm for rapidly accessing this type of 
-data. Whether the information to be stored, is a component's configuration, a 
-user's security profile, a business rule or a business process, directories are 
-the place to store it for centralized management, and distribution across 
-systems. 
-<P>To date, a fully compliant pure Java open source LDAPv3 server has not yet 
-been written. This is partially due to the fact that a practical stateful 
-protocol server in Java was virtually impossible until the introduction of the 
-NIO packages in the 1.4 SDK. LDAP, as a stateful protocol, manages client state 
-through a TCP socket connection. The socket connection persists through several 
-client requests and server responses tying them together under a logical session 
-or conversation. Before the introduction of non-blocking IO in the NIO packages 
-of the 1.4 SDK, a thread had to be dedicated to each socket to detect IO. A 
-stateful protocol server written completely in Java, would have needed as many 
-active threads as the number of concurrent clients. Theoretically, scalability 
-would have been very poor; the performance curve would be asymptotic, degrading 
-rapidly with an increase in the number of concurrent connections. To scale pure 
-Java statefull protocol server implementations had to wait until the Merlin 
-release of the JDK. 
-<P>Furthermore, no embeddable pure Java LDAPv3 server has yet been written and 
-made freely available. We believe the embedding of LDAP servers into existing 
-mail, application and web servers to be the next logical steps in the 
-progression and integration of LDAP. Several commercial examples can already be 
-sited: Microsoft Exchange and BEA Weblogic Server. The management benefits of 
-coupling these servers with an LDAP server are beyond the scope of this proposal 
-and left to the imagination of the reader. However, the synergy between embedded 
-LDAP servers and other flagship Apache servers would lead to greater economies 
-of scale for the Apache server suite and reduce the overhead of management for 
-the Apache software user community. 
-<P>LDAP directories are specialized databases, however unlike their RDBMS 
-counterparts, LDAP directories are fairly new and for this reason lack rich 
-integration features. High on the list of features lacking in LDAP servers are 
-stored procedures and triggers. Triggers and Java stored procedures would expand 
-the horizon of LDAP in itself even without the benefits of Java. Triggers and 
-stored procedures would alleviate ugly workarounds which currently using polling 
-and meta directories. These features alone would attract groups within the LDAP 
-and Java communities to band together and support the Apache LDAP Project. 
-<P>LDAP is both a network line protocol and a hierarchical relational database. 
-Some might even argue that LDAP is object oriented. Regardless, the 
-implementation of an LDAP server is not a trivial matter. LDAP code bases 
-written in native languages have to be ported to run on different platforms. 
-Conditional complies in C based implementations were shown to considerably 
-reduce the maintainability of code bases. The complexity of a database, a 
-network line protocol and conditional compilation together have resulted in 
-reduced maintainability for C based LDAP servers. Also the learning curve and 
-hence barrier to entry for developers is greater. These complications would not 
-exist for a Java based LDAP server that is written once and can run anywhere. 
-<P>The Apache Foundation supports several component container projects which 
-provide the proper foundation for a Java LDAP directory server. Apache also 
-supports several server side application containers which can realize 
-significant functional enhancements by employing an LDAP directory server. Also 
-LDAP requiring organizations today must settle for less than optimal 
-implementations and often have to pay as high as a dollar per entry to directory 
-enable their applications. The Apache LDAP Project would solve these problems by 
-providing a free robust LDAPv3 implementation in a standalone configuration or 
-an embeddable configuration for use in all Apache servers and other third party 
-products. 
-<P>Our goal is to produce a community of developers with backgrounds in LDAP, 
-X.500, Database Engineering and JNDI tasked with the development of pure Java 
-LDAPv3 Clients, APIs, JNDI providers and LDAPv3 compliant servers with the 
-aforementioned features. The produced software will be ASF licensed. Where 
-applicable the best available ASF/BSD licensed code will be reused and new code 
-will be added to complete the LDAPv3 protocol as defined in <A 
-href="http://www.ietf.org/rfc/rfc3377.txt">[RFC 3377]</A> and its associated 8 
-RFCs listed below: 
-<P>
-<UL>
-  <LI><A href="http://www.ietf.org/rfc/rfc2251.txt">[RFC2251]</A> Lightweight 
-  Directory Access Protocol (v3): LDAP on-the-wire protocol 
-  <LI><A href="http://www.ietf.org/rfc/rfc2252.txt">[RFC2252]</A> Lightweight 
-  Directory Access Protocol (v3): Attribute Syntax Definitions 
-  <LI><A href="http://www.ietf.org/rfc/rfc2253.txt">[RFC2253]</A> Lightweight 
-  Directory Access Protocol (v3): UTF-8 String Representation of DNs 
-  <LI><A href="http://www.ietf.org/rfc/rfc2254.txt">[RFC2254]</A> The String 
-  Representation of LDAP Search Filters 
-  <LI><A href="http://www.ietf.org/rfc/rfc2255.txt">[RFC2255]</A> The LDAP URL 
-  Format 
-  <LI><A href="http://www.ietf.org/rfc/rfc2256.txt">[RFC2256]</A> A Summary of 
-  the X.500(96) User Schema for use with LDAPv3 
-  <LI><A href="http://www.ietf.org/rfc/rfc2829.txt">[RFC2829]</A> Authentication 
-  Methods for LDAP 
-  <LI><A href="http://www.ietf.org/rfc/rfc2830.txt">[RFC2830]</A> Lightweight 
-  Directory Access Protocol (v3): Extension for Transport Layer Security 
-</LI></UL>
-<P>Additionally, the schema objects specified within the following RFCs will be 
-defined for use and partial or full complaince will be met where relavent to the 
-project: 
-<P>
-<UL>
-  <LI><A href="http://www.ietf.org/rfc/rfc1274.txt">[RFC1274]</A> The COSINE and 
-  Internet X.500 Schema 
-  <LI><A href="http://www.faqs.org/rfcs/rfc1804.html">[RFC1804]</A> Schema 
-  Publishing in X.500 Directory 
-  <LI><A href="http://www.ietf.org/rfc/rfc2079.txt">[RFC2079]</A> Definition of 
-  an X.500 Attribute Type and an Object Class to Hold Uniform Resource 
-  Identifiers (URIs) 
-  <LI><A href="http://www.ietf.org/rfc/rfc2247.txt">[RFC2247]</A> Using Domains 
-  in LDAP/X.500 Distinguished Names 
-  <LI><A href="http://www.ietf.org/rfc/rfc2293.txt">[RFC2293]</A> Representing 
-  Tables and Subtrees in the X.500 Directory 
-  <LI><A href="http://www.ietf.org/rfc/rfc2294.txt">[RFC2294]</A> Representing 
-  the O/R Address hierarchy in the X.500 Directory Information Tree 
-  <LI><A href="http://www.ietf.org/rfc/rfc2307.txt">[RFC2307]</A> An Approach 
-  for Using LDAP as a Network Information Service 
-  <LI><A href="http://www.ietf.org/rfc/rfc2377.txt">[RFC2377]</A> Naming Plan 
-  for Internet Directory-Enabled Applications 
-  <LI><A href="http://www.ietf.org/rfc/rfc2587.txt">[RFC2587]</A> Internet X.509 
-  Public Key Infrastructure LDAPv2 Schema 
-  <LI><A href="http://www.ietf.org/rfc/rfc2589.txt">[RFC2589]</A> Lightweight 
-  Directory Access Protocol (v3): Extensions for Dynamic Directory Services 
-  <LI><A href="http://www.ietf.org/rfc/rfc2596.txt">[RFC2596]</A> Use of 
-  Language Codes in LDAP 
-  <LI><A href="http://www.ietf.org/rfc/rfc2649.txt">[RFC2649]</A> An LDAP 
-  Control and Schema for Holding Operation Signatures 
-  <LI><A href="http://www.ietf.org/rfc/rfc2696.txt">[RFC2696]</A> LDAP Control 
-  Extension for Simple Paged Results Manipulation 
-  <LI><A href="http://www.ietf.org/rfc/rfc2713.txt">[RFC2713]</A> Schema for 
-  Representing Java(tm) Objects in an LDAP Directory 
-  <LI><A href="http://www.ietf.org/rfc/rfc2714.txt">[RFC2714]</A> Schema for 
-  Representing CORBA Object References in an LDAP Directory 
-  <LI><A href="http://www.ietf.org/rfc/rfc2798.txt">[RFC2798]</A> Definition of 
-  the inetOrgPerson<A 
-  href="http://nagoya.apache.org/wiki/apachewiki.cgi?action=edit&amp;id=OrgPerson">?</A> 
-  LDAP Object Class 
-  <LI><A href="http://www.ietf.org/rfc/rfc2829.txt">[RFC2829]</A> Authentication 
-  Methods for LDAP 
-  <LI><A href="http://www.ietf.org/rfc/rfc2830.txt">[RFC2830]</A> Lightweight 
-  Directory Access Protocol (v3): Extension for Transport Layer Security 
-  <LI><A href="http://www.ietf.org/rfc/rfc2849.txt">[RFC2849]</A> The LDAP Data 
-  Interchange Format (LDIF) - Technical Specification 
-  <LI><A href="http://www.ietf.org/rfc/rfc2891.txt">[RFC2891]</A> LDAP Control 
-  Extension for Server Side Sorting of Search Results 
-  <LI><A href="http://www.ietf.org/rfc/rfc3045.txt">[RFC3045]</A> Storing Vendor 
-  Information in the LDAP root DSE 
-  <LI><A href="http://www.ietf.org/rfc/rfc3062.txt">[RFC3062]</A> LDAP Password 
-  Modify Extended Operation 
-  <LI><A href="http://www.ietf.org/rfc/rfc3088.txt">[RFC3088]</A> OpenLDAP<A 
-  href="http://nagoya.apache.org/wiki/apachewiki.cgi?action=edit&amp;id=OpenLDAP">?</A> 
-  Root Service An experimental LDAP referral service 
-  <LI><A href="http://www.ietf.org/rfc/rfc3112.txt">[RFC3112]</A> LDAP 
-  Authentication Password Schema 
-  <LI><A href="http://www.ietf.org/rfc/rfc3296.txt">[RFC3296]</A> Named 
-  Subordinate References in Lightweight Directory Access Protocol (LDAP) 
-  Directories 
-  <LI><A href="http://www.ietf.org/rfc/rfc3383.txt">[RFC3383]</A> Internet 
-  Assigned Numbers Authority (IANA) considerations for the Lightweight Directory 
-  Access Protocol (LDAP) </LI></UL>
-<P>
-<P><STRONG>Section 0.1 : Criteria</STRONG> 
-<P>We feel that this project has a good chance for success as the following 
-project aspects are carefully considered : 
-<P><EM>Meritocracy:</EM> The project will be meritocratic - the usual Apache 
-meritocracy rules would apply. 
-<P><EM>Community:</EM> The user community for this project is potentially 
-massive. The initial developer community for this project consists of developers 
-from Apache and LDAPd projects. The aim is for this community to grow 
-considerably once this project enters the incubator. 
-<P><EM>Core Developers:</EM> The initial developers are listed further below 
-within this document and consist of some existing Apache committers together 
-with committers from the LDAPd Group. 
-<P><EM>Alignment:</EM> There is clear alignment with many existing Apache 
-projects. From Jakarta projects such as Tomcat, James and Slide for embedding 
-LDAP. The LDAP DSML standards will eventually require the use of several XML 
-projects. Other projects like OpenJms<A 
-href="http://nagoya.apache.org/wiki/apachewiki.cgi?action=edit&amp;id=OpenJms">?</A>, 
-which currently are not Apache projects but very well may be in the future will 
-be used for things like replication. Jdbm likewise is used for building Btree 
-based indices for custom databases. Also projects like Apache Xindice may be 
-leveraged for an XML based backend or for DSML enabling subsystems of an LDAP 
-server. 
-<P>We see the Apache Directory Project as a separate project to existing Apache 
-projects, serving several roles 
-<UL>
-  <LI>Home for Apache Directory Client APIs and Client Scripts 
-  <LI>Home for Apache JNDI Providers for Various Directory Namespaces 
-  <LI>Home for Apache Directory Servers 
-  <LI>May also become home to an ASN.1 Encoding/Decoding<A 
-  href="http://nagoya.apache.org/wiki/apachewiki.cgi?action=edit&amp;id=ApacheDirectoryProject/Decoding">?</A> 
-  Library </LI></UL>
-<P>
-<P><STRONG>Section 0.2 : Warning Signs</STRONG> 
-<P>We feel this project has a good chance for success as the following warning 
-signs do not apply to the project we are proposing: 
-<P><EM>Orphaned products:</EM> This project is starting with an existing code 
-base which using lots of the high quality open source code out there which is 
-ASF/BSD licensed. 
-<P><EM>Inexperience with open source:</EM> The initial community is made up of 
-existing Apache and LDAPd Group committers exclusively so the open source 
-experience is there to varying degrees. 
-<P><EM>Reliance on salaried developers:</EM> None of the initial developers are 
-currently paid to work on the Directory Project. 
-<P><EM>No ties to other Apache products:</EM> The Apache Directory Project is 
-complementary to existing technologies at Apache. LDAPd currently uses Avalon 
-and will eventually be used by james. LDAPd will eventually integrate into 
-Geronimo. The Apache Directory Project will integrate with, and possibly 
-subsume, Jakarta Commons Naming. 
-<P><EM>A fascination with the Apache brand:</EM> The committers are interested 
-in developing a healthy open source community around ASF/BSD licensed directory 
-servers and their clients along with other JNDI accessible name spaces. Is 
-Apache the right place? We think it is. Several Apache folks have already shown 
-interest in LDAPd, the seed code base to be used for this project. In fact the 
-LDAPd Group was initially approached by Apache to submit an Incubator proposal. 
-LDAPd Group members voted unanimously to donate the code to Apache in an effort 
-to build the next flagship server at Apache and much more. 
-<P>
-<P><STRONG>Section 1 : Scope of the Project</STRONG> 
-<P>There are multiple goals for this Apache project: 
-<P>
-<UL>
-  <LI>Promote a healthy open source community! 
-  <LI>Promote a language agnostic environment for both client side and server 
-  side endeavors. 
-  <LI>A one stop location for all directory and naming needs on any platform or 
-  any language. 
-  <UL>
-    <LI>client APIs 
-    <LI>clients 
-    <LI>JNDI providers for Java and other namespaces. 
-    <LI>May also include an LDAP protocol correctness and stress testing suite 
-    in the future. </LI></UL>
-  <LI>Provide servers in embeddable configurations. 
-  <LI>Provide servers in standalone configurations as UNIX daemons or NT 
-  Services. 
-  <LI>Provide support for Directory Server embedding or integration with 
-  existing Apache servers like httpd, Slide, Tomcat, James and Geronimo. 
-</LI></UL>
-<P>
-<P><STRONG>Section 2 : Initial Source</STRONG> 
-<P>The initial code base from which to create the Apache Directory repository is 
-contained mostly at Sourceforge under the LDAPd project accessible <A 
-href="http://sourceforge.net/projects/ldapd">[here]</A>. This code base must 
-assign copyright to the Apache Software Foundation. The code base will need to 
-be licensed under The Apache Software Foundation license. The license file in 
-every subproject will be changed to the Apache license. The current license is 
-already an Apache "style" license, so this change is basically a change to name 
-The ASF as the owner. 
-<P>The proposed TLP (after incubation) would have an one or more directory 
-servers with multiple datastore backends, a JNDI context for J2EE configuration, 
-JNDI service provider(s) for LDAP and other transports, State and Object 
-Factories suitable for use in the various Context/DirContext<A 
-href="http://nagoya.apache.org/wiki/apachewiki.cgi?action=edit&amp;id=ApacheDirectoryProject/DirContext">?</A> 
-implementations, etc. 
-<P>Beside source code the LDAPd Group must transfer its IANA assigned ASN.1 
-Object Identifier to Apache Software Foundation. 
-<P><STRONG>Section 3 : ASF Resources to be Created</STRONG> 
-<P><EM>Section 3.1 : Mailing Lists</EM> 
-<P>
-<UL>
-  <LI>directory-dev@incubator.apache.org </LI></UL>
-<P><EM>Section 3.2 : CVS Repositories</EM> 
-<P>
-<UL>
-  <LI>incubator-directory </LI></UL>
-<P><EM>Section 3.3 : Bugzilla or (preferably) Jira</EM> 
-<P>
-<UL>
-  <LI>directory </LI></UL>
-<P>
-<P><STRONG>Section 4 : Initial Set of Committers</STRONG> 
-<P>All contributors must sign and submit a Contributors License Agreement. The 
-following individuals are the contributors, and have signed and sent the 
-agreement at one time or another: 
-<P>
-<UL>
-  <LI>Alex Karasulu 
-  <LI>Phil Steitz 
-  <LI>Robb Penoyer 
-  <LI>Noel Bergman 
-  <LI>Jeff Machols 
-  <LI>Henri Yandell 
-  <LI>Wes McKean<A 
-  href="http://nagoya.apache.org/wiki/apachewiki.cgi?action=edit&amp;id=McKean">?</A> 
-  </LI></UL>
-<P>
-<P><STRONG>Section 5 : Apache Sponsoring Individuals</STRONG> 
-<P>
-<UL>
-  <LI>Nicola Ken Barozzi (Apache Incubator) 
-  <LI>Noel J. Bergman (Apache James) 
-  <LI>Henri Yandell (Jakarta Commons Naming) 
-  <LI>Stephen McConnell<A 
-  href="http://nagoya.apache.org/wiki/apachewiki.cgi?action=edit&amp;id=McConnell">?</A> 
-  (Apache Avalon) 
-  <LI>James Strachan (Apache Geronimo) </LI></UL>
-<P>
-<P><STRONG>Section 6 : Incubation Exit Criteria</STRONG> 
-<P>We feel this project should exit the incubator to a TLP using the domain name 
-directory.apache.org should the following goals be met: 
-<P><EM>Technical Goals:</EM> 
-<P>
-<UL>
-  <LI>Clean status with Apaches Continuous Integration System 
-  <LI>Website cross reference to existing Apache literature with respect to 
-  rules and regulations 
-  <LI>At a minimum a beta release and/or a series of Release Candidates for a 
-  directory server and its clients. 
-  <LI>At least one server that complies with <A 
-  href="http://www.ietf.org/rfc/rfc2251.txt">[RFC2251]</A> </LI></UL>
-<P><EM>Non-Technical Goals:</EM> 
-<P>
-<UL>
-  <LI>List presence and monitoring in wider Apache communities 
-  <LI>Website cross reference to existing Apache literarature with respect to 
-  rules and regulations 
-  <LI>Initial integration plan and cooperation with Geronimo, and James 
-  <LI>Member presence on the licensing@apache list 
-  <LI>More Apache or non-Apache committers who are actively modifying source 
-  code </LI></UL>
-<HR>
-
-<FORM action=apachewiki.cgi method=post><A 
-href="http://nagoya.apache.org/wiki/apachewiki.cgi?HomePage">HomePage</A> | <A 
-href="http://nagoya.apache.org/wiki/apachewiki.cgi?RecentChanges">RecentChanges</A> 
-| <A 
-href="http://nagoya.apache.org/wiki/apachewiki.cgi?action=editprefs">Preferences</A><BR><A 
-href="http://nagoya.apache.org/wiki/apachewiki.cgi?action=edit&amp;id=ApacheDirectoryProject">Edit 
-text of this page</A> | <A 
-href="http://nagoya.apache.org/wiki/apachewiki.cgi?action=history&amp;id=ApacheDirectoryProject">View 
-other revisions</A><BR>Last edited September 30, 2003 7:59 am <A 
-href="http://nagoya.apache.org/wiki/apachewiki.cgi?action=browse&amp;diff=1&amp;id=ApacheDirectoryProject">(diff)</A><BR>Search: 
-<INPUT name=search><INPUT type=hidden value=1 name=dosearch> 
-</FORM></BODY></HTML>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<!-- saved from url=(0067)http://nagoya.apache.org/wiki/apachewiki.cgi?ApacheDirectoryProject -->
+<HTML><HEAD><TITLE>Apache Wiki: ApacheDirectoryProject</TITLE>
+<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
+<META content="MSHTML 6.00.2800.1276" name=GENERATOR></HEAD>
+<BODY text=black vLink=purple link=blue bgColor=white>
+<H1><A href="http://nagoya.apache.org/wiki/apachewiki.cgi?HomePage"><IMG 
+alt=[Home] src="./images/asf_logo_wide.gif" border=0></A><A 
+href="http://nagoya.apache.org/wiki/apachewiki.cgi?search=ApacheDirectoryProject">ApacheDirectoryProject</A></H1><A 
+href="http://nagoya.apache.org/wiki/apachewiki.cgi?HomePage">HomePage</A> | <A 
+href="http://nagoya.apache.org/wiki/apachewiki.cgi?RecentChanges">RecentChanges</A> 
+| <A 
+href="http://nagoya.apache.org/wiki/apachewiki.cgi?action=editprefs">Preferences</A><BR>
+<HR>
+
+<H1>Proposal for an Apache Directory Project</H1><EM>10 Sept 2003, Alex Karasulu 
+(aok123@bellsouth.net) LDAPd Group Founder</EM> 
+<HR>
+
+<P>
+<P>
+<P><STRONG>Section 0 : Rationale</STRONG> 
+<P>The geometric growth of networks, services, distributed systems, and their 
+components has brought about a revival of interest in directories. Directories 
+are no longer considered commodity products used to store a phone book or list 
+of users. Directories and LDAP have grown into a critical technology that will 
+inevitably become a cornerstone of distributed systems. Several software giants 
+like BEA, SUN, and Microsoft have already demonstrated their belief in this 
+outcome by heavily integrating their products with directories. Directory and 
+naming systems are being used in everything from a simplified form for J2EE 
+configuration to full-blown enterprise directories, within identity management 
+systems and distributed computing platforms like JINI. 
+<P>
+<P>The overhead of managing several copies of relatively static information 
+across systems and enterprises is daunting and introduces the potential for data 
+inconsistency. The frequently replicated user and group tables in almost every 
+database driven application alone is a testament to this fact. When multiple 
+systems have to inter operate, they must share access to common information, and 
+directories are the best storage paradigm for rapidly accessing this type of 
+data. Whether the information to be stored, is a component's configuration, a 
+user's security profile, a business rule or a business process, directories are 
+the place to store it for centralized management, and distribution across 
+systems. 
+<P>To date, a fully compliant pure Java open source LDAPv3 server has not yet 
+been written. This is partially due to the fact that a practical stateful 
+protocol server in Java was virtually impossible until the introduction of the 
+NIO packages in the 1.4 SDK. LDAP, as a stateful protocol, manages client state 
+through a TCP socket connection. The socket connection persists through several 
+client requests and server responses tying them together under a logical session 
+or conversation. Before the introduction of non-blocking IO in the NIO packages 
+of the 1.4 SDK, a thread had to be dedicated to each socket to detect IO. A 
+stateful protocol server written completely in Java, would have needed as many 
+active threads as the number of concurrent clients. Theoretically, scalability 
+would have been very poor; the performance curve would be asymptotic, degrading 
+rapidly with an increase in the number of concurrent connections. To scale pure 
+Java statefull protocol server implementations had to wait until the Merlin 
+release of the JDK. 
+<P>Furthermore, no embeddable pure Java LDAPv3 server has yet been written and 
+made freely available. We believe the embedding of LDAP servers into existing 
+mail, application and web servers to be the next logical steps in the 
+progression and integration of LDAP. Several commercial examples can already be 
+sited: Microsoft Exchange and BEA Weblogic Server. The management benefits of 
+coupling these servers with an LDAP server are beyond the scope of this proposal 
+and left to the imagination of the reader. However, the synergy between embedded 
+LDAP servers and other flagship Apache servers would lead to greater economies 
+of scale for the Apache server suite and reduce the overhead of management for 
+the Apache software user community. 
+<P>LDAP directories are specialized databases, however unlike their RDBMS 
+counterparts, LDAP directories are fairly new and for this reason lack rich 
+integration features. High on the list of features lacking in LDAP servers are 
+stored procedures and triggers. Triggers and Java stored procedures would expand 
+the horizon of LDAP in itself even without the benefits of Java. Triggers and 
+stored procedures would alleviate ugly workarounds which currently using polling 
+and meta directories. These features alone would attract groups within the LDAP 
+and Java communities to band together and support the Apache LDAP Project. 
+<P>LDAP is both a network line protocol and a hierarchical relational database. 
+Some might even argue that LDAP is object oriented. Regardless, the 
+implementation of an LDAP server is not a trivial matter. LDAP code bases 
+written in native languages have to be ported to run on different platforms. 
+Conditional complies in C based implementations were shown to considerably 
+reduce the maintainability of code bases. The complexity of a database, a 
+network line protocol and conditional compilation together have resulted in 
+reduced maintainability for C based LDAP servers. Also the learning curve and 
+hence barrier to entry for developers is greater. These complications would not 
+exist for a Java based LDAP server that is written once and can run anywhere. 
+<P>The Apache Foundation supports several component container projects which 
+provide the proper foundation for a Java LDAP directory server. Apache also 
+supports several server side application containers which can realize 
+significant functional enhancements by employing an LDAP directory server. Also 
+LDAP requiring organizations today must settle for less than optimal 
+implementations and often have to pay as high as a dollar per entry to directory 
+enable their applications. The Apache LDAP Project would solve these problems by 
+providing a free robust LDAPv3 implementation in a standalone configuration or 
+an embeddable configuration for use in all Apache servers and other third party 
+products. 
+<P>Our goal is to produce a community of developers with backgrounds in LDAP, 
+X.500, Database Engineering and JNDI tasked with the development of pure Java 
+LDAPv3 Clients, APIs, JNDI providers and LDAPv3 compliant servers with the 
+aforementioned features. The produced software will be ASF licensed. Where 
+applicable the best available ASF/BSD licensed code will be reused and new code 
+will be added to complete the LDAPv3 protocol as defined in <A 
+href="http://www.ietf.org/rfc/rfc3377.txt">[RFC 3377]</A> and its associated 8 
+RFCs listed below: 
+<P>
+<UL>
+  <LI><A href="http://www.ietf.org/rfc/rfc2251.txt">[RFC2251]</A> Lightweight 
+  Directory Access Protocol (v3): LDAP on-the-wire protocol 
+  <LI><A href="http://www.ietf.org/rfc/rfc2252.txt">[RFC2252]</A> Lightweight 
+  Directory Access Protocol (v3): Attribute Syntax Definitions 
+  <LI><A href="http://www.ietf.org/rfc/rfc2253.txt">[RFC2253]</A> Lightweight 
+  Directory Access Protocol (v3): UTF-8 String Representation of DNs 
+  <LI><A href="http://www.ietf.org/rfc/rfc2254.txt">[RFC2254]</A> The String 
+  Representation of LDAP Search Filters 
+  <LI><A href="http://www.ietf.org/rfc/rfc2255.txt">[RFC2255]</A> The LDAP URL 
+  Format 
+  <LI><A href="http://www.ietf.org/rfc/rfc2256.txt">[RFC2256]</A> A Summary of 
+  the X.500(96) User Schema for use with LDAPv3 
+  <LI><A href="http://www.ietf.org/rfc/rfc2829.txt">[RFC2829]</A> Authentication 
+  Methods for LDAP 
+  <LI><A href="http://www.ietf.org/rfc/rfc2830.txt">[RFC2830]</A> Lightweight 
+  Directory Access Protocol (v3): Extension for Transport Layer Security 
+</LI></UL>
+<P>Additionally, the schema objects specified within the following RFCs will be 
+defined for use and partial or full complaince will be met where relavent to the 
+project: 
+<P>
+<UL>
+  <LI><A href="http://www.ietf.org/rfc/rfc1274.txt">[RFC1274]</A> The COSINE and 
+  Internet X.500 Schema 
+  <LI><A href="http://www.faqs.org/rfcs/rfc1804.html">[RFC1804]</A> Schema 
+  Publishing in X.500 Directory 
+  <LI><A href="http://www.ietf.org/rfc/rfc2079.txt">[RFC2079]</A> Definition of 
+  an X.500 Attribute Type and an Object Class to Hold Uniform Resource 
+  Identifiers (URIs) 
+  <LI><A href="http://www.ietf.org/rfc/rfc2247.txt">[RFC2247]</A> Using Domains 
+  in LDAP/X.500 Distinguished Names 
+  <LI><A href="http://www.ietf.org/rfc/rfc2293.txt">[RFC2293]</A> Representing 
+  Tables and Subtrees in the X.500 Directory 
+  <LI><A href="http://www.ietf.org/rfc/rfc2294.txt">[RFC2294]</A> Representing 
+  the O/R Address hierarchy in the X.500 Directory Information Tree 
+  <LI><A href="http://www.ietf.org/rfc/rfc2307.txt">[RFC2307]</A> An Approach 
+  for Using LDAP as a Network Information Service 
+  <LI><A href="http://www.ietf.org/rfc/rfc2377.txt">[RFC2377]</A> Naming Plan 
+  for Internet Directory-Enabled Applications 
+  <LI><A href="http://www.ietf.org/rfc/rfc2587.txt">[RFC2587]</A> Internet X.509 
+  Public Key Infrastructure LDAPv2 Schema 
+  <LI><A href="http://www.ietf.org/rfc/rfc2589.txt">[RFC2589]</A> Lightweight 
+  Directory Access Protocol (v3): Extensions for Dynamic Directory Services 
+  <LI><A href="http://www.ietf.org/rfc/rfc2596.txt">[RFC2596]</A> Use of 
+  Language Codes in LDAP 
+  <LI><A href="http://www.ietf.org/rfc/rfc2649.txt">[RFC2649]</A> An LDAP 
+  Control and Schema for Holding Operation Signatures 
+  <LI><A href="http://www.ietf.org/rfc/rfc2696.txt">[RFC2696]</A> LDAP Control 
+  Extension for Simple Paged Results Manipulation 
+  <LI><A href="http://www.ietf.org/rfc/rfc2713.txt">[RFC2713]</A> Schema for 
+  Representing Java(tm) Objects in an LDAP Directory 
+  <LI><A href="http://www.ietf.org/rfc/rfc2714.txt">[RFC2714]</A> Schema for 
+  Representing CORBA Object References in an LDAP Directory 
+  <LI><A href="http://www.ietf.org/rfc/rfc2798.txt">[RFC2798]</A> Definition of 
+  the inetOrgPerson<A 
+  href="http://nagoya.apache.org/wiki/apachewiki.cgi?action=edit&amp;id=OrgPerson">?</A> 
+  LDAP Object Class 
+  <LI><A href="http://www.ietf.org/rfc/rfc2829.txt">[RFC2829]</A> Authentication 
+  Methods for LDAP 
+  <LI><A href="http://www.ietf.org/rfc/rfc2830.txt">[RFC2830]</A> Lightweight 
+  Directory Access Protocol (v3): Extension for Transport Layer Security 
+  <LI><A href="http://www.ietf.org/rfc/rfc2849.txt">[RFC2849]</A> The LDAP Data 
+  Interchange Format (LDIF) - Technical Specification 
+  <LI><A href="http://www.ietf.org/rfc/rfc2891.txt">[RFC2891]</A> LDAP Control 
+  Extension for Server Side Sorting of Search Results 
+  <LI><A href="http://www.ietf.org/rfc/rfc3045.txt">[RFC3045]</A> Storing Vendor 
+  Information in the LDAP root DSE 
+  <LI><A href="http://www.ietf.org/rfc/rfc3062.txt">[RFC3062]</A> LDAP Password 
+  Modify Extended Operation 
+  <LI><A href="http://www.ietf.org/rfc/rfc3088.txt">[RFC3088]</A> OpenLDAP<A 
+  href="http://nagoya.apache.org/wiki/apachewiki.cgi?action=edit&amp;id=OpenLDAP">?</A> 
+  Root Service An experimental LDAP referral service 
+  <LI><A href="http://www.ietf.org/rfc/rfc3112.txt">[RFC3112]</A> LDAP 
+  Authentication Password Schema 
+  <LI><A href="http://www.ietf.org/rfc/rfc3296.txt">[RFC3296]</A> Named 
+  Subordinate References in Lightweight Directory Access Protocol (LDAP) 
+  Directories 
+  <LI><A href="http://www.ietf.org/rfc/rfc3383.txt">[RFC3383]</A> Internet 
+  Assigned Numbers Authority (IANA) considerations for the Lightweight Directory 
+  Access Protocol (LDAP) </LI></UL>
+<P>
+<P><STRONG>Section 0.1 : Criteria</STRONG> 
+<P>We feel that this project has a good chance for success as the following 
+project aspects are carefully considered : 
+<P><EM>Meritocracy:</EM> The project will be meritocratic - the usual Apache 
+meritocracy rules would apply. 
+<P><EM>Community:</EM> The user community for this project is potentially 
+massive. The initial developer community for this project consists of developers 
+from Apache and LDAPd projects. The aim is for this community to grow 
+considerably once this project enters the incubator. 
+<P><EM>Core Developers:</EM> The initial developers are listed further below 
+within this document and consist of some existing Apache committers together 
+with committers from the LDAPd Group. 
+<P><EM>Alignment:</EM> There is clear alignment with many existing Apache 
+projects. From Jakarta projects such as Tomcat, James and Slide for embedding 
+LDAP. The LDAP DSML standards will eventually require the use of several XML 
+projects. Other projects like OpenJms<A 
+href="http://nagoya.apache.org/wiki/apachewiki.cgi?action=edit&amp;id=OpenJms">?</A>, 
+which currently are not Apache projects but very well may be in the future will 
+be used for things like replication. Jdbm likewise is used for building Btree 
+based indices for custom databases. Also projects like Apache Xindice may be 
+leveraged for an XML based backend or for DSML enabling subsystems of an LDAP 
+server. 
+<P>We see the Apache Directory Project as a separate project to existing Apache 
+projects, serving several roles 
+<UL>
+  <LI>Home for Apache Directory Client APIs and Client Scripts 
+  <LI>Home for Apache JNDI Providers for Various Directory Namespaces 
+  <LI>Home for Apache Directory Servers 
+  <LI>May also become home to an ASN.1 Encoding/Decoding<A 
+  href="http://nagoya.apache.org/wiki/apachewiki.cgi?action=edit&amp;id=ApacheDirectoryProject/Decoding">?</A> 
+  Library </LI></UL>
+<P>
+<P><STRONG>Section 0.2 : Warning Signs</STRONG> 
+<P>We feel this project has a good chance for success as the following warning 
+signs do not apply to the project we are proposing: 
+<P><EM>Orphaned products:</EM> This project is starting with an existing code 
+base which using lots of the high quality open source code out there which is 
+ASF/BSD licensed. 
+<P><EM>Inexperience with open source:</EM> The initial community is made up of 
+existing Apache and LDAPd Group committers exclusively so the open source 
+experience is there to varying degrees. 
+<P><EM>Reliance on salaried developers:</EM> None of the initial developers are 
+currently paid to work on the Directory Project. 
+<P><EM>No ties to other Apache products:</EM> The Apache Directory Project is 
+complementary to existing technologies at Apache. LDAPd currently uses Avalon 
+and will eventually be used by james. LDAPd will eventually integrate into 
+Geronimo. The Apache Directory Project will integrate with, and possibly 
+subsume, Jakarta Commons Naming. 
+<P><EM>A fascination with the Apache brand:</EM> The committers are interested 
+in developing a healthy open source community around ASF/BSD licensed directory 
+servers and their clients along with other JNDI accessible name spaces. Is 
+Apache the right place? We think it is. Several Apache folks have already shown 
+interest in LDAPd, the seed code base to be used for this project. In fact the 
+LDAPd Group was initially approached by Apache to submit an Incubator proposal. 
+LDAPd Group members voted unanimously to donate the code to Apache in an effort 
+to build the next flagship server at Apache and much more. 
+<P>
+<P><STRONG>Section 1 : Scope of the Project</STRONG> 
+<P>There are multiple goals for this Apache project: 
+<P>
+<UL>
+  <LI>Promote a healthy open source community! 
+  <LI>Promote a language agnostic environment for both client side and server 
+  side endeavors. 
+  <LI>A one stop location for all directory and naming needs on any platform or 
+  any language. 
+  <UL>
+    <LI>client APIs 
+    <LI>clients 
+    <LI>JNDI providers for Java and other namespaces. 
+    <LI>May also include an LDAP protocol correctness and stress testing suite 
+    in the future. </LI></UL>
+  <LI>Provide servers in embeddable configurations. 
+  <LI>Provide servers in standalone configurations as UNIX daemons or NT 
+  Services. 
+  <LI>Provide support for Directory Server embedding or integration with 
+  existing Apache servers like httpd, Slide, Tomcat, James and Geronimo. 
+</LI></UL>
+<P>
+<P><STRONG>Section 2 : Initial Source</STRONG> 
+<P>The initial code base from which to create the Apache Directory repository is 
+contained mostly at Sourceforge under the LDAPd project accessible <A 
+href="http://sourceforge.net/projects/ldapd">[here]</A>. This code base must 
+assign copyright to the Apache Software Foundation. The code base will need to 
+be licensed under The Apache Software Foundation license. The license file in 
+every subproject will be changed to the Apache license. The current license is 
+already an Apache "style" license, so this change is basically a change to name 
+The ASF as the owner. 
+<P>The proposed TLP (after incubation) would have an one or more directory 
+servers with multiple datastore backends, a JNDI context for J2EE configuration, 
+JNDI service provider(s) for LDAP and other transports, State and Object 
+Factories suitable for use in the various Context/DirContext<A 
+href="http://nagoya.apache.org/wiki/apachewiki.cgi?action=edit&amp;id=ApacheDirectoryProject/DirContext">?</A> 
+implementations, etc. 
+<P>Beside source code the LDAPd Group must transfer its IANA assigned ASN.1 
+Object Identifier to Apache Software Foundation. 
+<P><STRONG>Section 3 : ASF Resources to be Created</STRONG> 
+<P><EM>Section 3.1 : Mailing Lists</EM> 
+<P>
+<UL>
+  <LI>directory-dev@incubator.apache.org </LI></UL>
+<P><EM>Section 3.2 : CVS Repositories</EM> 
+<P>
+<UL>
+  <LI>incubator-directory </LI></UL>
+<P><EM>Section 3.3 : Bugzilla or (preferably) Jira</EM> 
+<P>
+<UL>
+  <LI>directory </LI></UL>
+<P>
+<P><STRONG>Section 4 : Initial Set of Committers</STRONG> 
+<P>All contributors must sign and submit a Contributors License Agreement. The 
+following individuals are the contributors, and have signed and sent the 
+agreement at one time or another: 
+<P>
+<UL>
+  <LI>Alex Karasulu 
+  <LI>Phil Steitz 
+  <LI>Robb Penoyer 
+  <LI>Noel Bergman 
+  <LI>Jeff Machols 
+  <LI>Henri Yandell 
+  <LI>Wes McKean<A 
+  href="http://nagoya.apache.org/wiki/apachewiki.cgi?action=edit&amp;id=McKean">?</A> 
+  </LI></UL>
+<P>
+<P><STRONG>Section 5 : Apache Sponsoring Individuals</STRONG> 
+<P>
+<UL>
+  <LI>Nicola Ken Barozzi (Apache Incubator) 
+  <LI>Noel J. Bergman (Apache James) 
+  <LI>Henri Yandell (Jakarta Commons Naming) 
+  <LI>Stephen McConnell<A 
+  href="http://nagoya.apache.org/wiki/apachewiki.cgi?action=edit&amp;id=McConnell">?</A> 
+  (Apache Avalon) 
+  <LI>James Strachan (Apache Geronimo) </LI></UL>
+<P>
+<P><STRONG>Section 6 : Incubation Exit Criteria</STRONG> 
+<P>We feel this project should exit the incubator to a TLP using the domain name 
+directory.apache.org should the following goals be met: 
+<P><EM>Technical Goals:</EM> 
+<P>
+<UL>
+  <LI>Clean status with Apaches Continuous Integration System 
+  <LI>Website cross reference to existing Apache literature with respect to 
+  rules and regulations 
+  <LI>At a minimum a beta release and/or a series of Release Candidates for a 
+  directory server and its clients. 
+  <LI>At least one server that complies with <A 
+  href="http://www.ietf.org/rfc/rfc2251.txt">[RFC2251]</A> </LI></UL>
+<P><EM>Non-Technical Goals:</EM> 
+<P>
+<UL>
+  <LI>List presence and monitoring in wider Apache communities 
+  <LI>Website cross reference to existing Apache literarature with respect to 
+  rules and regulations 
+  <LI>Initial integration plan and cooperation with Geronimo, and James 
+  <LI>Member presence on the licensing@apache list 
+  <LI>More Apache or non-Apache committers who are actively modifying source 
+  code </LI></UL>
+<HR>
+
+<FORM action=apachewiki.cgi method=post><A 
+href="http://nagoya.apache.org/wiki/apachewiki.cgi?HomePage">HomePage</A> | <A 
+href="http://nagoya.apache.org/wiki/apachewiki.cgi?RecentChanges">RecentChanges</A> 
+| <A 
+href="http://nagoya.apache.org/wiki/apachewiki.cgi?action=editprefs">Preferences</A><BR><A 
+href="http://nagoya.apache.org/wiki/apachewiki.cgi?action=edit&amp;id=ApacheDirectoryProject">Edit 
+text of this page</A> | <A 
+href="http://nagoya.apache.org/wiki/apachewiki.cgi?action=history&amp;id=ApacheDirectoryProject">View 
+other revisions</A><BR>Last edited September 30, 2003 7:59 am <A 
+href="http://nagoya.apache.org/wiki/apachewiki.cgi?action=browse&amp;diff=1&amp;id=ApacheDirectoryProject">(diff)</A><BR>Search: 
+<INPUT name=search><INPUT type=hidden value=1 name=dosearch> 
+</FORM></BODY></HTML>

Modified: directory/project/trunk/site/src/site/xdoc/community/process/pmc.xml
URL: http://svn.apache.org/viewvc/directory/project/trunk/site/src/site/xdoc/community/process/pmc.xml?rev=578163&r1=578162&r2=578163&view=diff
==============================================================================
--- directory/project/trunk/site/src/site/xdoc/community/process/pmc.xml (original)
+++ directory/project/trunk/site/src/site/xdoc/community/process/pmc.xml Fri Sep 21 08:10:08 2007
@@ -11,8 +11,8 @@
         For now because we are within the incubator we do not have a PMC but 
         the incubator's equivalent of one for a incubated project.  Until we
         exit the incubator the this PPMC will operate using the PMC guidelines
-        below.
-      </p>
+        below.
+      </p>
     </section>
     
 	  <section name="Informative material only">

Modified: directory/project/trunk/site/src/site/xdoc/community/who/akarasulu.xml
URL: http://svn.apache.org/viewvc/directory/project/trunk/site/src/site/xdoc/community/who/akarasulu.xml?rev=578163&r1=578162&r2=578163&view=diff
==============================================================================
--- directory/project/trunk/site/src/site/xdoc/community/who/akarasulu.xml (original)
+++ directory/project/trunk/site/src/site/xdoc/community/who/akarasulu.xml Fri Sep 21 08:10:08 2007
@@ -13,7 +13,7 @@
         Alex wrote the LDAPd pure Java LDAP server and founded the LDAPd Group.
         He eventually disolved the LDAPd Group and proposed and founded the 
         Directory Project at Apache which absorbed the code base to the LDAPd 
-        Directory Server.
+        Directory Server.
       </p>
       
       <subsection name="Some Background">
@@ -93,7 +93,7 @@
             <td>
               This is the proposal submitted to the ASF to start the 
               Directory Project as an incubator project.
-            </td>
+            </td>
           </tr>
           
           <tr>
@@ -111,7 +111,7 @@
             </td>
             <td>
               Homepage where you can find resources on directory
-              technologies and other peices of information.
+              technologies and other peices of information.
             </td>
           </tr>
           

Modified: directory/project/trunk/site/src/site/xdoc/community/who/index.xml
URL: http://svn.apache.org/viewvc/directory/project/trunk/site/src/site/xdoc/community/who/index.xml?rev=578163&r1=578162&r2=578163&view=diff
==============================================================================
--- directory/project/trunk/site/src/site/xdoc/community/who/index.xml (original)
+++ directory/project/trunk/site/src/site/xdoc/community/who/index.xml Fri Sep 21 08:10:08 2007
@@ -1,41 +1,41 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<document>
-  <properties>
-    <author email="akarasulu@apache.org">Alex Karasulu</author>
-    <title>Apache Directory Project: Who we are</title>
-  </properties> 
-  <body>
-    <section name="Active Committers">
-      <p>
-      The current Directory committers are: 
-      adc, akarasulu, bayard, bloritsch, brett, 
-      elecharny, erodriguez, ersiner, jmachols, niklas, noel, 
-      psteitz, szoerner, trustin, vtence, wesmckean
-      </p>
-    </section>
-    <section name="Inactive Committers">
-      <p>
-      The current inactive Directory committers (an inactive committer is
-      someone who hasn't done a cvs commit in three months, or hasn't
-      bothered to move himself from this list to the one above) are:
-      none yet.
-      </p>
-    </section>
-    <section name="Emeritus Committers">
-      <p>
-       The current emeritus committers (an emeritus committer is
-      someone who is not active within the Directory Project anymore)
-      are: none yet.
-      </p>
-    </section>
-    <section name="Contributors">
-      <p>
-      Contributors are: Nick Faiz
-      </p>
-      <p>
-      If you are a contributor but are not listed, submit a patch for the site docs.
-      </p>
-    </section>
-  </body>
-
-</document>
+<?xml version="1.0" encoding="UTF-8"?>
+<document>
+  <properties>
+    <author email="akarasulu@apache.org">Alex Karasulu</author>
+    <title>Apache Directory Project: Who we are</title>
+  </properties> 
+  <body>
+    <section name="Active Committers">
+      <p>
+      The current Directory committers are: 
+      adc, akarasulu, bayard, bloritsch, brett, 
+      elecharny, erodriguez, ersiner, jmachols, niklas, noel, 
+      psteitz, szoerner, trustin, vtence, wesmckean
+      </p>
+    </section>
+    <section name="Inactive Committers">
+      <p>
+      The current inactive Directory committers (an inactive committer is
+      someone who hasn't done a cvs commit in three months, or hasn't
+      bothered to move himself from this list to the one above) are:
+      none yet.
+      </p>
+    </section>
+    <section name="Emeritus Committers">
+      <p>
+       The current emeritus committers (an emeritus committer is
+      someone who is not active within the Directory Project anymore)
+      are: none yet.
+      </p>
+    </section>
+    <section name="Contributors">
+      <p>
+      Contributors are: Nick Faiz
+      </p>
+      <p>
+      If you are a contributor but are not listed, submit a patch for the site docs.
+      </p>
+    </section>
+  </body>
+
+</document>

Modified: directory/project/trunk/site/src/site/xdoc/community/who/jmachols.xml
URL: http://svn.apache.org/viewvc/directory/project/trunk/site/src/site/xdoc/community/who/jmachols.xml?rev=578163&r1=578162&r2=578163&view=diff
==============================================================================
--- directory/project/trunk/site/src/site/xdoc/community/who/jmachols.xml (original)
+++ directory/project/trunk/site/src/site/xdoc/community/who/jmachols.xml Fri Sep 21 08:10:08 2007
@@ -11,37 +11,37 @@
       </p>
       
       <p> 
-        Jeff is one of the original members of the LDAPd group founded by 
-        Alex Karasulu. He came into the Apache Software Foundation when it 
+        Jeff is one of the original members of the LDAPd group founded by 
+        Alex Karasulu. He came into the Apache Software Foundation when it 
         absorbed the LDAPd source code and members.
       </p>
     </section>
     
     <section name="Background">
       <p> 
-        Jeff had the good fortune of becoming associated with Alex Karasulu 
-        at a pivotal time early in 2002. Alex had some frustrations with LDAP 
-        due to deficiencies in all of the servers he used and was toying with 
-        the idea of writing one. Jeff's initial role was simply to serve as a 
-        sounding board for ideas. As time went on and he heard not only the 
-        ideas but, the passion of Alex about this endeavor, Jeff eagerly
+        Jeff had the good fortune of becoming associated with Alex Karasulu 
+        at a pivotal time early in 2002. Alex had some frustrations with LDAP 
+        due to deficiencies in all of the servers he used and was toying with 
+        the idea of writing one. Jeff's initial role was simply to serve as a 
+        sounding board for ideas. As time went on and he heard not only the 
+        ideas but, the passion of Alex about this endeavor, Jeff eagerly
         accepted Alex's invitation to become involved in the LDAPd project.
       </p>
       
-      <p> 
-        Jeff's primary focus on the project is the client side of LDAP. After a 
-        struggle implementing Unix user authentication with other LDAP servers 
-        and clients, he saw additional opportunity for improvement. The goal of 
-        the client and LDAP common sub-project is to provide a set LDAP tools 
+      <p> 
+        Jeff's primary focus on the project is the client side of LDAP. After a 
+        struggle implementing Unix user authentication with other LDAP servers 
+        and clients, he saw additional opportunity for improvement. The goal of 
+        the client and LDAP common sub-project is to provide a set LDAP tools 
         to match the ease of use, flexibility and rich features of Eve. 
       </p>
       
       <p> 
-        Jeff's also worked closely with the Apache Infrastructure team, 
-        especially Noel Bergman, to import the LDAPd CVS source code into 
-        Subversion. The Apache Directory project was one of the first to 
+        Jeff's also worked closely with the Apache Infrastructure team, 
+        especially Noel Bergman, to import the LDAPd CVS source code into 
+        Subversion. The Apache Directory project was one of the first to 
         implement Subversion. 
-      </p>
+      </p>
     </section>
   </body>
 </document>



Mime
View raw message