Beefy Boxes and Bandwidth Generously Provided by pair Networks
Perl-Sensitive Sunglasses

Comment on

( #3333=superdoc: print w/replies, xml ) Need Help??

I somewhat agree. The main reason to not put stuff on the front page is length. This just means that <READMORE> needs to be inserted before it goes to the front page. An automated way of inserting such would be nice but I won't hold my breath nor jump up and down hoping for such.

The second reason to not frontpage is things like uninteresting repeats. But I think we should frontpage most approved articles these days because of the points you raise about the implications of the recent stats.

Another option would be to make it clear on the front page that only "Selected New Questions" are listed and that you can go to "See All New Questions" for more. Hmm, I think I'd vote for that change and keep the frontpage approval process the same. YMMV. I'd probably also add a See All New Nodes link on the front page (besides the differently labeled ones already there).

I'm somewhat for changing the "approval for a section" methodology. We've had problems with nodes not getting approved for their section when they should. Also, I'd like to give people a way to "vent" about a "poor" question w/o running to Nodes to Consider. So I'd like people to be able to vote "unapprove" on nodes. Though handling both whether or not to approve and whether to move something to a new section makes an eligant solution more difficult.

One idea I have is to have the approval nodelet let you select "approve" or "unapprove" and/or select a section and these just get tallied as votes. Posting an article to SoPW counts as 1/2 vote for "approve" and 1/2 vote for "SoPW". To change sections, a different section would need to get more votes. To change approval, the other approval option would require more votes.

        - tye (but my friends call me "Tye")

In reply to (tye)Re: Let the doors open wide! by tye
in thread Let the doors open wide! by theorbtwo

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, 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, 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.
  • Log In?

    What's my password?
    Create A New User
    and all is quiet...

    How do I use this? | Other CB clients
    Other Users?
    Others avoiding work at the Monastery: (4)
    As of 2018-06-23 23:46 GMT
    Find Nodes?
      Voting Booth?
      Should cpanminus be part of the standard Perl release?

      Results (126 votes). Check out past polls.