forrest-svn mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r345799 - in /forrest/site: docs_0_80/howto/howto-structurer-install.html docs_0_80/howto/howto-structurer-install.pdf guidelines.html guidelines.pdf
Date Mon, 21 Nov 2005 01:02:37 GMT
Author: crossley
Date: Sun Nov 20 17:02:31 2005
New Revision: 345799

Automatic publish from forrestbot


Modified: forrest/site/docs_0_80/howto/howto-structurer-install.html
--- forrest/site/docs_0_80/howto/howto-structurer-install.html (original)
+++ forrest/site/docs_0_80/howto/howto-structurer-install.html Sun Nov 20 17:02:31 2005
@@ -446,7 +446,7 @@
        For the moment we will use a special seed template called seed-v2. We still 
         need to fix issues of the dispatcher, so that it really can replace old 
         fashion skins. Like performance, standalone contracts, other testing output/input
formats - using POJO based 
-        processing will help solving this.  All this will ATM happen in the v2 seed-target
till the dispatcher will 
+        processing will help solving this.  All this will happen in the v2 seed-target until
the dispatcher will 
         be released to the stable plugins. So make regular updates of your forrest-trunk
to keep track.
@@ -477,8 +477,7 @@
         Now you have finished the preparation and the setup to finally do
         <span class="codefrag">'forrest run'</span> and
         point your browser to <span class="codefrag">http://localhost:8888/</span>
and you will see the default
-        dispatcher-based site. Use your browser's menu option "View -&gt; Page Style"
to switch
-        themes.
+        dispatcher-based site.
 <a name="N10090"></a><a name="availableContracts"></a>
 <h3 class="underlined_5">Available contracts</h3>

Modified: forrest/site/docs_0_80/howto/howto-structurer-install.pdf
Binary files - no diff available.

Modified: forrest/site/guidelines.html
--- forrest/site/guidelines.html (original)
+++ forrest/site/guidelines.html Sun Nov 20 17:02:31 2005
@@ -246,8 +246,10 @@
    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
-   (<a href="">ASF</a>) which holds
-   the copyright for all Apache projects. The ASF website explains the
+   (<a href="">ASF</a>) 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
@@ -281,13 +283,15 @@
       <a href="">ASF ByLaws</a>
       and the
       <a href="">How it works</a>
-      as well as the
+      the 
+      <a href="">FAQs</a>
+      about the Foundation, and the
       <a href="">Incubator project</a>.
-<a name="N1003C"></a><a name="roles"></a>
+<a name="N10040"></a><a name="roles"></a>
 <h2 class="underlined_10">Roles and responsibilities</h2>
 <div class="section">
 <p>The meritocracy enables various roles as defined in the
@@ -308,7 +312,7 @@
-<a name="N10068"></a><a name="pmc"></a>
+<a name="N1006C"></a><a name="pmc"></a>
 <h2 class="underlined_10">Project Management Committee (PMC)</h2>
 <div class="section">
 <p>The Apache Forrest project was established in January 2002 and became a
@@ -386,7 +390,7 @@
       <a href="">PMC FAQ</a>
-<a name="N100B5"></a><a name="report"></a>
+<a name="N100B9"></a><a name="report"></a>
 <h3 class="underlined_5">Quarterly reports to ASF Board</h3>
         Every three months, it is the responsibility of our PMC chair to
@@ -399,7 +403,7 @@
         <a href="">
         board meeting</a>. Our reporting schedule is: Feb, May, Aug, Nov.
-<a name="N100C6"></a><a name="elect"></a>
+<a name="N100CA"></a><a name="elect"></a>
 <h3 class="underlined_5">Electing new committers and PMC members</h3>
         We conduct the vote on the private PMC mailing list to enable a frank
@@ -415,7 +419,7 @@
-<a name="N100D1"></a><a name="decision"></a>
+<a name="N100D5"></a><a name="decision"></a>
 <h2 class="underlined_10">Decision making</h2>
 <div class="section">
@@ -429,7 +433,7 @@
       Most day-to-day operations do not require explicit voting - just get on
       and do the work. See the "Lazy approval" type described below.
-<a name="N100DD"></a><a name="voting"></a>
+<a name="N100E1"></a><a name="voting"></a>
 <h3 class="underlined_5">Voting</h3>
         Certain actions and decisions regarding the project are made by votes
@@ -518,7 +522,7 @@
         typically take the form of a veto (-1) in reply to the commit message
         sent when the commit is made.
-<a name="N10141"></a><a name="approvals"></a>
+<a name="N10145"></a><a name="approvals"></a>
 <h3 class="underlined_5">Types of approval</h3>
         Different actions require different types of approval:
@@ -584,7 +588,7 @@
-<a name="N10194"></a><a name="veto"></a>
+<a name="N10198"></a><a name="veto"></a>
 <h3 class="underlined_5">Vetoes</h3>
         A valid veto cannot be over-ruled, it can only be withdrawn by its issuer.
@@ -606,7 +610,7 @@
         If a veto is not withdrawn, the action that has been vetoed must
         be reversed in a timely manner.
-<a name="N101A7"></a><a name="actions"></a>
+<a name="N101AB"></a><a name="actions"></a>
 <h3 class="underlined_5">Actions</h3>
         This section describes the various actions which are undertaken within
@@ -770,7 +774,7 @@
-<a name="N102A3"></a><a name="timeframe"></a>
+<a name="N102A7"></a><a name="timeframe"></a>
 <h3 class="underlined_5">Voting timeframes</h3>
         Votes are normally open for a period of one week to allow all active voters
@@ -780,7 +784,7 @@
         Votes relating to code changes are not subject to a strict timetable,
         but should be made as timely as possible.
-<a name="N102AD"></a><a name="procedure"></a>
+<a name="N102B1"></a><a name="procedure"></a>
 <h3 class="underlined_5">Voting procedure</h3>
         Discussion about the topic would have already happened in a [Proposal]
@@ -799,7 +803,7 @@
         At the end of the vote period, the instigator tallies the number of
         final votes and reports the results.
-<a name="N102C1"></a><a name="ultimatum"></a>
+<a name="N102C5"></a><a name="ultimatum"></a>
 <h3 class="underlined_5">Ultimatum and breakdown</h3>
         For breakdown situations and those requiring unanimous consensus,
@@ -810,7 +814,7 @@
-<a name="N102CC"></a><a name="communication"></a>
+<a name="N102D0"></a><a name="communication"></a>
 <h2 class="underlined_10">Communication channels</h2>
 <div class="section">
@@ -844,7 +848,7 @@
-<a name="N102E2"></a><a name="code"></a>
+<a name="N102E6"></a><a name="code"></a>
 <h2 class="underlined_10">Code management</h2>
 <div class="section">

Modified: forrest/site/guidelines.pdf
Binary files - no diff available.

View raw message