svn commit: r414411 - /forrest/trunk/site-author/content/xdocs/contrib.xml

[cr...@apache.org]

Author: crossley
Date: Wed Jun 14 16:26:18 2006
New Revision: 414411

URL: http://svn.apache.org/viewvc?rev=414411&view=rev
Log:
Refer new devs to our "obtain SVN" instructions rather than
dumping them into the viewvc interface.
Encourage contributions of samples.
Other minor text tweaks.

Modified:
    forrest/trunk/site-author/content/xdocs/contrib.xml

Modified: forrest/trunk/site-author/content/xdocs/contrib.xml
URL: http://svn.apache.org/viewvc/forrest/trunk/site-author/content/xdocs/contrib.xml?rev=414411&r1=414410&r2=414411&view=diff
==============================================================================
--- forrest/trunk/site-author/content/xdocs/contrib.xml (original)
+++ forrest/trunk/site-author/content/xdocs/contrib.xml Wed Jun 14 16:26:18 2006
@@ -28,7 +28,7 @@
       project - either with direct participation (coding, documenting, answering
       questions, proposing ideas, reporting bugs, suggesting bug-fixes, etc..) or by
       resource donations (staff time, conference presentations, publicity, software)
-      and even direct hardware/money
+      and even general hardware/money
       <link href="http://www.apache.org/foundation/thanks.html">donations</link>
       via the ASF.
       </p>
@@ -37,11 +37,11 @@
       information on how to subscribe and to access the mail list archives).
       Listen-in for a while, to hear how others make contributions. </p>
       <p>You can get your local working copy of the
-        <link href="site:SVN">latest and
-      greatest code</link> (which you find in the Forrest module in the SVN code
-      repository. Review the todo list, choose a task (or perhaps you have noticed
-      something that needs patching). Make the changes, do the testing, generate a
-      patch, and post to the dev mailing list. (Do not worry - the process is easy
+        <link href="site:build">latest and
+      greatest code</link> (which you find in the Forrest module in the Subversion code
+      repository). Review the todo list and the issue tracker, choose a task. Perhaps you have noticed
+      something that needs patching, or have a new feature to contribute. Make the changes, do the testing, generate a
+      patch, and discuss on the dev mailing list. (Do not worry - the process is easy
       and explained below.) </p>
       <p> Document writers are usually the most wanted people so if you like to
         help but you're not familiar with the innermost technical details, don't worry:
@@ -55,6 +55,8 @@
         <li>Assisting to improve documentation.</li>
         <li>Testing Forrest (especially its less-frequently-used features) on
           various configurations and reporting back.</li>
+        <li>New samples for the 'forrest seed-sample' to concisely describe
+          and demonstrate features. Such samples can also enable automated testing.</li>
         <li>Debugging - producing reproduceable test cases and/or finding
           causes of bugs. Some known bugs are informally listed on To Do, and some are
           recorded as issues (see <link href="#procedure">explanation