forrest-svn mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cross...@apache.org
Subject svn commit: r376128 [31/34] - in /forrest/site: ./ docs_0_60/ docs_0_60/howto/ docs_0_60/howto/bugzilla-patch/ docs_0_60/howto/multi/ docs_0_70/ docs_0_70/howto/ docs_0_70/howto/cvs-ssh/ docs_0_70/howto/multi/ docs_0_80/ docs_0_80/howto/ docs_0_80/howt...
Date Thu, 09 Feb 2006 00:26:32 GMT
Propchange: forrest/site/dtdx/howto-v20.dtdx.source.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Added: forrest/site/events.source.xml
URL: http://svn.apache.org/viewcvs/forrest/site/events.source.xml?rev=376128&view=auto
==============================================================================
--- forrest/site/events.source.xml (added)
+++ forrest/site/events.source.xml Wed Feb  8 16:26:20 2006
@@ -0,0 +1,139 @@
+<?xml version="1.0" encoding="ISO-8859-1"?><!--
+  Copyright 2005-2006 The Apache Software Foundation or its licensors,
+  as applicable.
+
+  Licensed under the Apache License, Version 2.0 (the "License");
+  you may not use this file except in compliance with the License.
+  You may obtain a copy of the License at
+
+      http://www.apache.org/licenses/LICENSE-2.0
+
+  Unless required by applicable law or agreed to in writing, software
+  distributed under the License is distributed on an "AS IS" BASIS,
+  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+  See the License for the specific language governing permissions and
+  limitations under the License.
+--><document>
+  <header>
+    <title>Apache Forrest: Events</title>
+  </header>
+  <body>
+    <section id="upcoming">
+      <title>Upcoming events</title>
+
+      <section id="forrest-friday">
+        <title>ForrestFriday monthly get-together (10 February 2006)</title>
+        <p>
+          On the second Friday of each month we have a 24-hour get-together using
+          IRC and other collaborative tools, to work on Forrest development and
+          get to know each other. See how to
+          <link href="site:forrest-friday">participate</link>.
+        </p>
+      </section>
+    </section>
+
+    <section id="past">
+      <title>Past events</title>
+
+      <section id="apachecon-us-2005">
+        <title>ApacheCon US 2005 (10-14 December)</title>
+        <p>
+          Please make plans to join us at
+          <link href="http://apachecon.com/2005/US/">ApacheCon US 2005</link>
+          in San Diego, California, USA on 10-14 December 2005.
+        </p>
+        <p>
+          Apart from all of the general ApacheCon events, there is one
+          Forrest-specific event.
+        </p>
+
+        <section id="fs-ac-us-2005">
+          <title>ApacheCon Session: Single Source Publishing with Apache Forrest</title>
+          <p>
+            Tuesday 13 December at 09:00 to 10:00 - Official ApacheCon session
+            conducted by Ferdinand Soethe. See the
+            <link href="http://apachecon.com/2005/US/html/sessions.html">ApacheCon
+            Schedule</link> Session TU01.
+            The event is only open to ApacheCon attendees.
+          </p>
+        </section>
+      </section>
+
+    <section id="apachecon-eu-2005">
+      <title>ApacheCon Europe 2005 (18-22 July)</title>
+      <p>
+        <link href="http://apachecon.com/2005/EU/">ApacheCon Europe 2005</link>
+        in Stuttgart, Germany on 18-22 July 2005. For the first time there is
+        a session related to Apache Forrest.
+      </p>
+      <p>
+        Apart from all of the general ApacheCon events, there are a number of
+        Forrest-specific events. In chronological order ...
+      </p>
+
+      <section id="ht-stuttgart-2005">
+        <title>Apache committers hackathon</title>
+        <p>
+          Monday 18 July and Tuesday 19 July all day - Open to any Apache
+          committer. Among the many topics, some of us will informally chat
+          about Apache Forrest and maybe fix some bugs. We will probably
+          collaborate with the Apache Lenya committers too.
+        </p>
+      </section>
+
+      <section id="ws-stuttgart-2005">
+        <title>Apache Forrest workshop on Views</title>
+        <p>
+          Monday 18 July commencing at 18:30 - We will go out to dinner and then
+          meet for a developers workshop specifically about the new Views plugin
+          development. Topics will include Views, XHTML2 internal format, and
+          general project planning. Discussions will be technical and will assume
+          knowledge of Forrest. We will certainly answer questions to ensure that
+          people understand the background. However the main aim is an intensive
+          project design session.
+          The event is open to anybody, you don't need to be attending ApacheCon.
+          Venue and Directions: Gather at the foyer of the ApacheCon.
+        </p>
+      </section>
+
+      <section id="ua-stuttgart-2005">
+        <title>Usability professionals meeting</title>
+        <p>
+          Tuesday 19 July commencing at 18:30 - Johannes Schaefer will
+          present Apache Forrest to an informal meeting of usability
+          professionals. The event is open to other German-speaking people.
+          See
+          <link href="http://www.gui-design.de/ak/ak_050719.htm">further information</link>.
+        </p>
+      </section>
+
+      <section id="rf-stuttgart-2005">
+        <title>ApacheCon Session: Single Source Publishing with Apache Forrest</title>
+        <p>
+          Wednesday 20 July at 14:30 to 15:30 - Official ApacheCon session
+          conducted by Ross Gardler and Ferdinand Soethe. See the
+          <link href="http://apachecon.com/2005/EU/html/sessions.html">ApacheCon
+          Schedule</link> Session WE16.
+          The event is only open to ApacheCon attendees.
+        </p>
+      </section>
+
+      <section id="gt-stuttgart-2005">
+        <title>Apache Forrest get-together</title>
+        <p>
+          Wednesday 20 July commencing at 20:00 - Informal get together to
+          discuss any topic related to Apache Forrest. Follows on from
+          the session earlier in the day. Please come and meet other
+          Forrest developers and users. Describe your own use cases.
+          The event is open to anybody, you don't need to be attending ApacheCon.
+          Venue and Directions: Gather at the foyer of the ApacheCon at 20:00.
+          The event will be held at Stuttgart University of Applied Sciences
+          Many thanks to HfT.
+          See (<link href="http://www.hft-stuttgart.de/Hochschule/wirueberuns/Lageplan/">HfT map</link>)
+          which is just a few steps north-west of the ApacheCon-site:</p>
+          <p><img src="apacheconsites.jpg" alt="map of sites"/></p>
+      </section>
+    </section>
+    </section>
+  </body>
+</document>
\ No newline at end of file

Propchange: forrest/site/events.source.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Added: forrest/site/flyer.source.xml
URL: http://svn.apache.org/viewcvs/forrest/site/flyer.source.xml?rev=376128&view=auto
==============================================================================
--- forrest/site/flyer.source.xml (added)
+++ forrest/site/flyer.source.xml Wed Feb  8 16:26:20 2006
@@ -0,0 +1,97 @@
+<?xml version="1.0" encoding="ISO-8859-1"?><!--
+  Copyright 2002-2005 The Apache Software Foundation or its licensors,
+  as applicable.
+
+  Licensed under the Apache License, Version 2.0 (the "License");
+  you may not use this file except in compliance with the License.
+  You may obtain a copy of the License at
+
+      http://www.apache.org/licenses/LICENSE-2.0
+
+  Unless required by applicable law or agreed to in writing, software
+  distributed under the License is distributed on an "AS IS" BASIS,
+  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+  See the License for the specific language governing permissions and
+  limitations under the License.
+--><document>
+  <header>
+    <title>Apache Forrest: documentation framework</title>
+  </header>
+  <body>
+    <p>
+      Apache Forrest
+      (<link href="site:forrest">forrest.apache.org</link>)
+      is a publishing framework that transforms
+      input from various sources into a unified presentation
+      in one or more output formats. The modular and extensible
+      plugin architecture is based on Apache Cocoon and relevant
+      standards, which separates presentation from content.
+      Forrest can generate static documents, or be used as a
+      dynamic server, or be deployed by its automated facility.
+    </p>
+    <p>
+      By <strong>separating content from
+      presentation</strong>, providing <strong>content templates</strong>
+      and <strong>pre-written skins</strong>, Forrest is unequalled at enabling
+      content producers to get their message out fast.  This separation of
+      concerns makes Forrest excellent
+      to publish <strong>project documentation</strong> (notably software projects),
+      <strong>intranets</strong>, and <strong>home pages</strong>.
+    </p>
+    <p>
+      Forrest is
+      built on one of the world's leading XML application frameworks, 
+      <link href="ext:cocoon">Apache Cocoon</link>, which provides advanced
+      users with extremely powerful publishing capabilities.
+    </p>
+    <ul>
+      <li>Multiple task-specific source XML formats can be used
+       (<link href="site:v0.70//howto">How-To</link>,
+        <link href="site:v0.70//faq"><acronym title="Frequently Asked             Questions">FAQ</acronym></link>,
+        <link href="site:v0.70//changes">changelogs</link> and
+        <link href="site:v0.70//todo">todo lists</link> supported natively).
+        Source formats include: Apache xdocs xml format, plain html
+        documents, some Wiki formats, a subset of DocBook, ...
+      </li>
+      <li>Multiple output formats supported, for example HTML and PDF (using
+        <link href="ext:fop">Apache FOP</link>).
+      </li>
+      <li>SVG to PNG rendering (using <link href="ext:batik">Apache
+        Batik</link>). Simply drop the SVG in the appropriate directory
+        and it will be rendered as PNG.</li>
+      <li>
+        Transparent inclusion and aggregation of external content, like
+        <link href="site:v0.70//changes-rss">RSS feeds</link>.
+      </li>
+      <li>
+        Anything else possible with the
+        <link href="ext:cocoon/sitemap">Cocoon sitemap</link>.  Using database
+        queries, <link href="ext:apache-stats">charting</link>, web services
+        integration; the possibilities are constantly growing as Cocoon grows.
+        See the <link href="ext:cocoon/features">Cocoon Features</link> list
+        for the full suite of capabilities.
+      </li>
+      <li>
+        Based on Java, Forrest is platform-independent, making for a
+        documentation system that is just as portable as the XML data it
+        processes.
+      </li>
+      <li>
+        Your development team does not need Java experience, or even XML
+        skills, to use Forrest. The framework lets you concentrate on
+        content and design.
+      </li>
+    </ul>
+    <p>
+      Unique amongst comparable documentation tools, Forrest generates
+      sites that can run both <strong>interactively</strong> as a dynamic
+      web application, or as statically rendered pages.
+      Running as a webapp has a major advantage during development:
+      content can be written, and
+      then the rendered output viewed almost instantly in a web browser.
+      This <link href="site:v0.70//your-project/webapp">webapp technique</link>
+      enables the edit/review cycle to be faster than command-line
+      transformation tools.
+    </p>
+  </body>
+</document>
\ No newline at end of file

Propchange: forrest/site/flyer.source.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Added: forrest/site/forrest-friday.source.xml
URL: http://svn.apache.org/viewcvs/forrest/site/forrest-friday.source.xml?rev=376128&view=auto
==============================================================================
--- forrest/site/forrest-friday.source.xml (added)
+++ forrest/site/forrest-friday.source.xml Wed Feb  8 16:26:20 2006
@@ -0,0 +1,151 @@
+<?xml version="1.0" encoding="ISO-8859-1"?><!--
+  Copyright 2005-2006 The Apache Software Foundation or its licensors,
+  as applicable.
+
+  Licensed under the Apache License, Version 2.0 (the "License");
+  you may not use this file except in compliance with the License.
+  You may obtain a copy of the License at
+
+      http://www.apache.org/licenses/LICENSE-2.0
+
+  Unless required by applicable law or agreed to in writing, software
+  distributed under the License is distributed on an "AS IS" BASIS,
+  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+  See the License for the specific language governing permissions and
+  limitations under the License.
+--><document>
+  <header>
+    <title>ForrestFriday monthly get-together</title>
+  </header>
+  <body>
+    <section id="overview">
+      <title>Overview</title>
+      <p>
+        On the second Friday of each month we have a 24-hour get-together using
+        the dev mailing list, Internet Relay Chat (IRC), and other collaborative
+        tools, to work on Forrest development and get to know each other.
+      </p>
+      <p>
+        ForrestFriday starts at 06:00 UTC (6am Greenwich Mean Time in London)
+        and lasts for 24 hours.
+      </p>
+      <p>
+        The next event will take place on <strong>10 February 2006</strong>. See 
+        <link href="http://www.timeanddate.com/worldclock/fixedtime.html?year=2006&amp;month=02&amp;day=10&amp;hour=6&amp;min=0&amp;sec=0">start time</link>
+        and
+        <link href="http://www.timeanddate.com/worldclock/meetingtime.html?day=10&amp;month=02&amp;year=2006&amp;p1=136&amp;p2=48&amp;p3=176&amp;p4=240&amp;p5=224&amp;p6=213">zone overlap</link>.
+      </p>
+    </section>
+
+    <section id="purpose">
+      <title>Purpose</title>
+      <p>
+        The day is devoted to working collaboratively to solve particular issues
+        and getting to know each other. In the weeks leading up to each event,
+        decide on the dev mailing list what the main topic should be. Probably
+        something that needs groups work (e.g. moving the internal format to
+        be XHTML2).
+      </p>
+      <p>
+        There will also be an effort to clean up the
+        <link href="site:bugs">Issue Tracker</link>.
+      </p>
+      <p>
+        The dev mailing list is still the main form of communication and all
+        decisions are made there. The IRC channel is to support that and provide
+        a place for near real-time discussion.
+      </p>
+      <p>
+        The IRC channel is definitely not open continuously. It is only for
+        temporary communications at this monthly meeting.
+      </p>
+      <p>
+        This is not a user help forum, please do that on the user mailing list.
+      </p>
+    </section>
+
+    <section id="how">
+      <title>How to participate</title>
+      <ul>
+        <li>
+          All volunteers are welcome.
+        </li>
+        <li>
+          Get an IRC client (some are mentioned at <link href="http://irchelp.org/">irchelp.org</link>)
+          and see <link href="http://www.irchelp.org/irchelp/irctutorial.html">IRC Tutorial</link>.
+        </li>
+        <li>
+          Read the dev mailing list. That is where any decisions will be
+          made and the name of the IRC channel will be announced.
+        </li>
+        <li>
+          At the start time, connect to irc.freenode.net and join the channel.
+        </li>
+        <li>
+          The discussion will be logged and added to our
+          "<link href="http://svn.apache.org/repos/asf/forrest/events/">events</link>"
+          SVN repository.
+        </li>
+        <li>
+          See notes about the <link href="site:plan/overview">topic of the day</link>.
+        </li>
+        <li>
+          We hope to also have a Lenya instance. This will enable a "whiteboard"
+          for the day, and also be the first step for later Forrest-Lenya integration.
+        </li>
+      </ul>
+    </section>
+
+    <section id="op">
+      <title>Notes for channel operator</title>
+      <ul>
+        <li>
+          The first person to join the channel is the operator.
+        </li>
+        <li>
+          See the irchelp.org
+          <link href="http://www.irchelp.org/irchelp/changuide.html">guide</link>
+          for channel operators.
+        </li>
+        <li>
+          Make sure that your irc client is creating a logfile.
+        </li>
+        <li>
+          Decide on a channel name. Join it a bit before the start time, then do
+          this setup ...
+        </li>
+        <li>
+          Set the channel mode: <code>/mode +n</code>
+        </li>
+        <li>
+          Declare today's topic: <code>/topic ForrestFriday: XHTML2 core and Jira cleanup</code>
+        </li>
+        <li>Ask cheche to start the logger bot and tell the URL for the live logfile.
+        </li>
+        <li>
+          Make sure that your client is creating a logfile.
+        </li>
+        <li>
+          Begin a summary text file in the "forrest-events" SVN. Committers
+          should add to this during the day. Don't leave it until the end.
+        </li>
+        <li>
+          Announce to the dev mailing list that the channel is open and tell the channel name
+          and the URL for the live log.
+        </li>
+        <li>
+          During the session, occasionally refer to the live logfile URL. People can read
+          what they missed, and also refer to previous discussion by stating the time that
+          it occurred.
+        </li>
+        <li>
+          At the end, everyone leaves the channel and it will automatically close.
+          Ask cheche to stop the logger bot.
+        </li>
+        <li>
+          Add the logfile to the Forrest Events repository.
+        </li>
+      </ul>
+    </section>
+  </body>
+</document>
\ No newline at end of file

Propchange: forrest/site/forrest-friday.source.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Added: forrest/site/guidelines.source.xml
URL: http://svn.apache.org/viewcvs/forrest/site/guidelines.source.xml?rev=376128&view=auto
==============================================================================
--- forrest/site/guidelines.source.xml (added)
+++ forrest/site/guidelines.source.xml Wed Feb  8 16:26:20 2006
@@ -0,0 +1,701 @@
+<?xml version="1.0" encoding="ISO-8859-1"?><!--
+Copyright 2002-2005 The Apache Software Foundation or its licensors,
+as applicable.
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+    http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.
+--><!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "http://forrest.apache.org/dtd/document-v13.dtd">
+<document> 
+<header> 
+  <title>Apache Forrest project guidelines</title> 
+</header> 
+<body> 
+
+  <p>
+   This document provides the guidelines under which the Apache Forrest
+   project operates. It defines the roles and responsibilities, who may vote,
+   how voting works, how conflicts are resolved, etc.
+   Apache Forrest is a project of the Apache Software Foundation
+   (<link href="http://www.apache.org/foundation/">ASF</link>) which is a
+   non-profit corporation. As with all such organistions there are some
+   procedures to be followed.
+   The ASF website explains the
+   operation and background of the ASF. These project guidelines supplement that
+   ASF documentation. Normally these guidelines are not needed - the project
+   just gets on with its day-to-day operation - but they enable
+   all people to understand how the project operates.
+  </p>
+
+  <section id="mission">
+    <title>The mission of Apache Forrest</title>
+    <p>
+      The generation of aggregated multi-channel documentation,
+      maintaining a separation of content and presentation.
+    </p>
+  </section>
+
+  <section id="way">
+    <title>The Apache Way</title>
+    <p>
+      Forrest is typical of Apache projects, in that it operates under a set of
+      principles known collectively as the "Apache Way". This facilitates
+      open collaborative development, with respect for others.
+      For more information about how Apache projects operate, please refer to
+      the
+      <link href="http://www.apache.org/foundation/">ASF foundation</link>
+      and
+      <link href="http://www.apache.org/dev/">ASF developer</link> sections
+      of the ASF website, including the
+      <link href="http://www.apache.org/foundation/bylaws.html">ASF ByLaws</link>
+      and the
+      <link href="ext:how-it-works">How it works</link> document,
+      the 
+      <link href="http://www.apache.org/foundation/faq.html">FAQs</link>
+      about the Foundation, and the
+      <link href="http://incubator.apache.org/">Incubator project</link>.
+    </p>
+  </section>
+
+  <section id="roles">
+    <title>Roles and responsibilities</title>
+    <p>The meritocracy enables various roles as defined in the
+      <link href="ext:how-it-works">How it works</link> document.
+    </p>
+    <p>
+    <link href="http://www.apache.org/foundation/how-it-works.html#users">user</link> |
+    <link href="http://www.apache.org/foundation/how-it-works.html#developers">developer</link> |
+    <link href="http://www.apache.org/foundation/how-it-works.html#committers">committer</link> |
+    <link href="http://www.apache.org/foundation/how-it-works.html#pmc-members">PMC member</link> |
+    <link href="http://www.apache.org/foundation/how-it-works.html#asf-members">ASF member</link>
+    </p>
+    <p>The current Apache Forrest committers and PMC members are
+      <link href="site:who">listed</link>.
+    </p>
+  </section>
+
+  <section id="pmc">
+    <title>Project Management Committee (PMC)</title>
+    <p>The Apache Forrest project was established in January 2002 and became a
+      top-level project in May 2004.
+      The Project Management Committee (PMC) was created by a
+      <link href="http://www.apache.org/foundation/records/minutes/2004/board_minutes_2004_05_26.txt">resolution</link>
+      of the board of the Apache Software Foundation.
+      See explanation of the role of the PMC in that resolution and also the
+      <link href="http://www.apache.org/foundation/bylaws.html">ASF Bylaws</link>
+      and 
+    <link href="http://www.apache.org/foundation/how-it-works.html#pmc">How-it-works</link>.
+    </p>
+    <p>The responsibilities of the PMC include:</p>
+    <ul>
+      <li>Be familiar with these project guidelines, and the
+      ASF Bylaws, and with the ASF documentation and procedures
+      in general.</li>
+      <li>Keep oversight of the commit log messages and ensure that
+       the codebase does not have copyright and license issues.</li>
+      <li>Resolve license disputes regarding products of the project,
+        including other supporting software that is re-distributed.</li>
+      <li>Decide what is distributed as products of the project.
+        In particular all releases must be approved by the PMC.</li>
+      <li>Guide the direction of the project.</li>
+      <li>Strive for and help to facilitate a harmonious productive community.</li>
+      <li>Nominate new PMC members and committers.</li>
+      <li>Maintain the project's shared resources, including the
+        codebase repository, mailing lists, websites.</li>
+      <li>Speak on behalf of the project.</li>
+      <li>Maintain these and other guidelines of the project.</li>
+    </ul>
+    <p>
+      The PMC does have a private mailing list on which it can discuss
+      certain issues. However this list is rarely used and every effort
+      is made to conduct all discussion on the public mailing lists.
+    </p>
+
+    <p>
+      Membership of the PMC is by invitation only and must receive
+      consensus approval of the active PMC members.
+    </p> 
+    <p>
+      A PMC member is considered
+      "emeritus" by their own declaration or by not contributing in
+      any form to the project for over six months. An emeritus member may
+      request reinstatement to the PMC. Such reinstatement is subject to
+      consensus approval of the active PMC members. Membership of the PMC can be
+      revoked by unanimous consensus of all active PMC members (other than
+      the member in question).
+    </p>
+
+    <p>
+      The chair of the PMC is appointed by the Board and is an officer of
+      the ASF (Vice President). The chair has primary responsibility to the
+      Board, and has the power to establish rules and procedures for the
+      day-to-day management of the communities for which the PMC is
+      responsible, including the composition of the PMC itself.
+      The chair reports to the board every three months about the status of the
+      project. The PMC may consider the position of PMC chair annually and 
+      may recommend a new chair to the board.
+      Ultimately, however, it is the board's responsibility who it chooses
+      to appoint as the PMC chair.
+      See further explanation of the role of the chair in the
+      <link href="http://www.apache.org/foundation/bylaws.html">ASF Bylaws</link>
+      and the
+      <link href="http://www.apache.org/dev/pmc.html#chair">PMC FAQ</link>
+    </p>
+
+    <section id="report">
+      <title>Quarterly reports to ASF Board</title>
+      <p>
+        Every three months, it is the responsibility of our PMC chair to
+        send a report to the ASF Board. This is mainly concerned with the
+        status of our community, but can also include the technical progress.
+        Further details are in the "committers" SVN in the /board/ directory.
+      </p>
+      <p>
+        The minutes are available for each
+        <link href="http://www.apache.org/foundation/board/calendar.html">
+        board meeting</link>. Our reporting schedule is: Feb, May, Aug, Nov.
+      </p>
+    </section>
+
+    <section id="elect">
+      <title>Electing new committers and PMC members</title>
+      <p>
+        We conduct the vote on the private PMC mailing list to enable a frank
+        discussion.
+        In most cases we will be inviting people to go straight from developer
+        to PMC member, i.e. they simultaneously become committer and PMC
+        member. However, there may be extraordinary cases where we want
+        limited work-related commit access (not also a PMC member).
+        This will be resolved during the discussion and vote.
+        Notes about this process are in the "committers" svn in the
+        pmc/forrest/ directory.
+      </p>
+    </section>
+  </section>
+
+  <section id="decision">
+    <title>Decision making</title>
+    <p>
+      Different types of decisions require different
+      forms of approval. For example, the previous section describes
+      several decisions which require "consensus approval". This
+      section defines how voting is performed, the types of approval, and which
+      types of decision require which type of approval.
+    </p>
+
+    <p>
+      Most day-to-day operations do not require explicit voting - just get on
+      and do the work. See the "Lazy approval" type described below.
+    </p>
+
+    <section id="voting">
+      <title>Voting</title>
+      <p>
+        Certain actions and decisions regarding the project are made by votes
+        on the project development mailing list. Where necessary,
+        PMC voting may take place on the private PMC mailing list.
+      </p>
+      <p>
+        Votes are clearly indicated by subject line starting with [VOTE].
+        Discussion and proposal should have happened prior to the vote.
+        Voting is carried out by replying to the vote mail. 
+        See <link href="#procedure">voting procedure</link> below.
+        Votes are expressed using one of the following symbols:
+      </p>
+
+      <table>
+        <tr>
+          <td colspan="1" rowspan="1"><strong>+1</strong></td>
+          <td colspan="1" rowspan="1">
+            "Yes," "Agree," or "the action should be
+            performed." In general, this vote also indicates a willingness
+            on the behalf of the voter to assist with "making it happen".
+          </td>
+        </tr>
+
+        <tr>
+          <td colspan="1" rowspan="1"><strong>+0</strong></td>
+          <td colspan="1" rowspan="1">
+            This vote indicates a willingness for the action under
+            consideration to go ahead. The voter, however will not be able
+            to help.
+          </td>
+        </tr>
+
+        <tr>
+          <td colspan="1" rowspan="1"><strong>-0</strong></td>
+          <td colspan="1" rowspan="1">
+            This vote indicates that the voter does not, in general, agree with
+            the proposed action but is not concerned enough to prevent the
+            action going ahead.
+          </td>
+        </tr>
+
+        <tr>
+          <td colspan="1" rowspan="1"><strong>-1</strong></td>
+          <td colspan="1" rowspan="1">
+            This is a negative vote. On issues where consensus is required,
+            this vote counts as a <link href="#veto">veto</link>.
+            All vetoes must
+            contain an explanation of why the veto is appropriate. Vetoes with
+            no explanation are void. It may also be appropriate for a -1 vote
+            to include an alternative course of action.
+          </td>
+        </tr>
+
+        <tr>
+          <td colspan="1" rowspan="1"><strong>abstain</strong></td>
+          <td colspan="1" rowspan="1">People can abstain from voting. They can either remain
+          silent or express their reason.
+          </td>
+        </tr>
+      </table>
+
+      <p>
+        All participants in the project are encouraged to show their
+        preference for a particular action by voting. When the votes are
+        tallied, only the votes of PMC members are binding. Non-binding
+        votes are still useful to enable everyone to understand the
+        perception of an action by the wider community.
+      </p>
+
+      <p>
+        Voting can also be applied to changes made to the project codebase. These
+        typically take the form of a veto (-1) in reply to the commit message
+        sent when the commit is made.
+      </p>
+    </section>
+
+    <section id="approvals">
+      <title>Types of approval</title>
+      <p>
+        Different actions require different types of approval:
+      </p>
+
+      <table>
+        <tr>
+          <td colspan="1" rowspan="1"><strong>Consensus approval</strong></td>
+          <td colspan="1" rowspan="1">
+            Consensus approval requires 3 binding +1 votes and no binding vetoes.
+          </td>
+        </tr>
+
+        <tr>
+          <td colspan="1" rowspan="1"><strong>Lazy majority</strong></td>
+          <td colspan="1" rowspan="1">
+            A lazy majority vote requires 3 binding +1 votes and more binding +1
+            votes than -1 votes.
+          </td>
+        </tr>
+
+        <tr>
+          <td colspan="1" rowspan="1"><strong>Lazy approval</strong></td>
+          <td colspan="1" rowspan="1">
+            An action with lazy approval is implicitly allowed unless a -1 vote
+            is received, at which time, depending on the type of action, either
+            lazy majority or consensus approval must be obtained.
+          </td>
+        </tr>
+
+        <tr>
+          <td colspan="1" rowspan="1"><strong>2/3 majority</strong></td>
+          <td colspan="1" rowspan="1">
+            Some actions require a 2/3 majority of active PMC members.
+            Such actions typically affect the foundation
+            of the project (e.g. adopting a new codebase to replace an existing
+            product). The higher threshold is designed to ensure such changes
+            are strongly supported. To pass this vote requires at least 2/3 of
+            binding vote holders to vote +1
+          </td>
+        </tr>
+
+        <tr>
+          <td colspan="1" rowspan="1"><strong>Unanimous consensus</strong></td>
+          <td colspan="1" rowspan="1">
+            All voters with binding votes must vote and there
+            can be no binding vetoes (-1).
+          </td>
+        </tr>
+      </table>
+    </section>
+
+    <section id="veto">
+      <title>Vetoes</title>
+      <p>
+        A valid veto cannot be over-ruled, it can only be withdrawn by its issuer.
+        Any veto must be accompanied by reasoning and be prepared to defend it.
+      </p>
+
+      <p>
+        The validity of a veto, if challenged, can be confirmed by anyone who
+        has a binding vote. This does not necessarily signify agreement with the
+        veto - merely that the veto is valid. In case of disputes about whether
+        a veto is valid, then opinion of the PMC chair is final.
+      </p>
+
+      <p>
+        If you disagree with a valid veto, then you must engage the person
+        casting the veto to further discuss the issues. The vetoer is obliged
+        to vote early and to then work with the community to resolve
+        the matter.
+      </p>
+
+      <p>
+        If a veto is not withdrawn, the action that has been vetoed must
+        be reversed in a timely manner.
+      </p>
+    </section>
+
+    <section id="actions">
+      <title>Actions</title>
+      <p>
+        This section describes the various actions which are undertaken within
+        the project, the corresponding approval required for that action, and
+        those who have binding votes over the action.
+      </p>
+
+      <table>
+        <tr>
+          <th colspan="1" rowspan="1">Action</th>
+          <th colspan="1" rowspan="1">Description</th>
+          <th colspan="1" rowspan="1">Approval</th>
+          <th colspan="1" rowspan="1">Binding Votes</th>
+        </tr>
+        <tr>
+          <td colspan="1" rowspan="1"><strong>Code change</strong></td>
+          <td colspan="1" rowspan="1">
+            A change made to a codebase of the project by a committer.
+            This includes source code, documentation, website content, etc.
+          </td>
+          <td colspan="1" rowspan="1">
+            Lazy approval
+          </td>
+          <td colspan="1" rowspan="1">
+            Active PMC members
+          </td>
+        </tr>
+        <tr>
+          <td colspan="1" rowspan="1"><strong>Release plan</strong></td>
+          <td colspan="1" rowspan="1">
+            Defines the timetable and actions for a release.
+          </td>
+          <td colspan="1" rowspan="1">
+            Lazy majority
+          </td>
+          <td colspan="1" rowspan="1">
+            Active PMC members
+          </td>
+        </tr>
+        <tr>
+          <td colspan="1" rowspan="1"><strong>Product release</strong></td>
+          <td colspan="1" rowspan="1">
+            When a release of one of the project's products is ready, a vote is
+            required to accept the release as an official release of the
+            project.
+          </td>
+          <td colspan="1" rowspan="1">
+            Lazy majority
+          </td>
+          <td colspan="1" rowspan="1">
+            Active PMC members
+          </td>
+        </tr>
+        <tr>
+          <td colspan="1" rowspan="1"><strong>Adoption of new codebase</strong></td>
+          <td colspan="1" rowspan="1">
+            When the codebase for an existing, released product is to be
+            replaced with an alternative codebase. If such a vote fails to
+            gain approval, the existing code base will continue.
+            This also covers the creation of new sub-projects
+            within the project.
+          </td>
+          <td colspan="1" rowspan="1">
+            2/3 majority
+          </td>
+          <td colspan="1" rowspan="1">
+            Active PMC members
+          </td>
+        </tr>
+        <tr>
+          <td colspan="1" rowspan="1"><strong>New committer</strong></td>
+          <td colspan="1" rowspan="1">
+            When a new committer is proposed for the project.
+          </td>
+          <td colspan="1" rowspan="1">
+            Consensus approval
+          </td>
+          <td colspan="1" rowspan="1">
+            Active PMC members
+          </td>
+        </tr>
+        <tr>
+          <td colspan="1" rowspan="1"><strong>New PMC member</strong></td>
+          <td colspan="1" rowspan="1">
+            When a new member is proposed for the PMC.
+          </td>
+          <td colspan="1" rowspan="1">
+            Consensus approval
+          </td>
+          <td colspan="1" rowspan="1">
+            Active PMC members
+          </td>
+        </tr>
+        <tr>
+          <td colspan="1" rowspan="1"><strong>Reinstate emeritus member</strong></td>
+          <td colspan="1" rowspan="1">
+            An emeritus PMC member can be reinstated.
+          </td>
+          <td colspan="1" rowspan="1">
+            Consensus approval
+          </td>
+          <td colspan="1" rowspan="1">
+            Active PMC members (excluding the member in question)
+          </td>
+        </tr>
+        <tr>
+          <td colspan="1" rowspan="1"><strong>Committer removal</strong></td>
+          <td colspan="1" rowspan="1">
+            When removal of commit privileges is sought.
+          </td>
+          <td colspan="1" rowspan="1">
+            Unanimous consensus
+          </td>
+          <td colspan="1" rowspan="1">
+            Active PMC members (excluding the committer in question if a
+            member of the PMC)
+          </td>
+        </tr>
+        <tr>
+          <td colspan="1" rowspan="1"><strong>PMC member removal</strong></td>
+          <td colspan="1" rowspan="1">
+            When removal of a PMC member is sought.
+            See also section 6.5 of the ASF Bylaws whereby the ASF Board may
+            remove a PMC member.
+          </td>
+          <td colspan="1" rowspan="1">
+            Unanimous consensus
+          </td>
+          <td colspan="1" rowspan="1">
+            Active PMC members (excluding the member in question)
+          </td>
+        </tr>
+      </table>
+    </section>
+
+    <section id="timeframe">
+      <title>Voting timeframes</title>
+      <p>
+        Votes are normally open for a period of one week to allow all active voters
+        time to consider the vote. If the vote has not achieved a quorum,
+        then it can be extended for another week. If still no quorum, then
+        the vote fails, and would need to be raised again later.
+        Votes relating to code changes are not subject to a strict timetable,
+        but should be made as timely as possible.
+      </p>
+    </section>
+
+    <section id="procedure">
+      <title>Voting procedure</title>
+      <p>
+        Discussion about the topic would have already happened in a [Proposal]
+        email thread to express the issues and opinions. The [Vote] thread is
+        to ratify the proposal.
+      </p>
+      <p>
+        The instigator sends the Vote email to the dev mailing list.
+        Describe the issue with no ambiguity and in a positive sense.
+        Define the date and time for the end of the vote period.
+      </p>
+      <p>
+        Votes are expressed by replying email using the
+        <link href="#voting">voting symbols</link> defined above.
+        Voters can change their vote during the timeframe.
+        At the end of the vote period, the instigator tallies the number of
+        final votes and reports the results.
+      </p>
+    </section>
+
+    <section id="ultimatum">
+      <title>Ultimatum and breakdown</title>
+      <p>
+        For breakdown situations and those requiring unanimous consensus,
+        if this consensus cannot be reached within the extended timeframe,
+        then the Board expects the chair to act as the officer of the
+        Foundation and make the ultimate decision.
+      </p>
+    </section>
+  </section>
+
+  <section id="communication">
+    <title>Communication channels</title>
+    <p>
+      The primary mechanism for communication is the mailing lists.
+      Anyone can participate, no matter what their time zone.
+      A reliable searchable archive of past discussion is built.
+      Oversight is enabled. Many eyes ensures that the project evolves
+      in a consistent direction.
+    </p>
+    <p>
+      All decisions are made on the "dev" mailing list.
+    </p>
+    <p>
+      The main channel for user support is the "user" mailing list.
+      As is usual with mailing lists, be prepared to wait for an answer.
+    </p>
+    <p>
+      Occasionally we will use other communication channels such as IRC.
+      These are used only for a specific purpose and are not permanently
+      available. This policy ensures that solutions are available in the
+      mailing list archives and enables people to respond at whatever time
+      that they choose. Permanent IRC channels are poor from a community-building
+      point-of-view, as they tend to create time-zone based cliques.
+      So we don't.
+    </p>
+    <p>
+      Similarly, private discussions are discouraged. The rest of the community
+      would not benefit from the understanding that is developed.
+      Off-list discussions put too much load on overworked volunteers.
+    </p>
+  </section>
+
+  <section id="code">
+    <title>Code management</title>
+
+    <p>
+      The term "patch" has two meanings: Developers provide a set of changes
+      via our <link href="site:bugs">Issue Tracker</link> marked for inclusion,
+      which will be applied by a committer. Committers apply their own work
+      directly, but it is still essentially a patch.
+    </p>
+
+    <p>
+      We use the
+      <link href="http://www.apache.org/foundation/glossary.html#CommitThenReview">Commit-then-review</link>
+      method for decision-making about code changes. Please refer to that
+      glossary definition. Note that it does not preclude the committer
+      from making changes to patches prior to their commit, nor mean that the
+      committer can be careless. Rather it is a policy for decision-making.
+    </p>
+
+    <p>
+      There is an important issue where both developers and committers need
+      to pay special attention: "licenses". We must not introduce licensing
+      conditions that go beyond the terms of the <link href="ext:asl">Apache License</link>.
+      If such issues do creep in to our repository, then we must work as
+      quickly as possible to address it and definitely before the next release.
+    </p>
+
+    <p>
+      There are some other problem areas:
+      What should a committer do if the patch is sloppy, containing inconsistent
+      whitespace and other code formatting, which mean that actual changes are not
+      easily visible in the svn diff messages. What if there is poorly constructed
+      (yet working) xml or java code? What if the new functionality is beyond the
+      scope of the project? What if there is a better way to do the task? What if
+      the patch will break the build, thereby preventing other developers from
+      working and causing an unstable trunk?
+    </p>
+
+    <p>
+      The committer has various options: ask the developer to resubmit the patch;
+      change the patch to fix the problems prior to committing; discuss the
+      issues on the dev list; commit it and then draw attention to the
+      issues so that the rest of the community can review and fix it.
+      A combination of these options would appear to be the best approach.
+      Please aim to not break the build, or introduce license problems, or make
+      noisy changes that obscure the real differences.
+    </p>
+
+    <p>
+      Committers should not be afraid to add changes that still need attention.
+      This enables prompt patch application and eases the load on the individual
+      committer. An interesting side-effect is that it encourages community growth.
+    </p>
+
+  </section>
+
+  <section id="develop">
+    <title>Development procedure</title>
+
+<note>
+  This section is still under development. The issues have been discussed
+  on the mailing list. Decisions need to be put into words, so that we do
+  not need to revisit the topic.
+</note>
+
+    <p>
+     Development work is done on the trunk of SVN.
+     Wherever possible, functionality is contained in "plugins". 
+     There are "release branches" of SVN, e.g. forrest_07_branch.
+    </p>
+
+<fixme author="open">
+The following issues still need to be added above.
+There are also some relevant email threads, from which we need to extract info.
+</fixme>
+    <source xml:space="preserve">
+* Define our policy for adding changes to release branch.
+* Define the purpose of the "whiteboard/incubator".
+* Declare that we only really maintain the current release branch
+  (although contributed patches will be applied).
+* When to create a temporary branch for development and when/how to merge.
+  
+
+Some of the many relevant threads in no particular order ...
+
+http://marc.theaimsgroup.com/?t=113344003500003
+Whiteboard usage - rename it to incubator
+
+http://marc.theaimsgroup.com/?t=112798856400001
+Starting a 1.0 development  (Re: [Proposal] rollback)
+
+http://marc.theaimsgroup.com/?l=forrest-dev&amp;m=111968323717620
+http://marc.theaimsgroup.com/?l=forrest-dev&amp;m=111983663526246
+http://marc.theaimsgroup.com/?t=111970529900001
+Project participation and hackability    (was: [VOTE] merge locationmap
+
+http://marc.theaimsgroup.com/?t=112507381300001
+use of whiteboard in forrest
+
+http://marc.theaimsgroup.com/?t=112504310100005
+[Proposal] Development process and a stable trunk
+
+http://marc.theaimsgroup.com/?l=forrest-dev&amp;m=113521408020541
+when to make a release of a branch
+http://marc.theaimsgroup.com/?l=forrest-dev&amp;m=112643002807899
+How to apply an update to 0.7
+
+http://marc.theaimsgroup.com/?t=113616009300002
+[RT] "Last known working snapshot" of Forrest head
+
+http://marc.theaimsgroup.com/?t=113830245600001
+[Proposal] code freeze on dispatcher related resources
+    </source>
+  </section>
+
+<!-- FIXME:
+
+The default is lazy consensus. So just get on with the job
+unless someone asks to stop, review, perhaps revert.
+
+==================
+> We should make mention somewhere of our relationship to other projects
+> Cocoon committers are Forrest committers; something with xml-commons
+
+==================
+Mention the "Contributer License Agreement".
+Who needs to send it? ... is it committers plus major contributers?
+
+==================
+
+-->
+</body>
+</document>
\ No newline at end of file

Propchange: forrest/site/guidelines.source.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Added: forrest/site/gump.source.xml
URL: http://svn.apache.org/viewcvs/forrest/site/gump.source.xml?rev=376128&view=auto
==============================================================================
--- forrest/site/gump.source.xml (added)
+++ forrest/site/gump.source.xml Wed Feb  8 16:26:20 2006
@@ -0,0 +1,47 @@
+<?xml version="1.0" encoding="ISO-8859-1"?><!--
+Copyright 2005 The Apache Software Foundation or its licensors,
+as applicable.
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+    http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.
+--><document> 
+<header> 
+  <title>Apache Gump integration</title> 
+</header> 
+<body> 
+  <p>
+    Apache Gump builds Apache Forrest trunk each day.
+    If dependencies (e.g. Cocoon and certain blocks) fail, then of course
+    the build of Forrest will fail.
+  </p>
+
+  <p>
+    The
+    <link href="http://svn.apache.org/repos/asf/gump/metadata/project/forrest.xml">Gump metadata descriptor</link>
+    for Forrest defines a number of different projects. Notifications are
+    sent to the forrest-dev mailing list.
+  </p>
+
+  <p>
+    The results ...
+  </p>
+
+  <ul>
+    <li><link href="http://vmgump.apache.org/gump/public/forrest/forrest/">forrest</link></li>
+    <li><link href="http://vmgump.apache.org/gump/public/forrest/forrest-forrestbar/">forrest-forrestbar</link></li>
+    <li><link href="http://vmgump.apache.org/gump/public/forrest/forrest-test/">forrest-test</link></li>
+    <li><link href="http://vmgump.apache.org/gump/public/forrest/forrest-whiteboard-forrestdoc/">forrest-whiteboard-forrestdoc</link></li>
+    <li><link href="http://vmgump.apache.org/gump/public/forrest/forrest-whiteboard-forrestdoc-autotest/">forrest-whiteboard-forrestdoc-autotest</link></li>
+  </ul>
+
+</body>
+</document>
\ No newline at end of file

Propchange: forrest/site/gump.source.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Added: forrest/site/images/built-with-forrest-button.png
URL: http://svn.apache.org/viewcvs/forrest/site/images/built-with-forrest-button.png?rev=376128&view=auto
==============================================================================
Binary file - no diff available.

Propchange: forrest/site/images/built-with-forrest-button.png
------------------------------------------------------------------------------
    svn:mime-type = image/png

Added: forrest/site/index.source.xml
URL: http://svn.apache.org/viewcvs/forrest/site/index.source.xml?rev=376128&view=auto
==============================================================================
--- forrest/site/index.source.xml (added)
+++ forrest/site/index.source.xml Wed Feb  8 16:26:20 2006
@@ -0,0 +1,241 @@
+<?xml version="1.0" encoding="ISO-8859-1"?><!--
+  Copyright 2002-2005 The Apache Software Foundation or its licensors,
+  as applicable.
+
+  Licensed under the Apache License, Version 2.0 (the "License");
+  you may not use this file except in compliance with the License.
+  You may obtain a copy of the License at
+
+      http://www.apache.org/licenses/LICENSE-2.0
+
+  Unless required by applicable law or agreed to in writing, software
+  distributed under the License is distributed on an "AS IS" BASIS,
+  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+  See the License for the specific language governing permissions and
+  limitations under the License.
+--><!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.2//EN" "http://forrest.apache.org/dtd/document-v12.dtd">
+<document>
+  <header>
+    <title>Welcome to Apache Forrest</title>
+  </header>
+  <body>
+    <section>
+      <title>Introduction</title>
+      <p>
+        Apache Forrest is a publishing framework that transforms
+        input from various sources into a unified presentation
+        in one or more output formats. The modular and extensible
+        plugin architecture is based on Apache Cocoon and relevant
+        standards, which separates presentation from content.
+        Forrest can generate static documents, or be used as a
+        dynamic server, or be deployed by its automated facility.
+      </p>
+      <note>
+        Please realise that Forrest is still pre-1.0 release version.
+        It is certainly usable for those who are prepared to move with it.
+        See more notes about <link href="#status">status</link> below.
+      </note>
+    </section>
+
+    <section>
+      <title>User-friendly</title>
+      <p>
+        Forrest is designed with the new user in mind.  Much effort has gone
+        into making the process of generating a new site <strong>easy</strong> and
+        <strong>simple</strong>:
+      </p>
+      <ul>
+        <li><strong>Step 1</strong>: Do <code>'forrest seed'</code> to populate
+          the directory with template site structure and contents.</li>
+        <li><strong>Step 2</strong>: Add content by editing docs in
+          task-specific, presentation-neutral XML.</li>
+        <li><strong>Step 3</strong>: Do <code>'forrest run'</code> then use
+          the web browser to immediately review
+          changes at <code>http://localhost:8888/</code>
+        </li>
+        <li><strong>Step 4</strong>: Do <code>'forrest'</code> to generate the
+          complete website from the XML sources.
+          Various styles (known as skins) are available. Custom skins
+          can be developed.</li>
+        <li><strong>Step 5</strong>: For more information about installation
+          and use, see the
+          <link href="site:v0.70//your-project">Using Forrest</link> guide.
+        </li>
+      </ul>
+<!-- FIXME: Needs review for 0.8 -->
+      <note>
+        The first time you run Forrest it will attempt to retrieve some plugins
+        from the Internet. This will happen whenever a new plugin is specified. For more 
+        information see the <link href="site:pluginVersions/overview">plugins documentation</link>.
+      </note>
+      <p>
+        Forrest's focus on low "startup cost" makes it ideal for rapid
+        development of small sites, where time and budget constraints do not
+        allow time-wasting HTML experiments. Of course, that same methodology
+        can scale up to large projects.
+        Your development team does not need Java experience, or even XML skills,
+        to use Forrest. The framework lets you concentrate on content and design.
+      </p>
+      <p>
+        By <strong>separating content from
+          presentation</strong>, providing <strong>content templates</strong>
+        and <strong>pre-written skins</strong>, Forrest is unequalled at enabling
+        content producers to get their message out fast.  This separation of
+        concerns makes Forrest excellent
+        to publish <strong>project documentation</strong> (notably software projects),
+        <strong>intranets</strong>, and <strong>home pages</strong>,
+        and anything else you can think of.
+      </p>
+    </section>
+    <section>
+      <title>Powerful</title>
+      <p>
+        Forrest is far from a quick and dirty solution however.  Forrest is
+        built on the world's leading XML application framework,
+        <link href="ext:cocoon">Apache Cocoon</link>, which provides advanced
+        users with extremely powerful publishing capabilities.
+      </p>
+      <ul>
+        <li>Multiple task-specific source XML formats can be used
+         (<link href="site:v0.70//howto">How-To</link>,
+          <link href="site:v0.70//documentation/faq"><acronym title="Frequently Asked               Questions">FAQ</acronym></link>,
+          <link href="site:v0.70//changes">changelogs</link> and
+          <link href="site:v0.70//todo">todo lists</link> supported natively).
+          Source formats include: Apache xdocs xml format, plain html
+          documents, some Wiki formats, a subset of DocBook, ...
+        </li>
+        <li>Multiple output formats supported, for example HTML and PDF (using
+          <link href="ext:fop">Apache FOP</link>).
+        </li>
+        <li>SVG to PNG rendering (using <link href="ext:batik">Apache
+            Batik</link>). Simply drop the SVG in the appropriate directory
+            and it will be rendered as PNG.</li>
+        <li>
+          Transparent inclusion and aggregation of external content, like
+          <link href="site:v0.70//changes-rss">RSS feeds</link>.
+        </li>
+        <li>
+          Anything else possible with the
+          <link href="ext:cocoon/sitemap">Cocoon sitemap</link>.  Using database
+          queries, <link href="ext:apache-stats">charting</link>, web services
+          integration; the possibilities are constantly growing as Cocoon grows.
+          See the <link href="ext:cocoon/features">Cocoon Features</link> list
+          for the full suite of capabilities.
+        </li>
+        <li>
+          Based on Java and XML standards, Forrest is platform-independent,
+          making for a documentation system that is just as portable as the
+          XML data that it processes.
+        </li>
+      </ul>
+      <section>
+        <title>Static or Dynamic</title>
+        <p>
+          Unique amongst comparable documentation tools, Forrest generates
+          sites that can run both <strong>interactively</strong> as a dynamic
+          web application, or as statically rendered pages.
+        </p>
+        <p>
+          This provides a path for site growth: start off small and static, and
+          if dynamic features (user login, forms processing, runtime data, site
+          search etc) are one day needed, these can be accommodated by switching
+          to webapp mode.
+        </p>
+        <p>
+          Running as a webapp has a major advantage during development:
+          content can be written, and
+          then the rendered output viewed almost instantly in a web browser.
+          This <link href="site:v0.70//your-project/webapp">webapp technique</link>
+          enables Forrest's edit/review cycle to be faster than command-line
+          transformation tools.
+        </p>
+      </section>
+    </section>
+
+    <section>
+      <title>History</title>
+      <p>Apache Forrest was started in January 2002, with the major use-case being to
+        create a consistent and efficient
+        <link href="http://xml.apache.org/">xml.apache.org</link> group of project
+        websites with a
+        uniform, lightweight, easy-to-navigate layout and structure.  In
+        addition, Forrest was to be a Sourceforge-like project management
+        tool, complementing <link href="ext:gump">Apache Gump</link> (hence
+        the name 'Forrest').
+      </p>
+      <p>
+        The focus shifted for Apache Forrest to primarily be a generic documentation
+        tool capable of meeting many needs. Certain relevant project management
+        facilities are being added.
+      </p>
+    </section>
+
+    <section id="status">
+      <title>Project status and website status</title>
+      <p>Apache Forrest is currently progressing rapidly through a series of 0.x
+        releases. It is certainly usable now (despite not yet being version 1.x).
+         See the growing list of
+         <link href="site:live-sites">example sites</link> including
+         many Apache sites.
+      </p>
+      <p>
+        In general, prior to 1.0, ensuring quality of design will be considered
+        more important than retaining backwards-compatibility.  Users
+        (particularly those with custom sitemaps and skins) should be aware that
+        this is evolving software, and read the release notes carefully before
+        upgrading.  That said, we appreciate the commitment in time that
+        adopters make, and will not make capricious or undocumented
+        backwards-incompatible changes.
+      </p>
+
+      <p>
+        Documentation on the Apache Forrest website exists for various versions
+        including the latest release, the current development, and past releases.
+        All versions of Forrest include their own copy of the documentation.
+        To view it, do 'cd site-author; forrest run' and visit
+        http://localhost:8888/ in your browser.
+        The <link href="site:forrest">Apache Forrest website</link> is updated
+        manually as needed, while we develop the
+        <link href="site:asf-forrestbot">forrestbot</link> deployment facility.
+      </p>
+    </section>
+    <section id="news">
+      <title>News and events</title>
+      <p>See the <link href="site:events">events</link> list for more detail.
+      </p>
+      <ul>
+        <li>
+         <!--
+         <link href="http://apachecon.com/">
+           <img src="http://apache.org/images/ac2005eu_135x50.gif"
+             alt="ApacheCon Europe 2005" width="135" height="50"/>
+         </link>
+         -->
+         <link href="http://apachecon.com/">ApacheCon US 2005</link>
+         - Please make plans to join us for the conference in
+         San Diego, California, USA on 10-14 December 2005.
+         See our <link href="site:events">events</link> list for the schedule
+         of Forrest meetings at ApacheCon.
+        </li>
+        <li>Apache Forrest 0.7 was released on 2005-06-23.
+          An architecture for Plugins which enables a smaller Forrest
+          core and the ability to add new features in a modular way.
+        </li>
+      </ul>
+    </section>
+    <section id="help">
+      <title>Help Wanted!</title>
+      <p>
+        Apache Forrest is fairly new, and is in need of developers.
+        If you know (or want to learn) any of XML, Ant, HTML, XSLT, or CSS,
+        then you are qualified to help.
+      </p>
+      <p>
+        As with all Apache projects, Forrest is a meritocracy; the more you
+        put in, the more you get to define the project's future.  See the
+        <link href="site:contrib">"contributing"</link> page for more
+        information.
+      </p>
+    </section>
+  </body>
+</document>
\ No newline at end of file

Propchange: forrest/site/index.source.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Added: forrest/site/issues.source.xml
URL: http://svn.apache.org/viewcvs/forrest/site/issues.source.xml?rev=376128&view=auto
==============================================================================
--- forrest/site/issues.source.xml (added)
+++ forrest/site/issues.source.xml Wed Feb  8 16:26:20 2006
@@ -0,0 +1,181 @@
+<?xml version="1.0" encoding="ISO-8859-1"?><!--
+Copyright 2005 The Apache Software Foundation or its licensors,
+as applicable.
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+    http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.
+--><document>
+<header>
+  <title>Apache Forrest issue tracker</title>
+</header>
+<body>
+
+  <section id="intro">
+    <title>Introduction</title>
+  <p>
+    The Apache Forrest uses an issue tracker call Jira. All of the project
+    contributions should go there (not to the mailing list). This enables us to
+    keep track of contributions and to classify and manage the issues.
+  </p>
+
+  <p>
+    <link href="http://issues.apache.org/jira/browse/FOR">http://issues.apache.org/jira/browse/FOR</link>
+    is the main entry point which provides access to enter, view, search, and
+    add additional comments to issues. There are some additional search
+    <link href="#filters">filters</link> provided below.
+  </p>
+
+  <p>
+    You need to set up an account there before you can create new issues or
+    add comments to existing issues.
+    Anyone can register as a user and report issues.
+    See <link href="#guide">guidelines</link> below.
+  </p>
+
+  <p>
+    Note that the issue tracker is not a discussion or user help forum.
+    Please discuss issues about using Forrest on the user or dev mailing list.
+  </p>
+
+  </section>
+
+  <section id="guide">
+    <title>Guidelines and hints for reporting issues</title>
+    <ul>
+      <li>Ensure that an issue does not already exist.</li>
+      <li>Use Jira's powerful "Find Issues" ability. Set the Project and
+        Status fields. See the Help about boolean queries in the Query field.
+      </li>
+      <li>Follow the prompts below each entry field.</li>
+      <li>If you don't know the answer to a particular question, then
+        leave the field blank.</li>
+      <li>Add a concise initial Description, then add more Comments later to
+        further describe the issue.</li>
+      <li>Other people will follow up and enhance your description and
+        classifications.</li>
+      <li>If details about your computing environment are relevant
+        (e.g. Java version or operating system) then add them to a Comment.</li>
+    </ul>
+
+    <section id="priority">
+      <title>Special fields: Priority (a.k.a. Severity)</title>
+      <p>
+        The Priority is the severity according to the issue reporter. This will
+        be a guideline to the development team to identify the most urgent
+        issues. It is not a guarantee that a Critical issue will be resolved
+        before a Major issue.
+      </p>
+      <p>
+        Follow the Jira help icon to see the definition of the options.
+      </p>
+    </section>
+
+    <section id="urgency">
+      <title>Special fields: Urgency</title>
+      <p>
+        The project team will classify this according to their urgency. The aim is
+        to be able to see at a glance which issues should be attended to, so that
+        developers can operate efficiently and so that the product can be released
+        as soon as possible. Some issues hinder the project, so need to be identified.
+      </p>
+
+      <p>
+        We use the following definition of the options.
+      </p>
+
+      <ul>
+        <li>
+          None: The default. Not yet classified.
+        </li>
+        <li>
+          Blocker: Prevents other developers from working; or critical issue with functionality;
+          or holds up the implementation of other functionality.
+          Cannot release until it is fixed. Will be fixed ASAP.
+        </li>
+        <li>
+          Urgent: Is a key new feature; or affects many users. Will be fixed before the next
+          release.
+        </li>
+        <li>
+          Normal: If this issue scratches the itch of any particular developer, then
+          they should help to solve it and provide a patch.
+        </li>
+        <li>
+          Low: If this issue bothers you, then fix it because it is not a high priority
+          for the project.
+        </li>
+      </ul>
+    </section>
+
+    <section id="permissions">
+      <title>Permissions</title>
+      <ul>
+        <li>
+          Anyone: Browse, Find, View.
+        </li>
+        <li>
+          jira-users: People who have registered as a user of the ASF Jira.
+          Create, Edit, Comment, Attach, Vote, Watch.
+          The reporter can also Close.
+        </li>
+        <li>
+          forrest-developers: People who are Forrest committers.
+          Resolve, Close, Delete issues, Delete coments, Link, Assign, Administer Projects.
+        </li>
+        <li>
+          Some committers are global adminstrators: Edit user details, Add users to groups, Configure.
+        </li>
+      </ul>
+    </section>
+  </section>
+
+  <section id="filters">
+    <title>Some search filters</title>
+    <p>
+      Various general searches are available from the
+      <link href="http://issues.apache.org/jira/browse/FOR">front page</link>,
+      e.g. "open issues classified by component", or "Added recently".
+      The following are some special filters.
+    </p>
+
+    <ul>
+      <li>
+        <link href="http://issues.apache.org/jira/secure/IssueNavigator.jspa?mode=hide&amp;requestId=12310472">FOR-open-with-patch</link>
+        - Committers need to visit this regularly and deal with the patches.
+      </li>
+      <li>
+        <link href="http://issues.apache.org/jira/secure/IssueNavigator.jspa?mode=hide&amp;requestId=12310473">FOR-urgency-blocker</link>
+        - Issues that the project considers to be Blockers.
+      </li>
+      <li>
+        <link href="http://issues.apache.org/jira/secure/IssueNavigator.jspa?mode=hide&amp;requestId=12310475">FOR-urgency-urgent</link>
+        - Issues that the project considers to be Urgent.
+      </li>
+      <li>
+        <link href="http://issues.apache.org/jira/browse/FOR?report=com.atlassian.jira.plugin.system.project:roadmap-panel">Roadmap</link>
+        - Issues that are scheduled to be investigated.
+      </li>
+      <li>
+        <link href="http://issues.apache.org/jira/secure/IssueNavigator.jspa?mode=hide&amp;requestId=12310476">FOR-unresolved-with-attachment</link>
+        - Issues that have demonstrations of problems, but no solution or patch.
+        Of course it will include FOR-open-with-patch.
+        (Note that this filter searches for the string "attach" so will not find all.)
+      </li>
+      <li>
+        <link href="http://issues.apache.org/jira/secure/IssueNavigator.jspa?mode=hide&amp;requestId=12310043">FOR-unscheduled</link>
+        - Issues that have not yet been scheduled to be fixed for a certain version.
+      </li>
+    </ul>
+  </section>
+
+</body>
+</document>
\ No newline at end of file

Propchange: forrest/site/issues.source.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Added: forrest/site/license.source.xml
URL: http://svn.apache.org/viewcvs/forrest/site/license.source.xml?rev=376128&view=auto
==============================================================================
--- forrest/site/license.source.xml (added)
+++ forrest/site/license.source.xml Wed Feb  8 16:26:20 2006
@@ -0,0 +1,236 @@
+<?xml version="1.0" encoding="ISO-8859-1"?><!--
+  Copyright 2002-2005 The Apache Software Foundation or its licensors,
+  as applicable.
+
+  Licensed under the Apache License, Version 2.0 (the "License");
+  you may not use this file except in compliance with the License.
+  You may obtain a copy of the License at
+
+      http://www.apache.org/licenses/LICENSE-2.0
+
+  Unless required by applicable law or agreed to in writing, software
+  distributed under the License is distributed on an "AS IS" BASIS,
+  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+  See the License for the specific language governing permissions and
+  limitations under the License.
+--><!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.2//EN" "http://forrest.apache.org/dtd/document-v12.dtd">
+<document>
+ <header>
+  <title>Apache License</title>
+ </header>
+
+<body>
+  <p>
+    The Forrest distribution is licensed according to the liberal
+    Apache License. See the files in the top-level of the Forrest
+    distribution called LICENSE.txt (copy shown below) and NOTICE.txt
+    and see licenses for accompanying products in the "lib" directories
+    of the Forrest core and plugins.
+    See full explanation and FAQs regarding the
+    <link href="ext:asf/asl">Apache License</link>.
+  </p>
+<source xml:space="preserve"><![CDATA[
+                                 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]]]><![CDATA[
+
+   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.
+]]></source>
+</body>
+</document>
\ No newline at end of file

Propchange: forrest/site/license.source.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Added: forrest/site/linkmap.source.xml
URL: http://svn.apache.org/viewcvs/forrest/site/linkmap.source.xml?rev=376128&view=auto
==============================================================================
--- forrest/site/linkmap.source.xml (added)
+++ forrest/site/linkmap.source.xml Wed Feb  8 16:26:20 2006
@@ -0,0 +1,77 @@
+<?xml version="1.0" encoding="ISO-8859-1"?><!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.2//EN" "http://forrest.apache.org/dtd/document-v12.dtd">
+<document><header><title>Site Linkmap</title></header><body><section><title>Table of Contents</title><ul><li><a href="">Forrest</a>   _________________________  <em>site</em></li><ul>
+
+  
+  <ul><li><a href="">About</a>   _________________________  <em>about</em></li><ul>
+    <ul><li><a href="index.html">Index</a>   _________________________  <em>index</em></li></ul>
+    <ul><li><a href="license.html">License</a>   _________________________  <em>license</em></li></ul>
+    <ul><li><a href="http://forrest.apache.org/mirrors.cgi">Download</a>   _________________________  <em>download</em></li></ul>
+    
+    
+    <ul><li><a href="who.html">Who we are</a>   _________________________  <em>who</em></li></ul>
+    <ul><li><a href="events.html">Events</a>   _________________________  <em>events</em></li></ul>
+    <ul><li><a href="flyer.html">Flyer</a>   _________________________  <em>flyer</em></li></ul>
+    <ul><li><a href="live-sites.html">Example sites</a>   _________________________  <em>live-sites</em></li></ul>
+  </ul></ul>
+  
+  <ul><li><a href="">Getting Involved</a>   _________________________  <em>getting-involved</em></li><ul>
+    <ul><li><a href="contrib.html">Contributing</a>   _________________________  <em>contrib</em></li><ul>
+      
+    </ul></ul>
+    <ul><li><a href="http://svn.apache.org/viewcvs.cgi/forrest/trunk/">Browse SVN</a>   _________________________  <em>SVN</em></li></ul>
+    <ul><li><a href="mail-lists.html">Mail lists</a>   _________________________  <em>mail-lists</em></li><ul>
+      
+      
+      
+    </ul></ul>
+    <ul><li><a href="issues.html">Bugs and Issues</a>   _________________________  <em>bugs</em></li></ul>
+    <ul><li><a href="forrest-issues.html">Open Issues</a>   _________________________  <em>forrest-issues</em></li></ul>
+    <ul><li><a href="gump.html">Gump Integration</a>   _________________________  <em>gump-forrest</em></li></ul>
+    <ul><li><a href="guidelines.html">Project guidelines</a>   _________________________  <em>guidelines</em></li></ul>
+    <ul><li><a href="committed.html">Being committed</a>   _________________________  <em>committed</em></li></ul>
+    <ul><li><a href="forrest-friday.html">ForrestFriday</a>   _________________________  <em>forrest-friday</em></li></ul>
+    <ul><li><a href="zone.html">Zone notes</a>   _________________________  <em>zone</em></li></ul>
+    <ul><li><a href="plan/">Planning notes</a>   _________________________  <em>plan</em></li><ul>
+      <ul><li><a href="plan/index.html">Overview</a>   _________________________  <em>overview</em></li></ul>
+      <ul><li><a href="plan/internal-xhtml.html">Internal XHTML</a>   _________________________  <em>internal-xhtml</em></li></ul>
+    </ul></ul>
+  </ul></ul>
+
+  <ul><li><a href="">Proposals</a>   _________________________  <em>proposals</em></li><ul>
+    <ul><li><a href="proposal-asf-forrestbot.html">ASF Forrestbot</a>   _________________________  <em>asf-forrestbot</em></li></ul>
+  </ul></ul>
+
+  <ul><li><a href="">Related projects</a>   _________________________  <em>references</em></li><ul>
+    <ul><li><a href="http://gump.apache.org/">Apache Gump</a>   _________________________  <em>gump</em></li></ul>
+    <ul><li><a href="http://cocoon.apache.org/">Apache Cocoon</a>   _________________________  <em>cocoon</em></li></ul>
+    <ul><li><a href="http://lenya.apache.org/">Apache Lenya</a>   _________________________  <em>lenya</em></li></ul>
+    <ul><li><a href="http://xml.apache.org/">Apache XML</a>   _________________________  <em>xml</em></li></ul>
+  </ul></ul>
+
+  
+
+  
+
+  
+  
+  
+
+  <ul><li><a href="tools/">Tools</a>   _________________________  <em>tools</em></li><ul>
+    <ul><li><a href="tools/index.html">Index</a>   _________________________  <em>index</em></li></ul>
+    <ul><li><a href="tools/forrestbar.html">ForrestBar</a>   _________________________  <em>forrestbar</em></li></ul>
+    <ul><li><a href="tools/forrestbot.html">Forrestbot</a>   _________________________  <em>forrestbot</em></li></ul>
+    <ul><li><a href="tools/forrestbot-web-interface.html">Forrestbot Webapp</a>   _________________________  <em>forrestbot-web-interface</em></li></ul>
+    <ul><li><a href="tools/eclipse.html">Eclipse Plugin</a>   _________________________  <em>eclipse</em></li></ul>
+    <ul><li><a href="tools/xxe.html">XXE-Editor</a>   _________________________  <em>xxe</em></li></ul>
+  </ul></ul>
+
+  
+  
+    
+
+    
+
+    
+
+    
+</ul></ul></section></body></document>
\ No newline at end of file

Propchange: forrest/site/linkmap.source.xml
------------------------------------------------------------------------------
    svn:eol-style = native



Mime
View raw message