I agree that requiring a login to report a bug is a pain. Reporting via e-mail is a different kind of pain. PerlMonks could get an RT login and provide a link for "submit this thread as an RT bug report" that would prompt for a distribution name and text to go in the bug report below the boiler-plate text + link to the thread in question. Then some vetting would be required to prevent duplicates or invalid submissions. Perhaps just require some PerlMonks-cabal-subset-member approval for the submission to be sent (which would post a reply noting this submission and linking to the generated bug).
Heh, perhaps we should just have an e-mail-based RT/PerlMonks gateway server similar to the usenet gateway theorbtwo wrote (only for selected and vetted threads, of course).
Well, I'm not going to write any of this so it'd require a pmdevil's dedication to make it happen so I won't hold my breath, but I like the idea. :)
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Outside of code tags, you may need to use entities for some characters:
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
|
|
