Considerations can be either delete requests or edit requests. They can never be both. In that case, why allow approvers to vote 'delete' against an edit request, or 'edit' against a delete request?

For the simple reason that Consideration is "first consideration comment in wins". If someone submits a comment to the effect that a node should be deleted for no Perl content, but I look at it and decide that the node doesn't need to be deleted, but does need a formatting edit, I want to vote to that effect, rather than waiting some indeterminant time for the delete vote to settle, so that I can reconsider the node with a "this needs an edit" comment. If enough people agree with one side or the other, it'll be reflected in the vote.

For edit reqests, why not get the approver to do the changes and submit his/her edit for approval? This could be displayed in NTC in its raw pre-markup form, either with changes highlighted, or as a diff listing.

This could lead to gridlock. It assumes that the approver agrees that the edits need to be done. Our current system, where an editor volunteers to make the fix, works fine.

In reply to Re: Considering NTC and approval nodelet by dws
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.