forrest-svn mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cross...@apache.org
Subject svn commit: r152645 - in forrest/site: contrib.html forrest-issues.html forrest-issues.pdf guidelines.html guidelines.pdf index.html index.pdf linkmap.html linkmap.pdf mail-lists.html proposal-asf-forrestbot.html proposal-asf-publish.html
Date Tue, 08 Feb 2005 06:36:39 GMT
Author: crossley
Date: Mon Feb  7 22:36:36 2005
New Revision: 152645

URL: http://svn.apache.org/viewcvs?view=rev&rev=152645
Log:
Publish the "Project guidelines".

Added:
    forrest/site/guidelines.html   (with props)
    forrest/site/guidelines.pdf   (with props)
Modified:
    forrest/site/contrib.html
    forrest/site/forrest-issues.html
    forrest/site/forrest-issues.pdf
    forrest/site/index.html
    forrest/site/index.pdf
    forrest/site/linkmap.html
    forrest/site/linkmap.pdf
    forrest/site/mail-lists.html
    forrest/site/proposal-asf-forrestbot.html
    forrest/site/proposal-asf-publish.html

Modified: forrest/site/contrib.html
URL: http://svn.apache.org/viewcvs/forrest/site/contrib.html?view=diff&r1=152644&r2=152645
==============================================================================
--- forrest/site/contrib.html (original)
+++ forrest/site/contrib.html Mon Feb  7 22:36:36 2005
@@ -125,6 +125,9 @@
 <div class="menuitem">
 <a title="" href="http://brutus.apache.org/gump/public/forrest/">Gump Integration</a>
 </div>
+<div class="menuitem">
+<a title="" href="guidelines.html">Project guidelines</a>
+</div>
 </div>
 <div onclick="SwitchMenu('menu_1.2', 'skin/')" id="menu_1.2Title" class="menutitle">Proposals</div>
 <div id="menu_1.2" class="menuitemgroup">

Modified: forrest/site/forrest-issues.html
URL: http://svn.apache.org/viewcvs/forrest/site/forrest-issues.html?view=diff&r1=152644&r2=152645
==============================================================================
--- forrest/site/forrest-issues.html (original)
+++ forrest/site/forrest-issues.html Mon Feb  7 22:36:36 2005
@@ -125,6 +125,9 @@
 <div class="menuitem">
 <a title="" href="http://brutus.apache.org/gump/public/forrest/">Gump Integration</a>
 </div>
+<div class="menuitem">
+<a title="" href="guidelines.html">Project guidelines</a>
+</div>
 </div>
 <div onclick="SwitchMenu('menu_1.2', 'skin/')" id="menu_1.2Title" class="menutitle">Proposals</div>
 <div id="menu_1.2" class="menuitemgroup">
@@ -172,9 +175,6 @@
 <a href="#%5BFOR-379%5D+Make+plugin+test+a+part+of+%22build+test%22">[FOR-379] Make plugin test a part of "build test"</a>
 </li>
 <li>
-<a href="#%5BFOR-373%5D+Excel+to+Forrest+stylesheets">[FOR-373] Excel to Forrest stylesheets</a>
-</li>
-<li>
 <a href="#%5BFOR-354%5D+Add+plugin+libraries+to+classpath">[FOR-354] Add plugin libraries to classpath</a>
 </li>
 <li>
@@ -237,6 +237,9 @@
 <li>
 <a href="#%5BFOR-187%5D+Redefine+project+documentation+dirs">[FOR-187] Redefine project documentation dirs</a>
 </li>
+<li>
+<a href="#%5BFOR-185%5D+Can%27t+get+svg+files+served+along+with+the+PNG">[FOR-185] Can't get svg files served along with the PNG</a>
+</li>
 </ul>
 </div>
 <div class="frame note">
@@ -283,65 +286,7 @@
 <br>
 This will result in all plugins being tested as part of the normal test process.</p>
 </div>
-<a name="N1003B"></a><a name="%5BFOR-373%5D+Excel+to+Forrest+stylesheets"></a>
-<h2 class="underlined_10">[FOR-373] Excel to Forrest stylesheets</h2>
-<div class="section">
-<p>
-<a class="external" href="http://issues.cocoondev.org//browse/FOR-373">http://issues.cocoondev.org//browse/FOR-373</a>
-</p>
-<p>I'm trying to get some tables out of Excel into
-<br>
-Forrest ... should be easy since Excel writes
-<br>
-legible XML [1].
-<br>
-
-<br>
-I put together a sitemap.xmap [2] for *-table.xml.
-<br>
-
-<br>
-I started writing my table2document.xsl [3] but
-<br>
-it didn't match anything, i.e. the version below
-<br>
-doesn't match anything. Matching &quot;/*/*&quot; gives me
-<br>
-the 2nd level elements: DocumentProperties, ...,
-<br>
-and Worksheets.
-<br>
-
-<br>
-After removing all references to namespaces (xmlns)
-<br>
-and replacing &quot;:&quot; with &quot;_&quot; it works.
-<br>
-
-<br>
-Can any XSL guru help me to get the XSLT working
-<br>
-without modifying the Excel-output first?
-<br>
-
-<br>
-Thanks,
-<br>
-Johannes
-<br>
-
-<br>
-See Attachments
-<br>
-[1] Excel XML output: test2-table.xml
-<br>
-[2] documents/sitemap.xmap
-<br>
-[3] table2document.xsl
-<br>
-</p>
-</div>
-<a name="N10049"></a><a name="%5BFOR-354%5D+Add+plugin+libraries+to+classpath"></a>
+<a name="N1003B"></a><a name="%5BFOR-354%5D+Add+plugin+libraries+to+classpath"></a>
 <h2 class="underlined_10">[FOR-354] Add plugin libraries to classpath</h2>
 <div class="section">
 <p>
@@ -349,7 +294,7 @@
 </p>
 <p>Some plugins (e.g. rtf) require additional libraries to be used. At present these need to be copied across to the forrest/main/webapp/WEB-INF/lib directory. It would be far better if the relevant lib directories of plugins were put on the classpath by the forrest execution scripts.</p>
 </div>
-<a name="N10057"></a><a name="%5BFOR-343%5D+Upgrading+Plugins"></a>
+<a name="N10049"></a><a name="%5BFOR-343%5D+Upgrading+Plugins"></a>
 <h2 class="underlined_10">[FOR-343] Upgrading Plugins</h2>
 <div class="section">
 <p>
@@ -361,7 +306,7 @@
 <br>
 We need a traget in the buildfile that will upgrade an indicated plugin when possible. This can then (optionally) be used when running Forrest to automatically upgrade plugins.</p>
 </div>
-<a name="N10065"></a><a name="%5BFOR-342%5D+%5BPatch%5D+%27scale-dev%27++CSS+enhancement+for+leather-dev"></a>
+<a name="N10057"></a><a name="%5BFOR-342%5D+%5BPatch%5D+%27scale-dev%27++CSS+enhancement+for+leather-dev"></a>
 <h2 class="underlined_10">[FOR-342] [Patch] 'scale-dev'  CSS enhancement for leather-dev</h2>
 <div class="section">
 <p>
@@ -375,7 +320,7 @@
 <br>
 working well.</p>
 </div>
-<a name="N10073"></a><a name="%5BFOR-341%5D+Plugin+resources+are+not+copied+to+site"></a>
+<a name="N10065"></a><a name="%5BFOR-341%5D+Plugin+resources+are+not+copied+to+site"></a>
 <h2 class="underlined_10">[FOR-341] Plugin resources are not copied to site</h2>
 <div class="section">
 <p>
@@ -383,7 +328,7 @@
 </p>
 <p>If a plugin contains some resources required in a statically built site (such as Javascripts) they are not copied across to build/site when  &quot;forrest site&quot; is run</p>
 </div>
-<a name="N10081"></a><a name="%5BFOR-340%5D+plugin+build+file"></a>
+<a name="N10073"></a><a name="%5BFOR-340%5D+plugin+build+file"></a>
 <h2 class="underlined_10">[FOR-340] plugin build file</h2>
 <div class="section">
 <p>
@@ -407,7 +352,7 @@
 <br>
 </p>
 </div>
-<a name="N1008F"></a><a name="%5BFOR-298%5D+Revise+the+build+system+to+remove+relics+which+were+prior+to+copyless+method"></a>
+<a name="N10081"></a><a name="%5BFOR-298%5D+Revise+the+build+system+to+remove+relics+which+were+prior+to+copyless+method"></a>
 <h2 class="underlined_10">[FOR-298] Revise the build system to remove relics which were prior to copyless method</h2>
 <div class="section">
 <p>
@@ -415,7 +360,7 @@
 </p>
 <p>There are some old targets in the build system that can be removed following the move to being &quot;copyless&quot;. Some targets such as &quot;copy-sitemap&quot; have already had such parts removed, leaving them with a different purpose which doesn't match their name.</p>
 </div>
-<a name="N1009D"></a><a name="%5BFOR-284%5D+%27error%3A%27+prepending+problems"></a>
+<a name="N1008F"></a><a name="%5BFOR-284%5D+%27error%3A%27+prepending+problems"></a>
 <h2 class="underlined_10">[FOR-284] 'error:' prepending problems</h2>
 <div class="section">
 <p>
@@ -431,7 +376,7 @@
 <br>
 @see declare-broken-site-links.xsl in teh core templates for more info.</p>
 </div>
-<a name="N100AB"></a><a name="%5BFOR-282%5D+Custom+search+engines"></a>
+<a name="N1009D"></a><a name="%5BFOR-282%5D+Custom+search+engines"></a>
 <h2 class="underlined_10">[FOR-282] Custom search engines</h2>
 <div class="section">
 <p>
@@ -445,7 +390,7 @@
 <br>
 </p>
 </div>
-<a name="N100B9"></a><a name="%5BFOR-277%5D+investigate+use+of+forrest-0.6-dev+as+webapp+with+Tomcat+5"></a>
+<a name="N100AB"></a><a name="%5BFOR-277%5D+investigate+use+of+forrest-0.6-dev+as+webapp+with+Tomcat+5"></a>
 <h2 class="underlined_10">[FOR-277] investigate use of forrest-0.6-dev as webapp with Tomcat 5</h2>
 <div class="section">
 <p>
@@ -463,7 +408,7 @@
 <br>
 &nbsp;Wed, 4 Aug 2004 10:18:34 -0500</p>
 </div>
-<a name="N100C7"></a><a name="%5BFOR-259%5D+openoffice+files+can+skip+sections"></a>
+<a name="N100B9"></a><a name="%5BFOR-259%5D+openoffice+files+can+skip+sections"></a>
 <h2 class="underlined_10">[FOR-259] openoffice files can skip sections</h2>
 <div class="section">
 <p>
@@ -487,7 +432,7 @@
 <br>
 The last two lines are not translated into sections.</p>
 </div>
-<a name="N100D5"></a><a name="%5BFOR-247%5D+Tigris+*.css+need+cleanup+to+remove+our+local+changes"></a>
+<a name="N100C7"></a><a name="%5BFOR-247%5D+Tigris+*.css+need+cleanup+to+remove+our+local+changes"></a>
 <h2 class="underlined_10">[FOR-247] Tigris *.css need cleanup to remove our local changes</h2>
 <div class="section">
 <p>
@@ -497,7 +442,7 @@
 <br>
 <a href="http://marc.theaimsgroup.com/?l=forrest-dev&m=109169132601758">http://marc.theaimsgroup.com/?l=forrest-dev&amp;m=109169132601758</a></p>
 </div>
-<a name="N100E3"></a><a name="%5BFOR-241%5D+forrest+undoes+entity+resolution"></a>
+<a name="N100D5"></a><a name="%5BFOR-241%5D+forrest+undoes+entity+resolution"></a>
 <h2 class="underlined_10">[FOR-241] forrest undoes entity resolution</h2>
 <div class="section">
 <p>
@@ -543,7 +488,7 @@
 <br>
 the ampersand in the link href attribute is not.</p>
 </div>
-<a name="N100F1"></a><a name="%5BFOR-237%5D+xml+stylesheets+unnecessary+copied+to+deployed+site"></a>
+<a name="N100E3"></a><a name="%5BFOR-237%5D+xml+stylesheets+unnecessary+copied+to+deployed+site"></a>
 <h2 class="underlined_10">[FOR-237] xml stylesheets unnecessary copied to deployed site</h2>
 <div class="section">
 <p>
@@ -551,7 +496,7 @@
 </p>
 <p>Why are forrest.css.xslt and skinconf.xsl copied over to the deployment location? They're not required there, and therefore should not be copied.</p>
 </div>
-<a name="N100FF"></a><a name="%5BFOR-232%5D+skin+fetching+cleanup"></a>
+<a name="N100F1"></a><a name="%5BFOR-232%5D+skin+fetching+cleanup"></a>
 <h2 class="underlined_10">[FOR-232] skin fetching cleanup</h2>
 <div class="section">
 <p>
@@ -559,7 +504,7 @@
 </p>
 <p>Fix skin fetching.  It's an ugly combination of XSL and unusual ant tasks.  It's also broken in at least one way: you get a malformed URL exception if you try to use a skin that doesn't exist.  It should instead just say it doesn't exist.</p>
 </div>
-<a name="N1010D"></a><a name="%5BFOR-229%5D+SVG+not+converted+to+PNG"></a>
+<a name="N100FF"></a><a name="%5BFOR-229%5D+SVG+not+converted+to+PNG"></a>
 <h2 class="underlined_10">[FOR-229] SVG not converted to PNG</h2>
 <div class="section">
 <p>
@@ -567,7 +512,7 @@
 </p>
 <p>See <a href="http://mail-archives.apache.org/eyebrowse/BrowseList?listName=dev@forrest.apache.org&by=thread&from=828955">http://mail-archives.apache.org/eyebrowse/BrowseList?listName=dev@forrest.apache.org&amp;by=thread&amp;from=828955</a></p>
 </div>
-<a name="N1011B"></a><a name="%5BFOR-215%5D+site.lucene+name+colaps+with+site.html+request"></a>
+<a name="N1010D"></a><a name="%5BFOR-215%5D+site.lucene+name+colaps+with+site.html+request"></a>
 <h2 class="underlined_10">[FOR-215] site.lucene name colaps with site.html request</h2>
 <div class="section">
 <p>
@@ -589,7 +534,7 @@
 <br>
 </p>
 </div>
-<a name="N10129"></a><a name="%5BFOR-211%5D+whole-site+html+and+pdf%3A+broken+ext+links"></a>
+<a name="N1011B"></a><a name="%5BFOR-211%5D+whole-site+html+and+pdf%3A+broken+ext+links"></a>
 <h2 class="underlined_10">[FOR-211] whole-site html and pdf: broken ext links</h2>
 <div class="section">
 <p>
@@ -597,7 +542,7 @@
 </p>
 <p>In the the generated site.html all of the external links are broken (i.e. the href attributes are like ... error:#ext:forrest).</p>
 </div>
-<a name="N10137"></a><a name="%5BFOR-210%5D+whole-site+html+and+pdf%3A+broken+link+faq%2C+broken+image+links"></a>
+<a name="N10129"></a><a name="%5BFOR-210%5D+whole-site+html+and+pdf%3A+broken+link+faq%2C+broken+image+links"></a>
 <h2 class="underlined_10">[FOR-210] whole-site html and pdf: broken link faq, broken image links</h2>
 <div class="section">
 <p>
@@ -609,7 +554,7 @@
 <br>
 </p>
 </div>
-<a name="N10145"></a><a name="%5BFOR-201%5D+Common+template+to+add+alternate+views+in+docs"></a>
+<a name="N10137"></a><a name="%5BFOR-201%5D+Common+template+to+add+alternate+views+in+docs"></a>
 <h2 class="underlined_10">[FOR-201] Common template to add alternate views in docs</h2>
 <div class="section">
 <p>
@@ -617,7 +562,7 @@
 </p>
 <p>The pdf, xml, etc links should be in the document itself for all skins, and be removed when printing. A common template would make all skins look consistent in this regard.</p>
 </div>
-<a name="N10153"></a><a name="%5BFOR-197%5D+Link+for+whole-site+docs"></a>
+<a name="N10145"></a><a name="%5BFOR-197%5D+Link+for+whole-site+docs"></a>
 <h2 class="underlined_10">[FOR-197] Link for whole-site docs</h2>
 <div class="section">
 <p>
@@ -627,13 +572,21 @@
 <br>
 We should add an icon on the skins to download the whole-site pdf after accessing a page that explains that it's the *whole* site, and not just the page.</p>
 </div>
-<a name="N10161"></a><a name="%5BFOR-187%5D+Redefine+project+documentation+dirs"></a>
+<a name="N10153"></a><a name="%5BFOR-187%5D+Redefine+project+documentation+dirs"></a>
 <h2 class="underlined_10">[FOR-187] Redefine project documentation dirs</h2>
 <div class="section">
 <p>
 <a class="external" href="http://issues.cocoondev.org//browse/FOR-187">http://issues.cocoondev.org//browse/FOR-187</a>
 </p>
 <p>We should finalize all discussions about where to put sources and extensions in the projects.</p>
+</div>
+<a name="N10161"></a><a name="%5BFOR-185%5D+Can%27t+get+svg+files+served+along+with+the+PNG"></a>
+<h2 class="underlined_10">[FOR-185] Can't get svg files served along with the PNG</h2>
+<div class="section">
+<p>
+<a class="external" href="http://issues.cocoondev.org//browse/FOR-185">http://issues.cocoondev.org//browse/FOR-185</a>
+</p>
+<p>The sitemap does not allow to get a file that is in xdocs as .svg, thus preventing users from adding a link to it from a page that contains the png version.</p>
 </div>
 </div>
 <!--+

Modified: forrest/site/forrest-issues.pdf
URL: http://svn.apache.org/viewcvs/forrest/site/forrest-issues.pdf?view=diff&r1=152644&r2=152645
==============================================================================
Binary files - no diff available.

Added: forrest/site/guidelines.html
URL: http://svn.apache.org/viewcvs/forrest/site/guidelines.html?view=auto&rev=152645
==============================================================================
--- forrest/site/guidelines.html (added)
+++ forrest/site/guidelines.html Mon Feb  7 22:36:36 2005
@@ -0,0 +1,799 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
+<meta content="Apache Forrest" name="Generator">
+<meta name="Forrest-version" content="0.7-dev">
+<meta name="Forrest-skin-name" content="pelt">
+<title>Apache Forrest project guidelines</title>
+<link type="text/css" href="skin/basic.css" rel="stylesheet">
+<link media="screen" type="text/css" href="skin/screen.css" rel="stylesheet">
+<link media="print" type="text/css" href="skin/print.css" rel="stylesheet">
+<link type="text/css" href="skin/profile.css" rel="stylesheet">
+<script src="skin/getBlank.js" language="javascript" type="text/javascript"></script><script src="skin/getMenu.js" language="javascript" type="text/javascript"></script><script src="skin/fontsize.js" language="javascript" type="text/javascript"></script>
+<link rel="shortcut icon" href="favicon.ico">
+</head>
+<body onload="init()">
+<script type="text/javascript">ndeSetTextSize();</script>
+<div id="top">
+<!--+
+    |breadtrail
+    +-->
+<div class="breadtrail">
+<a href="http://www.apache.org/">apache</a> &gt; <a href="http://forrest.apache.org/">forrest</a><script src="skin/breadcrumbs.js" language="JavaScript" type="text/javascript"></script>
+</div>
+<!--+
+    |header
+    +-->
+<div class="header">
+<!--+
+    |start group logo
+    +-->
+<div class="grouplogo">
+<a href="http://www.apache.org/"><img class="logoImage" alt="Apache" src="images/apache-forrest.png" title="The Apache Software Foundation"></a>
+</div>
+<!--+
+    |end group logo
+    +-->
+<!--+
+    |start Project Logo
+    +-->
+<div class="projectlogo">
+<a href="http://forrest.apache.org/"><img class="logoImage" alt="Forrest" src="images/project-logo.gif" title="Apache Forrest"></a>
+</div>
+<!--+
+    |end Project Logo
+    +-->
+<!--+
+    |start Search
+    +-->
+<div class="searchbox">
+<form action="http://www.google.com/search" method="get" class="roundtopsmall">
+<input value="forrest.apache.org" name="sitesearch" type="hidden"><input onFocus="getBlank (this, 'Search the site with google:');" value="Search the site with google:" size="25" name="q" id="query" type="text">&nbsp; 
+                    <input name="Search" value="Search" type="submit">
+</form>
+</div>
+<!--+
+    |end search
+    +-->
+<!--+
+    |start Tabs
+    +-->
+<ul id="tabs">
+<li>
+<a class="base-not-selected" href="index.html">Welcome</a>
+</li>
+<li class="current">
+<a class="base-selected" href="contrib.html">Project</a>
+</li>
+<li>
+<a class="base-not-selected" href="docs/index.html">Documentation</a>
+</li>
+<li>
+<a class="base-not-selected" href="howto/index.html">How-To</a>
+</li>
+</ul>
+<!--+
+    |end Tabs
+    +-->
+</div>
+</div>
+<div id="main">
+<div id="publishedStrip">
+<!--+
+    |start Subtabs
+    +-->
+<div id="level2tabs"></div>
+<!--+
+    |end Endtabs
+    +-->
+<script type="text/javascript" language="JavaScript"><!--
+              document.write("Published: " + document.lastModified);
+              //  --></script>
+</div>
+<!--+
+    |breadtrail
+    +-->
+<div class="breadtrail">
+             
+             &nbsp;
+           </div>
+<!--+
+    |start Menu, mainarea
+    +-->
+<!--+
+    |start Menu
+    +-->
+<div id="menu">
+<div onclick="SwitchMenu('menu_selected_1.1', 'skin/')" id="menu_selected_1.1Title" class="menutitle" style="background-image: url('skin/images/chapter_open.gif');">Getting Involved</div>
+<div id="menu_selected_1.1" class="selectedmenuitemgroup" style="display: block;">
+<div class="menuitem">
+<a title="" href="contrib.html">Contributing</a>
+</div>
+<div class="menuitem">
+<a title="" href="http://svn.apache.org/viewcvs.cgi/forrest/trunk/">Browse SVN</a>
+</div>
+<div class="menuitem">
+<a title="" href="mail-lists.html">Mail lists</a>
+</div>
+<div class="menuitem">
+<a title="" href="http://issues.cocoondev.org/secure/BrowseProject.jspa?id=10000">Bugs and Issues</a>
+</div>
+<div class="menuitem">
+<a title="" href="forrest-issues.html">Open Issues</a>
+</div>
+<div class="menuitem">
+<a title="" href="http://brutus.apache.org/gump/public/forrest/">Gump Integration</a>
+</div>
+<div class="menupage">
+<div class="menupagetitle">Project guidelines</div>
+</div>
+</div>
+<div onclick="SwitchMenu('menu_1.2', 'skin/')" id="menu_1.2Title" class="menutitle">Proposals</div>
+<div id="menu_1.2" class="menuitemgroup">
+<div class="menuitem">
+<a title="" href="proposal-asf-publish.html">ASF Publishing</a>
+</div>
+<div class="menuitem">
+<a title="" href="proposal-asf-forrestbot.html">ASF Forrestbot</a>
+</div>
+</div>
+<div id="credit"></div>
+<div id="roundbottom">
+<img style="display: none" class="corner" height="15" width="15" alt="" src="skin/images/rc-b-l-15-1body-2menu-3menu.png"></div>
+<!--+
+  |alternative credits
+  +-->
+</div>
+<!--+
+    |end Menu
+    +-->
+<!--+
+    |start content
+    +-->
+<div id="content">
+<div title="Portable Document Format" class="pdflink">
+<a class="dida" href="guidelines.pdf"><img alt="PDF -icon" src="skin/images/pdfdoc.gif" class="skin"><br>
+        PDF</a>
+</div>
+<div class="trail">
+	        Font size: 
+	          &nbsp;<input value="Reset" class="resetfont" title="Reset text" onclick="ndeSetTextSize('reset'); return false;" type="button">      
+	          &nbsp;<input value="-a" class="smallerfont" title="Shrink text" onclick="ndeSetTextSize('decr'); return false;" type="button">
+	          &nbsp;<input value="+a" class="biggerfont" title="Enlarge text" onclick="ndeSetTextSize('incr'); return false;" type="button">
+</div>
+<h1>Apache Forrest project guidelines</h1>
+<div id="minitoc-area">
+<ul class="minitoc">
+<li>
+<a href="#mission">The mission of Apache Forrest</a>
+</li>
+<li>
+<a href="#way">The Apache Way</a>
+</li>
+<li>
+<a href="#roles">Roles and responsibilities</a>
+</li>
+<li>
+<a href="#pmc">Project Management Committee (PMC)</a>
+</li>
+<li>
+<a href="#decision">Decision making</a>
+<ul class="minitoc">
+<li>
+<a href="#voting">Voting</a>
+</li>
+<li>
+<a href="#approvals">Types of approval</a>
+</li>
+<li>
+<a href="#veto">Vetoes</a>
+</li>
+<li>
+<a href="#actions">Actions</a>
+</li>
+<li>
+<a href="#timeframe">Voting timeframes</a>
+</li>
+<li>
+<a href="#procedure">Voting procedure</a>
+</li>
+<li>
+<a href="#ultimatum">Ultimatum and breakdown</a>
+</li>
+</ul>
+</li>
+<li>
+<a href="#code">Code management</a>
+</li>
+</ul>
+</div> 
+  
+<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
+   (<a href="http://www.apache.org/foundation/">ASF</a>) which holds
+   the copyright for all Apache projects. 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>
+
+  
+<a name="N10014"></a><a name="mission"></a>
+<h2 class="underlined_10">The mission of Apache Forrest</h2>
+<div class="section">
+<p>
+      The generation of aggregated multi-channel documentation,
+      maintaining a separation of content and presentation.
+    </p>
+</div>
+
+  
+<a name="N1001E"></a><a name="way"></a>
+<h2 class="underlined_10">The Apache Way</h2>
+<div class="section">
+<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
+      <a href="http://www.apache.org/foundation/">ASF foundation</a>
+      and
+      <a href="http://www.apache.org/dev/">ASF developer</a> sections
+      of the ASF website, including the
+      <a href="http://www.apache.org/foundation/bylaws.html">ASF ByLaws</a>
+      and the
+      <a href="http://www.apache.org/foundation/how-it-works.html">How it works</a> document,
+      as well as the
+      <a class="external" href="http://incubator.apache.org/">Incubator project</a>.
+    </p>
+</div>
+
+  
+<a name="N1003C"></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
+      <a href="http://www.apache.org/foundation/how-it-works.html">How it works</a> document.
+    </p>
+<p>
+    
+<a href="http://www.apache.org/foundation/how-it-works.html#users">user</a> -&gt;
+    <a href="http://www.apache.org/foundation/how-it-works.html#developers">developer</a> -&gt;
+    <a href="http://www.apache.org/foundation/how-it-works.html#committers">committer</a> -&gt;
+    <a href="http://www.apache.org/foundation/how-it-works.html#pmc-members">PMC member</a> -&gt;
+    <a href="http://www.apache.org/foundation/how-it-works.html#asf-members">ASF member</a>
+    
+</p>
+<p>The current Apache Forrest committers and PMC members are
+      <a href="who.html">listed</a>.
+    </p>
+</div>
+
+  
+<a name="N10068"></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
+      top-level project in May 2004.
+      The Project Management Committee (PMC) was created by a
+      <a href="http://www.apache.org/foundation/records/minutes/2004/board_minutes_2004_05_26.txt">resolution</a>
+      of the board of the Apache Software Foundation.
+      See explanation of the role of the PMC in that resolution and also the
+      <a href="http://www.apache.org/foundation/bylaws.html">ASF Bylaws</a>
+      and 
+    <a href="http://www.apache.org/foundation/how-it-works.html#pmc">How-it-works</a>.
+    </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 quarterly on developments within 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
+      <a href="http://www.apache.org/foundation/bylaws.html">ASF Bylaws</a>
+      and the
+      <a href="http://www.apache.org/dev/pmc.html#chair">PMC FAQ</a>
+    
+</p>
+</div>
+
+  
+<a name="N100B6"></a><a name="decision"></a>
+<h2 class="underlined_10">Decision making</h2>
+<div class="section">
+<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>
+<a name="N100C2"></a><a name="voting"></a>
+<h3 class="underlined_5">Voting</h3>
+<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 <a href="#procedure">voting procedure</a> below.
+        Votes are expressed using one of the following symbols:
+      </p>
+<table class="ForrestTable" cellspacing="1" cellpadding="4">
+        
+<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 <a href="#veto">veto</a>.
+            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>
+<a name="N10126"></a><a name="approvals"></a>
+<h3 class="underlined_5">Types of approval</h3>
+<p>
+        Different actions require different types of approval:
+      </p>
+<table class="ForrestTable" cellspacing="1" cellpadding="4">
+        
+<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 that -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>
+<a name="N10179"></a><a name="veto"></a>
+<h3 class="underlined_5">Vetoes</h3>
+<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>
+<a name="N1018C"></a><a name="actions"></a>
+<h3 class="underlined_5">Actions</h3>
+<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 class="ForrestTable" cellspacing="1" cellpadding="4">
+        
+<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>
+<a name="N10288"></a><a name="timeframe"></a>
+<h3 class="underlined_5">Voting timeframes</h3>
+<p>
+        Votes are 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>
+<a name="N10292"></a><a name="procedure"></a>
+<h3 class="underlined_5">Voting procedure</h3>
+<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.
+      </p>
+<p>
+        Votes are expressed by replying email using the
+        <a href="#voting">voting symbols</a> 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>
+<a name="N102A6"></a><a name="ultimatum"></a>
+<h3 class="underlined_5">Ultimatum and breakdown</h3>
+<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>
+</div>
+
+  
+<a name="N102B1"></a><a name="code"></a>
+<h2 class="underlined_10">Code management</h2>
+<div class="section">
+<p>
+    
+<a href="http://www.apache.org/foundation/glossary.html#CommitThenReview">Commit-then-review</a>.
+    </p>
+</div>
+
+<!-- FIXME:
+
+==================
+> 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?
+
+==================
+
+-->
+
+</div>
+<!--+
+    |end content
+    +-->
+<div class="clearboth">&nbsp;</div>
+</div>
+<div id="footer">
+<!--+
+    |start bottomstrip
+    +-->
+<div class="lastmodified">
+<script type="text/javascript"><!--
+document.write("Last Published: " + document.lastModified);
+//  --></script>
+</div>
+<div class="copyright">
+ Copyright &copy; 2002-2004 The Apache Software Foundation.</div>
+<!--+
+    |end bottomstrip
+    +-->
+</div>
+</body>
+</html>

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

Added: forrest/site/guidelines.pdf
URL: http://svn.apache.org/viewcvs/forrest/site/guidelines.pdf?view=auto&rev=152645
==============================================================================
Binary file - no diff available.

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

Propchange: forrest/site/guidelines.pdf
------------------------------------------------------------------------------
    svn:mime-type = application/pdf

Modified: forrest/site/index.html
URL: http://svn.apache.org/viewcvs/forrest/site/index.html?view=diff&r1=152644&r2=152645
==============================================================================
--- forrest/site/index.html (original)
+++ forrest/site/index.html Mon Feb  7 22:36:36 2005
@@ -391,15 +391,13 @@
         backwards-incompatible changes.
       </p>
 <p>
-        The documentation on the Apache Forrest website relates to the current
-        release. The documentation for the
-        <a href="docs/dev/">development</a>
-        version is also available.
-        Whatever version
-        of Forrest that you are using, will provide the local documentation for
-        that specific version.
-        Do '<a href="http://forrest.apache.org/docs/build.html#run">forrest run</a>'
-        to view it.
+        Documentation on the Apache Forrest website exists for the
+        <a href="docs/">latest release</a> and for the
+        <a href="docs/dev/">current development</a>
+        version from the source
+        repository. All versions of Forrest include their own copy of the documentation.
+        To view it, do '<a href="http://forrest.apache.org/docs/build.html#run">forrest run</a>' and go to
+        http://127.0.0.1:8888/  (for versions after 0.6, do 'cd docs-author' first).
         The <a href="http://forrest.apache.org/">Apache Forrest website</a> is updated
         manually as needed, while we develop the 
         <a class="external" href="site:forrestbot">forrestbot</a> deployment facility.
@@ -411,7 +409,7 @@
       </p>
 </div>
     
-<a name="N1010A"></a><a name="news"></a>
+<a name="N1010E"></a><a name="news"></a>
 <h2 class="underlined_10">News and events</h2>
 <div class="section">
 <ul>
@@ -430,7 +428,7 @@
 </ul>
 </div>
     
-<a name="N1011A"></a><a name="help"></a>
+<a name="N1011E"></a><a name="help"></a>
 <h2 class="underlined_10">Help Wanted!</h2>
 <div class="section">
 <p>

Modified: forrest/site/index.pdf
URL: http://svn.apache.org/viewcvs/forrest/site/index.pdf?view=diff&r1=152644&r2=152645
==============================================================================
Binary files - no diff available.

Modified: forrest/site/linkmap.html
URL: http://svn.apache.org/viewcvs/forrest/site/linkmap.html?view=diff&r1=152644&r2=152645
==============================================================================
--- forrest/site/linkmap.html (original)
+++ forrest/site/linkmap.html Mon Feb  7 22:36:36 2005
@@ -155,6 +155,9 @@
 <div class="menuitem">
 <a title="" href="http://brutus.apache.org/gump/public/forrest/">Gump Integration</a>
 </div>
+<div class="menuitem">
+<a title="" href="guidelines.html">Project guidelines</a>
+</div>
 </div>
 <div onclick="SwitchMenu('menu_1.4', 'skin/')" id="menu_1.4Title" class="menutitle">Proposals</div>
 <div id="menu_1.4" class="menuitemgroup">
@@ -311,9 +314,10 @@
 <li>
 <a class="external" href="http://brutus.apache.org/gump/public/forrest/">Gump Integration</a>&nbsp;&nbsp;&nbsp;_________________________&nbsp;&nbsp;<em>gump-forrest</em>
 </li>
-
-
-
+    
+<li>
+<a href="guidelines.html">Project guidelines</a>&nbsp;&nbsp;&nbsp;_________________________&nbsp;&nbsp;<em>guidelines</em>
+</li>
   
 </ul>
 

Modified: forrest/site/linkmap.pdf
URL: http://svn.apache.org/viewcvs/forrest/site/linkmap.pdf?view=diff&r1=152644&r2=152645
==============================================================================
Binary files - no diff available.

Modified: forrest/site/mail-lists.html
URL: http://svn.apache.org/viewcvs/forrest/site/mail-lists.html?view=diff&r1=152644&r2=152645
==============================================================================
--- forrest/site/mail-lists.html (original)
+++ forrest/site/mail-lists.html Mon Feb  7 22:36:36 2005
@@ -125,6 +125,9 @@
 <div class="menuitem">
 <a title="" href="http://brutus.apache.org/gump/public/forrest/">Gump Integration</a>
 </div>
+<div class="menuitem">
+<a title="" href="guidelines.html">Project guidelines</a>
+</div>
 </div>
 <div onclick="SwitchMenu('menu_1.2', 'skin/')" id="menu_1.2Title" class="menutitle">Proposals</div>
 <div id="menu_1.2" class="menuitemgroup">

Modified: forrest/site/proposal-asf-forrestbot.html
URL: http://svn.apache.org/viewcvs/forrest/site/proposal-asf-forrestbot.html?view=diff&r1=152644&r2=152645
==============================================================================
--- forrest/site/proposal-asf-forrestbot.html (original)
+++ forrest/site/proposal-asf-forrestbot.html Mon Feb  7 22:36:36 2005
@@ -125,6 +125,9 @@
 <div class="menuitem">
 <a title="" href="http://brutus.apache.org/gump/public/forrest/">Gump Integration</a>
 </div>
+<div class="menuitem">
+<a title="" href="guidelines.html">Project guidelines</a>
+</div>
 </div>
 <div onclick="SwitchMenu('menu_selected_1.2', 'skin/')" id="menu_selected_1.2Title" class="menutitle" style="background-image: url('skin/images/chapter_open.gif');">Proposals</div>
 <div id="menu_selected_1.2" class="selectedmenuitemgroup" style="display: block;">

Modified: forrest/site/proposal-asf-publish.html
URL: http://svn.apache.org/viewcvs/forrest/site/proposal-asf-publish.html?view=diff&r1=152644&r2=152645
==============================================================================
--- forrest/site/proposal-asf-publish.html (original)
+++ forrest/site/proposal-asf-publish.html Mon Feb  7 22:36:36 2005
@@ -125,6 +125,9 @@
 <div class="menuitem">
 <a title="" href="http://brutus.apache.org/gump/public/forrest/">Gump Integration</a>
 </div>
+<div class="menuitem">
+<a title="" href="guidelines.html">Project guidelines</a>
+</div>
 </div>
 <div onclick="SwitchMenu('menu_selected_1.2', 'skin/')" id="menu_selected_1.2Title" class="menutitle" style="background-image: url('skin/images/chapter_open.gif');">Proposals</div>
 <div id="menu_selected_1.2" class="selectedmenuitemgroup" style="display: block;">



Mime
View raw message