Wikipedia:Requests for comment

This page describes the process, including instructions for how and why to create a request for comment (RfC), to participate in one, and to end one.

RfC is one of several processes available within Wikipedia's dispute resolution system. Alternative processes include third opinion, reliable sources noticeboard, neutral point of view noticeboard, the dispute resolution noticeboard, and, for editors' behavior, the administrator's incident noticeboard and binding arbitration.


 * A list of all current RfCs can be found at Requests for comment/All (WP:RFC/A).
 * An archive of (selected) past RfCs and other discussions can be found at Centralized discussion/Archive.

What an RfC is
A request for comment (RfC) is a way to ask the Wikipedia community for input on an issue. Often, the issue is what an article should say. Sometimes it is a proposal for a Wikipedia process or policy change. The aim of RfC discussions is to improve the encyclopedia, and they may relate to article content pages, editorial disputes; changes to policies, guidelines, or procedures; or other topics. An RfC invites comment from a broader selection of editors than a normal talk page discussion. The normal talk page guidelines apply to these discussions.

An RfC discussion typically takes place on a section or subsection of a talk page or noticeboard, and is an ordinary Wikipedia discussion that follows the normal rules and procedures, including possible closing. Summarizing longer discussions is often helpful, as the purpose of an RfC is usually to develop a consensus about some disputed point.

Because Wikipedia makes decisions by consensus, an RfC can act as a dispute resolution. If, for example, editors cannot agree on whether a certain fact should be mentioned in an article, they can use an RfC to find out what the community thinks and, if a consensus emerges, that usually resolves the dispute.

A bot-assisted RfC uses a system of centralized noticeboards and random, bot-delivered invitations to advertise RfCs to other editors. After an RfC creator adds an tag on the talk page that hosts the RfC, a bot will do the rest for them. The RfC is then advertised on a subpage of Requests for comment, all of which are aggregated at Requests for comment/All. Editors interested in responding to RfCs can visit these pages regularly or watch them. There is also a Feedback request service (FRS), in which an editor can subscribe to be notified at random about RfCs at a rate the editor chooses.

Before starting the process
RfCs are time consuming, and editor time is valuable. Editors should try to resolve their issues before starting an RfC. Try discussing the matter with any other parties on the related talk page. If you can reach a consensus or have your questions answered through discussion, then there is no need to start an RfC.

If a local discussion does not answer your question or resolve the problem, then some other forums for resolution include:


 * Asking for input or assistance at one or more relevant WikiProjects, which are often listed at the top of the article's talk page.
 * If an article content question is just between two editors, you can simply and quickly ask for a third opinion on the Third opinion page.
 * If more than two editors are involved or the issue is complex, dispute resolution is available through the Dispute resolution noticeboard.
 * If you want general help in improving an article, such as achieving Featured status, then list it at Peer review.

For a more complete description of dispute resolution options, see the Dispute resolution policy and the list of noticeboards.

If you are not sure if an RfC is necessary, or about how best to frame it, ask on the talk page of this project.

About the conduct of another user

 * To report an offensive or confusing user name in violation of Wikipedia username policy, see subpage User names.


 * To report spam, page blanking, and other blatant vandalism, see Vandalism.

The use of requests for comment on user conduct has been discontinued. In severe cases of misconduct, you may try Administrators' noticeboard/Incidents. If the dispute cannot be resolved there, then arbitration may be warranted as a last resort. You may want to read about other options in the Resolving user conduct disputes policy.

Creating an RfC

 * 1) Make sure that all relevant suggestions have been tried.
 * 2) Open a new section at the bottom of the talk page of the article or project page that you are interested in. The section heading should begin with "RfC" or "Request for comment", for example "RfC on beak length" or "Request for comment on past or present tense for television series".
 * 3) * In some situations, such as when you expect an extremely high number of comments or there is no obviously relevant talk page, you may instead place an RfC on a subpage of this page or a subpage of a policy page; Pending changes/Request for Comment 2012 and Requests for comment/Categorization of persons are examples.
 * 4) At the top of the new talk page section, insert an tag.  The tag must list one or more categories as parameters, for example .  The category must be in lower case.  See the adjacent table for the categories and their meanings.
 * 5) * If no category seems to fit, pick the one that seems closest.
 * 6) * If the RfC is relevant to two categories, include them both in the same tag.  For example:.
 * 7) * Don't add two tags in the same edit.  If you want to start two RfCs on the same page, then read  first.
 * 8) Include a brief, neutral statement of or question about the issue in the talk page section, immediately below the  tag (see ).
 * 9) Sign the statement with either  (name, time and date) or   (just the time and date). Failing to provide a time and date will cause Legobot to remove your discussion from the pages that notify interested editors of RfCs.
 * 10) Publish the talk page. Now you're done. Legobot will take care of the rest, including posting the RfC in the proper RfC lists. Whilst Legobot normally runs once an hour, it may take it up to a day to list the RfC, so be patient.

Categories
The list of RfC categories is in the adjacent table.

The "Wikipedia policies and guidelines" category is for discussing changes to the policies and guidelines themselves, not for discussing how to apply them to a specific case. The same applies to "style", "WikiProject", and the other non-article categories.

The "Language and linguistics" category is for requests related to a Wikipedia article (or part of one) about language and linguistics, not for requests concerning the language on a page. If you want comments on how an article should be worded, categorize your request according to the topic of the article.

Statement should be neutral and brief
Keep the RfC statement (and heading) neutrally worded and short. Statements are often phrased as questions, for example: "Should this article say in the lead that John Smith was a contender for the Pulitzer Prize?"

 ✅ Good questions:
 * Should the picture in the lead be changed?
 * Is this website a good source for information about this product's invention?

Bad questions:
 * What do other editors think about the discussions on this page?
 * We should talk about this some more.
 * Please vote on the following four five six options for the first sentence.

Legobot will copy the markup of your statement (from the end of the tag through the first timestamp) to the list of active RfCs, if it is sufficiently brief; a long statement will fail to be copied. For technical reasons, statements may not contain tables or complex formatting, although these may be added after the initial statement (i.e., after the first timestamp). Similarly, the statement should not begin with a list – but if this is unavoidable, use the markup  before the list, either directly after the  tag or on a line of its own. If the markup of the RfC statement is too long, Legobot may fail to copy it to the RfC list pages, and will not publicise the RfC via the feedback request service.

The statement should be self-contained, and should not assume that the section title is available (because the statement, but not the section title, will be copied to the RfC list pages). If the RfC is about an edit that's been disputed, consider including a diff in the RfC question.

If you have lots to say on the issue, give and sign a brief statement in the initial description and publish the page, then edit the page again and place additional comments below your first statement and timestamp. If you feel that you cannot describe the issue neutrally, you may either ask someone else to write the question or summary, or simply do your best and leave a note asking others to improve it. It may be helpful to discuss your planned RfC question on the talk page before starting the RfC, to see whether other editors have ideas for making it clearer or more concise.

Multiple simultaneous RfCs on one page
 Overuse of RfCs doesn't help.

It is rare for a single article, or a single editor, to have more than one or two productive RfCs open at a time. Before starting a lot of RfCs, please check in on the RfC talk page for advice.

There is no technical limit to the number of simultaneous RfCs that may be held on a single talk page, but to avoid discussion forks, they should not overlap significantly in their subject matter.

Each tag should also be added in a separate edit, with a delay between each edit to let the bot assign an id number to the first before attempting to start a second. If you are starting another RfC on a page which already has one or more ongoing RfCs, first ensure that all of the existing tags already contain a rfcid parameter. The process looks like this:
 * Add your question with one tag.
 * Wait for the bot to edit the page and add an id number to the first RfC question. (Part of the text will change from "Within 24 hours, this page will be added ..." to "This page has been added ..."; this usually takes less than an hour.)
 * Add another question with a second tag.

If any tag anywhere on the page lacks this parameter, even if that RfC was started by another editor, then wait for Legobot to add it before adding another  tag anywhere on the page. If there are two tags on the same page that both lack the rfcid parameter, Legobot will assign the same value to both, with the result that only the lowest one of the page will be publicised; moreover, the incoming link will lead to the higher RfC question, which will cause confusion. To repair this, remove the rfcid parameter from the unpublicised one (usually the higher one).

Example of an RfC
There are many acceptable ways to format an RfC discussion. Below is one example of how a simple RfC discussion could appear when you are editing the talk page. This example will work best for average or smaller discussions; for major disputes, other, more structured formats may be more appropriate.

You can copy and paste this example, but be sure to change the wording to reflect your particular topic (for example, the "hist" category may need to be changed). A signature (" ~ ") or at least a time and date (" ") is required. Do not include any opening html tags (e.g., ) in the initial RfC statement unless its corresponding closing tag (e.g., ) also comes before the first timestamp, i.e., don't "straddle" the first timestamp inside html code, otherwise it may corrupt the entry of the RfC on the topic discussion pages. After you have inserted text similar to this into the talk page, you must publish the page.

Modifying an RfC
If you amend the RfC statement (including the addition of another RfC category), Legobot will copy the amended version to the RfC listings the next time that it runs. If you add another RfC category, this must not be placed after the rfcid parameter (if one is present), because Legobot will not process it properly.

Publicizing an RfC
After you create an RfC, it will be noticed by editors that watch the talk page, by editors that watch the RfC lists, and by some editors subscribed to the Feedback Request Service (FRS), who will be automatically notified by Yapperbot. However, there may not be enough editors to get sufficient input. To get more input, you may publicize the RfC by posting a notice at one or more of the following locations, if related to it:


 * One of the Village Pump forums, such as those for policy issues, proposals, or miscellaneous (The technical forum is almost never an appropriate venue. You may want to ask there before starting an RfC.)
 * Noticeboards such as point-of-view noticeboard, reliable source noticeboard, or original research noticeboard
 * Talk pages of relevant WikiProjects
 * Talk pages of closely related articles or policies

When posting a notice at those locations, provide a link to the RfC, and a brief statement, but do not argue the RfC. You may use to inform other editors. Take care to adhere to the canvassing guideline, which prohibits notifying a chosen group of editors who may be biased. When creating a new Wikipedia policy or suggesting major modifications to a policy, follow the instructions at WP:PROPOSAL. Centralized discussion may be used for policy-related RfCs but is not for publicizing any content disputes in articles. Further guidance is available at WP:Publicising discussions.

Responding to an RfC
All editors (including IP users) are welcome to respond to any RfC.


 * Responses may be submitted in a variety of formats. Some RfCs are structured as a series of distinct responses, one per editor. Others result in a threaded (indented) conversation involving multiple editors. Yet others offer one or more alternative proposals that are separately endorsed or opposed by editors using a polling process. Other RfCs combine polling with threaded discussions. See the example section above for a suggested format.
 * Edits to content under RfC discussion may be particularly controversial. Avoid making edits that others may view as unhelpful. Editing after others have raised objections may be viewed as disruptive editing or edit warring. Be patient; make your improvements in accord with consensus after the RfC is resolved.
 * Try not to be confrontational. Be friendly and civil, and assume good faith of other editors' actions.
 * If you feel an RfC is improperly worded, ask the originator to improve the wording, or add an alternative unbiased statement immediately below the RfC question (after the tag).  You can also ask for help or a second opinion at Wikipedia talk:Requests for comment.  Do not end an RfC just because you think the wording is biased. An  tag generally remains on the page until removed by Legobot or the originator. An RfC can be ended only when the criteria at Ending RfCs are met.
 * Mediate where possible—identify common ground, and attempt to draw editors together rather than push them apart.

Ending RfCs
As an RfC is the solicitation of comment in a discussion, ending an RfC consists of ending that solicitation. When an RfC is used to resolve a dispute, the resolution is determined the same way as for any other discussion: the participants in the discussion determine what they have agreed on and try to implement their agreement.

 Some terms we use:
 * Ending an RfC
 * Removing the link to the discussion from the central RfC lists. This is accomplished by removing the  tag from the talk page; a bot takes care of the rest.  The bot will also remove the tag, if you wait long enough.


 * The end of a discussion
 * This means people have stopped discussing the question. When a discussion has naturally ended, you should consider ending the RfC.


 * Closing the discussion
 * Someone lists conclusions (if any) and discourages further discussion. Some editors make a distinction between "closing" a discussion (discouraging further discussion, usually with the  tag pair) and "summarizing" a discussion (naming outcomes).  Neither "closing" nor "summarizing" are required.

Duration
An RfC should last until enough comment has been received that consensus is reached, or until it is apparent that it won't be. There is no required minimum or maximum duration; however, Legobot assumes an RfC has been forgotten and automatically ends it (removes the tag) 30 days after it begins, to avoid a buildup of stale discussions cluttering the lists and wasting commenters' time.

But editors should not wait for that. If one of the reasons to end RfCs applies, someone should end it manually, as soon as it is clear the discussion has run its course. Conversely, whenever additional comments are still wanted after 30 days, someone should delay Legobot's automatic action. This latter function is based on the first timestamp following the tag.

To extend a current RfC for another 30 days, and to prevent Legobot from automatically ending the RfC during the next month, insert a current timestamp immediately before the original timestamp of the opening statement with either  (name, time and date) or   (just the time and date).

Reasons and ways to end RfCs
Like other discussions, RfCs sometimes end without an agreement or clear resolution. There are several ways in which RfCs end: Please remove the tag when the dispute has been resolved, or when discussion has ended.
 * 1) The question may be withdrawn by the poster (e.g., if the community's response became obvious very quickly).  In this situation, the editor who started the RfC would normally be the person to remove the  tag.
 * 2) The RfC participants can agree to end it at any time; one of them removes the  tag.
 * 3) The dispute may be moved to another dispute resolution forum.
 * 4) Any uninvolved editor can post a closing summary of the discussion; if consensus is undoubtedly clear, even an involved editor may summarize the discussion. The editor removes the  tag while closing the discussion. To avoid concerns about biased summaries, involved editors (on all sides of a dispute) are encouraged to let someone else write a summary.
 * 5) The discussion may just stop, and no one cares to restore the  tag after the bot removes it.

To end an RfC manually, remove the tag from the talk page. Legobot will remove the discussion from the central lists on its next run. (When Legobot automatically ends an RfC because of its age, it will remove the tag.)  If you are also closing the discussion, you should do this in the same edit. As an alternative to removing the tag, you may use one of the template-linking templates such as tlx to disable it, as in.

Do not enclose the tag in  or  tags, nor place it in HTML comment markers  since Legobot will ignore these and treat the RfC as if it is still open – and may also corrupt the RfC listing pages.

Closing the discussion
Anyone who wants an uninvolved editor to write a closing summary of the discussion (ideally with a determination of consensus) can formally request closure by posting at Closure requests. If the matter under discussion is not contentious and the consensus is obvious to the participants, then formal closure is neither necessary nor advisable. Written closing statements are not required. Editors are expected to be able to evaluate and agree upon the results of most RfCs without outside assistance.

To alert readers that an RfC has ended, you may optionally enclose the talk page section in a box using a tag pair such as / or /. This is not required, and may be done with or without a closing statement about the discussions results. This example shows one way to do this:

Restarting an RfC
Anyone who wants to have more comments on the topic can restart an RfC that has ended, as long as the discussion has not been closed. For example, the original poster of an RfC might withdraw it, but someone else may have become interested in the topic in the meantime and restart it.

To restart an RfC, reinsert the tag. If it was automatically removed by Legobot, then be sure to insert a current timestamp after the RfC statement, and before its original timestamp, or it will just get re-removed by the bot. This will give a thirty-day extension; but if the RfC is to be of long duration, you may instead add the line before the  tag.

You should mention at the end of the RfC statement that the RfC ended and restarted, and add your signature if appropriate.