There are lots of modules on CPAN, and this is generally perceived
to be a Good Thing. The barrier to entry is also relatively low,
which encourages people to upload early versions, which they'll
hopefully get feedback on, and maybe even help.
The downside is that for many tasks you will find multiple modules,
and it's often not clear which is the most appropriate module for
you. Recently I needed code to randomly generate a temporary
password, and discovered 12 CPAN modules which I might use.
I decided to try a CPAN Curation experiment. Every time I need a
module and find multiple candidates on CPAN, I'll write a review.
I'll submit bugs and where possible patches on the modules I
look at. And I'll keep the reviews up to date as new versions of
modules are released.
In this talk I'll cover experiences so far, the tools I'm working on
to help this process, and how I think the approach could be
Attended by: Tom Hukins, Gabor Szabo (szabgab), Leo Lapworth (Ranguard), Stevan Little (stevan), Ian Norton (idn), Peter Rabbitson (ribasushi), Kayvan Javid, Mark Norman Francis, John Harrison (JohnGH), Peter Shangov (pshangov), Claes Jakobsson (claes), Arthur Schmidt (fREW), Tomas Doran (t0m), Jess Robinson (castaway),