But the fact that the Perl troll army is after me because I rate my own module

Let me explain how I think of the cpanrating service, because I think that many perl monks and mongers share this view:

The cpanrating system is intended to give people a clue about whether to use a particular module, or rather look for alternatives. Since participation is sadly low, it significantly skews the picture of a module if the author itself rates it.

Most authors think their modules are good, which is why they wrote and published them, so the author's own review only adds new information in very few cases. If a module author wants to compare his module to other modules in the same area, it is a very good idea to include a section in the POD of the module, listing possible reasons for using this module over another, and maybe even the other way round.

As tinita wrote, you were told before that rating your own modules is bad style. Continuing to brag about it is even worse style, and explains a certain hostility that you might feel from other monks.

When I tell you there is a security hole somewhere you better believe me

As I wrote before, such critisms is best mentioned in form of a bug report, including a small piece of code that demonstrates a vulnerability. And if the author does not respond to security related bug reports after a reasonable amount of time, that's a good reason to write a negative review for that module.

but for every new Monk there is some amount of needless hazing to the new member

Beware of over-generalizations. In terms of temporal monestary usage I'm pretty young here, and I do remember my first time here. I experienced no hostility whatsoever.

Perl 6 - links to (nearly) everything that is Perl 6.

In reply to Re: Modules you build yourself = Your Child by moritz
in thread Modules you build yourself = Your Child by SFLEX

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.