I like #1. I don't like #2 or #3.

WRT #2: if the reasons are at all useful, it's likely people will simply pick whichever default comes closest and leave it at that, rather than spell out his concern. Though considering the valid reasons would probably be something like "Trolling / Excess profanity / Yes, there really is another reason to delete:" (last one for supplying a freeform reason), we might see less misconsidered nodes so I'd be all for it. *grin* For editing, preset reasons don't offer much either: most editing considerations seem to be for markup fixes and title changes. But in case of retitling, it is a good idea to propose a new title with the reason, so the dropdown would only contain "fix markup" which seems like a waste..

WRT #3: Most of the time, retitling requests already include a new title in the consideration reason. The only real change would be voting on edited content proposals, and I expect that will lead to occasionally having to keepvote against a bad proposition before someone else can reconsider with a better edit. In contrast, I trust the editors to do a good job of editing nodes that need fixing without trial and error. Voting for actual edits might have merit if it was felt that the editors are overburdened, but I don't see that.

Bunch of updates later: I hope this post is actually coherent now..

Makeshifts last the longest.


In reply to Re: Considering NTC and approval nodelet by Aristotle
in thread Considering NTC and approval nodelet by rinceWind

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



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.