Misplaced Pages

This is an old revision of this page, as edited by JohnBlackburne (talk | contribs) at 18:10, 17 March 2012 (rm pre-emptively added categories: discussion ongoing and no consensus that it's a guideline yet). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

The following is a proposed Misplaced Pages policy, guideline, or process. The proposal may still be in development, under discussion, or in the process of gathering consensus for adoption.

This page in a nutshell: A good argument for rejecting a proposed contribution should go beyond linking a policy or guideline page to include a considerate explanation showing exactly why it is applicable, and specifically what is questionable.

It often happens that a new contribution to an article is rejected. The way the rejection is made has a lot to do with how it is received. This guideline is intended as help to avoid incendiary actions in rejecting new contributions.

A goal of WP is to provide a conciliatory environment for contributors. That goal is served by carefully considered responses to contributors' requests for clarification of reasons for rejection.

Changing consensus

Major edits are best aired on the Talk page before implementation to see what the reaction will be. An existing consensus may exist among those interested in the page, and these editors may oppose the new addition. Because the new addition may provide something new to consider, a presently prevailing majority opposition does not validate a prima facie claim that the new proposal is an attempt to upset consensus.

Where a proposal repeats a previous one, and consensus against the proposal resulted, the new contributor should be provided with appropriate diffs, and with an explanation of why it seems that their proposal is a rehash of the prior one. In this discussion, rejecting editors should bear in mind that their involvement in discussion of prior proposals may give them a mind-set that is blinkered to the novelty of a new proposal that is only superficially similar. A useful guard against such a mind-set is the process of explanation of the similarity, which provokes some thought about the new contribution and avoids knee-jerk rejection.

One reason why a new contribution may result in rehashing old issues is that the article in its present form is correct but not clear, leading to misunderstanding or confusion. To avoid this situation occurring again and again, revision may be appropriate.

Getting the point

Upon rejection, it is natural for a contributor to attempt justification of their addition. Upon initial refusal, a contributor will make what they believe to be a more careful explanation.

It is a frequent failure not to listen carefully to such explanations. It can happen that the contributor's extended explanation is summarily dismissed by the rejecting editors, particularly after a few attempts at justification, perhaps citing Misplaced Pages:Too long; didn't read. The tendency is to see the new justification as just more of the same, and prematurely classify opposition to rejection as a refusal to get the point.

Some sensitivity to the efforts of the contributor demands more than off-the-cuff rejection of arguments, and refusal to read the response carefully. If the new argument appears to be the same and subject to the same objections, this failure of the justification should be presented to the contributor in detail, not just claimed. Careful presentation of the reasons for rejection will help the back-and-forth to converge, and ultimately will result in agreement or in a clear case for refusal to get the point.

Consensus building

It is natural for some controversy to arise over the value of proposed additions. An extended discussion does not in itself constitute interference with building consensus.

Consensus can be constructed: a rejection is helpful when it suggests what can be done to make the contribution acceptable. For example, suggested rewording, or identification of points needing sources, can make it clear to the contributor what is needed. A failure to respond to these explicit and clear suggestions may then indeed constitute a refusal to engage in consensus building.

It is easy to be caught up in a "one-way-and-only-one" controversy. Counterproductive argument can be avoided by assuming at the outset that there is a valid plurality of usages and views, and by subduing expression of strong attachment to one's initial conceptions before the discussion matures. In particular, one should avoid pejorative use of WP:OR, WP:Soap, WP:Fringe and the like to assail an unwelcome view. The goal is to find sources supporting various usages and viewpoints to result in a resolution based upon WP:NPOV.

Critiquing with guidelines and policies

WP guidelines and policies are spelled out on their respective pages, and provide guidance toward good content and productive behavior. But the application of the general policy to the particular case takes judgment that may be controversial. In such cases, an explanation of policy does not help a contributor understand how a policy is judged to apply to their text, or exactly what details are judged objectionable. An obvious and simple fact to one is not like that to another. Impeccable sourcing to one is misinterpretation to another. In any case, the appearance of cavalier rejection without explanation is inflammatory and may result in a hostile encounter on Talk pages that is hard to correct.

Accordingly, when critiquing a proposed addition, rejection based upon guidelines and policies such as WP:OR, WP:Syn, WP:VS, WP:Fringe, WP:Undue and so forth should include detailed explanation of why these descriptions apply to the proposed text. It is considered to be disruptive editing when these guidelines and policies are simply claimed or applied as pejorative adjectives without careful supporting argument, preferably including example quotes of offending material. Direct quotes are preferable as examples, rather than paraphrases or summary statements, to avoid possible misstatement of the offending text.

It should be borne in mind in citing WP:RS that primary sources are acceptable for establishing particular facts when worded properly to maintain a WP:NPOV. Secondary sources are necessary to establish notability only for the subject of the article as a whole, and WP:Notability is not an issue for a subtopic.

Also, citing WP:Undue suggests that a minor topic is being given more prominence in the article than it deserves. That objection may be mitigated by suggesting detail of the minor topic be explained under a separate page devoted to the minor topic. A separate page requires establishment of notability. Care must be taken to distinguish discussion of a topic from discussion of a point of view per se, as the latter is subject to criticism as a WP:POV fork. These two often can be separated by a careful choice of wording and sources.

One-line edit summaries

A feature of WP is the one-line edit summary. The key guideline here is:

• Expand on important information. Readers who see only the summary might not get the entire picture. Prevent misunderstanding: If an edit requires more explanation than will fit in the summary box, use the Talk page to give more information, adding "See Talk" or "See Discussion Page" to the summary.

When material is rejected, the terse one-line summary without Talk-page amplification works best with obvious reversions. Such one-line summaries are prone to abuse, however, perhaps in the hope of avoiding Talk-page discussion. A reversion with a one-line edit summary hardly ever works for serious, extended contributions; the one-line edit summary easily can lead to an unproductive and unpleasant Talk-page exchange.

If the one-line edit summary employs links to a policy or guideline like WP:OR, WP:Syn or so forth, it is quite likely to result in a Talk-page engagement because the contributor is unlikely to view their addition as a violation. With that in mind, the one-line edit using such links should be supplemented with a Talk-page explanation that frames subsequent discussion, or worded in a way unlikely to set up an irritated Talk-page exchange, or even an edit war. For example: "This edit appears to violate WP:Syn. If you differ, please discuss it on the Talk page."

References

1. "continuing to edit in pursuit of a certain point despite an opposing consensus from impartial editors". See "Signs of disruptive editing: Rejects or ignores community input". WP:Disruptive editing. Misplaced Pages. 12 March 2012.
2. "Failure or refusal to "get the point"". WP:Disruptive editing. Misplaced Pages. 12 March 2012.
3. For criteria regarding such interference, see "Signs of disruptive editing: Does not engage in consensus building". WP:Disruptive editing. Misplaced Pages. 12 March 2012.
4. "Attributing and specifying biased statements". Misplaced Pages:Neutral point of view. 13 March 2012. Retrieved 2012-03-14.
5. "Notability guidelines do not limit content within an article". Misplaced Pages:Notability. Misplaced Pages. 27 February 2012.
6. "How to summarize". Help:Edit summary. Misplaced Pages. 15 February 2012. Retrieved 2012-03-15.

See also

• Misplaced Pages:Dispute resolution
• Misplaced Pages:Navigating conflict

• Misplaced Pages proposals