- Hillary Clinton (talk|edit|history|logs|links|archive|watch) (RM)
This was the fifth requested move for this article, which has long been located at Hillary Rodham Clinton. It was a non-administrator close by User:Obiwankenobi for a contentious discussion with no clear consensus. I think the general viewpoint on the side of keeping the article at its (now prior) location was that "Hillary Rodham Clinton" is the name she has long used in her personal and professional lives and it is the name that many of the "most reliable" sources use for her on first reference (such as the New York Times, the Washington Post, and so forth). It's also the title used by Britannica and other encyclopedias (which policy recommends considering when in doubt). The argument on the other side, for moving the article to Hillary Clinton, is that — primarily over the past three years — Hillary Clinton has become the more common usage of her name as judged by certain news databases, Google Books ngrams, and general Google searches. A further argument is that it is more concise. The non-administrator closure was, at first, overturned by User:Good Olfactory per wp:rmnac, but he later reversed himself on the basis that User:Obiwankenobi's closure was done in good faith. Simply put, I don't think anyone could argue there was a clear consensus, which not only makes the non-administrator closure inappropriate, but would make any move inconsistent with our policies and the the intent and spirit of wp:noconsensus.user:j (talk) 05:55, 19 June 2013 (UTC)[reply]
I ask that you judge the close on it's merits, and not on the presence or absence of a bit in my user profile. This recent discussion reinforces this particular point, by the way, so please don't put forth the "it's a non-admin close" arguments. Please argue the merits of the case, not the closer. --Obi-Wan Kenobi (talk) 06:51, 19 June 2013 (UTC)[reply]
I informed Nathan Johnson and Dennis Brown of this discussion, as they were involved in recent ANI thread about non-admin closures. I also informed all of the participants in the rename discussion who haven't already commented below. -Obi
- Survey
- When I came into this, it was via the RM backlog which I was attempting to chip away at. I first looked at this one, and decided to skip it, but then after a quick read through, it seemed to be an obvious no-consensus close just based on length of the discussion and many supports and many opposes, so decided to close and started reading more carefully. After my second read-through, and checking the policies more carefully, I was surprised to find that there *was* actually rough consensus on a number of points relevant to the move, but (unfortunately for the oppose side), the oppose arguments were much *less* based on firm policy and much more based on softer issues. For example, many of the "oppose" voters noted it was a name she preferred, or that it referenced her life before Clinton, or that she was "well-known" by that name, etc - all of these are useful, but not as strong as clear policy based arguments, which the supporters were making more of. (If you don't believe me, just read the top-line "oppose" arguments one by one - you'll notice very few actually reference titling policy)
- I thus found myself with what was IMHO a clear consensus to move, if we discounted emotion and forcefullness and drama and numbers, and just looked at cold hard policy and cold hard facts (which is what you are supposed to do when judging consensus). I thus felt, provided I explained the close well, that I would be competent to close this as a non-admin. I found rough consensus on a number of points:
- WP:COMMONNAME That HC was *more* frequently used in reliable sources. There were many arguments about how HRC is *also* frequently used, but very little evidence provided that HRC was *more* frequently used in RS. COMMONNAME is explicitly about FREQUENCY of use. There was strong evidence, such as the ngrams, provided that HC is now *more* frequently used, and that usage has changed over time. Thus, I found that there was rough consensus to say that both are certainly equally used, and evidence that HC was *more* used in RS. In addition, almost every single "support" editor mentioned WP:COMMONNAME, so there was clear consensus from that side that COMMONNAME was an important policy in judging this, and the oppose side did not mount a strong defense against that. Towards the end, some of the oppose editors basically conceded this point, but then said "it's not about # of hits, there are other issues at play". And on that point, I agreed with them - I would not have closed to move purely based on a finding that HC is used 50% more than HRC for example. But there were two other key policy points, on which I also found rough consensus:
- WP:PRECISE That HC was precise. HRC was *more* precise, but HC was precise enough. I didn't see any significant disagreement on this point.
- WP:CRITERIA That HC was concise. No significant disagreement on this point either.
- Thus, on three substantive points, all part of the POLICY around WP:AT, there was rough consensus and no significant dissent (there was some quibbling, but it was around things like what the word "concise" means, and those arguments ignored the definition given in the policy: "The title is no longer than necessary to identify the article's subject and distinguish it from other subjects." It was on this basis that I found a rough consensus for the move. I did not invent any of these policy points, and all of them were extensively argued by people in the move.
- There were several arguments by the oppose side made that amounted to basically Other stuff exists - e.g. Lyndon B. Johnson, etc. In the close, I detailed many other arguments that I discarded, like twitter handles, etc, as being not based on policy, or not logical, or not workable.
- To sum up, before deciding, I ask you to read this, a quote from WP:CONSENSUS:
- "Consensus is determined by the quality of the arguments given on the various sides of an issue, as viewed through the lens of Wikipedia policy." This is exactly what I did. I judged the quality of the arguments for a rename, or not, based on how well they adhered to policy. Simply put, the supporters had three indisputable policy prescriptions on their side, while the opposers did not.
- Another point of consensus is the following: "The closer is there to judge the consensus of the community, after discarding irrelevant arguments: those that flatly contradict established policy, those based on personal opinion only, those that are logically fallacious, those that show no understanding of the matter of issue.[2] If the discussion shows that some people think one policy is controlling, and some another, the decider is expected to close by judging which view has the predominant number of responsible Wikipedians supporting it, not select himself which is the better policy." Again, there was rough consensus on three policy points, and then arguments made by the oppose side that weren't really based on policy points, except WP:COMMONNAME, but the evidence ended up being against them on that.
- So, in a first read, it may look like no-consensus, but if you read it carefully, and think in terms of "Which argument is based on policy, which is based on guidance, and which is based on softer issues", the answer becomes clear (at least, it was clear to me.)
- Note: re accusations of SUPERVOTE. First, I did not have any particular outcome in mind when I decided to close this, and my first hour was spent building a case for no-consensus (FWIW, at one point I even started going down a path of keep (vs NC) based on what I thought was a particularly strong piece of evidence, but I abandoned this path based on another counterargument). The discovery and analysis of the policy-based arguments of WP:PRECISE and conciseness tipped the scales, so I found a consensus to move instead. Secondly, if you read Wikipedia:Supervote, it states the following: "it's not a "supervote" to close in accordance with a significant minority opinion." In this case, I closed in accordance with what I know now to be a majority opinion (I didn't count votes, but now have), with rough consensus from both sides on the key issues leading to the close.--Obi-Wan Kenobi (talk) 06:51, 19 June 2013 (UTC)[reply]
- Note: An interesting comparison from last year, on a topic that is a lot more debated than this one:
- [[Talk:Burma/Archive_10#Requested_move_.28Burma_.E2.86.92_Myanmar.29_August_2012 - NOT moved (e.g. kept at Burma)
- Wikipedia:Move_review/Log/2012_August_26 User:Tariqabjotu, the closing admin, had to balance a complex and unclear debate about COMMONNAME, but ultimately it came down to WP:CRITERIA vs WP:OFFICIALNAME. Burma was selected as a result, as fulfilling WP:CRITERIA. The closing admin did NOT find no-consensus, however, in spite of the incredibly messy discussion - they explicitly found that the article should live at Burma. Frankly, it's not a result I would have personally agreed with, but it is more in line with current policy than Myanmar, so I also would have endorsed the close as being within closers discretion. There are strong parallels here.--Obi-Wan Kenobi (talk) 20:48, 21 June 2013 (UTC)[reply]
- Endorse close Reading through the move discussion ( including following back to some of the earlier no consensus ones ), it looks like User:Obiwankenobi made a good tally of the discussion. A good part of determining consensus is being able to weigh the arguments which looks to have been done here. While I would have rather seen an admin close this—as the RMCI recommend for contentious discussions, I can't really find fault with the reasoning of the close. PaleAqua (talk) 06:50, 19 June 2013 (UTC)[reply]
- Overturn close. The RM discussion resulted in no consensus to move, and so Obiwankenobi's closure appears to have been a supervote. In addition, the admin who made the move on his behalf, Timrollpickering, had commented several times during the discussion in support of the move (e.g. here), and should therefore not have used the tools (the target title had to be deleted), given that the result was not straightforward. Tim and Obiwankenobi expressed very strong views recently during the RM at Sarah Brown (wife of Gordon Brown), and should ideally regard themselves as involved during any similar discussion. SlimVirgin (talk) 07:06, 19 June 2013 (UTC)[reply]
- Overturn close. I had no involvement in the move discussion, nor do I have an opinion on the proposed move. However, it is clear that there was no consensus in the discussion so the close is a WP:SUPERVOTE. Begoon talk 07:25, 19 June 2013 (UTC)[reply]
- Overturn close I'm very surprised that the move request was in any way controversial. Hillary Clinton seems to me to be the obvious (and I would have thought uncontroversial) place for the page. I suspect that if the RM discussion was advertised to a very wide audience it would result in a move to Hillary Clinton. However, the close, as was, just moved the article from one controversial title to another and looks like a supervote. --RA (talk) 12:17, 19 June 2013 (UTC)[reply]
- Adds: I'm not one to make a big distinction between admins and non-admins. I think Obiwankenobi is doing the project a great service by addressing the backlog (in a number of different places). However, I think given the (surprisingly) contentious nature of the RM, it would probably be best to do things by the book. From Wikipedia:Requested moves/Closing instructions:
"If you are not an administrator you should only close certain types of requests; ... Non-admin closes normally require: The consensus or lack of consensus is clear after a full listing period (seven days). ... Many editors do not approve of non-admins closing contentious debates. Non-admins should be cautious when closing discussions where significant contentious debate among participants is unresolved." --RA (talk) 07:48, 20 June 2013 (UTC)[reply]
- Overturn close - This is why non-admins aren't allowed within a mile of discussion (RM, AfD, etc...) closes that aren't crystal-clear snow cases, they don't have the experience necessary or the trust of the community to measure consensus an make the tough call. For move requests, this is clearly laid out at Wikipedia:Requested moves/Closing instructions#Non-admin closure as a failure of criteria #1, "Non-admin closes normally require the consensus or lack of consensus is clear after a full listing period (seven days)." The discussion was fairly evenly split with sound arguments all around, no "i like it" or "it sucks" nonsense. This non-admin cast the proverbial "supervote", he did not take a measure of the discussion in the slightest. This user has also bee on the...how does one say it without using the m-word...critical-of-women side of several wide-ranging discussions lately, including the Novelists categorization (taking women out of "American Novelists") and at Sarah Brown (wife of Gordon Brown), where editors are attempting to rename the article to something non-paternalistic and 19th-century. Following those, attempting to butt in to made decisions on whether a woman is more known by her married name vs birth name + married name was an unwise choice. The primary issue is still ignoring the obvious split and lack of consensus, and closing the discussion improperly. But the "big picture" emerging here is IMO troublesome. Tarc (talk) 12:39, 19 June 2013 (UTC)[reply]
- Overturn close. As much as Obi-Wan insists that there was rough consensus, there was not. There were arguments made on both sides, and the arguments were based on interpretation of policy rather than positions such as "I just don't like it". The name of the article has been stable for many years, and the default result in a situation where there is no clear consensus is not to move; a move performed in the face of clear and well-articulated opposition is naturally going to generate strife, whereas a "no move" due to "no consensus" is naturally not satisfying to the pro side, but also not controversial. He claims that there were "three indisputable policy prescriptions" on the pro side and not on the con side. But of course those interpretations of policy were disputed in the discussion, and of course there were policy-based arguments on the other side. He defines "concise" as "no longer than necessary", but that is an over-simplification of what is stated in the policy, without even getting into the definition of the word. In short, this was a supervote -- though I do not believe that was necessarily the intent. I believe the close was done in good faith but was misguided and should be overturned. Omnedon (talk) 15:17, 19 June 2013 (UTC)[reply]
- Overturn close This was an obvious no-consensus situation - lengthy and contentious enough that it should probably not have been attempted by a non-admin. And that was ObiWan's first impression - no consensus. Once he had read through the arguments and decided which side he agreed with, he was no longer a closer - he was a participant. At that point he should have simply added his opinion to the discussion, not closed with a !supervote. I believe that 1) ObiWan's improper closure should be reverted; 2) either Good Ol'Factory's close should be reinstated, or a neutral third-party admin should decide how to close; 3) ObiWan should be cautioned to avoid doing non-admin closures where the consensus is not clear, per WP:RMNAC. --MelanieN (talk) 15:58, 19 June 2013 (UTC)[reply]
- Endorse Close I was not involved in the original RM discussion but I have read through the arguments there as well as ObiWan's closure statement and the ensuing discussions on his and GoodOlFactory's talk pages. ObiWan made a fair assessment based on the strength (not numbers) of the arguments as they relate to policy to reach his decision. That assessment is no less valid simply because he doesn't wield a mop. The "overturn close" votes are using terms like "lengthy and contentious" and "well-articulated opposition". If that were reason enough to conclude "no consensus", every RM could be filibustered into a no consensus close. Once the extraneous verbiage is removed from the discussion, I agree with ObiWan that there is a rough consensus for HC.--William Thweatt TalkContribs 16:39, 19 June 2013 (UTC)[reply]
- Overturn close This move has been requested several times before, each time without reaching consensus to move; that there still is no consensus to do so is no surprise, and is clear from reading the current discussion. There are strong opinions on both sides, but nothing approaching a consensus, so the appropriate close would be "no consensus" and no move. The closure was inappropriate, and seems to represent an opinion rather than a neutral analysis, and is therefore a supervote, per Slim Virgin, Begoon and others. Tvoz/talk 17:17, 19 June 2013 (UTC)[reply]
- Overturn close. Agree with Omnedon, MelanieN, et al. I think there are various problems here that make it necessary to overturn this, but the most fundamental is that it's inappropriate to move/retitle a stable article without consensus – and the result of the discussion was about as far from consensus as I've seen in move discussions. Good Ol'Factory in his original reversion comments rightly noted that this is not a case where a handful of commentators made flimsy arguments that can be easily overridden by applicable guidelines; it's a situation where there was a large amount of participation from a robust number of commentators on both sides who made convincing, guideline-based arguments each way, and is a classic "no consensus" discussion. ╠╣uw [talk] 17:18, 19 June 2013 (UTC)[reply]
- Overturn close. - There's nothing wrong with non-admin closures in general but Tarc has a point. NACs at xFD and RM can result in this kind of thing. Becuase RM cases usually are contentious and in this case there was "significant contentious debate among participants [that was] unresolved." The close was in good faith but it falls into the catgeory of a supervote becuase, in fact there was no clear consensus in a contentious discussion. As such MelanieN is correct. Suggest reverting the move, relisting the RM and redoubling the advertisment of the discussion--Cailil talk 18:20, 19 June 2013 (UTC)[reply]
- Overturn close – I have no preference either way but there has to be an obvious consensus to change the status quo ... and there is no obvious consensus. Oculi (talk) 18:42, 19 June 2013 (UTC)[reply]
- Overturn close - There was no clear consensus and a slight shift in the frequency of use of HC over HRC doesn't justify this supervote.
- I agree that, on concision and common name, HC beats HRC. But titling policy is not the only policy bearing on this case. Had I noticed the discussion and contributed, I would have supported the status quo (HRC) because she said in 1993 that she wanted to be known as Hillary Rodham Clinton, and that hasn't changed as far as any of us knows. That the subject prefers to be called HRC is a strong and valid reason for us to do so. Trivial factors such as concision or a few more instances of HC in Google are irrelevant compared with respect for our BLP subjects, and the numerous instances of official usage. Regarding this argument:
- Wasted time R's summary of the arguments included that HRC was the name she announced that she preferred in 1993 and is her official name, and most opposers concurred
- Tvoz: "Wasted Time R's recap below sums up the arguments quite well, and I concur completely"
- Huwmankind: "... per J, Tvoz, Wasted Time R."
- TonyTheTiger: "I think the historical reasons and BLP user preferences still carry." (I think this refers to the subject's preference, but I've asked for clarification.)
- Omnedon: "...per Wasted Time R, Huw, and others."
- Tarc: "...has herself emphasized her given name over the last 2-3 decades."
- Smokey Joe: "...preferred in formal use by the subject..."
- Bellagio99: "Wasted R said it well."
- I think we can assume MelanieN and J won't oppose this view either.
- There is no policy that explicitly states that, when a BLP subject prefers a given formulation of their name, and that formulation is very well-known and widely-used, and is the formulation normally used in official situations, we defer to the subject's preference. But boilerplate naming policies are always going to be too clunky to handle all possible subtle and nuanced implications of something as sensitive as a person's name. That's why IAR is a policy.
- Obiwankenobi said above, "my understanding of consensus is that policy-based-arg will beat a logic-based arg any day, unless you IAR." The oppose voters chose to IAR. Obiwankenobi, for reasons yet to be explained, chose to dismiss their IAR argument, and thereby see consensus where there was none. (UTC)--Anthonyhcole (talk · contribs · email) 22:22, 19 June 2013 (UTC) (Expanded 08:02, 20 June 2013)[reply]
- Comment on the NAC portion. No policy says NAC closures of moves is disallowed, nor that NAC has less authority than admin closes. I wish the admin bit made you "better", but I can attest that it doesn't. Being an NAC doesn't matter in this discussion, only the merits do, of which I have no opinion. I will restrict any further comment to my talk page. Dennis Brown | 2¢ | © | WER 22:26, 19 June 2013 (UTC)[reply]
- Comment: Either my ears were ringing or I had an orange
bar button, or both. Admins have no special powers in closing discussions. If there was a problem with the close it should be discussed on its merits and not because the closer was not an administrator. No comment on this specific case because I frankly don't give a crap what that article is titled and can't be arsed to read the RM discussion. -Nathan Johnson (talk) 22:28, 19 June 2013 (UTC)[reply]
- Retain. Although I don't agree with the close - specifically, if I had closed it, I would have found the unambiguous arguments based on WP:TITLECHANGES to be more binding than the hair-splitting around WP:COMMONNAME - I do support the closure as a good-faith, reasonable, and judicious summary of the move discussion, and support retaining the move on that grounds. VanIsaacWS Vexcontribs 22:29, 19 June 2013 (UTC)[reply]
- Overturn (no consensus). Obvious no consensus borderline needing further and wider input. The close was well beyond the nebulous "admin discretion" and squarely into WP:Supervote. If the closer can't close without going beyond a summary of points already made, it is a Supervote.
On the NAC issue, we are not overturning because it was a NAC, however, NAC closers would be well advised to steer clear of closing less-then-clear discussions. I note that the NAC closer has abandoned usual admin decorum in letting his close be reviewed as it stands, and accepting the decision of the community. For better or worse, this is one of the skills proven or learned from passing through the baptism of fire known as RfA. I stand by my comments in the discussion linked by the closer, Wikipedia:Village_pump_(policy)/Archive_91#Non-AfD_NACs. --SmokeyJoe (talk) 00:14, 20 June 2013 (UTC)[reply]
- Don't you think it would be more of a supervote if the closer had to go beyond what was in the discussion? A closer is supposed to weigh arguments given. --BDD (talk) 16:19, 20 June 2013 (UTC)[reply]
- Isn't that what I wrote? --SmokeyJoe (talk)
- Maybe I didn't phrase that right. You seemed to complain that the closing statement rehashed the support votes, that Obi-Wan's failure to go "beyond a summary of points already made" indicated a supervote. I was suggesting a better sign of a supervote would have been new arguments on the part of Obi-Wan presented as closing rationale. --BDD (talk) 19:22, 21 June 2013 (UTC)[reply]
- I don't mean to complain of a rehash of support votes. A summary of similar rationales is very good. A failure to go "beyond a summary of points already made" is not indicative a supervote. A closer should not go beyond the points already made. New arguments by the closer are indeed the feature of a supervote. I think I wrote a poor sentence with a double negative that can be misread. I seem to be in complete agreement with you. --SmokeyJoe (talk) 07:00, 23 June 2013 (UTC)[reply]
- On considering other points made below...
- On LOCALCONSENSUS versus CONSENSUS:
Note that the applicable titling policy and guidelines are controversial, littered with a history of problematic battles and bad behaviours, and themselves are not unambiguously reflecting of wide community consensus. They are also poorly organised, overlapping, and poorly explained, indicative of an imperfect state, indicative of a weak connection to true community consensus. The RM discussion drew a large number of participants, perhaps a selection more representative of consensus than the self-selected authors of the few lines of applicable policy. Policy is supposed to reflect actual practice. It is simply unacceptable for a single editor, supervoting, to disregard a wide selection of community members in favour of controversial policy. This close should be overturned as a SuperVote. Further, it should be overturned as it clearly does not carry the confidence of the community. The closer should learn from this, and will probably become a better closer for it. If overturned, the overturn should have no bearing on continued discussion. Continued discussion may find a clear consensus on this title, but it hasn't happened yet. --SmokeyJoe (talk) 07:06, 23 June 2013 (UTC)[reply]
Endorse close (I voted to support the move). Re-reading the discussion I think the closer made a reasonable call to move, based on what he perceived as weak arguments by those opposed to the move -- consensus isn't a vote count so this seems like a fair outcome. Had the closer been an admin I doubt we'd be having this discussion. Calidum Sistere 00:37, 20 June 2013 (UTC)[reply]
- after reading more about the user who closed this discussion, I am no longer comfortable with him having closed it and would be more comfortable of this were relisted so someone else could look at it. Calidum Sistere 21:20, 23 June 2013 (UTC)[reply]
- Endorse close (although I voted to support the move, so my endorsement might not be too surprising). This is an inherently-difficult choice, and I think the closer did as good as anyone could do. It's such a prominent and controversial person, and the maiden name issue is also so difficult, that you'll never get a snowball on this question. The discussion could have gone on forever. It was the 5th time the same move had been requested (somehow I had previously miscounted it as the 6th), with all previous ones closed as "no consensus". Movement in sources toward the shorter name was evident. It's time to let the article have the other name for a while and see what happens after that. —BarrelProof (talk) 01:00, 20 June 2013 (UTC)[reply]
- Endorse close I did not vote in favor of the move, but I support it. I think that user's preference rather than subject preference for the name should prevail. Without getting into the nitty gritty of all the possibly relevant policies, I think this is a better solution to the neverending debate.--— Preceding unsigned comment added by TonyTheTiger (talk • contribs) 16:01, 20 June 2013
- Endorse close. Likewise, I voted for the move, so no surprise here. But she is known around the world as Hillary Clinton. It is by far her commonest name. Her own preferences are immaterial, as is her "official" name on any organisation's website. Who actually calls her Hillary Rodham Clinton outside official publications and some overly formal media outlets? Would you really say "I hear Hillary Rodham Clinton is going to visit Outer Mongolia"? Really? No, of course you wouldn't. I would hazard a guess that many people didn't even known her middle/maiden name was Rodham. We are merely going around in circles here. Best to once and for all move the article to the name by which she is best known and follow our own naming conventions. -- Necrothesp (talk) 16:10, 20 June 2013 (UTC)[reply]
- Overturn close. Appalling to see anything resembling consensus to move in that discussion. older ≠ wiser 16:27, 20 June 2013 (UTC)[reply]
- Relist and publicize to the community more broadly, to avoid an endless cycle of this sort of thing. bd2412 T 17:18, 20 June 2013 (UTC)[reply]
- I agree, and best idea I've heard so far, although I almost think there needs to be a wider policy and naming conventions discussion on whether the wp:officialnames essay properly handles preferred matronymic names and other variants of that concept first. The wp:officialnames essay shouldn't — and I believe the the spirit of recognizing common usage doesn't — cancel a woman's preference for hyphenated or joined "First Maiden-Married" or "First Maiden Married" names that are in wide usage. It didn't get discussed as much as it probably should have in the original requested move discussion, but I think the last few comments from User:Anthonyhcole below in the extended discussion are particularly interesting. user:j (talk) 17:34, 20 June 2013 (UTC)[reply]
- Endorse close. I see an awful lot of comments above asserting that there was no consensus, but very little argument in support of that claim. Unless you can actually point out where the closer's reasoning went wrong, simply stating that he was wrong is meaningless. Remember, consensus is more than just counting numbers. The closer correctly analyzed the quality of arguments, and noted that there was, in fact, consensus on several of the points, and the logical outcome of that agreement is a move. Powers T 17:33, 20 June 2013 (UTC)[reply]
- Endorse close. As the nom and involved editor I wasn't going to participate here, but so many participants have chimed in above (many without identifying themselves as being involved), I figured I may as well weigh in too. First, I commend Obi for providing such a thorough explanation of how and why consensus was determined that those opposing the move and now supporting overturning his decision are almost completely ignoring his solid reasoning.
Those favoring overturning this decision are almost unanimously simply claiming there was no consensus, but what they seem to be mean by "no consensus" is "no WP:LOCALCONSENSUS". However, the closer is tasked not with determining WP:LOCALCONSENSUS, but with determining community WP:CONSENSUS. In theory, it shouldn't matter how many people participate in one particular discussion or how many of them favor one side or another. What should matter is the arguments presented and how well they are based in policy and conventions. Whether 5 participate with 2 to 3 favoring moving, or 50 participate with 40 supporting moving, if the arguments indicate community consensus favors the move, then that should be the finding. If not, then not. If people don't think greater usage of one name in reliable sources, along with that name being more concise, indicates that name should be the title, for whatever reason, then they need to get consensus to update the relevant policies to say that. But right now there is no policy basis for this. We do lack a clear WP:LOCALCONSENSUS favoring the move, but, per the arguments presented in the discussion, we have clear community WP:CONSENSUS favoring the move. And that's what Obi explained in his closing (and again above), and that's what matters. Great job, Obi. Bravo! I for one, am very impressed, and will hold up this close as an example for other closers to follow. --B2C 20:15, 20 June 2013 (UTC)[reply]
- B2C, I would remind you that you were directed to disengage from discussion of this move. Omnedon (talk) 20:48, 20 June 2013 (UTC)[reply]
- will hold up this close as an example for other closers to follow - maybe you'd better wait and see if this close holds up, before you do that. --MelanieN (talk) 21:44, 20 June 2013 (UTC)[reply]
- Endorse close with several caveats. This is going to fundamentally change the way we treat non-admin closers if this holds up. I would agree with that change, personally; we'll probably have to change the closing instructions if this stands (and again, I think that's a good thing, but maybe you don't).
Second, this is big--this has a great chance to prove the WP:Yogurt rule because I am almost certain that there will be no successful request (perhaps not even a proposed request) to bring back HRC as a title if you declare consensus was reached to move to HC.(We'll see in a year or two.) ThirdSecond, it should serve as a textbook case of how to close a move request. Did you see what Obi wrote? I don't think I've ever in my life considered any issue ever with as much care and wisdom as he showed. [citation needed] I supported the move for reasons that are clear and I think he did alright closing this, but you probably can't consider my !vote here as valid. Keep in mind, closer, that this is a big deal. Please treat it carefully. Red Slash 22:08, 20 June 2013 (UTC)[reply]
- Comment. Obiwankenobi invited me to comment here, but I pretty much said all I had to say in the move discussion itself and in all the ones that preceeded it. I am a bit disappointed that a non-admin decided to jump in and close this, but I don't normally hang around MR or DRV so I don't know whether that was proper or not. Similarly, I never heard of the "supervote" concept until now, so I don't know whether this was a violation of that or not. I do know this this is actually the seventh go-around for this issue - the five formal RM's were preceded by this discussion in early 2006 and this flap in early 2007, where it was briefly moved before being moved back. I always figured that if it was put up for moves enough times, sooner or later by randomness if nothing else, it would succeed. Regardless of outcome here, though, I would hope this does not cement in place the "Yogurt Rule", which for reasons I gave at the end of the move discussion I think is more than a little arrogant and dismissive. Wasted Time R (talk) 01:16, 21 June 2013 (UTC)[reply]
- Overturn close, on grounds of improper assumption of closer role. For the first time, I've taken a look at the ongoing Talk:Sarah Brown (wife of Gordon Brown)#Requested move 6 (June 2013), and the point others have raised here is valid. Obiwankenobi is an advocate with many posts there, in a long and pretty heated debate that involves many of the same cast of editors who appeared in the Hillary RM (including B2C, Tarc, SmokeyJoe, Kauffner, and the admin who first implemented Obiwankenobi's close, Timrollpickering). It does not seem right that a participant in one debate promotes himself to be the judge in another debate involving some of the same people, especially when that participant is not even an admin in the first place. Note that I'm not saying that Obiwankenobi showed actual bias or bad faith; like all conflict-of-interest situations, it is the appearance of a possible conflict that is the problem, not an actual deed. The situation is even more worrying if, as I suspect, this MR proves inconclusive and the outcome is (like in the video replay review guideline in American sports) to let the original close stand. Wasted Time R (talk) 11:49, 21 June 2013 (UTC)[reply]
- Endorse close, but reject yogurt rule and use of this close as a precedent (I didn't !vote, but think WP:RS look slightly weighted on merits towards Obi-Wan's close). Overturn because despite Dennis Brown's modesty several recent non-admin closes have been of lower quality than most admin closes. What is more of a concern is "will hold up this close as an example for other closers to follow" - that sets alarm bells ringing. As for WP:Yogurt rule that essay IMHO deserves an AfD or to be clearly moved into a user sandbox, the only thing Yogurt shows is (a) after enough fighting, editors get sick and accept anything, and (b) Yogurt is part of a trend of spelling words closer to native (in this case nearer to Turkish) spelling. In ictu oculi (talk) 02:30, 21 June 2013 (UTC)[reply]
- Clarify - if the issue of precedent and Yogurt hadn't been raised I would be saying Endorse close this non-admin close is one of the better non-admin closes, and Obi-wan more competent in this area than some admins. Alternatively those who made them strike their precedent and yoghurt comments and keep to the actual move then no problem. In ictu oculi (talk) 02:54, 21 June 2013 (UTC)[reply]
- Your take on the Yogurt rule is possible; it's also possible that it shows that inertia is always difficult to overcome. But regardless, we're going to have some form of precedent created. That always is the case on Wikipedia. And I have no idea what a couple of editor's takes on precedent stated at a move review have to do with whether or not Obi's close correctly gauged consensus. It almost seems pointy to say that, like you're saying "drop this or else I won't support something you guys and I all actually believe in". Please clarify this misconception I have. Red Slash 05:05, 21 June 2013 (UTC)[reply]
- You do not have a misconception. My concern is that B2C and yourself are attempting to create a bandwagon here. I have said clearly that I would like to endorse Obi-Wan's close and have confidence in Obi-Wan's judgement. But at the same time I echo the comment of Wasted Time R "though, I would hope this does not cement in place the "Yogurt Rule", which for reasons I gave at the end of the move discussion I think is more than a little arrogant and dismissive." As for point, my point is this - your comment "Second, this is big--this has a great chance to prove the WP:Yogurt rule because I am almost certain that there will be no successful request (perhaps not even a proposed request) to bring back HRC as a title if you declare consensus was reached to move to HC." is highly disruptive. You and B2C shouldn't be making this a bandwagon issue. I hope that the decision goes in favour of Obi-Wan on this, but with clear disowning of any talk of "precedent" or "Yoghurt". In ictu oculi (talk) 06:13, 21 June 2013 (UTC)[reply]
- Oh dear. I could give a rip about the "yogurt rule", seriously. But it's a fine essay and it's a well-reasoned point of view. My point with citing it was that I'll bet that if the move stands, no proposed move a year from now back toward HRC would come close to having consensus. But that's an unproductive thing to say and is mere crystal-ball gazing. Unfortunately, it seems to have upset you, which is regrettable and I apologize for having disturbed you so. I'm not married to that essay and honestly it doesn't really add anything to my argument. I'll strike it out as an olive branch, as it were. Red Slash 09:44, 21 June 2013 (UTC)[reply]
- Thank you. I have amended my first line for clarity to "endorse close, but reject yogurt rule and use of this close as a precedent" In ictu oculi (talk) 13:53, 21 June 2013 (UTC)[reply]
- Endorse close, considering the fact that this his the name she's most well known by. — Preceding unsigned comment added by Canuckian89 (talk • contribs) 07:07, 21 June 2013 (UTC)[reply]
Endorse close The article has to be located at some name, and I'm not a fan of "no consensus, default to what was there before". Given the two proposed names, it should be possible to make a decision that puts the article one place or the other, rather than resorting to the cop-out (as the closer said, I had the same issue when closing the latest [also controversial] move request for Burma). And I believe the closure's result is, while not uncontroversial, within discretion based on the arguments put forth. Specifically, the biggest blow to the opposition is that most seemed content with "we debated this just a couple months ago" and "she's been called that for decades". Consensus and usage can change. -- tariqabjotu 13:51, 22 June 2013 (UTC)[reply]
- Overturn close. Closer is not qualified to make this contentious judgement. -- tariqabjotu 03:13, 23 June 2013 (UTC)[reply]
- Overturn close - the massive wall of text below, and on various user talk pages, demonstrates amply that in not being able to find a simple black and white consensus, Obi-Wan-Kenobi began to tease apart the shades of gray. Shades of gray, however, are just that, and equal no consensus. Victoria (talk) 16:53, 23 June 2013 (UTC)[reply]
- Overturn. I've only skim-read the above comments, but I've thoroughly read the RM discussion and there was no consensus to move the page with the strongest opposition argument being that it is the name still most commonly used on first mention in high-quality media, and the strongest supporting argument being that the shorter form is the most common usage over all in recent coverage. The "yogurt rule" so favoured by the nominator is not a rule but an essay written by the nominator inviting tendentious editing. Combining this with the history of this article I would strongly support a moritorium on new RM discussions for this page for at least a year and there has a been a clearly demonstrated shift in usage relative to now (both conditions must be true). Neither title is incorrect or misleading so keeping it at whichever title will not harm anyone. Thryduulf (talk) 18:09, 23 June 2013 (UTC)[reply]
- Overturn. I believe this will be a first, but I do not see that the closer gave adequate weight to the various considerations. And whenever there is "rough consensus from both sides", the status quo stands. I do though, commend the closer for jumping in and hope that they will attempt more closes, as the backlog has only gotten longer. Apteva (talk) 02:46, 24 June 2013 (UTC)[reply]
- Overturn It appears the closer has a vested interest in relation to the close, and there clearly wasn't any consensus to move. AniMate 04:08, 24 June 2013 (UTC)[reply]
- Endorse A majority of editors in the discussion supported the move, and their arguments were based on policy. Some oppose voters made very weak arguments, such as procedural complaints. That's enough for me to say consensus. It wasn't a strong, blowout consensus, but so what? And, recognizing B2C just kind of came up with the Yogurt Rule, I think there's a very real chance that it will prove to be a valuable principle, and that a Hillary Clinton title would be more stable. Obi-Wan probably should have left the close to an administrator, but the right decision was made. As an active RM admin facing a significant backlog, I appreciate the help of non-admins in good standing helping out, and I don't appreciate editors latching onto that status to object to a move they just don't like. --BDD (talk) 21:31, 24 June 2013 (UTC)[reply]
- Some support !voters made very weak arguments, such as procedural complaints, as well. I don't think procedural concerns were the crux of the argument for those on either side, though. Likewise, there were policy arguments made supporting the article remaining at the title including "Rodham," as well. Culling those two points of your endorse, it seems to boil down to, in yours words, "a [slim] majority of editors in the discussion supported the move," which I'm sure is just as inaccurate a summary of your logic as is your unconsidered dismissal of those opposing the move with wp:idontlikeit. user:j (talk) 23:30, 25 June 2013 (UTC)[reply]
- No, that's not really an inaccurate summary of my logic. Some people like to bandy about WP:NOTAVOTE, but when both sides make policy-based arguments (which is really the norm), the majority opinion should be preferred in absence of a compelling reason not to. Besides the danger of endorsing supervotes, ignoring majority opinions is only going to irritate and alienate editors. Yeah, it wasn't a huge majority, but would one more editor chiming in with "Support per whoever" be enough for clear consensus? Two? Three? How much of a majority is necessary? And whatever you think of the yogurt rule, it's applicable here. Not counting anyone who would feel wounded over this decision, we're unlikely to see a new RM to re-insert the middle name. --BDD (talk) 05:45, 26 June 2013 (UTC)[reply]
- Narrowly more editors "chiming in with 'support per whoever'" than the alternative does not a consensus make, clear or otherwise. Which is one of the reasons why twice as many of the editors in this review who did not participate in the original discussion have voted to overturn the close. (By my rough math, for those uninvolved in the original requested move, it's twelve to overturn, five to endorse. Including those who participated in the original discussion, it's 21 to overturn, 13 to endorse.) user:j (talk) 08:40, 26 June 2013 (UTC)[reply]
- Endorse close. An article has to have a title, whether a consensus for any particular title exists or not. Obiwan has given an exceptionally well-reasoned analysis of the issues involved in selecting this title. Various recent events, including the establishment of a "Hillary Clinton" Twitter account, suggest that subject now wants to be referred to this way, or has at least made her peace with the fact that people will continue to refer to her as Hillary Clinton whether she likes it or not. Her 1993 name-clarification announcement is pretty stale at this point. Kauffner (talk) 01:28, 26 June 2013 (UTC)[reply]
- The Twitter myth was thoroughly debunked in the requested move discussion. It would not technically have been possible for her to have chosen @HillaryRodhamClinton, nor would it have been possible for her to have used "Hillary Rodham Clinton" as her display name. Both are considerably longer than Twitter permits (in order to maintain backwards compatibility with SMS character limitations). Further, her official biographies (ignoring the fact that "official" is a dirty word due to an essay here) continue to refer to as "Hillary Rodham Clinton" on first reference, so I don't think her 1993 statements can be described as "stale" nor discarded. user:j (talk) 01:59, 26 June 2013 (UTC)[reply]
- It's 15 characters for the username, 20 for the display name.[3] So she could be "HillaryRodhamClinton@HillaryRClinton" if she so desired. Kauffner (talk) 04:00, 26 June 2013 (UTC)[reply]
- You made my point for me by pointing out how absurd both of those look. Her name isn't "HillaryRClinton," it's Hillary Rodham Clinton. I have not, even once, seen "Rodham" reduced to an initial on anything from the White House, her Senate office, nor the Department of State. I think it would be reasonable to assume, when it can't be spelled out, she'd probably rather it be omitted. Thankfully, we can have article titles much longer than fifteen characters here at Wikipedia. :) user:j (talk) 07:22, 26 June 2013 (UTC)[reply]
- Paying attention to twitter reflects very poorly on us with respect to the building of a respected, authoritative, reference work. We should be looking at reputable reference and academic publications, not recently fashionable social media. --SmokeyJoe (talk) 08:12, 26 June 2013 (UTC)[reply]
- Oh, you don't know the half of it. They have this thing nowadays, it's called "the news media." It's like some sort of newfangled version of Acta Diurna, if you can imagine that. This was huge in the US media, with Hillary Clinton Twitter getting almost 76,000 GNews hits. I linked to the Washington Post`s version above. Kauffner (talk) 09:40, 26 June 2013 (UTC)[reply]
- Just to set the record straight, Hillary Diane Rodham has never legally changed her name. It has always been Hillary Rodham. She went by Mrs. Bill Clinton and Hillary Clinton beginning in 1982 to help her husband get elected. She went by Hillary Rodham Clinton beginning in 1993 and throughout her political career, although in 2008 her presidential campaign, and not her, referred to her as Hillary Clinton in 49 states. In New York she was still called Hillary Rodham Clinton. But she is clearly best known as Hillary Rodham Clinton, and that is the name used as author for all of her books. Apteva (talk) 16:07, 26 June 2013 (UTC)[reply]
- So her campaign couldn't get her name right? Surely she is better known as a politician than as a book author. Kauffner (talk) 21:37, 26 June 2013 (UTC)[reply]
- Let go of the Twitter myth, Kauffner. It, by far, is the least persuasive argument that was made in the original move request, and it's even less persuasive here (as this is not — at least it is not supposed to be — a revote). As was previously pointed out to you, her preferred name wouldn't fit if typed properly. But it's really quite irrelevant, as Twitter is probably the least desired method for us to source an article title from, especially when there are sources such as, say, the New York Times.[4] user:j (talk) 21:53, 26 June 2013 (UTC)[reply]
- So if they allowed 22 characters, she would gone have with "Hillary Rodham Clinton", but a display name like "HillaryRodhamClinton" would have cramped her style? Hey, believe that if it makes you feel happier. Whether Twitter handles in general are a good source for names is beside the point. This one has been hugely publicized and analysed. I thought if I took an example that was currently in the news, it would be more likely to strike a chord. As far as the New York Times goes, both the Wall Street Journal and USA Today are more widely read. Kauffner (talk) 23:54, 26 June 2013 (UTC)[reply]
|
- Being bold and closing the discussion is okay. But running and hiding to avoid scrutiny after is another. Calidum Sistere 22:47, 26 June 2013 (UTC)[reply]
- Calidum, who or what does this comment refer to? You can't possibly be talking about Obiwan, who engaged in the present discussion vigorously and repeatedly, and only stopped because he was criticized for engaging too much. --MelanieN (talk) 23:43, 27 June 2013 (UTC)[reply]
- Discussion
- @SlimVirgin, what does Tim have to do with this? GOF reverted my close, and moved the pages, then reverted himself, and moved the pages back, so Tim's work has already been undone twice by another admin. I don't think he needs to be dragged through the mud here for simply enacting a close.--Obi-Wan Kenobi (talk) 07:32, 19 June 2013 (UTC)[reply]
- @Tarc: "This is why non-admins aren't allowed within a mile of discussion (RM, AfD, etc...) closes that aren't crystal-clear snow cases" Where do you find this guidance? The most recent thread I could find on this, here Wikipedia:Village_pump_(policy)/Archive_91#Non-AfD_NACs seemed pretty clear that non-admins closing discussions was ok, and even welcome, even for controversial closes. They gave several examples of non-admins closing highly controversial discussions, like Ireland/Republic of Ireland. Also, I don't appreciate your bullshit characterization of what I did during the novelists fiasco. I never once ghettoized a woman novelist by removing her from a category with men and leaving her only in a category with women, and I de-ghettoized at least a hundred, developed a de-ghettoizing algorithm, and am currently working with a developer on category intersection which will solve this problem en-masse if it works. In any case, what happened there is completely irrelevant to this close. Shall I drag in your multitude of insults over the years to (basically, everyone) to discredit your comments here?
- @Everyone else: You may notice Tarc's subtle character attack and name calling. This is rather droll, coming from someone who has a whole website out there devoted to cataloging his well-known bullying ways. I won't even quote some of Tarc's most foul utterances, but suffice to say they are not for the faint of heart.--Obi-Wan Kenobi (talk) 13:13, 19 June 2013 (UTC)[reply]
- My "guidance" come from both common sense and WP:NAC, which you can review at your leisure. As for the "whole website", I presume this is in reference to Daniel Brandt's blog? Brandt is a boogeyman from Wikipedia past, long known for "doxing" many admins and editors but sadly also known for some laughingly inaccurate summations. The small bits that are truthful are entirely off-wikipedia, i.e. beyond your purview. We're talking about your actions here, anyways; less deflection on your part would be good. Tarc (talk) 13:30, 19 June 2013 (UTC)[reply]
- @Omnedon, I realize it was you who was making the terminology discussions around "concise". I've read WP:AT several times, and the description of concise, is, well, concise. It says: "The title is no longer than necessary to identify the article's subject and distinguish it from other subjects." So I think my interpretation of the arguments for conciseness was in line with policy, and your arguments went beyond it.--Obi-Wan Kenobi (talk) 15:54, 19 June 2013 (UTC)[reply]
- In the survey section above, you only used the first four words of the sentence and clearly gave that as the full meaning. It is not. In any case, the fact that the sentence follows the word "conciseness" doesn't somehow provide a new definition of the word. Omnedon (talk) 16:21, 19 June 2013 (UTC)[reply]
- Sorry, I've corrected that to have the full definition above. I don't think it changes a thing. I looked at this issue of conciseness quite carefully, as I mentioned it was one of the policy points that tipped the scale in my mind, and if you look again, you will see that MANY of the support !votes mentioned it, while only 2 by my count opposed it - you, and J. J said concise means "as brief as is encyclopedically possible." - this is an interpretation, not covered by policy, no-one else took it up, so I discounted it. You said "It's not only about brevity -- concision strikes the balance between brevity and comprehensiveness". In my original analysis, I also discounted your argument - first because no-one else made it, even those on your side, and secondly, because the policy doesn't say that (in fact the lede of WP:AT says: "the ideal article title resembles titles for similar articles, precisely identifies the subject, and is short, natural, and recognizable." so they use SHORT to fill in for CONCISE). In general, if a wikipedia policy uses a word, and then defines what we mean by that word right after, that holds more weight than a dictionary definition of a word.
- However, even if I do grant you that, and we assume concise really means brevity + comprehensiveness and that is what was fully intended in WP:AT, you didn't follow up that argument to demonstrate that Hillary Clinton is somehow less concise that Hillary Rodham Clinton - e.g. that HC is NOT a comprehensive, brief description of the subject, and no-one else took up that argument either.
- Concise and WP:PRECISION was a weak point in the oppose argument, while the support side hammered on it again and again,
and so it's not surprising you're now harping on it and trying to lawyer your way around it, but in my neutral judgement, the oppose team did not put forth a good case why HRC is either precise enough vs HC (with WP:PRECISE, the explicit goal is precise enough, but no more), nor did they make a strong case why HRC is somehow more concise than HC. If such arguments had been made, I would have considered them.
- My assessment, as stated many times, is that HC beats HRC for precise and concise, the support votes hammered this point home, and there was little resistance. What was *not* sufficiently recognized, IMHO, in the discussion, was the fact that some people were arguing from policy, while some people were arguing from "other stuff" - but it's the job of the closer to judge adherance to policy, and then guidance. "Consensus is determined by the quality of the arguments given on the various sides of an issue, as viewed through the lens of Wikipedia policy."
- The resistance that was there to concise was of the form WP:OSE - e.g. we have Dwight_D._Eisenhower and Lyndon B. Johnson and Boeing B-17 Flying Fortress etc. I personally am not against WP:OSE arguments, as they demonstrate a consensus elsewhere in the wikipedia, and if broad enough, can be used to demonstrate a global consensus. However, WP:OSE arguments cannot compare to a clear, crisp, policy-based argument. You have to weigh the weight of different types of appeal to authority, and appeal to policy is the strongest of all.--Obi-Wan Kenobi (talk) 18:36, 19 June 2013 (UTC)[reply]
- Now you are bordering on being offensive. I am not trying to "lawyer my way around" anything; you have spent a great deal of effort parsing policies, but when someone else does it, they are lawyering?. I have assumed good faith on your part; you need to do the same.
- The definition of "concise" has figured in several other discussions in which I've been involved. It is frequently misunderstood to mean the shortest possible title. As for the phrase "as short as encyclopedically possible" -- this IS an encyclopedia, so that is a clarification, not an interpretation. You do not have the right to discount an argument simply because only one person makes it, or because it is not made with a large number of words again and again.
- You used the phrase "hammered away" when referring to the pro side, as if you somehow feel that repeated application of the same argument over and over is supposed to make it more valid. There was disagreement throughout the discussion as to what reliable sources to use, and which should have most weight, and there were arguments on both sides using that same principle as a basis.
- As for "short" "filling in" for "concise" in the nutshell of WP:AT -- for one thing, "short" is one thing and "shortest" is another. In any case, the nutshell is just that; it cannot encapsulate the entire policy.
- You mention that many supporters use an argument while only two opposers use it -- yet you have many times dismissed the idea of vote-counting. This is a form of vote-counting; it seems to matter to you very much how many times a single argument is applied and restated, and with how much vigor. Some editors make their arguments in shorter forms, and some do so with a great deal of wordiness, and not all editors on one side chime in to agree with what has already been stated by someone else. Yet you seem to give more weight to those that talk more loudly. Omnedon (talk) 21:47, 19 June 2013 (UTC)[reply]
- I didn't !vote count as stated, but I did weigh policy-based arguments more strongly if more people referred to them and provided evidence and arguments thereto- that is what WP:CONSENSUS tells us to do (there's an explicit quote, I can find it you need) I did not mean to be offensive and I struck that section above, so I'm sorry. I agree, there was a good discussion about which reliable sources to use, which is why COMMONNAME was not the deciding factor for me, and I wouldn't have found for a move based on that alone - it was clear cut application of the other two policies which swayed the balance - and the fact that multiple supporters referenced those policies (which means I did not supervote that idea into existence).--Obi-Wan Kenobi (talk) 22:00, 19 June 2013 (UTC)[reply]
- Obiwankenobi: Here and elsewhere you say you simply "weigh policy-based arguments" or just "follow where the arguments take you", but I should point out that you're doing more than that: you're making decisions about which arguments you yourself favor based in some cases on more (or less) than the results of the discussion itself, and in some cases on more than just policy. (And regarding policy arguments in particular, I'll come back to those later.)
To take just one example: you've stated several times that you think that on the subject of COMMONNAME, opponents "lost on strong evidence", and cite in your conclusion that you consider an ngram chart showing different frequencies of usage of shorter and longer forms of the same name in books "a great example" (while noting that opponents didn't contest the differing figures). However, this begs the question (which was explicitly debated without reaching consensus) of whether ngram counts are even a suitable metric in the first place when comparing longer and shorter forms of a single name for the purposes of titling – an apropos question given that abbreviated forms are often used for expediency after a longer but favored form is first established or understood through context. Some asserted that the ngram was a good basis, others that it was not. You decided that it was, but I don't see how that can be considered a policy decision. What policy governs how/when/whether a frequency ngram in a book is appropriate to determination of title, or how much weight it should receive? I don't think there is one. Instead, this was a point that required consideration through discussion, and indeed it was both considered and challenged, with commentators coming down on both sides of the issue. In a similar vein, you dismiss one side or the other on a contested point with statements like "I found this argument weak" and "I don't think there's lots of evidence..." It may very well be the case that you yourself favor some arguments as stronger (or reject some as weaker), and in fact this does appear to be the case since you explicitly say so yourself. However, many others – the RM's participants – clearly disagreed. As some like MelanieN have already correctly pointed out, your favoring of a particular views in a divided discussion would be perfectly acceptable as a participant in the discussion, since that's the role of participants: to voice their opinions on relevant matters, discuss why they hold them, and work in good faith to reach consensus. However: you chose not to be a participant in the debate, and instead assumed the role of a closer – and that role is different. I guess to put it simply, this seems to be a situation where you as an editor had the well-intentioned but nonetheless mistaken goal of trying to "pick a winner" in a divided discussion that lacked consensus. Further, it was undertaken by not just evaluating the results of the discussion but by making your own determinations of which arguments (both policy and non-policy) you personally considered weak or strong – again, done in spite of a lack of consensus on such matters from lengthy and honest discussion by the participants themselves. I think it needs to be clearly understood that a finding of no consensus in such a situation is perfectly appropriate, but for a closer to somehow impose a consensus extracted from a discussion that has not clearly produced one – despite considerable discussion and valid arguments voiced by many users on both sides – is not. ╠╣uw [talk] 10:28, 20 June 2013 (UTC)[reply]
- Thanks for your thoughtful comment. I urge you to read WP:CONSENSUS and especially Wikipedia:Closing_discussions#How_to_determine_the_outcome. The word "judgement" and "quality of arguments" appear, and closers are explicitly given the role to reject or discount arguments not based on policy. They aren't supposed to bring NEW policies into play, but only use those policies which the majority of participants invoke, which I did. Thus, when I say an argument is "weak", what I mean is, "Not based on policy" or "logically fallacious" or "irrelevant" or "flatly contradicts policy as written". I already mentioned below that there was extensive discussion on COMMONNAME and ngrams and analysis and so on, and while my read was that the evidence and consensus from the majority of participants was still that COMMONNAME applied for Hillary Clinton (even some oppose !voters conceded this), that was not the determinant. In other words, all else being equal, I would not have found consensus for move ONLY based on COMMONNAME, because of the vigorous debate. However, the debate was much less muted on WP:PRECISION and WP:CRITERIA, and the oppose arguments for why HRC fit WP:PRECISION or Concise better were rejected by me as NOT ADHERING TO POLICY. It was a judgement call, and all closers make judgement calls of how well an argument applies to a policy, and the guidelines for closing explicitly give rights to the closer to reject arguments that aren't based on policy. That is the very definition of a close in a complex discussion. Anyway, I've said enough here. I was NOT trying to pick a winner, as I stated many times already, I went in with intention to close as NC, and only through careful analysis found that there was a clear policy-based consensus to move.--Obi-Wan Kenobi (talk) 13:44, 20 June 2013 (UTC)[reply]
- I've followed up in more detail in our discussion at my talk page; I think that's preferable in order to avoid further spamming this forum. Anyone interested, please read on there.
- One small item I'll briefly note inline before signing out is that WP:CONSENSUS calls for discussion participants to advance reasons based not just in policy but also in sources and common sense. To say "x isn't policy, so I'm rejecting it" ignores this and devalues the important role of discussion in ensuring sensible, community-approved action – rather than (as we have here) a single editor's opinion about what "ADHERES TO POLICY" (emphasis yours) in a discussion that produced no agreement. Anyway, continued on the talk page... ╠╣uw [talk] 02:06, 21 June 2013 (UTC)[reply]
- @Cailil, I obviously disagree, but especially on SUPERVOTE - I hope you will reconsider your analysis. A contentious discussion does NOT mean NC; when one side has policy on their side, and the other side is making WP:OSE arguments or WP:THETITLEHASBEENHEREALONGTIME, there can still be a consensus decision that goes against the wishes of the oppose side, and that does not make it a supervote. That's what surprised me here - at first glance, it does seem like NC, but when you look at policy-based vs non-policy-based arguments, and map them all out (which I did), there is a clear winner in terms of adherence to policy. I actually thought it would be more balanced than it was. Commonname, WP:PRECISE, and conciseness - these are all headline items in WP:AT, and Hillary Clinton passes all of these tests with flying colors.--Obi-Wan Kenobi (talk) 18:42, 19 June 2013 (UTC)[reply]
- How many times do you plan to repeat this? And when are you going to acknowledge the plain language at WP:RMNAC: "Non-admin closes normally require: The consensus or lack of consensus is clear after a full listing period (seven days)." ? — Preceding unsigned comment added by MelanieN (talk • contribs) 20:02, June 19, 2013 (UTC)
- As I mentioned above, my first reaction was that this was a clear NC close. Further study convinced me this was actually a clear consensus close, once you focus on policy-based arguments, which is what CONSENSUS MEANS. I acknowledge that language, but the presence or lack of a bit is no longer relevant to this discussion, which should be judged on its merits.--Obi-Wan Kenobi (talk) 20:11, 19 June 2013 (UTC)[reply]
- You may consider the non-admin issue irrelevant; I do not. One of my proposals above was that you should be counseled about non-admin closures. Your continued refusal to recognize the obvious - that this discussion was not an appropriate one for a non-admin closure - makes me wonder if you understand what non-admin closure is all about, or if you should be enjoined from making any further closures. That is not something for me to determine, but I bring it up for consideration by those whose role it is to think about such things. --MelanieN (talk) 20:33, 19 June 2013 (UTC)[reply]
- Read this, then get back to me. There is no clear consensus that non-admins can never close any contentious discussions anywhere on the wiki. If you want to make that the case, start an RFC, but you will likely not prevail. Non-admins have closed some of the most contentious RMs in wikipedia history, such as Ireland/Republic of Ireland. Try arguing this particular case on it's merits MelanieN, not on mop-lackingness.--Obi-Wan Kenobi (talk) 20:47, 19 June 2013 (UTC)[reply]
- That was just a discussion, with various people chiming in, and no summing up or conclusion reached. It certainly did not result in any change to the clear instructions at WP:RMNAC. --MelanieN (talk) 20:56, 19 June 2013 (UTC)[reply]
- Yeah, well this is *also* just a discussion - and the one I pointed you to had some very good points, made by some very senior editors. I wonder if *you've* read the instructions at WP:RMNAC. They say, for example, "normally" require, not "always" require. They also say such a move should not be reverted just because the person was not an admin. And they don't define for whom consensus must be clear. In any case, that's what MR is for. I made a call, some people disagree, life will go on, don't get hung up about it.--Obi-Wan Kenobi (talk) 21:12, 19 June 2013 (UTC)[reply]
- I think the point here is that non-admin closes require CLEAR consensus. It should be quite obvious from the discussion there, and the discussion here, that it was anything but clear. When you have to provide this sort of voluminous explanation to even attempt justification, then that is surely an indication that consensus was not CLEAR. You have found what you feel to be consensus, but you essentially took a position on this subject. Your first instinct, a no-consensus close, was correct. Omnedon (talk) 20:19, 19 June 2013 (UTC)[reply]
- If you think there was "actually a clear consensus close" there, then you quite frankly lack the ability to determine the outcome of any deletion/move/etc discussion in this project, as that is about as far from the truth as one can get here. Simply disagreeing with ones side does not invalidate their positions, so outside of a raft of "Keep I like it the way it is" votes, you simply cannot ignore the split of the discussion. Evaluating consensus does not mean you pick a side that you agree with and close in that direction. This is falling into a bit of Dunning-Kruger here, the inability to recognize one's mistakes and learn from them. Tarc (talk) 20:24, 19 June 2013 (UTC)[reply]
- I guess we have different definitions. Y'all may disagree, but to me it was indeed clear at the moment I made the decision, and other non-participants have already agreed with my call. In hindsight, some don't agree, so obviously it was less clear to others. The problem is it takes time to eliminate all of the fluff arguments and the emotion and get to the meat, and I doubt most !voting here have taken as much time as I have with this discussion, mapping all the arguments, and comparing them to policies - but once you strip it all away, per WP:AT, the consensus was clear, and as I said before, there was rough consensus on all three major points - common, precise, concise. Many of those opposed were passionately making arguments that had no bearing whatsoever on wikipedia titling policy, so most of those arguments were discounted per WP:CONSENSUS. The oppose side made very FEW policy-based arguments - the main one they did make was COMMONNAME, and that one they lost on very strong evidence, and they even started to concede it at the end. I did *not* pick a side I agreed with, I followed the arguments where they took me, and applied the arguments made with a lens of wikipedia policy. I'm not saying oppose didn't make good, cogent, logical arguments - they DID - but the supporters were just much more focused on policy-based arguments - and my understanding of consensus is that policy-based-arg will beat a logic-based arg any day, unless you IAR. If it had been policy vs policy, this would have closed no-consensus, easily, or then you get into guidance and officialname and other ancillary arguments. But that wasn't the argument presented. HC beat HRC 3-to-zero on titling policy.--Obi-Wan Kenobi (talk) 20:44, 19 June 2013 (UTC)[reply]
- Yes, a few non-participants have agreed with your call; but very few, compared to those who disagree with what you did, both from the pro and con side of the discussion. You inaccurately characterize the result as 3 to 0 in terms of policy-based arguments, as if there were none whatsoever on the con side. That's simply not true. WP:AT was used by both sides; there is a lot of text in that policy. You refer to three different sections of the same policy; both sides used various aspects of that policy to support their arguments. One editor in particular, B2C (the proposer) is known for flooding discussions with large amounts of text and claiming that arguments have not been addressed or refuted when they have. This is becoming similar: large amounts of text claiming that no policy-based arguments were made, when they were. Omnedon (talk) 21:56, 19 June 2013 (UTC)[reply]
- Let's not judge the score here until it's done, okay? What I meant by the shorthand 3-0 is that in my judgement, HC surpassed HRC on the 3 key policies that were discussed again and again by BOTH sides. No significant other details of WP:AT were used by any of the oppose editors as far as I recall. So, again, I'm not claiming the other side didn't make policy-based arguments, I'm saying that in the determination of consensus (which means applying arguments to policy), their arguments did not hold up to snuff - they were simply weaker, and less based on what is actually written in WP:AT and more based on extensions to it. I've just looked it over again - can you find for me the three strongest, policy-based arguments from that discussion, that aren't about COMMONNAME? Even if you call a tie of COMMONNAME, the other two policies sway it towards HC. I feel like you won't be convinced unless I map every single oppose argument against the policy it invokes or references, and then compare that to the supports. The result wouldn't be pretty.--Obi-Wan Kenobi (talk) 04:16, 20 June 2013 (UTC)[reply]
- Obiwankenobi: Delving into the arguments you feel are stronger or weaker is fine – as a participant. This is the kind of thing that the many commentators did at length in the discussion. However, for you as a closer to impose in what was throughout a very divided discussion your opinions that "I think x argument is weak", "I dismissed y", "I favor z", etc. is not IMHO appropriate, and is essentially a supervote... and that is what's "not pretty". To be clear, I don't suggest that closers have an easy job, nor do I suggest that they should not examine discussions: for instance, if this was a situation where a couple of people simply kept shouting "I just don't like it", then that would be one thing. But, as many editors have pointed out and you yourself admit, it's clear that this is not such a case. Many reasonable points were raised on both sides by many participants, with no consensus being reached – and in such a situation it's not the job of a closer to "pick a winner".
- That said, I totally get that you don't agree with all of this: you personally favor some arguments as stronger and dismiss others as weaker, and seemingly consider that discrepancy which you see to constitute consensus. But please understand that while that's your opinion, that's a very different thing from the actual result of the discussion. As a closer in such a situation, you simply cannot cast a supervote on what arguments you personally feel are best; instead, if after reasonable debate the participants cannot agree on clear support for the move, then it's not moved, per WP:NOCONSENSUS. ╠╣uw [talk] 13:48, 20 June 2013 (UTC)[reply]
- I understand where you're coming from too, and in my shorthand and numerous replies I haven't always spelled out in full detail what I mean by things like "this argument is weaker". However, let me again point you to WP:CONSENSUS, which explicitly uses the word "quality of arguments". The closing instructions explicitly use the words judgement/judge several times. Thus, in my understanding, closers do have leeway to judge the quality of arguments, and their applicability to policy, and that's what I did. Finally, I am not saying both sides didn't have strong, logical arguments, they did. But if we break it down simply, we could tally thus:
- Policy-based arguments:
- WP:COMMONNAME: (much debate from both sides, but slight edge given to support due to evidence provided, and concession by several oppose voters)
- WP:PRECISE: (hammered by support, slight resistance from oppose but I discarded that as not being based on policy as written, or invoking WP:OSE)
- WP:CRITERIA (concise): (much argument by support, slight resistance from oppose, but I discarded that as not being based on policy as written, rather based on extended interpretation of what the word concise means)
- WP:TITLECHANGES: Only brought up by one oppose !voter, and contested by support. Reading it, I don't see that TITLECHANGES means you cant' change the title if there are "good" reasons. Support explicitly brought "good reasons" to the table, arguing for a change in usage over time.
- Non-policy-based arguments:
- WP:OSE: (as exception to WP:PRECISION) This was widely rejected by support, and only a few oppose argued using this
- WP:OFFICIALNAME: This one was no-contest, oppose clearly owns this.
- That's obviously not the complete tally of all arguments, several others were made, but the basic point is, when you tally the policy-based vs non-policy based arguments, support made stronger policy-based arguments and brought evidence to boot, and the opposition was discarded in my judgement as not understanding the policy as written.--Obi-Wan Kenobi (talk) 15:21, 20 June 2013 (UTC)[reply]
- This is becoming a redux of the whole RM discussion that we've just had, and I'm not sure it's appropriate to spam this forum (any more than it already has been). If you or anyone else is interested in reading on, discussion continues here. ╠╣uw [talk] 01:32, 21 June 2013 (UTC)[reply]
- "...when one side has policy on their side, and the other is making WP:OSE arguments..."
- "...a policy-based arg will beat a logic-based arg any day..."
- "...if it had been policy vs. policy, this would have closed no-consensus..."
- "...HC beat HRC 3-to-zero on titling policy..."
- At first, and throughout your earlier comments, you were mainly claiming that the pro side was mostly using policy and the con side was mostly not, using what you called "soft issues" and "logic-based args". Now you say that it was about the "3 key policies that were discussed again and again by BOTH sides", but that one side was stronger than the other. So it comes down to your own personal interpretation of policy, in which case (as has been stated before) you should have participated in the discussion once you decided it wasn't a no-consensus close after all, rather than closing. This makes your close a supervote. Omnedon (talk) 12:28, 20 June 2013 (UTC)[reply]
- Hi Omnedon. I appreciate your position, and I stand by my statements, that the pro side WAS mostly using policy, and the con side WAS mostly using "soft" issues, such as "official name", WP:OSE (as an exception to WP:PRECISION), etc. Both sides did address and discuss COMMONNAME extensively, and as I mentioned now many many times, the evidence for COMMONNAME given by searches of news sources, ngrams, book titles, and others, was convincing, but it wasn't convincing enough to completely sway the argument. In other words, I granted that COMMONNAME may hold for HC, but it was a close call, and I would not have found consensus to move based solely on that. instead, it was the other two - which were hammered by the pro side, and mentioned by a few of the con side (thus, allowing me as closer to apply those policies, per WP:CONSENSUS). I weighed the arguments, and it wasn't a personal interpretation of policy, it was a judgement call, which all closers must make. Otherwise, you would have arguments like the following:
- side A: "title A is better because of WP:COMMONNAME, because here are 54 sources that demonstrate this."
- side B: "title B is better because of WP:COMMONNAME, because I found this one website that says this"
- Closer: Well, both sides invoked COMMONNAME, and I can't interpret that policy, therefore, it's a no-consensus.
- I've studied a lot of closes over the years, and if you read WP:CONSENSUS, it states "Consensus is determined by the quality of the arguments given on the various sides of an issue, as viewed through the lens of Wikipedia policy." That to me clearly implies the closer is allowed to judge the quality of the arguments. Then on Wikipedia:Closing_discussions, it says "Please also note that closing admins are expected and required to exercise their judgment to ensure the decision complies with the spirit of Wikipedia policy and with the project goal.", and then "He (or she) is not expected to decide the issue, just to judge the result of the debate, and is expected to know policy sufficiently enough to know what arguments are to be excluded as irrelevant." I have read this stuff again and again, very carefully, both before, during, and after this close. I have outlined my reasons above for rejecting certain arguments made by OPPOSE on WP:PRECISE and Concise, and I don't want to rehash them again. It was a judgement call, which is the very definition of a closing, but I did not decide or add my own views, I simply weighed the various arguments, downgraded those not based on policy, and this is the result.--Obi-Wan Kenobi (talk) 13:34, 20 June 2013 (UTC)[reply]
- FWIW, I have now studied the earlier four move discussions. I didn't read them before, as I didn't want them to influence my close, which should be based on the arguments presented. One thing which amazed me is that
- discussion 1 was closed as no-consensus-to-move, but I would have closed as STRONG KEEP - so we need to get our language straight. There was clear consensus there to keep. #2 was also a pretty clear keep.
- In all of the previous discussions, COMMONNAME rarely shows up, only in the last two, but used weakly.
- WP:PRECISE and WP:CRITERIA are never invoked until this most recent discussion, or if they are, they aren't referenced/debated/discussed. Which is surprising to me.
- On balance, the "move" supporters strengthened their arguments over time, while the "oppose" voters maintained more or less the same stance. It worked for a while, but eventually the 3-sections-of-the-titling-policy argument won out (IMHO). --Obi-Wan Kenobi (talk) 21:53, 19 June 2013 (UTC)[reply]
- Fascinating. Would you care to offer a 2nd opinion on the Lincoln-Douglas debates, the Scopes monkey trial, and Roe v. Wade while you're at it? Reaching into the past and offering one's own spin on long-closed discussions may be an interesting academic exercise, but it has no application at all to the matter at hand. Tarc (talk) 22:55, 19 June 2013 (UTC)[reply]
- The point being, much meal was made of the fact that this has already closed 4 times as NC. I was simply pointing out that the arguments mounted by "support" in the past 4 moves were rather weak, compared to this last one. And I was pointing out that two key policy-based arguments were not mooted until this time around.--Obi-Wan Kenobi (talk) 04:16, 20 June 2013 (UTC)[reply]
- @Anthonyhcole, re IAR. None of the participants explicitly (or even implicitly, IMO) invoked IAR. Instead, the arguments you outlined above were couched by both sides in terms of WP:OFFICIALNAME, which is not a policy, and this was widely discussed by both sides and I deeply considered the "official name" argument, and gave the oppose side credit for this particular argument. If it had come down to a split on policy issues, the official name would have swayed in the oppose direction. But the discussion didn't go that way, and as mentioned many times, two other policy-based considerations, namely WP:PRECISE and WP:CRITERIA, swayed the other direction.--Obi-Wan Kenobi (talk) 13:24, 20 June 2013 (UTC)[reply]
- I didn't say they "invoked IAR", whatever that means, and I'm fairly sure there's no rule anywhere saying you have to spell it out. You simply do it when appropriate. You're saying that the subject's express preference and the use in most (all?) official situations may be disregarded because we don't have a rule that says we can take those into account.
- Are you assuming that IAR isn't really a policy, or that our present title policy is so perfect and all-embracing that there are no circumstances under which "non-policy" arguments may have value? --Anthonyhcole (talk · contribs · email) 14:01, 20 June 2013 (UTC)[reply]
- Closers aren't allowed to bring in policies that aren't invoked in the discussion. That is explicit in the guidance for closing discussions. That *would* definitely be a supervote. I'm also not saying that the officialname arguments aren't strong - they are, and I gave them credit as mentioned. However, they are not policy, so when you have adherance to one title based on three parts of WP:AT, and the strongest argument from the oppose side is based on something that isn't policy, policy wins (IMHO). But that's also what WP:CONSENSUS says.--Obi-Wan Kenobi (talk) 14:04, 20 June 2013 (UTC)[reply]
- Ah. I missed the bit about closers being unable to take account of policies that aren't expressly invoked in the discussion. Can you point me to it, please? It was my understanding that closers determine consensus by evaluating the arguments, assigning due weight accordingly, while giving due consideration to all the relevant policies, guidelines and naming conventions.--Anthonyhcole (talk · contribs · email) 14:23, 20 June 2013 (UTC)[reply]
- Perhaps I worded that too strongly. The language I was referring to is this: "If the discussion shows that some people think one policy is controlling, and some another, the decider is expected to close by judging which view has the predominant number of responsible Wikipedians supporting it, not select himself which is the better policy" from Wikipedia:Closing_discussions. Since IAR wasn't invoked, I think it would have been improper for me to invoke it in deciding this close, since none of the wikipedians referred to it (they referred instead to an existing guideline around officialname, thus they were not really proposing to IAR, they were saying "use this rule instead of that one".) Also, I think yes, a closer should be aware of all relevant policies, but it would be extremely improper for a closer to bring up a naming guideline that wasn't mentioned, for example, or even invoke some part of WP:AT that participants didn't address. In other words, the way I read it is, you judge based on the policies used by participants - and you don't bring in new policies not mentioned by them, except perhaps in extreme conditions. I noted below that I read the past closes on this issue, but the arguments in all past closes were much weaker, so I never would have closed any of them as move - to do so would have required bringing in policies not mentioned by any of the discussants. This close was based only on arguments presented.--Obi-Wan Kenobi (talk) 14:55, 20 June 2013 (UTC)[reply]
- "This close was based only on arguments presented." No it wasn't. You disregarded the subject's on-the-record preference for HRC, and the fact that HRC is used in most (all?) official situations because WP:AT says nothing about those cases. You're acting as if WP:AT is complete, and there are no circumstances where factors not (yet) addressed in that policy can override the rules as they stand. There was no clear consensus. You had no grounds to ignore the very reasonable arguments of the oppose voters, just because they were (knowingly - they're all familiar with that policy) ignoring the existing rules in favor of respect for our subject. They were valid arguments, the proponents, all responsible Wikipedians, knew they were non-policy arguments, and you should have included them in your assessment of consensus. --Anthonyhcole (talk · contribs · email) 15:20, 20 June 2013 (UTC)[reply]
- Wrong. WP:AT does discuss it, right here: "Wikipedia does not necessarily use the subject's "official" name as an article title; it prefers to use the name that is most frequently used to refer to the subject in English-language reliable sources." Therefore, our policy is explicit about preferring common usage vs subject preference. I gave a slight edge to COMMONNAME for HC, based on evidence provided and number of participants invoking COMMONNAME as Hillary Clinton (even including some from OPPOSE that basically conceded it), but I would not have closed based on that alone. For example, if the two choices were Hillary Clinton and Hillary Rodham, both being equally "as precise as they need to be" and concise, with COMMONNAME an edge for HC, and strong support for Hillary Rodham as the WP:OFFICIALNAME and the name she prefers, then I would have closed in the other direction. But concise and precise are called out separately in WP:AT, and we shouldn't go outside of WP:AT to non-policy essays if we have a clear winner, argued by the participants, using only WP:AT. That's what WP:CONSENSUS means, when they say: "Consensus is determined by the quality of the arguments given on the various sides of an issue, as viewed through the lens of Wikipedia policy." --Obi-Wan Kenobi (talk) 15:40, 20 June 2013 (UTC)[reply]
- Thanks. I'd forgotten that. (It used to say, "When there are several names for a subject, all of them fairly common, and the most common has problems, it is perfectly reasonable to choose one of the others" until it was deleted recently.) Anyway, that doesn't address the subject's preference. You can include consideration of the subject's preference withinin the scope of that lens. It is within policy to take into account factors that are not (yet) addressed in policy. Our arguments are allowed to be premised on overlooking a rule, like concision or common name, in favour of a principle that is not addressed in policy, like the subject's declared preferred name.
- NB a small interjection: "all of them fairly common" was not deleted it was moved to a new paragraph and is still in the AT policy. -- PBS (talk) 10:22, 22 June 2013 (UTC)[reply]
- Consider this, what if the RM discussion had unanimously agreed that, because the subject has stated 20 years ago that she prefers to be called HRC, we would ignore the trivial difference in concision and Google hits? Should that discussion then be closed in favour of HC or no consensus? If you agree that it should not, if you agree that in such a case, consensus favours the IAR option, then surely you still have to take account of the many opposers who support that position when the discussion is largely divided, and find no consensus in this case. --Anthonyhcole (talk · contribs · email) 16:47, 20 June 2013 (UTC)[reply]
- Hi Anthony. I appreciate your reasoned arguments, and your recognition that I have carefully considered and analyzed this, so thanks for the vote of good faith. That said, it is hard to do what-if scenarios, but let me present you with another clear what-if besides the Hillary Clinton vs Hillary Rodham idea I provided above. Assume we have the same discussion in the RM, but with one addition: in the discussion, several of the oppose !voters say "Yes, we concede that per precision, concise, and commonname, Hillary Clinton probably wins out. However, the result of this is inacceptable, for the following 5 reasons. A, B, C, D, E. A) is because the subject herself has stated in places X, Y, Z that she prefers HRC, and that she does not like to be referred to as HC. Thus, even though OFFICIALNAME is an essay, and "subject's preference" is not written anywhere, we should IAR and keep at HRC, because the result is likely to be better for readers and the encyclopedia." And then, you have the "support" voters begrudgingly saying "Yes, IAR could possibly be applied here, but I still think COMMONNAME and PRECISE apply". So then you have a policy which was brought up by multiple voters and debated, and IAR was explicitly invoked, with reasoning given. Then, I probably would have closed as NC to move. But IAR wasn't invoked, and I still maintain it is improper for a closer to invoke it on his own. Instead of IAR, what I read is "Official name + subject preference" - and weighed that against "concise and precise". Concise and precise won out, as they are policy, and the others aren't.--Obi-Wan Kenobi (talk) 17:24, 20 June 2013 (UTC)[reply]
- Why do the opposers have to "invoke" IAR? Can't you just recognise that by arguing for the importance of the BLP subject's preference (when they all know it's not addressed in WP:AT) they are making an IAR argument? Where does this rule that they have to use the words IAR come from? The relevant policy simply says you, the closer, determine consensus by evaluating the arguments, assigning due weight accordingly, while giving due consideration to the relevant policies, guidelines and naming conventions. There is no consensus (agreement), not even rough consensus, in that RM discussion, and you confected a consensus by ignoring all of the opposers on invalid grounds. --Anthonyhcole (talk · contribs · email) 04:39, 21 June 2013 (UTC)[reply]
- I'm usually at loggerheads with Anthony on a variety of issues, but he's nailing it on the head here. This was a bad close by an editor wholly unsuited to reading the consensus of the discussion. You cannot declare a "winner" in a discussion so evenly split, unless there are some making clear arguments to avoid. This is why focusing on the non-admin close aspect is critical, despite the subjects desperate attempts to get people to ignore it. I have a smidgen of faith left in our admin corps that one of them would have known how to properly deal with an evenly-split discussion, and not have so blatantly supervoted to close on personal preference. Tarc (talk) 16:03, 20 June 2013 (UTC)[reply]
- I agree that Obiwankenobi's strident arguing for Sarah Brown (wife of Gordon Brown), an issue with significant feminist elements, and then coming here to close another highly-contested naming issue with significant feminist elements, both centering on the wife of a former national leader, was probably ill-advised. But I'm very impressed by the breadth and detail of his analysis. And he's not the first closer I've encountered who has disregarded a strongly- and widely-supported "policy free" argument in a discussion. It's a common error. --Anthonyhcole (talk · contribs · email) 17:01, 20 June 2013 (UTC)[reply]
- One can be just as wrong in 1,000 words and one can be in 10, I'm not impressed with the quantity of an argument; a person simply cannot be allowed to fabricate consensus where none exists. I think this will be the last I have to say on this topic, I just hope the right thing (a reversal) is done in the end. It'll be a Quorty-esque travesty if not. Tarc (talk) 17:22, 20 June 2013 (UTC)[reply]
- That is an excellent comparison Tarc. Or, actually, it's not.--Obi-Wan Kenobi (talk) 17:25, 20 June 2013 (UTC)[reply]
- Do you have any comment on my criticism above regarding the appropriateness of you closing this RM discussion while you're deeply involved, arguing stridently against the apparent consensus, at Sarah Brown (wife of Gordon Brown). Aside from the obvious striking similarities of the BLP subjects, there's a similarity in the arguments, too. At the Brown discussion, you're arguing meticulously on the basis of policy against experienced editors in good standing whose main thrust is really not covered in our very clunky and limited rule set. Do you think, on reflection, that you're the right person to be closing this Clinton discussion, and ignoring those who argue for principles not (yet) addressed in that incomplete and imperfect rule set? --Anthonyhcole (talk · contribs · email) 04:39, 21 June 2013 (UTC)[reply]
- I'm being beat up for responding too much here, so I'm going to stop unless absolutely required. I responded on your talk page. Short answer - the arguments and hinge-points of these debate are completely different, and the close here could easily be used to go against the arguments I'm making there, namely around CONCISE and PRECISE (as the solution I'm arguing for there is, frankly, neither, or at least, there are better options on those counts). Thus, I see no COI. Also, the two subjects are quite dissimilar. We have one who is a sitting secretary of state, candidate for president, while the other is almost entirely known for being spouse of a PM. Night and day in terms of reasons-for-notability in my opinion.--Obi-Wan Kenobi (talk) 13:34, 21 June 2013 (UTC)[reply]
- Just a small correction - Clinton is not the sitting secretary of state; she resigned effective February 1, 2013. John Kerry is her successor. --B2C 19:07, 21 June 2013 (UTC)[reply]
- Comment Above SmokeyJoe said "I note that the NAC closer has abandoned usual admin decorum in letting his close be reviewed as it stands, and accepting the decision of the community. For better or worse, this is one of the skills proven or learned from passing through the baptism of fire known as RfA." I assume he is referring to Obi-Wan's repeated, lengthy arguments here in defense of the close. (By my count, ObiWan has made more than twice as many edits to this thread as anyone else.) I agree with SmokeyJoe that this appears to be contrary to usual practice at MRV, and IMO it demonstrates once again the wisdom of WP:RMNAC in saying that non-admins should close only when the consensus or lack of consensus is clear. --MelanieN (talk) 17:44, 20 June 2013 (UTC)[reply]
- Melanie, I agree. On the one hand, I can appreciate that the closer wishes to defend his decision; but on the other, the responses are both extremely repetitive and extremely extensive. The move should not have been closed in this manner; the resulting furor should have been foreseeable, given the extensiveness of the move discussion and the number of participants. Yet the closer expected the opposite reaction. Many of us have spent a great deal of energy on this, and it didn't have to be this way. It's a no-consensus situation. When the move was originally reverted, it should have been left that way. Yet here we are, and I feel that one reason is inexperience, as well as a tendency to disregard opposing views. Omnedon (talk) 18:51, 20 June 2013 (UTC)[reply]
- We actually have an essay for that; Wikipedia:Don't bludgeon the process. One sees this sort of behavior in AfDs, where the nominator feels compelled to respond to each and every opposition opinion. Tarc (talk) 19:12, 20 June 2013 (UTC)[reply]
- This is off-topic. The purpose of Move Review is to discuss and determine whether the closing editor followed policy and made a proper good-faith decision. His behavior after the fact has no bearing on the merits of the close itself. Perhaps if he were to remain silent in the face of accusations of "supervote" and picking apart every word of his closing, you would be asking, "why hasn't the closer weighed in to defend himself? His silence speaks volumes." He's damned if he does and damned if he doesn't. Questioning his closure (in part) on the basis that he is not a admin is, by definition, not something an admin has to deal with. Therefore criticizing him for not conducting himself with the "usual admin decorum" is a bit unfair. Perhaps the very fact that he is not an admin requires a more vociferous involvement in the discussion.--William Thweatt TalkContribs 20:52, 20 June 2013 (UTC)[reply]
- It isn't off-topic at all, and gets to the heart of why non-admins are instructed to only close discussions where the consensus is CLEAR. Let us review WP:RMNAC;
"If you are not an administrator you should only close certain types of requests; ... Non-admin closes normally require: The consensus or lack of consensus is clear after a full listing period (seven days). ... Many editors do not approve of non-admins closing contentious debates. Non-admins should be cautious when closing discussions where significant contentious debate among participants is unresolved."
- Note that part "The consensus or lack of consensus is clear". What means is just what it says, C-L-E-A-R, as in not a snowball's chance in hell that any other reasonable person would see it differently, that there is no possible way the discussion would end differently. "The consensus or lack of consensus is clear" does NOT mean "it is clear to ME (i.e. the potential non-admin discussion-closer) that the consensus lies in X direction, so I will close it as X". That is what Obiwankenobi did, he took a move discussion where the consensus was not clear, and began to evaluate the opinions of the commenters. Right at that precise point was where the WP:RMNAC violation occurred; as soon as a non-admin begins the evaluation/weighing process, that should be the Klaxon Signal to "Stop", and back out immediately. That this was an improper non-admin close is completely not in doubt here, and any of those who have weighed in with "endorse close", some of them editors who are simply endorsing their initial opinion to move & rename, are really missing the point of why we're here. Tarc (talk) 21:55, 20 June 2013 (UTC)[reply]
- Please don't mischaracterize all of us that !voted endorse. As I noted above, I would have rather an admin close it and actually personally would have slightly preferred HRC ( HC seems to define her too much by her relationship to her husband ) but the policies don't support that. The consensus seemed clear to me when I looked at the RM and Obiwankenobi's reasoning is sound. I do have concerns with the precedents this might sight, and the closer of this MRV should address those points. But can't vote overturn close just because I don't like the outcome, or worry that others might take this as suddenly a reversal of RMNAC. BTW, note the word "normally require" ( including in the bit that you quoted ) before the list of conditions in RMNAC. PaleAqua (talk) 03:54, 21 June 2013 (UTC)[reply]
- Yes, I noticed that word "normallly" too. What exactly was not "normal" about this discussion, such that a non-admin needed to close it even though consensus or lack-of-consensus wasn't obvious? --MelanieN (talk) 05:49, 21 June 2013 (UTC)[reply]
- It implies that there are exceptions. It is mostly to avoid discussions such as this one; a crystal clear SNOW cases it is unlikely to have been so heavily discussed. That said just because the person closing was not an admin does not suddenly make their reasoning incorrect, and to me it seems like they have correctly determined consensus. That puts it into the exceptional case. PaleAqua (talk) 14:57, 21 June 2013 (UTC)[reply]
- Yes we use consensus decision making, but in this case there was not a clear consensus, and at best can be said to have chosen which arguments to consider in determining the outcome, but to call that outcome a consensus is a stretch. Apteva (talk) 16:36, 26 June 2013 (UTC)[reply]
- For comparison, I will point out a recently-closed discussion of something I nominated for deletion, Wikipedia:Miscellany for deletion/Wikipedia:OMGNUDEHUMANBODIES. Roughly 7 deletes, 9 keeps,m and 3 userfy, closed as no consensus. That's what a closer does in that situation, recognize that there is a split and note that people have not come to any sort of agreement on the matter. Tarc (talk) 12:26, 21 June 2013 (UTC)[reply]
- Without looking at the XfD, you are leaving out a step in that. The way you phrase it implies a closer is supposed to go from the straight tally of the votes to the result. ( A straight tally would have been only 36% delete. ) The closer is supposed to consider the arguments, not the number of people or even if the people have come up with a mutual compromise; they are supposed to weigh the arguments made by all parties. PaleAqua (talk) 14:57, 21 June 2013 (UTC)[reply]
- Comment. I know that among other things, supervoting includes the use of reasoning not found in the discussion. Statements like the following seem concerning:
- "Since Obama is shorter than Barack Obama, wouldn't we move him there to be more concise by the same reasoning? I found this argument weak... and I don't think there is lots of evidence that there are RS that *only* refer to Obama as Obama..."
- I don't see that the discussion introduced this claim. (Even if it had been, it doesn't seem accurate, with a preliminary Google search indicating a sizable number of hits.) ╠╣uw [talk] 00:47, 22 June 2013 (UTC)[reply]
- argh. I'm trying to stay out of this, but I'm sorry, this simply isn't true - I did not bring this argument out of nowhere. Your Obama argument was disputed by a participant thusly: "Not even remotely comparable. You can't say that mentions of a surname in isolation are comparable to mentions of the combination of first and surname. The surname in isolation will be used multiple times in any article, while the combined first and surname will only be used, generally, about once (maybe slightly more if counting separate uses for title and captions), whether we are discussing Obama or Clinton." Also, your search is terribly flawed, but I don't wanna get into it, raw google searches are useless, we can talk on your talk page if you want to try to refine that search. It was a minor point, in any case.--Obi-Wan Kenobi (talk) 01:56, 22 June 2013 (UTC)[reply]
- I mentioned its inaccuracy (and included a rough search) merely as an aside; accurate or not, it's not from the discussion. The user you quote says that a surname will be used multiple times after a full name is introduced; you're saying specifically that you don't think sources use only "Obama", something for which no claims or evidence was introduced.
- I don't say this is huge (though you do use it in dismissing an argument); I just felt it might be relevant given the preceding claims/discussions of supervoting. ╠╣uw [talk] 10:08, 22 June 2013 (UTC)[reply]
- im flabbergasted you are pushing the reductio-ad-absurdum argument of "obama" here as applied to concise. If taken to its limit, it would mean move this article, or Bill's, to Clinton. i dont think anyone else took up your view, and support argued vigorously against, using the same argument oppose used for HRC (first usage full name, later usages shortened name). That's what i meant in my close, i was restating the support argument quoted, perhaps my rewording was less than ideal but it was certainly not a super-argument. Naming conventions are clear to avoid mononyms except in special cases, so,i cant see obama as anything more than a red herring.--Obi-Wan Kenobi (talk) 16:47, 22 June 2013 (UTC)[reply]
- Pushing? I'm not pushing anything, just noting an instance where I felt the closure didn't match the discussion: it's just a comment, and I apologize if it "flabbergasted" you. That said, I would ask that you please not mischaracterize my position in the debate: nowhere in the discussion did I advocate "mononyms" as titles. ╠╣uw [talk] 21:43, 22 June 2013 (UTC)[reply]
- I must say, Obiwan, I think this whole thing is going on too long. I'm sure everyone realizes by now that you believe you found consensus. But so many people disagree that I do feel the community is being ignored here. It's just too disruptive to close with consensus where so many disagree that it's even there. In this case, I think Huw's point was that there were elements of your decision that weren't in the discussion. Omnedon (talk) 03:27, 23 June 2013 (UTC)[reply]
- Y'know at this point, I am losing the will to actually care. Obiwan just savaged the closer of the "Sarah Brown, wife of..." discussion because it didn't go his way, just like what happened wit the admin who initially reversed the non-admin close at the Clinton discussion. So, hell, if this move review doesn't go the way that someone likes, we'll just see more of the same til it gets reversed, right? This is this kind of petty bullshit that just seriously makes one reconsider why the fuck one spends time trying to affect change on this project... Tarc (talk) 04:06, 23 June 2013 (UTC)[reply]
- BTW, some interesting comments from Obiwankenobi in his MR seeking to overturn a closure he feels lacked sufficient consensus: "The closer was closing a contentious RM, on a page that had been up for move 5 times in the past, so they should not have been surprised at all that their decision was questioned, nor acted so irritated when people did so in good faith..." Quite so. ╠╣uw [talk] 23:19, 24 June 2013 (UTC)[reply]
On the issue of HC's purported preference for HRC, Obi-Wan Kenobi (talk · contribs) explains:
"Likes to use" [HRC] is quite different from "Please don't call me HC", and again, evidence of HRC's preference presented in the RM was weak on this point - her signs/banners/logos/website/twitter/etc all say HC, and I didn't see any recent letters or communiques from HRC's office that clarified this point. OTOH, we have a precedent, of Ivory Coast and Burma, two whole countries (and thus filled with millions of citizens who might care) where encyclopedias call them Cote d'Ivoire and Myanmar, where the UN calls them this, and where they have written official diplomatic letters clearly asking people to stop calling them the other name, even very recently! And yet still, wikipedia moved them to the more broadly-known, simpler, and more recognizeable names - basically saying, we don't care about the country's preferences, we're following WP:AT. I've stated before I disagreed with both these moves, but on policy, both these moves are correct. The moves had wide participation, were both contested at move review, and yet they stood. So precedent for ignoring a subject's preferences when it conflicts with WP:CRITERIA is well established, and it was (partially) on that basis I made the decision I did.
I think it's an important point, so I've copied it here. --B2C 23:26, 24 June 2013 (UTC)[reply]
- Comments/responses are in the thread (e.g. [5]). ╠╣uw [talk] 09:53, 25 June 2013 (UTC)[reply]
- FYI - I already linked to the source immediately above the quote... the hyperlinked "explains". --B2C 16:34, 26 June 2013 (UTC)[reply]
|