*: If one wants to contribute code to cvstrac who would you need to contact? This should maybe be a {wiki:FrequentlyAskedQuestions FAQ}... The _best_ method to contribute code is to attach a patch to a ticket (new or otherwise). Patches would hopefully follow CvstracCodingGuidelines and common sense (small, discrete patches are better than big masses of unrelated changes), but _some_ code (even incomplete or obviously unsuitable) is almost as valuable as _perfect_ code. *: What kind of patch format does cvstrac development prefer? _::Would *cvs diff -N -u | gzip > patch.gz* suffice _:::Certainly, although uncompressed would be best if the size is reasonable (under 100k). But we're not overly picky about formats. Even an archive of changed/new files is useful. We can fix just about any kind of patch _except_ the kind that doesn't exist. Smaller patches will usually be committed by an existing developer. Larger development work will normally be handled by granting someone a CVSTrac account with checkin permissions. Should _direct_ contact with a maintainer be required (i.e. security issues, account stuff), e-mail to {link:mailto:drh@hwaci.com drh} and/or {link:mailto:cpb@cpan.org cpb} would be appropriate ({link:mailto:cpb@cpan.org cpb} currently handles most day-to-day development issues). However, keep in mind that very, _very_ little development is done via e-mail; get used to the ticket system.