Knowledge

:Move review/Log/2012 November - Knowledge

Source đź“ť

218:
information to comets, bridges and airports. That is the disruption - changing hundreds to thousands of articles to inappropriate titles by using endashes where hyphens should be used, and I take strong offense to the word disruption being used in connection with someone who is obviously simply correcting an obvious error in Knowledge. Disruption is not a word that should be thrown out in such a casual manner. There are disruptions to Knowledge, what I am doing is not one of them, and even if ten people vote that someone is being disruptive in proposing say that France should be moved to F'*&ing Fyz, the closer should be level headed enough to use the closing argument "no consensus", or something, because of the pejorative context of the word "disruptive". As I said before, if someone thinks they need to use the word disruptive in a closing remark, they should not be doing the close. Admins are required to remain level headed, and when they can not do that, they need to recuse themself.
1895:. Not the best RM, I agree – it would have been much better had there been more participation, but reading over it I stand by my closure. The nominator gives a very reasonable rationale for moving the article and in the month that the RM was open (three weeks longer than usual) no one offered a good counter argument (it was pretty much "someone will get around to it sometime"). The one person who actively opposed withdrew his opposition and the other editor to comment (Lihaas) said he would add prose within a week – by the time I closed it, almost a month later, that had not been done and I therefore found the nominator's argument compelling enough for there to be a consensus to move. I will add that I think, because the first RM had so little participation, there should be no prejudice against starting a new RM, but the article should not be moved back unless there is a consensus. 182:
uphill battle which might not be won, and finally, even a speedy close should not be done in less than 19 hours over the weekend, when Knowledge traditionally has less traffic. Comets, of the four ways that MOS advocates have been inappropriately applying endashes, is the most inappropriate, because there is actually a naming authority that names comets the same way they name planets - with only spaces and hyphens (after a name is given). In these move requests we always have a half a dozen or so MOS editors who want to enforce their view of how things should be spelled, regardless of common sense. While they made a perfectly logical decision, they came to a completely illogical conclusion. It happens. Someone simply needs to point that out. There is no reason for a few editors to think they have any right to tell all of the rest of us how to spell things.
1211:
anything about airports is misnamed and needs to be returned to its original name. Pejoratives have no place in Knowledge. We always need to be fair and unbiased and always assume good faith. The closing admin, should this pattern persist, should be removed of their adminship. The closing admin was not capable of forming an unbiased opinion clearly having an ax to grind against the editor opening the RM, and should have had the wisdom to recuse themself from performing the close. There are about 800 active admins, so why would the one and only admin who has an ax to grind against this editor be the one who felt compelled to be the one and only admin to close this RM?
437:
Articles have half a dozen equally valid choices, if not even hundreds. What is patently absurd is I am trying to get people to end sentences with periods and capitalize the first words in sentences, and there are two or three editors running around insisting on misspelling comets. Obviously there is nothing wrong with fixing them as I am attempting, and obviously it is inappropriate to shut off discussion by pretending there is a consensus to misspell anything. There are
1058:. Obviously airports are spelled with hyphens. There are over 9,000 airports around the world, many of which are spelled with hyphens, but none which are spelled with endashes. This is obvious to anyone who knows very much about airports, and those who are guessing should not be stating opinions instead of facts. The reason this was opened immediately is because the previous MRV was closed as no consensus, with the only admin voting having voted to overturn the close. 198:
unable to get consensus for your preferred treatment of dashes and hyphens at the manual of style, kindly stop pursuing moves contrary to that consensus. That an unbiased admin came to the discussion and found your approach to be disruptive does not magically bias that admin. Noting that a disruptive request is being closed as disruptive is not evidence of a problem in the close, but of a problem in the request. --
1943:) is not justification for thus naming an article that echoes the layout, but not the prose content, of such articles. I repeat that I would happily support a return to the original name as soon as it can be seen that there is some concerted effort to make the article fit such a description. This is about the principle that an article title should not lead to expectations that are not fulfilled by the content. 320:"Suppose we all decide to use commas at the end of sentences..." is a straw man, since no one uses commas as period-substitutes just because their keyboard lacks an easy way to enter periods. It is not the same in principle or practice. If you want to help, get consensus for a new MOS guidelines on endashes and hyphens before making more of the disruptive move requests. -- 1505:
for what he is trying to do, and his continuing repetitive efforts are certainly disruptive to people trying to do normal edits and improvements in line with the guidelines such as the MOS. I had warned him (before these closes) that if he opens any more such RMs I will take him to AN/I and seek a block; yes, it has gone that far, in 3 months of continuing disruption.
357:. Plus it is never disruptive to correct an error. Sure it takes time to address, but that is why Knowledge is a wiki, so that anyone can suggest changes. To define certain changes (when they are correct) as not permitted is absurd. We do need to discuss the endash/hyphen issue, but not at the expense of putting endashes into articles that do not use endashes. 306:
hurt the credibility of the encyclopedia? Using dashes where hyphens should be used is no different than using commas instead of periods at the end of sentences - in principle. If anyone wants everyone to follow the MOS we need to have it follow common usage. Otherwise we create a conflict between policy and guideline, and in that case, policy always wins.
1876:
The original discussion was proposed and supported by only the proposer, there were 2 others who did not support it. It was then somehow closed citing consensus to move. In the ;ast 2 days again the original proposer is the only one who sticks to the need to mvoe, while two editors agree there was no
1257:
I am stating that the closing admin should not be closing discussions which they are involved in, and that due to the recent interaction with this editor are clearly not able act responsibly. Why would this one admin out of 800 be the one to do the close? This is not a coincidence. Reopen the RM, and
2038:
I didn't want it to be moved and hoped it would work as a Chronological Summary. I did some work in that direction and if Lihaas wishes to complete that I'd be happy. However it is correct that I withdrew my objection as it seemed the work needed to make it different than a list of event winners did
1504:
and disruption situation here, and calling a spade a spade. The early close was called for by several respondents, and was clearly justified. JHunterJ was perhaps the admin most familiar with the history, so it was obvious to him what needed to be done. Apteva has found approximately zero support
1406:
That is not even remotely possible. All I am asking for is one admin who I believe to clearly be not impartial to allow someone who is far more likely to be impartial to perform the close. A refusal to allow that simply reinforces my supposition that the close was not done impartially. Reverting the
1300:
So no admin who has ever disagreed with you can ever disagree with you again? No, I don't think it works that way. An admin who has impartially disagreed with you before can indeed impartially reach another decision, and might even be able to do so more efficiently. Regardless, refrain from saying I
598:
that were made by an admin who should have had the sense to recuse themself from closing them. The issue is not who did what but what was done, and was it reasonable. When the issue becomes who did what then there can be no discussion of what is reasonable. Yes the issue will be discussed here there
334:
The point is that Knowledge never chooses something that no one else does. To say that we can is ridiculous - as ridiculous as commas at the end of sentences. I am certainly pursuing the issue at the MOS but the MOS reflects what is current practice, it does not dictate practice, so if someone wants
181:
Four reasons. As below, a pejorative should never be used in a close, a closing admin needs to be unbiased, and clearly JhunterJ is not - if someone feels they need to use a pejorative in a close, they should not be doing the close, Snow can not be used when the vote is 4:2, nor can it be used in an
1968:
Which is why I posted my comment as "Endorse close as proposer of move". Accusation of duplicitousness is not appreciated. How on earth can anybody's vote not be biased in support of their own view? That is the nature of expressing opinion in a vote! Note that Lihaas does not identify himself as
1334:
If you will stop trying to focus this discussion on me, I will stop pointing out that you are wrong to do so, and the drama will end naturally. You do not get to select the admins who can or cannot close your proposals, and you do not get to restrict it to the group of admins you believe will agree
1016:
As with Aspen-Pitkin County Airport, 4:1 certainly can not be cited as Snow, nor does Snow apply to an uphill battle which might not succeed, not should a pejorative be used in reference to the close. The airport is clearly and obviously misspelled, and it is absurd for a few people at MOS who know
795:
Same as Seattle-Tacoma International Airport. 4:1 certainly can not be cited as Snow, nor does Snow apply to an uphill battle which might not succeed, not should a pejorative be used in reference to the close. The airport is clearly and obviously misspelled, and it is absurd for a few people at MOS
501:
It's this "no reason not to go ahead on the assumption that my consensus has already been reached" approach that is disruptive. Yes, the MOS follows what the articles do, but the articles follow the current consensus. Current consensus does not agree with you that using an endash on Knowledge where
467:
you could get a new consensus. Going after the local consensuses first is disruptive, and simple repetition of your claim that "endash = misspelling" does not make it true. Also, you keep using the word "obviously" to apply to things that are obviously not obvious, as the extensive conversations at
305:
I thought there was a consensus on this at WP:MOS, based on the discussion there. But to say that how we do things does not have to conform to what we do sounds pretty strange. Suppose we all decide to use commas at the end of sentences instead of periods, would that be acceptable? Would it help or
1938:
better describes the article than the current title, then in retrospect I wonder whether it was unnecessarily cautious to even use the RM procedure for a potentially contentious change. I have no objection to re-listing for discussion, but would maintain vehemently that the precedent of similarly
1319:
Focus on the issue, not the individual. If someone has been involved with an editor or an issue, simply let cooler minds prevail. Otherwise it simply comes across as being vindictive. Knowledge has enough drama trying to get things right without introducing more by introducing personal vendettas.
1210:
Three reasons. First Snow does not apply when the vote is 2:1. Second Snow does not apply when fighting an uphill battle which might not succeed. Third, the use of the word disruptive in the close is a pejorative that is totally unwarranted as the airport clearly and obviously to anyone who knows
1039:
seems to be the right call here. Also the time between this move request and the previous failed one seemed to be too short. (I was involved in the 2nd move request, and the move review of the first move request, but not in the 1st move request itself. It was the first move review that brought my
212:
A separate discussion was opened on 9 October, and withdrawn on 11 October based on the information that I had at the time, which turned out to be erroneous. It was opened on 18 November after this had been fully discussed at MOS, with the last information prevailing that a hyphen should be used.
1242:
assume good faith. AGP does have it limits. That said though, I believe that you truly believe what you are doing is good for the encyclopedia. That does not mean though that your attempts are not boarding on disruptive even if you don't intend it to be. Also not that while you site AGP, you are
1233:
seems to be the right call here. If you consider the comments it was actually 4:1 as two of the discussion comments that did not vote were both against the move. One calling for the moves request to be considered as a single request, the other calling for a speedy close for disruption. Note that
197:
The move discussion has been going on since October 11 while you disruptively forum-shop for anyone who agrees with you. You are absolutely right, there is no reason for a single editor to think he or she has any right to tell all of the rest of Knowledge how to spell things. Since you have been
486:
Changing the MOS is clearly being pursued, but there is a) a very toxic atmosphere there that makes normal discussion difficult, and b) no reason to misspell things in the meantime. The MOS follows what articles does, not the other way around, so changing articles first is more meaningful than
436:
This is getting way off topic, but what appears to be a stylistic choice for consistency case makes no sense for two reasons. The choice of punctuation is definitely not a stylistic choice, and wikipedia will never nor should ever attempt, to maintain a uniform, consistent style. Even Featured
416:
is just repeatedly overlooking the difference between a substantive error in encyclopedic content and stylistic choices made for consistency's sake based on Knowledge's in-house manual of style. It is antithetical to the point of having a manual of style in the first place to go around making
217:
it seemed clear that this RM would proceed without challenge. There is a severe disruption to Knowledge, and I am not it. The disruption is thinking that Mexican American War should be spelled with an endash instead of a hyphen, even though that clearly is not the case, and applying that false
282:
generally need to conform with the content standards. It is therefore not necessary to provide reliable sources to verify Knowledge's administrative pages, or to phrase Knowledge procedures or principles in a neutral manner, or to cite an outside authority in determining Knowledge's editorial
393:
Disruptive editing clearly does not apply. The first sentence ends "disrupts progress towards improving an article or building the encyclopedia". It is clearly an improvement to the encyclopedia to use hyphens where hyphens are appropriate and endashes where endashes are appropriate. What is
2039:
not really happen. Maybe I gave up too easily, not sure. Still I guess I am saying the closure had some justification, even if it was disappointing, but that I'm not sure I precisely endorse it as I may have given up too fast. If titling "uncertain" is unacceptable I'll change it later.--
352:
I will remind everyone that "disruptive" is a pejorative, a word used to degrade, denounce, or discredit, and it is simply not appropriate in a discussion. To make it simpler to understand, it is used as an attack word to attack the editor, and I believe there is a policy against
1465:
Before we get a bunch more repeated responses like PaleAqua's, can I propose that we treat these four as one, since they were are brought by the same guy, for essentially the same reason, and all closed by the same closer? Can we just discuss in this section instead of above?
2078:
Seems like the unfortunately logical close at the time. Seems like "Chronological summary of the 2012 Summer Paralympics" would be a better article, but that is not what the article is right now. Probably should be moved back after it is improved in that direction.
915:. Closing early a move request opened shortly after another was closed—especially when it doesn't seem to be getting any traction—is probably reasonable. I don't see compelling evidence here or any consensus for the idea that the closing admin was biased. – 770: 1391:
That's a false dichotomy. By that supposed logic, you could ask every closer who claimed to be impartial to revert until you found a closer who closed in your favor. While certainly self-serving, it's logically bankrupt. --
1851: 796:
who know nothing about airports to decide how airports should be spelled. The admin is not able to form an unbiased opinion and should have recused themself in favor of any one of the 800 other active admins.
421:
the first person to state this, yet you repeatedly open move discussions in all sorts of places based on your views about what is and isn't the common usage of dashes and hyphens in particular circumstances.
1969:
the only opposer of the move in the original discussion, nor does he acknowledge that it was he who reverted the move against the decision of the closing admin, and without using the accepted procedures.
991: 2009:
Please provide your reasons for believing that the article, either as it currently stands, or as it has stood at any time in the past, fulfils the description of a chronological summary of the games.
1989:
Further the page does have prose that said user removed citing it as unlikely to be expanded and then he moved it. Its an arduous process and help was needed, which is better than removing and moving.
1017:
nothing about airports to decide how airports should be spelled. The admin is not able to form an unbiased opinion and should have recused themself in favor of any one of the 800 other active admins.
1934:
as proposer of move. Obviously wider discussion would have been welcome, but if only one person can be seen to have opposed the move, and that person has yet to offer any reason why the phrase
788: 740: 1320:
There are 800 other active admins who can close these RM's. Do the right thing by reverting the closes, and let one of them close them whenever and if they think a close is appropriate.
1377:
If they were impartial than I would expect that you would have no problem with reverting them. If they were not impartial I would expect an objection to reverting them. Which is it?
776: 1185: 417:
article-by-article exceptions to the manual based on common usage. This isn't the encyclopedia of Comet Hale–Bopp (or Comet Hale-Bopp), it's the encyclopedia of everything. I am
1535:
If you think my comment applies to some of the closes and not to others, you are free to express that here. I thought it is was best not to repeat the comment in four places.
736: 686: 1500:– as one of the particpants against many of Apteva's anti-en-dash efforts, I'm clearly not unbiased here, but I do think that JHunterJ did the right thing in recognizing the 283:
practices. Instead, the content of these pages is controlled by community-wide consensus, and the style should emphasize clarity, directness, and usefulness to other editors.
441:
in WP:MOS - fix those and all of this goes away. One is misspelling Hale-Bopp and using it as an example of using an endash, and that is currently under discussion there.
287:
The MOS doesn't have to follow the most common usage. There is no "wrong" answer to this style question so there's no need to fix all of these "wrong" titles. If there
1869: 1821: 811:
I suppose all admins who would also close contrary to your preference should also recuse themselves? Please note that everyone who disagrees with you is not biased. --
1857: 997: 2140: 1009: 961: 613:
No, comets do not use English. The IAU does not use endashes. Knowledge is not the IAU. Also, please take your own advice about not focusing on the person. --
472:
prove. Perhaps you could focus more on the consensuses you agree with, such as ending sentences with periods and capitalizing the first words in sentences. --
269:
Knowledge has many policies and guidelines about encyclopedic content. These standards require verifiability, neutrality, respect for living people, and more.
1817: 1778: 580:
This discussion is a review of moves you initiated. The on-going discussion over there is the one in which this issue should be discussed. Good advice. --
1191: 60: 156: 1766: 1571: 957: 907: 47: 37: 1961:
Comment/caveat: Kevin McE was the user actively involved in calling for the move. His endorsement here is thus biased in support of his view.
1520:
That is he or she thank you. This section is meaningless. Each close is being discussed separately, and it is not meaningful to combine them.
2057:
Oh, no. "Uncertain" is a good vote for those who do not either support or oppose. Hopefully, this discussion should not be a rehash of RM. --
1203: 1155: 843:. Obviously if you close the discussion I can validly claim that it was a biased close. Let someone else do the close and that goes away. 162: 2096:. Suggest a fresh RM for after when it is improved in the direction of chronology. It is important that titles are not misleading. -- 1286:
I do not think that the decision could be made in an impartial manner because of prior involvement with the editor proposing the move.
1714:- Move review is no place for new requests. Also, the requested move was two years old, and arguing over titles is no longer fun. -- 260: 1363:
Yes, this is silly. Withdraw your requests for review, since the closes were impartial. Is there seriously a problem with that? --
1913:
In the same vein, it should not bbe moved with consensus either. Cause precedent changes need wider consensus in the first place.
1119: 925: 704: 90: 1151: 1101: 1690:, such as credit cards, mobile phone cards and so on. Therefore I think we should move it back to the long but accurate name. 335:
to change the MOS, the first step is to change the articles that are affected, and then change the MOS to reflect that change.
1661: 535: 469: 456: 438: 214: 1421:
Refusal to allow you to admin shop is not evidence of partiality, although I am not surprised to see it spun that way. --
839:
The point is that even if a vote is 20:1 we do not allow someone who participated in a discussion to close the discussion
631:
with hyphens and spaces. Is that better? Sorry, but this discussion is about the actions of the admin who closed the RMs.
538:. Which someone has tried to "fix" with a poll, after a few editors failed to support the arguments against the change. -- 42: 372: 1667: 566:
Rule number one in building consensus is to discuss the issue, not the person or persons involved in the discussion.
394:
disruptive is doing the opposite. This is an example of being wrong and accusing those who are right of being wrong.
1349:
This is getting silly. Revert the closes and let someone else close them. Is there seriously a problem with that?
376: 21: 379:) deleted; once they are deleted, I will stop using them in discussions about the behaviors described there. -- 174: 126: 825:
No, of course not. But do you really expect anyone to believe that this was an impartial assessment of the RM?
460: 1481:
No. They all have separate issues, and it would not be reasonable to expect the same result for all of them.
428: 297: 371:
You are wrong about this as well. "Disruptive" is not a pejorative, and I am not using it to degrade. See
2116: 1801: 1750: 1611: 1555: 1135: 1080: 941: 886: 720: 665: 543: 106: 17: 375:, and if you still feel that it has no place in a discussion, see if you can get that page (as well as 2044: 1115: 921: 700: 86: 122: 72: 2101: 2062: 2014: 1974: 1948: 1719: 1596: 1272:
I was not involved in the discussions I closed. Please do not resort to lies in your arguments. --
2105: 2088: 2066: 2048: 2018: 1998: 1978: 1952: 1922: 1904: 1886: 1790: 1737: 1723: 1705: 1600: 1544: 1529: 1514: 1490: 1475: 1430: 1416: 1401: 1386: 1372: 1358: 1344: 1329: 1314: 1295: 1281: 1267: 1252: 1220: 1124: 1067: 1049: 1026: 930: 875: 852: 834: 820: 805: 709: 640: 622: 608: 589: 575: 561: 547: 511: 496: 481: 450: 431: 403: 388: 366: 329: 315: 300: 246: 227: 207: 191: 95: 2084: 1540: 1510: 1471: 1426: 1397: 1368: 1340: 1310: 1277: 1248: 1045: 871: 816: 618: 585: 557: 507: 477: 423: 384: 325: 292: 242: 203: 291:, it'd be best to get a consensus on the MOS rather than doing this serially article-by-article. 1900: 1697: 1591:. This similar reasoning is used for new requested move in the article talk page right now. – 552:"Someone" being Apteva, after a few editors failed to form a new consensus for the change. -- 1994: 1918: 1882: 1733: 1687: 1525: 1486: 1412: 1382: 1354: 1325: 1291: 1263: 1243:
assuming bad faith on the part of the closing admin. (Note I involved in the discussion. )
1216: 1063: 1022: 848: 830: 801: 636: 604: 571: 539: 492: 446: 399: 362: 354: 311: 223: 187: 2040: 1110: 916: 695: 81: 866:
seems to be the right call here. ( Note I was involved in the most recent discussion. )
2097: 2058: 2010: 1970: 1944: 1715: 1592: 1501: 1230: 1055: 1036: 863: 413: 2134: 2080: 1787: 1679: 1631: 1536: 1506: 1467: 1422: 1393: 1364: 1336: 1306: 1273: 1244: 1235: 1041: 867: 812: 614: 581: 553: 503: 473: 380: 321: 238: 199: 534:
I have tried getting a consensus in WP:MOS, but I get stonewalled all the time.....
1896: 1692: 1407:
closes and allowing another admin to step in removes that issue from the equation.
841:
so that that one person can not complain about the close not being done impartially
1990: 1914: 1878: 1729: 1521: 1482: 1408: 1378: 1350: 1321: 1287: 1259: 1212: 1059: 1018: 844: 826: 797: 632: 600: 567: 488: 442: 395: 358: 307: 219: 183: 594:
No, it is not a review of moves one person initiated. It is a review of the
1229:
Only the requester supported the move based on other similar move requests
1035:
Only the requester supported the move based on other similar move requests
862:
Only the requester supported the move based on other similar move requests
1258:
let an uninvolved admin close it in a week. That is the proper procedure.
1686:
Yikatong (一卡通, literally all-purpose card or multi-purpose card) is used
1627: 1583: 237:
per JHunter. ( Note I was involved in the most recent discussion. )
261:
Knowledge:Policies_and_guidelines#Not_part_of_the_encyclopedia
599:
and anywhere else it comes up. Comets do not use endashes.
274:
The policies, guidelines, and process pages themselves are
1864: 1844: 1836: 1828: 1674: 1654: 1646: 1638: 1198: 1178: 1170: 1162: 1004: 984: 976: 968: 783: 763: 755: 747: 278:
part of the encyclopedia proper. Consequently, they do
169: 149: 141: 133: 1936:
Chronological summary of the 2012 Summer Paralympics
1941:Chronological summary of the 2012 Summer Olympics 737:Fort Lauderdale–Hollywood International Airport 687:Fort Lauderdale–Hollywood International Airport 8: 1818:Event winners at the 2012 Summer Paralympics 1779:Event winners at the 2012 Summer Paralympics 1800:The following is an archived debate of the 1610:The following is an archived debate of the 1134:The following is an archived debate of the 940:The following is an archived debate of the 719:The following is an archived debate of the 105:The following is an archived debate of the 1771: 1576: 1094: 900: 679: 65: 1461:Group of en-dash closes brought by Apteva 1054:Please read Snow, in particular the part 536:There is an on-going discussion right now 1728:Opened RM. Feel free to close this now. 1056:WP:Snow#What the snowball clause is not 502:IAU uses a hyphen is "misspelling". -- 2141:Knowledge move review monthly listings 1305:discussions, since that is a lie. -- 7: 958:Seattle–Tacoma International Airport 908:Seattle–Tacoma International Airport 455:As ever, build the new consensus at 2119:of the page listed in the heading. 1753:of the page listed in the heading. 1558:of the page listed in the heading. 1083:of the page listed in the heading. 889:of the page listed in the heading. 668:of the page listed in the heading. 463:at the articles that would change 259:I think this can be resolved with 215:no challenge to that for two weeks 28: 2115:The above is an archive of the 1749:The above is an archive of the 1693: 1554:The above is an archive of the 1079:The above is an archive of the 885:The above is an archive of the 664:The above is an archive of the 470:Knowledge talk:Manual of Style 457:Knowledge talk:Manual of Style 1: 1791:08:27, 16 November 2012 (UTC) 1738:05:18, 14 November 2012 (UTC) 1601:04:44, 20 November 2012 (UTC) 1545:05:09, 25 November 2012 (UTC) 1530:04:43, 25 November 2012 (UTC) 1515:05:26, 24 November 2012 (UTC) 1491:23:50, 20 November 2012 (UTC) 1476:05:52, 20 November 2012 (UTC) 1431:12:30, 25 November 2012 (UTC) 1417:04:56, 25 November 2012 (UTC) 1402:13:47, 23 November 2012 (UTC) 1387:22:47, 22 November 2012 (UTC) 1373:21:00, 22 November 2012 (UTC) 1359:20:31, 22 November 2012 (UTC) 1345:17:59, 22 November 2012 (UTC) 1330:17:24, 22 November 2012 (UTC) 1315:12:41, 22 November 2012 (UTC) 1296:02:24, 22 November 2012 (UTC) 1282:13:18, 21 November 2012 (UTC) 1268:00:40, 20 November 2012 (UTC) 1253:23:22, 19 November 2012 (UTC) 1221:18:36, 19 November 2012 (UTC) 1125:18:10, 27 November 2012 (UTC) 1068:00:35, 20 November 2012 (UTC) 1050:23:22, 19 November 2012 (UTC) 1027:19:28, 19 November 2012 (UTC) 931:18:05, 27 November 2012 (UTC) 876:23:22, 19 November 2012 (UTC) 853:01:49, 20 November 2012 (UTC) 835:01:41, 20 November 2012 (UTC) 821:20:25, 19 November 2012 (UTC) 806:19:28, 19 November 2012 (UTC) 710:18:08, 27 November 2012 (UTC) 641:20:27, 22 November 2012 (UTC) 623:18:01, 22 November 2012 (UTC) 609:16:43, 22 November 2012 (UTC) 590:12:43, 22 November 2012 (UTC) 576:02:22, 22 November 2012 (UTC) 562:13:16, 21 November 2012 (UTC) 548:22:19, 20 November 2012 (UTC) 512:12:27, 25 November 2012 (UTC) 497:04:49, 25 November 2012 (UTC) 482:13:24, 24 November 2012 (UTC) 451:07:43, 24 November 2012 (UTC) 432:06:46, 23 November 2012 (UTC) 404:20:27, 22 November 2012 (UTC) 389:17:59, 22 November 2012 (UTC) 367:17:24, 22 November 2012 (UTC) 330:13:16, 21 November 2012 (UTC) 316:01:38, 20 November 2012 (UTC) 301:01:08, 20 November 2012 (UTC) 247:23:22, 19 November 2012 (UTC) 228:00:28, 20 November 2012 (UTC) 208:20:23, 19 November 2012 (UTC) 192:19:28, 19 November 2012 (UTC) 96:17:55, 27 November 2012 (UTC) 30: 2106:03:44, 5 November 2012 (UTC) 2089:02:33, 5 November 2012 (UTC) 2067:14:45, 4 November 2012 (UTC) 2049:10:39, 3 November 2012 (UTC) 2019:11:27, 4 November 2012 (UTC) 1999:06:23, 4 November 2012 (UTC) 1979:11:27, 4 November 2012 (UTC) 1953:10:20, 3 November 2012 (UTC) 1923:06:24, 4 November 2012 (UTC) 1905:06:25, 3 November 2012 (UTC) 1887:05:53, 3 November 2012 (UTC) 1877:consensus on the first mve. 1724:15:25, 5 November 2012 (UTC) 1706:11:03, 5 November 2012 (UTC) 1698: 1238:does not state that we must 459:first before trying to make 373:Knowledge:Disruptive editing 1152:Aspen–Pitkin County Airport 1102:Aspen–Pitkin County Airport 1040:attention to this issue. ) 2157: 1893:Comment from closing admin 377:Knowledge:Disruptive user 2122:Please do not modify it. 1807:Please do not modify it. 1756:Please do not modify it. 1617:Please do not modify it. 1561:Please do not modify it. 1141:Please do not modify it. 1086:Please do not modify it. 947:Please do not modify it. 892:Please do not modify it. 726:Please do not modify it. 671:Please do not modify it. 487:changing the MOS first. 112:Please do not modify it. 18:Knowledge:Move review 439:three obvious errors 43:Move review archives 1939:named articles (eg 1804:of the page above. 1614:of the page above. 1138:of the page above. 944:of the page above. 723:of the page above. 109:of the page above. 1688:in many situations 1589:Procedural closure 2129: 2128: 1763: 1762: 1568: 1567: 1123: 1093: 1092: 929: 899: 898: 708: 678: 677: 461:WP:LOCALCONSENSUS 94: 56: 55: 2148: 2124: 1867: 1847: 1839: 1831: 1809: 1784:Closure endorsed 1772: 1758: 1704: 1702: 1695: 1677: 1657: 1649: 1641: 1619: 1577: 1563: 1301:was involved in 1201: 1181: 1173: 1165: 1143: 1113: 1107:Closure endorsed 1095: 1088: 1007: 987: 979: 971: 949: 919: 913:Closure endorsed 901: 894: 786: 766: 758: 750: 728: 698: 692:Closure endorsed 680: 673: 426: 295: 172: 152: 144: 136: 114: 84: 78:Closure endorsed 66: 61:2012 November 19 52: 36: 31: 2156: 2155: 2151: 2150: 2149: 2147: 2146: 2145: 2131: 2130: 2120: 2094:Endorse for now 1863: 1862: 1856: 1850: 1843: 1842: 1835: 1834: 1827: 1826: 1805: 1770: 1767:2012 November 3 1754: 1701: 1691: 1673: 1672: 1666: 1660: 1653: 1652: 1645: 1644: 1637: 1636: 1615: 1575: 1572:2012 November 5 1559: 1197: 1196: 1190: 1184: 1177: 1176: 1169: 1168: 1161: 1160: 1139: 1084: 1003: 1002: 996: 990: 983: 982: 975: 974: 967: 966: 945: 890: 782: 781: 775: 769: 762: 761: 754: 753: 746: 745: 724: 669: 424: 412:disruptive per 293: 255: 168: 167: 161: 155: 148: 147: 140: 139: 132: 131: 123:Comet Hale–Bopp 110: 73:Comet Hale–Bopp 64: 57: 50: 34: 26: 25: 24: 12: 11: 5: 2154: 2152: 2144: 2143: 2133: 2132: 2127: 2126: 2111: 2110: 2109: 2108: 2091: 2072: 2071: 2070: 2069: 2052: 2051: 2032: 2031: 2030: 2029: 2028: 2027: 2026: 2025: 2024: 2023: 2022: 2021: 1987: 1986: 1985: 1984: 1983: 1982: 1981: 1956: 1955: 1928: 1927: 1926: 1925: 1908: 1907: 1874: 1873: 1860: 1854: 1848: 1840: 1832: 1824: 1812: 1811: 1796: 1795: 1794: 1793: 1769: 1764: 1761: 1760: 1745: 1744: 1743: 1742: 1741: 1740: 1699: 1684: 1683: 1670: 1664: 1658: 1650: 1642: 1634: 1622: 1621: 1606: 1605: 1604: 1603: 1574: 1569: 1566: 1565: 1550: 1549: 1548: 1547: 1518: 1517: 1498:Endorse closes 1494: 1493: 1463: 1462: 1458: 1457: 1456: 1455: 1454: 1453: 1452: 1451: 1450: 1449: 1448: 1447: 1446: 1445: 1444: 1443: 1442: 1441: 1440: 1439: 1438: 1437: 1436: 1435: 1434: 1433: 1208: 1207: 1194: 1188: 1182: 1174: 1166: 1158: 1146: 1145: 1130: 1129: 1128: 1127: 1091: 1090: 1075: 1074: 1073: 1072: 1071: 1070: 1014: 1013: 1000: 994: 988: 980: 972: 964: 952: 951: 936: 935: 934: 933: 897: 896: 881: 880: 879: 878: 857: 856: 855: 837: 793: 792: 779: 773: 767: 759: 751: 743: 731: 730: 715: 714: 713: 712: 676: 675: 660: 659: 658: 657: 656: 655: 654: 653: 652: 651: 650: 649: 648: 647: 646: 645: 644: 643: 532: 531: 530: 529: 528: 527: 526: 525: 524: 523: 522: 521: 520: 519: 518: 517: 516: 515: 514: 343: 342: 341: 340: 339: 338: 337: 336: 285: 271: 265: 264: 257:Endorse close. 251: 249: 232: 231: 230: 179: 178: 165: 159: 153: 145: 137: 129: 117: 116: 101: 100: 99: 98: 63: 58: 54: 53: 45: 40: 29: 27: 15: 14: 13: 10: 9: 6: 4: 3: 2: 2153: 2142: 2139: 2138: 2136: 2125: 2123: 2118: 2113: 2112: 2107: 2103: 2099: 2095: 2092: 2090: 2086: 2082: 2077: 2076:Endorse close 2074: 2073: 2068: 2064: 2060: 2056: 2055: 2054: 2053: 2050: 2046: 2042: 2037: 2034: 2033: 2020: 2016: 2012: 2008: 2007: 2006: 2005: 2004: 2003: 2002: 2001: 2000: 1996: 1992: 1988: 1980: 1976: 1972: 1967: 1966: 1965: 1964: 1963: 1962: 1960: 1959: 1958: 1957: 1954: 1950: 1946: 1942: 1937: 1933: 1932:Endorse close 1930: 1929: 1924: 1920: 1916: 1912: 1911: 1910: 1909: 1906: 1902: 1898: 1894: 1891: 1890: 1889: 1888: 1884: 1880: 1871: 1866: 1859: 1853: 1846: 1838: 1830: 1823: 1819: 1816: 1815: 1814: 1813: 1810: 1808: 1803: 1798: 1797: 1792: 1789: 1785: 1781: 1780: 1776: 1775: 1774: 1773: 1768: 1765: 1759: 1757: 1752: 1747: 1746: 1739: 1735: 1731: 1727: 1726: 1725: 1721: 1717: 1713: 1710: 1709: 1708: 1707: 1703: 1696: 1689: 1681: 1676: 1669: 1663: 1656: 1648: 1640: 1633: 1629: 1626: 1625: 1624: 1623: 1620: 1618: 1613: 1608: 1607: 1602: 1598: 1594: 1590: 1586: 1585: 1581: 1580: 1579: 1578: 1573: 1570: 1564: 1562: 1557: 1552: 1551: 1546: 1542: 1538: 1534: 1533: 1532: 1531: 1527: 1523: 1516: 1512: 1508: 1503: 1499: 1496: 1495: 1492: 1488: 1484: 1480: 1479: 1478: 1477: 1473: 1469: 1460: 1459: 1432: 1428: 1424: 1420: 1419: 1418: 1414: 1410: 1405: 1404: 1403: 1399: 1395: 1390: 1389: 1388: 1384: 1380: 1376: 1375: 1374: 1370: 1366: 1362: 1361: 1360: 1356: 1352: 1348: 1347: 1346: 1342: 1338: 1335:with you. -- 1333: 1332: 1331: 1327: 1323: 1318: 1317: 1316: 1312: 1308: 1304: 1299: 1298: 1297: 1293: 1289: 1285: 1284: 1283: 1279: 1275: 1271: 1270: 1269: 1265: 1261: 1256: 1255: 1254: 1250: 1246: 1241: 1237: 1232: 1228: 1227:Endorse close 1225: 1224: 1223: 1222: 1218: 1214: 1205: 1200: 1193: 1187: 1180: 1172: 1164: 1157: 1153: 1150: 1149: 1148: 1147: 1144: 1142: 1137: 1132: 1131: 1126: 1121: 1117: 1112: 1108: 1104: 1103: 1099: 1098: 1097: 1096: 1089: 1087: 1082: 1077: 1076: 1069: 1065: 1061: 1057: 1053: 1052: 1051: 1047: 1043: 1038: 1034: 1033:Endorse close 1031: 1030: 1029: 1028: 1024: 1020: 1011: 1006: 999: 993: 986: 978: 970: 963: 959: 956: 955: 954: 953: 950: 948: 943: 938: 937: 932: 927: 923: 918: 914: 910: 909: 905: 904: 903: 902: 895: 893: 888: 883: 882: 877: 873: 869: 865: 861: 860:Endorse close 858: 854: 850: 846: 842: 838: 836: 832: 828: 824: 823: 822: 818: 814: 810: 809: 808: 807: 803: 799: 790: 785: 778: 772: 765: 757: 749: 742: 738: 735: 734: 733: 732: 729: 727: 722: 717: 716: 711: 706: 702: 697: 693: 689: 688: 684: 683: 682: 681: 674: 672: 667: 662: 661: 642: 638: 634: 630: 626: 625: 624: 620: 616: 612: 611: 610: 606: 602: 597: 593: 592: 591: 587: 583: 579: 578: 577: 573: 569: 565: 564: 563: 559: 555: 551: 550: 549: 545: 541: 537: 533: 513: 509: 505: 500: 499: 498: 494: 490: 485: 484: 483: 479: 475: 471: 466: 462: 458: 454: 453: 452: 448: 444: 440: 435: 434: 433: 430: 427: 425:AgnosticAphid 420: 419:certainly not 415: 411: 408:What I think 407: 406: 405: 401: 397: 392: 391: 390: 386: 382: 378: 374: 370: 369: 368: 364: 360: 356: 351: 350: 349: 348: 347: 346: 345: 344: 333: 332: 331: 327: 323: 319: 318: 317: 313: 309: 304: 303: 302: 299: 296: 294:AgnosticAphid 290: 286: 284: 281: 277: 272: 270: 267: 266: 262: 258: 254: 250: 248: 244: 240: 236: 235:Endorse close 233: 229: 225: 221: 216: 211: 210: 209: 205: 201: 196: 195: 194: 193: 189: 185: 176: 171: 164: 158: 151: 143: 135: 128: 124: 121: 120: 119: 118: 115: 113: 108: 103: 102: 97: 92: 88: 83: 79: 75: 74: 70: 69: 68: 67: 62: 59: 49: 48:2012 December 46: 44: 41: 39: 33: 32: 23: 19: 2121: 2114: 2093: 2075: 2035: 1940: 1935: 1931: 1892: 1875: 1806: 1799: 1783: 1777: 1755: 1748: 1712:Speedy close 1711: 1685: 1616: 1609: 1588: 1582: 1560: 1553: 1519: 1497: 1464: 1302: 1239: 1226: 1209: 1140: 1133: 1106: 1100: 1085: 1078: 1032: 1015: 946: 939: 912: 906: 891: 884: 859: 840: 794: 725: 718: 691: 685: 670: 663: 628: 595: 464: 418: 409: 288: 279: 275: 273: 268: 256: 252: 234: 213:There being 180: 111: 104: 77: 71: 38:2012 October 2117:move review 1802:move review 1751:move review 1612:move review 1556:move review 1136:move review 1081:move review 942:move review 887:move review 721:move review 666:move review 627:Comets are 540:Enric Naval 107:move review 2041:T. Anthony 1111:ErikHaugen 917:ErikHaugen 696:ErikHaugen 355:WP:Attacks 82:ErikHaugen 2098:SmokeyJoe 2059:George Ho 2036:Uncertain 2011:Kevin McE 1971:Kevin McE 1945:Kevin McE 1716:George Ho 1593:George Ho 2135:Category 2081:PaleAqua 1788:Armbrust 1628:Yikatong 1584:Yikatong 1537:Dicklyon 1507:Dicklyon 1468:Dicklyon 1423:JHunterJ 1394:JHunterJ 1365:JHunterJ 1337:JHunterJ 1307:JHunterJ 1274:JHunterJ 1245:PaleAqua 1120:contribs 1042:PaleAqua 926:contribs 868:PaleAqua 813:JHunterJ 705:contribs 615:JHunterJ 582:JHunterJ 554:JHunterJ 504:JHunterJ 474:JHunterJ 381:JHunterJ 322:JHunterJ 239:PaleAqua 200:JHunterJ 91:contribs 20:‎ | 1897:Jenks24 1858:archive 1837:history 1694:Makecat 1668:archive 1647:history 1502:WP:SNOW 1231:WP:Snow 1192:archive 1171:history 1037:WP:Snow 998:archive 977:history 864:WP:Snow 777:archive 756:history 629:spelled 414:WP:IDHT 163:archive 142:history 1991:Lihaas 1915:Lihaas 1879:Lihaas 1730:Apteva 1522:Apteva 1483:Apteva 1409:Apteva 1379:Apteva 1351:Apteva 1322:Apteva 1288:Apteva 1260:Apteva 1240:always 1236:WP:AGF 1213:Apteva 1060:Apteva 1019:Apteva 845:Apteva 827:Apteva 798:Apteva 633:Apteva 601:Apteva 596:closes 568:Apteva 489:Apteva 443:Apteva 396:Apteva 359:Apteva 308:Apteva 253:Oppose 220:Apteva 184:Apteva 1865:watch 1852:links 1675:watch 1662:links 1303:these 1199:watch 1186:links 1109:. – 1005:watch 992:links 784:watch 771:links 170:watch 157:links 51:: --> 16:< 2102:talk 2085:talk 2063:talk 2045:talk 2015:talk 1995:talk 1975:talk 1949:talk 1919:talk 1901:talk 1883:talk 1845:logs 1829:edit 1822:talk 1786:. – 1734:talk 1720:talk 1700:Talk 1655:logs 1639:edit 1632:talk 1597:talk 1541:talk 1526:talk 1511:talk 1487:talk 1472:talk 1427:talk 1413:talk 1398:talk 1383:talk 1369:talk 1355:talk 1341:talk 1326:talk 1311:talk 1292:talk 1278:talk 1264:talk 1249:talk 1217:talk 1179:logs 1163:edit 1156:talk 1116:talk 1064:talk 1046:talk 1023:talk 985:logs 969:edit 962:talk 922:talk 872:talk 849:talk 831:talk 817:talk 802:talk 764:logs 748:edit 741:talk 701:talk 694:. – 637:talk 619:talk 605:talk 586:talk 572:talk 558:talk 544:talk 508:talk 493:talk 478:talk 447:talk 429:talk 400:talk 385:talk 363:talk 326:talk 312:talk 298:talk 289:were 243:talk 224:talk 204:talk 188:talk 150:logs 134:edit 127:talk 87:talk 80:. – 35:< 1868:) ( 1678:) ( 1202:) ( 1008:) ( 787:) ( 280:not 276:not 173:) ( 22:Log 2137:: 2104:) 2087:) 2065:) 2047:) 2017:) 1997:) 1977:) 1951:) 1921:) 1903:) 1885:) 1870:RM 1782:– 1736:) 1722:) 1680:RM 1599:) 1587:– 1543:) 1528:) 1513:) 1489:) 1474:) 1429:) 1415:) 1400:) 1385:) 1371:) 1357:) 1343:) 1328:) 1313:) 1294:) 1280:) 1266:) 1251:) 1219:) 1204:RM 1118:| 1105:– 1066:) 1048:) 1025:) 1010:RM 924:| 911:– 874:) 851:) 833:) 819:) 804:) 789:RM 703:| 690:– 639:) 621:) 607:) 588:) 574:) 560:) 546:) 510:) 495:) 480:) 465:if 449:) 410:is 402:) 387:) 365:) 328:) 314:) 245:) 226:) 206:) 190:) 175:RM 89:| 76:– 2100:( 2083:( 2061:( 2043:( 2013:( 1993:( 1973:( 1947:( 1917:( 1899:( 1881:( 1872:) 1861:| 1855:| 1849:| 1841:| 1833:| 1825:| 1820:( 1732:( 1718:( 1682:) 1671:| 1665:| 1659:| 1651:| 1643:| 1635:| 1630:( 1595:( 1539:( 1524:( 1509:( 1485:( 1470:( 1425:( 1411:( 1396:( 1381:( 1367:( 1353:( 1339:( 1324:( 1309:( 1290:( 1276:( 1262:( 1247:( 1215:( 1206:) 1195:| 1189:| 1183:| 1175:| 1167:| 1159:| 1154:( 1122:) 1114:( 1062:( 1044:( 1021:( 1012:) 1001:| 995:| 989:| 981:| 973:| 965:| 960:( 928:) 920:( 870:( 847:( 829:( 815:( 800:( 791:) 780:| 774:| 768:| 760:| 752:| 744:| 739:( 707:) 699:( 635:( 617:( 603:( 584:( 570:( 556:( 542:( 506:( 491:( 476:( 445:( 398:( 383:( 361:( 324:( 310:( 263:: 241:( 222:( 202:( 186:( 177:) 166:| 160:| 154:| 146:| 138:| 130:| 125:( 93:) 85:(

Index

Knowledge:Move review
Log
2012 October
Move review archives
2012 December
2012 November 19
Comet Hale–Bopp
ErikHaugen
talk
contribs
17:55, 27 November 2012 (UTC)
move review
Comet Hale–Bopp
talk
edit
history
logs
links
archive
watch
RM
Apteva
talk
19:28, 19 November 2012 (UTC)
JHunterJ
talk
20:23, 19 November 2012 (UTC)
no challenge to that for two weeks
Apteva
talk

Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.

↑