AmtWiki:Request for comment
Requests for comment (RfC) is a process for requesting outside input concerning disputes, policies, guidelines or article content. RfCs are a way to attract more attention to a discussion about making changes to pages or procedures, including articles, guidelines, policies, and many other kinds of pages. The normal talk page guidelines apply to these discussions.
A list of all current RfCs can be found at Category:Requests for comment.
Contents
Using the RfC tag
It's often faster and more effective to thoroughly discuss the matter with any other parties on the related talk page, if there are any. Editors are normally expected to make a reasonable attempt to working out their disputes before seeking help from others. If you are able to come to a consensus or have your questions answered through discussion with other editors, then there is no need to start an RfC.
If a local discussion does not answer your question or resolve the problem, either due to lack of editors or a dispute, then starting an RfC might be the best solution.
About the conduct of another user
If another user is displaying problematic behavior, according to the policies of AmtWiki, the first step to take to is message them on their talk page and try to resolve the issue. Most conduct problems can be solved in this manner. If the disruptive behavior continues, a RfC can be opened on the appropriate talk page. For vandalism, spam, or behavior that cannot be solved by the community, it's better to notify an admin.
Request comment on articles, policies, or other issues
For other issues that require outside commenting, the steps to create an RfC are as follows:
- Edit the talk page of the article or discussion in question. Create a new topic at the bottom of the talk page, preferably with "RfC" in the title of the heading so it is easier to locate for others. Add the template {{rfc}} under the heading, before the text.
- Write a clear, brief statement or question about the issue. Sign the statement with ~~~~.
After you create an RfC, it will be noticed by editors that watch the talk page, and by editors that watch the RfC lists.
Responding to a RfC
All editors (including IP users) are welcome to respond to any RfC. Try not to be confrontational. Be friendly and civil, and assume good faith of other editors' actions.
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.
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 template. Do not close the RfC just because you think the wording is biased. An RfC tag generally remains on the page until removed by the originator. A discussion can be closed only when the criteria at Ending RfCs are met.
Ending RfCs
There are several ways that RfCs end:
- The question may be withdrawn by the poster (e.g., if the community's response became obvious very quickly).
- The RfC participants can agree to end it at any time.
- It can be formally closed by any uninvolved editor.
The outcome is determined by weighing the merits of the arguments and assessing if they are consistent with Wikipedia policies. Counting "votes" is not an appropriate method of determining outcome, though a closer should not ignore numbers entirely.
The default duration of an RfC is 30 days. Editors may choose to end them earlier or extend them longer. Deciding how long to leave an RfC open depends on how much interest there is in the issue and whether editors are continuing to comment.
To end an RfC that is on the active RfC list, remove the RfC template, {{rfc}}, from the talk page.
