What is meta? ×
Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 134 Stack Exchange communities.

I've seen a issue about reviews developing, and have finally found a good example.

On Stack Overflow we preach that posts are community-owned (to a point) and encourage collaborative editing of content. I have seen numerous times in the suggested edits review queue where I felt the editor edited too much extra into the answer, and rejected them. I just saw an instance here where an answer was updated with some more current information (to cover Iphone 5), and thought it was appropriate and approved it, but it was rejected by three others.

It seems like we need to be careful not to lose our proclivity for updating information.

I don't have any solution yet, just wanted to bring it up for discussion.

share|improve this question
1  
+1 I posted a very related question about this particular topic. –  AbZy Mar 4 '13 at 19:34
3  
This is an old concern. (Dupe, technically, but it's good to raise awareness now and then.) –  Gilles Mar 4 '13 at 21:50

2 Answers 2

Problems

  • There are many reviewers who don't know the proper way to review (at least, the effect of low quality reviewers is so grim that review audit has since been implemented and the number of reviews per suggested edit has to be increased).

    What is the proper way to review is also not plainly in sight. I am also not sure if there is any meta post describing in details the steps in a review process. Nevertheless, if you need to search for it, then there is even lower chance people are going to read it.

  • Reviewing for grammatical mistakes and formatting is easy. The knowledge necessary to review is low. We only need to have good English background and a bit of knowledge about the language syntax, plus Markdown.

    When I said it is "easy", it is easy compared to major changes (discussed below), but in no way I imply it is trivial work. There was one case where a spam link is slipped into the suggested edit, which requires people to pay attention to the Markdown diff.

  • Reviewing for major changes in the code and content is hard, since this requires as much research as the editor, or you must have the knowledge beforehand. It may also require intimate knowledge about the language or technology. Such major changes are sometimes result of an update to the technology, or to fix problems that was not commonly aware of in the past.

    The above are the 2 cases where major changes should be encouraged. In other cases, an answer might be applicable. However, between editing a highly-voted answer and write a new answer, the former will expose the new content more than the latter.

  • Currently, the review system trains people (like how you would train an agent in AI) how not to approve of garbage. But it does not train people to find gem.

    There are also ways to detect audit. There is a hole that allows userscript to detect with 100% accuracy and 0 false positive, at least 2 weeks ago - not sure whether the code has been changed. Disregarding the problem with the implementation for a moment, the "training system" may also train people to detect audit and avoid them.

  • The site is collaboratively edited. However, in reality, there exists a strong sense of ownership, since the post is tied to the reputation.

    The common suggestion is to leave a comment to the author to improve the post. It is a fair suggestion, and good etiquette. This assumes that the author is around, and is updated with the technology. From my experience, the assumption above is OK in most cases. However, in case it does not hold, important information is buried inside comment - a secondary citizen.

share|improve this answer

Improving is always welcome, but I think the issue in this particular question you mentioned might be the 'risk' of the edit being wrong.

Because the editor is not the original author, if the added information is not valid then the whole answer could turn invalid too. This could have been the reason behind the rejects.

I would probably suggest the new information in a comment, and let the OP of the answer decide whether it's better to add it or not.

share|improve this answer
    
There is even links in the edit summary! And there is a link to Apple's documentation! I think it should be approve if the information matches with the source. –  nhahtdh Mar 4 '13 at 19:49
    
@nhahtdh Agree, the sources weren't probably checked in this case. I was thinking more in general (in the lines of "what happens if there is no link or the link is an opinion?"). –  Yisela Mar 4 '13 at 20:03
1  
If you don't know whether the edit is correct, click “Skip”. –  Gilles Mar 4 '13 at 21:51
    
@Gilles, I agree, I often 'skip' edits if I don't have the technical knowledge to think it's right. –  Lance Roberts Mar 4 '13 at 21:55

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .