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