httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sl...@apache.org
Subject cvs commit: httpd-site/docs/dev patches.html
Date Thu, 17 Jun 2004 18:15:23 GMT
slive       2004/06/17 11:15:23

  Modified:    xdocs/dev patches.xml
               docs/dev patches.html
  Log:
  What to do if your patch gets ignored.
  
  Revision  Changes    Path
  1.8       +29 -0     httpd-site/xdocs/dev/patches.xml
  
  Index: patches.xml
  ===================================================================
  RCS file: /home/cvs/httpd-site/xdocs/dev/patches.xml,v
  retrieving revision 1.7
  retrieving revision 1.8
  diff -u -d -b -u -r1.7 -r1.8
  --- patches.xml	20 Nov 2003 13:12:13 -0000	1.7
  +++ patches.xml	17 Jun 2004 18:15:21 -0000	1.8
  @@ -157,5 +157,34 @@
   
   </section>
   
  +<section id="ignored"><title>What if my patch gets ignored?</title>
  +
  +<p>Because Apache has only a small number of volunteer developers, and
  +these developers are often very busy, it is possible that your patch
  +will not receive any immediate feedback.  Developers must prioritize
  +their time, dealing first with serious bugs and with parts of the code
  +in which they have interest and knowledge.  Here are some suggestions
  +on what you can do to encourage action on your patch:</p>
  +
  +<ol>
  +
  +<li>Encourage other Apache users to review and test your patch, and then
  +append a note to the bug report with the details.  Developers are much more
  +likely to review and commit a patch if they see that it has been widely
  +tested.</li>
  +
  +<li>Make sure your patch is easy to read and apply.  Follow all the
  +style suggestions in the above sections and include any necessary
  +documentation changes.</li>
  +
  +<li>Be persistent but polite.  Post to the developers list pointing
  +out your patch and why you feel it is important.  Feel free to do this
  +about once a week and continue until you get a response. Just be sure
  +to be polite about it, since the developers are unlikely to respond to
  +rude messages.</li>
  +
  +</ol>
  +</section>
  +
   </body>
   </document>
  
  
  
  1.30      +35 -0     httpd-site/docs/dev/patches.html
  
  Index: patches.html
  ===================================================================
  RCS file: /home/cvs/httpd-site/docs/dev/patches.html,v
  retrieving revision 1.29
  retrieving revision 1.30
  diff -u -d -b -u -r1.29 -r1.30
  --- patches.html	29 May 2004 22:55:49 -0000	1.29
  +++ patches.html	17 Jun 2004 18:15:23 -0000	1.30
  @@ -218,6 +218,41 @@
     </blockquote>
    </td></tr>
   </table>
  +           <table border="0" cellspacing="0" cellpadding="2" width="100%">
  + <tr><td bgcolor="#525D76">
  +  <font color="#ffffff" face="arial,helvetica,sanserif">
  +   <a name="ignored"><strong>What if my patch gets ignored?</strong></a>
  +  </font>
  + </td></tr>
  + <tr><td>
  +  <blockquote>
  +<p>Because Apache has only a small number of volunteer developers, and
  +these developers are often very busy, it is possible that your patch
  +will not receive any immediate feedback.  Developers must prioritize
  +their time, dealing first with serious bugs and with parts of the code
  +in which they have interest and knowledge.  Here are some suggestions
  +on what you can do to encourage action on your patch:</p>
  +<ol>
  +
  +<li>Encourage other Apache users to review and test your patch, and then
  +append a note to the bug report with the details.  Developers are much more
  +likely to review and commit a patch if they see that it has been widely
  +tested.</li>
  +
  +<li>Make sure your patch is easy to read and apply.  Follow all the
  +style suggestions in the above sections and include any necessary
  +documentation changes.</li>
  +
  +<li>Be persistent but polite.  Post to the developers list pointing
  +out your patch and why you feel it is important.  Feel free to do this
  +about once a week and continue until you get a response. Just be sure
  +to be polite about it, since the developers are unlikely to respond to
  +rude messages.</li>
  +
  +</ol>
  +  </blockquote>
  + </td></tr>
  +</table>
            </td>
      </tr>
      <!-- FOOTER -->
  
  
  

Mime
View raw message