Wikipedia:Move review/Log/2018 May
__TOC__
=[[Wikipedia:Move review/Log/2018 May|2018 May]]=
class="navbox collapsible collapsed" style="text-align: left; border: 0px; margin-top: 0.2em;" |
style="background-color: #E2FFE2; font-weight:normal; text-align:left;" |
|
---|
style="text-align:center;" | The following is an archived debate of the move review of the page above. Please do not modify it. |
style="border: solid 1px silver; padding: 8px; background-color: white;" |
:{{move review links|Kshmr|rm_page={{TALKPAGENAME:Kshmr}}|rm_section=Requested move 21 May 2018}} The closure is unreasonable because the arguments for supporting the move are stronger than the opposes. The support-oppose ratio is 3:5 but there should be more due weight assigned for the support votes that are policy-based than the oppose votes that are based on the MoS which does not explicitly support the spelling of the current title. Overturn or relist. The editor whose username is Z0 18:52, 29 May 2018 (UTC)
::::I think those would be strong arguments at an RM, but I disagree with your assessment of the consensus at the discussion. The consensus there was that the name was Kashmir, and that he was stylizing it without vowels. I also disagree that the supporting arguments in the RM were more persuasive: the points were talking past one another and the COMMONNAME point doesn't address the issue of this not being an acronym but being a stylization of another word. Based on the discussion, I don't see how Primefac could have closed it any other way. Your argument here might be grounds for a new RM in a few months. A relist is a possibility, but I'm not sure an additional week relisting, even with your position above, would change the outcome beyond no consensus, which would end in the same result. TonyBallioni (talk) 21:20, 29 May 2018 (UTC) :::::Well perhaps you're right, but I'm not sure I've actually made any new points in my argument above, most of them were made by those in support, and the "talking past each other" was mainly because those in opposition were engaging in personal attacks and unfounded assertions rather than actually giving policy-based reasons why the points made in support were wrong. If consensus is a battle to see who can shout the loudest and boast the longest record at RM, then sure, there was no other way to close it. But if the arguments made are verified and viewed through a lens of policy, then the supports should have carried the day. — Amakuru (talk) 21:46, 29 May 2018 (UTC) ::::::I think you made it more clearly and actually addressed the points. Consensus is not a shouting match, but when there are valid points being made you need to take them into consideration even if the form they are written in is non-ideal (and I think those in opposition did make valid points, even if you can argue against them) There may have been some behavior that was less than ideal there, but I still think the arguments made on the oppose side had value to the point where even if we were to weight the support ones higher because of policy (which I'm not yet convinced we should have) this would have ended as no consensus and not a relist as most of the issues had been fleshed out. TonyBallioni (talk) 21:56, 29 May 2018 (UTC) :::::::{{ping|TonyBallioni}} what were the good arguments of the oppose side? I barely see any, apart from the appeal to three fringe publications to back up the claim that occasional sources do decapitalise this name. So perhaps you could use those three to make an exception but I just don't think it's enough to counter the well-reasoned and policy-based arguments made in support. The notion that we don't capitalise according to sources per WP:COMMONNAME, and {{u|SMcCandlish}}'s self-written essay at WP:COMMONSTYLE, cited below, which attempts to establish that as a guideline, is quite simply false. eBay, iPhone and SMERSH are good examples of that, and I'm sure I could come up with others. MOS:TM is crystal clear on this matter - we don't make up stylizations that aren't found in sources, and the only argument you could make against that is those three fringe sources do call it Kashmir. But neither you nor the closer have said that the close was no-consensus because of the three fringe sources, instead you're saying the close was crystal clear not-moved. It really wasn't, in my view. Anyway, it does'nt look like this MRV has much legs, so perhaps I will come back in 3-6 months and see if I can make a better case for moving. Thanks again for your reasoned responses. — Amakuru (talk) 13:01, 30 May 2018 (UTC)
|
style="text-align:center;" | The above is an archive of the move review of the page listed in the heading. Please do not modify it. |
class="navbox collapsible collapsed" style="text-align: left; border: 0px; margin-top: 0.2em;" |
style="background-color: #E2FFE2; font-weight:normal; text-align:left;" |
|
---|
style="text-align:center;" | The following is an archived debate of the move review of the page above. Please do not modify it. |
style="border: solid 1px silver; padding: 8px; background-color: white;" |
:{{move review links|Meghan, Duchess of Sussex|rm_page={{TALKPAGENAME:Meghan, Duchess of Sussex}}|rm_section=Requested move 19 May 2018}} {{tmbox |small = {{{small |
|image = Image:Ambox warning orange.svg
|text = Comment for those unfamiliar with move review. This discussion may draw a lot of eyes that have not been to move review before. Please be sure to read the instructions at the top of the page before commenting here. In particular, the instructions state that "Move Review is not an opportunity to rehash, expand upon or first offer your opinion on the proper title of the page in question – move review is not a do-over of the WP:RM discussion but is an opportunity to correct errors in the closing process. Thus, the action specified should be the editor's analysis of whether the close of the discussion was reasonable or unreasonable based on the debate and applicable policy and guidelines. Providing evidence such as page views, ghits, ngrams, challenging sourcing and naming conventions, etc. to defend a specific title choice is not within the purview of a Move Review. Evidence should be limited to demonstrating that the RM closer did or did not follow the spirit and intent of WP:RMCI in closing the Requested Move discussion." This means comments that base support for endorsing or overturning upon whether or not the topic of the article "is still called Meghan Markle" or "is now the Duchess of Sussex" are not appropriate in this section. This discussion is specifically about the close. When commenting, please be sure to identify whether you were involved or uninvolved in the original RM discussion. Dekimasuよ! 16:10, 27 May 2018 (UTC)}}
So, there's a bit of a constitutional crisis now playing out at AN, as a result of an RM closer's extremely unusual close. As background, Jimbo decided to [https://en.wikipedia.org/w/index.php?title=Special:Log&action=view&page=Meghan_Markle&type=move move] this page unilaterally and without discussion, and since this was obviously controversial, an RM was opened for community review. The ensuing RM came up with a near 2/3 supermajority endorsing the move (by my count it was 110-60 in support). Most admins would interpret the discussion as having yielded a relatively strong consensus, IMO, but the closer claimed there was in fact a minority consensus to overturn the move. They then further complicated things by claiming the consensus could not be enacted because Jimbo can't be overruled. Now, people are calling for Jimbo to be desysopped. The debate over Jimbo's role aside, I believe this controversy is fabricated by a blatantly bad reading of consensus in the first place. The close was akin to a supervote and needs to be overturned. No overarching policy justification was provided for throwing out an overwhelming majority view, apart from the closer's vague claim that the minority !voters had 'stronger arguments'. People are discussing how to implement the reading of consensus given the controversial role of Jimbo in all this, but I believe the reading of consensus itself was dead wrong. As an uninvolved admin, I think there's a strong consensus to endorse the move, and the initial reading of a minority consensus here was either incompetent or abusive. Swarm ♠ 00:23, 27 May 2018 (UTC)
:In what way are you uninvolved? You have previously expressed an opinion on how very good Jimbo's move is and on the very consensus for the move: " . . . Perhaps Jimbo still believed in those ideals, and we've greatly let him down. Perhaps it was just an ego-fueled power play. But given the overwhelming community consensus backing it, the move itself was a good one. . . . Swarm ♠ 00:49, 21 May 2018 (UTC)" [https://en.wikipedia.org/w/index.php?title=Wikipedia:Administrators%27_noticeboard&diff=prev&oldid=842215994&diffmode=source] -- Alanscottwalker (talk) 05:08, 27 May 2018 (UTC)
::Yes, that was my assessment of consensus as an uninvolved administrator, hence why I requested this move review. Assessing a consensus as an uninvolved admin does not make one involved. Swarm ♠ 19:42, 27 May 2018 (UTC)
::::You are not neutral you have already expressed a non-neutral claim about a week ago. You explicitly endorsed the move because Jimbo made it, you have said we should defer to Jimbo. You are totally involved. Alanscottwalker (talk) 20:01, 27 May 2018 (UTC)
:::::I actually am neutral that I don't have an opinion on the move, and I am also uninvolved in that I have never become involved or stated an opinion in the requested move itself. You're referring to me opposing a page move ban for Jimbo, which I did not do based on any involvement in the move or requested move itself, but based on a reading of consensus as an uninvolved administrator. Your thinly-veiled attempt to manipulate this discussion by falsely accusing me of being involved and lying about it is even more vapid in integrity and honesty as the reading of a minority consensus itself. Swarm ♠ 20:21, 27 May 2018 (UTC)
::::::No. There is nothing veiled here, nor is there anything to do with your false charges. A week ago, you pronounced Jimbo's move good, making clear your express opinion on the move and committing your opinion to Jimbo's choice of title, and telling others to give him deference. Now, you decided to open this move review by calling Dr. Kay incompetent or abusive just because he has the temerity to find differently, so you'll have to look in the mirror with respect to your false charges. Alanscottwalker (talk) 21:23, 27 May 2018 (UTC)
:::::::That's not WP:INVOLVED, because opening an MR is not an administrative action. It may be non-neutral, but 99.9% of MRs are opened by people with a strong opinion. — SMcCandlish ☏ ¢ 😼 01:09, 30 May 2018 (UTC)
::::::::True, there's no reason for someone to be uninvolved when they open a move review, but I think what Alan was questioning was that Swarm explicitly declared themselves to be uninvolved in the nomination statement. The blurb above says {{tq|"As an uninvolved admin, I think there's a strong consensus to endorse the move"}}, but it seems like they were not just an impartial observer of the discussion, as they had previously expressed strong approval for the move when Jimbo first made it. — Amakuru (talk) 19:33, 2 June 2018 (UTC)
- Endorse
the closethe nom’s contention that there was a consensus in support of the move, the heavily participated discussion shows consensus to not reverse Jimbo’s rename. —SmokeyJoe (talk) 05:20, 27 May 2018 (UTC)
:: Do you mean 'overturn the aspect of the close that said that there was a consensus to reverse the move, and leave the page where it is as a result'; 'endorse the entire close, including the consensus that there was a consensus to reverse the move'; or 'endorse the fact that the closure didn't ultimately reverse the move, and ignore the finding that there was a consensus to reverse the move because it doesn't matter?' I'm not being facetious - Swarm is asking us to overturn the finding that there was a consensus to move, so your endorsement and reason contradict each other, and I can see this MRV getting very confusing very fast if people use "endorse" to mean two contradictory things. --Aquillion (talk) 05:44, 27 May 2018 (UTC)
::: I read the RM and I read a consensus to not move back. That is a de facto consensus in support of the move, although technically different but same outcome. I endorse the status quo and think that nothing should be done. I’d recommend a short moratorium before a fresh RM, if that’s what some want. Give it a few weeks for new sources to show what the future is. —SmokeyJoe (talk) 06:33, 27 May 2018 (UTC). Modified !vote
RelistReclose. Firstly, this discussion has nothing to do Jimbo. Secondly, the closure was silly - the closing admin did not follow through on what he or she judged to be the consensus, presumably out of fear. I note the table at Wikipedia:Move review lists various possibilities for move review and all of them assume that "RM Closers Decision" is identical to "Article Title Action at RM Close" - it is unheard of for an admin to decide that the consensus is for a move and then not move it! So the only sensible way forward is torelistreclose - not because there needs to be further discussion, but so that an admin who has the courage to follow through on his or her convictions can provide some resolution. Personally, I don't think there was a clear consensus, and I initially !voted oppose before striking my !vote. But that's neither here nor there. StAnselm (talk) 05:26, 27 May 2018 (UTC) Edited per following comments which better expressed what I was getting at. StAnselm (talk) 08:59, 27 May 2018 (UTC)- Relist or re-close so someone else can do it, the situation is hopelessly muddled at this point and the best thing to do is to go back to the drawing board to get a clear consensus. If relisted, I suggest that the relisted version be closed by three admins (so nobody can claim it's a supervote) and only by admins who are unambiguously willing to reverse the move if that's what the consensus says. I don't feel that it's particularly likely that Jimbo would pursue any further actions if he were reversed in that fashion (he hasn't indicated he was acting in any sort of official fashion, and AFAIK hasn't objected to the discussion of reversing him if someone finds a consensus to do so), but if so we can cross that bridge when we come to it. Either way the first thing to do is to relist things and get a more clear consensus. --Aquillion (talk) 05:38, 27 May 2018 (UTC)
::Question: And if there is a no consensus move back too? Per Wikipedia:Requested_moves/Closing_instructions#Determining_consensus, "However, sometimes a requested move is filed in response to a recent move from a long existing name that cannot be undone without administrative help. Therefore, if no consensus has been reached, the closer should move the article back to the most recent stable title." and WP:NOCONSENSUS too, "When actions by administrators are contested and the discussion results in no consensus either for the action or for reverting the action, the action is normally reverted.") Alanscottwalker (talk) 05:57, 27 May 2018 (UTC)
:::Obviously a no consensus outcome would lead to it being reversed, yes. Also, I edited my comment to note that a new closure of the existing discussion by a different admin (or group of admins) would probably also be fine. --Aquillion (talk) 06:02, 27 May 2018 (UTC)
::::Thanks. The reason I asked is that some have seemed to argue that it's not obvious that a 'no consensus' would result in moving back to before Jimbo's 'out-of-process' move. But the rules do seem to be that a 'no consensus' close would be moving back to before Jimbo's move. Alanscottwalker (talk) 06:07, 27 May 2018 (UTC)
- Endorse a no consensus and move back to Meghan Markle Like I said on AN, a consensus the other way is tough to call but a no consensus is the clear result. If "Most admins would interpret the discussion as having yielded a relatively strong consensus", then I'm thankful that most of them don't close RM discussions, because my guess is that a most of the regular RM admin closers (with Dekimasu already saying a no consensus) and even lot of the non-admin RM closers, the ones who discount policyfree !votes would close for no consensus. Per WP:RMCI ("However, sometimes a requested move is filed in response to a recent move from a long existing name that cannot be undone without administrative help. Therefore, if no consensus has been reached, the closer should move the article back to the most recent stable title."), and normal procedure at WP:RM, we return to the stable title when there is no consensus.
:I really hope I don't need to explain why WP:OFFICIALNAME !votes can be discounted, or ones that cite British royalty as supreme or whatever. In here, they have no power, and our WP:TITLE policy is supreme.
:Either that or reclose as per Aquillion, but I don't see a need to drag this out for another 7 days with a relist, that is unlikely to generate much more than acrimony. Galobtter (pingó mió) 05:48, 27 May 2018 (UTC) noting I did !vote support for moving to Meghan Markle in the RM discussion. Galobtter (pingó mió) 08:57, 28 May 2018 (UTC)
- Endorse as no consensus, but Overturn to move back to Meghan Markle - Wikipedia is a "rule of law" community - our guidelines tell us how to approach this and the closer hasn't completed the task (and I don't blame them) of following through with the WP:RMCI. A no-consensus decision defaults to returning the article to the last stable title. I wish our rule was to just do that before a RM proceeds, so as to make a move discussion less muddied with objections to the out-of-process move. I don't see a need to relist. If this review results in it being moved back to Meghan Markle, and a superuser moves it back again, then at least we've held true to our guidelines. -- Netoholic @ 06:16, 27 May 2018 (UTC)
- Re-close or re-list. Let's be clear that a Jimbo move is not irreversible, unless Jimbo has specifically said so (as he might do with an 'office' action). It's quite nice sometimes to have someone who can cut out the crap, but he won't claim to be infallible. In his comments in the move discussion, where he explained his reasons for the move, he clearly spelled out that it would be for others to decide. This alone makes it a bad close. It also doesn't make it easy for anyone else to move the article. If a non-admin had legitimately reached the same conclusion about the consensus, but left out the stuff about Jimbo, I don't think many admins would hesitate to move the article whence it came (even if it caused another discussion). Obviously I don't recommend a non-admin closure. Either the closing admin needs to move the article, or another closure is needed. It's not good enough to say it needs to be moved and that we can't move it. This is not a recognised outcome. Like Swarm I'd also question whether the closer feels a bit conflicted about the closure, so if they're not going to move it then let's just see if someone else comes to the same conclusion. But please leave out the stuff about Jimbo this time because it's not an issue. (I'm un-involved) -- zzuuzz (talk) 06:23, 27 May 2018 (UTC)
- Re-Close/Endorse/Implement the close/Whatever means return to status quo ante and figure it out after the dust from the needless charlie-foxtrot caused by Jimbo wanting to "have fun". The closer did not follow policy in that they determined what the outcome should be yet did not implement the consensus they found so endorse does not really work but I think they made a reasonable finding based on policy. (See my comment below [http://en.wikipedia.org/w/index.php?title=Wikipedia:Move_review/Log/2018_May&diff=843189823&oldid=843189483]). Pretty much any proper outcome here would require moving the article back to its original title. A no consensus re-close would mean returning to the original title as would implementing the close made. The question is whether an immediate fresh RM should be started or whether this closes finding of consensus for COMMONNAME should stand and the issue only be revisited after several months. I do not think any reasonable reading of the policy backed arguments in the original RM can justify a finding of consensus to move. {{pb}} {{ping|Jimbo Wales}} this disruption right here is why you must follow Wikipedia's policies and procedures just like everyone else. We can not take your founder bit but the community can and at sometime will take your admin bit if you abuse it like this again. It would be best all around if you simply resign your bit for your personal account and have a 'Jimbo Wales (WMF)' account with admin and other advanced permissions which you can use for official/office/'it shall be so because I say so' edits. This will remove the ambiguity of authority and intention which led to this, entirely avoidable, drama. It would also be seen as an act of good faith by the segments of the community which feel, based on action like this, you are somehow more equal than everyone else. Please consider this. Jbh Talk 06:24, 27 May 2018 (UTC) Last edited: 17:38, 27 May 2018 (UTC)
- Endorse as no consensus and move back to Meghan Markle or re-close as per Galobtter. This is a GF and necessary Move Review by Swarm. Nonetheless, I believe DrKay was correct in finding a consensus, though I would suggest it was right on the edge between consensus/no consensus and, out of a preponderance of caution, a no consensus endorsement should be made. While there was a strong majority in favor of maintaining the move, I believe DrKay made a reasonable evaluation on the strength of argument. There was a plethora of well-intentioned !votes to maintain the move, however, a seemingly large portion were from accounts less than 30 days old, IP editors, or SPAs. Obviously, these types of accounts should be welcome, however, a closer inspection of the rationale offered by drive-thru accounts see a great number of WP:VAGUEWAVEs, WP:CRYSTALBALL arguments, or - in a number of novel cases - arguments apparently based on Windsor House Law, rather than arguments based on WP policy. I quote a small selection here:
::*{{xt|... we should do her the honour of using her new title ...}}
::*{{xt|The Duchess has risen above the ranks of the plethora of female actresses.}}
::*{{Xt|...any arguments about WP policy and even user consensus, frankly, are irrelevant when faced with such historic officialdom. Basically, the Queen's vote wins.}}
::*{{xt|... change Wikipedia:COMMONNAME to include an exception for British royalty.}}
:Can we legitimately consider declarations of these types to be equal in value to policy-based reasons for reversal? (On the secondary question of founder omnipotence raised via the close, I take no position.)
:Chetsford (talk) 06:28, 27 May 2018 (UTC)
EndorseRe-close as no consensus and move back to Meghan Markle – In their reading of the discussion, the closer accurately noted that policy arguments favored the apparent common name "Meghan Markle" but that a large number of editors also approved of Jimbo's out-of-process move. Had I evaluated the same discussion, I would have concluded "no consensus" and advised to wait a few months until we can determine whether the common name has been changed by real-world usage. See for reference the discussions about Dnipro when the city's name was officially changed from "Dnepropetrovsk" but the English Wikipedia flip-flopped[https://en.wikipedia.org/w/index.php?title=Dnipro&diff=730125540&oldid=730122802&diffmode=source] and eventually tooka few monthsa full year to settle on the new name.[https://en.wikipedia.org/w/index.php?title=Dnipro&diff=792083781&oldid=791349664&diffmode=source] When faced with no consensus in a contested move, the usual process is to revert to the longstanding article title, without prejudice to a future move request for the new title. The fact that Jimbo is "having fun" by expressing personal deference to British royalty is totally irrelevant. Hence the article must be moved back to Meghan Markle, and an RM moratorium of 6 months should be advised. — JFG talk 08:00, 27 May 2018 (UTC) Full disclosure: I have been totally uninvolved in prior discussions.- Comment The above statements already give clear demonstration of one of the reasons why we don't just deal in counting-up bolded ivotes, as Swarm argues for - you have to read them and the discussion. Multiple comments in the discussion on both sides actually did come to a clear consensus that Jimbo's move was out of process (something that is difficult to argue against, given the move protection Jimbo edited through). I did not ivote in the underlying discussion, although I did comment, but the 'Jimbo's move' side was basically devoid of any reference to reliable sources and the ones they did cite did not support Jimbo's move, Jimbo cited google trends which could only tell that "Meghan Markle" became famous as "Meghan Markle", and then became more famous as "Meghan Markle" - The other source was the royal website, which was somehow argued, "Meghan, Duchess of Sussex" is her official name, even though it never uses that formulation -- even putting aside that there was controversy that, that could never be her name because it's a divorced or widow's style, we don't care about official name. Nor as already noted, do we predict the future -- as a tertiary source, we are not even suppose to be even a smidge ahead of sources Alanscottwalker (talk) 12:12, 27 May 2018 (UTC)
- Endorse a no consensus and move back to Meghan Markle because policy-based !votes do get precedence over the fluff cited by Chetsford. Looking back over the discussion, very few of the !votes in favor of Jimbo's move are based on actual policy. Lepricavark (talk) 12:48, 27 May 2018 (UTC)
- Keep at Meghan, Duchess of Sussex - 2/3 of editors at the Rfc, have endorsed Jimbo's moving the article. GoodDay (talk) 13:13, 27 May 2018 (UTC)
- Yet Wikipedia is not a democracy, and "most decisions on Wikipedia are made on the basis of consensus, not on vote-counting or majority rule". Arguments matter, not numbers, and a large number of voters there were tagged by Dekimasu as single-purpose accounts (with sock-puppets as cherries on the top). Surtsicna (talk) 13:28, 27 May 2018 (UTC)
:::I don't understand the opposition at Harry's & Meghan's articles. Would look quite odd - having Prince William, Duke of Cambridge & Catherine, Duchess of Cambridge, yet Prince Harry & Meghan Markle. GoodDay (talk) 14:45, 27 May 2018 (UTC)
::::GoodDay, your pleas for consistency are awfully inconsistent. Let me remind you, once again, that you supported having Felipe VI of Spain and Queen Letizia of Spain, despite that looking much weirder than one couple differing from another. Surtsicna (talk) 14:51, 27 May 2018 (UTC)
:::::I've no resistance, to changing the king's article to King Philip VI of Spain. GoodDay (talk) 14:53, 27 May 2018 (UTC)
::: I find that "single-purpose" tagging unfair -- my vote was tagged as such, though I have made many contributions, but work in a sensitive area and so have a shifting IP. You don't know the situation, you shouldn't assume people come to stir up trouble; in any case, it's still a valid opinion and vote. 2A00:23C5:DE05:B000:B890:8873:8AAB:6ED (talk) 22:16, 27 May 2018 (UTC)
::::To be clear, I tagged both supporters and opposers of the move as SPAs; there is further explanation of this on my user talk page. SPA tagging is not an indication that an opinion will not be taken into consideration. For that matter, DrKay states that no !vote counting took place. Here, it is worth noting that GoodDay is an [https://en.wikipedia.org/w/index.php?title=Talk:Meghan,_Duchess_of_Sussex&diff=prev&oldid=842156949 involved] editor. Since the original comment here calls an RM an RfC here, I'm guessing GoodDay doesn't have a lot of experience with move review and isn't familiar with that convention. Like the SPA tagging, this research is intended to assist the eventual closer. Dekimasuよ! 08:11, 28 May 2018 (UTC)
Step 1 in the move review process is to ask for clarification from the original closer (me). I was made aware of the discussions at AN and here but no-one asked me directly for clarification, and so I decided to keep quiet in the hope that the arguments would resolve themselves. That doesn't seem to be happening, and so I will make a statement here. My close stated that an out-of-process move had been performed by the founder using special rights during a move discussion and while the page was under move-protection but that the move should not be reversed. The opening party of the move review acknowledges that the original move was performed "unilaterally and without discussion" and "was obviously controversial", and agrees with me that the move should not be reversed. So, we are opening a move review to demand the same finding of fact (that it was an out-of-process move) and the same outcome (retain the current name) as decided in the closure but with a different explanation linking the two. That explanation appears to be that many more voters chose the current title than the old one. Well, I'll be quite honest: I didn't count the votes. That didn't seem wise given the number of new accounts and IPs commenting in the discussion. I made a conscious decision to write a more subtle and nuanced close than usual that would be clear in its finding of fact, give the outcome wanted by one side and give comfort to the other side who had strong arguments but would be unsuccessful in practice. I mistakenly thought that it would help to heal rifts if neither side was offered total victory. I was wrong, but I don't think I was wrong to try. I think my one regret is not mentioning Jimbo's argument (that an article title should reflect what a person is known for) in the closing statement. DrKay (talk) 13:43, 27 May 2018 (UTC)
:IMHO, an Rfc should be opened at WP:ROY, to settle once & for all, how to name articles of spouses of royalty. No matter how you cut the butter, it would look odd to have one article Catherine, Duchess of Cambridge & the other article as Meghan Markle. Also, Jimbo is correct about Meghan. She only became more notable, when she got involved with the British royal family. GoodDay (talk) 14:06, 27 May 2018 (UTC)
:{{ec}} Possibly that is what you meant but what you wrote was {{tq|"The best argument is one of common name, and evidence has been provided that the common name at the time of moving was (and for the moment seems to remain) "Meghan Markle". However, even though the logic of the arguments below favors the common name, Meghan Markle, we are faced with the fact that the page was moved by a user with special powers. Any attempt to undo the move by anyone other than the founder is likely to result in more disturbance and potential accusations of wheel-warring."}} This, on plain reading, says the move was out of process; the consensus favored common name (Meghan Markle) and the only reason not to move it back was Jimbo did it. This does not, in my mind, comport with what you said above which is that the discussion has consensus not to reverse it. Are we all misreading the close? Jbh Talk 14:10, 27 May 2018 (UTC)
::Not particularly. There is a dichotomy in my close between justice (the arguments were stronger on one side and the page shouldn't have been moved beforehand) and pragmatism (Jimbo is in practice untouchable and moving the article back would have created a shitstorm). To give you my own opinion on where this discussion will go from where we are now, there are only two possible outcomes:
::(1) the page is moved back. I think this will result in a new requested move either now or in the near future that will present better evidence than the last discussion (because by that time the style "Meghan, Duchess of Sussex" will gain in popularity among reliable sources and it fulfils the requirements of WP:AT) and, I predict, a new request will attract fewer opponents because there will be less anger at the out-of-process unilateral move. Consequently, it is almost certain that the page will be moved to the current title. It's the same endpoint just along a longer and more tortuous road.
::(2) re-opening the discussion so that it can be closed with the same finding of fact and the same outcome but with a different (but still substandard) rationale (that there was a majority for retention). It's the same endpoint just along a different path. It can't be reclosed with a better rationale (such as "because 'Meghan, Duchess of Sussex' is gaining in popularity among reliable sources and it fulfils the requirements of WP:AT") because closers aren't supposed to introduce new evidence not raised or shown in the discussion.
::In neither case will the original article title be retained in the long run and in neither case will there be any action against the founder. DrKay (talk) 15:53, 27 May 2018 (UTC)
:::I disagree with your analysis in only one point {{tq|"Jimbo is in practice untouchable"}}. That 'finding' is far outside of community norms. I do not have a link but it was presented in the ANI thread, but the community expressly removed Jimbo's the administrative privileges of the founder bit and instead granted him an admin bit. This was in response to an out of process act on his part. So, if anything, the precedent is that Jimbo can be held responsible for violating our rules and establishing precedent otherwise in your close by expressly saying he is untouchable was, in my opinion, so wrong that we must demonstrate otherwise here. {{pb}} I appreciate the difficulty of making the close and I understand your desire to find rational compromise. I think. however, in doing so you magnified a single out of process administrative abuse, which could have been addressed by reversal, into a 'constitutional crisis' by de facto endorsing it. Jbh Talk 17:52, 27 May 2018 (UTC)
- Endorse the close, and implement the move back to the stable name "Meghan Markle" as the close found to be the consensus of well-founded policy-based arguments. DES (talk)DESiegel Contribs 14:24, 27 May 2018 (UTC)
- For the record, I commented in the move discussion, and am therefore an involved editor in this matter. DES (talk)DESiegel Contribs 21:44, 27 May 2018 (UTC)
- Endorse as no consensus to move, move back, wait a few weeks, then open an RM. This was moved out of process, and it should have been moved back immediately. WP:RM#CM is clear on this point: we hold RM discussions when "Someone could reasonably disagree with the move." In addition, it was moved through move protection; on 17 May 2018, NeilN added full move protection until 31 May, and at 03:47, 19 May, Zzyzx11 extended that to indefinite ([https://en.wikipedia.org/w/index.php?title=Meghan_Markle&action=unprotect protection log]). Jimbo [https://en.wikipedia.org/w/index.php?title=Meghan,_Duchess_of_Sussex&action=unprotect moved] it through protection a few hours later at 11:15, 19 May; he may have done this without noticing the protection. The best solution would be for {{u|Jimbo Wales|Jimbo}} to revert his move now, and for another RM to be held, preferably in a few weeks' time when news coverage of the name and title has settled down. SarahSV (talk) 15:40, 27 May 2018 (UTC)
- Endorse. (Uninvolved) – the closing statement seemed a bit long; however, had I closed this RM, the result would have been the same. As for Jimmy renaming the article without discussion, I've done that hundreds of times with little objection, and I'm not alone. If he ignored policy, who here hasn't? It appears to me that the RM upheld the page move to its present title. Let us all move on. There's nothing to see here. Painius put'r there 15:45, 27 May 2018 (UTC)
:*You haven't made undiscussed moves through protection after previous title discussion on the talk page. I don't believe you would. Dekimasuよ! 02:23, 28 May 2018 (UTC)
::* I haven't made undiscussed moves through protection, that's true; however, I'm not an admin, so I don't have that user right, and I don't have a crystal ball. If I were an admin, I might very well have renamed the page, because in this instance it was the right thing to do, and it has been soundly supported by the community. The rest is just window dressing. Painius put'r there 09:33, 28 May 2018 (UTC)
- Comment. I note that there is no link from the (talk) page under discussion to this page. I would most likely have looked briefly at the move discussion, found that it had been successfully concluded and the page given its now-correct title, and left it at that. But somehow I noticed a reference to Move Review, and found my way here. Of course the move was correct, as agreed by the majority of those commenting on the original move discussion on the talk page. "Meghan Markle" is now a historic name. This is a case of a woman now-married, who is clearly not going to continue to use her previous name, who is not continuing her previous occupation, and who has for the last week been described in the authoritative media as the Duchess of Sussex. It is of course true that the wedding event is correctly described as the marriage of Prince Harry and Meghan Markle, just as we might once have talked about the wedding of David Beckham and Victoria Adams. But in discussing the woman herself and the role she has now taken on, there should be no conception that we continue to use an out of date name.
:This is not a normal case of a move away from a "stable title". The real-world situation changed a week ago when the marriage (and the creation of the title) occurred. Many of the original comments were of the nature "she is commonly called Meghan Markle" being made so soon after Saturday 19th that no-one could seriously be anticipating how the change would change that "fact". If the title was to be changed to the out of date name now, it would simply have to be moved again based on the obvious fact that she is now known as the Duchess of Sussex.
:As for how to deal with similar circumstances in future, I have seen very many cases where a person, or a company/institution/charity etc, has changed its legal name and the page gets changed within few minutes of that change coming into effect. Perhaps some sort of principle could be adopted that where a change in the name of something "in the real world" occurs, the article name will not be changed for at least 3 days while the impact of the change is considered. In some cases that should be very much longer while the community waits to see if the change is accepted in reliable sources. Sussexonian (talk) 15:58, 27 May 2018 (UTC)
- Pragmatic endorse I will pragmatically endorse the close as is. However, I still utterly condemn Jimbo's out of policy move of the article. I would prefer the article be moved back to its original title and a proper move discussion occur, but I am pragmatic enough to know that nobody is going to dare cross Jimbo and move the article back. Safiel (talk) 19:42, 27 May 2018 (UTC)
::Additional point Wikipedia does not use voting, we use consensus. Just because there were more oppose than support in the original discussion means squat. Most of the oppose comments did not cite policy, while most of the support comments did. So in reality, support carried the day. Safiel (talk) 19:42, 27 May 2018 (UTC)
::Safiel is also [https://en.wikipedia.org/w/index.php?title=Talk:Meghan,_Duchess_of_Sussex&diff=prev&oldid=842957010 involved] in the original discussion. Since I have found that several editors have neglected to note this in their comments here, I'll add a comment on that in the message at the top of the section. Dekimasuよ! 08:17, 28 May 2018 (UTC)
::*Involved user Mea culpa. Safiel (talk) 23:31, 29 May 2018 (UTC)
- It's concerning to me that involved users are coming here, trying to claim there's "no consensus" thus the page should be moved back, when there's a clear consensus in support of the move. Involved users are inherently unable to judge consensus for exactly this reason. This is a shameless and blatant abuse of the process in an attempt to override a clear community consensus. The lack of competence and integrity surrounding the RM's closure and the corrupt attempts to overturn the move in spite of an unusually strong consensus are disgusting. If I knew how dirty this move review would be, I never would have started it. Shame on all of you. Swarm ♠ 19:55, 27 May 2018 (UTC)
- Shame on you for interpreting numerical superiority as consensus rather than addressing arguments. It shows a complete ignorance of the Wikipedia:Consensus policy, which says that "consensus is ascertained by the quality of the arguments ... as viewed through the lens of Wikipedia policy". While I agree that this discussion here should not be hijacked by people involved in the move discussion, it is concerning to me that an administrator gives the same weight to Wikipedia policies such as WP:Article titles and to arguments such as "The Duchess has risen above the ranks of the plethora of female actresses" or "the Queen's vote wins". I cannot help but hope that you are not normally involved in closing discussions. Your comment is very unsettling. Surtsicna (talk) 20:33, 27 May 2018 (UTC)
- And shame on you, Swarm - evidently you do not know how move review works (perhaps you would call your comments abusive or incompetent) -- Dr. Kay read the discussion, fine you don't agree with it because against policy you count votes, but it does not make him your punching bag, because he sees a consensus that Jimbo moved out of process, et al., and that there were much stronger arguments against your stated preferred outcome. Alanscottwalker (talk) 21:32, 27 May 2018 (UTC)
- {{U|Swarm}}, WP:MR where the instructions for this process are laid out, says (in relevant part) {{tqqi|Commenters should identify whether or not they were involved or uninvolved in the RM discussion under review.}} pretty clearly indicating that having involved editors commenting in MRs is expected. DES (talk)DESiegel Contribs 21:42, 27 May 2018 (UTC)
:: {{re|Swarm}} You need to calm down. I don't see anything "dirty" or "abusive of the process" in this move review, just a bunch of editors familiar with move requests (some with hundreds under their belt) who are evaluating the closer's reading of this particular discussion, and recommending further action in good faith. Please trust the process and let it run its course. Had you not opened this move review, somebody else would surely have taken this step anyway, so no regrets necessary, whatever the outcome. {{p}} — JFG talk 23:11, 27 May 2018 (UTC)
:::You're right, I got a bit too worked up here and I'll bow out. Thanks, Swarm ♠ 23:50, 27 May 2018 (UTC)
- Right direction per, in part, to "If we can't have a bit of fun in Wikipedia without a lot of hand wringing, we're going in the wrong direction." - Jimbo Wales in his title move. We are hand wringing. A "bit of fun" every blue moon (or much less) should be fine, as long as it is not so blatant that it will severely wound the encyclopedia. This does not. It wasn't vandalism, or done with an intent to harm. I also read the rest of Wales' statement, and he makes his case well, as the consensus (involved: my RM comment would be one which the closer would have ascertained as frivolous and not counted, but I made it, as I do this comment, with the certain awareness that the title will, after all is said and done, end up reflecting the formal name of the new duchess, bless her heart) appeared at the time, and appears now, to support the "move". As I said in the RM, leave it as is, somebody give Wales' a two-hour ban so he can meditate on the fun he had (either that or take in a good film), which allows Wikipedia to move forward with a sense of justice done, a slap on the wrist, and the title still in the right place, where it is at present. If he does it again desop him so quick that Larry Sanger comes back just because he feels the brisk wind. (full disclosure, I've admitted to my one fun edit too, which luckily has been caught and removed, and a short ban would also be in order) Randy Kryn (talk) 22:31, 27 May 2018 (UTC)
:*That's gotta be worth a WHALE of a trout! Whales sing, don't they? How they sound, Randy 'n Jimmy? {{p}} Painius put'r there 23:33, 27 May 2018 (UTC)
::*That time at band camp I got Jimbo Whaled. Randy Kryn (talk) 02:32, 28 May 2018 (UTC)
:::*Jim told me about that. He also told me about how much he just loathes jokes about his name. So watch yer back. '[[User:Painius|Painius]]' put'r there 09:33, 28 May 2018 (UTC)
:::::*I was referring to your sound whaling as "that time", and this move review as band camp.{{citation needed}} Randy Kryn (talk) 15:12, 28 May 2018 (UTC)
::::*Is this a private gathering, or can anyone cling on? Martinevans123 (talk) 10:37, 28 May 2018 (UTC)
- reclose as no consensus which is the result if the invalid WP:OFFICIALNAME !votes are discounted, and move back to Meghan Merkle. Please get rid of the rubbish about Jimbo using "special rights " in the close; Jimbo just used page mover rights that every admin has. If folks want to have a new move discussion, they will do. Jytdog (talk) 02:30, 28 May 2018 (UTC)
::By "special rights", I mean "the technical ability held by a user by virtue of a flag giving access to specialized functions", i.e. "admin rights" or "the ability to move a page while it is under move-protection". I don't mean "prerogative to override normal processes". DrKay (talk) 07:47, 28 May 2018 (UTC)
:::User:DrKay the part should be gotten rid of, exactly, is {{tq|owever, even though the logic of the arguments below favors the common name, Meghan Markle, we are faced with the fact that the page was moved by a user with special powers. Any attempt to undo the move by anyone other than the founder is likely to result in more disturbance and potential accusations of wheel-warring.}}. This is the part that should be gotten rid of. While I understand your fear (as a human), as a community we don't tremble before the Magical Power of Jimbo. :) Jytdog (talk) 16:36, 28 May 2018 (UTC)
- Endorse DrKay's close and DrKay's well-reasoned comments in this discussion. Randy Kryn, with his usual gentle humor, also put the matter into perspective. Leave the title where it is. What has been done is done. Let us not have to go through another lengthy, contentious and exhausting discussion on the same topic. However, if there is to be another RM, perhaps it can be focused on setting the record straight on another frequently mentioned part of the equation, which is to clarify or determine support for Meghan, Duchess of Sussex → Duchess of Sussex, which already redirects to the current title. Roman Spinner (talk • contribs) 05:46, 28 May 2018 (UTC)
::Please remember that "commenters should identify whether or not they were [https://en.wikipedia.org/w/index.php?title=Talk:Meghan,_Duchess_of_Sussex&diff=prev&oldid=842048538 involved] or uninvolved in the RM discussion under review." There may be others here who haven't done this; I only single out this particular comment because as a regular at WP:RM I expected you'd know to do so. Dekimasuよ! 08:00, 28 May 2018 (UTC)
:::Thank you for the reminder. I am involved, having voted "Oppose" in the RM discussion. Roman Spinner (talk • contribs) 09:09, 28 May 2018 (UTC)
- Endorse the finding that Jimbo made an out of process move; Endorse the findings that the "Meghan Markle" 'side' made the better policy compliant arguments (see my earlier comment, above) and as to other matters there was no consensus (the consistency argument as noted in the close was hotly contested, because of a plethora of different models already existing in our article titles (for royal wives)); Reclose to move back to Meghan Markle, as others have argued. As at least one of the "opposes" in the discussion below basically said, Jimbo's move intentionally or unintentionally created a naming fiat accompli, which potentially effects Wikipedia's integrity. This is due to citogenisis the ability of Wikipedia, regardless of what we mean by title to effect sources (after all, the title as we mean it, should not change even one fact of her life related in the article), but Wikipedia's integrity and tertiary purpose is built on following the body of RS, not leading. In a while's time then editors of the article can revisit title, editors can change minds, and in the meantime focus on making the article better. (For ease of reference, as noted in my comment above, I did not ivote but I did comment in the underlying discussion). -- Alanscottwalker (talk) 09:46, 28 May 2018 (UTC)
- Keep at Meghan, Duchess of Sussex' I am really not sure what the issue is here. Has she suddenly become a different person? As to Mr Wales (no relation!) turning to the dark side, I am not sure he is alone in making such judgments about consensus. Consensus is not a vote, and such value judgement as to who made the best arguments often close such debates. I wonder how many people had even heard of her before this, she was not (as far as I can recall, never having heard of her) even B list.Slatersteven (talk) 09:58, 28 May 2018 (UTC)
- {{ping|Fram}} has now moved the article back to Meghan Markle Galobtter (pingó mió) 10:04, 28 May 2018 (UTC)
- (ec)I have moved the page back to the status-quo situation before this clusterfuck started, per "While the requested move close is under review, any involved editor is free to revert any undiscussed moves of a nominated page without those actions being considered a violation of Wikipedia:No wheel warring." (top of Wikipedia:Move review) and per the closure of the latest move discussion. Moving the page again following the conclusion of this move review or a full page move discussion is of course standard procedure and not wheel-warring, and I have no opinion on what the eventual page title should be. Fram (talk) 10:06, 28 May 2018 (UTC)
- Endorse close (uninvolved user). {{U|DrKay}} has weighed the arguments and correctly determined the strength being with those who object to the move done by {{u|Jimbo Wales}} without prior discussion and who supported a move back to the old title of Meghan Markle. As DrKay has outlined in their well-reasoned closing statement, the numerical majority made the weaker policy-based arguments, with many citing no reason at all or non-reasons like "official name", "legal name", "more appropriate", "cosistency", "respect" and of course "If Jimbo says so!". Those few in support of the new title who cited guidelines (WP:NCROY and WP:CONSISTENT mostly) failed to advance arguments why WP:AT, a policy, should be overwritten in this case, especially considering the precedent mentioned by multiple users supporting the old name that other members of Royal families (including this one, i.e. Sophie Winkleman) have articles named based on their "common" name. As such, I agree that the consensus was in favor of the article's title being Meghan Markle. Regards SoWhy 10:29, 28 May 2018 (UTC)
- Endorse No Consensus, Move back to Meghan Markle - Do not allow the out of process move made through protection "for fun" to stand. Carrite (talk) 11:53, 28 May 2018 (UTC)
- Re-close the existing close is unacceptable. Despite 2-1 numerical support for opposing the move, a "No consensus" close is reasonable, though I'd prefer to see a 3-admin panel find that conclusion. If there is no consensus, the page must be moved back to Meghan Markle, Jimbo notwithstanding. The primary argument appears to be WP:COMMONNAME, and a Google search for "Meghan" gives results primarily using "Meghan Markle", with only a few using the title Duchess. The arguments for consistency are cherry-picked; Grace Kelly and Catherine, Duchess of Cambridge show that there cannot be perfect consistency. As a final note, Wikipedia generally lags behind in moves, and a move's eventual inevitability is not an argument to move the article now; Bangalore and Hirohito being examples of articles I am sure will be at different titles in 100 years. power~enwiki (π, ν) 16:21, 28 May 2018 (UTC)
- Endorse No Consensus, Move back to Meghan Markle — I was not involved in the original discussion. The closer gave a detailed and well-reasoned analysis in which his conclusion was that Meghan Markle, like the similarly previously famous Grace Kelly, is the correct common-name title. The closer's trepidation appeared to be based on a user with special tools (and by "founder," does this mean Jimbo Wales?) who made a unilateral, undiscussed move and whom the closer feared would behave badly if that move were reversed. Fear of someone behaving badly ("Any attempt to undo the move by anyone other than the founder is likely to result in more disturbance and potential accusations of wheel-warring.") is not something on which decisions should be based.--Tenebrae (talk) 20:13, 28 May 2018 (UTC)
- Yes, Jimbo is [https://en.wikipedia.org/w/index.php?title=Special:ListUsers&group=founder the only editor in the founder group] and he moved the article (see [https://en.wikipedia.org/w/index.php?title=Special:Log&page=Meghan%2C+Duchess+of+Sussex logs]). Regards SoWhy 20:22, 28 May 2018 (UTC)
- Overturn the bit about Jimbo, but endorse the move back to Meghan Markle. Determining consensus is not a vote count, and the numerical advantage of "oppose" over "support" should always be viewed through the lens of policy. In this case, the closer correctly rejected votes relying on an WP:OFFICIALNAME type argument, and noted the evidence provided in support votes saying that the WP:COMMONNAME had not apparently changed. As such, a "consensus to move" was legitimate despite the apparent minority vote tally for that option. Some admins might have called it "no consensus" instead, but the outcome is the same either way. Back to Meghan Markle we go. As for the Jimbo argument, I do not believe it to be wheel warring for an admin to reverse the founder's move where consensus/lack of consensus in a discussion has supported that. If Jimbo wants to invoke some special powers to enforce a move to Meghan, Duchess of Sussex, then let him go ahead and do so, and we can deal with the fall out if that happens. But for now, we should just treat Jimbo like any other admin, and undo his actions if community consensus says to do so. — Amakuru (talk) 20:36, 28 May 2018 (UTC)
- Endorse closure as consensus favoring Meghan Markle and overturn to the aforesaid (uninvolved user): Consensus is not counted in votes, it is based on policy. We collect votes because reasonable, experienced editors often disagree on how to interpret and apply policy, and votes help us determine which of those interpretations holds more water with the community. This requires, however, that policy-based reasons be advanced by those voting in that discussion. And that rather conspicuously did not happen. Having the read the entire thread, most arguments were based on an official/legal name type argument, which is not policy-based and so holds no weight: {{tq|Consensus among a limited group of editors, at one place and time, cannot override community consensus on a wider scale.}} The only policy-based argument in favor of the move was consistency. The problem is that there was a consistency argument for both sides, which more or less renders the entire argument moot, as the whole naming schema is not consistent. That leaves us only with the common name argument against it. {{u|DrKay}} noted all of this in her closure and noted correctly. His/her only failure was in not implementing it. —Compassionate727 (T·C) 23:15, 28 May 2018 (UTC)
- Comment This needs to be closed and reopened (or not). The article is still gyrating and is now Meghan Markle. No result here will be legitimate considering the talk page discussion and all the disconnected and disjoint discussion. It's not even clear what this review is endorsing or opposing. — Preceding unsigned comment added by 2600:8800:1300:16E:192C:D49F:EAB:7AEC (talk) 06:21, 29 May 2018 (UTC)
- There was a RM discussion whether to move this article to Meghan Markle (reverting the move made by Jimbo). It was closed in support of such an action but the closer did not implement it. The editor starting this review contended that DrKay misread consensus, so we are reviewing their closing. Regards SoWhy 07:44, 29 May 2018 (UTC)
- :Yes, the closer clearly stated that they saw consensus to move back to the original title. They then went on to say that actually they wouldn't close it that way because of Jimbo. Yet there is nothing in the remit of WP:RMCI which gave DrKay the authority not to implement a close they had already decided upon. The last part of the close was out of process, and has now been overruled by the article going back to Meghan Markle. It's true that this MRV is confused, because there are several different variables at play, and even "endorse" isn't clear because there are two parts of the close (the consensus-finding and the let's-not-do-this-because-of-Jimbo parts). I have seen very few votes here which endorse the second part of that. — Amakuru (talk) 09:27, 29 May 2018 (UTC)
We have Camilla, Duchess of Cornwall , Catherine, Duchess of Cambridge why should Megan duchess of Sussex be treated any differently?Slatersteven (talk) 10:08, 29 May 2018 (UTC)
::{{u|Slatersteven}}, it isn't clear that "Meghan, Duchess of Sussex" is right. She's not "a" Duchess of Sussex; she's "the" Duchess of Sussex, because she's currently married to the Duke. When Diana was married to Charles, she was "The Princess of Wales". When they divorced, the palace issued a press release that she would be styled from then on as "Diana, Princess of Wales" (i.e. "a" Princess of Wales; no longer "the"). I therefore wonder whether we have these styles correct on WP; again, "Catherine, Duchess of Cambridge" is "The Duchess of Cambridge", not "a", etc. SarahSV (talk) 15:51, 29 May 2018 (UTC)
:::Sorry I a not seeing "the" in those page titles (or in the honorific titles either come to that), so I would say that yes we have them correct according to their usage.Slatersteven (talk) 15:59, 29 May 2018 (UTC)
::::{{u|Slatersteven}}, what I mean is this. When Charles and Diana divorced, she became "Diana, Princess of Wales". This signalled that she was no longer THE Princess of Wales. If a Prince of Wales were to divorce and remarry several times, there might be a "Susan, Princess of Wales", a "Jane, Princess of Wales", and a "Helen, Princess of Wales". Each would be "The Princess of Wales" during the marriage. Therefore, by calling current wives "Name, Duchess of ...", I'm not sure we've got it right. SarahSV (talk) 16:41, 29 May 2018 (UTC)
:::::Well it is how they would be styled, not with a the or an "a". It is what they are officially know as, and we do in fact have a precident for what happens when more then one person holds a title [George Villiers, 1st Duke of Buckingham], note no the.Slatersteven (talk) 16:53, 29 May 2018 (UTC)
::::::It seems you and SV are talking past each other, there is no question the style and title for the living and present is "HRH The Duchess of . . ., and yes the former and the dead don't have an 'a' or a 'the', because the dead, et al. are not 'the' and they never could be an 'a', unless there are more than one former living at a time (which has not really happened). Alanscottwalker (talk) 18:22, 29 May 2018 (UTC)
:::::::{{u|Slatersteven}} and {{u|Alanscottwalker}}, when we say "Diana, Princess of Wales", we imply the indefinite article while the person is alive. Question: which Princess of Wales? Answer: Diana. (Note that she was given this style because of her divorce, not her death.) Following this logic, I'm not convinced that "Meghan, Duchess of Sussex" is correct. Is there an authoritative source for that being how she is styled? The big problem with our aristocracy and nobility articles is that we confuse titles with names. We don't title our BLPs "Dr. Susan Smith". We don't call Justin Welby's article "The Most Reverend and Right Honourable Justin Welby". Therefore, why Charles Gerard, 1st Earl of Macclesfield? Okay, maybe sometimes we need to do it for disambig purposes. But otherwise I think we should drop it. SarahSV (talk) 18:43, 29 May 2018 (UTC)
::::::::? The first part does not sound right, she did become HRH [a] 'Princess of Wales' because she was no longer (or, she was the former) HRH The Princess of Wales. Alanscottwalker (talk) 19:03, 29 May 2018 (UTC) strike, per correction, below). Alanscottwalker (talk) 19:34, 29 May 2018 (UTC)
:::::::::{{u|Alanscottwalker|Alan}}, not "HRH Diana, Princess of Wales". She lost the HRH and became the more ordinary (in her view) "Diana, Princess of Wales". That she was a former THE Princess of Wales was signalled by calling her "Diana, Princess of Wales". (And she was reportedly upset about it.) But Meghan Markle is THE Duchess of Sussex, not "Meghan, Duchess of Sussex". SarahSV (talk) 19:23, 29 May 2018 (UTC)
::::::::::Oh, I thought they let her keep HRH (the beasts!) but any rate, the rest of what you say now sounds right. Alanscottwalker (talk) 19:26, 29 May 2018 (UTC)
:I would guess that it all stems from WP:COMMONNAME, so reliable sources must be the telling factor. I've seen her compared with Grace Kelly, who was also an actress and married into royalty as the Princess of Monaco. Is Meghan Markle as famous now as was Grace Kelly when she became royalty? Probably no. So it's most likely true that Markle's royal title will soon rise to the top of our article about her. Did everyone's beloved Jimbo jump the fun-gun? Maybe. What I don't get is why this has drawn such avid attention with some downright non-AGF feelings expressed by some editors toward other editors. Quite the sad commentary. Lot's more important things to be improved here, Wikipedia has so much more to give if editors would only work harder to fulfill its needs and stop buying in to such drama-duchess duping. Too many trollers have weighed in here and in other discussions on this topic. I think we should collectively agree to give the duchess her rightful title! Right this moment! Painius put'r there 10:55, 29 May 2018 (UTC)
::Oh, why so glum? This may prove useful, we now all know the quick move back is the way to go - and let discussion continue on (may even lessen heat) and we can even have a standard edit summary for the move back ('Jimbo fun?', perhaps will get quick self reverts, 'Jimbo fun!') - at any rate, the only 'sad' thing is the beating actual fun on Wikipedia has taken -- every day thousands upon thousands of editors have fun - no moving through protection required (It's 'sad' that someone and then others suggest, that's the way to have a bit of fun? Do they really find the rest of what's done here such drudgery? :) ). Alanscottwalker (talk) 12:55, 29 May 2018 (UTC)
:::{{smallcaps|cheese and crackers}}! You're correct! Again! Ta, off to have some more fun with Jimmy. Painius put'r there 15:12, 29 May 2018 (UTC)
- Endorse both the close and the subsequent move back (involved). We need to draw a line under everything that's gone on so far and start again. It's become confused and messy because the processes aren't being followed, which just goes to show why we have processes. Neither DrKay's close nor the subsequent move of the article back to 'Meghan Markle' prevents there being another requested move (Meghan Markle to Meghan, Duchess of Sussex), which is what should have happened in the first place. If we now go back a step and undo the close it's not going to help matters. It's just going to make things worse because whatever the outcome someone will object. Draw a line under everything so far and re-run the discussion properly. Celia Homeford (talk) 11:58, 29 May 2018 (UTC)
- :I agree with most of what you say, things have become too confused and heated. However, I would recommend not rerunning the discussion immediately, but waiting 3-6 months, as suggested by {{u|JFG}} above. This will give time for the media frenzy following the wedding to settle down, and hopefully for it to become clear what the long-term WP:COMMONNAME for her will be. With enough evidence, (either that everyone still calls her Meghan Markle, or that everyone calls her the Duchess of Sussex), a future move request would likely not even be very contentious. — Amakuru (talk) 12:43, 29 May 2018 (UTC)
:::And that was certainly what happened with the Bradley to Chelsea Manning saga. StAnselm (talk) 18:58, 29 May 2018 (UTC)
::::Exactly, like Dnipro in 2016, I was reminded of the Manning case from 2013 as well. Was ultra-sensitive when first moved, with lots of name-calling on both sides of the argument, then became totally uncontroversial a year later. A good reminder that as an encyclopedia, we shouldn't try to lead sources or respond to emotional arguments. WP:There is no deadline. — JFG talk 13:53, 30 May 2018 (UTC)
- Endorse the close and the move back to Meghan Markle, which is really, really obviously the WP:COMMONNAME, the most WP:RECOGNIZABLE (I had no idea who "Meghan, Duchess of Sussex" until reading this), the more WP:CONCISE, etc. Our title policies and consensus-assessment policy and procedures do not just evaporate because an admin/WMF officer decides to unilaterally WP:SUPERVOTE in a way that scares off most who would reverse it. A review of the discussion shows a) a clear consensus that Jimbo's action was out-of-process, b) solid policy-based arguments which carry weight, and c) a big steaming pile of WP:ILIKEIT with nothing to back it up (and most of it off-topic, about liking Jimbo and supporting him doing what he likes, not focused on the substance of the article title matter). This was perhaps a "brave" close, but it was not an incorrect one. We need more admins who follow policy and procedure like this, even if some people get pissy about or want to wiki-politicize the result. — SMcCandlish ☏ ¢ 😼 01:09, 30 May 2018 (UTC)
- Endorse move to Meghan Markle. The closer correctly found that the policy-based consensus was in favor of "Markle", both for procedural (Jimbo's abuse of sysop powers, moving a move-protected page against then-established consensus rather than filing a move request) and substantive (COMMONNAME) reasons. That consensus should be followed, regardless of an individual user's opinions. A special title does not confer the privilege of violating consensus on any editor, even Jimbo. James (talk/contribs) 16:13, 30 May 2018 (UTC)
- Disclosure: I commented in favor of "Meghan Markle" at the RM. James (talk/contribs) 16:15, 30 May 2018 (UTC)
- Relist Obviously many users still favor the article being titled Meghan, Duchess of Sussex. It seems that some users are using WP:COMMONNAME as the basis of their argument that this article must be moved back to Meghan Markle. I would like to remind everyone that the Duchess of Cambridge, the Duchess of Cornwall, and Diana, Princess of Wales, are all "commonly" known as Kate Middleton, Camilla Parker Bowles and Princess Diana respectively, thus I don't see a reason for making Markle an exception, especially since she'll be known by her "royal" title" for the rest of her life. Even if this discussion gets closed, the issue can be revisited again after several months. Keivan.fTalk 16:50, 31 May 2018 (UTC)
- Such arguments were presented during the move discussion by many users, but were rejected because they did not comply with move policy. In other words, the argument does not hold much weight. Surtsicna (talk) 19:17, 31 May 2018 (UTC)
- :The argument is also factually incorrect. See this article for instance: [http://www.dailymail.co.uk/femail/article-5761397/Royal-fans-criticise-Meghans-dreadful-tights-Twitter.html]. The opening paragraph mentions "Meghan Markle" and the "Duchess of Cambridge". Sure, that's the Daily Mail, so maybe not a full RS, but evidence enough that the two are not treated the same in all sources. — Amakuru (talk) 19:45, 31 May 2018 (UTC)
- My thoughts on this is that the move to “Duchess of Sussex” occurred prematurely. Per WP:Article titles, when a name changes, we should give more weight to sources written after the change... but I am not sure we have enough “sources written after the change” to make that determination yet. So... whether we overturn the move or keep it, I think the entire issue should be revisited in about a year. By then we should have a much clearer picture of what name “sources written after the change” are using. Blueboar (talk) 21:14, 1 June 2018 (UTC)
- Endorse reverting to Meghan Markle - Requested Move discussions are not a vote, so the claimed 2/3 supermajority does not have relevance. Focusing on stronger arguments instead of vote counting is in no way unusual. --Joshua Issac (talk) 22:10, 1 June 2018 (UTC)
|-
| style="text-align:center;" | The above is an archive of the move review of the page listed in the heading. Please do not modify it.
|}
class="navbox collapsible collapsed" style="text-align: left; border: 0px; margin-top: 0.2em;" |
style="background-color: #E2FFE2; font-weight:normal; text-align:left;" |
|
---|
style="text-align:center;" | The following is an archived debate of the move review of the page above. Please do not modify it. |
style="border: solid 1px silver; padding: 8px; background-color: white;" |
:{{move review links|Aloy (Horizon Zero Dawn)|rm_page={{TALKPAGENAME:Aloy (Horizon Zero Dawn)}}|rm_section=Requested move 11 May 2018}} Closed with reason "disambiguate" which is not one of the WP:THREEOUTCOMES. The closer also elaborated on this by providing page view evidence and additional rationale of the sort we'd expect from a participant expressing their viewpoint, not an impartial closer. There is at least enough support for the move of this article to primary for a relisting, especially since on the last day of the RM, one of the related articles was moved out of process and a late concern about mispelling was brought up. -- Netoholic @ 07:27, 19 May 2018 (UTC)
:{{gi|Feel free to open a new RM for Aloy → Aloy (disambiguation) and Aloy (Horizon Zero Dawn) → Aloy, as a defacto relisting of the above, if you want to.}} :Since the closed RM is all muddled, it would be better to follow the closer's advice to open a new RM. Kudes to the closer for a tough call. Paine Ellsworth put'r there 13:45, 20 May 2018 (UTC)
|
style="text-align:center;" | The above is an archive of the move review of the page listed in the heading. Please do not modify it. |
class="navbox collapsible collapsed" style="text-align: left; border: 0px; margin-top: 0.2em;" |
style="background-color: #E2FFE2; font-weight:normal; text-align:left;" |
|
---|
style="text-align:center;" | The following is an archived debate of the move review of the page above. Please do not modify it. |
style="border: solid 1px silver; padding: 8px; background-color: white;" |
:{{move review links|Involuntary celibacy|rm_page=Talk:Incel|rm_section=Requested_move_25_April_2018}} Improper Non-Admin close(WP:NAC) Not only should the requested move not be closed by a non-admin, the move was relisted 5 days before the non-admin closed discussion and moved the page, [https://en.wikipedia.org/w/index.php?title=Talk:Incel&diff=839372052&oldid=839363725 here]. There was definitely not clear consensus to move the page, and the move was controversial. Since the article was previously deleted numerous times before, the last time it was also salted. There is no way the move request should not have been closed by an admin.Dave Dial (talk) 20:57, 8 May 2018 (UTC)
:*Regarding NAC - Having challenged such a non-admin closure of a contentious subject in the past, I learned that, as per WP:RMNAC, "the mere fact that the closer was not an admin is not sufficient reason to reverse a closure". :*Regarding the relisting, WP:RM is clear that "When a relisted discussion reaches a resolution, it may be closed at any time according to the closing instructions;" (i.e. there's no obligation to wait another 7 days). In this case, the discussion which had been active at the time of relisting had died down. It was closed on May 8. There was 1 edit on May 8, 1 edit on May 7, and 0 edits to the discussion on May 6. :*Regarding consensus - as soon as it became clear there was consensus that the article was about the subculture, which is called the "incel"/"incels" subculture, and not a broader subject of people who cannot find romantic/sexual partners, it was obvious [to me at least] that it should be named for that subculture. In other words, it's about a subculture known as "incels" (a portmanteau of "involuntary" and "celibate"); it is not about the broad concept "involuntary celibacy" that some people have formed an "incel" subculture around. If it were the latter, the former title made sense, but as the subculture it seems pretty clear that it should be named after the subculture and not the words the subculture combined to make its name (i.e. reliable source coverage predominantly covers them as insels, regardless of whether they also explain that the name comes from "involuntary celibacy"). The arguments in support seem much stronger along those lines, in addition to there being a decent number more of them. — Rhododendrites talk \\ 21:09, 8 May 2018 (UTC) :::I am probably not going to express an opinion on what to do here (though I don't think this was a great close), but I strongly agree with the second point, and agree to a certain extent with the first one. Discussions should be closed whenever they have reached a resolution, since we're not a bureaucracy. As to the first point, in most cases it should not matter if the closer is an administrator or not. In this particular case I think it is less clear cut, since one of the issues under discussion was the history of salting related titles (i.e. use of tools) by a panel of administrators. Dekimasuよ! 18:46, 9 May 2018 (UTC)
:*{{ping|SmokeyJoe}} Just out of curiosity, since your oppose !vote was {{tq|The current title is clear, recognisable, and scholarly. The proposed is abbreviated slang. The self-identifying “Incel” communities are not individually notable.}}, doesn't that conflict with our article on the subject (using the text from before the move) "a subculture consisting of online communities whose members define themselves as being unable to find a romantic or sexual partner despite desiring one"? There was some talk of including the broader concept "involuntary celibacy" with the article, but the article became, before/without the move, squarely about the subculture. This is in large part because the hybrid article is what was rejected repeatedly in past AfDs, and it was only when coverage of the subculture surged that the topic became notable. Given it's about an online subculture and not a scholarly term, wouldn't it be more accurate to use the name of that subculture as the title, rather than a term that could easily be misunderstood by readers expecting to read about the broader phenomenon? If someone wants to start a separate article about the pathology/psychology/anthropology, they can do that (although given past AfDs, it seems likely to result in a merge), but that doesn't need to affect the naming of this article, no? — Rhododendrites talk \\ 14:12, 9 May 2018 (UTC) ::* Not sure. I have been watching, but not seriously enagaged. The lack of scholarly sources is poor justification for heavy use of mere mention sources. I remained quite unconvinced that any single incel community is notable. It’s all a big mess in my opinion, and I was quite shocked and unimpressed that someone could claim there was a consensus. The AfD history is clear evidence of a history of controversy about this article. I do think incel is both a slang abbreviation and an adjective and unsuitable as a title even just for those two reasons. —SmokeyJoe (talk) 14:26, 9 May 2018 (UTC)
::::Well, evidence for COMMONNAME was provided in the discussion: "(see, showing international heads above for 'incel', also as of this writing 'incel' is used like twice as much in our article - in particular, 'incel' is used throughout the sources section of our article)" and "we choose based on what's most common and ordinary and the topic, all of which points to incel, which the very reliable sources section of this article demonstrates (20 references to incel, 3 references to 'involuntary [something]'" Or perhaps you should say what you mean by evidence? Because what would you count as evidence? And is that a personal standard to you? -- Alanscottwalker (talk) 11:22, 9 May 2018 (UTC) :::::Actual sourcing that demonstrates this. Some supporters did present this, but overall, most provided pretty weak grounds to support, and the opposers also brought sourcing. TonyBallioni (talk) 12:03, 9 May 2018 (UTC) ::::::Those are actual sources, so what do you mean 'actual sources'? Also. the supporters did not bring sources. the best they could do is assert, merely assert, that 'incel' and 'involuntary celibacy' are equally common. Alanscottwalker (talk) 12:55, 9 May 2018 (UTC) ::::When talking about which name to call something, when would the standard not be to start with the sources cited in the article already? Nobody should even be commenting about the common name without looking at those. It's when it comes down to competing subsets of citations and/or sources not in the article that it gets messier. Had I known that someone would assume bad faith that I was making things up, and would not themselves look through the sources already cited, I might've grudgingly copy/pasted just about anything from the article onto the talk page, but that shouldn't be a requirement. — Rhododendrites talk \\ 13:57, 9 May 2018 (UTC) :*This explanation is as clear cut of a Supervote as I could have given. Reading the closer statements it is obvious they are making new arguments that weren't debated in the move request, and they are discounting the WP:COMMONNAME rational from the Oppose voters. Yes, that argument was made by both sides, since EVERY time a source mentions "Incel" it mentions "Involuntary celibacy". This should be overturned and Red Slash should be reprimanded. Dave Dial (talk) 13:49, 9 May 2018 (UTC) :::The explanation may need helping though I'd say that most of the opposes seemed IDONTLIKEIT based on the supposed "unencylopaedicness" of the term incel ("playing with current media interest - wikipedia article titles I thought were encyclopediac not media acronyms", "The proposed is abbreviated slang", even you're rationale of "And we aren't Reddit or 4chan, or even Wiktionary"). Sources use the term most, most introducing it like we do (though of course this isn't the place to relitigate such arguing) Galobtter (pingó mió) 14:02, 9 May 2018 (UTC) :::(e/c) No, the 'just as common' assertion argument was entirely refuted 'incel' occurs much, much more often both as shown by google trends, and in examining the sources, sources overwhelmingly use "incel" in title, and first mention, and while they may mention Involuntary[something], they use incel many, many multiples of times more. -- Alanscottwalker (talk) 14:07, 9 May 2018 (UTC) ::::I'm not going to argue the move request here again, but those claims were refuted. I also copy and pasted my Oppose from a different request started and closed the same day, which was archived and Red Slash didn't even mention. I am disappointed that anyone would think that there was consensus there to move the page, much less "clear consensus". Pointing to headlines without reading the actual sources seems like a poor argument for moving an article. Dave Dial (talk) 14:39, 9 May 2018 (UTC) ::::::No, they were not refuted because, you had no evidence, and "as shown by google trends, and in examining the sources, sources overwhelmingly use "incel" in title, and first mention, and while they may mention Involuntary[something], they use incel many, many multiples of times more." is clearly not just referring to title, although title is particularly relevant since we are talking title. Alanscottwalker (talk) 15:19, 9 May 2018 (UTC)
::* Not surprised since I am aware of your consideration that nacs are unqualified to close controversial RMs, which I do consistently, as you also know. The community has already come to consensus on that, though, and as I said, the nac vs. admin arg has no place here. I will agree that the close rationale could have been less like a !supervote and more concise and objective; however, the outcome would have been the same if I had closed it. The page would have been moved as proposed. Paine Ellsworth put'r there 11:38, 9 May 2018 (UTC) :::* User:Paine Ellsworth, no, I am sure I do not know you to be a consistent closer of controversial discussions. Is that really what you meant to write? —SmokeyJoe (talk) 12:45, 9 May 2018 (UTC) ::::*Wouldn't have written it if I hadn't meant it, SmokeyJoe. The debates I close have almost always been relisted and are from the bottom of the table. And those are frequently controversial. Those take longer to research; however, they provide me with that old "find a need and fill it". Paine Ellsworth put'r there 13:01, 9 May 2018 (UTC) :::::* Maybe you are doing excellently well, I don’t recall seeing any complaints. Do you ever !vote instead of closing when the close is just a bit too unclear? —SmokeyJoe (talk) 13:33, 9 May 2018 (UTC) ::::::* Depends on several factors, such as my interest in the subject, or my interest in how WP policies/guidelines are/are not being followed and so on. I think "unclear" is a very subjective call. This MR is all about an RM that seems "unclear" to some people; however, to the closer and to myself, the decision to rename the article came from a crystal clear understanding of the debate. It was a good call. Paine Ellsworth put'r there 14:15, 9 May 2018 (UTC) ::*Regarding {{tq|On the other, I can say that no admin would ever have written that closing statement.}}, I suppose Ivory Coast may be the equivalent of an RM godwin's law, but I'd say here Beeblebrox exerted quite a bit of effort in a supervotey looking close a la this one. I don't think it there is an as vast gap in non-admin and admin closes as you think Galobtter (pingó mió) 11:48, 9 May 2018 (UTC) :::* I am holding to that statement. Ivory Coast was quite a storm, to much for me to have even come close to engaging in. User:Beeblebrox is noted as erring on the side of being interesting yes, and can be supervotery, but let’s see if even he will attest that he would have closed this incel RM the same way, substance and rationale. Vast gap? I didn’t say vast gap. There is a line, thicker than a fine line, but not quite a bright line. —SmokeyJoe (talk) 12:45, 9 May 2018 (UTC) ::*This board has just three contested closes last month, and one this month, so what's your evidence for all this controversy? Alanscottwalker (talk) 11:57, 9 May 2018 (UTC) :::* The controversy is evident in the pre-MRV days. These reviews brought about a massive decline in post-RM close controversy. There was some surge in MRV excitement with the creation of pagemover rights leading to courageous pagemover closings. There is not a lot of controversy, did I say there was? A lack of controversy is a poor reason to loosen the standard on closings. —SmokeyJoe (talk) 12:45, 9 May 2018 (UTC) :::::Oh, I thought you were saying there was too much controversy and somehow that had to do with NAC, but since NAC do fine and are empowered by policy to do so, that seems great, right? Alanscottwalker (talk) 13:03, 9 May 2018 (UTC) :::::: WP:NAC, the essay now supplement, is important for keeping controversy under control. I think NAC, unlike RMNAC, is in good shape, has the balance pretty right. I think the NAC lines need to be supported, otherwise RMs can be decided by the fasted NAC-er to jump in. This was not an uncontroversial close. I’m not sure I get your question. —SmokeyJoe (talk) 14:34, 9 May 2018 (UTC) :::::::My questions are that non-admin closes of moves is supported by policy and that's a good thing, right? Whereas your essay is not policy, and that's a good thing right? Alanscottwalker (talk) 14:46, 9 May 2018 (UTC) :::::::: You’re asking policy taggery and wonkery? Which has higher standing, the supplement to deletion policy, or the RM closing instructions? The lines of possible debate! It’s very much non-ideal, I want to fix it, but now is not a good moment. —SmokeyJoe (talk) 14:51, 9 May 2018 (UTC) :::::::::I'm asking why you would want to change non-admin-closes of moves when it's consensus to have them (they don't actually create much controversy) and it's a fine and rational system since admins are just as perfect as non admins (no more perfect than editors, certainly)? Alanscottwalker (talk) 14:57, 9 May 2018 (UTC) :::::::::: What are you suggesting I am wanting to change? Very few NACs are BADNACs, but some are from time to time. I would like RMNAC harmonised with NAC. —SmokeyJoe (talk) 15:20, 9 May 2018 (UTC) :::::::::::Apparantly you want to restrict non-admins from closing moves, that is a change because it is against current consensus, and it's frankly a bad idea. Alanscottwalker (talk) 16:00, 9 May 2018 (UTC) :::::::::::: Non admins have a tendency to supervote close calls, the advice of WP:NAC applies to both XfD and RM discussions. —SmokeyJoe (talk) 16:37, 9 May 2018 (UTC) :::::::::::::What? That seems entirely untrue, when you compare to admins, and at any-rate, it does not logically follow, nor is it supported by evidence. Alanscottwalker (talk) 17:20, 9 May 2018 (UTC) :::::::::::::: I have noticed that supervote allegations are more often made against NACs. —SmokeyJoe (talk) 12:17, 10 May 2018 (UTC)
::*Plainly false. The sources section of the article currently uses 'incel' 28 times and 'involuntary[something]' twice. Alanscottwalker (talk) 14:32, 9 May 2018 (UTC) :*{{tq|few if any supporting "Incel" provided evidence that it's the more WP:COMMONNAME for the subculture}} - It's strange to see so many people saying nobody provided evidence as though we should presume that people will be opining without bothering to look at the sources already cited for themselves. The burden should be on those who want to argue against what is clearly the common name among the sources we already cite. As soon as it's moved back, we will have an article about a subject about which just about all of the sources use a different name. Should I have copy/pasted the whole list of sources? I won't quite do that, but below I've started just running through the sources we cite, starting at 1 and going down until I run out of steam. None are omitted. ::*CNN - [https://edition.cnn.com/2018/04/25/us/incel-rebellion-alek-minassian-toronto-attack-trnd/index.html The Toronto suspect apparently posted about an 'incel rebellion.' Here's what that means] (multiple instances of "incel community", also ""Incel" is short for "involuntarily celibate." It's a movement made up almost....", "Central to incel ideology is...") ::*Guardian - [https://www.theguardian.com/world/2018/apr/24/toronto-van-attack-facebook-post-may-link-suspect-with-incel-group Toronto van attack: Facebook post may link suspect to misogynist 'incel' subculture] ::*CBC - [http://www.cbc.ca/radio/thecurrent/the-current-for-april-26-2018-1.4636157/violent-misogyny-found-in-incel-is-a-form-of-terrorism-says-author-1.4636164 Violent misogyny found in 'incel' is a form of terrorism, says author] ("As the online phenomenon of "incels" makes headlines...", "...the incel community...", "...incel ideology...") ::*Vox - [https://www.vox.com/world/2018/4/25/17277496/incel-toronto-attack-alek-minassian Incel, the misogynist ideology that inspired the deadly Toronto attack, explained] ::*Atlantic - [https://www.theatlantic.com/international/archive/2018/04/toronto-van-incel/558836/ ISIS Tactics Have Spread to Other Violent Actors] ("...to “incels,” short for “involuntarily celibate.” Incels, mostly male..." -- as others do, it gives a "short for" or a "combination of", or a "comes from", and then proceeds to use "incel" as the primary identifier) ::*Globalnews - [https://globalnews.ca/news/4164340/alek-minassian-facebook-page/ What we learned from Alek Minassian’s Incel-linked Facebook page – and what we’d like to know] ("Alan Carter looks into what the "incel" subculture is.", ""referenced the misogynist Incel subculture") ::*Weekend Edition Sunday - [https://www.npr.org/2018/04/29/606773813/whats-an-incel-the-online-community-behind-the-toronto-van-attack What's An 'Incel'? The Online Community Behind The Toronto Van Attack] ::*Globe and Mail - [https://www.theglobeandmail.com/canada/article-the-incel-community-and-the-dark-side-of-the-internet/ The ‘incel’ community and the dark side of the internet] ::*SPLC - [https://www.splcenter.org/hatewatch/2018/04/24/i-laugh-death-normies-how-incels-are-celebrating-toronto-mass-killing "I laugh at the death of normies": How incels are celebrating the Toronto mass killing] ("Minassian was part of the “incel” community") ::*Elle - [https://www.elle.com/life-love/sex-relationships/a33782/involuntary-celibacy/ Elle] (one of the best sources for "involuntary celibate" that we cite, perhaps, but even that combines it with incel and love-shy) ::*Observer - [http://observer.com/2014/05/hating-the-players-elliot-rodger/ Hating Women Was His Disease] ::*Fox News - [http://www.foxnews.com/us/2018/04/24/incel-sexual-frustration-rebellion-at-center-toronto-attack.html 'Incel' sexual frustration 'rebellion' at center of Toronto attack] ("What are ‘incels’? While the group is supposed to be a “support group” for men...") ::*Politico - [https://www.politico.com/magazine/story/2018/05/08/intel-involuntary-celibate-movement-218324 How ‘Incel’ Got Hijacked] (uses involuntary celibate several times as a way to show the evolution of the "incel" culture) ::*Guardian - [https://www.theguardian.com/world/2018/apr/25/woman-who-invented-incel-movement-interview-toronto-attack Woman behind 'incel' says angry men hijacked her word 'as a weapon of war'] (similar) ::*Guardian - [https://www.theguardian.com/technology/2017/nov/08/reddit-incel-involuntary-celibate-men-ban 'Incel': Reddit bans misogynist men's group blaming women for their celibacy] ("The 40,000-strong ‘Incels’ community...") ::*NBC News - [https://www.nbcnews.com/news/us-news/after-toronto-attack-online-misogynists-praise-suspect-new-saint-n868821 After Toronto attack, online misogynists praise suspect as 'new saint'] ("online community known as 'incels'" -- as elsewhere, it gives this "short for" and proceeds to use "incels" as primary identifier) ::*Vice [https://www.vice.com/en_us/article/gyj3yw/how-reddit-is-teaching-young-men-to-hate-women How Reddit Is Teaching Young Men to Hate Women] ::*USA Today - [https://www.usatoday.com/story/news/2018/04/26/incel-rebellion-alek-minassian-sexual-entitlement-mens-rights-elliot-rodger/550635002/ Incels, Alek Minassian and the dangerous idea of being owed sex] ::*Can anybody reading these really say that an argument that "incel is the name most commonly used in the sources for this subculture" is not supported by evidence, etc.? — Rhododendrites talk \\ 14:55, 9 May 2018 (UTC) :::*Well, it's not that many who say that (although yes, one is too many), because it's just not true, it's a flat-out falsehood, and should be stricken by the MR closer.Alanscottwalker (talk) 15:03, 9 May 2018 (UTC) :::*So we should only title our articles by headlines and not what the sources say in the body? List one of the sources that do not also mention "Involuntary celibacy" in the body of the article. I can give several that mention "Involuntary celibacy", but not "Incel", but I could not find any that did not also mention "Involuntary celibacy" from your list. Dave Dial (talk) 15:06, 9 May 2018 (UTC) :::::Not-the-point. Reliable Sources overwhelmingly, use it in title case, they use it in first mention, and they use it multiple times more in body - thus it is much, much more common, which is confirmed by Google Trend. Alanscottwalker (talk) 15:12, 9 May 2018 (UTC) ::::::That's what I was getting at, {{u|Dave Dial}}. Looking at the sources given, they tend to give "incel", often in quotation marks, as an alternate term for "involuntary celibacy". No clear evidence was presented that "incel" is the common name, let alone so much more common that it overrides reasonable objections. And it's certainly true that no one parsed the evidence in the actual discussion (which is presumably why they're trying to do it now that it's been pointed out.)--Cúchullain t/c 17:08, 9 May 2018 (UTC) :::::::You have again misrepresented the sources and shown your ivote here is not based on procedure -- the reliable sources in the article use "incel" much, much more often, 100% upon 100%'s times more if you read them than "involuntary [anything]" (and using them in quotation marks just means they're taking about the word) You are the only one who is trying to make a new analysis of sources, here, and misrepresenting them to boot, so your ivote here has to be stricken, as out-of-process. Alanscottwalker (talk) 19:13, 9 May 2018 (UTC) ::::::::Nonsense. You are parsing, which would be fine in the RM discussion, but is just re-litigation here. At any rate it's only one of the various issues with this close.--Cúchullain t/c 19:26, 9 May 2018 (UTC) :::::::::The only nonsense is yours. Your Ivote must be stricken because it is you that is trying to argue the underlying move, indeed you gave us your own personal analysis of the sources, here, not procedure at all. -- Alanscottwalker (talk) 19:37, 9 May 2018 (UTC) :::*Also, several on this page are relitigating the Move Request, with arguments not presented in the actual MR. Dave Dial (talk) 15:09, 9 May 2018 (UTC) :::::Untrue, rather, it's important to point out falsehoods and flat-out-unsupported mistakes and statements. Alanscottwalker (talk) 15:12, 9 May 2018 (UTC) :::::: There’s an awful lot of scare quoting in your listed sources. Also, they mostly contain negligible commentary on “incel”s per se. Their use violates WP:UNDUE. —SmokeyJoe (talk) 15:17, 9 May 2018 (UTC) ::::::::Even, were that true, which it is not, that makes no sense, we are talking about which word is used more commonly and those sources show 'incel' is used much more commonly Alanscottwalker (talk) 16:16, 9 May 2018 (UTC) ::::::::: It’s not true that there are a lot of scare quotes? Or that the listed sources make brief mention of communities before devoting coverage to an incident? Used more commonly in quality sources is what counts. You listed a lot of sources that shouldn’t be used. —SmokeyJoe (talk) 16:37, 9 May 2018 (UTC) ::::::::::No, it's not true that those are scare quotes - and reliable sources commonly use 'incel' over and over again (and no, I did not just use scare quotes). The rest of your comment is nonsense on stilts, the article uses multiple quality reliable sources, so quality reliable sources commonly use 'incel', and they use 'involuntary celibacy' very rarely in comparison to 'incel' (and no I did not just use scare quotes). We are not naming another article, we are naming an article that uses these RS. Even more telling, is you cited absolutely no sources for anything you argued, just told us what you like and don't like, so you made no cognizable argument in the underlying matter, nor here in this appeal. - Alanscottwalker (talk) 17:45, 9 May 2018 (UTC) ::::::::::: Nah, they are scare quotes. :::::::::::::You did not bring any sources in the underlying discussion. You did not discuss sources at all, you merely told us what you like and don't like. Now, you tell us you have not even read the sources in the article, which just reaffirms your position is based not on sources but what you like and don't like. You're new reference bombing complaint is just you complaining that the reliable sources use the word incel too much, for your taste. In other words, its somehow too much, the common name.Alanscottwalker (talk) 10:59, 10 May 2018 (UTC) ::::::::::::::: I read enough of the referenced sources. All of them from the lede, and all from the communities section, and I read all of the titles. The scare quotes are pretty prominent. —SmokeyJoe (talk) 12:17, 10 May 2018 (UTC) ::::::::::::::::They're all from the lead/early part of the article because I started at 1 and started linking. These are the sources every person who commented in that RM should have looked at, and are all right there. Nobody should have to link them all. Quotation marks are used when introducing a neologism. It doesn't mean they're not actually called that. It wouldn't matter if it were a portmanteau or some other term readers have never heard of. The statement "they call themselves 'X'" which then goes on to use 'X' (with or without quotes) to refer to that subject seems to me that that's the common name of the subject if we have an article about X... — Rhododendrites talk \\ 13:27, 10 May 2018 (UTC) ::::::Despite you calling that Raccoon a Coon, because article headlines overwhelming refer to it as a "'Coon", it's not "falsehoods and flat-out-unsupported mistakes and statements" pointing out that the body of articles all refer to the Racoon as a Racoon in the articles. This is definitely being litigated with people trying to provide "new evidence". Or evidence that was countered in the MR. Discounting countered evidence is supervoting. There is just no way there was a consensus to move. Dave Dial (talk) 15:19, 9 May 2018 (UTC) :::::::Well, then why repeat falsehoods and flat-out mistakes, we are not discussing coons - we are discussing a word for something that is used many, many times more commonly than the other. That's just the the way the real world works, we are not here to enshrine what you don't like about the real world. Alanscottwalker (talk) 15:23, 9 May 2018 (UTC) ::::*{{ec}}x2 @Dave Are you kidding me with this? {{tq|So we should only title our articles by headlines and not what the sources say in the body}} - Headlines can be useful to summarize an article, but yes, all of those sources (with the possible exception of Elle) use "incel" as the primary identifier in the source, not just in the headline. ::::*{{tq|List one of the sources that do not also mention}} - Yes, sometimes another name is mentioned. They say where the name came from. The name. Where the name of the subculture came from. The subculture is "incel" (short for/comes from/a combination of... involuntary and celibate). We don't use more words just to use more words, we don't use the etymology of a concept as the name for the concept when the name of the concept is far more prominent and frequently used, we don't different name for a community just because the actual name of that community is a portmanteau, and we don't ask "yes, but do the sources also include the name Dave prefers, even if it's mentioned just as background?" The question is, for the subculture, based on these sources, what is the common name for that subculture? What is the most recognizable name for the subculture? Which is the most precise name for the subculture? ::::*{{tq|Also, several on this page are relitigating the Move Request, with arguments not presented in the actual MR}} - Obviously not true. Some people decided that arguments that presume we're talking about the sources in the article are articles that have no basis in sources. The above list is for convenience, since it seems people are not interested to look at the sources we were talking about. — Rhododendrites talk \\ 15:27, 9 May 2018 (UTC)
:*I don't understand why you keep referring to opposing arguments in such bad faith. You made the [https://en.wikipedia.org/w/index.php?title=Talk:Incel&diff=838208997&oldid=838208615 same argument in the previous attempt to change the article name] to "Incel". Rhododendrites wrote: Oppose - When reliable sources use the term "incel" it is almost always quickly identified as meaning "involuntary celibacy." As this article has been framed to be about that concept and not just the culture around it, we should use the full name.So when I, or others, make the same points, we are "Appalling" or "promoting falsehoods"? I understand disagreements, but not the accusations. Dave Dial (talk) 15:45, 9 May 2018 (UTC) ::*I'm only going to clarify this one thing: as I've already said multiple times, I supported the original name when it was unclear whether it would be just about the subculture or a broader topic. In the latter case, because part of the subject is clearly not known as "incel," and because the former is intelligible with the longer name, it made sense. When it became just about the subculture, we should name it after the subculture. — Rhododendrites talk \\ 13:27, 10 May 2018 (UTC) :::Move review is specifically for handling "procedural hangups" in a closing. It's certainly not for re-arguing the move discussion, or for introducing new arguments. It would be better to just re-open to move discussion and then folks can introduce all the new arguments and evidence they want.-Cúchullain t/c 17:08, 9 May 2018 (UTC) ::::Then why did you make blatantly false arguments above about sources, here? It appears you are now arguing your, ivote, here should be stricken. -- Alanscottwalker (talk) 17:14, 9 May 2018 (UTC) :::::What? I said that few if any supporters of "Incel" in the discussion provided evidence that that form is more common or otherwise preferable by policy, and it's also not evident from the sources in the article. Hence, the closer's decision was faulty.--Cúchullain t/c 17:24, 9 May 2018 (UTC) ::::::That is a blatantly false statement, 'incel' is used multiple times more commonly in the sources in the article, and you still have not explained why you are giving your personal analysis of sources - so your ivote, here, must be stricken because you are not sticking with procedure at all, you are trying to blatantly wedge your editorial opinion in. Alanscottwalker (talk) 17:35, 9 May 2018 (UTC) :::::::Drop the hyperbole. It's not a "personal analysis" of sources - it's simply not obvious in the sources that "incel" is more common, without considerable parsing, as you are doing. Nor did most of the supporters provide evidence to that effect in the discussion. Hence, it's a faulty close. Again, you could add the interpretation and evidence you want if the RM is re-opened, and then the next close won't be under such a cloud.--Cúchullain t/c 19:20, 9 May 2018 (UTC) ::::::::It's not hyperbole, it is just your misrepresentation and your personal analysis (you bizarrely and falsely claim just what you want to deem as 'not obvious' is not personal to you - when it totally is personal to you) and it is blatant misrepresentation of the reliable sources, which say over and over again 'incel' much, much more commonly - you are just here, ivoting as if this were the underlying move, and trying to make arguments as if this were the move. Alanscottwalker (talk) 19:34, 9 May 2018 (UTC) :::::::::If you want to make those arguments, you're free to in a reopened RM. And you're more likely to persuade people if you stop being so nasty.--Cúchullain t/c 19:41, 9 May 2018 (UTC) ::::::::::If anyone is being nasty, it is you. Your ivote here needs to be stricken because you have clearly made non-procedural arguments, and misrepresented sources. Alanscottwalker (talk) 19:47, 9 May 2018 (UTC) {{unindent}}I'd still like to hear {{u|RedSlash}}'s explanation for why they closed the discussion several days early, when comments were continuing to come in. That alone should have been a reason for them to reverse their close and let it run its course when asked by multiple reasonable editors.--Cúchullain t/c 19:41, 11 May 2018 (UTC) :{{tq|several days early}} - the requirement is that it last for 7 days. After relisting, if discussion winds down, it's not "early" in the sense of being premature to close it. {{tq|when comments were continuing to come in}} - When it was relisted, discussion was active. Here's what it looked like at time of close: ::5/3 there were 45 edits ::5/4 there were 25 edits ::5/5 there were 23 edits ::5/6 there were 0 edits ::5/7 there was 1 edit ::5/8 there was 1 edit ::Then it was closed. ::— Rhododendrites talk \\ 23:43, 11 May 2018 (UTC) :::I've closed hundreds of RMs, many of them controversial, and sometimes before the relisting period is complete. However, if another editor, let alone several, reasonably asked me to reopen the discussion until the full period, I would never ignore them, if only so that it doesn't make the decision look incompletely formed, and to avoid forcing everyone to sink their time into a lengthy move review. If there's really a clear consensus, it'll still be there in a few days, and if new comments change the outcome, it's obviously for the best. The only reasons I can think of not to respond to this perfectly reasonable request are bad ones - the closer can't brook challenge and is digging their heels in to protect their decision, they're invested in the outcome and WP:SUPERVOTING, they don't value others' time, they just choked, etc. Perhaps {{u|Red Slash}} has another reason; they should give it here.--Cúchullain t/c 14:56, 12 May 2018 (UTC) :::::In the underlying discussion, at the time of relisting you argued that it should be closed as no consensus, and you further argued content claims based on a draft of prior deleted/salted article. Others disagreed with you and your claims, so perhaps you should turn your accusatory questions on yourself. Are you digging in your heals to protect your invested outcome? When RedSlash closed, commenting was not continuing and you have made other argumentative misstatements, which have been laid bare, above - thus, it appears you accuse yourself. -- Alanscottwalker (talk) 20:35, 12 May 2018 (UTC) ::::::Cool story, bro.Cúchullain t/c 00:22, 13 May 2018 (UTC) :::::::Bro? Adolescent talk, does not make your arguments any less invested. Alanscottwalker (talk) 08:41, 13 May 2018 (UTC)
:And for the same reason the article shouldn't be titled "Involuntary celibacy" if it's only going to cover the subculture it currently mainly covers, "Involuntary celibacy" shouldn't redirect there either. Flyer22 Reborn (talk) 20:44, 10 May 2018 (UTC)
|
style="text-align:center;" | The above is an archive of the move review of the page listed in the heading. Please do not modify it. |