Beefy Boxes and Bandwidth Generously Provided by pair Networks
Perl-Sensitive Sunglasses

Comment on

( #3333=superdoc: print w/replies, xml ) Need Help??
The more I think about it, the more accurate I think I was in Re^8: swissprot assignment (effort) (i.e. less due diligence when a reason is given). Especially for Nodes to consider, where drilling down to perform due diligence is discouraged by the slowness of the site. I lost interest in Nodes to Consider several years ago because many successful edit considerations to fix typos, re-title, restore contents of a node, etc. were never followed with the actual edit. No doubt because of the small number of members with the privileges to edit someone else's node (understandable since they are volunteers). As a side note, the jargon used is not exactly intuitive to new users either, though when I brought that up several years ago there was little interest in changing that.

It might be useful to split "edit" into "move" and "edit", and maybe have a different consideration page for the edits or create a preference setting to show edit considerations or not. This would reduce Nodes to Consider to those that are actionable, which might increase interest -- i.e. less clutter and one's vote matters more. This assumes that e.g. move votes are automated in some way (maybe require 5 votes). That is, that a successful consideration is always carried out.

For actual edits, you could open it up to more monks. Though to prevent abuse, there would have to be a review process, e.g. randomly pick a few edited nodes, show the before and after, and let monks vote on whether the edits were good or not.

Unfortunately, Consideration is in some ways broken just because of the disincentives (slow site, successful edit considerations are not always acted upon) and I am not sure how much can realistically be done about that. :(

Elda Taluta; Sarks Sark; Ark Arks
My deviantART gallery

In reply to Re^8: swissprot assignment (effort) by Argel
in thread swissprot assignment by faten daim

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
    [ovedpo15]: Asking for the wisdom of Perl Monks in the following question about JSON module:
    [ovedpo15]: http://www. node_id=1213478
    [LanX]: it's considered spamming to advertise threads here
    [LanX]: just wait

    How do I use this? | Other CB clients
    Other Users?
    Others drinking their drinks and smoking their pipes about the Monastery: (7)
    As of 2018-04-24 15:32 GMT
    Find Nodes?
      Voting Booth?