Beefy Boxes and Bandwidth Generously Provided by pair Networks
"be consistent"
 
PerlMonks  

Re: Enforcing unreap

by yitzchak (Sexton)
on Sep 28, 2005 at 02:33 UTC ( #495606=note: print w/ replies, xml ) Need Help??


in reply to Enforcing unreap

I would rather see effort spent toward allowing votes by three janitors to force reap or unreap a node, similar to the no longer available three-janitor nuke.

Or in testing castaway's consideration changes that have languished so long.


Comment on Re: Enforcing unreap
Replies are listed 'Best First'.
Re^2: Enforcing unreap
by Arunbear (Parson) on Sep 29, 2005 at 20:38 UTC
    There is aleady editor_vote - (patch) that would enable janitorial reaping as you've described. What I'm trying to point out is that unreap on its own doesn't do much good unless there is a way to make it stick.

    Another idea that occurs to me is that whenever a reaped node is unreaped, we would record that in an unreaped table. Then we make a superdoc that shows any nodes in reapednode that were once unreaped, so janitors can unreap again.

    What do you think?
Re^2: Enforcing unreap
by castaway (Parson) on Sep 29, 2005 at 20:44 UTC
    Yes, me too ;)

    My changes don't address this particular problem.. But it would be nice to get them in, since I was planning follow-up ones to the actual consideration system. (The current ones are more moderation/approval ones).

    C.

Log In?
Username:
Password:

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

How do I use this? | Other CB clients
Other Users?
Others rifling through the Monastery: (15)
As of 2015-07-31 21:13 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    The top three priorities of my open tasks are (in descending order of likelihood to be worked on) ...









    Results (282 votes), past polls