Planters – Moot. Everyone can read the RM discussion for themselves and see how close it was (or not). There are no hard and fast rules governing a moratorium based on the type of "no move" close, and even if there were they can be ignored with a sufficiently good reason; the content of the previous RM is what matters rather than one or two words. King of♥♦♣ ♠ 09:07, 20 April 2020 (UTC)[reply]
The following is an archived debate of the move review of the page above. Please do not modify it.
Although I agree that a close without a move might be reasonable, I don't think "not moved" was the correct outcome, "no consensus" would probably have been more appropriate, see my (longer) reasoning on the closer's talk page. See a similar example of "not moved" v "no consensus" at Wikipedia:Move review/Log/2016 July. Crouch, Swale (talk) 17:42, 27 March 2020 (UTC)[reply]
Endorse. While I don't fully agree with the closer's talk page statements, I do understand how, in some cases, one wants to say "no consensus" but does not want to see another move request for a good while. So I think this RM's closure should stand as is. P.I. Ellsworthed.put'r there 00:14, 28 March 2020 (UTC)[reply]
“Not moved” is ambiguous. See WP:NOTMOVED. I think it looks like a “no consensus” to move. The issue seems to be of the moratorium for repeating the proposal. I encourage admin closers to declare a specific moratorium if they chose, including a specific moratorium for a specific editor such as the previous RM initiator. There has been disagreement on the default moratorium following a “no consensus” RM. I suggested a two-month minimum, but others have said it should be six months. Whatever the moratorium, I think it should count from the close of this MRV, at least for the MRV nominator. Too much discussion on unimportant questions is disruption. —SmokeyJoe (talk) 00:35, 28 March 2020 (UTC)[reply]
Endorse. The outcome (not moving the article) was certainly correct. The closing summary was "not moved ... per the discussion below". Anyone reading that discussion can make their own assessment as to whether there was no consensus or consensus not to move, but either way the outcome is the same. I don't see a point to move reviews unless it's to overturn the outcome (moving something not moved, or reverting a move). Issues regarding moratoriums or wording of the close summary are better discussed on individual article talk pages. Station1 (talk) 04:46, 28 March 2020 (UTC)[reply]
I don't think it was certainly correct, there have been numerous cases where we've made primary topic redirects (such as Bookends) in the end of these discussions in accordance with PLURALPT and that could have at least applied here to redirecting to the DAB (since the singular anyway has no PT) but I don't see how there was clear consensus. I already discussed it with the closer and although they replied and appeared to offer to change it, they didn't end up doing so but I understand that there're busy so that's probably why. Crouch, Swale (talk) 09:34, 28 March 2020 (UTC)[reply]
By "certainly correct" I meant only that given the discussion in this particular case, no closer would have moved the article as proposed. Station1 (talk) 20:51, 28 March 2020 (UTC)[reply]
Reject Move Review as unneeded, by which I mean, look at the chart. Pay attention to the center-right of the flowchart here.. We need to make this bold: if you think it should be "no consensus" instead of "not moved" or the other way around, do not file a move request; just write a note on the talk page saying "the closer called this X, but it's obviously Y." I can see why people make a big deal out of this, but just a bit of clarification on the article's talk page is all that's needed. RedSlash 00:59, 31 March 2020 (UTC)[reply]
The above is an archive of the move review of the page listed in the heading. Please do not modify it.
Pink_Season_(Pink_Guy_album) – Overturn to move. The side in favor of the move has provided detailed evidence, contrasted with a mere assertion of WP:NOPRIMARY from the lone opposer. As two relists have failed to attract more participation, it is not clear whether more relisting will help. As this is a fairly marginal result WP:NPASR applies. King of♥♦♣ ♠ 08:50, 20 April 2020 (UTC)[reply]
The following is an archived debate of the move review of the page above. Please do not modify it.
This RM had three participants: the nom, me in !support, and one in !oppose. The nom and I provided evidence and arguments for the !support view, whereas the !oppose voter offered no evidence or argument. I asked the closer to clarify/revisit their close in light of that, quoting the relevant guidelines, and they declined, so I'm bringing it here for discussion. Dohn joe (talk) 14:27, 9 March 2020 (UTC)[reply]
Relist because both relists were inadequate. The discussion sits near the “no consensus”-“move” boundary, the problem is the brevity of User:In_ictu_oculi’s !vote. He should be pinged and invited to expand. —SmokeyJoe (talk) 08:36, 10 March 2020 (UTC)[reply]
My view is that a No.5 album in Japan can be expected to get less page views than a No.70 album in the US, but that Primary Topic nevertheless requires both PT criteria to be met. And not convinced that the US album is more long term significant in print sources, where the hits are for the No.5 in Japan album. In ictu oculi (talk) 15:51, 10 March 2020 (UTC)[reply]
There is no requirement for a topic to meet both WP:PRIMARYTOPIC criteria to be primary. As it says: in many other cases, only one sense of primacy is relevant. Whether this is one of those "many" cases is why we're here. Iffy★Chat -- 18:30, 10 March 2020 (UTC)[reply]
Overturn. The nominator and the one support voter offered solid arguments for the move; the dissent was a perfunctory "no primary" with nothing to support that argument. Schazjmd(talk) 21:38, 9 March 2020 (UTC)[reply]
Overturn.No relist as this RM has already been twice relisted. There is consensus for renames, so those pages should be moved.PI Ellsworthed.put'r there 03:22, 10 March 2020 (UTC)[reply]
Overturn and move per Paine Ellsworth and the similar points with regard to the Ice age discussion, just because there is an oppose !vote doesn't mean there can't be consensus. The strength of the arguments matter more than the number (which including the nom was 2:1 anyway). Crouch, Swale (talk) 07:25, 10 March 2020 (UTC)[reply]
Endorse - two editors said it was the primary topic, one editor said it wasn’t. All three opinions are based on the same evidence of page links. I’m not sure how thats anything other than no consensus. Levivich[dubious – discuss] 15:44, 10 March 2020 (UTC)[reply]
The other thing it can be is “Not ready to be closed”. There was an obvious need to ping an early !voter to explain a rationale. —SmokeyJoe (talk) 21:37, 11 March 2020 (UTC)[reply]
I see your point, a relist to discuss the oppose vote rationale could be productive. Levivich[dubious – discuss] 03:42, 12 March 2020 (UTC)[reply]
Comment I am unsure if a relist would result in a consensus. So the no-consensus was likely the correct result. Lightburst (talk) 18:00, 10 March 2020 (UTC)[reply]
Overturn and move. The lone oppose vote was not grounded in reality. Calidum 17:32, 11 March 2020 (UTC)[reply]
That is insulting, and as a closer opinion, a supervote. Not PRIMARYTOPIC is a perfectly valid reason to not move a DAB page off the basename. —SmokeyJoe (talk) 21:35, 11 March 2020 (UTC)[reply]
Saying there is no primary topic without explaining why is akin to a WP:VAGUEWAVE or WP:JDLI vote, meaning it can be disregarded. Calidum 01:04, 12 March 2020 (UTC)[reply]
"VAGUEWAVE" is much better than "not grounded in reality". The nom's "seems like a primary topic" invited the denial, except the nom goes on to provide evidence. Calling "discount the VAGUEWAVE, consensus to move" would be a bold close. Not discounting the VAGUEWAVE, which is what the closer did, was not OK. I think the VAGUEWAVE vote needed a challenge with a ping for a clear result if not answered, or further discussion if answered. --SmokeyJoe (talk) 03:08, 12 March 2020 (UTC)[reply]
Endorse closure there was 1 for moving the No.70-in-US album to primary, there was 1 for having the No.5-in-Japan and No.70-in-US albums retain their full titles with artist names to enable readers to distinguish. How is that consensus for a move??In ictu oculi (talk) 09:20, 13 March 2020 (UTC)[reply]
For starters, since apparently we're counting votes, you always have to count the nominator, as well. OVerturn and relistRedSlash 23:00, 20 March 2020 (UTC)[reply]
The above is an archive of the move review of the page listed in the heading. Please do not modify it.
Ice age (disambiguation) – Decision endorsed. The WP:NAC may not have been advisable, but it appears to be a correct reading of the result. King of♥♦♣ ♠ 08:35, 20 April 2020 (UTC)[reply]
The following is an archived debate of the move review of the page above. Please do not modify it.
Although there were reasonable points based on PT#2 against the move, the arguments that it failed PT#1 were surely stronger and contained more explanation and references to guidelines, views and how people search, also 5 were in favour v only 3 against so it seems like among the strength and number of arguments that there was a narrow consensus to move. Closer suggested taking it to move review from my objection to the close. It could also be relisted but given that it had been open for over 18 days that might not have been necessary. Crouch, Swale (talk) 18:26, 1 March 2020 (UTC)[reply]
Endorse closure. Head-counting is not how we do things. There were reasoned arguments on both sides in a moderately well-attended debate, and no clear winner; therefore, WP:NOCONSENSUS. No prejudice against a future WP:RM. Narky Blert (talk) 01:25, 2 March 2020 (UTC)[reply]
Yes I know head counting isn't how we do things, I was pointing that as well as the stronger arguments there were more support, a factor that is often taken into account after the strength of arguments. Crouch, Swale (talk) 05:53, 2 March 2020 (UTC)[reply]
Yet again, we have a relatively new Wikipedian presumably trying to be helpful, but WP:NAC closes of all but clear cut cases are not helpful if they mean revisiting the whole thing here at WP:MRV. Sure, budding soon to be administrators can prove their wisdom by clever NAC closes, but this NAC closer is not cleverly persuading the complainant, and so the close is a net negative. I suggest to the closer that they would best contribute to the project here by reverting their close for an admin to close.
That said, I really can’t see that discussion closed any other way. —SmokeyJoe (talk) 07:01, 2 March 2020 (UTC)[reply]
Endorse closure. Clear no consensus. Support arguments were not stronger, given the very common capitalisation of the primary term in the sources. Correct closure. -- Necrothesp (talk) 15:24, 2 March 2020 (UTC)[reply]
Joe, you crack me up... "Yet again, [complaints about NAC]. Good close." What makes you think we wouldn't be here if an admin had closed it no consensus? If the closer did what you suggested and self-reverted, and then another admin re-closed as no consensus, do you think the MR would not still be filed? In that case, we will have spent even more time, which would be even more of a net negative. With respect, your anti-NAC digression is out of line. Suggesting a non-admin closed a discussion because they are "budding soon to be administrators" or are trying to "prove their wisdom by clever NAC closes" is kind of a personal attack, certainly an ad hominem, and certainly WP:ABF. This is a volunteer who volunteered their time to assess consensus. And did so correctly. Opinions about NACs should be at WT:NAC; here, we should just apply the global consensus that exists regarding NACs (WP:RMNAC), rather than write things that make non-admin closers feel bad about the volunteer work they've done. Especially when it's a good close, which this was, because both sides had solid policy-based arguments, and there just wasn't general agreement one way or another. Endorse closure. Levivich[dubious – discuss] 07:16, 8 March 2020 (UTC)[reply]
What makes you think we wouldn't be here if an admin had closed it no consensus?. The fact that admins as a rule make better closing statements, and respond better to queries about their closes.
If the closer did what you suggested and self-reverted, and then another admin re-closed as no consensus, do you think the MR would not still be filed? Yes. The questioner would know that an admin's close should be respected unless there is a clear reason otherwise. If the closer is a non admin, and he doesn't understand the close, why should he think the closer understood anything better?
"budding soon to be administrators" is the typical support for why non admins are allowed to attempt difficult cases. If they make a good job of it, it is evidence to point to at RfA. At RfA, many ask about how they would perform close calls.
I do not agree it was a "good" close. It was a "correct" close. However, the close demonstrably fails to convince someone. The closer's answer on their talk page fails to impress. I really understand how you feel about the closure. But, you don't expect me to just discard all the Opposes on the discussion. Hence, the no consensus result is a non-explanation. It's okay. If you really think and believe that there was a narrow consensus to move. Take it to move review and hopefully, it'll be sorted there once and for all is a complete failure to take responsibility for the close. Someone has a question, flick it to WP:MR. That is much help.
You wrote: both sides had solid policy-based arguments. That's another non-statement, non-explanation. A person asking about the close obviously doesn't see the "solid policy-based arguments" the way you do, and asserting "solid policy-based arguments" at them explains nothing. A better closing statement, or later explanation, would point to at least one solid policy-based argument for, and one solid policy-based argument against, both not well countered, as the explanation for no consensus. Anything less does not advance the explanation for the questioner.
It was a no consensus. Participants on both sides are citing valid reasons, and talking past each other. Someone says DIFFCAPS carries the proposal. Someone else says DIFFCAPS is a fading practice. That matches policy talk threads, such as Wikipedia talk:Article titles/Archive_57#RFC. The RM contains seven instances of "clear", with almost that many perspectives on what is clear. The only participant in the RM working much to turn the voting into the consensus building exercise is User:Crouch,_Swale, who raised good points that went unanswered. When such a discussion is closed with a bland "no consensus" and the followup discussion ends with "Take it to move review and hopefully, it'll be sorted there", it really isn't good enough. The close was correct, but it was not a good close, and the closer should not walk away thinking they did an OK job wrapping up a contested discussion. The closer, User:Nnadigoodluck, should either be here defending their close, or reverting their close. --SmokeyJoe (talk) 07:53, 8 March 2020 (UTC)[reply]
Perhaps maybe it should have been relisted again. Crouch, Swale (talk) 07:57, 8 March 2020 (UTC)[reply]
I would say no in this case. There have been some good points made about the inadequate closing statement and the questionable handling of the situation by the closer on their talk page, but one relist should usually be enough, especially when the most recent post was eight days prior to the close. This was brought to MRV for good reason; however, that survey and discussion was finished, and there was definitely no consensus. Another relist was not the answer. PI Ellsworthed.put'r there 08:21, 8 March 2020 (UTC)[reply]
I don’t think relisting would be justified, but then I think relisting is pointless compared to leaving it open. Someone clever might have Relisted with a good refocusing comment. No, instead, I think DIFFCAPS needs to be continued as a policy discussion, as it was. Actually, I think DIFFCAPS should be removed as a LINKBOX SHORTCUT from the policy page, as it does not enjoy consensus, is not clearly written anyway, and accordingly it should not be considered a policy-based reason. —SmokeyJoe (talk) 08:26, 8 March 2020 (UTC)[reply]
DIFFCAPS appears to enjoy more consensus than years ago especially since the Red Meat example (a case where the upper case topic had less than 1/71 of the views of the lower case meaning) has now been removed. Years ago (say 2008) there was far less guidance on this. Similar to here users explained how readers would benefit from placing theDAB at the Title Case title in accordance with WP:PRIMARYTOPIC, again the opposers didn't provide a significant amount of evidence that the Title Case version primarily refers to the age. I also don't think the non-admin in its self is a problem and I would have dealt with this in the same way had this been an admin. I've filed hundreds of RMs and maybe questioned the closure of around half a dozen but haven't started MRs of any of them (note that I'm not even the nom) see a discussion at User talk:Dekimasu#Planters for a close by an admin that I am discussing. That said the point about overlooking/discarding the oppose views came up again here when even though we might not discard/ignore a comment it doesn't have to necessarily be given the same amount of weight. Crouch, Swale (talk) 19:04, 8 March 2020 (UTC)[reply]
"DIFFCAPS appears to enjoy more consensus"? I don't think that is right. That is certainly your contention, explicitly in the RM, and in the RM it is actively disagreed with. I consider it contentious. Maybe "contentious" is too strong a word, because it is repeatedly brought up at WT:AT, but few engage, and this makes me think that the majority does not particularly care. --SmokeyJoe (talk) 01:30, 9 March 2020 (UTC)[reply]
Endorse - DIFFCAPS itself has a lot of ambiguity. I honestly regret having codified it into our doctrine--looking back on it, it's silly. Lots of people don't care about capitalization when they search for things; most search engines are not case-sensitive. Anyway, that's a tangent. I wish the closer had elucidated more, but the close is reasonable on the merits. RedSlash 23:06, 20 March 2020 (UTC)[reply]
User:Red Slash, you’ve interspersed a but of “citation needed” tags into my post above. That implies that you want to discuss further. I note that you were a bold NAC closer, and yes you do have quite a history bold codification of RM doctrines, overbold in my opinion, especially at RMCI, and including RMNAC. It’s worth discussing at WT:RM. Somethings, like how RM NACs constitute the bulk of MR business is WP:BLUESKY.
On this matter, you wish the closer had elucidated more, great, but what are you going to do about it, or help do about it. I note that the closer User: Nnadigoodluck has archived notification of this review without even posting here to acknowledge it. That is an accountability failure. —SmokeyJoe (talk) 00:51, 21 March 2020 (UTC)[reply]
Yes I did. First, there are far fewer admins on Wikipedia than non-admins, so obviously we would expect more RMNACs than RMACs, so we would therefore naturally expect more non-admin closures here. If you want to go look through all the closures of all RMs and see the percentage of non-admin closures, and then compare it to the percentage of non-admin closures on WP:MRV, you are more than capable of doing so. Until then, yes, a citation is needed that non-admins end up on WP:MRV disproportionately, lest your claim be as pointless as saying "Most of the problems in my life come from people not named 'Fred', so I shall only trust people named Fred from now on".
Second, no one has ever provided evidence that RMNAC closers are admins in training. That's a strawman argument. We close because it's a necessary part of the encyclopedia's business and we like to do it.
Third, this particular closer didn't do a fantastic job. Granted. But admins as a rule make better closes? Really? Cite me that one. RedSlash 21:11, 23 March 2020 (UTC)[reply]
User:Red_Slash, good answers thank you. I need to clarify myself:
I am not against non admins closing RMs, but I do think a proper standard should be maintained. I think all closers should should be cautious and careful closing contested discussions. If the close is not obvious, the close must be explained, in the closing statement. The WP:ADMINACCT level of accountability for the close must be assumed by NAC-ers. In this case, the closer does not meet the standard.
This forum, WP:MRV, is for reviewing closes, and the process generally. It is not RM#2. I think some people are !voting "Endorse" because it was the right result, and not because it was a good close. I think you have made yourself clear. I think the standard bold statements "Endorse" vs "Overturn" are too inarticulate.
A good NAC-er will revert their close if they can't explain their close to a reasonable complainant. They should not say: Take it to move review and hopefully, it'll be sorted there. --SmokeyJoe (talk) 02:02, 24 March 2020 (UTC)[reply]
Good answers yourself, Smokey. (Or rather, @SmokeyJoe:.) I agree with you 100% on an ADMINACCT-level accountability for non-admin closers. I agree with you on endorsing closes that are correct but done poorly; I think that happens here because our focus isn't on making sure the process is right but rather the final result. As for your final point, any good closer should revert their close if they can't explain it. RedSlash 22:54, 31 March 2020 (UTC)[reply]
