If I understand jjhorner right, I agree wholeheartedly:
Gaining XP by voting (and being voted on) appears to work very well to encourage positive participation.
What may be needed is a mechanism to prevent an intermediate-at-best Perler like myself from advancing to Friar, Bishop or such just by being a reasonably well behaved Monk for a long time. Make me advance in my coding ability if I want to advance as a Monk.
- XP could still work as it does now.
- When XP earned to advance level, Monk must author documentation that benefits PM before gaining new level.
- Alternate methods of demonstrating Perl expertise are also possible.
- Monk earns no further XP until doc presented and approved by group of high-level Monks.
- Monk could be pre-emptive by presenting doc before XP earned, but only for the next level.
- Review process might begin at Monk (5) level.
Having said that, I still have questions or concerns:
- how would the review board be selected?
- how could plaguerism be prevented?
- retroactive or not?
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
