On Fri, 2002-08-02 at 19:56, Marc Schier wrote: > I know it was probably asked a million times before
yup. You'd need archives for avalon-dev though; I'll bet ya searching the archive for this list would've yielded zero results until now as it is pretty new. > but what is the best way > to submit patches and code for Apache (and specifically Avalon) projects? > Do the committers prefer direct mail contact with the code author, bugzilla > or newsgroup, or doesn't it matter? I guess bugzilla makes sense in the > case of feature requests and actual bugs... Specific to avalon ------------------ Either bugzilla or mailing list (this is not a newsgroup =) is cool. It should be bugzilla-only but we don't like it very much and will be moving to something else (Scarab) in the future, at which point we might start an official policy. Also anything you are unsure about, like you are not sure whether the bug is in your app or in avalon, this mailing list is the best place. Please do not contact committers directly though. There's usually several people that can apply your patch, and the one that's least busy (or most awake; we're pretty much 24/7 =) usually does so. for Jakarta in general ---------------------- I don't think any project finds it annoying if you post a patch to the mailing list (preprend "[PATCH]" though), the -dev list is usually the place for patches; some might prefer use of either bugzilla or scarab though. The place for future requests is probably the -user list if it exists; if it does not use avalon-dev. In any case, contacting committers directly is probably not the best idea. If you are not sure, check the project docs/mail archives. Any enhancement is generally welcomed though =) for Apache in general --------------------- You need to check the docs/mail archives for the Apache project you use. Different projects have different guidelines. In any case, contacting committers directly is probably not the best idea. final notes ----------- please send patches in unified diff format $(diff -u) as that means less trouble applying it. It is usually most appropriate to create your diff with the src/ directory as basedir, and preferably against the latest CVS version. best regards, Leo Simons -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
