cocoon-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cross...@apache.org
Subject cvs commit: xml-cocoon2/documentation/xdocs contrib.xml
Date Sat, 24 Nov 2001 08:43:23 GMT
crossley    01/11/24 00:43:23

  Modified:    documentation/xdocs Tag: cocoon_20_branch contrib.xml
  Log:
  Revised introduction and added some tips about email.
  
  Revision  Changes    Path
  No                   revision
  
  
  No                   revision
  
  
  1.1.2.6   +24 -5     xml-cocoon2/documentation/xdocs/contrib.xml
  
  Index: contrib.xml
  ===================================================================
  RCS file: /home/cvs/xml-cocoon2/documentation/xdocs/contrib.xml,v
  retrieving revision 1.1.2.5
  retrieving revision 1.1.2.6
  diff -u -r1.1.2.5 -r1.1.2.6
  --- contrib.xml	2001/11/01 04:06:06	1.1.2.5
  +++ contrib.xml	2001/11/24 08:43:23	1.1.2.6
  @@ -30,14 +30,20 @@
      To begin with, we suggest you to subscribe to the
      <link href="mail-lists.html">Cocoon mailing lists</link>
      (follow the link for information on how to subscribe and to access the mail
  -   list archives), to checkout the 
  +   list archives). Listen-in for a while, to hear how others make contibutions.
  +  </p>
  +
  +  <p>You can get your local working copy of the
      <link href="http://cvs.apache.org/viewcvs.cgi/xml-cocoon2/">latest and
      greatest code</link> (which you find in the xml-cocoon2 module in
      the cvs.apache.org CVS code repository, or from the
  -   <link href="http://xml.apache.org/from-cvs/xml-cocoon2/">CVS snapshots</link>),
  -   control the <link href="todo.html">todo</link>
  -   list and jump in.
  +   <link href="http://xml.apache.org/from-cvs/xml-cocoon2/">CVS snapshots</link>).
  +   Review the <link href="todo.html">todo</link> 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 cocoon-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:
  @@ -361,9 +367,22 @@
       humans trying to browse a voluminous list, will respond favourably to a
       descriptive title.
      </li>
  +   <li>Start new threads with new Subject for new topics, rather than
  +    re-using the previous Subject line.
  +   </li>
  +   <li>Keep each topic focussed. If some new topic arises then start a new
  +    discussion. This leaves the original topic to continue un-cluttered.
  +   </li>
  +   <li>Whenever you decide to start a new topic, then start with a fresh
  +    new email message window. Do not use the &quot;Reply to&quot; button,
  +    because threaded mail-readers get confused (they utilise the 
  +    <code>In-reply-to</code> header). If so, then your new topic will get
  +    lost in the previous thread and go un-answered.
  +   </li>
      <li>
       Prepend your email subject line with <code>[Patch]</code>, or
  -   <code>[Proposal]</code>, or something else, when that is appropriate.
  +    <code>[Proposal]</code>, <code>RT</code> (Research Topic),
etc. when that
  +    is appropriate.
      </li>
      <li>
       When making changes to XML documentation, or any XML document for that
  
  
  

----------------------------------------------------------------------
In case of troubles, e-mail:     webmaster@xml.apache.org
To unsubscribe, e-mail:          cocoon-cvs-unsubscribe@xml.apache.org
For additional commands, e-mail: cocoon-cvs-help@xml.apache.org


Mime
View raw message