forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From brond...@apache.org
Subject cvs commit: xml-forrest/src/documentation/content/xdocs contrib.xml
Date Wed, 26 Nov 2003 05:18:57 GMT
brondsem    2003/11/25 21:18:57

  Modified:    src/documentation/content/xdocs contrib.xml
  Log:
  update cvs link; update issue tracking & mail list names
  
  Revision  Changes    Path
  1.10      +13 -15    xml-forrest/src/documentation/content/xdocs/contrib.xml
  
  Index: contrib.xml
  ===================================================================
  RCS file: /home/cvs/xml-forrest/src/documentation/content/xdocs/contrib.xml,v
  retrieving revision 1.9
  retrieving revision 1.10
  diff -u -r1.9 -r1.10
  --- contrib.xml	13 Aug 2003 10:34:55 -0000	1.9
  +++ contrib.xml	26 Nov 2003 05:18:57 -0000	1.10
  @@ -21,7 +21,7 @@
         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="http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/Forrest">latest
and
  +        <link href="site:CVS">latest and
         greatest code</link> (which you find in the Forrest module in the CVS 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
  @@ -37,18 +37,15 @@
           improved code and/or documentation, but we would also be glad to have extra
           help in any of the following areas: </p>
         <ul>
  -        <li>Answering questions on the <code>users</code> mailing list
- there
  -          is often a problem of having too many questioners and not enough experts to
  -          respond to all the questions.</li>
           <li>Testing Forrest (especially its less-frequently-used features) on
             various configurations and reporting back.</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 in Bugzilla (see <link href="#procedure">explanation
  +          recorded as issues (see <link href="#procedure">explanation
         below</link>).</li>
         <li>Specifying/analysing/designing new features - and beyond. (If you
  -        wish to get involved with this, please join <code>general Forrest mailing
  -        list</code>, install and try out Forrest and read some of the
  +        wish to get involved with this, please join the <code>forrest-dev</code>
mailing
  +        list, install and try out Forrest and read some of the
           <link href="site:mail-lists">mail archives</link>. You should have
a strong
         "fluency" in XML technologies, Java and a basic understanding of the Forrest
         architecture - don't just say "it should have XYZ" without reading anything
  @@ -57,7 +54,7 @@
           possible configurations out there. (The project does not maintain anything but
           the basic <code>.zip</code> and <code>.tar.gz</code> packages,
but anyone is
           welcome to build their own specific packages and announce them on the
  -        <code>general Forrest list</code>)</li>
  +        <code>forrest-dev</code> list)</li>
         <li>... and there is just one other thing - don't forget to tell everyone
           who asks, how great Forrest is! ;-) The more people that know about and start
           to use Forrest, the larger the pool of potential contributors there will be.
  @@ -100,21 +97,22 @@
         <p> There are two methods for discussing development and submitting
           patches. So that everyone can be productive, it is important to know which
           method is appropriate for a certain situation and how to go about it without
  -        confusion. This section explains when to use the <code>developer</code>
  -        <link href="site:mail-lists">mailing list</link> the bug database.
</p>
  +        confusion. This section explains when to use the developer
  +        <link href="site:mail-lists">mailing list</link> and the
  +        <link href="site:forrest-issues">issue tracker</link>. </p>
         <p> Research your topic thoroughly before beginning to discuss a new
           development issue. Search and browse through the email archives - your issue
           may have been discussed before. Prepare your post clearly and concisely. </p>
         <p> Most issues will be discovered, resolved, and then patched quickly
  -        via the <code>developer</code> mailing list. Larger issues, and ones
that are
  -        not yet fully understood or are hard to solve, are destined for Bugzilla. </p>
  -      <p> Experienced developers use Bugzilla directly, as they are very sure
  +        via the developer mailing list. Larger issues, and ones that are
  +        not yet fully understood or are hard to solve, are destined for the issue tracker.
</p>
  +      <p> Experienced developers use the issue tracker directly, as they are very
sure
           when they have found a bug and when not. However, less experienced users should
           first discuss it on the user or developer mailing list (as appropriate).
  -        Impatient people always enter everything into Bugzilla without caring if it is
  +        Impatient people always enter everything into the issue tracker without caring
if it is
           a bug of Forrest or their own installation/configuration mistake - please do
           not do this. </p>
  -      <p> As a rule-of-thumb, discuss an issue on the <code>developers</code>
  +      <p> As a rule-of-thumb, discuss an issue on the developers
           mailing list first to work out any details. After it is confirmed to be
           worthwhile, and you are clear about it, then submit the bug description or
           patch via Bug Tracking. </p>
  
  
  

Mime
View raw message