Beefy Boxes and Bandwidth Generously Provided by pair Networks
Perl: the Markov chain saw
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
I quite dislike a knee-jerk gainsaying of "that is not Perl related, go away". I don't mind a well-considered comment noting that a question is far enough afield from Perl that one might get a better or faster answer elsewhere [...]
I think a better approach would be rooting out places in the site UI and documentation that give topic purists encouragement and making sure there is a site document clearly spelling out that "topics related to working with Perl are welcome", at least as a starting point.

I agree with everything you said, but especially with these two points. Considering the generally helpful and open attitude here, I'm frankly puzzled sometimes by the rudeness (usually posted anonymously) that's shown toward newcomers who appear to be honestly ignorant of how Perl-unrelated their problems are, especially as contrasted with the tolerance that's shown toward some other kinds of posts. But in any case, there seem to be plenty of topic monitors to prevent the site from taking off into endless threads about politics and favorite spaghetti recipes.

I use RSS to keep up with new posts, so the "schema" is meaningless to me; there could be one big category or a hundred little ones and I wouldn't notice. So from that perspective, the question isn't whether there should be an off-topic area, but whether off-topic posts should be censored as harshly as they have been so far.

There are two very different kinds of off-topic posts that we could be talking about (not counting obvious spam and attacks):

  • A newbie has been programming for a month and was tossed into a task involving Perl, Javascript, HTML, Apache control files, and possibly a couple of other things, and he has no idea where the problem lies. He thinks (or hopes) he's on-topic, but he isn't. There are two possible responses (other than being a jerk):

    1. Politely tell him his problem isn't with Perl, so he'll need to go elsewhere. Point him in the right direction if it's not much trouble.

    2. Allow the post and try to help him with his non-Perl problem if you can.

    Those are both reasonable; which a forum follows is just a matter of policy. The policy could even be left open to each member's discretion: help them if you want, point them somewhere else if you want, but otherwise ignore them.

  • The regulars have gotten to know each other and formed friendships and learned to respect each other's knowledge beyond Perl, and they'd like to talk to each other about non-Perl topics. This is common on long-standing forums that don't have strict topical requirements. It's not a question of right or wrong, but simply what the people in charge of the forum (the members, if it's a democracy) want the forum to be like. There are three main places they can draw the line:

    1. Censor it all.

    2. Allow anything.

    3. Censor it somewhat -- in this case perhaps to topics only a step or two away from Perl, like installing an operating system or dealing with a difficult boss at your programming job.

    #2 here is almost certainly a bad idea. #3 seems most reasonable to me, and not too hard to define. There would always be the option of going back to #1 if it doesn't go well.

Aaron B.
Available for small or large Perl jobs and *nix system administration; see my home node.


In reply to Re^2: [OT] How about an Off Topic Section? (take my meds... please) by aaron_baugher
in thread [OT] How about an Off Topic Section? by flexvault

Title:
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?
Username:
Password:

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

How do I use this?Last hourOther CB clients
Other Users?
Others meditating upon the Monastery: (3)
As of 2024-04-25 05:13 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found