[Tielman, Greg, and John contacted me - I'm replying with technical details here, rather than direct to them, since I hope it'll help others get interested in helping out as well.]
If you send me your perl.org id (http://auth.perl.org/ or https://www.bitcard.org) then I'll give you commit access to svn. Meanwhile, read the first part of this to get yourself a local copy of DBI http://search.cpan.org/~timb/DBI-1.52/DBI.pm#How_to_create_a_patch_using_Subversion Here are some general areas that need work: - Increasing test coverage, It's pretty poor right now: http://pjcj.sytes.net/cover/latest/DBI-1.52/coverage.html Start with improving the subroutine coverage http://pjcj.sytes.net/cover/latest/DBI-1.52/blib-lib-DBI-pm--subroutine.html - Fixing bugs, of which a few are listed here: http://rt.cpan.org/NoAuth/Bugs.html?Dist=DBI Naturally I'll offer direction and guidance on any you want to tackle. I've also got a few that could be entered into rt.cpan.org. - Test the proxy the same way that DBI::PurePerl is tested. In other words, by creating wrappers test files for each test file that just set $ENV{DBI_AUTOPROXY} and run the original test. This is a bigger job and likely to uncover a bunch of issues. We really need someone to focus on proxy development. Any volunteers out there? Using DBD::Proxy? Want to help out? - Refactor %DBI::DBI_methods into a separate module and replace the O => 0x0418 | 0x4 mess with the rather more meaningful O => IMA_KEEP_ERR|IMA_KEEP_ERR_SUB|IMA_NO_TAINT_IN|IMA_UNRELATED_TO_STMT This would probably also help with DBI v2. Pick whichever takes your fancy. Also see Roadmap.pod and ToDo in http://svn.perl.org/modules/dbi/trunk/ - those are somewhat out of date but many of the things outlined there are still worth doing. Use [email protected] to coordinate so you don't duplicate work, and for any other DBI development discussions. I'm going to arrange for the automated svn checkin emails to be sent to dbi-dev so everyone sees progress, can spot issues early, and keeps in sync. Have fun! Tim.
