Beefy Boxes and Bandwidth Generously Provided by pair Networks
There's more than one way to do things

Re: How do janitors get fired?

by ptum (Priest)
on Jan 10, 2007 at 16:48 UTC ( #593945=note: print w/replies, xml ) Need Help??

in reply to How do janitors get fired?

I upvoted this node, not because I think janitors need to be fired, but because it raises an interesting question. Presumably the gods decide such things, but I have noticed that the list of nodes for consideration is growing lately and several nodes languish un-janitored with a large number of edit votes having been cast. Perhaps we need to recruit some more janitors?

Replies are listed 'Best First'.
Re^2: How do janitors get fired?
by davido (Cardinal) on Jan 10, 2007 at 16:58 UTC

    Your question differs from the topic addressed by the original poster in this thread. But I'll respond to it here too.

    It's not an issue of how many janitors we have, but rather a slight shift in our attitude. Generally speaking, we feel that it's better to wait awhile before unconsidering nodes so that they don't get reconsidered for the same thing by someone who missed seeing the first consideration (this is in regards to nodes where we have opted not to act upon the node itself). We also are trying harder to minimize our impact. We want to reserve action for nodes that really need work, leaving minor issues alone if they don't present a hazard to navigation or seriously hamper readability.

    Some considerations will sit for a long time and may not get implemented. This doesn't mean we won't work quickly to fix a code tag issue, but for some things we just want to be more thoughtful.

    We're also trying to be more considerate of authors by asking them to make their own fixes when practical, and when they can do so in a timely fashion. That way they'll become more familiar with the way things work around here, and we won't keep seeing their nodes getting considered for the same sorts of problems.


      It certainly seems a good thing to educate node authors (and Friars) on what kind of node errors should be fixed or considered, since our janitors are unpaid and the perks associated with the job seem minimal. I wonder, though, at the effectiveness of leaving nodes un-janitored to avoid re-consideration ... wouldn't it be better to simply display the consideration history for a node so that people could see it had already been considered and un-considered?

      Hmmm. Looks like something along these lines (RFC: a nodetype for considerations) has been discussed recently ... did any change to the site come of that discussion?

        I'm told a moderation history is in the works. Leaving the consideration open for awhile is still a tool of the janitors. Haste isn't always in the site's best interest.


Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://593945]
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others taking refuge in the Monastery: (7)
As of 2021-03-05 11:15 GMT
Find Nodes?
    Voting Booth?
    My favorite kind of desktop background is:

    Results (109 votes). Check out past polls.