I don't think it's a really hot idea. Sure patches get taken up slowly, but I think that's because of a) problems with the patch mechanism, and b) not all patches are a great idea.
I don't think patches should automatically be approved. This overextends the boundaries of what pmdev is here for. We are here to provide suggestions, and patches, to spot bugs, etc. Making us a 1/5th god doesn't really make it the right idea.
A better idea might be to add commenting to patches so that they can be discussed, rather than the dogpile method in the wikis. Any god can just make a change (you don't need two or whatever). If we want to throw our two cents in under a patch to say "yeah I tested this" or "this idea sucks", then that might be more organized, than some kind of automatic approval system.
The security problems inherent there would make me itchy. Or are you talking about "needs 5 votes to be presented for application"?
--
jaybonci
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.