It's great to see that things are happening, Jeff!
The people issues are at least:
a) making sure patches submitted on the mailing list are in the db, by prodding the submitter to consult some on-line doc that describes the requirements for submitting a patch
- get the style correct
- use the right diff flavor
- explain how to reproduce the problem and how the patch has been tested
- go to nagoya.apache.org and submit the patch as a PR, not forgetting to flag the entry with PatchAvailable
- make sure that the PR # is in the subject of any on-list discussion of the patch
Why not automate this process. Change bugzilla to do the job and autogenerate the right link:
<a hred="mailto:[EMAIL PROTECTED]">Post the patch to the httpd-dev list]</a>
The cool thing about RT is that it does all this for you and all discussions at the list are "blogged" into the bug record.
__________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
