in reply to Maintainer looking for a module

I'd think any maintainer might be somewhat leery of someone coming out of the blue asking to help with the maintenance of one of their modules. There's also the problem that if you just pick something at random now you might get bored with it n months down the road and then the module's back unloved again.

A better route might be to just do your work and find out what modules you are using regularly and then work on improving those (fix bugs, submit patches, etc). You'll be more likely to keep involved since it's your itch that you're helping to scratch.

Replies are listed 'Best First'.
Re^2: Maintainor looking for a module
by brian_d_foy (Abbot) on Nov 29, 2005 at 00:50 UTC

    You'd be wrong. I know plenty of maintainers (however you spell it), including myself, who accept help for people they don't know. All that matters is that they do good work or send in good patches.

    The modules that most people use regularly are already the modules that get a lot of attention and don't need that much help. If someone wants to work on their Perl chops, choosing a neglected module is a pretty safe and effective way to do it.

    --
    brian d foy <brian@stonehenge.com>
    Subscribe to The Perl Review