Requests for comment/Guideline

This is an outline, a very rough draft. Feel free to revert, change, blank, etc. This is not yet a Guideline.

Filing an RfC edit

First, is an RfC needed? Having a clear idea of the purpose will help in drafting it.

  • To file an RfC, create a page an RfC name. It is suggested that the RfC be drafted in user space, until it is ready to be opened. Make the page name short and concisely descriptive.

Closing an RfC edit

  • An RfC should be closed by a neutral user, not by someone who started it, who is a party to it or is a target of it, and generally not by someone who has commented in it, with an exception mentioned below.
  • Speedy close is possible when the closer considers that considering the RfC will be disruptive and without use to the community.
  • A speedy close should not assert any result as consensus, it should be a close "without prejudice,* representing only an opinion that discussion at this time is not of value. If the close stands, that is effectively a consensus to that effect. It does not prejudice future process, in itself.
  • Any user may promptly revert a close. If reverting a close, move the original close comment at the bottom of the page as a Request to close, so that the closing comment is not removed, it becomes an expressed opinion. One reverting a close should state a reason for that reversion.
  • If a close has stood for three months, it should be considered final. This is not a closure of the issue, it is simply a closure of that particular discussion. Issues may be raised again, with new discussions.
  • When RfCs have been open for a substantial time, and no more comments are arriving, perhaps for three months, it can be time to close.
  • If a result is clearly the community's consensus, supported by evidence and argument, as appropriate, the close should state that result as a conclusion.
  • If no consensus is apparent from the discussion, the RfC should be closed as no consensus, or simply as inactive.
  • An active RfC may be closed if it is considered that leaving it open is causing disruption greater in harm than the value of discussion. If consensus is obviously visible and is not going to change, such a close may declare a conclusion.
  • A close may be made at any time that there has been adequate opportunity for those concerned to comment, and consensus is apparent. It is not necessary that discussion be "complete."
  • When closing an RfC, move the listing on Requests for comments to the appropriate year section for closed RfCs.
  • Moving the listing of a closed RfC to the Archive page is an acceptance of the close.
  • There should be no revert warring over closes. Neither continued discussion nor close of discussion is an emergency. If a user closes, and another re-opens, the original closer should not revert, and if a user re-opens, and other reverts this, the original re-opener should not re-open again. Each of these actions can become a comment in a discussion of closure, generally at the bottom of the RfC, again seeking a neutral close.
  • RfCs should not be opened in such a manner as to duplicate discussion taking place elsewhere, thus forking the discussion. If a policy is being considered, an RfC can be opened for the purpose of collecting comments and thoughts, but not for the purpose of decision. The proposed policy talk page would then, in a small group, decide on a developed draft policy. This may then be presented as a ratification RfC, being relatively stable.

Post-close process edit

  • As mentioned above, closes may be reverted. Reversion re-opens the RfC. This should not be done more than three months after the closure. Beyond re-opening, there are the following methods for continued comment and for reconsideration of issues:
  • Comments may be made at the bottom of a closed RfC, outside the closure template. These comments should relate to the close itself.
  • Comments may be made on the attached Talk page of any RfC after closure.
  • A new RfC may be opened. If an issue has already been considered, it is recommended that at least two users sign the new RfC in order to re-open an issue in this way.
  • A new RfC, even if the issue seems similar, will not be the same. Nevertheless, the new RfC, if sufficiently related, should link to the old RfC, and a note regarding the new RfC may be placed on the Talk page of the older RfC, thus users who commented in it may be notified of the new discussion.
  • Contacting users with regard to an open RfC can be considered canvassing if done in a non-neutral manner. However, discussing issues with users with reference to a closed RfC, seeking to identify support for re-opening an issue, is not canvassing.