Others have pointed you to Neil Bowers' Pull Request Challenge, and that's an excellent suggestion. But another way to do it (the way I've done it), is to use CPAN modules. As you use them, read their documentation, and so on, you may well discover some issues that could be improved upon. Get in touch with the author; github pull requests, email, whatever. Before you know it, you could be submitting patches to the module, or even added as a co-maintainer.
One typically doesn't just set out to find a module to contribute to; that's hard. But it's easy to discover rough edges when using modules, and from there the natural progression is to start finding ways to fix those rough edges.
In reply to Re: How to find a module to contribute to
by davido
in thread How to find a module to contribute to
by stevieb
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |