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