forrest-svn mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cross...@apache.org
Subject svn commit: r406639 [2/2] - in /forrest/site: ./ docs_0_60/ docs_0_70/ docs_0_80/
Date Mon, 15 May 2006 14:38:42 GMT
Modified: forrest/site/forrest-issues.html
URL: http://svn.apache.org/viewcvs/forrest/site/forrest-issues.html?rev=406639&r1=406638&r2=406639&view=diff
==============================================================================
--- forrest/site/forrest-issues.html (original)
+++ forrest/site/forrest-issues.html Mon May 15 07:38:38 2006
@@ -189,60 +189,45 @@
 <div id="minitoc-area">
 <ul class="minitoc">
 <li>
-<a href="#%5BFOR-713%5D+HTML-to-document.xsl+no+longer+generates+an+XDoc">[FOR-713] HTML-to-document.xsl no longer generates an XDoc</a>
-</li>
-<li>
-<a href="#%5BFOR-762%5D+Default+page+URL+for+breadcrumbs+and+site%3A+links">[FOR-762] Default page URL for breadcrumbs and site: links</a>
+<a href="#%5BFOR-591%5D+MaxMemory+needs+increasing+for+large+document+sets%3A+Memory+Leak+with+XMLFileModule">[FOR-591] MaxMemory needs increasing for large document sets: Memory Leak with XMLFileModule</a>
 </li>
 <li>
-<a href="#%5BFOR-796%5D+Merge+all+view%2Fdispatcher+work+into+org.apache.forrest.plugin.internal.dispatcher+and+org.apache.forrest.themes.core">[FOR-796] Merge all view/dispatcher work into org.apache.forrest.plugin.internal.dispatcher and org.apache.forrest.themes.core</a>
+<a href="#%5BFOR-713%5D+HTML-to-document.xsl+no+longer+generates+an+XDoc">[FOR-713] HTML-to-document.xsl no longer generates an XDoc</a>
 </li>
 <li>
-<a href="#%5BFOR-492%5D+Inconsistent+Line+Endings+in+generated+sites">[FOR-492] Inconsistent Line Endings in generated sites</a>
+<a href="#%5BFOR-855%5D+verify+the+license+situation+prior+to+each+release">[FOR-855] verify the license situation prior to each release</a>
 </li>
 <li>
 <a href="#%5BFOR-865%5D+Add+missing+entries+to+status.xml+to+generate+the+changes+list">[FOR-865] Add missing entries to status.xml to generate the changes list</a>
 </li>
 <li>
-<a href="#%5BFOR-867%5D+need+doc+to+explain+status+of+skins+and+dispatcher">[FOR-867] need doc to explain status of skins and dispatcher</a>
-</li>
-<li>
 <a href="#%5BFOR-868%5D+add+relevant+notes+to+the+%22Upgrading%22+xdoc">[FOR-868] add relevant notes to the "Upgrading" xdoc</a>
 </li>
 <li>
-<a href="#%5BFOR-855%5D+verify+the+license+situation+prior+to+each+release">[FOR-855] verify the license situation prior to each release</a>
+<a href="#%5BFOR-867%5D+need+doc+to+explain+status+of+skins+and+dispatcher">[FOR-867] need doc to explain status of skins and dispatcher</a>
 </li>
 <li>
-<a href="#%5BFOR-681%5D+Include+xconf+files+in+plugins+using+includes%2C+not+XPatch">[FOR-681] Include xconf files in plugins using includes, not XPatch</a>
+<a href="#%5BFOR-572%5D+run+a+memory+profiler+while+forrest+is+operating">[FOR-572] run a memory profiler while forrest is operating</a>
 </li>
 <li>
-<a href="#%5BFOR-591%5D+MaxMemory+needs+increasing">[FOR-591] MaxMemory needs increasing</a>
+<a href="#%5BFOR-388%5D+Use+plugins+in-place+if+src+available">[FOR-388] Use plugins in-place if src available</a>
 </li>
 <li>
 <a href="#%5BFOR-533%5D+Auto+Generate+plugins.xml+entry">[FOR-533] Auto Generate plugins.xml entry</a>
 </li>
 <li>
-<a href="#%5BFOR-735%5D+Plugins+are+not+correctly+deployed+in+webapp+mode">[FOR-735] Plugins are not correctly deployed in webapp mode</a>
-</li>
-<li>
-<a href="#%5BFOR-711%5D+Cache+results+from+the+Locationmap">[FOR-711] Cache results from the Locationmap</a>
+<a href="#%5BFOR-639%5D+define+terminology+for+the+various+aspects+of+Dispatcher">[FOR-639] define terminology for the various aspects of Dispatcher</a>
 </li>
 <li>
-<a href="#%5BFOR-707%5D+Document+i18n+features+of+Forrest">[FOR-707] Document i18n features of Forrest</a>
+<a href="#%5BFOR-735%5D+Plugins+are+not+correctly+deployed+in+webapp+mode">[FOR-735] Plugins are not correctly deployed in webapp mode</a>
 </li>
 <li>
-<a href="#%5BFOR-388%5D+Use+plugins+in-place+if+src+available">[FOR-388] Use plugins in-place if src available</a>
+<a href="#%5BFOR-711%5D+Cache+results+from+the+Locationmap">[FOR-711] Cache results from the Locationmap</a>
 </li>
 <li>
 <a href="#%5BFOR-742%5D+trouble+accessing+unversioned+plugin+for+a+released+version+of+Forrest%2C+e.g.+projectInfo">[FOR-742] trouble accessing unversioned plugin for a released version of Forrest, e.g. projectInfo</a>
 </li>
 <li>
-<a href="#%5BFOR-639%5D+define+terminology+for+the+various+aspects+of+Dispatcher">[FOR-639] define terminology for the various aspects of Dispatcher</a>
-</li>
-<li>
-<a href="#%5BFOR-572%5D+run+a+memory+profiler+while+forrest+is+operating">[FOR-572] run a memory profiler while forrest is operating</a>
-</li>
-<li>
 <a href="#%5BFOR-876%5D+locationmap+demo+in+fresh-site+is+broken">[FOR-876] locationmap demo in fresh-site is broken</a>
 </li>
 <li>
@@ -255,6 +240,9 @@
 <a href="#%5BFOR-209%5D+First+level+selected+tab+is+not+highlighted+when+containing+2nd+level+tabs">[FOR-209] First level selected tab is not highlighted when containing 2nd level tabs</a>
 </li>
 <li>
+<a href="#%5BFOR-211%5D+whole-site+html+and+pdf%3A+broken+ext+links">[FOR-211] whole-site html and pdf: broken ext links</a>
+</li>
+<li>
 <a href="#%5BFOR-203%5D+2nd+level+tabs+are+not+selected+appropriately">[FOR-203] 2nd level tabs are not selected appropriately</a>
 </li>
 <li>
@@ -263,6 +251,18 @@
 <li>
 <a href="#%5BFOR-546%5D+Sitemap+reference+doc+should+be+updated+to+reflect+plugin+architecture">[FOR-546] Sitemap reference doc should be updated to reflect plugin architecture</a>
 </li>
+<li>
+<a href="#%5BFOR-560%5D+Remove+duplicate+jars+from+eclipse+plugins">[FOR-560] Remove duplicate jars from eclipse plugins</a>
+</li>
+<li>
+<a href="#%5BFOR-644%5D+code-style+cleanup+for+xml+files">[FOR-644] code-style cleanup for xml files</a>
+</li>
+<li>
+<a href="#%5BFOR-666%5D+clarify+the+sitemap+matches+etc.+in+FAQ+about+non-skinned+html">[FOR-666] clarify the sitemap matches etc. in FAQ about non-skinned html</a>
+</li>
+<li>
+<a href="#%5BFOR-726%5D+use+locationmap+in+all+of+the+plugins">[FOR-726] use locationmap in all of the plugins</a>
+</li>
 </ul>
 </div>
 <div class="note">
@@ -273,101 +273,65 @@
        <a href="http://issues.apache.org/jira/secure/IssueNavigator.jspa?pid=12310000&resolutionIds=-1&tempMax=1000&reset=true">all</a> open issues).
       The listing below is regenerated on each Forrest run.</div>
 </div>
-<a name="N10011"></a><a name="%5BFOR-713%5D+HTML-to-document.xsl+no+longer+generates+an+XDoc"></a>
-<h2 class="underlined_10">[FOR-713] HTML-to-document.xsl no longer generates an XDoc</h2>
+<a name="N10011"></a><a name="%5BFOR-591%5D+MaxMemory+needs+increasing+for+large+document+sets%3A+Memory+Leak+with+XMLFileModule"></a>
+<h2 class="underlined_10">[FOR-591] MaxMemory needs increasing for large document sets: Memory Leak with XMLFileModule</h2>
 <div class="section">
 <p>
-<a href="http://issues.apache.org/jira/browse/FOR-713">http://issues.apache.org/jira/browse/FOR-713</a>
+<a href="http://issues.apache.org/jira/browse/FOR-591">http://issues.apache.org/jira/browse/FOR-591</a>
 </p>
-<p>html-to-document.xsl no longer converts content to an XDoc. Instead it renders converts documents to XDoc, instead it allows H1, H2 etc. elements to pass through.
+<p>Since the docs restructuring for the 0.7 release it has become necessary to increase the maxmemory to be able to build the Forrest site. We gained three copies of the documents so suddenly have a large document set to trigger memory leakage issues.
 &lt;br/&gt;
 
 &lt;br/&gt;
-The result is a page that seems to render correctly and in the single test case I have used it still renders correctly in PDF and Text format. However, this is a backward incompatible change that will break sites that use includes with XPath statements such as /section[@id=&amp;quot;foo&amp;quot;] (sections are no longer created)
+Possibly &lt;a href="http://issues.apache.org/jira/browse/COCOON-1574" title="Memory Leak with XMLFileModule"&gt;COCOON-1574&lt;/a&gt; &amp;quot;Memory Leak with XMLFileModule&amp;quot;.
 &lt;br/&gt;
 
 &lt;br/&gt;
-</p>
+Does someone have the tools to run some diagnostics?
+&lt;br/&gt;
+
+&lt;br/&gt;
+(NB maxmemory has been increased in our site-author/forrest.properties, if we resolve this issue it should be reduced again)</p>
 </div>
-<a name="N1001D"></a><a name="%5BFOR-762%5D+Default+page+URL+for+breadcrumbs+and+site%3A+links"></a>
-<h2 class="underlined_10">[FOR-762] Default page URL for breadcrumbs and site: links</h2>
+<a name="N1001D"></a><a name="%5BFOR-713%5D+HTML-to-document.xsl+no+longer+generates+an+XDoc"></a>
+<h2 class="underlined_10">[FOR-713] HTML-to-document.xsl no longer generates an XDoc</h2>
 <div class="section">
 <p>
-<a href="http://issues.apache.org/jira/browse/FOR-762">http://issues.apache.org/jira/browse/FOR-762</a>
+<a href="http://issues.apache.org/jira/browse/FOR-713">http://issues.apache.org/jira/browse/FOR-713</a>
 </p>
-<p>When employing breadcrumbs,
-&lt;br/&gt;
-
-&lt;br/&gt;
-example generated links:  home &amp;gt; dir &amp;gt; subdir
+<p>html-to-document.xsl no longer converts content to an XDoc. Instead it renders converts documents to XDoc, instead it allows H1, H2 etc. elements to pass through.
 &lt;br/&gt;
 
 &lt;br/&gt;
-if the user is in node subdir, then clicks dir,
-&lt;br/&gt;
-cocoon returns &amp;quot;The requested resource &amp;quot;/dir /&amp;quot; could not be found.
-&lt;br/&gt;
-The link's absolute path during testing is &lt;a href="http://localhost:8888/dir/"&gt;http://localhost:8888/dir/&lt;/a&gt;
-&lt;br/&gt;
-Case 1. If you place an index.html file under &lt;a href="http://localhost:8888/dir/"&gt;http://localhost:8888/dir/&lt;/a&gt; for a redirect or viewable content,
-&lt;br/&gt;
-clicking on breadcrumbs'  dir link throws the error.
-&lt;br/&gt;
-Case 2. If you manually enter the index.html in the browser path after &lt;a href="http://localhost:8888/dir/,"&gt;http://localhost:8888/dir/,&lt;/a&gt; the request is handled.
-&lt;br/&gt;
-Case 3. If sitemap has match=&amp;quot;dir/index.html&amp;quot;, cocoon still isn't happy with request dir/
+The result is a page that seems to render correctly and in the single test case I have used it still renders correctly in PDF and Text format. However, this is a backward incompatible change that will break sites that use includes with XPath statements such as /section[@id=&amp;quot;foo&amp;quot;] (sections are no longer created)
 &lt;br/&gt;
 
 &lt;br/&gt;
-Cocoon does not appear to assume the end node directory is index.* and thus appends no file automatically as tomcat or the http server does so it must be manually done. </p>
-</div>
-<a name="N10029"></a><a name="%5BFOR-796%5D+Merge+all+view%2Fdispatcher+work+into+org.apache.forrest.plugin.internal.dispatcher+and+org.apache.forrest.themes.core"></a>
-<h2 class="underlined_10">[FOR-796] Merge all view/dispatcher work into org.apache.forrest.plugin.internal.dispatcher and org.apache.forrest.themes.core</h2>
-<div class="section">
-<p>
-<a href="http://issues.apache.org/jira/browse/FOR-796">http://issues.apache.org/jira/browse/FOR-796</a>
 </p>
-<p>This is the global issue to keep track on the merging effort</p>
 </div>
-<a name="N10035"></a><a name="%5BFOR-492%5D+Inconsistent+Line+Endings+in+generated+sites"></a>
-<h2 class="underlined_10">[FOR-492] Inconsistent Line Endings in generated sites</h2>
+<a name="N10029"></a><a name="%5BFOR-855%5D+verify+the+license+situation+prior+to+each+release"></a>
+<h2 class="underlined_10">[FOR-855] verify the license situation prior to each release</h2>
 <div class="section">
 <p>
-<a href="http://issues.apache.org/jira/browse/FOR-492">http://issues.apache.org/jira/browse/FOR-492</a>
+<a href="http://issues.apache.org/jira/browse/FOR-855">http://issues.apache.org/jira/browse/FOR-855</a>
 </p>
-<p>Sites generated by Forrest have inconsistent line endings when created on a Windows platform. 
+<p>This should be continually happening anyway, but immediately prior to each release we need to verify that our license situation is in order. This issue should not ever be closed, rather just move the &amp;quot;Fix for Version&amp;quot; on to the next release.
 &lt;br/&gt;
 
 &lt;br/&gt;
-I did a little testing, here's what I have discovered so far:
-&lt;br/&gt;
-&amp;nbsp;
-&lt;br/&gt;
-- any file that is processed by XSLT has the line endings problem
-&lt;br/&gt;
-- on investigating one such file (index.html) I discovered that the  generated comments from site2xhtml.xsl (such as breadtrail comment) have LF endings whilst most other lines have CRLF endings.
-&lt;br/&gt;
-&amp;nbsp;
-&lt;br/&gt;
-I'm running on Windows, and get the same results whether I run under 
-&lt;br/&gt;
-CYGWIN or DOS.
-&lt;br/&gt;
-&amp;nbsp;
-&lt;br/&gt;
-To reproduce run &amp;quot;forrest site&amp;quot; in any site and check out the generated docs in build/site.
+Here are some of the tasks:
 &lt;br/&gt;
 
 &lt;br/&gt;
-This appears to a result of the XSLT transformations. xsl:comments retain the line endings contained in the XSL file, whilst other line endings are set to the environment default.
+A) Ensure that all supporting libraries have a corresponding license. Basically every jar file or other external package needs to have a *.license.txt file. Ensure that any license conditions are met, e.g. for some we must add an entry to NOTICE.txt, while for some others we must not. Remember to abide by the ASF guidelines (e.g. nothing more restrictive than the Apache License).
 &lt;br/&gt;
 
 &lt;br/&gt;
-Is there a way to tell the XSLT transformer what line endings to use?
+B) Scan the whole trunk repository to add missing ASF license headers to source files and to ensure that the ASF license headers have not been accidently added to external files. See etc/relicense.txt
 &lt;br/&gt;
 </p>
 </div>
-<a name="N10041"></a><a name="%5BFOR-865%5D+Add+missing+entries+to+status.xml+to+generate+the+changes+list"></a>
+<a name="N10035"></a><a name="%5BFOR-865%5D+Add+missing+entries+to+status.xml+to+generate+the+changes+list"></a>
 <h2 class="underlined_10">[FOR-865] Add missing entries to status.xml to generate the changes list</h2>
 <div class="section">
 <p>
@@ -385,6 +349,14 @@
 &lt;br/&gt;
 &lt;a href="http://marc.theaimsgroup.com/?t=114274836600001"&gt;http://marc.theaimsgroup.com/?t=114274836600001&lt;/a&gt;</p>
 </div>
+<a name="N10041"></a><a name="%5BFOR-868%5D+add+relevant+notes+to+the+%22Upgrading%22+xdoc"></a>
+<h2 class="underlined_10">[FOR-868] add relevant notes to the "Upgrading" xdoc</h2>
+<div class="section">
+<p>
+<a href="http://issues.apache.org/jira/browse/FOR-868">http://issues.apache.org/jira/browse/FOR-868</a>
+</p>
+<p>We need to add some notes to the upgrading_0*.html doc for the upcoming release. This would most easily be done after attending to &lt;a href="http://issues.apache.org/jira/browse/FOR-865" title="Add missing entries to status.xml to generate the changes list"&gt;FOR-865&lt;/a&gt; &amp;quot;Add missing entries to status.xml to generate the changes list&amp;quot;.</p>
+</div>
 <a name="N1004D"></a><a name="%5BFOR-867%5D+need+doc+to+explain+status+of+skins+and+dispatcher"></a>
 <h2 class="underlined_10">[FOR-867] need doc to explain status of skins and dispatcher</h2>
 <div class="section">
@@ -397,171 +369,59 @@
 &lt;br/&gt;
 I have already commenced this xdoc.</p>
 </div>
-<a name="N10059"></a><a name="%5BFOR-868%5D+add+relevant+notes+to+the+%22Upgrading%22+xdoc"></a>
-<h2 class="underlined_10">[FOR-868] add relevant notes to the "Upgrading" xdoc</h2>
+<a name="N10059"></a><a name="%5BFOR-572%5D+run+a+memory+profiler+while+forrest+is+operating"></a>
+<h2 class="underlined_10">[FOR-572] run a memory profiler while forrest is operating</h2>
 <div class="section">
 <p>
-<a href="http://issues.apache.org/jira/browse/FOR-868">http://issues.apache.org/jira/browse/FOR-868</a>
+<a href="http://issues.apache.org/jira/browse/FOR-572">http://issues.apache.org/jira/browse/FOR-572</a>
 </p>
-<p>We need to add some notes to the upgrading_0*.html doc for the upcoming release. This would most easily be done after attending to &lt;a href="http://issues.apache.org/jira/browse/FOR-865" title="Add missing entries to status.xml to generate the changes list"&gt;FOR-865&lt;/a&gt; &amp;quot;Add missing entries to status.xml to generate the changes list&amp;quot;.</p>
+<p>We need to run a memory profiler while forrest is operating.</p>
 </div>
-<a name="N10065"></a><a name="%5BFOR-855%5D+verify+the+license+situation+prior+to+each+release"></a>
-<h2 class="underlined_10">[FOR-855] verify the license situation prior to each release</h2>
+<a name="N10065"></a><a name="%5BFOR-388%5D+Use+plugins+in-place+if+src+available"></a>
+<h2 class="underlined_10">[FOR-388] Use plugins in-place if src available</h2>
 <div class="section">
 <p>
-<a href="http://issues.apache.org/jira/browse/FOR-855">http://issues.apache.org/jira/browse/FOR-855</a>
+<a href="http://issues.apache.org/jira/browse/FOR-388">http://issues.apache.org/jira/browse/FOR-388</a>
 </p>
-<p>This should be continually happening anyway, but immediately prior to each release we need to verify that our license situation is in order. This issue should not ever be closed, rather just move the &amp;quot;Fix for Version&amp;quot; on to the next release.
-&lt;br/&gt;
-
-&lt;br/&gt;
-Here are some of the tasks:
+<p>At present Forrest will attempt to download plugins even if they are available in src form in the local filesystem as part of an SVN checkout.
 &lt;br/&gt;
 
 &lt;br/&gt;
-A) Ensure that all supporting libraries have a corresponding license. Basically every jar file or other external package needs to have a *.license.txt file. Ensure that any license conditions are met, e.g. for some we must add an entry to NOTICE.txt, while for some others we must not. Remember to abide by the ASF guidelines (e.g. nothing more restrictive than the Apache License).
+Have Forrest mount plugins from designated directories in preference to downloading them wherever possible (need more than posible location for src plugins as some people may be developing their own plugins outside of Forrest)
 &lt;br/&gt;
 
 &lt;br/&gt;
-B) Scan the whole trunk repository to add missing ASF license headers to source files and to ensure that the ASF license headers have not been accidently added to external files. See etc/relicense.txt
-&lt;br/&gt;
 </p>
 </div>
-<a name="N10071"></a><a name="%5BFOR-681%5D+Include+xconf+files+in+plugins+using+includes%2C+not+XPatch"></a>
-<h2 class="underlined_10">[FOR-681] Include xconf files in plugins using includes, not XPatch</h2>
+<a name="N10071"></a><a name="%5BFOR-533%5D+Auto+Generate+plugins.xml+entry"></a>
+<h2 class="underlined_10">[FOR-533] Auto Generate plugins.xml entry</h2>
 <div class="section">
 <p>
-<a href="http://issues.apache.org/jira/browse/FOR-681">http://issues.apache.org/jira/browse/FOR-681</a>
+<a href="http://issues.apache.org/jira/browse/FOR-533">http://issues.apache.org/jira/browse/FOR-533</a>
 </p>
-<p>See &lt;a href="http://marc.theaimsgroup.com/?l=forrest-dev&amp;m=112781600212715&amp;w=2"&gt;http://marc.theaimsgroup.com/?l=forrest-dev&amp;amp;m=112781600212715&amp;amp;w=2&lt;/a&gt;
-&lt;br/&gt;
-
-&lt;br/&gt;
-&amp;gt; I was excited to see the addition of xconf capability into plugins. See
-&lt;br/&gt;
-&amp;gt; &lt;a href="http://svn.apache.org/viewcvs?rev=227190&amp;view=rev"&gt;http://svn.apache.org/viewcvs?rev=227190&amp;amp;view=rev&lt;/a&gt;.
-&lt;br/&gt;
-&amp;gt; 
-&lt;br/&gt;
-&amp;gt; I rebuild cocoon with authentication and session blocks, and added the jars
-&lt;br/&gt;
-&amp;gt; to 'plugin/lib' and the xconf files from the
-&lt;br/&gt;
-&amp;gt; 'cocoon-2.2.0-dev\build\webapp\WEB-INF\xconf' to 'plugin/conf'.
-&lt;br/&gt;
-
-&lt;br/&gt;
-...
-&lt;br/&gt;
-
-&lt;br/&gt;
-&amp;gt; So am bit confused, on two counts:
-&lt;br/&gt;
-&amp;gt; 1. if xpatch is required, how do I generate this file?
-&lt;br/&gt;
-&amp;gt; 2. why are we using xpatch, when the current cocoon.xconf uses includes,
-&lt;br/&gt;
-&amp;gt; can't we do the same here?
-&lt;br/&gt;
-
-&lt;br/&gt;
-This was a rather hasty commit of mine that I have not yet fixed, even 
-&lt;br/&gt;
-though David spotted it as soon as I committed. Sorry that it has stung you.
-&lt;br/&gt;
-
-&lt;br/&gt;
-My original solution for including config files for plugins was to use 
-&lt;br/&gt;
-the XPatch utility. This sat on my hard drive for some time because I 
-&lt;br/&gt;
-had a few minor issues to iron out before committing. Then somebody 
-&lt;br/&gt;
-needed some functionlaity from my local &amp;quot;branch&amp;quot; that also contained the 
-&lt;br/&gt;
-XConf code. I committed in a hurry, not noticing that I still used the 
-&lt;br/&gt;
-XPatch method.
-&lt;br/&gt;
-
-&lt;br/&gt;
-The good news is that I have also enabled the XConf includes 
-&lt;br/&gt;
-functionality. But this has not yet been leveraged for plugins.
-&lt;br/&gt;
-
-&lt;br/&gt;
-There are two short term workarounds for you:
-&lt;br/&gt;
-
-&lt;br/&gt;
-1) Use the XPatch facility (see Cocoon docs on XPatch)
-&lt;br/&gt;
-2) is to edit the main/webapp/cocoon.xconf and add the include you need, 
-&lt;br/&gt;
-it will work ust fine.
-&lt;br/&gt;
-
-&lt;br/&gt;
-If you opt for one be aware that we will be removing this in favour of 
-&lt;br/&gt;
-using the includes at some point before the 0.8 release.
+<p>The information in the plugins.xml file would be better kept in the plugin directory and added to the plugins.xml file when deployed. This would reduce the amount of duplication in the plugins config files.
 &lt;br/&gt;
 
 &lt;br/&gt;
-The long term solution to the problem is to create a plugin.xconf file 
-&lt;br/&gt;
-that s built each time Forrest is run, much the same as we do with the 
-&lt;br/&gt;
-sitemap mounts for plugins. We would welcome a patch for this, I can 
-&lt;br/&gt;
-help point you in the right direction if you fancy tackling it.
+All the necessary values are now in the plugin build.xml file.
 &lt;br/&gt;
 
 &lt;br/&gt;
-Could you please create an issue for this and point to this thread in 
-&lt;br/&gt;
-the archives so I do not forget again.
-&lt;br/&gt;
-</p>
+This change will require that the plugins.xml file be retrieved from the build directory rather than the plugins directory when building the plugin documentation pages. We will therefore need a fall back to retrieve this file from the network if it is not currently available - this can be done with the locationmap</p>
 </div>
-<a name="N1007D"></a><a name="%5BFOR-591%5D+MaxMemory+needs+increasing"></a>
-<h2 class="underlined_10">[FOR-591] MaxMemory needs increasing</h2>
+<a name="N1007D"></a><a name="%5BFOR-639%5D+define+terminology+for+the+various+aspects+of+Dispatcher"></a>
+<h2 class="underlined_10">[FOR-639] define terminology for the various aspects of Dispatcher</h2>
 <div class="section">
 <p>
-<a href="http://issues.apache.org/jira/browse/FOR-591">http://issues.apache.org/jira/browse/FOR-591</a>
+<a href="http://issues.apache.org/jira/browse/FOR-639">http://issues.apache.org/jira/browse/FOR-639</a>
 </p>
-<p>Since the docs restructurng for the 0.7 release it has become necessary to increase the maxmemory to be able to build the Forrest site.
-&lt;br/&gt;
-
-&lt;br/&gt;
-Does this indicate a memory leak?
-&lt;br/&gt;
-
-&lt;br/&gt;
-Does someone have the tools to run some diagnostics?
+<p>See the email thread:
 &lt;br/&gt;
-
+&lt;a href="http://marc.theaimsgroup.com/?t=112276643700001"&gt;http://marc.theaimsgroup.com/?t=112276643700001&lt;/a&gt;
 &lt;br/&gt;
-(NB maxmemory has been increased in forrest.properties, if we resolve this issue it should be reduced again)</p>
-</div>
-<a name="N10089"></a><a name="%5BFOR-533%5D+Auto+Generate+plugins.xml+entry"></a>
-<h2 class="underlined_10">[FOR-533] Auto Generate plugins.xml entry</h2>
-<div class="section">
-<p>
-<a href="http://issues.apache.org/jira/browse/FOR-533">http://issues.apache.org/jira/browse/FOR-533</a>
 </p>
-<p>The information in the plugins.xml file would be better kept in the plugin directory and added to the plugins.xml file when deployed. This would reduce the amount of duplication in the plugins config files.
-&lt;br/&gt;
-
-&lt;br/&gt;
-All the necessary values are now in the plugin build.xml file.
-&lt;br/&gt;
-
-&lt;br/&gt;
-This change will require that the plugins.xml file be retrieved from the build directory rather than the plugins directory when building the plugin documentation pages. We will therefore need a fall back to retrieve this file from the network if it is not currently available - this can be done with the locationmap</p>
 </div>
-<a name="N10095"></a><a name="%5BFOR-735%5D+Plugins+are+not+correctly+deployed+in+webapp+mode"></a>
+<a name="N10089"></a><a name="%5BFOR-735%5D+Plugins+are+not+correctly+deployed+in+webapp+mode"></a>
 <h2 class="underlined_10">[FOR-735] Plugins are not correctly deployed in webapp mode</h2>
 <div class="section">
 <p>
@@ -577,7 +437,7 @@
 &lt;br/&gt;
 - the pdf links give an error &amp;quot;Resource Not Found&amp;quot;</p>
 </div>
-<a name="N100A1"></a><a name="%5BFOR-711%5D+Cache+results+from+the+Locationmap"></a>
+<a name="N10095"></a><a name="%5BFOR-711%5D+Cache+results+from+the+Locationmap"></a>
 <h2 class="underlined_10">[FOR-711] Cache results from the Locationmap</h2>
 <div class="section">
 <p>
@@ -593,43 +453,7 @@
 &lt;br/&gt;
 If we test all locationmaps and find no result we should record that tere is no result in this hashmap. This will also be a good place to throw an exception so that Cocoon can better report such errors (see &lt;a href="http://issues.apache.org/jira/browse/FOR-701" title="Missing locationmap entry gives poor error"&gt;FOR-701&lt;/a&gt;)</p>
 </div>
-<a name="N100AD"></a><a name="%5BFOR-707%5D+Document+i18n+features+of+Forrest"></a>
-<h2 class="underlined_10">[FOR-707] Document i18n features of Forrest</h2>
-<div class="section">
-<p>
-<a href="http://issues.apache.org/jira/browse/FOR-707">http://issues.apache.org/jira/browse/FOR-707</a>
-</p>
-<p>There is next to no documentation about i18n, just a pretty poor FAQ entry that points at an issue that has now been closed.
-&lt;br/&gt;
-
-&lt;br/&gt;
-Cheche wrote a blog entry on his work:
-&lt;br/&gt;
-
-&lt;br/&gt;
-&lt;a href="http://casa.che-che.com/blog/2005/05/10/internalization-a-site-using-forrest-07-dev/"&gt;http://casa.che-che.com/blog/2005/05/10/internalization-a-site-using-forrest-07-dev/&lt;/a&gt;
-&lt;br/&gt;
-
-&lt;br/&gt;
-We could, at the very least use the locationmap to pull this content into our site [OT: I wonder if this could be a way to generate more documentation?)</p>
-</div>
-<a name="N100B9"></a><a name="%5BFOR-388%5D+Use+plugins+in-place+if+src+available"></a>
-<h2 class="underlined_10">[FOR-388] Use plugins in-place if src available</h2>
-<div class="section">
-<p>
-<a href="http://issues.apache.org/jira/browse/FOR-388">http://issues.apache.org/jira/browse/FOR-388</a>
-</p>
-<p>At present Forrest will attempt to download plugins even if they are available in src form in the local filesystem as part of an SVN checkout.
-&lt;br/&gt;
-
-&lt;br/&gt;
-Have Forrest mount plugins from designated directories in preference to downloading them wherever possible (need more than posible location for src plugins as some people may be developing their own plugins outside of Forrest)
-&lt;br/&gt;
-
-&lt;br/&gt;
-</p>
-</div>
-<a name="N100C5"></a><a name="%5BFOR-742%5D+trouble+accessing+unversioned+plugin+for+a+released+version+of+Forrest%2C+e.g.+projectInfo"></a>
+<a name="N100A1"></a><a name="%5BFOR-742%5D+trouble+accessing+unversioned+plugin+for+a+released+version+of+Forrest%2C+e.g.+projectInfo"></a>
 <h2 class="underlined_10">[FOR-742] trouble accessing unversioned plugin for a released version of Forrest, e.g. projectInfo</h2>
 <div class="section">
 <p>
@@ -643,27 +467,7 @@
 &lt;br/&gt;
 &lt;a href="http://marc.theaimsgroup.com/?t=113176328300002"&gt;http://marc.theaimsgroup.com/?t=113176328300002&lt;/a&gt;</p>
 </div>
-<a name="N100D1"></a><a name="%5BFOR-639%5D+define+terminology+for+the+various+aspects+of+Dispatcher"></a>
-<h2 class="underlined_10">[FOR-639] define terminology for the various aspects of Dispatcher</h2>
-<div class="section">
-<p>
-<a href="http://issues.apache.org/jira/browse/FOR-639">http://issues.apache.org/jira/browse/FOR-639</a>
-</p>
-<p>See the email thread:
-&lt;br/&gt;
-&lt;a href="http://marc.theaimsgroup.com/?t=112276643700001"&gt;http://marc.theaimsgroup.com/?t=112276643700001&lt;/a&gt;
-&lt;br/&gt;
-</p>
-</div>
-<a name="N100DD"></a><a name="%5BFOR-572%5D+run+a+memory+profiler+while+forrest+is+operating"></a>
-<h2 class="underlined_10">[FOR-572] run a memory profiler while forrest is operating</h2>
-<div class="section">
-<p>
-<a href="http://issues.apache.org/jira/browse/FOR-572">http://issues.apache.org/jira/browse/FOR-572</a>
-</p>
-<p>We need to run a memory profiler while forrest is operating.</p>
-</div>
-<a name="N100E9"></a><a name="%5BFOR-876%5D+locationmap+demo+in+fresh-site+is+broken"></a>
+<a name="N100AD"></a><a name="%5BFOR-876%5D+locationmap+demo+in+fresh-site+is+broken"></a>
 <h2 class="underlined_10">[FOR-876] locationmap demo in fresh-site is broken</h2>
 <div class="section">
 <p>
@@ -675,7 +479,7 @@
 &lt;br/&gt;
 &lt;a href="http://marc.theaimsgroup.com/?t=114681865100003"&gt;http://marc.theaimsgroup.com/?t=114681865100003&lt;/a&gt;</p>
 </div>
-<a name="N100F5"></a><a name="%5BFOR-241%5D+character+entities+%28e.g.+ampersand%29+are+expanded+again+for+href+or+src+attributes"></a>
+<a name="N100B9"></a><a name="%5BFOR-241%5D+character+entities+%28e.g.+ampersand%29+are+expanded+again+for+href+or+src+attributes"></a>
 <h2 class="underlined_10">[FOR-241] character entities (e.g. ampersand) are expanded again for href or src attributes</h2>
 <div class="section">
 <p>
@@ -721,7 +525,7 @@
 &lt;br/&gt;
 the ampersand in the link href attribute is not.</p>
 </div>
-<a name="N10101"></a><a name="%5BFOR-210%5D+whole-site+html+and+pdf%3A+broken+link+faq%2C+broken+image+links"></a>
+<a name="N100C5"></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>
@@ -731,7 +535,7 @@
 &lt;br/&gt;
 </p>
 </div>
-<a name="N1010D"></a><a name="%5BFOR-209%5D+First+level+selected+tab+is+not+highlighted+when+containing+2nd+level+tabs"></a>
+<a name="N100D1"></a><a name="%5BFOR-209%5D+First+level+selected+tab+is+not+highlighted+when+containing+2nd+level+tabs"></a>
 <h2 class="underlined_10">[FOR-209] First level selected tab is not highlighted when containing 2nd level tabs</h2>
 <div class="section">
 <p>
@@ -745,7 +549,15 @@
 &lt;br/&gt;
 </p>
 </div>
-<a name="N10119"></a><a name="%5BFOR-203%5D+2nd+level+tabs+are+not+selected+appropriately"></a>
+<a name="N100DD"></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>
+<a href="http://issues.apache.org/jira/browse/FOR-211">http://issues.apache.org/jira/browse/FOR-211</a>
+</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="N100E9"></a><a name="%5BFOR-203%5D+2nd+level+tabs+are+not+selected+appropriately"></a>
 <h2 class="underlined_10">[FOR-203] 2nd level tabs are not selected appropriately</h2>
 <div class="section">
 <p>
@@ -767,7 +579,7 @@
 &lt;br/&gt;
 &amp;nbsp;&amp;nbsp;Lorenz Froihofer.</p>
 </div>
-<a name="N10125"></a><a name="%5BFOR-200%5D+Locationmap+for+Forrest+and+Users"></a>
+<a name="N100F5"></a><a name="%5BFOR-200%5D+Locationmap+for+Forrest+and+Users"></a>
 <h2 class="underlined_10">[FOR-200] Locationmap for Forrest and Users</h2>
 <div class="section">
 <p>
@@ -779,7 +591,7 @@
 &lt;br/&gt;
 Beware that it will not work for raw files that are not linked, as this &amp;quot;feature&amp;quot; currently uses a fixed dir being being copied by Ant.</p>
 </div>
-<a name="N10131"></a><a name="%5BFOR-546%5D+Sitemap+reference+doc+should+be+updated+to+reflect+plugin+architecture"></a>
+<a name="N10101"></a><a name="%5BFOR-546%5D+Sitemap+reference+doc+should+be+updated+to+reflect+plugin+architecture"></a>
 <h2 class="underlined_10">[FOR-546] Sitemap reference doc should be updated to reflect plugin architecture</h2>
 <div class="section">
 <p>
@@ -810,6 +622,52 @@
 
 &lt;br/&gt;
 I found out about this because my sitemap uses the fo2pdf too (docbook to PDF), and had to add the serializer.</p>
+</div>
+<a name="N1010D"></a><a name="%5BFOR-560%5D+Remove+duplicate+jars+from+eclipse+plugins"></a>
+<h2 class="underlined_10">[FOR-560] Remove duplicate jars from eclipse plugins</h2>
+<div class="section">
+<p>
+<a href="http://issues.apache.org/jira/browse/FOR-560">http://issues.apache.org/jira/browse/FOR-560</a>
+</p>
+<p>tools/eclipse/plugins/org.apache.forrest.eclipse.servletEngine/lib contains some duplicate jars to those in the main Forrest trunk. We should find a way of reusing the jars from their existing location.</p>
+</div>
+<a name="N10119"></a><a name="%5BFOR-644%5D+code-style+cleanup+for+xml+files"></a>
+<h2 class="underlined_10">[FOR-644] code-style cleanup for xml files</h2>
+<div class="section">
+<p>
+<a href="http://issues.apache.org/jira/browse/FOR-644">http://issues.apache.org/jira/browse/FOR-644</a>
+</p>
+<p>We have much inconsistent whitespace in all of our files. This is known to cause trouble in a collaborative environment. See discussion at: &lt;a href="http://marc.theaimsgroup.com/?t=112450901100001"&gt;http://marc.theaimsgroup.com/?t=112450901100001&lt;/a&gt; and &lt;a href="http://marc.theaimsgroup.com/?t=112495618800002"&gt;http://marc.theaimsgroup.com/?t=112495618800002&lt;/a&gt; and various linked discussions.
+&lt;br/&gt;
+</p>
+</div>
+<a name="N10125"></a><a name="%5BFOR-666%5D+clarify+the+sitemap+matches+etc.+in+FAQ+about+non-skinned+html"></a>
+<h2 class="underlined_10">[FOR-666] clarify the sitemap matches etc. in FAQ about non-skinned html</h2>
+<div class="section">
+<p>
+<a href="http://issues.apache.org/jira/browse/FOR-666">http://issues.apache.org/jira/browse/FOR-666</a>
+</p>
+<p>The pattern matching example is quite misleading. There should be a note where exactly to copy your old site (in a standard seeded project) to make the pattern matching work.
+&lt;br/&gt;
+
+&lt;br/&gt;
+At least for me it worked only after I used a  **.html directeive.
+&lt;br/&gt;
+
+&lt;br/&gt;
+&amp;lt;map:match pattern=&amp;quot;old_site/**.html&amp;quot;&amp;gt;</p>
+</div>
+<a name="N10131"></a><a name="%5BFOR-726%5D+use+locationmap+in+all+of+the+plugins"></a>
+<h2 class="underlined_10">[FOR-726] use locationmap in all of the plugins</h2>
+<div class="section">
+<p>
+<a href="http://issues.apache.org/jira/browse/FOR-726">http://issues.apache.org/jira/browse/FOR-726</a>
+</p>
+<p>Each plugin has sitemaps that need to use the locationmap.
+&lt;br/&gt;
+
+&lt;br/&gt;
+(Perhaps we need Jira sub-tasks for each plugin.)</p>
 </div>
 </div>
 <!--+

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

Modified: forrest/site/guidelines.html
URL: http://svn.apache.org/viewcvs/forrest/site/guidelines.html?rev=406639&r1=406638&r2=406639&view=diff
==============================================================================
--- forrest/site/guidelines.html (original)
+++ forrest/site/guidelines.html Mon May 15 07:38:38 2006
@@ -334,7 +334,7 @@
     <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
+<p>The Apache Forrest committers and PMC members are
       <a href="who.html">listed</a>.
     </p>
 </div>
@@ -351,7 +351,24 @@
       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>.
+      <a href="http://www.apache.org/foundation/how-it-works.html#pmc">How-it-works</a>
+      and this
+      <a href="http://mail-archives.apache.org/mod_mbox/incubator-general/200311.mbox/%3C7025D8A1-1D0F-11D8-8AF4-000393753936@apache.org%3E">mail thread</a>.
+    </p>
+<a name="pmc-committers"></a>
+<p id="pmc-committers">
+      At Forrest, the group of PMC members essentially equates to the group of
+      committers. We encourage all committers to be PMC members. See explanation
+      <a href="#elect">below</a>. See the "<a href="who.html">who we are</a>"
+      page for explanation of why some committers from the old project are not
+      PMC members.
+    </p>
+<p>
+      PMC members can be as active as they choose, with no pressure from the
+      project. People can be quiet and speak up occasionally when they see a
+      topic that motivates them enough to contribute to the discussion or to
+      cast a vote. Individual PMC members do not need to be involved in every
+      aspect of the project. As a group, the PMC will maintain sufficient oversight.
     </p>
 <p>The responsibilities of the PMC include:</p>
 <ul>
@@ -361,7 +378,11 @@
       in general.</li>
       
 <li>Keep oversight of the commit log messages and ensure that
-       the codebase does not have copyright and license issues.</li>
+       the codebase does not have copyright and license issues, and that the
+       project is heading in the desired direction.</li>
+      
+<li>Keep oversight of the mailing lists and community to ensure that
+       the <a href="#way">open development</a> ideals are upheld.</li>
       
 <li>Resolve license disputes regarding products of the project,
         including other supporting software that is re-distributed.</li>
@@ -390,15 +411,16 @@
     </p>
 <p>
       Membership of the PMC is by invitation only and must receive
-      consensus approval of the active PMC members.
+      consensus approval of the 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
+      A PMC member is considered "emeritus" by their own declaration, e.g.
+      perhaps personal reasons. Please send a note to the PMC private mail list
+      and we will follow up to request acknowledgement of the Board.
+      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
+      consensus approval of the PMC members. Membership of the PMC can be
+      revoked by unanimous consensus of PMC members (other than
       the member in question).
     </p>
 <p>
@@ -418,7 +440,7 @@
       <a href="http://www.apache.org/dev/pmc.html#chair">PMC FAQ</a>
     
 </p>
-<a name="N100CF"></a><a name="report"></a>
+<a name="N100E9"></a><a name="report"></a>
 <h3 class="underlined_5">Quarterly reports to ASF Board</h3>
 <p>
         Every three months, it is the responsibility of our PMC chair to
@@ -431,23 +453,41 @@
         <a href="http://www.apache.org/foundation/board/calendar.html">
         board meeting</a>. Our reporting schedule is: Feb, May, Aug, Nov.
       </p>
-<a name="N100E0"></a><a name="elect"></a>
+<a name="N100FA"></a><a name="elect"></a>
 <h3 class="underlined_5">Electing new committers and PMC members</h3>
 <p>
+        When we see new people who are committed and consistent, we will discuss
+        each case to ensure that the PMC is in agreement. See the list of
+        <a href="committed.html">qualities</a> that we look for.
         We conduct the vote on the private PMC mailing list to enable a frank
-        discussion.
+        discussion and so that we do not conduct public discussions about people.
+      </p>
+<p>
         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).
+        member. We always want new committers to also be PMC members. Otherwise
+        they do not have a binding vote and so we would create classes of
+        committers. Another issue is
+        <a href="http://mail-archives.apache.org/mod_mbox/incubator-general/200311.mbox/%3C7025D8A1-1D0F-11D8-8AF4-000393753936@apache.org%3E">indemnification</a>.
+        However, when we invite a new committer we do let them choose not to be
+        on the PMC, though we do not encourage that.
+      </p>
+<p>
+        However, there may be extraordinary cases where we want
+        limited work-related commit access and so the committer is not also a
+        PMC member (e.g. perhaps temporary access for
+        <a href="http://wiki.apache.org/general/SummerOfCode">GSoC</a>).
         This will be resolved during the discussion and vote.
-        Notes about this process are in the "committers" svn in the
-        pmc/forrest/ directory.
+      </p>
+<p>
+        PMC members can also see further
+        <a href="https://svn.apache.org/repos/private/committers/pmc/forrest/pmc-member-vote.txt">notes</a>
+        about the process of electing new people.
       </p>
 </div>
 
   
-<a name="N100EB"></a><a name="decision"></a>
+<a name="N1011E"></a><a name="decision"></a>
 <h2 class="underlined_10">Decision making</h2>
 <div class="section">
 <p>
@@ -461,7 +501,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.
     </p>
-<a name="N100F7"></a><a name="voting"></a>
+<a name="N1012A"></a><a name="voting"></a>
 <h3 class="underlined_5">Voting</h3>
 <p>
         Certain actions and decisions regarding the project are made by votes
@@ -550,7 +590,7 @@
         typically take the form of a veto (-1) in reply to the commit message
         sent when the commit is made.
       </p>
-<a name="N1015B"></a><a name="approvals"></a>
+<a name="N1018E"></a><a name="approvals"></a>
 <h3 class="underlined_5">Types of approval</h3>
 <p>
         Different actions require different types of approval:
@@ -594,12 +634,12 @@
           
 <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.
+            Some actions require a 2/3 majority of 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
+            the votes that are cast to be +1.
           </td>
         
 </tr>
@@ -609,14 +649,14 @@
           
 <td colspan="1" rowspan="1"><strong>Unanimous consensus</strong></td>
           <td colspan="1" rowspan="1">
-            All voters with binding votes must vote and there
+            All of the votes that are cast are to be +1 and there
             can be no binding vetoes (-1).
           </td>
         
 </tr>
       
 </table>
-<a name="N101AE"></a><a name="veto"></a>
+<a name="N101E1"></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.
@@ -638,7 +678,7 @@
         If a veto is not withdrawn, the action that has been vetoed must
         be reversed in a timely manner.
       </p>
-<a name="N101C1"></a><a name="actions"></a>
+<a name="N101F4"></a><a name="actions"></a>
 <h3 class="underlined_5">Actions</h3>
 <p>
         This section describes the various actions which are undertaken within
@@ -667,7 +707,7 @@
             Lazy approval
           </td>
           <td colspan="1" rowspan="1">
-            Active PMC members
+            PMC members
           </td>
         
 </tr>
@@ -682,7 +722,7 @@
             Lazy majority
           </td>
           <td colspan="1" rowspan="1">
-            Active PMC members
+            PMC members
           </td>
         
 </tr>
@@ -699,7 +739,7 @@
             Lazy majority
           </td>
           <td colspan="1" rowspan="1">
-            Active PMC members
+            PMC members
           </td>
         
 </tr>
@@ -718,7 +758,7 @@
             2/3 majority
           </td>
           <td colspan="1" rowspan="1">
-            Active PMC members
+            PMC members
           </td>
         
 </tr>
@@ -733,7 +773,7 @@
             Consensus approval
           </td>
           <td colspan="1" rowspan="1">
-            Active PMC members
+           PMC members
           </td>
         
 </tr>
@@ -748,7 +788,7 @@
             Consensus approval
           </td>
           <td colspan="1" rowspan="1">
-            Active PMC members
+            PMC members
           </td>
         
 </tr>
@@ -763,7 +803,7 @@
             Consensus approval
           </td>
           <td colspan="1" rowspan="1">
-            Active PMC members (excluding the member in question)
+            PMC members (excluding the member in question)
           </td>
         
 </tr>
@@ -778,7 +818,7 @@
             Unanimous consensus
           </td>
           <td colspan="1" rowspan="1">
-            Active PMC members (excluding the committer in question if a
+            PMC members (excluding the committer in question if a
             member of the PMC)
           </td>
         
@@ -796,28 +836,34 @@
             Unanimous consensus
           </td>
           <td colspan="1" rowspan="1">
-            Active PMC members (excluding the member in question)
+            PMC members (excluding the member in question)
           </td>
         
 </tr>
       
 </table>
-<a name="N102BD"></a><a name="timeframe"></a>
+<a name="N102F0"></a><a name="timeframe"></a>
 <h3 class="underlined_5">Voting timeframes</h3>
 <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,
+        time to consider the vote. If the vote has not achieved a quorum
+        (the chair decides if sufficient people have voted),
         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="N102C7"></a><a name="procedure"></a>
+<p>
+        Be careful about holidays when calling a vote. This is hard when we do
+        not know customs in every part of the world. So if someone knows that
+        there is a problem with the vote timing, then please say so.
+      </p>
+<a name="N102FD"></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.
+        to ratify the proposal if that is felt to be necessary.
       </p>
 <p>
         The instigator sends the Vote email to the dev mailing list.
@@ -831,7 +877,7 @@
         At the end of the vote period, the instigator tallies the number of
         final votes and reports the results.
       </p>
-<a name="N102DB"></a><a name="ultimatum"></a>
+<a name="N10311"></a><a name="ultimatum"></a>
 <h3 class="underlined_5">Ultimatum and breakdown</h3>
 <p>
         For breakdown situations and those requiring unanimous consensus,
@@ -842,7 +888,7 @@
 </div>
 
   
-<a name="N102E6"></a><a name="communication"></a>
+<a name="N1031C"></a><a name="communication"></a>
 <h2 class="underlined_10">Communication channels</h2>
 <div class="section">
 <p>
@@ -876,7 +922,7 @@
 </div>
 
   
-<a name="N102FC"></a><a name="code"></a>
+<a name="N10332"></a><a name="code"></a>
 <h2 class="underlined_10">Code management</h2>
 <div class="section">
 <p>
@@ -927,7 +973,7 @@
 </div>
 
   
-<a name="N10321"></a><a name="contribution"></a>
+<a name="N10357"></a><a name="contribution"></a>
 <h2 class="underlined_10">Contribution and acknowledgement</h2>
 <div class="section">
 <p>
@@ -1020,7 +1066,7 @@
 </div>
 
   
-<a name="N10373"></a><a name="develop"></a>
+<a name="N103A9"></a><a name="develop"></a>
 <h2 class="underlined_10">Development procedure</h2>
 <div class="section">
 <div class="note">

Modified: forrest/site/guidelines.pdf
URL: http://svn.apache.org/viewcvs/forrest/site/guidelines.pdf?rev=406639&r1=406638&r2=406639&view=diff
==============================================================================
Binary files - no diff available.

Modified: forrest/site/linkmap.html
URL: http://svn.apache.org/viewcvs/forrest/site/linkmap.html?rev=406639&r1=406638&r2=406639&view=diff
==============================================================================
--- forrest/site/linkmap.html (original)
+++ forrest/site/linkmap.html Mon May 15 07:38:38 2006
@@ -216,8 +216,10 @@
 </li>
 </ul>
 
-
     
+    
+    
+
     
 <ul>
 <li>

Modified: forrest/site/who.html
URL: http://svn.apache.org/viewcvs/forrest/site/who.html?rev=406639&r1=406638&r2=406639&view=diff
==============================================================================
--- forrest/site/who.html (original)
+++ forrest/site/who.html Mon May 15 07:38:38 2006
@@ -180,10 +180,7 @@
 <a href="#community">The Forrest Community</a>
 </li>
 <li>
-<a href="#active">Active Committers</a>
-</li>
-<li>
-<a href="#inactive">Inactive Committers</a>
+<a href="#committers">List of committers</a>
 </li>
 <li>
 <a href="#notes">Notes</a>
@@ -194,7 +191,7 @@
 <a name="N1000D"></a><a name="community"></a>
 <h2 class="underlined_10">The Forrest Community</h2>
 <div class="section">
-<p> The Forrest Project operates on a meritocracy: the more you do, the
+<p> The Forrest Project operates as a meritocracy: the more you do, the
         more responsibility you will obtain. This page lists all of the people who have
         gone the extra mile and are Committers. If you would like to get involved, the
         first step is to join the mailing lists. </p>
@@ -203,6 +200,7 @@
         Thanks to the many people for their contributions
         of patches, assistance, ideas, and email discussion.
         Some are mentioned at the <a href="docs_0_80/changes.html">changes</a> page.
+        See how we <a href="guidelines.html#contribution">acknowledge</a> contributions.
       </p>
 <p>
         Please do not send emails directly to individual developers asking for
@@ -211,17 +209,25 @@
       </p>
 </div>
     
-<a name="N10025"></a><a name="active"></a>
-<h2 class="underlined_10">Active Committers</h2>
+<a name="N10029"></a><a name="committers"></a>
+<h2 class="underlined_10">List of committers</h2>
 <div class="section">
+<p>List of all people who have ever been committers at Apache Forrest, sorted alphabetically.</p>
 <ul>
         
 <li>
+<em>[NKB] - Nicola Ken Barozzi (nicolaken.at.apache.org)</em>
+</li>
+        
+<li>
 <strong>[DB] - Dave Brondsema (brondsem.at.apache.org)</strong>
 </li>
         
 <li>
-<strong><em>[DC] - David Crossley (crossley.at.apache.org)</em></strong>
+<strong>[DC] - David Crossley (crossley.at.apache.org)</strong> - PMC Chair</li>
+        
+<li>
+<strong>[CD] - Cyriaque Dupoirieux (cdupoirieux.at.apache.org)</strong>
 </li>
         
 <li>
@@ -233,76 +239,65 @@
 </li>
         
 <li>
-<strong>[JJP] - Juan Jose Pablos (cheche.at.apache.org)</strong>
+<strong>[DG] - Diwaker Gupta (diwaker.at.apache.org)</strong>
 </li>
         
-<li>
-<strong>[JS] - Johannes Schaefer (josch.at.apache.org)</strong>
-</li>
+<li>[SM] - Stefano Mazzocchi (stefano.at.apache.org)</li>
+        
+<li>[JM] - John Morrison (morrijr.at.apache.org)</li>
+        
+<li>[SN] - Steven Noels (stevenn.at.apache.org)</li>
         
 <li>
-<strong>[TS] - Thorsten Scherler (thorsten.at.apache.org)</strong>
+<strong>[JJP] - Juan Jose Pablos (cheche.at.apache.org)</strong>
 </li>
         
+<li>[KP] - Konstantin Piroumian (kpiroumian.at.apache.org)</li>
+        
+<li>[MP] - Marc Portier (mpo.at.apache.org)</li>
+        
+<li>[SR] - Sam Ruby (rubys.at.apache.org)</li>
+        
 <li>
-<strong>[RFT] - Rick F. Tessner (rick.at.apache.org)</strong>
+<strong>[JS] - Johannes Schaefer (josch.at.apache.org)</strong>
 </li>
         
 <li>
-<strong>[FSO] - Ferdinand Soethe (ferdinand.at.apache.org)</strong>
+<strong>[TS] - Thorsten Scherler (thorsten.at.apache.org)</strong>
 </li>
         
 <li>
-<strong>[TW] - Tim Williams (twilliams.at.apache.org)</strong>
+<strong>[FSO] - Ferdinand Soethe (ferdinand.at.apache.org)</strong>
 </li>
         
 <li>
-<strong>[CD] - Cyriaque Dupoirieux (cdupoirieux.at.apache.org)</strong>
+<strong>[RFT] - Rick F. Tessner (rick.at.apache.org)</strong>
 </li>
-      
-</ul>
-</div>
-    
-<a name="N1005C"></a><a name="inactive"></a>
-<h2 class="underlined_10">Inactive Committers</h2>
-<div class="section">
-<ul>
-        
-<li>[NKB] - Nicola Ken Barozzi (nicolaken.at.apache.org)</li>
-        
-<li>[SM] - Stefano Mazzocchi (stefano.at.apache.org)</li>
-        
-<li>[JM] - John Morrison (morrijr.at.apache.org)</li>
-        
-<li>[SN] - Steven Noels (stevenn.at.apache.org)</li>
-        
-<li>[KP] - Konstantin Piroumian (kpiroumian.at.apache.org)</li>
-        
-<li>[MP] - Marc Portier (mpo.at.apache.org)</li>
-        
-<li>[SR] - Sam Ruby (rubys.at.apache.org)</li>
         
 <li>[JT] - Jeff Turner (jefft.at.apache.org)</li>
         
-<li>[DG] - Diwaker Gupta (diwaker.at.apache.org)</li>
+<li>
+<strong>[TW] - Tim Williams (twilliams.at.apache.org)</strong>
+</li>
       
 </ul>
 </div>
     
-<a name="N10081"></a><a name="notes"></a>
+<a name="N10080"></a><a name="notes"></a>
 <h2 class="underlined_10">Notes</h2>
 <div class="section">
-<p>Strong type denotes <strong>PMC member</strong>
-</p>
-<p>Emphasis type denotes <em>PMC chair</em>
-</p>
-<p>See the <a href="http://apache.org/foundation/how-it-works.html#roles">ASF role definitions</a> for detailed role information.</p>
+<p>Strong type denotes "Project Management Committee (<a href="guidelines.html#pmc">PMC</a>) member".
+      Emphasis type denotes "emeritus PMC member".
+      See the <a href="guidelines.html#roles">ASF role definitions</a> for detailed role information.</p>
+<p>Some people were committers prior to Forrest becoming a top-level project and
+      so gaining a PMC. They were not around since then, so have never been on the PMC.
+      All new committers are <a href="guidelines.html#pmc-committers">encouraged</a> to be PMC members.
+      </p>
 <p>
-        The term "active" is not measured by "number of svn commits".
-        A committer can be active simply by participating occasionally
-        on the mailing lists.
-        Some people go away for various reasons.
-        They are welcome to return at any time.
+        Committers can be as active as they choose and there is no performance
+        pressure from the project. For those who are interested in the work
+        that each paticular committer has done, see the
+        <a href="guidelines.html#contributions">acknowledgements</a> section.
       </p>
 <p> All <a href="http://cocoon.apache.org/community/members.html">Apache Cocoon committers</a>
       and <a href="http://lenya.apache.org/community/acknowledgements.html">Apache Lenya committers</a>

Modified: forrest/site/who.pdf
URL: http://svn.apache.org/viewcvs/forrest/site/who.pdf?rev=406639&r1=406638&r2=406639&view=diff
==============================================================================
Binary files - no diff available.



Mime
View raw message