That's a good one. But other than the list, I would think that communities like this one would be good places to float suggestions for new modules.

The traditional way to find an unmet need is to have a continually annoying problem yourself. I've trained myself, over the years, to go looking for solutions to such problems on the net, before attempting to write my own code. If I don't find a solution, then I generally try to adapt one that is more or less near to addressing my problem. If I can't find anything even close, then I sit down and have a good cry. But I also realize that there's an opportunity at hand to bring succor and enlightenment to a troubled world, and maybe get someone to help write my solution.

Usually by then the problem has gone away. But if it hasn't, then I try to fix it myself. That usually results in some Perl code. If that isn't too embarrassing to see the light of day, I sometimes publish it. (That is, of course, a link to my most successful Open Source project. Um, well, my only successful Open Source project. The point is still valid. Really. Trust me.)

"Even if you are on the right track, you'll get run over if you just sit there." - Will Rogers

In reply to Re: CPAN module writer connection? by hbo
in thread CPAN module writer connection? by tomazos

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.