My question ( yes, I actually have one ) is whether or not members of the monastery believe my code is useful enough for me to apply for CPAN id and open a module and start maintaining this.

Please don't get the impression CPAN only hosts quality code, or that it only should host quality code. The only requirement for code to live on CPAN is that it should be freely distributable.

Don't let your decision whether to upload or not depend on what a handful of people here will say. Perlmonks isn't CPAN, and CPAN isn't perlmonks. I'd say, upload it to CPAN if you are satisfied with it, and then just let history run its course. If people like it, they'll use it. If they don't, you might get suggestions for improvement, but if not, then it's just taking up a bit of diskspace.

Abigail


In reply to Re: Submit fork-control module to CPAN? by Abigail-II
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.