in reply to How to get Perlmonks to report bugs?

Nice idea, but if we implement it, you're just going to get your hopes up that much more, and be that much more disappointed. Look - we have a hard enough time just getting people to put [mod:// ] markup around module names!

My counter-proposal is education (yes, a training issue) — add some verbiage in the "how do I post effectively" section of the site docs saying "if you have complaints/requests about a CPAN module, please consider opening an RT ticket", and so on.

A word spoken in Mind will reach its own level, in the objective world, by its own weight

Replies are listed 'Best First'.
Re^2: How to get Perlmonks to report bugs?
by CountZero (Bishop) on Aug 01, 2007 at 06:47 UTC
    [mod:// ] around module names? I always use [cpan:// ]. Is there any difference?

    DBIx::Class or DBIx::Class

    Ah, now I see, [mod:// ] brings you straight to the module's documentation page and [cpan:// ] goes to the search result page!

    CountZero

    A program should be light and agile, its subroutines connected like a string of pearls. The spirit and intent of the program should be retained throughout. There should be neither too little or too much, neither needless loops nor useless variables, neither lack of structure nor overwhelming rigidity." - The Tao of Programming, 4.1 - Geoffrey James

[reply]
[d/l]
[select]

In Section Perl Monks Discussion