I am amazed at the role that semantics are playing in this discussion. What if BrowserUK had used the phrase “General Discussion” instead? And I had no idea how insecure some of us are. Would creating a general discussion section really turn us into Slashdot? Do we really expect Ruby and Python questions to usurp the Monastery?

If it does not take too much work to create a new section perhaps we should just give it a try and see what actually happens? Maybe I am wrong but I think that our sense of community is strong enough that the benefits would outweigh the negatives. Down voting seemed to work when plagiarism reared its ugly head so why couldn’t it work here to keep things in check? And think about all those "mark off-topic" considerations that could become "move to" considerations instead! Heck, it might actually help discourage off-topic questions!

In keeping with interesting names I would like to suggest we call it “Life, the Universe, and Everything”. It should not be possible to frontpage nodes in this section and by default nodes should not be included in searches and super searches. I would also suggest we give things a try before we decide whether aging out older nodes is appropriate or not.

In reply to Re: An OT section (again). by Argel
in thread An OT section (again). by BrowserUk

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.