You may find How to make a CPAN Module Distribution and the links of use. I personally find the makemanifest.pl wiidget very handy for crating a clean distro.

The one glaring omission that I see is NO DOCUMENTATION. A module is worth using because it WORKS and is EASY TO USE. If I have to RTFS to work out how to use it.... Many modules on CPAN suffer from this flaw BTW. Especially a number of core ones. I use a number of say URI and LWP idioms that work fine but are essentially completely undocumented outside of RTFS. Generally I found them because merlyn or some other programmer has demonstratated them. Bad docs are also discouraging, especially code snippets that don't work as advertised, not naming any names.

The other important thing is tests. You code will probably have some issues. Fixing one may lead to another. When you release version 2 it is good for you to know it passes all the tests for version 1. It is however potentially vital to your end users. See Autogenerate Test Scripts for a handy widget.

And as Abigail-II says upload it and see what people think.

cheers

tachyon

s&&rsenoyhcatreve&&&s&n.+t&"$'$`$\"$\&"&ee&&y&srve&&d&&print

In reply to Re: Submit fork-control module to CPAN? by tachyon
in thread Submit fork-control module to CPAN? by reyjrar

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.