Thanks for posting this.

> I'm constantly torn between what is right for
> Perl and what is right for everything else.

For the original monks this was the answer.

However consider also that this organization has stayed as faithful as it could and achieved only local and intermittent success and that this organization has from time to time compromised and achived more global success

>How then, should commercial scripts be reviewed?

Well, you could refuse to post scripts that haven't been reviewed.

Alternately you could charge $50 per year to list scripts that can't be reviewed and mark those links as advertising.

>The hard part about this is what should be charged
>for a personal code review?

Maybe nothing. I've learned by reviewing scripts here and by reading people's review's of my reviews. I can justify the time to myself. (Arguably my review time is not worth paying for)

You could probably post 1-3 scripts a week here for review...

People could ++ the node if they thought it worth distribution and -- if not.

>Use strict and warnings (or know/explain why they are not)
>Should use CGI.pm

A couple regex's would probably test for this pretty quickly.

There is probably other simple QA code that could help you quickly winnow through the 90% ....

>Should perlguru simply point to perlmonks and those sites instead?

Yes, you should feed strength.

One question you might ask yourself is:

If my forums should be phased out because they are not as rigorous as perlmonks, Are my script archives as rigorous as CPAN?"

It wouldn't be hard to argue that your site fills a niche that CPAN does not. It is not for me to make the case.

If you are looking to increase quality, you might look at CPAN's methods...

Other questions you might ask yourself are:

“If I take the site down will people wind up writing their own even more insecure and crappy scripts?”

"Are insecure and crappy scripts better than no scripts at all?"

In reply to Re: Re: Should it live or die? by social_mandog
in thread Should it live or die? by Jazz

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.