in reply to A couple of site changes

Very nice, hopefully it'll keep down "accidental deletes".

I was thinking a couple of changes to the interface would do the trick also:

  1. Change the vote buttons in Nodes to consider to a "Yea" and "Nay".
  2. Add a "Consider for delete" checkbox in Approval nodelet

This gets rid of the problem of people voting "delete" on nodes that have been considered for editing (some people seem to vote delete on everything). It also lets auto-delete work: if "consider for delete" is checked, and there are 5 "yea" and less than 2 (4?) "nay" votes, NodeReaper swings his scythe. Finally, an editor could remove the node from consideration if there were more than 4 "nay" votes.

I think that covers it. Have I overlooked something? I think the code changes aren't very big, but I could easily have overlooked something that makes this difficult and/or impossible. Guidance and comments welcome.

Replies are listed 'Best First'.
(tye)Re: A couple of site changes
by tye (Sage) on Sep 18, 2002 at 06:00 UTC

    No, if someone considers a node for 'delete', I still want to be able to say "yes, it sucks, but it'd be better to edit it than delete it". And I don't want someone trying to prevent deletion of a troll by considering it for "non delete" and thus requiring a bunch of "nay" votes and then unconsideration, etc. before it can be reaped.

    We have a design for selecting "consideration type" but it is more than just "delete/other" and was mostly thought up as a way to provide feedback because we were getting a lot of considerations that a lot of people felt strongly against and were spending a lot of effort to "fix" things and not getting anywhere. But footpad's best node seems to have made a huge improvement.

    I'd like to add a "consider it" checkbox so that it will look less like the chatterbox and typing "/msg paco Who are you?" w/o checking the box will get you a warning, not an invalid consideration (and disable "/msg ..." as a consideration reason) but I wanted the code for the two related nodelets merged before making more changes that would make merging more difficult.

    Oh, one of the enhancements in the "consideration type" design was a consideration type of "duplicate" which would require a node ID be entered into the reason field and would do some automated things to make dealing with duplicates go more smoothly. This still might be worth doing but it isn't as easy nor as important as some other things that I still don't have time to do, so I wouldn't hold my breath. (:

            - tye (but my friends call me "Tye")
Re(2): A couple of site changes
by FoxtrotUniform (Prior) on Sep 18, 2002 at 04:06 UTC

    Good call, VSarkiss.

    I like the idea of a specific "consider for delete" option, with unspecified considerations effectively asking for an edit. I don't notice it as much anymore, but there are still a fair number of ambiguous considerations, which I tend to vote "Keep" on only because of the ambiguity: the nodes might merit changing, but I'd hate for someone to think that I voted to delete an otherwise salvageable node....

    The only thing I'd add would be an "abstain" button, both in Nodes to consider and in general voting on nodes. This idea has been raised before, and I still like it....

    --
    F o x t r o t U n i f o r m
    Found a typo in this node? /msg me
    The hell with paco, vote for Erudil!