Beefy Boxes and Bandwidth Generously Provided by pair Networks
P is for Practical

Comment on

( #3333=superdoc: print w/replies, xml ) Need Help??
My big concern is accountability -- not that I don't trust fellow editors, just that I believe it is of paramount importance.

In terms of the technical and social approach to implementing checks and balances on the editing process, I would like to see something along the lines of the following.

  • The node should go "live" immediately on editing
  • If a person's node is edited, they should be autonotified in the chatterbox.
  • If the author feels that the editing has been done in error or with no regard for content/intent, there should be an option easily accessible from that node called "Petition to Restore".
  • When a petition is made (and I imagine this will be quite rare, since the vast majority of edits are due to the newness of the user), at most ONE editor should be required to approve it in order for the node to be restored to its original glory.
    • Point: The original intentions of the poster ought to be given a great deal more weight than the wishes, however well-intentioned, of the editors.
    • Effect: Edits would be essentially an assumed unanimous agreement by the editors group. For a petition to be denied (and an edit permanent), every editor must deny it
    • Why "petition" and not just "restore"? Users who have not bothered to figure out the correct tags to wrap code in will also not bother to figure out what the "Petition to Restore Node" button does before clicking it. And since there will be users that will click it without useful intent, the hard work of the editors should be protected at a minimum level.

It should also be noted somewhere which editor is responsible for changed nodes as well, so that they may be queried as to the logic behind the changes.

That is all I have thought of at the moment.

Update: I should clarify my assumption that for any of the above to work, node-level locking is a required technology. Thanks tye!

e-mail neshura

In reply to Re: New site editors by neshura
in thread New site editors by vroom

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, 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, 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.
  • Log In?

    What's my password?
    Create A New User
    and all is quiet...

    How do I use this? | Other CB clients
    Other Users?
    Others wandering the Monastery: (4)
    As of 2018-02-26 04:33 GMT
    Find Nodes?
      Voting Booth?
      When it is dark outside I am happiest to see ...

      Results (316 votes). Check out past polls.