The idea is excellent - however, I would suggest this not be distributed by mail. Rather, ideally it would be posted in a special area on this site only editors have access to.

My exact proposition, not knowing how much work it would entail to implement, is as follows: there'd be a "PM Weekly" link at the top, the node it leads to would be locked to replies, and would of course come with links to the previous and (if you're reading an old issue) the next PM Weekly, plus the archive which lists all issues.

The newest PM Weekly issue in progress is almost a regular node, but with the following features: Only the chief editor can post one. It starts life as a node hidden to non-editors - the editors can read it and reply to it (presumably posting a link to a node along with a comment, but also commenting on each other's posts). The editors can vote on submissions simply by using the voting system of PM. The chief editor can view the node sorted by votes of the 1st level replies (so at the end of the week when he edits the toplevel node he doesn't have to manually sort the submissions). He also has a "Publish" button: it locks the node to further replying, makes it world-viewable, sorts the 1st level replies by votes, points the link at the top of PM to this issue, places it in the archive, and sends a /msg to all users who asked for it in their settings.

As far as I can tell, it's the most flexible mechanism and the only new feature it requires is the chief editor's Publish button, otherwise it only uses mechanisms that already are in place. Editors can comment on each other's posts, allowing for (literally) editorial content. You can see who submitted which node, and how many votes the submission got.

---

---

• 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.