Firstly, good for you! Code contributions such as this are what keeps the whole open-source ecosystem running.

I have done that 'to do' and tested it and it works.

Also very good. When you say you "tested it" do you mean you wrote a test script? That would be ideal - module authors love code contributions which come along with their own test script too.

There's no Pull Request system like with a Git repo?

No, there is not. What there is is https://rt.cpan.org/ where you can submit your patch and test script so that not only does the module author get to see it but all the co-maintainers (if there are any) will also be alerted to it. If the author (or principal maintainer if different) is indisposed it means that your contribution will still receive attention. It also means that anyone else who spots the "to do" section could find your contribution there even if it has not yet been merged into the distribution.

Some modules are additionally on other distributed code platforms such as GitHub, GitLab, BitBucket, etc. and if the module is one of those you could also go that route with your contribution.

If you would care to say which module you are talking about then we would be better placed to provide specific advice.

🦛

In reply to Re: I made a small but useful improvement to a module … now what? by hippo
in thread I made a small but useful improvement to a module … now what? by LittleJack

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.