Should I just send an e-mail to the maintainer address listed in the module documentation

That's a good way to start, particularly if you're thinking about doing a good deal of work and if you might be annoyed if you did the work and found that it wasn't accepted. Also, some authors keep a source code repository and may be willing to give you access. Even if they don't, it might be helpful to know if they prefer to get patches against current code or a complete tarball of changes.

You can also submit patches via the RT bug tracker -- this makes your work visible to others, which is often handy for bug-fixes where the maintainer is slow to apply submitted patches.

As a minor note -- if you're working with someone's code, it's a good idea to try to match their style, space vs. tab preference and so on. If they use Perl::Tidy or Perl::Critic they may be able to share their settings with you.

-xdg

Code written by xdg and posted on PerlMonks is public domain. It is provided as is with no warranties, express or implied, of any kind. Posted code may not have been tested. Use of posted code is at your own risk.

In reply to Re: Best practice for contributing to CPAN modules. by xdg
in thread Best practice for contributing to CPAN modules. by Pic

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.