990:
57:
1818:
315:
2640:
1704:
1730:
2229:
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
1806:
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
1772:
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).
2597:
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
2715:
tag (exclusive) and the first valid timestamp (inclusive), and which is copied by bot to various pages. The statement itself needs to be neutrally worded and brief. After that first date stamp, you should follow normal talk page rules, which allow you to be verbose (within reason) and as
2297:
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
2585:
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.
1852:
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
1966:) 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.
2281:
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
1794:
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
1957:
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.,
1924:
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
374:
369:
1048:
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".
1880:
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
1945:
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;
2895:
1541:
570:. 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.
1697:
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?"
1070:
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;
2883:
2835:
1491:
1355:
554:
An RfC discussion typically takes place on a section or subsection of a talk page or noticeboard, and is an ordinary
Knowledge (XXG) discussion that follows the normal rules and procedures, including possible
2720:
saying that editors who start RfCs must make their initial explanations look like they are responses to the question (e.g., by placing them inside a ===Discussion=== subsection) or otherwise making them less
2312:
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
1192:. 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.
2889:
1516:
2829:
1330:
2841:
2811:
1380:
1255:
2853:
1430:
2028:. 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:
2877:
1466:
1076:
2094:, which prohibits notifying a chosen group of editors who may be biased. When creating a new Knowledge (XXG) policy or suggesting major modifications to a policy, follow the instructions at
2823:
1305:
2137:
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
2847:
1405:
2263:
Someone lists conclusions (if any) and discourages further discussion. Some editors make a distinction between "closing" a discussion (discouraging further discussion, usually with the
2817:
1280:
2660:
2421:
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
2901:
2867:
1566:
1458:
1072:
1947:
1940:
1802:
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
966:
249:
231:
2382:
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.
2665:
2159:
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
2491:
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
1658:
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.
732:
1787:
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
2795:
1222:
1829:
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
164:
2499:. 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.
962:
2805:
1230:
577:-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
294:
2004:), 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
934:
2497:
If the matter under discussion is not contentious and the consensus is obvious to the participants, then formal closure is neither necessary nor advisable
499:
421:
226:
80:; rather, its purpose is to explain certain aspects of Knowledge (XXG)'s norms, customs, technicalities, or practices. It may reflect differing levels of
2998:
2907:
2199:
1596:
2768:
2738:
tag must be removed and the discussion ended first, since most dispute resolution forums and processes will not accept a case while an RfC is ongoing.
2045:
1904:
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
1667:
350:
426:
124:
2534:. 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:
2988:
2122:
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
2964:
2168:
1830:
1654:
The "Language and linguistics" category is for requests related to a
Knowledge (XXG) article (or part of one) about language and linguistics,
1000:
702:
379:
2782:
2677:
2671:
2049:
2041:
2021:
1788:
1211:
598:
590:
488:
384:
335:
330:
2993:
2717:
2126:
involving multiple editors. Yet others offer one or more alternative proposals that are separately endorsed or opposed by editors using a
2107:
1644:
559:. Summarizing longer discussions is often helpful, as the purpose of an RfC is usually to develop a consensus about some disputed point.
528:
340:
77:
2099:
1651:
for discussing how to apply them to a specific case. The same applies to "style", "WikiProject", and the other non-article categories.
856:
362:
308:
520:
2037:
325:
261:
2255:
This means people have stopped discussing the question. When a discussion has naturally ended, you should consider ending the RfC.
650:
639:
548:
266:
159:
73:
2082:
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
287:
2333:
Like other discussions, RfCs sometimes end without an agreement or clear resolution. There are several ways in which RfCs end:
2258:
556:
401:
2364:
635:
567:
536:
456:
345:
119:
634:
RfCs are time consuming, and editor time is valuable. Editors should try to resolve their issues before starting an RfC. Try
2683:
2619:
You should mention at the end of the RfC statement that the RfC ended and restarted, and add your signature if appropriate.
2179:
tag generally remains on the page until removed by
Legobot or the originator. An RfC can be ended only when the criteria at
2153:
139:
65:
2502:
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
645:
If a local discussion does not answer your question or resolve the problem, then some other forums for resolution include:
2761:
2290:
tag) 30 days after it begins, to avoid a buildup of stale discussions cluttering the lists and wasting commenters' time.
642:. If you can reach a consensus or have your questions answered through discussion, then there is no need to start an RfC.
2492:
772:
523:
for input on an issue. Often, the issue is what an article should say. Sometimes it is a proposal for a
Knowledge (XXG)
2483:
since Legobot will ignore these and treat the RfC as if it is still open – and may also corrupt the RfC listing pages.
910:
776:
2429:
tag.) If you are also closing the discussion, you should do this in the same edit. As an alternative to removing the
658:
If an article content question is just between two editors, you can simply and quickly ask for a third opinion on the
280:
974:
585:
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
1837:
There is no technical limit to the number of simultaneous RfCs that may be held on a single talk page, but to avoid
2513:
786:
2374:; if consensus is undoubtedly clear, even an involved editor may summarize the discussion. The editor removes the
906:
660:
192:
2935:
section, where "xxx" is the category abbreviation. The different category abbreviations that should be used with
2249:
tag from the talk page; a bot takes care of the rest. The bot will also remove the tag, if you wait long enough.
2142:
2055:
2033:
695:
209:
2754:
2689:
2271:
tag pair) and "summarizing" a discussion (naming outcomes). Neither "closing" nor "summarizing" are required.
2073:
970:
681:
154:
2529:
2505:
2266:
677:
667:
If more than two editors are involved or the issue is complex, dispute resolution is available through the
601:(FRS), in which an editor can subscribe to be notified at random about RfCs at a rate the editor chooses.
2932:
2655:
2649:
2186:
2017:
1044:
952:
876:
540:
524:
392:
204:
169:
144:
85:
81:
2189:
where possible—identify common ground, and attempt to draw editors together rather than push them apart.
1807:
before starting the RfC, to see whether other editors have ideas for making it clearer or more concise.
2631:
2205:
2149:
2095:
1838:
1673:
1623:
1054:
1010:
930:
714:
610:
149:
95:
2241:
Removing the link to the discussion from the central RfC lists. This is accomplished by removing the
1100:. The category must be in lower case. See the adjacent table for the categories and their meanings.
2521:
1954:
2945:
are listed above in parenthesis. Multiple categories are separated by a vertical pipe. For example,
2320:
2314:
2103:
2091:
1177:
1171:
866:
532:
2085:
1773:
Similarly, the statement should not begin with a list – but if this is unavoidable, use the markup
2123:
2001:
480:
468:
2341:). In this situation, the editor who started the RfC would normally be the person to remove the
539:; changes to policies, guidelines, or procedures; or other topics. An RfC invites comment from a
2371:
492:
460:
36:
28:
2052:
forum is almost never an appropriate venue. You may want to ask there before starting an RfC.)
2338:
2127:
2059:
947:
846:
824:
820:
808:
544:
472:
464:
40:
760:
2067:
2063:
2020:
the talk page, by editors that watch the RfC lists, and by some editors subscribed to the
896:
842:
838:
834:
816:
812:
804:
800:
796:
669:
574:
563:
476:
32:
2138:
886:
691:
2145:. Be patient; make your improvements in accord with consensus after the RfC is resolved.
1643:
The "Knowledge (XXG) policies and guidelines" category is for discussing changes to the
2025:
2008:
parameter (if one is present), because Legobot will not process it properly if you do.
594:
701:
If you are not sure if an RfC is necessary, or about how best to frame it, ask on the
2982:
754:
444:
This page describes the process, including instructions for how and why to create a
2968:
2939:
2733:
2710:
2611:
2592:
2464:
2450:
2441:
2432:
2424:
2416:
2401:
2388:
2377:
2355:
2344:
2301:
2285:
2244:
2174:
2162:
1915:
1907:
1899:
1887:
1872:
1856:
1847:
1782:
1767:
1612:
1582:
1557:
1532:
1507:
1482:
1446:
1421:
1396:
1371:
1346:
1321:
1296:
1271:
1246:
1183:
1155:
1129:
1117:
1109:
1095:
1087:
973:
may be warranted as a last resort. You may want to read about other options in the
580:
17:
1186:
to remove your discussion from the pages that notify interested editors of RfCs.
2337:
The question may be withdrawn by the poster (e.g., if the community's response
593:. Editors interested in responding to RfCs can visit these pages regularly or
2352:
The RfC participants can agree to end it at any time; one of them removes the
2746:
1796:
2639:
1962:) in the initial RfC statement unless its corresponding closing tag (e.g.,
1948:
for major disputes, other, more structured formats may be more appropriate
1092:
tag. The tag must list one or more categories as parameters, for example
306:
46:
Information page on the process of requests for comment on Knowledge (XXG)
498:
An archive of (selected) past RfCs and other discussions can be found at
1182:(just the time and date). Failing to provide a time and date will cause
1106:
If the RfC is relevant to two categories, include them both in the same
690:
For a more complete description of dispute resolution options, see the
2707:
For clarity: The "statement" is the part that is located between the
2171:. Do not end an RfC just because you think the wording is biased. An
2949:, where "xxx" is the first category and "yyy" is the second category.
2680:– sign up to receive notifications of new RfCs on your user talk page
2406:
tag when the dispute has been resolved, or when discussion has ended.
2118:
All editors (including IP users) are welcome to respond to any RfC.
1764:
Legobot will copy the markup of your statement (from the end of the
676:
If you want general help in improving an article, such as achieving
455:
RfC is one of several processes available within Knowledge (XXG)'s
2000:
If you amend the RfC statement (including the addition of another
965:
has been discontinued. In severe cases of misconduct, you may try
1841:, they should not overlap significantly in their subject matter.
2130:. Other RfCs combine polling with threaded discussions. See the
535:
the encyclopedia, and they may relate to article content pages,
2750:
2437:
tag, you may use one of the template-linking templates such as
1988:
Should the "History" section contain a photograph of the ship?
1743:
What do other editors think about the discussions on this page?
655:, which are often listed at the top of the article's talk page.
2385:
The discussion may just stop, and no one cares to restore the
1929:
parameter from the unpublicised one (usually the higher one).
1077:
Knowledge (XXG):Requests for comment/Categorization of persons
984:
51:
2656:
Knowledge (XXG):Decisions not subject to consensus of editors
1724:
a good source for information about this product's invention?
1103:
If no category seems to fit, pick the one that seems closest.
2016:
After you create an RfC, it will be noticed by editors that
1137:
1147:
1136:
If you want to start two RfCs on the same page, then read
2167:
tag). You can also ask for help or a second opinion at
1073:
Knowledge (XXG):Pending changes/Request for Comment 2012
2220:
2213:
1941:
Knowledge (XXG):Requests for comment/Example formatting
1688:
1681:
1631:
1603:
1573:
1548:
1523:
1498:
1473:
1437:
1412:
1387:
1362:
1337:
1312:
1287:
1262:
1237:
1062:
1025:
1018:
722:
649:
Asking for input or assistance at one or more relevant
625:
618:
432:
416:
411:
406:
254:
197:
174:
103:
1721:
1640:
The list of RfC categories is in the adjacent table.
967:
Knowledge (XXG):Administrators' noticeboard/Incidents
2293:
But editors should not wait for that. If one of the
2090:
to inform other editors. Take care to adhere to the
2916:
2863:
2791:
1774:
1084:At the top of the new talk page section, insert an
385:
WMF asking for ideas for annual fundraising banners
2666:Special:Prefixindex/Wikipedia:Requests for comment
2648:For ongoing discussions and current requests, see
2078:Talk pages of closely related articles or policies
950:, page blanking, and other blatant vandalism, see
2294:
733:Specifying that RfCs should not be listed on AfDs
380:Subject-specific notability guideline for species
2539:== RfC about the photo in the History section ==
1971:== RfC about the photo in the history section ==
1152:in the talk page section, immediately below the
1036:
969:. If the dispute cannot be resolved there, then
731:For the rationale originating this section, see
2148:Try not to be confrontational. Be friendly and
2106:in articles. Further guidance is available at
793:Featured Article/List/Picture/Topic discussions
2896:Knowledge (XXG) technical issues and templates
1542:Knowledge (XXG) technical issues and templates
500:Knowledge (XXG):Centralized discussion/Archive
391:For a listing of ongoing discussions, see the
27:"WP:RFC" redirects here. For active RFCs, see
2762:
2024:(FRS), who will be automatically notified by
288:
8:
636:discussing the matter with any other parties
2479:tags, nor place it in HTML comment markers
2102:may be used for policy-related RfCs but is
1912:tag anywhere on the page. If there are two
1779:before the list, either directly after the
997:ask for help with writing your RfC question
562:Because Knowledge (XXG) makes decisions by
487:A list of all current RfCs can be found at
2769:
2755:
2747:
2565:.... here is the entire RfC discussion...
2557:Consensus was reached to keep the photo.
1717:Should the picture in the lead be changed?
452:), to participate in one, and to end one.
295:
281:
115:
2965:Knowledge (XXG) talk:Requests for comment
2169:Knowledge (XXG) talk:Requests for comment
1920:tags on the same page that both lack the
1865:parameter. The process looks like this:
2678:Knowledge (XXG):Feedback request service
2672:Knowledge (XXG):Requests for comment/All
2104:not for publicizing any content disputes
1138:§ Multiple simultaneous RfCs on one page
1043:Open a new section at the bottom of the
736:
591:Knowledge (XXG):Requests for comment/All
489:Knowledge (XXG):Requests for comment/All
370:Review of the RfA discussion-only period
78:Knowledge (XXG)'s policies or guidelines
2884:Knowledge (XXG) policies and guidelines
2700:
1492:Knowledge (XXG) policies and guidelines
433:
241:
184:
131:
118:
2005:
1926:
1921:
1862:
1811:Multiple simultaneous RfCs on one page
903:Renaming pages (other than categories)
2668:– a list of all subpages of this page
2603:<!-- RFCBot Ignore Expired --: -->
1662:Statement should be neutral and brief
773:WP:Deletion process § Deletion venues
7:
2999:Knowledge (XXG) requests for comment
2961:Knowledge (XXG):Requests for comment
2363:The dispute may be moved to another
1746:We should talk about this some more.
925:To report an offensive or confusing
587:Knowledge (XXG):Requests for comment
477:administrator's incident noticeboard
2480:
2475:
2470:
1963:
1959:
1884:Add another question with a second
961:The use of requests for comment on
746:Follow the procedures described at
709:What not to use the RfC process for
531:. The aim of RfC discussions is to
2967:. Lists are updated every hour by
2730:For this to succeed, however, the
2124:a threaded (indented) conversation
475:, and, for editors' behavior, the
35:. For redirects for creation, see
31:. For requests for checkuser, see
25:
2989:Knowledge (XXG) information pages
2922:To add a discussion to this list:
2836:Media, the arts, and architecture
2684:Knowledge (XXG):Request directory
2661:Archives of user conduct disputes
2372:closing summary of the discussion
2370:Any uninvolved editor can post a
1817:
1356:Media, the arts, and architecture
919:About the conduct of another user
825:Today's featured article/requests
821:Featured topic removal candidates
589:, all of which are aggregated at
469:neutral point of view noticeboard
459:. Alternative processes include
2878:Knowledge (XXG) style and naming
2638:
2589:To restart an RfC, reinsert the
2493:Knowledge (XXG):Closure requests
2200:WP:Advice on closing discussions
2180:
1816:
1728:
1702:
1467:Knowledge (XXG) style and naming
988:
809:Featured list removal candidates
313:
55:
49:Knowledge (XXG) information page
39:. For requests for closure, see
2890:WikiProjects and collaborations
2686:– all other request departments
2674:– a listing of all current RfCs
2629:This page is referenced in the
2230:to implement their agreement.
1759:options for the first sentence.
1668:WP:Writing requests for comment
1517:WikiProjects and collaborations
975:Resolving user conduct disputes
931:Knowledge (XXG) username policy
2994:Knowledge (XXG) glossary items
2830:Maths, science, and technology
1331:Maths, science, and technology
1150:of or question about the issue
831:Good Article/Topic discussions
670:Dispute resolution noticeboard
473:dispute resolution noticeboard
1:
2842:Politics, government, and law
2812:Economy, trade, and companies
2393:tag after the bot removes it.
2134:above for a suggested format.
2068:original research noticeboard
1825:Overuse of RfCs doesn't help.
1749:Please vote on the following
1381:Politics, government, and law
1256:Economy, trade, and companies
847:Good topic removal candidates
738:Alternative processes to RfC
2854:Society, sports, and culture
2477:...</syntaxhighlight: -->
2329:Reasons and ways to end RfCs
2131:
1431:Society, sports, and culture
1161:
551:apply to these discussions.
465:reliable sources noticeboard
2690:Knowledge (XXG):Expert help
2339:became obvious very quickly
2064:reliable source noticeboard
1869:Add your question with one
813:Featured picture candidates
797:Featured article candidates
605:Before starting the process
3015:
2959:For more information, see
2716:non-neutral as you want.
2325:(just the time and date).
2203:
2197:
2156:of other editors' actions.
2108:WP:Publicising discussions
2036:forums, such as those for
1938:
1671:
1665:
1621:
1052:
1008:
787:Template talk:Did you know
730:
712:
608:
93:
26:
2957:
2902:Knowledge (XXG) proposals
2650:Knowledge (XXG):Dashboard
2319:(name, time and date) or
2060:point-of-view noticeboard
1567:Knowledge (XXG) proposals
1203:
1176:(name, time and date) or
953:Knowledge (XXG):Vandalism
897:Categories for discussion
839:Good article reassessment
817:Featured topic candidates
692:Dispute resolution policy
543:of editors than a normal
521:Knowledge (XXG) community
457:dispute resolution system
2824:Language and linguistics
2632:Knowledge (XXG) Glossary
2600:
2536:
2476:<syntaxhighlight: -->
2453:|rfc|bio|rfcid=fedcba9}}
2365:dispute resolution forum
2022:Feedback Request Service
1968:
1789:feedback request service
1306:Language and linguistics
1148:brief, neutral statement
835:Good article nominations
805:Featured list candidates
783:Did You Know suggestions
599:Feedback request service
375:ArbCom election RFC 2024
250:Administrator assistance
2848:Religion and philosophy
2718:There is no actual rule
2310:To extend a current RfC
2252:The end of a discussion
2072:Talk pages of relevant
1861:tags already contain a
1645:policies and guidelines
1406:Religion and philosophy
801:Featured article review
597:them. There is also a
547:discussion. The normal
366:is open for discussion.
2487:Closing the discussion
2411:To end an RfC manually
2259:Closing the discussion
2100:Centralized discussion
1134:tags in the same edit.
857:In the news candidates
853:In the news candidates
843:Good topic nominations
566:, an RfC can act as a
519:) is a way to ask the
309:Centralized discussion
227:Resolution noticeboard
2963:. Report problems to
2818:History and geography
2447:to disable it, as in
1799:in the RfC question.
1281:History and geography
1190:Publish the talk page
1001:this page's talk page
363:request for adminship
160:Discuss on talk pages
155:Be open to compromise
2778:Requests for comment
2114:Responding to an RfC
2092:canvassing guideline
1455:Project-wide topics
1206:Issues by topic area
1037:relevant suggestions
549:talk page guidelines
74:encyclopedic article
2472:...</nowiki: -->
2295:reasons to end RfCs
2234:Some terms we use:
1114:tag. For example:
1035:Make sure that all
893:Renaming categories
739:
513:request for comment
481:binding arbitration
446:request for comment
18:Knowledge (XXG):RfC
2398:Please remove the
2139:disruptive editing
2012:Publicizing an RfC
1168:Sign the statement
777:WP:Deletion review
769:Deletion processes
737:
680:, then list it at
568:dispute resolution
537:editorial disputes
165:Failure to discuss
120:Dispute resolution
2976:
2975:
2581:Restarting an RfC
2571:closed rfc bottom
2514:closed rfc bottom
2481:<!--...--: -->
2154:assume good faith
1933:Example of an RfC
1831:the RfC talk page
1620:
1619:
1007:
1006:
916:
915:
705:of this project.
541:broader selection
305:
304:
140:Assume good faith
114:
113:
16:(Redirected from
3006:
2950:
2948:
2944:
2938:
2931:at the top of a
2930:
2871:
2799:
2786:
2771:
2764:
2757:
2748:
2739:
2737:
2728:
2722:
2714:
2705:
2642:
2634:
2615:
2604:
2596:
2576:
2575:
2572:
2569:
2564:
2563:
2560:
2556:
2553:
2550:
2547:
2544:
2540:
2533:
2525:
2517:
2509:
2482:
2478:
2473:
2468:
2454:
2446:
2440:
2436:
2428:
2420:
2405:
2392:
2381:
2359:
2348:
2323:
2317:
2305:
2289:
2270:
2248:
2223:
2216:
2178:
2166:
2089:
2007:
1996:Modifying an RfC
1991:
1987:
1986:
1982:
1979:
1976:
1972:
1965:
1961:
1928:
1923:
1919:
1911:
1903:
1891:
1876:
1864:
1860:
1851:
1839:discussion forks
1823:
1820:
1819:
1786:
1778:
1777:
1771:
1735:
1732:
1731:
1709:
1706:
1705:
1691:
1684:
1634:
1616:
1586:
1561:
1536:
1511:
1486:
1461:
1450:
1425:
1400:
1375:
1350:
1325:
1300:
1275:
1250:
1225:
1214:
1208:
1201:
1200:
1180:
1174:
1159:
1133:
1121:
1113:
1099:
1091:
1065:
1039:have been tried.
1028:
1021:
992:
991:
985:
929:in violation of
764:
740:
725:
694:and the list of
628:
621:
584:
437:
435:
365:
317:
316:
297:
290:
283:
270:
258:
242:Conduct disputes
234:
222:
215:Request comments
200:
185:Content disputes
177:
116:
106:
66:information page
59:
58:
52:
21:
3014:
3013:
3009:
3008:
3007:
3005:
3004:
3003:
2979:
2978:
2977:
2972:
2953:
2947:{{rfc|xxx|yyy}}
2946:
2942:
2936:
2928:
2926:
2912:
2865:
2859:
2793:
2787:
2780:
2775:
2742:
2731:
2729:
2725:
2708:
2706:
2702:
2698:
2645:
2644:
2643:
2636:
2630:
2625:
2609:
2606:
2605:
2602:
2590:
2583:
2578:
2577:
2573:
2570:
2567:
2566:
2561:
2558:
2554:
2551:
2548:
2545:
2542:
2541:
2538:
2527:
2519:
2511:
2503:
2489:
2471:<nowiki: -->
2462:
2448:
2444:
2438:
2430:
2422:
2414:
2399:
2386:
2375:
2353:
2342:
2331:
2321:
2315:
2299:
2283:
2279:
2274:
2264:
2242:
2227:
2226:
2219:
2212:
2208:
2202:
2196:
2172:
2160:
2132:example section
2128:polling process
2116:
2083:
2014:
1998:
1993:
1992:
1989:
1984:
1980:
1977:
1974:
1973:
1970:
1964:</small: -->
1943:
1935:
1913:
1905:
1897:
1885:
1870:
1854:
1845:
1835:
1821:
1813:
1780:
1775:
1765:
1762:
1733:
1729:
1707:
1703:
1695:
1694:
1687:
1680:
1676:
1670:
1664:
1638:
1637:
1630:
1626:
1610:
1580:
1555:
1530:
1505:
1480:
1456:
1444:
1419:
1394:
1369:
1344:
1319:
1294:
1269:
1244:
1220:
1219:Article topics
1209:
1204:
1199:
1178:
1172:
1153:
1127:
1115:
1107:
1093:
1085:
1069:
1068:
1061:
1057:
1032:
1031:
1024:
1017:
1013:
989:
983:
981:Creating an RfC
921:
911:Requested moves
873:Split proposals
863:Merge proposals
758:
735:
729:
728:
721:
717:
711:
678:Featured status
638:on the related
632:
631:
624:
617:
613:
607:
578:
509:
442:
441:
440:
431:
397:
389:
361:
355:
318:
314:
311:
301:
265:
253:
230:
218:
196:
173:
110:
109:
102:
98:
90:
89:
56:
50:
47:
44:
23:
22:
15:
12:
11:
5:
3012:
3010:
3002:
3001:
2996:
2991:
2981:
2980:
2974:
2973:
2958:
2955:
2954:
2952:
2951:
2920:
2918:
2914:
2913:
2911:
2910:
2905:
2899:
2893:
2887:
2881:
2874:
2872:
2861:
2860:
2858:
2857:
2851:
2845:
2839:
2833:
2827:
2821:
2815:
2809:
2802:
2800:
2789:
2788:
2776:
2774:
2773:
2766:
2759:
2751:
2744:
2741:
2740:
2723:
2699:
2697:
2694:
2693:
2692:
2687:
2681:
2675:
2669:
2663:
2658:
2653:
2637:
2628:
2627:
2626:
2624:
2621:
2601:
2582:
2579:
2546:closed rfc top
2537:
2530:archive bottom
2506:closed rfc top
2488:
2485:
2395:
2394:
2383:
2368:
2361:
2350:
2330:
2327:
2278:
2275:
2273:
2272:
2267:closed rfc top
2261:
2256:
2253:
2250:
2239:
2232:
2225:
2224:
2217:
2209:
2204:
2195:
2192:
2191:
2190:
2184:
2157:
2146:
2135:
2115:
2112:
2080:
2079:
2076:
2070:
2053:
2013:
2010:
1997:
1994:
1969:
1960:<small: -->
1955:copy and paste
1934:
1931:
1894:
1893:
1882:
1878:
1814:
1812:
1809:
1761:
1760:
1747:
1744:
1726:
1725:
1718:
1711:Good questions
1700:
1693:
1692:
1685:
1677:
1672:
1663:
1660:
1657:
1650:
1636:
1635:
1627:
1622:
1618:
1617:
1608:
1599:
1593:
1592:
1588:
1587:
1578:
1569:
1563:
1562:
1553:
1544:
1538:
1537:
1528:
1519:
1513:
1512:
1503:
1494:
1488:
1487:
1478:
1469:
1463:
1462:
1452:
1451:
1442:
1433:
1427:
1426:
1417:
1408:
1402:
1401:
1392:
1383:
1377:
1376:
1367:
1358:
1352:
1351:
1342:
1333:
1327:
1326:
1317:
1308:
1302:
1301:
1292:
1283:
1277:
1276:
1267:
1258:
1252:
1251:
1242:
1233:
1227:
1226:
1216:
1215:
1198:
1195:
1194:
1193:
1187:
1165:
1143:
1142:
1141:
1126:Don't add two
1123:
1104:
1082:
1081:
1080:
1067:
1066:
1058:
1053:
1040:
1030:
1029:
1022:
1014:
1009:
1005:
1004:
993:
982:
979:
959:
958:
942:
941:
933:, see subpage
920:
917:
914:
913:
904:
900:
899:
894:
890:
889:
884:
880:
879:
874:
870:
869:
864:
860:
859:
854:
850:
849:
832:
828:
827:
794:
790:
789:
784:
780:
779:
770:
766:
765:
752:
748:
747:
744:
727:
726:
718:
713:
710:
707:
688:
687:
674:
665:
656:
630:
629:
622:
614:
609:
606:
603:
508:
507:What an RfC is
505:
504:
503:
496:
439:
438:
429:
424:
419:
414:
409:
404:
398:
396:
390:
388:
387:
382:
377:
372:
367:
357:
356:
354:
353:
348:
343:
338:
333:
328:
323:
319:
312:
307:
303:
302:
300:
299:
292:
285:
277:
274:
273:
272:
271:
259:
244:
243:
239:
238:
237:
236:
224:
212:
207:
202:
187:
186:
182:
181:
180:
179:
167:
162:
157:
152:
147:
142:
134:
133:
129:
128:
122:
112:
111:
108:
107:
99:
94:
91:
71:
70:
62:
60:
48:
45:
24:
14:
13:
10:
9:
6:
4:
3:
2:
3011:
3000:
2997:
2995:
2992:
2990:
2987:
2986:
2984:
2970:
2966:
2962:
2956:
2941:
2934:
2925:
2924:
2923:
2919:
2915:
2909:
2906:
2903:
2900:
2897:
2894:
2891:
2888:
2885:
2882:
2879:
2876:
2875:
2873:
2869:
2864:Non-articles
2862:
2855:
2852:
2849:
2846:
2843:
2840:
2837:
2834:
2831:
2828:
2825:
2822:
2819:
2816:
2813:
2810:
2807:
2804:
2803:
2801:
2797:
2790:
2784:
2779:
2772:
2767:
2765:
2760:
2758:
2753:
2752:
2749:
2745:
2735:
2727:
2724:
2719:
2712:
2704:
2701:
2695:
2691:
2688:
2685:
2682:
2679:
2676:
2673:
2670:
2667:
2664:
2662:
2659:
2657:
2654:
2651:
2647:
2646:
2641:
2633:
2622:
2620:
2617:
2613:
2599:
2594:
2587:
2580:
2535:
2531:
2523:
2515:
2507:
2500:
2498:
2494:
2486:
2484:
2466:
2460:
2456:
2452:
2443:
2434:
2426:
2418:
2413:, remove the
2412:
2408:
2407:
2403:
2390:
2384:
2379:
2373:
2369:
2366:
2362:
2357:
2351:
2346:
2340:
2336:
2335:
2334:
2328:
2326:
2324:
2318:
2311:
2307:
2303:
2296:
2291:
2287:
2276:
2268:
2262:
2260:
2257:
2254:
2251:
2246:
2240:
2238:Ending an RfC
2237:
2236:
2235:
2231:
2222:
2218:
2215:
2211:
2210:
2207:
2201:
2193:
2188:
2185:
2182:
2176:
2170:
2164:
2158:
2155:
2151:
2147:
2144:
2140:
2136:
2133:
2129:
2125:
2121:
2120:
2119:
2113:
2111:
2109:
2105:
2101:
2097:
2093:
2087:
2077:
2075:
2071:
2069:
2065:
2061:
2057:
2054:
2051:
2047:
2046:miscellaneous
2043:
2039:
2038:policy issues
2035:
2031:
2030:
2029:
2027:
2023:
2019:
2011:
2009:
2003:
1995:
1967:
1956:
1951:
1949:
1942:
1937:
1932:
1930:
1917:
1909:
1901:
1889:
1883:
1879:
1874:
1868:
1867:
1866:
1858:
1849:
1842:
1840:
1834:
1832:
1827:
1826:
1810:
1808:
1805:
1800:
1798:
1792:
1790:
1784:
1769:
1758:
1755:
1752:
1748:
1745:
1742:
1741:
1740:
1738:
1737:Bad questions
1723:
1719:
1716:
1715:
1714:
1712:
1699:
1690:
1689:WP:RFCNEUTRAL
1686:
1683:
1679:
1678:
1675:
1669:
1661:
1659:
1655:
1652:
1648:
1646:
1641:
1633:
1629:
1628:
1625:
1614:
1609:
1607:
1605:
1600:
1598:
1597:Unsorted RfCs
1595:
1594:
1590:
1589:
1584:
1579:
1577:
1575:
1570:
1568:
1565:
1564:
1559:
1554:
1552:
1550:
1545:
1543:
1540:
1539:
1534:
1529:
1527:
1525:
1520:
1518:
1515:
1514:
1509:
1504:
1502:
1500:
1495:
1493:
1490:
1489:
1484:
1479:
1477:
1475:
1470:
1468:
1465:
1464:
1460:
1454:
1453:
1448:
1443:
1441:
1439:
1434:
1432:
1429:
1428:
1423:
1418:
1416:
1414:
1409:
1407:
1404:
1403:
1398:
1393:
1391:
1389:
1384:
1382:
1379:
1378:
1373:
1368:
1366:
1364:
1359:
1357:
1354:
1353:
1348:
1343:
1341:
1339:
1334:
1332:
1329:
1328:
1323:
1318:
1316:
1314:
1309:
1307:
1304:
1303:
1298:
1293:
1291:
1289:
1284:
1282:
1279:
1278:
1273:
1268:
1266:
1264:
1259:
1257:
1254:
1253:
1248:
1243:
1241:
1239:
1234:
1232:
1229:
1228:
1224:
1218:
1217:
1213:
1207:
1202:
1196:
1191:
1188:
1185:
1181:
1175:
1169:
1166:
1163:
1157:
1151:
1149:
1144:
1139:
1135:
1131:
1124:
1119:
1111:
1105:
1102:
1101:
1097:
1089:
1083:
1079:are examples.
1078:
1074:
1064:
1060:
1059:
1056:
1051:
1050:
1047:
1046:
1041:
1038:
1034:
1033:
1027:
1023:
1020:
1016:
1015:
1012:
1002:
998:
994:
987:
986:
980:
978:
976:
972:
968:
964:
957:
955:
954:
949:
944:
943:
940:
938:
937:
932:
928:
923:
922:
918:
912:
908:
907:Moving a page
905:
902:
901:
898:
895:
892:
891:
888:
885:
882:
881:
878:
875:
872:
871:
868:
865:
862:
861:
858:
855:
852:
851:
848:
844:
840:
836:
833:
830:
829:
826:
822:
818:
814:
810:
806:
802:
798:
795:
792:
791:
788:
785:
782:
781:
778:
774:
771:
768:
767:
762:
756:
755:Help:Contents
753:
750:
749:
745:
742:
741:
734:
724:
720:
719:
716:
708:
706:
704:
699:
697:
693:
685:
684:
679:
675:
672:
671:
666:
663:
662:
661:Third opinion
657:
654:
653:
648:
647:
646:
643:
641:
637:
627:
626:WP:RFC#BEFORE
623:
620:
616:
615:
612:
604:
602:
600:
596:
592:
588:
582:
576:
571:
569:
565:
560:
558:
552:
550:
546:
542:
538:
534:
530:
529:policy change
526:
522:
518:
514:
506:
501:
497:
494:
490:
486:
485:
484:
482:
478:
474:
470:
466:
462:
461:third opinion
458:
453:
451:
447:
436:
430:
428:
425:
423:
420:
418:
415:
413:
410:
408:
405:
403:
400:
399:
394:
386:
383:
381:
378:
376:
373:
371:
368:
364:
359:
358:
352:
349:
347:
344:
342:
339:
337:
334:
332:
329:
327:
324:
322:Village pumps
321:
320:
310:
298:
293:
291:
286:
284:
279:
278:
276:
275:
268:
263:
260:
256:
251:
248:
247:
246:
245:
240:
233:
228:
225:
221:
216:
213:
211:
208:
206:
203:
199:
194:
193:Third opinion
191:
190:
189:
188:
183:
176:
171:
168:
166:
163:
161:
158:
156:
153:
151:
148:
146:
145:Use etiquette
143:
141:
138:
137:
136:
135:
130:
126:
121:
117:
105:
101:
100:
97:
92:
87:
83:
79:
76:, nor one of
75:
72:It is not an
69:
67:
61:
54:
53:
42:
38:
34:
30:
19:
2960:
2927:Add the tag
2921:
2917:Instructions
2777:
2743:
2726:
2703:
2618:
2607:
2588:
2584:
2501:
2496:
2490:
2461:enclose the
2458:
2457:
2410:
2409:
2397:
2396:
2332:
2309:
2308:
2292:
2280:
2233:
2228:
2143:edit warring
2117:
2081:
2074:WikiProjects
2056:Noticeboards
2034:Village Pump
2015:
2002:RfC category
1999:
1952:
1944:
1936:
1895:
1843:
1836:
1833:for advice.
1828:
1824:
1815:
1803:
1801:
1793:
1763:
1756:
1753:
1750:
1736:
1727:
1722:this website
1710:
1701:
1696:
1653:
1647:themselves,
1642:
1639:
1601:
1571:
1546:
1521:
1496:
1471:
1435:
1410:
1385:
1360:
1335:
1310:
1285:
1260:
1235:
1205:
1189:
1170:with either
1167:
1145:
1125:
1042:
996:
963:user conduct
960:
951:
945:
935:
926:
924:
877:WP:Splitting
700:
696:noticeboards
689:
682:
668:
659:
652:WikiProjects
651:
644:
633:
619:WP:RFCBEFORE
586:
572:
561:
553:
516:
512:
510:
454:
449:
445:
443:
219:
214:
210:Noticeboards
63:
2929:{{rfc|xxx}}
2806:Biographies
2608:before the
2522:archive top
2221:WP:RFCCLOSE
2194:Ending RfCs
2181:Ending RfCs
2096:WP:PROPOSAL
2032:One of the
1939:Main page:
1682:WP:RFCBRIEF
1231:Biographies
1120:|econ|bio}}
971:arbitration
887:Peer review
883:Peer review
751:Help needed
683:Peer review
262:Arbitration
64:This is an
2983:Categories
2721:prominent.
2198:See also:
2086:rfc notice
1666:See also:
1197:Categories
1146:Include a
1026:WP:RFCOPEN
946:To report
936:User names
867:WP:Merging
2933:talk page
2792:Articles
2214:WP:RFCEND
2206:Shortcuts
2050:technical
2042:proposals
2026:Yapperbot
1776: 
1674:Shortcuts
1632:WP:RFCCAT
1591:Unsorted
1510:|policy}}
1459:View all)
1223:View all)
1212:View all)
1162:§ Example
1160:tag (see
1045:talk page
1011:Shortcuts
927:user name
723:WP:RFCNOT
703:talk page
640:talk page
611:Shortcuts
564:consensus
545:talk page
393:dashboard
336:proposals
205:Mediation
170:Help desk
82:consensus
2908:Unsorted
2886:(policy)
2623:See also
2277:Duration
2183:are met.
2058:such as
1953:You can
1624:Shortcut
1485:|style}}
1374:|media}}
1063:WP:RFCTP
1055:Shortcut
1019:WP:RFCST
995:You can
977:policy.
715:Shortcut
493:WP:RFC/A
341:idea lab
150:Be civil
125:Requests
96:Shortcut
37:WP:AFC/R
29:WP:RFC/A
2969:Legobot
2880:(style)
2838:(media)
2469:tag in
2187:Mediate
2006:|rfcid=
1927:|rfcid=
1922:|rfcid=
1896:If any
1863:|rfcid=
1585:|prop}}
1560:|tech}}
1535:|proj}}
1424:|reli}}
1324:|lang}}
1299:|hist}}
1274:|econ}}
1184:Legobot
1098:|econ}}
761:help me
743:Problem
557:closing
533:improve
525:process
422:archive
412:history
267:Request
255:Request
232:Request
220:Request
198:Request
175:Request
86:vetting
41:WP:RFCL
2904:(prop)
2898:(tech)
2892:(proj)
2850:(reli)
2826:(lang)
2820:(hist)
2814:(econ)
2552:result
2459:Do not
2152:, and
1881:hour.)
1449:|soc}}
1399:|pol}}
1349:|sci}}
1249:|bio}}
1140:first.
471:, the
326:policy
104:WP:RFC
33:WP:SPI
2856:(soc)
2844:(pol)
2832:(sci)
2808:(bio)
2696:Notes
2616:tag.
2598:line
2322:~~~~~
2306:tag.
2150:civil
2066:, or
2048:(The
2044:, or
2018:watch
1844:Each
1804:below
1604:watch
1574:watch
1549:watch
1524:watch
1499:watch
1474:watch
1438:watch
1413:watch
1388:watch
1363:watch
1338:watch
1313:watch
1288:watch
1263:watch
1238:watch
1179:~~~~~
775:, or
664:page.
595:watch
434:purge
417:watch
2559:~~~~
2360:tag.
2349:tag.
2316:~~~~
1990:~~~~
1983:hist
1950:.
1892:tag.
1877:tag.
1797:diff
1754:five
1751:four
1173:~~~~
1075:and
948:spam
479:and
427:talk
407:edit
402:view
351:misc
331:tech
132:Tips
84:and
2940:rfc
2868:All
2796:All
2783:All
2734:rfc
2711:rfc
2612:rfc
2593:rfc
2518:or
2495:.
2474:or
2465:rfc
2451:tlx
2442:tlx
2433:rfc
2425:rfc
2417:rfc
2402:rfc
2389:rfc
2378:rfc
2356:rfc
2345:rfc
2302:rfc
2286:rfc
2245:rfc
2175:rfc
2163:rfc
2141:or
2098:.
1978:rfc
1916:rfc
1908:rfc
1900:rfc
1888:rfc
1873:rfc
1857:rfc
1848:rfc
1783:rfc
1768:rfc
1757:six
1720:Is
1656:not
1649:not
1613:rfc
1583:rfc
1558:rfc
1533:rfc
1508:rfc
1483:rfc
1447:rfc
1422:rfc
1397:rfc
1372:rfc
1347:rfc
1322:rfc
1297:rfc
1272:rfc
1247:rfc
1156:rfc
1130:rfc
1118:rfc
1110:rfc
1096:rfc
1088:rfc
999:on
909:or
823:or
757:or
581:rfc
575:bot
527:or
517:RfC
450:RfC
346:WMF
2985::
2943:}}
2937:{{
2736:}}
2732:{{
2713:}}
2709:{{
2614:}}
2610:{{
2595:}}
2591:{{
2574:}}
2568:{{
2562:}}
2543:{{
2532:}}
2528:{{
2524:}}
2520:{{
2516:}}
2512:{{
2508:}}
2504:{{
2467:}}
2463:{{
2455:.
2449:{{
2445:}}
2439:{{
2435:}}
2431:{{
2427:}}
2423:{{
2419:}}
2415:{{
2404:}}
2400:{{
2391:}}
2387:{{
2380:}}
2376:{{
2358:}}
2354:{{
2347:}}
2343:{{
2304:}}
2300:{{
2288:}}
2284:{{
2269:}}
2265:{{
2247:}}
2243:{{
2177:}}
2173:{{
2165:}}
2161:{{
2110:.
2088:}}
2084:{{
2062:,
2040:,
1985:}}
1975:{{
1918:}}
1914:{{
1910:}}
1906:{{
1902:}}
1898:{{
1890:}}
1886:{{
1875:}}
1871:{{
1859:}}
1855:{{
1850:}}
1846:{{
1791:.
1785:}}
1781:{{
1770:}}
1766:{{
1739::
1713::
1615:}}
1611:{{
1581:{{
1556:{{
1531:{{
1506:{{
1481:{{
1445:{{
1420:{{
1395:{{
1370:{{
1345:{{
1320:{{
1295:{{
1270:{{
1245:{{
1164:).
1158:}}
1154:{{
1132:}}
1128:{{
1116:{{
1112:}}
1108:{{
1094:{{
1090:}}
1086:{{
845:,
841:,
837:,
819:,
815:,
811:,
807:,
803:,
799:,
763:}}
759:{{
698:.
583:}}
579:{{
573:A
511:A
495:).
483:.
467:,
463:,
360:A
2971:.
2870:)
2866:(
2798:)
2794:(
2785:)
2781:(
2770:e
2763:t
2756:v
2652:.
2635:.
2555:=
2549:|
2526:/
2510:/
2367:.
1981:|
1822:*
1734:N
1708:Y
1606:)
1602:(
1576:)
1572:(
1551:)
1547:(
1526:)
1522:(
1501:)
1497:(
1476:)
1472:(
1457:(
1440:)
1436:(
1415:)
1411:(
1390:)
1386:(
1365:)
1361:(
1340:)
1336:(
1315:)
1311:(
1290:)
1286:(
1265:)
1261:(
1240:)
1236:(
1221:(
1210:(
1122:.
1003:.
956:.
939:.
686:.
673:.
515:(
502:.
491:(
448:(
395:.
296:e
289:t
282:v
269:)
264:(
257:)
252:(
235:)
229:(
223:)
217:(
201:)
195:(
178:)
172:(
127:)
123:(
88:.
68:.
43:.
20:)
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.