Tutorials can be considered to be moved away from that section, and get moved by editors if need be.

I believe you mean well by your proposal, but I am afraid that this could be unrealistic.

I tested your statement yesterday. I considered this would-be tutorial for moving to Meditations, because it is clear from its reputation (it was negative when I considered) and from the comments added by knowledgeable monks, that the proposal had several serious flaws.

There is no consensus in the consideration, though. 6 people voted for keeping it, and the reasons why someone would want to keep a flawed (and possibly misleading) document as a tutorial is really beyond me.

I may make some assumptions to explain that. I may assume that people don't bother reading the comments, and from my request it just seemed that I was a snotty SOB who wanted to punish a tutorial that I didn't like. I may assume that people here don't like censoring, and this kind of node moving may sound like censoring, therefore the naturally kind monks voted for keeping.

This is just some more food for your thoughts. Please take it into consideration when cooking the final solution.

In reply to Re^2: Rethinking Tutorials by dbwiz
in thread Rethinking Tutorials by gmax

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.