Update: It appears that the consensus of those I was hoping would be part of this list is that the list is a "Bad Idea"(tm). I therefore withdraw the idea. Downvote this node, if you like, but please note that I now would not support this idea. It, like so many other ideas, looked good on paper. But, as always, the devil is in the details.

Now, I know that this topic was discussed a few years back, but I also know nothing came of it. So, I'd like to propose the following system:

  1. (Where "monk" appears below, that means any member of PM of level 2 or higher.)
  2. For a monk to become a mentor, that monk must be nominated by one monk and seconded by another.
  3. The nomination will be for a specific field of expertise. Some example fields of expertise (with an example monk I would nominate in that category):
  4. That monk is now available to be voted on. Once that monk receives five other votes, then that monk is offered the opportunity to become a mentor.
  5. That monk must then accept. (This is because some monks may not want their name advertised as an expert in some field.)
  6. This list would be maintained in PM. The page would be accessible from the following places:
    • The links section
    • Q & A
    • SOPW
  7. The list of categories would be relatively static. Anyone can propose a change to the categories and the change would occur by popular acclamation.
  8. The voting could either be something built within PM or by /msg to a group of volunteers. I, of course, volunteer for this duty. (I'm not going to talk without being willing to walk.)
  9. At any time, a monk can choose to remove themselves from any mentoring list.
  10. At any time, a monk can be recalled. The recall process is identical to the process of making a monk into a mentor.

I would propose the initial list of categories to be:

------
We are the carpenters and bricklayers of the Information Age.

The idea is a little like C++ templates, except not quite so brain-meltingly complicated. -- TheDamian, Exegesis 6

... strings and arrays will suffice. As they are easily available as native data types in any sane language, ... - blokhead, speaking on evolutionary algorithms

Please remember that I'm crufty and crochety. All opinions are purely mine and all code is untested, unless otherwise specified.

In reply to A PerlMonks mentoring list by dragonchild

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.