The term 'Perl community' is bandied about, but it's not always clear what it means, or the scope of it. I'm not going to try and nail it down, just talk about one aspect. When working on a new module, three different people helped me within 24 hours or so, and that felt good.
When I created the first version of the
dzil kwalitee command,
I ended up calling
cpants_lint.pl. I emailed ISHIGAKI,
telling him what I was trying to do, and suggesting the code for it could
be factored into a module. And I would submit a pull request for the change,
if he was happy with the idea. He was, and he made the change himself,
Within hours of releasing the first version of my dist, I had a pull request from ETHER (most authors have probably had one of those :-), to add a link to SEE ALSO. I'm a big believer in having good SEE ALSO coverage, so I was happy to get this. Having a good SEE ALSO section in your doc helps people discover more of CPAN.
And just a couple of hours later I had another pull request, from DOLMEN.
He pointed out that every time you run
Dist::Zilla::App::Command::* plugins are loaded.
So each plugin should minimise the number of additional
modules loaded at compile time, requiring them as and when they're needed.
A nice small PR, which also taught me something. And the third release on
the first day!
This gave me warm fuzzies towards the community, which made me realize that this sort of interaction would be great for new contributors to CPAN. Something to add to my buddy idea, if I ever get round to finishing it...comments powered by Disqus