- The official PAUSE guide to taking over a module.
- Identifying CPAN modules that need help
In the comments to the latter one, Neil Bowers describes his own procedure, which is the one I used:
- Find and solve a problem with a module. (This is sometimes the hard part.)
- Post a patch to RT.
- Fork the module on Github (this is a little pie-in-the-sky, so put the module on Github, the point being to have an open repository you can refer to)
- Don't forget to update the repo with meta-information to point to itself. (I didn't do this for Iterator::Simple, durr.) More Github integration is a benefit to everyone.
- Two weeks after this, email the author at whatever email addresses you can find, remind him or her of the patch, point to the Github repo, and offer to take over co-maint. Copy modules@perl.org on this email.
- One month after that, notify PAUSE that you haven't heard back.
- Wrap and upload your new version.
Wash, rinse, repeat: slow but certain world domination.
No comments:
Post a Comment