Beefy Boxes and Bandwidth Generously Provided by pair Networks
Don't ask to ask, just ask
 
PerlMonks  

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

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



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others making s'mores by the fire in the courtyard of the Monastery: (5)
As of 2023-02-06 13:49 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?
    I prefer not to run the latest version of Perl because:







    Results (34 votes). Check out past polls.

    Notices?