husted      2002/12/22 08:56:00

  Modified:    doc/faqs helping.xml
  Log:
  Clarify how to submit patches.
  
  Revision  Changes    Path
  1.3       +19 -5     jakarta-struts/doc/faqs/helping.xml
  
  Index: helping.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-struts/doc/faqs/helping.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- helping.xml       6 Nov 2002 22:48:46 -0000       1.2
  +++ helping.xml       22 Dec 2002 16:56:00 -0000      1.3
  @@ -39,11 +39,14 @@
   </p>
   
   <p>
  -Our challenge to any team using Struts is to donate the time of one team member one
  -afternoon a week (or more if you can spare the resources). Have your team member 
browse Bugzilla for any
  -issues without a <a href="#code">patch</a> or <a href="#tests">unit test</a>, and 
add the patch or test.
  -If the patch is written on company time, and you want to give your company an 
author's credit, that's
  -fine with us.
  +Our challenge to any team using Struts is to donate the time of one team member 
  +one afternoon a week (or more if you can spare the resources). 
  +Have your team member browse 
  +<a href="http://jakarta.apache.org/site/bugs.html";>Bugzilla</a> for any issues 
  +without a <a href="#code">patch</a> or <a href="#tests">unit test</a>, 
  +and add the patch or test.
  +If the patch is written on company time, 
  +and you want to give your company an author's credit, that's fine with us.
   </p>
   
   <p>
  @@ -57,6 +60,17 @@
   how-tos that we can make part of the <a href="documentation">documentation</a>. The 
mailing list is very
   active and trundling through the archives is no picnic. We can always use people 
who can reduce the best
   threads to coherent articles that we can put in the User Guide.
  +</p>
  +
  +<p>
  +Some Apache products like you to submit your patch to the mailing list. 
  +We would prefer that you create a 
  +<a href="http://jakarta.apache.org/site/bugs.html";>Bugzilla</a>
  +Bugzilla report and then attach the patch to the report. 
  +To do this, you must first create the report, 
  +and then modify the report to add your patch. 
  +We realize this is a bit clumsy, but it keeps us from losing things, 
  +and helps to ensure that your patch will be attended.
   </p>
   
   <p>
  
  
  

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to