Leader of Birmingham.pm [pm.org] and a CPAN author [cpan.org]. Co-organised YAPC::Europe in 2006 and the 2009 QA Hackathon, responsible for the YAPC Conference Surveys [yapc-surveys.org] and the QA Hackathon [qa-hackathon.org] websites. Also the current caretaker for the CPAN Testers websites and data stores.
If you really want to find out more, buy me a Guinness
Links:
Memoirs of a Roadie [missbarbell.co.uk]
[pm.org]
CPAN Testers Reports [cpantesters.org]
YAPC Conference Surveys [yapc-surveys.org]
QA Hackathon [qa-hackathon.org]
In other news, I've been fiddling with my Kwiki wiki and noticed a bit of a problem with config files. Unfortunately Brian only allowed for backup files with a ~ on the end. Here on Windows
Still having fun trying to figure out a good way to get the latest comments for WWW::UsePerl::Journal. I should really sort out the patch for the sorting and send that off soon too. But seeing as I haven't touched my laptop this week, I'm a bit behind. Does anyone know of a good way of creating a patch file on Windows? The diff app I have is a GUI, which isn't much help. A-ha! Text::Diff looks to like it'll do the trick. It's amazing what you can find on CPAN these days.
After promising myself, that I wasn't going to over stretch myself with talks at the next Birmingham.pm tech meet, aside from my now traditional YAPC::Europe debrief, I'm thinking about doing something about Cool File & Directory Modules. So far this year I have tried to highlight some great modules on CPAN and the File IO side of things is something I haven't touched on. Recently on a help forum I noticed the complete lack of knowledge of some great modules, and found people reinventing the wheel. Currently planned for the talk are:
A kind of short Perl Advent Calendar. Any others that people think I ought to include? I'm not covering File::Spec as it breaks too often for me.
Congratualtions! (Score:2)
As to the module list, I have only one thing to say: spread the love for File::Temp. I've fixed so many tests locally that used hard coded file names. Of course they broke as soon as the somebody other than the original author ran them... Of course, tell people to ignore most of the functions in there and concentrate on tempfile() and tempdir(). It's too confusing otherwise.
-Dom