|
|
Wikipedia works by building consensus, generally formed on talk pages or central discussion forums. Polling forms an integral part of several processes, e.g. WP:AFD; in other processes, e.g. article editing, polls are generally not used. In both cases, consensus is an inherent part of a wiki process. When conflicts arise, they are resolved through discussion, debate and collaboration. Polling, while not forbidden, should be used with care, if at all, and alternatives should be considered. In addition, even in cases that appear to be "votes", few decisions on Wikipedia are made on a "majority rule" basis, because Wikipedia is not a democracy. Apart from that, on occasion, "higher" bodies (e.g. the Arbitration Committee, Board of Trustees, or Jimbo Wales) can impose decisions regardless of consensus. Potential problems with voting include:
Use of polls when discussing Wikipedia articlesOn Wikipedia, we do not line up to cast ballots without discussion. In some cases, editors use straw polls during discussions of what material to include in various Wikipedia articles. Although such polls are occasionally used and sometimes helpful, their use is controversial. Where used, article straw polls should be developed in a way to assist in reaching true consensus, rather than in an attempt to silence an opposing opinion. Content issues are almost never subject to polling. Out of our 2,427,889 articles, less than 0.1% were ever polled upon.[citation needed] Editor conduct used to be subject to polling in the past, via a system called Quickpolls, but this was deprecated years ago because it generated more heat than light. Nevertheless, participants on article talk pages do sometimes start polls for gauging opinion, and focusing a long or unruly conversation on a specific question at hand. There is no absolute prohibition on polling, and there are often objections if a poll is summarily closed or deleted on sight on a claim that they are forbidden. Editors who feel that a poll is inappropriate under the circumstances may instead note that further commentary is needed, encourage the discussion to migrate back to a free-form conversation, or open a related discussion. Polling discourages consensusHaving the option of settling a dispute by taking a poll, instead of the careful consideration, dissection and eventual synthesis of each side's arguments, actually undermines the progress in dispute resolution that Wiki has allowed. Wikipedia is not a democracy. This is a strength, not a failing. Dialectics is one of the most important things that make Wiki special, and while taking a poll is very often a lot easier than helping each other find a mutually agreeable position, it's almost never better. Polling encourages the community to remain divided by avoiding that discourse; participants don't interact with the other voters, but merely choose camps. Establishing consensus requires expressing that opinion in terms other than a choice between discrete options, and expanding the reasoning behind it, addressing the points that others have left, until all come to a mutually agreeable solution. No one can address objections that aren't stated, points that aren't made. Yes, establishing consensus is a lot harder than taking a poll. So are most things worth doing. Straw poll guidelinesEditors considering an article-related straw poll must remember that polling should be used with care, and should not invoke straw polls prematurely. Note that straw polling cannot serve as a substitute for debate and consensus; that no straw poll is binding on editors who do not agree; and that polling may aggravate rather than resolve existing disputes. Straw polls regarding article content are often inconclusive and sometimes highly contentious. In order to have a chance of being productive, editors must appreciate the following:
Deletion, moving and featuringWikipedia has several processes to deal with such things as deletion debates (e.g. WP:AFD, although most deletions are resolved through WP:PROD and WP:CSD), requested moves (e.g. WP:RM), and featured content (e.g. WP:FAC). These are sometimes wrongly assumed to be majority votes. Each of these processes is not decided based on headcount, but on the strength of the arguments presented. Because the point of these processes is to form consensus, it is preferable that people explain their reasonings, respond to others and possibly compromise, rather than signing a one-word opinion and not looking back. Attempting to "vote stack" such processes are ineffective and potentially disruptive, and "votes" without reasoning may carry no weight in the final interpretation. The template {{Not a ballot}} can be used to remind people about this when necessary. Policy and guidelinesWikipedia is not a democracy; policy and guidelines are not ratified through a vote. Under the relevant policy, new policies and guidelines may be created by (1) codifying existing practice; (2) through community consensus, or (3) as a result of a declaration from Jimmy Wales, the Board, or the Developers in appropriate cases. Novice users sometimes think they should make a "motion" on some issue and "call for votes", but Wikipedia doesn't work like that. Because straw polling cannot create consensus, polling is rarely helpful in the development of policies or guidelines, and frequently counterproductive. Although straw polls and/or votes have been used in the adoption of a limited number of policies, including the three revert rule, and the older parts of Categories for speedy deletion, even in those these cases, the polls were put together carefully and only after discussing the matter for a month or more. No guideline has ever been enacted through a vote. The aim of many guidelines is primarily to describe current practice, to help editors to understand how Wikipedia works. This means that it is not necessary, and in many cases unwise, to call a vote or straw poll on a proposed policy or guideline. If a proposal is not controversial, doing a headcount is not necessary; if a proposal is controversial, doing a headcount to see where the majority lies will not resolve the controversy, and may polarize it further. The controversy may spill onto the poll itself, causing debate on its mechanics. People tend to respond to ill-advised polls by voting against the poll or by adding a section for "voting is evil". StandardsOnce it has been decided by consensus to standardize an issue (e.g. template layout), it is likely there will be several suggestions for standards. Unless one of them is clearly preferred, an approval poll is recommended to select the best-liked standard. This is a way of helping to gauge which of several possible (often similar) versions has the most widespread support, so that the final version reflects consensus. PeopleIn some cases on Wikipedia, community polls are used to determine whether to trust editors with additional responsibilities, in particular requests for adminship and elections for the arbitration committee. However, in both cases the poll results are subject to interpretation by the party who makes the decision (i.e. the bureaucrats or Jimbo). Historically, the party making the decision has considered the arguments made, the number of editors on each side of the issue, and any other relevant factors. In these processes it is preferable if people discuss, ask questions of the candidate, and state their reasonings, rather than simply stating "yes" or "no" with no further comment. While the end result is often obvious based directly on counts of who said yea or nay, it is possible to sway people's opinions by applying solid reasoning and logic. Even so, people new to wikipedia are often confused, due to the strong resemblence between such structured discussion and a majority vote process, which they are not. There is no exact "target" percentage that forms the cutoff point, although some processes, such as WP:RFA, do indicate a rough numerical percentage for establishing consensus. Feature requestsChanges to the MediaWiki software are made by the developers and are usually discussed on BugZilla. Some people are tempted to call a vote on feature requests on the assumption that the more people support a feature, the more likely the developers are to implement it. However, this is not generally the case, as the developers consider issues of feasibility and server load to be far more important. ArbitrationAlthough arbitration is not a community process, it is listed here for the sake of completeness. The ArbCom follows a procedure of listing principles, findings of facts and remedies; individual arbiters discuss these issues and then vote for or against statements and resolutions. However, no "vote" is final until the case is closed. Arbiters can change their positions as a result of discussions with fellow arbiters. In general, findings which attract opposition are reworded to address that opposition, with the aim of reaching a consensus view among the arbitrators. Nevertheless, Arbcom decisions are subject to simple-majority vote. See alsoCommentsNo comments have been added. |
Popular PagesEmail this Page |