You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@river.apache.org by ge...@apache.org on 2007/01/02 18:13:15 UTC
svn commit: r491855 [2/3] - in /incubator/river/site: ./ bin/ docs/ lib/
xdocs/ xdocs/images/ xdocs/stylesheets/
Added: incubator/river/site/docs/license.html
URL: http://svn.apache.org/viewvc/incubator/river/site/docs/license.html?view=auto&rev=491855
==============================================================================
--- incubator/river/site/docs/license.html (added)
+++ incubator/river/site/docs/license.html Tue Jan 2 09:13:12 2007
@@ -0,0 +1,411 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+
+<!--
+Licensed to the Apache Software Foundation (ASF) under one or more
+contributor license agreements. See the NOTICE file distributed with
+this work for additional information regarding copyright ownership.
+The ASF licenses this file to You 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.
+-->
+
+
+<!-- start the processing -->
+ <!-- ====================================================================== -->
+ <!-- GENERATED FILE, DO NOT EDIT, EDIT THE XML FILE IN xdocs INSTEAD! -->
+ <!-- Main Page Section -->
+ <!-- ====================================================================== -->
+ <html>
+ <head>
+ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"/>
+
+ <meta name="author" value="
+ Documentation Team">
+ <meta name="email" value="river-dev@incbator.apache.org">
+
+
+
+
+
+
+
+ <title>Apache River - Apache License</title>
+
+
+
+ <link rel="stylesheet" type="text/css" href="site.css"/>
+ </head>
+
+ <body>
+ <table width="100%" cellspacing="0">
+ <!-- TOP IMAGE -->
+ <tr>
+ <td align='LEFT'>
+ <table><tr><td>
+ <td>
+<a href="http://incubator.apache.org/river"><img src="./images/harmony-logo-new.png" alt="Apache River (we need a logo)" /></a>
+</td>
+</td>
+ </td></tr></table>
+ </td>
+ <td align='RIGHT'>
+ <a href="http://incubator.apache.org/river">
+ <img src="http://harmony.apache.org/images/apache-incubator-logo.png"
+ alt="Apache River (we need a logo)" /></a>
+ </td>
+ </tr>
+ </table>
+ <table width="100%" cellspacing="4">
+ <tr><td colspan="2">
+ <hr noshade="" size="1"/>
+ </td></tr>
+
+ <tr>
+ <!-- LEFT SIDE NAVIGATION -->
+ <td class="menuItem" width="20%" nowrap="true">
+
+ <!-- special ACon Logo - leave here for next time
+ <a href="http://www.us.apachecon.com/">
+ <img src="http://www.apache.org/ads/ApacheCon/240x120-2006-us.gif"
+ alt="ApacheCon US 2006" />
+ </a> -->
+
+ <!-- regular menu -->
+
+
+ <!-- ============================================================ -->
+
+ <p class="menuItem"><strong>General</strong></p>
+ <ul>
+ <li class="menuItem"> <a href="./index.html">Home</a>
+</li>
+
+
+ <li class="menuItem"> <a href="./license.html">License</a>
+</li>
+
+
+ <li class="menuItem"> <a href="./contribution_policy.html">Contribution Policy</a>
+</li>
+
+
+ <li class="menuItem"> <a href="./guidelines.html">Project Guidelines</a>
+</li>
+
+
+ <li class="menuItem"> <a href="http://www.apache.org/">ASF</a>
+</li>
+
+
+ <li class="menuItem"> <a href="./downloads.html">Downloads</a>
+</li>
+
+
+
+ </ul>
+ <p class="menuItem"><strong>Community</strong></p>
+ <ul>
+ <li class="menuItem"> <a href="./get-involved.html">Get Involved</a>
+</li>
+
+
+ <li class="menuItem"> <a href="./contributors.html">Committers</a>
+</li>
+
+
+ <li class="menuItem"> <a href="./mailing.html">Mailing Lists</a>
+</li>
+
+
+ <li class="menuItem"> <a href="./documentation.html">Documentation</a>
+</li>
+
+
+ <li class="menuItem"> <a href="http://wiki.apache.org/river">Wiki</a>
+</li>
+
+
+
+ </ul>
+ <p class="menuItem"><strong>Development</strong></p>
+ <ul>
+ <li class="menuItem"> <a href="./roadmap.html">Road Map / TODO</a>
+</li>
+
+
+ <li class="menuItem"> <a href="./svn.html">Source Code</a>
+</li>
+
+
+ <li class="menuItem"> <a href="http://issues.apache.org/jira/browse/RIVER">JIRA</a>
+</li>
+
+
+
+ </ul>
+ <p class="menuItem"><strong>Subcomponents</strong></p>
+ <ul>
+
+ </ul>
+ </td>
+ <td width="80%" valign="top"><a name="top"></a>
+ <h1>
+ <a name="Apache License v2.0">Apache License v2.0</a>
+ </h1>
+ <pre>
+
+
+
+ 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.
+
+
+ </pre>
+ <p><a href="#top">Back to top</a></p>
+
+ </td>
+ </tr>
+
+ <!-- FOOTER -->
+ <tr><td colspan="2">
+ <hr noshade="" size="1"/>
+ </td></tr>
+ <tr><td colspan="2">
+ <div class="special"><em>
+ Copyright © 2003-2006, The Apache Software Foundation
+ </em></div>
+ </td></tr>
+ </table>
+ </body>
+ </html>
+<!-- end the processing -->
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Added: incubator/river/site/docs/mailing.html
URL: http://svn.apache.org/viewvc/incubator/river/site/docs/mailing.html?view=auto&rev=491855
==============================================================================
--- incubator/river/site/docs/mailing.html (added)
+++ incubator/river/site/docs/mailing.html Tue Jan 2 09:13:12 2007
@@ -0,0 +1,292 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+
+<!--
+Licensed to the Apache Software Foundation (ASF) under one or more
+contributor license agreements. See the NOTICE file distributed with
+this work for additional information regarding copyright ownership.
+The ASF licenses this file to You 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.
+-->
+
+
+<!-- start the processing -->
+ <!-- ====================================================================== -->
+ <!-- GENERATED FILE, DO NOT EDIT, EDIT THE XML FILE IN xdocs INSTEAD! -->
+ <!-- Main Page Section -->
+ <!-- ====================================================================== -->
+ <html>
+ <head>
+ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"/>
+
+ <meta name="author" value="Documentation Team">
+ <meta name="email" value="river-dev@incubator.apache.org">
+
+
+
+
+
+
+
+ <title>Apache River - Apache Mailing Lists</title>
+
+
+
+ <link rel="stylesheet" type="text/css" href="site.css"/>
+ </head>
+
+ <body>
+ <table width="100%" cellspacing="0">
+ <!-- TOP IMAGE -->
+ <tr>
+ <td align='LEFT'>
+ <table><tr><td>
+ <td>
+<a href="http://incubator.apache.org/river"><img src="./images/harmony-logo-new.png" alt="Apache River (we need a logo)" /></a>
+</td>
+</td>
+ </td></tr></table>
+ </td>
+ <td align='RIGHT'>
+ <a href="http://incubator.apache.org/river">
+ <img src="http://harmony.apache.org/images/apache-incubator-logo.png"
+ alt="Apache River (we need a logo)" /></a>
+ </td>
+ </tr>
+ </table>
+ <table width="100%" cellspacing="4">
+ <tr><td colspan="2">
+ <hr noshade="" size="1"/>
+ </td></tr>
+
+ <tr>
+ <!-- LEFT SIDE NAVIGATION -->
+ <td class="menuItem" width="20%" nowrap="true">
+
+ <!-- special ACon Logo - leave here for next time
+ <a href="http://www.us.apachecon.com/">
+ <img src="http://www.apache.org/ads/ApacheCon/240x120-2006-us.gif"
+ alt="ApacheCon US 2006" />
+ </a> -->
+
+ <!-- regular menu -->
+
+
+ <!-- ============================================================ -->
+
+ <p class="menuItem"><strong>General</strong></p>
+ <ul>
+ <li class="menuItem"> <a href="./index.html">Home</a>
+</li>
+
+
+ <li class="menuItem"> <a href="./license.html">License</a>
+</li>
+
+
+ <li class="menuItem"> <a href="./contribution_policy.html">Contribution Policy</a>
+</li>
+
+
+ <li class="menuItem"> <a href="./guidelines.html">Project Guidelines</a>
+</li>
+
+
+ <li class="menuItem"> <a href="http://www.apache.org/">ASF</a>
+</li>
+
+
+ <li class="menuItem"> <a href="./downloads.html">Downloads</a>
+</li>
+
+
+
+ </ul>
+ <p class="menuItem"><strong>Community</strong></p>
+ <ul>
+ <li class="menuItem"> <a href="./get-involved.html">Get Involved</a>
+</li>
+
+
+ <li class="menuItem"> <a href="./contributors.html">Committers</a>
+</li>
+
+
+ <li class="menuItem"> <a href="./mailing.html">Mailing Lists</a>
+</li>
+
+
+ <li class="menuItem"> <a href="./documentation.html">Documentation</a>
+</li>
+
+
+ <li class="menuItem"> <a href="http://wiki.apache.org/river">Wiki</a>
+</li>
+
+
+
+ </ul>
+ <p class="menuItem"><strong>Development</strong></p>
+ <ul>
+ <li class="menuItem"> <a href="./roadmap.html">Road Map / TODO</a>
+</li>
+
+
+ <li class="menuItem"> <a href="./svn.html">Source Code</a>
+</li>
+
+
+ <li class="menuItem"> <a href="http://issues.apache.org/jira/browse/RIVER">JIRA</a>
+</li>
+
+
+
+ </ul>
+ <p class="menuItem"><strong>Subcomponents</strong></p>
+ <ul>
+
+ </ul>
+ </td>
+ <td width="80%" valign="top"><a name="top"></a>
+ <h1>
+ <a name="Apache River Mailing Lists">Apache River Mailing Lists</a>
+ </h1>
+ <p>
+Apache Harmony mailing lists operate under the following terms :
+</p>
+ <blockquote>
+This forum has been created for public communication about projects
+of The Apache Software Foundation (the "Foundation"), a Delaware
+nonprofit corporation classified as a public charity under 501(c)(3).
+All communication intentionally submitted to the Foundation on this
+forum is considered a Contribution to the Foundation unless otherwise
+noted in the communication. The terms and conditions that apply to
+your Contributions are defined by either a contributor license
+agreement (CLA) signed by you and/or your employer or, if no such CLA
+is on file at the Foundation, by the terms and conditions of
+Contributions as defined by the Apache License, Version 2.0.
+</blockquote>
+ <p>
+Further :
+</p>
+ <blockquote>
+<ul>
+<li>
+If you do not wish your post to be a Contribution, we would prefer that you do not post it. However, in the
+event that you do, please mark as "NOT A CONTRIBUTION" at the top of the posting.
+</li>
+<li>
+Do not post any code that is not your original work, or code that you do not have
+clear authorization to contribute.
+</li>
+<li>
+Do not engage in detailed discussion of any implementation that you have been exposed
+to unless such implementation is available to everyone under an open source license or is
+your own implementation.
+</li>
+</ul>
+</blockquote>
+ <p>
+There are currently three publicly available mailing lists for River :
+</p>
+
+ <h2>
+ <a name="Developer Mailing List">Developer Mailing List</a>
+ </h2>
+
+ <p>The developer mailing list is used by the developers to discuss
+plans, make decisions, vote on technical issues, etc.
+</p>
+ <ul>
+ <li><a href="mailto:river-dev-subscribe@incubator.apache.org">Subscribe</a> to river-dev@incubator.apache.org</li>
+ <li><a href="mailto:river-dev-unsubscribe@incubator.apache.org">Unsubscribe</a> from river-dev@incubator.apache.org</li>
+ <li>View the <a href="http://mail-archives.apache.org/mod_mbox/incubator-river-dev/">river-dev@incubator.apache.org archives</a></li>
+</ul>
+
+
+ <h2>
+ <a name="User Mailing List">User Mailing List</a>
+ </h2>
+
+ <p>The user mailing list is used by the users to discuss using the
+project software.
+</p>
+ <ul>
+ <li><a href="mailto:river-user-subscribe@incubator.apache.org">Subscribe</a> to river-user@incubator.apache.org</li>
+ <li><a href="mailto:river-user-unsubscribe@incubator.apache.org">Unsubscribe</a> from river-user@incubator.apache.org</li>
+ <li>View the <a href="http://mail-archives.apache.org/mod_mbox/incubator-river-user/">river-user@incubator.apache.org archives</a></li>
+</ul>
+
+
+ <h2>
+ <a name="Source Control Mailing List">Source Control Mailing List</a>
+ </h2>
+
+ <p>This list receives notifications (with diffs) every time a change is
+committed to the River source tree. It also receives change notices
+for changes to the River Wiki and whenever issues are added to or
+updated in our
+<a href="http://issues.apache.org/jira/browse/RIVER">JIRA issue tracking system</a>.</p>
+ <ul>
+ <li><a href="mailto:river-commits-subscribe@incubator.apache.org">Subscribe</a> to river-commits@incubator.apache.org</li>
+ <li><a href="mailto:river-commits-unsubscribe@incubator.apache.org">Unsubscribe</a> from river-commits@incubator.apache.org</li>
+ <li>View the <a href="http://mail-archives.apache.org/mod_mbox/incubator-river-commits/">river-commits@incubator.apache.org archives</a></li>
+</ul>
+
+
+ <h2>
+ <a name="Other Mailing Lists">Other Mailing Lists</a>
+ </h2>
+
+ <p>The Harmony PMC has a mailing list to resolve any administrative issues,
+This list is limited to PMC members (most committers on the project).</p>
+
+ <p><a href="#top">Back to top</a></p>
+
+ </td>
+ </tr>
+
+ <!-- FOOTER -->
+ <tr><td colspan="2">
+ <hr noshade="" size="1"/>
+ </td></tr>
+ <tr><td colspan="2">
+ <div class="special"><em>
+ Copyright © 2003-2006, The Apache Software Foundation
+ </em></div>
+ </td></tr>
+ </table>
+ </body>
+ </html>
+<!-- end the processing -->
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Added: incubator/river/site/docs/roadmap.html
URL: http://svn.apache.org/viewvc/incubator/river/site/docs/roadmap.html?view=auto&rev=491855
==============================================================================
--- incubator/river/site/docs/roadmap.html (added)
+++ incubator/river/site/docs/roadmap.html Tue Jan 2 09:13:12 2007
@@ -0,0 +1,232 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+
+<!--
+Licensed to the Apache Software Foundation (ASF) under one or more
+contributor license agreements. See the NOTICE file distributed with
+this work for additional information regarding copyright ownership.
+The ASF licenses this file to You 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.
+-->
+
+
+<!-- start the processing -->
+ <!-- ====================================================================== -->
+ <!-- GENERATED FILE, DO NOT EDIT, EDIT THE XML FILE IN xdocs INSTEAD! -->
+ <!-- Main Page Section -->
+ <!-- ====================================================================== -->
+ <html>
+ <head>
+ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"/>
+
+ <meta name="author" value="Documentation Team">
+ <meta name="email" value="river-dev@incubator.apache.org">
+
+
+
+
+
+
+
+ <title>Apache River - Project Roadmap</title>
+
+
+
+ <link rel="stylesheet" type="text/css" href="site.css"/>
+ </head>
+
+ <body>
+ <table width="100%" cellspacing="0">
+ <!-- TOP IMAGE -->
+ <tr>
+ <td align='LEFT'>
+ <table><tr><td>
+ <td>
+<a href="http://incubator.apache.org/river"><img src="./images/harmony-logo-new.png" alt="Apache River (we need a logo)" /></a>
+</td>
+</td>
+ </td></tr></table>
+ </td>
+ <td align='RIGHT'>
+ <a href="http://incubator.apache.org/river">
+ <img src="http://harmony.apache.org/images/apache-incubator-logo.png"
+ alt="Apache River (we need a logo)" /></a>
+ </td>
+ </tr>
+ </table>
+ <table width="100%" cellspacing="4">
+ <tr><td colspan="2">
+ <hr noshade="" size="1"/>
+ </td></tr>
+
+ <tr>
+ <!-- LEFT SIDE NAVIGATION -->
+ <td class="menuItem" width="20%" nowrap="true">
+
+ <!-- special ACon Logo - leave here for next time
+ <a href="http://www.us.apachecon.com/">
+ <img src="http://www.apache.org/ads/ApacheCon/240x120-2006-us.gif"
+ alt="ApacheCon US 2006" />
+ </a> -->
+
+ <!-- regular menu -->
+
+
+ <!-- ============================================================ -->
+
+ <p class="menuItem"><strong>General</strong></p>
+ <ul>
+ <li class="menuItem"> <a href="./index.html">Home</a>
+</li>
+
+
+ <li class="menuItem"> <a href="./license.html">License</a>
+</li>
+
+
+ <li class="menuItem"> <a href="./contribution_policy.html">Contribution Policy</a>
+</li>
+
+
+ <li class="menuItem"> <a href="./guidelines.html">Project Guidelines</a>
+</li>
+
+
+ <li class="menuItem"> <a href="http://www.apache.org/">ASF</a>
+</li>
+
+
+ <li class="menuItem"> <a href="./downloads.html">Downloads</a>
+</li>
+
+
+
+ </ul>
+ <p class="menuItem"><strong>Community</strong></p>
+ <ul>
+ <li class="menuItem"> <a href="./get-involved.html">Get Involved</a>
+</li>
+
+
+ <li class="menuItem"> <a href="./contributors.html">Committers</a>
+</li>
+
+
+ <li class="menuItem"> <a href="./mailing.html">Mailing Lists</a>
+</li>
+
+
+ <li class="menuItem"> <a href="./documentation.html">Documentation</a>
+</li>
+
+
+ <li class="menuItem"> <a href="http://wiki.apache.org/river">Wiki</a>
+</li>
+
+
+
+ </ul>
+ <p class="menuItem"><strong>Development</strong></p>
+ <ul>
+ <li class="menuItem"> <a href="./roadmap.html">Road Map / TODO</a>
+</li>
+
+
+ <li class="menuItem"> <a href="./svn.html">Source Code</a>
+</li>
+
+
+ <li class="menuItem"> <a href="http://issues.apache.org/jira/browse/RIVER">JIRA</a>
+</li>
+
+
+
+ </ul>
+ <p class="menuItem"><strong>Subcomponents</strong></p>
+ <ul>
+
+ </ul>
+ </td>
+ <td width="80%" valign="top"><a name="top"></a>
+ <h1>
+ <a name="Roadmap and TODO">Roadmap and TODO</a>
+ </h1>
+ <p>
+ Are roadmap and goals are always subject to discussion on the
+ <a href="mailing.html">developer's list.</a> As new people join with new focus and
+ interests, the things we do as a project adapt.
+ </p>
+ <p>
+ If you have an idea, come join the community and talk about it. Note that you will
+ need to subscribe to the <a href="mailing.html">mail list</a>
+ </p>
+ <p><a href="#top">Back to top</a></p>
+ <h1>
+ <a name="High-Level Roadmap">High-Level Roadmap</a>
+ </h1>
+ <p>
+ </p>
+ <p><a href="#top">Back to top</a></p>
+ <h1>
+ <a name="TODO List">TODO List</a>
+ </h1>
+ <p>
+ The following is a collection of things that the project community
+ has listed as needing to be done. This list is not exhaustive. If
+ you wish to add an item to this list, or discuss or even volunteer
+ to work on an item, please join us on the <a href="mailing.html">River
+ mail list.</a>
+ </p>
+ <p>
+ The following sections describe the high-level areas of effort, and
+ tasks that have been identified for those areas.
+ </p>
+ <p><a href="#top">Back to top</a></p>
+
+ </td>
+ </tr>
+
+ <!-- FOOTER -->
+ <tr><td colspan="2">
+ <hr noshade="" size="1"/>
+ </td></tr>
+ <tr><td colspan="2">
+ <div class="special"><em>
+ Copyright © 2003-2006, The Apache Software Foundation
+ </em></div>
+ </td></tr>
+ </table>
+ </body>
+ </html>
+<!-- end the processing -->
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Added: incubator/river/site/docs/site.css
URL: http://svn.apache.org/viewvc/incubator/river/site/docs/site.css?view=auto&rev=491855
==============================================================================
--- incubator/river/site/docs/site.css (added)
+++ incubator/river/site/docs/site.css Tue Jan 2 09:13:12 2007
@@ -0,0 +1,242 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You 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.
+ */
+
+body {
+ background-color: white;
+ color: black;
+ text-align: left;
+ text-align: left;
+ font: "Times New Roman", serif;
+}
+
+.menuItem {
+ vertical-align: top;
+ padding: 0pt;
+ margin-top: 4pt;
+ margin-bottom: 4pt;
+ margin-right: 0pt;
+ margin-left: 0pt;
+}
+
+h1 {
+ font-family: Arial, helvetica, sans-serif;
+ font-weight: bold;
+ font-size: 12pt;
+ background-color: #525D76;
+ color: white;
+ text-indent: 2pt;
+ margin-left: 0pt;
+}
+
+h2 {
+ font-family: Arial, helvetica, sans-serif;
+ font-weight: bold;
+ font-size: 12pt;
+ background-color: #828DA6;
+ color: white;
+ text-indent: 2pt;
+ margin-left: 10pt;
+}
+
+h3 {
+ font-weight: bold;
+ margin-left: 20pt;
+ margin-top: 5pt;
+ margin-right: 0pt;
+ margin-bottom: 5pt;
+ text-transform: uppercase;
+ font-size: 11pt;
+}
+
+a:link {
+ color:#525D76;
+}
+
+p {
+ padding-left: 2pt;
+ margin-left: 20pt;
+}
+
+td.TableCell {
+ vertical-align: top;
+ text-align: left;
+ background-color: #a0ddf0;
+}
+
+th.TableHeading {
+ background-color: #039acc;
+ text-align: center;
+ color: black;
+ font-family: Arial, Helvetica, sans-serif;
+ padding: 2pt;
+}
+
+table {
+ margin-left: 0pt;
+ margin-right: 0pt;
+}
+
+img {
+ border: none;
+}
+
+pre {
+ background: #F3F5F7;
+ border: thin solid;
+ border-color: #828DA6;
+ padding: 12pt;
+ font-size: 11.0pt;
+ font-family: Courier;
+ margin-right: 10pt;
+ margin-left: 25pt;
+}
+
+.class {
+ font-weight: bold;
+ font-size: 10pt;
+ font-family: Arial;
+ border-top: none;
+ border-right: none;
+ border-left: none;
+ border-bottom: solid #525D76 2px;
+}
+
+.special {
+ font-weight: bold;
+ text-align: center;
+ color: #525D76;
+ margin-top: 3pt;
+ margin-bottom: 3pt;
+ font-family: Arial, helvetica, sans-serif;
+ font-size: 10pt;
+}
+
+.backtotop {
+ font-weight: bold;
+ margin-left: 0pt;
+}
+
+.note {
+ color: red;
+ font-weight: bolder;
+ font-family: Arial, helvetica, sans-serif;
+ font-size: 10pt;
+}
+
+.notetext {
+ padding-left: 20pt;
+ margin-top: 0pt;
+ margin-bottom: 0pt;
+ font-family: Arial, helvetica, sans-serif;
+ font-size: 10pt;
+}
+
+.example {
+ font-weight: bolder;
+ font-family: Arial, helvetica, sans-serif;
+ font-size: 10pt;
+}
+
+.exampletext {
+ margin-left: 40pt;
+}
+
+.TOCHeading {
+ font-weight: bold;
+ font-size: 12pt;
+ text-align: left;
+ color: #000000;
+ font-family: Arial, helvetica, sans-serif;
+ padding-left: 15px;
+ margin-bottom: 5pt;
+ margin-top: 5pt;
+ margin-left: 5px;
+ margin-right: 0pt;
+}
+
+.TOC {
+ font-size: 11pt;
+ text-indent: 15pt;
+ color: white;
+ padding-left: 15px;
+ margin-left: 5px;
+ margin-right: 0.00px;
+ margin-top: 0px;
+ margin-bottom: 0px;
+ font-family: Arial, helvetica, sans-serif;
+}
+
+.update {
+ color: #A9A9A9;
+ font-size: smaller;
+ font-style: italic;
+}
+
+li {
+ margin-left: 20pt;
+ padding-left: 1pt;
+ padding-top: 1pt;
+ padding-bottom: 1pt;
+ padding-right: 0pt;
+}
+
+ol li {
+ list-style-type: decimal;
+}
+
+ul li {
+ list-style-type: square;
+}
+
+li ul li {
+ list-style-type: disc;
+}
+
+dl {
+ margin: 5pt;
+}
+
+dd {
+ margin-left: 30pt;
+ margin-top: 5pt;
+ margin-right: 20pt;
+ margin-bottom: 5pt;
+ border-right: none;
+ border-bottom: none;
+ border-left: none;
+ border-top: none;
+ padding-bottom: 8px;
+}
+
+dd p {
+ margin-left: 0pt;
+}
+
+dt {
+ font-size: 10pt;
+ font-family: Arial, helvetica, sans-serif;
+ font-weight: bolder;
+ margin-left: 20pt;
+ margin-top: 5pt;
+ margin-right: 0pt;
+ margin-bottom: 5pt;
+ border-top: none;
+ border-right: none;
+ border-bottom: solid #828DA6 1px;
+ border-left: none;
+ padding-bottom: 3px;
+}
Added: incubator/river/site/docs/svn.html
URL: http://svn.apache.org/viewvc/incubator/river/site/docs/svn.html?view=auto&rev=491855
==============================================================================
--- incubator/river/site/docs/svn.html (added)
+++ incubator/river/site/docs/svn.html Tue Jan 2 09:13:12 2007
@@ -0,0 +1,252 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+
+<!--
+Licensed to the Apache Software Foundation (ASF) under one or more
+contributor license agreements. See the NOTICE file distributed with
+this work for additional information regarding copyright ownership.
+The ASF licenses this file to You 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.
+-->
+
+
+<!-- start the processing -->
+ <!-- ====================================================================== -->
+ <!-- GENERATED FILE, DO NOT EDIT, EDIT THE XML FILE IN xdocs INSTEAD! -->
+ <!-- Main Page Section -->
+ <!-- ====================================================================== -->
+ <html>
+ <head>
+ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"/>
+
+ <meta name="author" value="Documentation Team">
+ <meta name="email" value="river-dev@incubator.apache.org">
+
+
+
+
+
+
+
+ <title>Apache River - Apache River</title>
+
+
+
+ <link rel="stylesheet" type="text/css" href="site.css"/>
+ </head>
+
+ <body>
+ <table width="100%" cellspacing="0">
+ <!-- TOP IMAGE -->
+ <tr>
+ <td align='LEFT'>
+ <table><tr><td>
+ <td>
+<a href="http://incubator.apache.org/river"><img src="./images/harmony-logo-new.png" alt="Apache River (we need a logo)" /></a>
+</td>
+</td>
+ </td></tr></table>
+ </td>
+ <td align='RIGHT'>
+ <a href="http://incubator.apache.org/river">
+ <img src="http://harmony.apache.org/images/apache-incubator-logo.png"
+ alt="Apache River (we need a logo)" /></a>
+ </td>
+ </tr>
+ </table>
+ <table width="100%" cellspacing="4">
+ <tr><td colspan="2">
+ <hr noshade="" size="1"/>
+ </td></tr>
+
+ <tr>
+ <!-- LEFT SIDE NAVIGATION -->
+ <td class="menuItem" width="20%" nowrap="true">
+
+ <!-- special ACon Logo - leave here for next time
+ <a href="http://www.us.apachecon.com/">
+ <img src="http://www.apache.org/ads/ApacheCon/240x120-2006-us.gif"
+ alt="ApacheCon US 2006" />
+ </a> -->
+
+ <!-- regular menu -->
+
+
+ <!-- ============================================================ -->
+
+ <p class="menuItem"><strong>General</strong></p>
+ <ul>
+ <li class="menuItem"> <a href="./index.html">Home</a>
+</li>
+
+
+ <li class="menuItem"> <a href="./license.html">License</a>
+</li>
+
+
+ <li class="menuItem"> <a href="./contribution_policy.html">Contribution Policy</a>
+</li>
+
+
+ <li class="menuItem"> <a href="./guidelines.html">Project Guidelines</a>
+</li>
+
+
+ <li class="menuItem"> <a href="http://www.apache.org/">ASF</a>
+</li>
+
+
+ <li class="menuItem"> <a href="./downloads.html">Downloads</a>
+</li>
+
+
+
+ </ul>
+ <p class="menuItem"><strong>Community</strong></p>
+ <ul>
+ <li class="menuItem"> <a href="./get-involved.html">Get Involved</a>
+</li>
+
+
+ <li class="menuItem"> <a href="./contributors.html">Committers</a>
+</li>
+
+
+ <li class="menuItem"> <a href="./mailing.html">Mailing Lists</a>
+</li>
+
+
+ <li class="menuItem"> <a href="./documentation.html">Documentation</a>
+</li>
+
+
+ <li class="menuItem"> <a href="http://wiki.apache.org/river">Wiki</a>
+</li>
+
+
+
+ </ul>
+ <p class="menuItem"><strong>Development</strong></p>
+ <ul>
+ <li class="menuItem"> <a href="./roadmap.html">Road Map / TODO</a>
+</li>
+
+
+ <li class="menuItem"> <a href="./svn.html">Source Code</a>
+</li>
+
+
+ <li class="menuItem"> <a href="http://issues.apache.org/jira/browse/RIVER">JIRA</a>
+</li>
+
+
+
+ </ul>
+ <p class="menuItem"><strong>Subcomponents</strong></p>
+ <ul>
+
+ </ul>
+ </td>
+ <td width="80%" valign="top"><a name="top"></a>
+ <h1>
+ <a name="Apache River Source Code">Apache River Source Code</a>
+ </h1>
+ <p>
+The River project uses the
+<a href="http://subversion.tigris.org/">Subversion</a> version control
+system. If you're new to Subversion, you can check out the
+<a href="http://svnbook.red-bean.com/">online book</a> about Subversion.
+Note that we are currently using Subversion 1.1.x (there are separate
+versions of the book covering 1.0 and 1.1).
+</p>
+
+ <h2>
+ <a name="Web Access to Subversion">Web Access to Subversion</a>
+ </h2>
+
+ <p>
+If you just want to browse the source code, you can use the
+<a href="http://svn.apache.org/viewcvs.cgi/incubator/river/?root=Apache-SVN">ViewCVS
+web interface</a> to Subversion. This is current at all times.
+</p>
+
+
+ <h2>
+ <a name="Normal Subversion Access">Normal Subversion Access</a>
+ </h2>
+
+ <p>Anyone can check code out of Subversion. You only need to specify a
+username and password in order to update the Subversion repository, and only
+Harmony committers have the permissions to do that. We run Subversion
+over standard HTTPS, so hopefully you won't have problems with intervening
+firewalls.</p>
+ <strong>Check out from Subversion</strong>
+ <p>Again, anyone can do this. Use a command like:</p>
+ <pre>svn checkout https://svn.apache.org/repos/asf/incubator/river/trunk</pre>
+ <strong>Commit Changes to Subversion</strong>
+ <p>
+Any River committer should have a shell account on
+<tt>svn.apache.org</tt>. Before you can commit, you'll need to set a
+Subversion password for yourself. To do that, log in to
+<tt>svn.apache.org</tt> and run the command <i>svnpasswd</i>.
+</p>
+ <p>
+Once your password is set, you can use a command like this to commit:
+</p>
+ <pre>svn commit</pre>
+ <p>If Subversion can't figure out your username, you can tell it
+explicitly:</p>
+ <pre>svn --username you commit</pre>
+ <p>Subversion will prompt you for a password, and once you enter it once, it
+will remember it for you. Note this is the password you configured with
+<tt>svnpasswd</tt>, not your shell or other password.</p>
+
+ <p><a href="#top">Back to top</a></p>
+
+ </td>
+ </tr>
+
+ <!-- FOOTER -->
+ <tr><td colspan="2">
+ <hr noshade="" size="1"/>
+ </td></tr>
+ <tr><td colspan="2">
+ <div class="special"><em>
+ Copyright © 2003-2006, The Apache Software Foundation
+ </em></div>
+ </td></tr>
+ </table>
+ </body>
+ </html>
+<!-- end the processing -->
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Added: incubator/river/site/lib/commons-collections.jar
URL: http://svn.apache.org/viewvc/incubator/river/site/lib/commons-collections.jar?view=auto&rev=491855
==============================================================================
Binary file - no diff available.
Propchange: incubator/river/site/lib/commons-collections.jar
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: incubator/river/site/lib/jdom-b10-rc1.jar
URL: http://svn.apache.org/viewvc/incubator/river/site/lib/jdom-b10-rc1.jar?view=auto&rev=491855
==============================================================================
Binary file - no diff available.
Propchange: incubator/river/site/lib/jdom-b10-rc1.jar
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: incubator/river/site/lib/logkit-1.0.1.jar
URL: http://svn.apache.org/viewvc/incubator/river/site/lib/logkit-1.0.1.jar?view=auto&rev=491855
==============================================================================
Binary file - no diff available.
Propchange: incubator/river/site/lib/logkit-1.0.1.jar
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: incubator/river/site/lib/oro.jar
URL: http://svn.apache.org/viewvc/incubator/river/site/lib/oro.jar?view=auto&rev=491855
==============================================================================
Binary file - no diff available.
Propchange: incubator/river/site/lib/oro.jar
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: incubator/river/site/lib/velocity-1.5-dev.jar
URL: http://svn.apache.org/viewvc/incubator/river/site/lib/velocity-1.5-dev.jar?view=auto&rev=491855
==============================================================================
Binary file - no diff available.
Propchange: incubator/river/site/lib/velocity-1.5-dev.jar
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: incubator/river/site/velocity.properties
URL: http://svn.apache.org/viewvc/incubator/river/site/velocity.properties?view=auto&rev=491855
==============================================================================
--- incubator/river/site/velocity.properties (added)
+++ incubator/river/site/velocity.properties Tue Jan 2 09:13:12 2007
@@ -0,0 +1 @@
+file.resource.loader.path=xdocs, xdocs/stylesheets
Added: incubator/river/site/xdocs/contribution_policy.xml
URL: http://svn.apache.org/viewvc/incubator/river/site/xdocs/contribution_policy.xml?view=auto&rev=491855
==============================================================================
--- incubator/river/site/xdocs/contribution_policy.xml (added)
+++ incubator/river/site/xdocs/contribution_policy.xml Tue Jan 2 09:13:12 2007
@@ -0,0 +1,78 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+
+<!--
+
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You 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.
+-->
+
+<document>
+
+ <properties>
+ <title>Apache River Contribution Policy</title>
+ <author email="river-dev@incubator.apache.org">Documentation Team</author>
+ </properties>
+
+<body>
+<section name="Apache River Contribution Policy">
+
+<p>
+Due to the oversight which we wish to provide for the River community, the following
+process is used for committers, contributors and their contributions.
+</p>
+
+<p>
+In summary :
+</p>
+
+<ul>
+<li>
+We encourage all <i>contributors</i> (not just committers) to have a Individual Contributor
+License Agreement on file with the ASF.
+</li>
+<li>
+All contributions that are of existing code - code that wasn't developed inside of the project
+from scratch - should be first submitted as a JIRA, and then brought into the SVN repository. This
+applies even if the contributor is an existing committer, to help make it clear where the
+external, re-purposes contributions are coming from.
+</li>
+<li>
+Of course, we follow all existing Apache IP contribution processes.
+</li>
+</ul>
+
+
+<subsection name="Policy for Committers">
+
+<p>
+Each committer is required to complete a standard
+<a href="http://www.apache.org/licenses/">Apache Individual Contributor License Agreement</a>.
+This document asserts that the contributor is licensing their
+material to the ASF under the Apache license and is their original work (there's some other details).
+This document is maintained and managed by the Secretary of the Apache Software Foundation.
+</p>
+
+<p>
+We encourage every committer, if appropriate, to have their employer execute a
+<a href="http://www.apache.org/licenses/">Apache Corporate Contributor License Agreement</a>.
+Note that this is recommended, but not required.
+</p>
+
+</subsection>
+
+</section>
+</body>
+</document>
+
Added: incubator/river/site/xdocs/contributors.xml
URL: http://svn.apache.org/viewvc/incubator/river/site/xdocs/contributors.xml?view=auto&rev=491855
==============================================================================
--- incubator/river/site/xdocs/contributors.xml (added)
+++ incubator/river/site/xdocs/contributors.xml Tue Jan 2 09:13:12 2007
@@ -0,0 +1,46 @@
+<?xml version="1.0"?>
+
+<!--
+
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You 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.
+-->
+
+<document>
+
+ <properties>
+ <title>Apache River Committers</title>
+ <author email="river-dev@incubator.apache.org">Documentation Team</author>
+ </properties>
+
+<body>
+
+<section name="Apache River Committers">
+
+<p>
+ If you would like to contribute to River, please see the
+ <a href="roadmap.html">roadmap</a> list to find areas where you can contribute.
+ If there is nothing in there that suits your interest, but you still have
+ ideas, please feel free to suggest them on
+ <a href="mailing.html">the mailing list</a>.
+</p>
+
+<table>
+ <tr><th>Name</th><th>Organization</th></tr>
+</table>
+
+</section>
+</body>
+</document>
Added: incubator/river/site/xdocs/documentation.xml
URL: http://svn.apache.org/viewvc/incubator/river/site/xdocs/documentation.xml?view=auto&rev=491855
==============================================================================
--- incubator/river/site/xdocs/documentation.xml (added)
+++ incubator/river/site/xdocs/documentation.xml Tue Jan 2 09:13:12 2007
@@ -0,0 +1,37 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+
+<!--
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You 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.
+-->
+
+<document>
+
+<properties>
+ <title>Apache River</title>
+ <author email="river-dev@incubator.apache.org">River Documentation Team</author>
+</properties>
+
+<body>
+
+ <section name="Welcome to Apache River - Jini Implementation Community">
+
+ <p>
+ No documentation yet :)
+ </p>
+</section>
+
+</body>
+</document>
Added: incubator/river/site/xdocs/downloads.xml
URL: http://svn.apache.org/viewvc/incubator/river/site/xdocs/downloads.xml?view=auto&rev=491855
==============================================================================
--- incubator/river/site/xdocs/downloads.xml (added)
+++ incubator/river/site/xdocs/downloads.xml Tue Jan 2 09:13:12 2007
@@ -0,0 +1,42 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!--
+
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You 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.
+-->
+
+<document>
+
+ <properties>
+ <title>Apache River</title>
+ <author email="river-dev@incubator.apache.org">Documentation Team</author>
+ </properties>
+
+ <body>
+
+<section name="Project Downloads">
+ <p>
+ The project currently has no downloads.
+ </p>
+ <p>
+ Access to <a href="svn.html">the code repository</a> is available to all, and we have
+ <a href="documentation/documentation.html">instructions</a> for building the
+ virtual machine code.
+ </p>
+ </section>
+</body>
+</document>
+
+
Added: incubator/river/site/xdocs/get-involved.xml
URL: http://svn.apache.org/viewvc/incubator/river/site/xdocs/get-involved.xml?view=auto&rev=491855
==============================================================================
--- incubator/river/site/xdocs/get-involved.xml (added)
+++ incubator/river/site/xdocs/get-involved.xml Tue Jan 2 09:13:12 2007
@@ -0,0 +1,127 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+
+<!--
+
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You 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.
+-->
+
+<document>
+
+ <properties>
+ <title>Get Involved</title>
+ <author email="river-dev@incubator.apache.org">Documentation Team</author>
+ </properties>
+
+ <body>
+
+<section name="How do I contribute, give feedback, fix bugs and so on?">
+
+<p>
+ The Apache River project really needs and appreciates any contributions,
+ including documentation help, source code and feedback. Suggested
+ changes should come in the form of source code and/or very detailed
+ and constructive feedback.
+</p>
+
+<ul>
+ <li>
+ Discussion occurs on the <a
+ href="mailing.html">river mailing lists</a>
+ </li>
+ <li>
+ Information on access to the project source code is
+ available <a href="svn.html">here</a>.
+ </li>
+ <li>
+ Bugs and other issues can be posted on the project
+ <a href="http://issues.apache.org/jira/browse/RIVER">JIRA</a>
+ </li>
+ <li>
+ Additional documentation and discussion can be found on the project
+ <a href="http://wiki.apache.org/river/">wiki</a>
+ </li>
+</ul>
+
+</section>
+
+<section name="How to Create and Submit A Patch or Enhancement">
+<a name="create_patch"/>
+
+<p>
+ One of the best ways to get involved in the River project is to
+ create patches or additions and contribute them. All contributions
+ should be made via a new entry in our project
+ <a href="http://issues.apache.org/jira/browse/RIVER">JIRA</a>.
+</p>
+
+<p>
+ Here are some basic guidelines and suggestions :
+ <ul>
+ <li>
+ Once you have completed your changes, please be sure
+ to test your changes very well.
+ </li>
+ <li>
+ If you are offering a code addition or change, be sure that
+ the codebase builds cleanly and the full test suite passes
+ before submitting. Patches that break the
+ build or break the code will be rejected.
+ </li>
+ <li>
+ If you are offering a change to documentation or the website,
+ please review the generated output and be sure that it is as you expect.
+ </li>
+ <li>
+ If you are offering a fix to a bug, please provide a testcase and
+ instructions to help us duplicate the bug, and then test that the bug
+ is fixed. We will add the testcase to our testsuite.
+ </li>
+ <li>
+ When offering something new, please include the entire file
+ that you are contributing.
+ </li>
+ <li>
+ When you are offering a change to something that already exists
+ in the project SVN repository, please submit a patch as outlined below.
+ </li>
+ </ul>
+</p>
+
+<p>
+ Once you are sure you have tested/reviewed your changes, open a
+ new JIRA entry. Clearly describe the patch or enhancement, and
+ provide details, such as how to re-create if a bug, why the
+ change or enhancement is useful, etc. Then, attach all materials
+ to the JIRA entry via "Attach File". Please be sure to select
+ "Grant license to ASF for inclusion in ASF works...". Any patch
+ without this grant will be rejected.
+</p>
+
+<p>
+ Please use the subversion 'diff' utility to create a patch as follows :
+
+ <pre>
+ svn diff file.java > file.patch
+ </pre>
+
+ where 'file' is the filename that you have changed. This will produce a
+ nice patch file that can be added to the JIRA, which makes it easy for
+ the project committers to review and possibly accept your patch.
+</p>
+
+</section>
+</body>
+</document>
Added: incubator/river/site/xdocs/guidelines.xml
URL: http://svn.apache.org/viewvc/incubator/river/site/xdocs/guidelines.xml?view=auto&rev=491855
==============================================================================
--- incubator/river/site/xdocs/guidelines.xml (added)
+++ incubator/river/site/xdocs/guidelines.xml Tue Jan 2 09:13:12 2007
@@ -0,0 +1,356 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!--
+
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You 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.
+-->
+
+<document>
+
+ <properties>
+ <title>Project Guidelines</title>
+ <author email="river-dev@incubator.apache.org">Documentation Team</author>
+ </properties>
+
+ <body>
+ <section name="Project Guidelines">
+
+<p>
+This document defines the guidelines for the
+<a href="http://incubator.apache.org/river">Apache River Project</a>.
+It includes definitions of how conflict is resolved by voting,
+who is able to vote, and the procedures to follow for proposing and
+making changes to the Apache products.
+</p>
+
+<p>
+The objective here is to avoid unnecessary conflict over changes and
+continue to produce a quality system in a timely manner. Not all conflict
+can be avoided, but at least we can agree on the procedures for conflict
+to be resolved.
+</p>
+
+ </section>
+
+<section name="People, Places, and Things">
+
+<dl>
+ <dt><strong>Apache River Project Management Committee</strong></dt>
+ <dd>The group of volunteers who are responsible for managing the Apache
+ Harmony Project. This includes deciding what is distributed
+ as products of the Project, maintaining the
+ Project's shared resources, speaking on behalf of the Project,
+ resolving license disputes regarding Apache products, nominating
+ new PMC members or committers, and establishing these guidelines.
+
+ <p>Membership in the Apache PMC is by invitation only and must
+ be approved by consensus of the active Apache PMC members.
+ A PMC member is considered inactive by their own declaration or by
+ not contributing in any form to the project for over six months.
+ An inactive member can become active again by reversing whichever
+ condition made them inactive (<em>i.e.</em>, by reversing their
+ earlier declaration or by once again contributing toward the
+ project's work). Membership can be revoked by a unanimous vote of
+ all the active PMC members other than the member in question.</p>
+
+ <p>
+ Our goal is that every committer willing and interested in the day-to-day
+ oversight and management of the project will be invited at the right time
+ to join the PMC. Our goal is 100% of the committers on the PMC.
+ </p>
+
+ <p>
+ <b>Please Note : </b> While in incubation, the PPMC of the incubating
+ River project will play the role of the official PMC.
+ </p>
+ </dd>
+
+ <dt><strong>Apache River Committers</strong></dt>
+ <dd>The group of volunteers who are responsible for the technical
+ aspects of the Apache River Project. This group has
+ write access to the appropriate source repositories and these
+ volunteers may cast binding votes on any technical discussion.
+
+ <p>Membership as a Committer is by invitation only and must
+ be approved by consensus of the active Apache PMC members.
+ A Committer is considered inactive by their own declaration or by
+ not contributing in any form to the project for over six months.
+ An inactive member can become active again by reversing whichever
+ condition made them inactive (<em>i.e.</em>, by reversing their
+ earlier declaration or by once again contributing toward the
+ project's work). Membership can be revoked by a unanimous vote of
+ all the active PMC members (except the member in question if they
+ are a PMC member).</p>
+ </dd>
+
+ <dt><strong>Apache River Developers</strong></dt>
+ <dd>All of the volunteers who are contributing time, code, documentation,
+ or resources to the Apache River Project. A developer that makes sustained,
+ welcome contributions to the project for over six months is usually
+ invited to become a Committer, though the exact timing of such
+ invitations depends on many factors.</dd>
+
+ <dt><strong>river-dev@incubator.apache.org</strong></dt>
+ <dd>The Apache developers' primary mailing list for discussion of issues
+ and changes related to the project (<em>river-dev@incubator.apache.org</em>).
+ Subscription to the list is open, but only subscribers
+ can post directly to the list.
+ </dd>
+
+ <dt><strong>river-rivate@incuabtor.apache.org</strong></dt>
+ <dd>The Apache River PMC's private mailing list for discussion of issues
+ that are inappropriate for public discussion, such as legal, personal,
+ or security issues prior to a published fix. Subscription to the list
+ is only open to Apache River PMC members.
+ </dd>
+
+ <dt><strong>river-commits@incubator.apache.org</strong></dt>
+ <dd>All of the Apache projects are maintained in shared information
+ repositories using SVN.
+ Only some of the Apache developers (the committers) have
+ write access to these repositories; everyone has read access via
+ <a href="anoncvs">anonymous SVN</a>.
+ </dd>
+</dl>
+</section>
+
+<section name="Voting">
+
+<p>Any of the Apache Developers may vote on any issue or action item.
+However, the only binding votes are those cast by active members of the
+Apache River PMC; if the vote is about a change to source code or
+documentation, the primary author of what is being changed may also
+cast a binding vote on that issue. All other votes are non-binding.
+All developers are encouraged to participate in decisions, but the
+decision itself is made by those who have been long-time contributors
+to the project. In other words, the Apache Harmony Project is a
+minimum-threshold meritocracy.</p>
+
+<p>The act of voting carries certain obligations -- voting members are
+not only stating their opinion, they are agreeing to help do the work of
+the Apache Harmony Project. Since we are all volunteers, members often become
+inactive for periods of time in order to take care of their "real jobs"
+or devote more time to other projects. It is therefore unlikely that the
+entire group membership will vote on every issue. To account for this,
+all voting decisions are based on a minimum quorum.</p>
+
+<p>Each vote can be made in one of three flavors:</p>
+
+<dl>
+ <dt><strong>+1</strong></dt>
+ <dd>Yes, agree, or the action should be performed. On some issues, this
+ vote is only binding if the voter has tested the action on
+ their own system(s).
+ </dd>
+ <dt><strong>0</strong></dt>
+ <dd>Abstain, no opinion, or I am happy to let the other group members
+ decide this issue. An abstention may have detrimental effects if
+ too many people abstain.
+ </dd>
+ <dt><strong>-1</strong></dt>
+ <dd>No. On issues where consensus is required, this vote counts as a
+ <strong>veto</strong>. All vetos must include an explanation of
+ why the veto is appropriate. A veto with no explanation is void.
+ No veto can be overruled. If you disagree with the veto, you
+ should lobby the person who cast the veto. Voters intending to veto
+ an action item should make their opinions known to the group immediately,
+ so that the problem can be remedied as early as possible.
+ </dd>
+</dl>
+
+<p>An action item requiring <em>consensus approval</em> must receive
+at least <strong>3 binding +1</strong> votes and <strong>no vetos</strong>.
+An action item requiring <em>majority approval</em> must receive
+at least <strong>3 binding +1</strong> votes and more <strong>+1</strong>
+votes than <strong>-1</strong> votes (<em>i.e.</em>, a majority with a minimum
+quorum of three positive votes). All other action items are considered
+to have <em>lazy approval</em> until someone votes <strong>-1</strong>,
+after which point they are decided by either consensus or a majority vote,
+depending upon the type of action item.</p>
+
+<p>Votes are tallied within the STATUS file, adjacent to the action
+item under vote. All votes must be sent to the mailing list.</p>
+
+</section>
+
+<section name="Types of Action Items">
+<dl>
+ <dt><strong>Long Term Plans</strong></dt>
+ <dd>Long term plans are simply announcements that group members
+ are working on particular issues related to the Apache software.
+ These are not voted on,
+ but group members who do not agree with a particular plan,
+ or think an alternate plan would be better, are obligated to
+ inform the group of their feelings. In general, it is always
+ better to hear about alternate plans <strong>prior</strong> to
+ spending time on less adequate solutions.
+ </dd>
+
+ <dt><strong>Short Term Plans</strong></dt>
+ <dd>Short term plans are announcements that a developer is working on
+ a particular set of documentation or code files, with the implication
+ that other developers should avoid them or try to coordinate their
+ changes. This is a good way to proactively avoid conflict and
+ possible duplication of work.
+ </dd>
+
+ <dt><strong>Release Plan</strong></dt>
+ <dd>A release plan is used to keep all the developers aware of when a
+ release is desired, who will be the release manager, when the
+ repository will be frozen in order to create the release, and
+ assorted other trivia to keep us from tripping over ourselves
+ during the final moments. Lazy majority decides each issue in
+ the release plan.
+ </dd>
+
+ <dt><strong>Release Testing</strong></dt>
+ <dd>After a new release is built, colloquially termed a tarball, it
+ must be tested before being released to the public. Majority
+ approval is required before the tarball can be publically released.
+ </dd>
+
+ <dt><strong>Showstoppers</strong></dt>
+ <dd>Showstoppers are issues that require a fix be in place
+ before the next public release. They are listed in the STATUS file
+ in order to focus special attention on the problem. An issue becomes
+ a showstopper when it is listed as such in STATUS and remains
+ so by lazy consensus.
+ </dd>
+
+ <dt><strong>Product Changes</strong></dt>
+ <dd>Changes to the Apache products, including code and documentation,
+ will appear as action items under several categories corresponding
+ to the change status:
+ <dl>
+ <dt><strong>concept/plan</strong></dt>
+ <dd>An idea or plan for a change. These are usually only listed in
+ STATUS when the change is substantial, significantly impacts the
+ API, or is likely to be controversial. Votes are being requested
+ early so as to uncover conflicts before too much work is done.
+ </dd>
+ <dt><strong>proposed patch</strong></dt>
+ <dd>A specific set of changes to the current product in the form
+ of <a href="#patch">input to the patch command</a> (a diff output).
+ </dd>
+ <dt><strong>committed change</strong></dt>
+ <dd>A one-line summary of a change that has been committed to the
+ repository since the last public release.
+ </dd>
+ </dl>
+ <p>All product changes to the currently active repository are subject
+ to lazy consensus. All product changes to a prior-branch (old version)
+ repository require consensus before the change is committed.</p>
+ </dd>
+</dl>
+</section>
+
+<section name="When to Commit a Change">
+
+<p>
+ Ideas must be review-then-commit; patches can be commit-then-review.
+ With a commit-then-review process, we trust that the developer doing the
+ commit has a high degree of confidence in the change. Doubtful changes,
+ new features, and large-scale overhauls need to be discussed before
+ being committed to a repository. Any major change
+ must receive consensus approval on the mailing list before being committed.
+ For detailed instructions on reporting, resolving and closing issues, refer to
+ <a href="issue_resolution_guideline.html">
+ Good Issue Resolution Guideline</a>.
+</p>
+
+<p>Each developer is responsible for notifying the mailing list and
+adding an action item to STATUS when they have an idea for a new feature
+or major change to propose for the product. The distributed nature of the
+Apache project requires an advance notice of 48 hours in order to properly
+review a major change -- consensus approval of either the concept or a
+specific patch is required before the change can be committed. Note that
+a committer might veto the concept (with an adequate explanation), but later
+rescind that veto if a specific patch satisfies their objections.
+No advance notice is required to commit singular bug fixes.</p>
+
+<p>Related changes should be committed as a group, or very closely
+together. Half-completed projects should not be committed unless
+doing so is necessary to pass the baton to another developer who has
+agreed to complete the project in short order. All code changes must
+be successfully compiled on the developer's platform before being
+committed.</p>
+
+<p>The current source code tree should be capable of complete compilation
+at all times. However, it is sometimes impossible for a developer on
+one platform to avoid breaking some other platform when a change is
+committed, particularly when completing the change requires access to
+a special development tool on that other platform. If it is anticipated
+that a given change will break some other platform, the committer must
+indicate that in the commit log.</p>
+
+<p>The committer is responsible to follow the Apache River procedure
+for any third-party code
+or documentation they commit to the repository. All software committed
+to the repository must be covered by the Apache LICENSE or contain a
+copyright and license that allows redistribution under the same conditions
+as the Apache LICENSE.</p>
+
+<p>A committed change must be reversed if it is vetoed by one of the
+voting committers and the veto conditions cannot be immediately satisfied by
+the equivalent of a "bug fix" commit. The veto must be rescinded before
+the change can be included in any public release.</p>
+
+</section>
+
+<section id="patch" name="Patch Format">
+<p>When a specific change to the software is proposed for discussion or
+voting on the mailing list, it should be presented in the form of input
+to the patch command. When sent to the mailing list, the message
+should contain a Subject beginning with <code>[PATCH]</code> and a
+distinctive one-line summary corresponding to the action item for that
+patch. Afterwards, the patch summary in the STATUS file should be
+updated to point to the Message-ID of that message.</p>
+
+<p>The patch should be created by using the <CODE>diff -u</CODE>
+command from the original software file(s) to the modified software
+file(s). E.g.,</p>
+
+<pre> diff -u http_main.c.orig http_main.c >> patchfile.txt</pre>
+<p>or</p>
+<pre> cvs diff -u http_main.c >> patchfile.txt</pre>
+
+<p>All patches necessary to address an action item should be concatenated
+within a single patch message. If later modification of the patch
+proves necessary, the entire new patch should be posted and not just
+the difference between two patches. The STATUS file entry should then
+be updated to point to the new patch message.</p>
+
+<p>The completed patchfile should produce no errors or prompts when the
+command,</p>
+<pre> patch -s < patchfile</pre>
+<p>is issued in the target repository.</p>
+</section>
+
+<section name="Addendum">
+
+<p>Outstanding issues with this document</p>
+
+<ul>
+ <li>We may need a better definition for "lazy consensus".</li>
+ <li>We should clarify under what conditions a veto can be rescinded
+ or overridden.</li>
+ <li>Should we set a time limit on vetos of patches? Two weeks?</li>
+</ul>
+
+</section>
+
+</body>
+</document>
+
Added: incubator/river/site/xdocs/index.xml
URL: http://svn.apache.org/viewvc/incubator/river/site/xdocs/index.xml?view=auto&rev=491855
==============================================================================
--- incubator/river/site/xdocs/index.xml (added)
+++ incubator/river/site/xdocs/index.xml Tue Jan 2 09:13:12 2007
@@ -0,0 +1,58 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+
+<!--
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You 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.
+-->
+
+<document>
+
+<properties>
+ <title>Apache River</title>
+ <author email="river-dev@incubator.apache.org">River Documentation Team</author>
+</properties>
+
+<body>
+
+ <section name="Welcome to Apache River - Jini Implementation Community">
+
+ <p>
+ <big>Welcome to Apache River - Jini Implementation Community</big>
+ </p>
+
+ <p>
+ Apache River is a new podling, just getting started. More to come!
+ </p>
+</section>
+
+<section name="Project Status">
+
+ <p>
+ How are we doing? We're just getting started...
+ </p>
+
+</section>
+
+ <section name="River News">
+ <p>
+ <strong>River Podling Status approved by Apache Incubator</strong>
+ <blockquote>
+ Apache River has been approved as an incubator podling. Please join!
+ (<i>2006-12-26</i>)
+ </blockquote>
+ </p>
+</section>
+</body>
+</document>