Re: How to find a module to contribute to

write tests

... the only thing authors hate more than writing documentation.

You can see the test coverage results of some modules at: cpancover.com: new web site for CPAN code coverage. Modules with lots of red (especially 0.00) need tests. Unfortunately, a very small percentage of all CPAN modules have results because people need to request to add a module to the list.

Comment on Re: How to find a module to contribute to

Replies are listed 'Best First'.
Re^2: How to find a module to contribute to by 1nickt (Canon) on Jul 08, 2015 at 14:46 UTC
Would be cool if CPAN didn't accept dists without comprehensive docs and tests. Or at least, if there were a "top tier" of dists that meet such a criterion. Or that a dist could be relegated to a "second tier" by being downvoted ... not removed, but somehow flagged. You can always look at the bugtracker, but if a module has no docs and no tests, why should I spend my time writing a bug report? I'd be happy to downvote it, though ... Remember: Ne dederis in spiritu molere illegitimi!	[reply] [d/l]
Re^3: How to find a module to contribute to by hippo (Archbishop) on Jul 08, 2015 at 16:02 UTC
That is (partly) why CPAN Ratings exists.	[reply]
Re^3: How to find a module to contribute to by Ea (Chaplain) on Jul 10, 2015 at 09:12 UTC
Remember CPAN was born in the time of archie, gopher and WAIS, so it was a good way to distribute alpha code or to explore an idea and it may still be providing that function when github decides to charge for all repositories in 2025. That said, the ratings, reviews, etc mentioned above are the minimum necessary for selecting the module for your needs. I've been having a look at numerical modules and, at over 500, it's a bit of a chore just to figure out what each one does in order to classify it. Sometimes I can think of 6 impossible LDAP attributes before breakfast.	[reply]
A reply falls below the community's threshold of quality. You may see it by logging in.