NEILB's Blog

I've just released a new version of HTML::Summary, which I adopted from Ave Wrigley (AWRIGLEY) and Tony Rose (TGROSE). The main reason I did this was to resolve a mix-up in PAUSE permissions, that was spotted by Brian Cassidy (BRICAS). But I was also coming full circle: I previously worked with Ave and Tony, and wrote the first version of HTML::Summary (with Tony), which never made it to CPAN.

I've extended the CPAN adoption list to factor in results from CPAN Testers. This caused 6 dists to move up into the top 20.

I've added an adoption leaderboard to my CPAN adoption list. Kudos to Ron Savage who chipping away at the adoption list.

Two weeks ago I published a list of CPAN modules that might be candidates for adoption, and described the metric used to score them. I had a lot of comments on that version, which has prompted version 3 of the metric. The key change is the use of gating criteria to decide whether a module should even be considered for the list. The new list contains dists that score at least 5 (out of 14), which is about 4% of the dists on CPAN.

PAUSE supports an informal mechanism for flagging that a module is available to be taken over, or to flag that you'd like help. In this article I'll outline the mechanism, and point out some things to be aware of.

Last week I described a process for adopting a CPAN module. In this post I describe a metric for identifying candidates for adoption. These are essentially modules that have outstanding bugs, haven't been released for a while, and are used by other modules. I've generated a list of the top 1000 adoption candidates according to my current scoring metric. This is very much a work in progress.

Adopting a module on CPAN is a good way to learn the process of creating, releasing and maintaining a CPAN module. If you fancy the challenge, there are plenty of modules out there with outstanding bugs. Or maybe there's a feature you'd like to add to one of the modules you use? In this post I'll outline the process I've used to adopt modules, then describe each step in more detail. Let me know how this can be improved.