Editor-B is the person who never actually submitted it, and the [Edit History] wouldn't need to reflect that he even tried. It could, for collision statistics (!), but it wouldn't be required.

5 minutes is, of course, arbitrary. It's plenty to change a simple spelling, worse if you're doing heavy duty reformatting. I'm not really fond of this idea, but one could add a box that would allow you to enter the expected number of minutes you think it might take you to edit it. But that's yucky.

Of course, none of these nodes are critical to national security, so if someone does start an edit, and the system timer is 30 minutes, it just means that it'll be about 30 minutes until the next person can edit it. I don't see that as a major issue.

And as far as /msg'ing the original author that his node has been edited, I don't know how I feel about that. I imagine it would be easy enough for vroom to add that, but I don't know if it's necessary. Perhaps YACB (Yet Another Check Box) to make that an option. If someone is fixing code tags, I don't see where the author needs to know about it, since s/he probably wasn't smart enough in the first place. On the other hand, if you're deleting socially questionable comments, the author has more of a right to know. I'm indifferent, at least until I see how it goes.

I'm sort of the mind that the [Edit History] should be public, so that non-editors can make a sport of checking out nodes that have been edited, and then start a whole list of threads to be edited by complaining about the ones that have been edited...

--Chris

e-mail jcwren

In reply to (jcwren) Re: (3) Best way to handle locking of nodes being edited? by jcwren
in thread Best way to handle locking of nodes being edited? by tye

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.