Beefy Boxes and Bandwidth Generously Provided by pair Networks
Pathologically Eclectic Rubbish Lister

comment on

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

Thanks for the opposing opinion. I included the reasons behind my opinion in hopes of either hearing opposing reasons or pursuading those with opposing opinions.

I also noted that it appears that there are quite a few monks on both sides of this spectrum. So I don't think it makes much sense to leave the issue unresolved such that we have lots of monks posting nodes to the section they think makes sense, lots of other monks considering the nodes, then lots of monks voting both ways on consideration such that we spend lots of time "fighting" over the same issue over and over and the result is nodes somewhat randomly distributed between the two sections (and sometimes getting considered/moved more than once).

I was hoping that some level of consensus might come out of this and tons of future consideration noise could be avoided. I'm not so much concerned with what section nodes end up in. I'm concerned with there being a whole class of nodes that appear to get considered and moved often with lots of members on each side of the issue.

(this part is also in reply to mirod's reply) I support not sweating the section much when the choice is not obvious, giving more weight to where the original author chose. But I also see that people often don't deal well with not being able to do something. The sections have some value (or else we should just get rid of them) so people will notice when nodes seem, to them, to be in the wrong section and often the best outcome can be had by letting people do something about it (consider it, vote on the consideration). I'd encourage people to not sweat the tough cases. And if a consideration gets a fairly even vote, then I'll usually unconsider it without moving it.

And I encourage level 6-10 monks and editors to be somewhat reluctant to move nodes when the final destination isn't clear.

But I think this particular class of nodes (nodes primarilly about the PM site but not primarilly about technical or policy issues) deserves to be explicitly addressed if possible to just avoid the continued noise. I think that is possible and beneficial.

                - tye

In reply to Re^2: Are "PM Discussions" only to be technical? (reason) by tye
in thread Are "PM Discussions" only to be technical? by tye

Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":

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

What's my password?
Create A New User
Domain Nodelet?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others musing on the Monastery: (6)
As of 2023-12-03 17:55 GMT
Find Nodes?
    Voting Booth?
    What's your preferred 'use VERSION' for new CPAN modules in 2023?

    Results (20 votes). Check out past polls.