Wikipedia:Supervote

From Wikipedia, the free encyclopedia
Jump to navigation Jump to search

A supervote is a term used on Wikipedia, often in a deletion review or move review, in reference to a discussion closure ("a close") that allegedly reflects the preference of the closer, rather than according to the content of the discussion. It is usually used as an accusation that this is the case, carrying the implication that the closer should have entered the discussion as a participant instead of closing, and that the close should be overturned.

Principle[edit]

Deletion discussions are closed to reflect the consensus in the discussion.

Supervoting vs "admin's discretion"[edit]

Advice to editors decrying a supervote close[edit]

It should be noted that consensus discussions (including XfDs and RfCs) are not really polls. For example, if an XfD discussion has more "keeps" than "deletes" but the "deletes" are grounded in policy and the "keeps" are of the WP:ILIKEIT variety (or conversely if the deletes say WP:ITSCRUFT and the "keeps" are grounded in policy), it's not a "supervote" to close in accordance with a significant minority opinion. (See also WP:Deletion guidelines for administrators § Rough consensus.)

Advice to admins facing a defective debate[edit]

However, an XfD discussion is not an "admin's suggestion box" either. Unless there are serious policy problems with the majority view, a consensus heavily skewed to one side should not be closed the other way. For example, if the majority view at an AfD is based on a position that would clearly violate verifiability or BLP concerns, the majority is wrong. Similarly, it doesn't matter whether the majority wants to keep a file in a FfD debate if it would violate the non-free content, which is prescriptively enforced as a legal matter. If a person feels that the opinions expressed in an XfD are contrary to policy but is not certain, then it is better to comment instead of close. The point raised can help inform the discussion, and this may help someone else to close appropriately.

Types of supervoting[edit]

There are several varieties of supervote, all of them problematic except the last one:

  • Consensus-reversal supervote: A discussion has concluded for a particular action, based on solid policy reasoning, but a minority takes a different view that has less backing. It is supervoting to close in favor of the dissenters. If a neutral closer would not have produced such a close, the discussion should not close that way.
  • Pile-on supervote: A discussion has an emotive majority in favor of an outcome, but it is clearly against policy. It is a supervote to close the discussion in favor of the majority as such, ignoring the policy faults of their arguments. If an impartial closer would have used admin discretion to close against the majority, that is the way the decision should be closed.
  • Forced-compromise supervote: A discussion has drawn to a close, with or without a clear outcome. It is supervoting to close in favor of an undiscussed or unfavored compromise idea, which may satisfy no one. If a discussion did not come to a consensus, it should be closed as such. If it did, it should be closed with that consensus, not with an "I'm going to force everyone to get along" attempt to split the difference. Attempts to do so often produce impractical or nonsensical results. Closers may add a note about significant dissenting viewpoints, caveats, and suggestions for future resolution or improvement, without trying to include them as part of the consensus determination, and this is sufficient.
  • Left-field supervote: A discussion has drawn to a close, with or without a clear outcome. It is a supervote to close in favor of a solution no one even mentioned, or which was mentioned only in passing but not supported. If one has a solution to propose, it should be included in the discussion as a comment. If it's too late, it can be suggested in a later discussion. The extant discussion must have a close that reflects it actual contents. (But see next item.)
  • Non-prejudicial supervote: (Covered in detail below.) A discussion has drawn to a close, with or without a clear outcome. A closer makes an editorial, rather than administrative decision, and it moots the discussion. Alone among supervote types, this kind is often not problematic, because anyone who objects may revert it (or expect the closer to revert), with discussion continuing or being closed differently.

Non-prejudicial supervote[edit]

A "non-prejudicial supervote" is when an XfD is closed either against the consensus in the discussion or where there is no clear consensus, though the closer has left a closing rationale that the close is an "editorial decision" and states what the actual consensus is (if there is one). An example would be an AfD discussion where the consensus is towards deletion, but a bold, non-controversial redirection can be made. It might also apply if an administrator closes an AfD with no !votes as "delete" but offers to restore the article upon request. As an editorial decision, the standard rules of consensus-building and edit-warring apply to the result of such a close so no attempt should be made to "administratively" enforce the result.

What to do with supervotes[edit]

If you believe that a closure reflects the closer's own opinion instead of consensus, civilly ask the closer to revert his/her closure and !vote by his/her preferences. As closing deletion discussions is an administrative action, closers, administrator or non-administrator, are subject to the administrators' accountability policy, and must explain all closes when questioned.

If the closer refuses to revert or adjust his/her closure and you find his/her explanation insufficient, nominate the closure for review (WP:Deletion review for XfDs, WP:Move review, or WP:Administrators' noticeboard for RfCs and other discussions), to have the close itself discussed by the community.

If an editor repeatedly fails to close based on consensus, or refuses to respond to questions regarding possible supervotes, despite multiple warnings and overturned closures, he/she may be banned from closing deletion discussions by the community (usually at WP:ANI or WP:AN), or even desysopped by the Arbitration Committee.

See also[edit]
http://www.let.rug.nl/~gosse/termpedia2/termpedia.php?language=dutch_general&density=7&link_color=000000&termpedia_system=perl_db&url=http%3A%2F%2Fen.wikipedia.org%2Fwiki%2FWikipedia%3ASupervote
www.let.rug.nl
crawl=CC-MAIN-2019-09
56451
application/http; msgtype=response
sha1:4ZGFT2HULDPMIHCKER4N2GBNYUYRH6JQ
<urn:uuid:fc30f62a-378c-45b5-92e0-78ca9c33d401>
2019-02-18T11:58:31Z
129.125.2.101
text/html
sha1:O3ZP6GSRCETJ6Q2SVG53C2K7TSVCS5ST
<urn:uuid:a25892e5-b1e2-434f-b873-f1045ff8207f>
http://www.let.rug.nl/~gosse/termpedia2/termpedia.php?language=dutch_general&density=7&link_color=000000&termpedia_system=perl_db&url=http%3A%2F%2Fen.wikipedia.org%2Fwiki%2FWikipedia%3ASupervote
response
<urn:uuid:e0f309ee-a066-43f9-9f6d-597e93cfd294>
isPartOf: CC-MAIN-2019-09
publisher: Common Crawl
description: Wide crawl of the web for February 2019
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-101-220-24.ec2.internal
software: Apache Nutch 1.15 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 0.11-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: http://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/