496:
accidentally excluding significant input or perspectives, or changing the weight of different views, if closed early. Especially, closers should beware of interpreting "early pile on" as necessarily showing how a discussion will end up. This can sometimes happen when a topic attracts high levels of attention from those engaged (or having a specific view) but slower attention from other less involved editors, perhaps with other points of view. It can sometimes be better to allow a few extra days even if current discussion seems very clearly to hold one opinion, to avoid precluding significant input and as a courtesy to ensure that it really will be a snowball.
571:
quality of an argument is more important than whether it comes from a minority or a majority). However, sometimes a requested move is filed in response to a recent move from a long existing name that cannot be undone without administrative help. Therefore, if no consensus has been reached, the closer should move the article back to the most recent stable title. If no recent title has been stable, then the article should be moved to the title used by the first major contributor after the article ceased to be a stub.
567:, should be closed without moving regardless of how many of the participants support it. Remember, the participants in any given discussion represent only a tiny fraction of the Knowledge community whose consensus is reflected in the policy, guidelines and conventions to which all titles are to adhere. Thus, closers are expected to be familiar with such matters, so that they have the ability to make these assessments.
38:
108:
1306:
is suggested), suppressing the creation of a redirect (in the event you forget to suppress the redirect, delete the same); next, move the article to the move target location, again suppressing the redirect and deleting the same if you forget; next, move the redirect from its temporary location to the
652:
Relisting is an option when a discussion cannot otherwise be closed, usually due to lack of consensus. Editors are under no obligation to wait to close a move request after it is relisted. Once a move request has been open for the full seven days, it may be closed at any time by an uninvolved editor.
495:
This clause should not be used to close a discussion when a particular outcome is merely "likely" or "highly likely", and there is a genuine and reasoned basis for disagreement. This is because move discussions are not a vote; it is important to be reasonably sure that there is little or no chance of
720:
There are generally three different outcomes for consensus in requested moves. The closer should clearly show which outcome has taken place so that other editors may quickly see the progression of consensus regarding the title; it is much easier to move an article that has never had a firm consensus
484:
Additionally, when the outcome of the move discussion is, or has become, almost certain, such that there is not a "snowball's chance in hell" that the outcome will be anything other than what is expected, and there is clearly no need at all to prolong discussion further, the discussion may be closed
1298:
For duplicate articles and merged content, or alternatively for cut and paste moves, the page histories of the article and the redirect can be swapped with a round-robin move. For cut and paste moves this leaves a bifurcated history, but has less chance of causing problems. Simply move the redirect
1231:
articles during contentious RM discussions when they believe a premature, undiscussed unilateral move would be disruptive to the discussion. The same discretion should be used to start or continue move protection immediately after the RM close. Generally, such move protection should be limited to
884:
good arguments for it to stay at X.) In these difficult circumstances, the closer should pick the best title of the options available, and then make clear that while consensus has rejected the former title (and no request to bring it back should be made lightly), there is no consensus for the title
773:
would likely result in everyone (or nearly everyone) agreeing that the proposed move should not take place; this notifies other editors that they should probably not propose this move in the future until and unless circumstances change. There is a positive consensus found, and that consensus is for
659:
if a page is added while relisting. Sometimes editors may not realize that to move page A to B, page B must first be moved to C. When a new page move request is added to one that is already seven days old, the RMCD bot places the notification tag on the newly added page that day, and the discussion
449:
In general, move discussions should remain open for at least seven days (168 hours) to allow interested editors adequate time to participate. However, when no one has commented yet, or if opposition is unanimous, discussions may be closed prior to the seven-day timeframe for the following reasons:
784:
a consensus to keep the current title. This may be because a discussion has fractured into several possible titles and none seem especially suitable, or simply because equally strong arguments and appeals to
Knowledge policy and outside sources were found on both sides, without any clear reason to
526:
is determined not just by considering the preferences of the participants in a given discussion, but also by evaluating their arguments, assigning due weight accordingly, and giving due consideration to the relevant consensus of the
Knowledge community in general as reflected in applicable policy,
1182:
template may be added to the top of the talk page (or updated if already present), allowing editors to see previous move discussions that might otherwise be archived. This is helpful for titles that are likely to be challenged again, so that any would-be re-proposer can make reference to previous
269:
An involved editor may comment in a move discussion, solicit a closure, or make a new move request at a later date, but may not close an open move request. When you are an involved editor, trust the process and leave the close to one of the many, many other editors on
Knowledge who are capable of
327:
Non-administrators are reminded that closing a discussion calls for an impartial assessment of consensus or lack thereof, although arguments supported by directly relevant policy and guidelines are given more weight (while keeping broader
Knowledge policy, guidelines, and consensus in mind). Any
570:
If objections have been raised, then the discussion should be evaluated just like any other discussion on
Knowledge: lack of consensus among participants along with no clear indication from policy and conventions normally means that no change happens (though like AfD, this is not a vote and the
1612:
will appear on a talk page. When this happens, the bot will link to the first one, even if the current move request is the second one. This can be remedied by giving the section containing the current move request a different name, such as "Requested move 2", or by giving the older section a
797:
considered bad form to re-raise a request that found "no consensus" to move. (Successful move re-requests generally, though not always, take place at least three months after the previous one. An exception is when the no-consensus move discussion suggests a clear, new course of action.)
1226:
Some RM discussions are contentious; undiscussed, unilateral page moves during a discussion or page moves made immediately after and contrary to an RM close decision are disruptive and hurt the integrity of the RM process. Admins monitoring RM discussions should use their discretion to
841:
But sometimes things get complicated. Alice proposes moving X to Y, but then Bob raises real concerns about Y, and proposes Z instead. Carol says, no, we should stay with Y. Dave says we actually need to keep the article at X. Edgar shows up and is very confused. What does he do?
370:), such as updating fair-use rationales and navbox links included on the page. If a non-admin closer is not willing to wait for the technical deletion and to perform the follow up in this manner, they should only close requested moves that do not require technical intervention.
1399:
If a page is to be moved as the result of a move request, mention should be made of this in the move proposal and a notice should be placed on the talk page of the article to be moved (unless of course it is hosting the discussion). Generally, a move request on whether to move
355:, and affirmed there. While non-admins should be cautious (as indeed all move closers should be) when closing discussions where significant contentious debate among participants is unresolved, any experienced and uninvolved editor in good standing may close any RM debate.
362:
with a link to the closed discussion. The results of discussions in favor of moves should generally be respected by the administrator (or page mover). If an administrator notices a clearly improper move closure, they should revert the closure and re-open the discussion.
604:
Therefore, if a page has been moved from a long-standing title, and it is not possible to move the page back to its original title during the discussion, the default title will be the title prior to the contested move. For example, if an article is created at
410:
page swap. A user is granted the page mover right after demonstrating a good understanding of the
Knowledge page naming system and decent page moving experience. Since closure by a page mover is a type of non-admin closure, it should be labeled as such using
1593:
Unusually formatted signatures will prevent recognizing the end of the proposal description, for example, if the date is formatted Month Day, Year instead of Day Month Year. This can be fixed by editing the timestamp or adding a formatted time
939:}}. You should also add and sign a comment to indicate whether the move was accepted or rejected in the discussion area for the requested move. To ease things a little bit, there are several scripts that can help, with the most common being
1422:
that mentions moving Z as a possibility. This is because the editors most interested and aware of Z are not able to contribute their expertise to the naming discussion, since it's happening at a different place without any notice given.
351:), but assuming the criteria above are met, the mere fact that the closer was not an admin is not sufficient reason to reverse a closure. Indeed, many high-profile, controversial move requests have been closed as NACs, taken to
1291:. On rare occasions, this procedure will not work correctly. Once a history merge is done, it cannot easily be undone, so don't pick this option unless it is definitely the right one. You can request history merges at
837:
Most move requests are simple. Alice proposes that we move X to Y. Bob, Carol and Dave chime in. Edgar analyzes the discussion and decides whether there is a consensus, and then gives one of the three outcomes above.
311:
Experienced and uninvolved registered editors in good standing are encouraged to close requested move discussions. Any non-admin closure (NAC) must be explicitly declared with an appropriate template (such as
683:
Where a discussion would result in the original title pointing to a "Foo (disambiguation)" page, the practice of pagemovers has been to immediately move the disambiguation page to the base page name, per
1273:
attribution. There are three ways to deal with target pages with major histories, dependent on circumstances. In the event this situation presents itself on a move, click "show" below for instructions.
889:
to provide an explicit closing statement in such closures. As this result does not indicate a consensus for the chosen title, anyone who objects to the closer's decision may make another move request
1446:
that a move request involving that page is taking place. This often leads to strife and another, more contentious move request. If consensus at X signals that Z should move, close the request at
366:
In any case where a non-admin closer does resort to a technical move request, the closer should actively monitor that request, and be ready and willing to perform all tidying after the move (as
176:
discussions. These should generally be applied only after the normal seven-day listing period has elapsed. These suggestions are addressed to formal move requests that occur on talk pages, i.e.
1288:
1183:
arguments and consider how a consensus may be formed to move. In the case of pages with multiple move discussions, these templates should always be added/updated after the closure of an RM.
1307:
title at which the article you just moved was formerly located. At this point the redirect will be pointing at itself; re-target it to point to the new location of the article. See also
1257:
page history, generally meaning it only existed as a redirect, and was never a duplicate article, never had content that was cut and pasted to the present title, nor merged there,
591:
preserves the most recent stable title. If there is no prior stable title, then the default is the title used by the first major contributor after the article ceased to be a
1434:, and someone mentions that they think the barge is actually the primary topic. A consensus of these barge enthusiasts may then informally suggest that the existing article
954:
While historically, there have been other options for closing the move request survey on the affected article's talk page, nowadays we exclusively use the twin templates
747:"). This almost always sets a consensus for the new title, and further requests to move the page are likely to fail unless new information or arguments are brought forth.
406:
Editors with the page mover permission can perform certain technical moves without administrator assistance, such as a move over a redirect with more than one edit via a
180:
move requests, but are instructive as to the necessary page history investigation and preservation and cleanup procedures advisable upon any move. Requests listed in the
1629:
Note that these criteria are significantly stricter than the criteria listed at WP:INVOLVED; this is intentional, befitting the less urgent nature of requested moves.
358:
Occasionally, a move involves a redirect with multiple revisions, and requires technical intervention. Editors are permitted to close the discussion and file a
617:, and a move request is filed leading to a decision of "no consensus", the article must be moved back to its longstanding title. This is the case even if the
185:
181:
1590:) between the proposed move and the proposal description will prevent the description from appearing. This can be fixed by simply adding the missing endash.
676:
A move request about moving X to Y should never be closed in such a way as to require page Z to move if Z wasn't listed in the original move request (see
277:
for an impartial administrator to assess consensus. The closer should be familiar with all relevant policies and guidelines (especially those relating to
660:
must go a full seven days (more) before being closed. It is helpful to closers when relisters leave a note just below the nomination that this happened.
331:
Anyone, administrator or not, who wishes to close a requested move must be very familiar with the policies and guidelines associated with it (especially
1516:
It is OK to change the auto-generated level 2 header to a level 3 header, thus making the RM section a sub-section of an earlier-started discussion.
205:
140:
1583:
comment from the end of the line – the bot allows up to 23 bytes following the timestamp at the end of the line, and that comment is 26 bytes long.
1052:
If additional explanation is provided as to why you have closed the move discussion as a certain result, add additional comments immediately after
343:), and ideally will have participated in several move requests previously. All closures of requested moves are subject to being taken to review at
1573:, you must place today's time/date stamp for this to remedy the problem, so you can use the form {{subst:unsigned|Foo|~~~~~}}, and note this uses
785:
move the page found in the discussion. Of course, as elsewhere on
Knowledge, this usually means that no action is to be taken at the present time.
1249:
to the present names. Whether a redirect or otherwise, that existing target title should be investigated to see whether it has a minor or major
1645:
1292:
845:
If you as a closer are in doubt because too many titles have been proposed and there's no real consensus anywhere, it is generally best to
1083:
Subsequent comments should be made in a new section on the talk page. Editors desiring to contest the closing decision should consider a
885:
actually chosen. Because such closures are inherently complex and require the closer to use more independent judgment than normal, it is
1655:
1318:
Another option is for redirect pages with major histories to be archived into a talk namespace, and a link then placed on the article's
1346:
58:
688:. This is because a disambiguation page is presumed to belong at the base page name unless that title is taken by a primary topic.
1563:
The move request is not signed. Sign the move request, and the problem is solved. If you are signing for someone else and you use
978:
After clicking the tab next to the move discussion, you may follow these step-by-step instructions for closing an RM discussion:
872:
But then again, there are situations where multiple names have been proposed and no consensus arises out of any, except that it
944:
184:
section can be simply removed after they have been processed. Where technical moves are contested, move the listing to the
1508:
1153:
Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
920:
911:
597:
583:
559:
or is otherwise in conflict with applicable guidelines or policy. Further, any move request that is out of keeping with
555:
for requested moves. If no one has objected, go ahead and perform the move as requested unless it is out of keeping with
1599:
In the first case, December 20, 2012 was changed to 20 December 2012, in the second case, a second time stamp was added.
1372:
Fixing any mistargeted wikilinks resulting from the move (only applies when the move involves a change to primary topic)
560:
556:
630:
1416:
1287:
way to fix this is to merge the page history of the present article and the redirect, using the procedure outlined at
933:
46:
1609:
274:
1577:
tildes to place the time stamp, or the actual timestamp can be copied from history - but adding (UTC) is required.
1431:
262:
You have ever commented on any talk page in a way that has indicated a clear position on the specific move request
1559:– rather than manually format the request yourself – to avoid this issue. Possible causes and solutions include:
1548:
1501:– rather than manually format the request yourself – to avoid this issue. Possible causes and solutions include:
1490:
1192:
1074:
948:
940:
646:
487:
474:
173:
50:
17:
57:
This page provides additional information about concepts in the page(s) it supplements. This page is not one of
1650:
1613:
different name, like "Requested move (month year)". A duplicate header for the same discussion can be deleted.
1232:
no more than 30 days under normal circumstances. The RM closing comment should reference the move protection.
880:
host the article. (There are good arguments for Y, and there are good arguments for Z, but there are virtually
336:
332:
282:
278:
285:) as well as the procedures described on this page. Do not ask for a specific closer under any circumstances.
1554:
1496:
1367:
1136:
1114:
1505:
The request was appended to an existing talk page section. Add a new section header immediately above the
1323:
588:
1206:
1084:
563:
or is otherwise in conflict with applicable guideline and policy, unless there is a very good reason to
344:
197:
1551:
when the listing bot cannot ascertain the date on which the request was made. Please remember to use
1312:
1270:
626:
379:
328:
editor wishing to express an opinion on the requested move should join the discussion, not close it.
252:
1351:
You should not close any move if you are unwilling to do the necessary clean up tasks described at
1319:
807:
685:
575:
523:
340:
125:
62:
1087:
after discussing it on the closer's talk page. No further edits should be made to this discussion.
743:
481:
Under those two circumstances, it is fine for the closer to have been involved in the discussion.
1520:
1474:
1427:
1382:
1352:
1331:
1246:
1176:
1162:
967:
855:
813:
770:
697:
531:
506:
432:
389:
294:
224:
162:
155:
72:
668:
A relister may later become a participant or closer in the requested move discussion or survey.
191:
Failure of an RM closer to follow the spirit and intent of these instructions, especially about
1439:
1567:
1527:
1327:
1250:
1132:
1110:
273:
If you wish to solicit a closure after at least a week of discussion has taken place, you can
1587:
1195:
page and delete the article's entry there; this will be performed automatically by a bot.
957:
927:
317:
256:
151:
1493:
when the listing bot fails to successfully interpret the request. Please remember to use
121:
If you are not an administrator you should be cautious when closing contentious requests;
637:
took over through consensus and can be determined to be the actual long-standing title.
1308:
1221:
905:
When you complete an entry on the project (whether the move was accepted or rejected),
610:
592:
416:
412:
407:
383:
359:
313:
248:
144:
23:
1639:
1360:
1199:
894:
564:
352:
348:
1128:
1106:
462:
of a move may withdraw their request. The closure should say that the request was
1191:
Once the article's talk page has been updated, there's no need to return to the
265:
Your editing on the page has demonstrated a clear position on the move request
1465:
except in the very clearest and not-even-plausibly controversial situations.
849:
and allow someone to re-propose the move to a more specific or better title.
766:
740:
title it should be moved to, please note this in the closing summary (e.g. "
893:, and is advised to create such a request instead of taking the closure to
1523:. Only pages with non-redirecting content should be requested to be moved.
1443:
634:
606:
1442:, without actually notifying Foobar-interested editors by signaling at
1366:
Updating any navigational templates to link directly to the new title,
1269:
be simply deleted, as we need to retain such page histories for proper
622:
614:
765:
rename the article(s) in question. For instance, a proposal to rename
653:
Closers wait mainly for general agreement, for consensus, to emerge.
244:
You have ever closed a previous controversial request to move the page
1455:
1447:
1124:
210:
helpful when considering the technical task of closing a discussion.
736:
found to rename the page. If there is any question whatsoever as to
251:
moved the page to a title you prefer (i.e., not including reverting
316:}}) placed directly after the reasoning for the close within the {{
193:
properly weighing consensus with applicable policies and guidelines
1245:
The majority of target names for move requests already exist as
1216:
Using move protection during RMs and immediately after RM closes
793:
found against it (until and unless circumstances change), it is
231:
close a move request (with certain exceptions, detailed below).
789:
While it is usually bad form to re-request a move if consensus
1435:
1120:
580:
102:
32:
1463:
do not move articles that have not been nominated to be moved
1330:
and later archived, when the original article was moved from
241:
You have ever supported or opposed a request to move the page
1283:
For page histories resulting from cut and paste moves, the
1530:
the timestamp must adhere to the system-generated format (
1289:
Knowledge:Administrators' guide/Fixing cut-and-paste moves
587:
When article title discussions end without consensus, the
131:
Investigate the page history of the target page title; if
1451:
1409:
1405:
1401:
1326:, which was originally created as a duplicate article at
780:
should be used when there is neither a consensus to move
1461:
Even if consensus is clear, when closing a move request
1355:. Some of the most commonly required cleanup tasks are:
645:
For the instructions on relisting move discussions, see
1596:
1390:
863:
828:
821:
705:
539:
514:
469:
Further, any editor may end such a move request with a
440:
397:
302:
87:
80:
647:
Knowledge:Requested moves § Relisting a requested move
1543:
A request will be listed in a special section titled
1485:
A request will be listed in a special section titled
1067:
After closing, the page should look similar to this:
1001:
Leave the heading alone; the close starts below it.
454:
As long as no one has suggested any outcome besides
1061:
Closing requested move survey; page moved/not moved
227:editor, whether an administrator or otherwise, may
128:
on the request or relist it for further discussion;
100:Explanatory essay about Knowledge:Requested moves
150:Close the move request on the talk page using {{
118:Don't close requested moves if you are involved;
367:
238:You have ever opened a request to move the page
147:, or archive and place a link on the talk page;
8:
1278:Procedure for redirects with major histories
1059:Save the page with an edit summary such as "
1359:Updating the article prose (including the
1299:with a major history to a temporary name (
1073:The following is a closed discussion of a
715:
192:
172:The following are suggestions for closing
1020:Replace text on left with text on right.
876:determined that the current title should
677:
609:and stays there for years prior to being
1608:Occasionally two sections with the same
1261:However, if the target page title has a
1212:from the page itself within 15 minutes.
1035:Body of the discussion stays unchanged.
980:
692:Write a clear, concise closing statement
1622:
1473:Please report unresolved incidents at
1412:'s title, unless it is initiated as a
1100:
802:Discussions involving multiple options
420:
321:
774:the page to stay exactly where it is.
761:formed to keep the current title and
7:
1519:The page requested to be moved is a
1426:These situations often come up when
1293:Knowledge:Requests for history merge
1092:The result of the move request was:
551:No minimum participation is required
423:parameter in the closing template).
324:parameter in the closing template).
195:, may result in the initiation of a
186:contested technical requests section
1322:. (An example of such a page is at
527:guidelines and naming conventions.
1347:Knowledge:Cleaning up after a move
757:) should be used when a consensus
576:Knowledge:Consensus § No consensus
63:thoroughly vetted by the community
59:Knowledge's policies or guidelines
31:
1581:<!-- Template:Unsigned --: -->
1454:, and file a new move request at
631:orangutan-flavored soft drink can
473:if the request was initiated via
1241:Edit history of destination page
1172:After the move is complete, the
1149:The discussion above is closed.
732:) should be used when consensus
234:You are considered involved if:
106:
36:
1545:"Time could not be ascertained"
1539:"Time could not be ascertained"
945:User:DannyS712/PageMoverClosure
1408:should have no impact on page
1168:to the talk page if so desired
1137:21:27, 29 September 2024 (UTC)
1115:21:27, 29 September 2024 (UTC)
974:Step-by-step closing procedure
1:
1534:) and must not be customized.
1430:is proposed to move to, say,
1006:{{Requested move/dated|Foo}}
419:}} or equivalent (or use the
214:Who can close requested moves
1646:Knowledge supplemental pages
1432:Foo (enormous sailing thing)
1009:{{subst:RM top|'''RESULT.'''
664:Relisting and participating
1672:
1656:Administrator instructions
1472:
1380:
1368:rather than via a redirect
1344:
1341:Cleaning up after the move
1219:
1127:– rationale of nominator.
901:Closing the requested move
853:
811:
805:
713:
695:
644:
529:
504:
430:
387:
377:
292:
270:closing move discussions.
70:
1549:Knowledge:Requested moves
1491:Knowledge:Requested moves
1259:it may simply be deleted.
1193:Knowledge:Requested moves
1045:Add the bottom template.
949:User:Andy M. Wang/closeRM
941:User:TheTVExpert/rmCloser
174:Knowledge:Requested moves
51:Knowledge:Requested moves
18:Knowledge:Requested moves
1151:Please do not modify it.
1080:Please do not modify it.
962:result of the discussion
672:Only move involved pages
337:Knowledge:Disambiguation
333:Knowledge:Article titles
320:}} template (or use the
135:, it may be deleted; if
114:This page in a nutshell:
716:§ Determining consensus
574:Note that according to
374:Closure by a page mover
163:clean up after the move
1532:HH:MM, D MM YYYY (UTC)
1324:Talk:Network SouthEast
917:tag from the talk page
24:Knowledge:OTHEROPTIONS
1363:) to use the new name
847:close as no consensus
755:consensus not to move
714:Further information:
501:Determining consensus
378:Further information:
219:Conflicts of interest
1555:subst:Requested move
1509:Requested move/dated
1497:subst:Requested move
1487:"Malformed requests"
1377:Moves of other pages
1042:{{subst:RM bottom}}
912:requested move/dated
380:Knowledge:Page mover
998:==Requested move==
995:==Requested move==
887:strongly encouraged
621:page was placed at
341:Knowledge:Consensus
253:page move vandalism
61:as it has not been
1481:Malformed requests
1475:User talk:RMCD bot
1469:Bot considerations
1417:multi-move request
1332:Network South East
1265:history it should
1187:Automatic removals
864:WP:NOTCURRENTTITLE
561:naming conventions
557:naming conventions
182:technical requests
1328:Network SouthEast
1236:Moving procedures
1104:
1101:non-admin closure
1049:
1048:
730:consensus to move
721:about the title.
602:
601:
589:applicable policy
289:Non-admin closure
257:technical request
204:Closers may find
170:
169:
98:
97:
47:explanatory essay
22:(Redirected from
1663:
1630:
1627:
1604:Header confusion
1598:
1582:
1579:Also remove the
1572:
1566:
1558:
1533:
1512:
1500:
1421:
1415:
1393:
1391:WP:NOTOTHERPAGES
1305:
1211:
1205:
1202:will remove the
1181:
1175:
1167:
1161:
1143:Supports/Opposes
1105:
1098:
1082:
1062:
1016:
1014:
981:
965:
916:
910:
866:
831:
824:
822:WP:NOGOODOPTIONS
708:
706:WP:THREEOUTCOMES
581:
553:
552:
542:
517:
485:early under the
471:procedural close
443:
422:
400:
368:instructed below
323:
305:
255:or performing a
161:If renamed then
110:
109:
103:
90:
83:
40:
39:
33:
27:
1671:
1670:
1666:
1665:
1664:
1662:
1661:
1660:
1651:Requested moves
1636:
1635:
1634:
1633:
1628:
1624:
1619:
1610:section heading
1606:
1595:
1586:A missing "–" (
1580:
1570:
1564:
1552:
1541:
1531:
1506:
1494:
1483:
1478:
1471:
1419:
1413:
1397:
1396:
1389:
1385:
1379:
1349:
1343:
1338:
1337:
1300:
1279:
1243:
1238:
1224:
1218:
1209:
1203:
1189:
1179:
1173:
1170:
1165:
1159:
1155:
1154:
1145:with discussion
1097:
1078:
1060:
1012:
1010:
984:Before closing
976:
968:subst:RM bottom
955:
934:requested move/
921:requested move/
914:
908:
903:
870:
869:
862:
858:
835:
834:
829:WP:OTHEROPTIONS
827:
820:
816:
810:
804:
718:
712:
711:
704:
700:
694:
674:
666:
650:
643:
627:fizzy drink can
550:
549:
546:
545:
538:
534:
521:
520:
513:
509:
503:
488:snowball clause
447:
446:
439:
435:
429:
404:
403:
396:
392:
386:
376:
309:
308:
301:
297:
291:
221:
216:
156:subst:RM bottom
107:
101:
94:
93:
86:
79:
75:
67:
66:
37:
29:
28:
21:
20:
12:
11:
5:
1669:
1667:
1659:
1658:
1653:
1648:
1638:
1637:
1632:
1631:
1621:
1620:
1618:
1615:
1605:
1602:
1601:
1600:
1591:
1584:
1578:
1540:
1537:
1536:
1535:
1524:
1517:
1514:
1482:
1479:
1470:
1467:
1450:, do not move
1395:
1394:
1386:
1381:
1378:
1375:
1374:
1373:
1370:
1364:
1361:first sentence
1342:
1339:
1336:
1335:
1316:
1296:
1280:
1277:
1276:
1253:. If it has a
1242:
1239:
1237:
1234:
1217:
1214:
1188:
1185:
1169:
1156:
1148:
1147:
1146:
1118:
1090:
1089:
1075:requested move
1069:
1065:
1064:
1057:
1047:
1046:
1043:
1040:
1037:
1036:
1033:
1028:
1022:
1021:
1018:
1007:
1003:
1002:
999:
996:
992:
991:
988:
987:After closing
985:
975:
972:
919:, or change {{
902:
899:
868:
867:
859:
854:
833:
832:
825:
817:
812:
803:
800:
787:
786:
775:
748:
710:
709:
701:
696:
693:
690:
673:
670:
665:
662:
642:
639:
600:
599:
596:
585:
544:
543:
535:
530:
519:
518:
510:
505:
502:
499:
498:
497:
479:
478:
467:
445:
444:
436:
431:
428:
425:
402:
401:
393:
388:
384:Template:RMnac
375:
372:
360:technical move
345:WP:Move review
307:
306:
298:
293:
290:
287:
283:disambiguation
279:article titles
275:make a request
267:
266:
263:
260:
247:You have ever
245:
242:
239:
220:
217:
215:
212:
168:
167:
166:
165:
159:
148:
129:
122:
119:
111:
99:
96:
95:
92:
91:
84:
76:
71:
68:
56:
55:
43:
41:
30:
15:
14:
13:
10:
9:
6:
4:
3:
2:
1668:
1657:
1654:
1652:
1649:
1647:
1644:
1643:
1641:
1626:
1623:
1616:
1614:
1611:
1603:
1597:
1592:
1589:
1585:
1576:
1569:
1562:
1561:
1560:
1556:
1550:
1546:
1538:
1529:
1525:
1522:
1518:
1515:
1510:
1504:
1503:
1502:
1498:
1492:
1488:
1480:
1476:
1468:
1466:
1464:
1459:
1457:
1453:
1449:
1445:
1441:
1437:
1433:
1429:
1424:
1418:
1411:
1407:
1403:
1392:
1388:
1387:
1384:
1376:
1371:
1369:
1365:
1362:
1358:
1357:
1356:
1354:
1348:
1340:
1333:
1329:
1325:
1321:
1317:
1314:
1313:WP:ROUNDROBIN
1310:
1304:
1297:
1294:
1290:
1286:
1282:
1281:
1275:
1272:
1268:
1264:
1260:
1256:
1252:
1248:
1240:
1235:
1233:
1230:
1223:
1215:
1213:
1208:
1201:
1196:
1194:
1186:
1184:
1178:
1164:
1157:
1152:
1144:
1141:
1140:
1139:
1138:
1134:
1130:
1126:
1122:
1117:
1116:
1112:
1108:
1102:
1095:
1088:
1086:
1081:
1076:
1071:
1070:
1068:
1058:
1055:
1054:'''RESULT'''.
1051:
1050:
1044:
1041:
1039:
1038:
1034:
1032:
1029:
1027:
1024:
1023:
1019:
1008:
1005:
1004:
1000:
997:
994:
993:
989:
986:
983:
982:
979:
973:
971:
969:
963:
959:
952:
950:
946:
943:(followed by
942:
938:
937:
931:
930:
925:
924:
918:
913:
900:
898:
896:
892:
888:
883:
879:
875:
865:
861:
860:
857:
852:
850:
848:
843:
839:
830:
826:
823:
819:
818:
815:
809:
801:
799:
796:
792:
783:
779:
776:
772:
768:
764:
760:
756:
752:
749:
746:
745:
739:
735:
731:
727:
724:
723:
722:
717:
707:
703:
702:
699:
691:
689:
687:
681:
679:
671:
669:
663:
661:
658:
654:
648:
640:
638:
636:
633:, as long as
632:
628:
624:
620:
616:
612:
608:
594:
590:
586:
582:
579:
577:
572:
568:
566:
562:
558:
554:
541:
537:
536:
533:
528:
525:
516:
512:
511:
508:
500:
494:
493:
492:
490:
489:
482:
476:
475:block evasion
472:
468:
465:
461:
457:
453:
452:
451:
442:
438:
437:
434:
427:Early closure
426:
424:
418:
414:
409:
399:
395:
394:
391:
385:
381:
373:
371:
369:
364:
361:
356:
354:
350:
346:
342:
338:
334:
329:
325:
319:
315:
304:
300:
299:
296:
288:
286:
284:
280:
276:
271:
264:
261:
258:
254:
250:
246:
243:
240:
237:
236:
235:
232:
230:
226:
218:
213:
211:
209:
208:
202:
200:
199:
194:
189:
187:
183:
179:
178:controversial
175:
164:
160:
157:
153:
149:
146:
142:
141:history merge
138:
134:
130:
127:
123:
120:
117:
116:
115:
112:
105:
104:
89:
85:
82:
78:
77:
74:
69:
64:
60:
53:
52:
48:
42:
35:
34:
25:
19:
1625:
1607:
1574:
1544:
1542:
1486:
1484:
1462:
1460:
1438:be moved to
1425:
1398:
1350:
1302:
1284:
1266:
1262:
1258:
1254:
1251:page history
1244:
1229:move protect
1228:
1225:
1207:Title notice
1197:
1190:
1171:
1150:
1142:
1119:
1093:
1091:
1079:
1072:
1066:
1053:
1030:
1025:
990:Description
977:
961:
958:subst:RM top
953:
935:
928:
922:
906:
904:
890:
886:
881:
877:
873:
871:
851:
846:
844:
840:
836:
808:WP:Bartender
794:
790:
788:
781:
778:No consensus
777:
762:
758:
754:
750:
744:Squeezy José
741:
737:
733:
729:
725:
719:
686:WP:MALPLACED
682:
675:
667:
656:
655:
651:
618:
603:
573:
569:
565:ignore rules
548:
547:
522:
486:
483:
480:
470:
463:
459:
455:
448:
405:
365:
357:
330:
326:
318:subst:RM top
310:
272:
268:
233:
228:
222:
206:
203:
196:
190:
177:
171:
152:subst:RM top
145:history swap
139:, perform a
136:
132:
113:
44:
1428:Foo (barge)
1353:WP:POSTMOVE
1345:Main page:
1301:Draft:Move/
1085:move review
907:remove the
895:move review
891:at any time
771:Squeezy Joe
417:subst:RMpmc
413:subst:RMnac
408:round-robin
314:subst:RMnac
198:Move Review
45:This is an
1640:Categories
1528:WP:SIGPROB
1220:See also:
1198:Likewise,
1031:DISCUSSION
1026:DISCUSSION
806:See also:
657:Exception:
540:WP:RMNOMIN
456:not moving
207:this guide
124:Determine
88:WP:RMCLOSE
1513:template.
1440:Foo (bar)
1320:talk page
1271:copyright
1247:redirects
1177:Old moves
1163:Old moves
814:Shortcuts
767:Bob Dylan
751:Not moved
742:moved to
641:Relisting
613:moved to
611:WP:BOLDly
524:Consensus
515:WP:RMCIDC
464:withdrawn
154:}} and {{
126:consensus
73:Shortcuts
1568:Unsigned
1521:redirect
1444:Talk:Foo
1383:Shortcut
1200:RMCD bot
926:}} to {{
856:Shortcut
698:Shortcut
635:soda can
619:original
607:Soda can
532:Shortcut
507:Shortcut
460:proposer
433:Shortcut
398:WP:RMPMC
390:Shortcut
303:WP:RMNAC
295:Shortcut
225:involved
1309:WP:SWAP
1285:correct
1222:WP:MOVP
1129:Example
1107:Example
1015:nac=yes
623:pop can
615:pop can
441:WP:RMEC
81:WP:RMCI
1594:stamp.
1588:endash
1456:Talk:Z
1448:Talk:X
1125:Foobar
1094:RESULT
966:and {{
458:, the
415:}}, {{
353:WP:MRV
349:WP:MRV
339:, and
249:boldly
49:about
1617:Notes
1267:never
1263:major
1255:minor
929:subst
923:dated
738:which
726:Moved
678:below
421:|pmc=
322:|nac=
137:major
133:minor
16:<
1575:five
1526:Per
1311:and
1303:NAME
1158:Add
1133:talk
1111:talk
1096:. .
970:}}.
947:and
753:(or
728:(or
680:).
593:stub
382:and
281:and
1547:on
1489:on
1436:Foo
1404:to
1121:Foo
1017:}}
964:.}}
951:).
936:end
878:not
795:not
782:nor
769:to
763:not
759:has
629:or
625:or
229:not
223:An
158:}}.
1642::
1571:}}
1565:{{
1557:}}
1553:{{
1511:}}
1507:{{
1499:}}
1495:{{
1458:.
1420:}}
1414:{{
1334:).
1210:}}
1204:{{
1180:}}
1174:{{
1166:}}
1160:{{
1135:)
1123:→
1113:)
1077:.
1063:".
1013:pm
956:{{
915:}}
909:{{
897:.
882:no
874:is
791:is
734:is
598:”
595:.
584:“
578::
491:.
411:{{
335:,
312:{{
201:.
188:.
143:,
54:.
1477:.
1452:Z
1410:Z
1406:Y
1402:X
1315:.
1295:.
1131:(
1109:(
1103:)
1099:(
1056:.
1011:|
960:|
932::
649:.
477:.
466:.
347:(
259:)
65:.
26:)
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.