Jump to content

Wikipedia:Move review/Log/2021 May

From Wikipedia, the free encyclopedia
The following is an archived debate of themove reviewof the page above.Please do not modify it.
List of the 100 largest population centres in Canada(talk|edit|history|logs|links|archive|watch) (RM) (Discussion with closer)

There is significant precedence ofWP:CONCISEhere specifically segretation of title issues from editorial issues.Catchpoke(talk)00:31, 24 May 2021 (UTC)[reply]

It doesn't work that way...WP:CONSENSUSstates "Consensus on Wikipedia does not mean unanimity (which is ideal but not always achievable), nor is it the result of a vote." in thelede.User:Buidhe counted votes as you have too.Catchpoke(talk)01:49, 24 May 2021 (UTC)[reply]
PerWikipedia:Closing discussions:"If the discussion shows that some people think one policy is controlling, and some another, the closer is expected to close by judging which view has the predominant number of responsible Wikipedians supporting it, not personally select which is the better policy."
  • Endorse.Closure couldn't have gone any other way. Not a single contributor to the discussion agreed with the nomination.Rreagan007(talk)05:24, 24 May 2021 (UTC)[reply]
  • Endorse.The participants disagreed with the nominator's views. Full stop. You could conceivably renominate after waiting a few months (although I wouldn't advise it), but a good-faith disagreement with other!voters about policy is no reason to appeal the closure.Extraordinary Writ(talk)00:29, 25 May 2021 (UTC)[reply]
The above is an archive of themove reviewof the page listed in the heading.Please do not modify it.
The following is an archived debate of themove reviewof the page above.Please do not modify it.
Upper Palaeolithic Europe(talk|edit|history|logs|links|archive|watch) (RM) (Discussion with closer)

Closed as consensus to move despite the head count of substantive!votes being 2-1 with no agreement amongst us. The closer's summary also introduced two arguments that weren't previously mentioned in the discussion. I asked buidhe to reopen it as an invalidWP:NAC,but they first refused and then went silent. – Joe(talk)09:11, 20 May 2021 (UTC)[reply]

  • Endorse(uninvolved). The reference in this MR statement to a 'head count' is fundamentally faulty logic. The appellant was the sole arguer for the other side of a reasonably well-attended RM (which tend to have quite sparse attendance), where extended justification was given by the majority of participants, plus a "per X"!vote endorsing another's argument. Buidhe's closing statement was a reasonable summary of a discussion in which she correctly found consensus, and qualms with the precise wording could have been brought to her without threats to open an MR. The appellant's conduct on Buidhe's talk was deeply unimpressive.Vaticidalprophet09:33, 20 May 2021 (UTC)[reply]
    • I would have preferred not to have had to bring this to MR, but doing so is the proper procedure when the outcome of an RM is disputed, not a "threat". – Joe(talk)10:01, 20 May 2021 (UTC)[reply]
  • See alsoWikipedia:Administrators' noticeboard/Incidents#Non-admin closes by Buidhe.– Joe(talk)09:54, 20 May 2021 (UTC)[reply]
  • Unclose and relistRelisting is cheap. The discussion had 3 participants and 0 relists, and Joe's concern seems reasonable on the surface (I say surface because this topic area isn't my area of expertise, so I wouldn't really be able to tell the difference).ProcrastinatingReader(talk)11:42, 20 May 2021 (UTC)[reply]
  • Overturn(uninvolved, because unaware) per Joe Roe, as the new title is thoroughly misleading - it shouldn't even be a redirect to this article. Or launch a new proposal to move toEarly modern humans in Europewhich I think is better (let me know if this happens). 3 people is not a great turn-out for a RM discussion.Johnbod(talk)13:38, 20 May 2021 (UTC)[reply]
  • Endorsebutencourage further discussion.The close really cannot be faulted as there was only one editor commenting in opposition, and whilein retrospectI think Joe Roe was making a good point about an anthropology topic being housed under a title implying geography, this was framed as concern about the scope of the article, and nobody who did participate was convinced. While I agree that a discussion with four participants is a long way from "reasonably well-attended", there had been no new comments in more than five days before the close, suggesting that relisting wouldn't have led to any different result, although I also don't see where any of the participants tried to advertise the discussion (there's no notice onWT:ANTHROPOLOGY,for example). I don't see why Joe's concern can't be a new discussion, possibly an RFC.Ivanvector's squirrel(trees/nuts)14:06, 20 May 2021 (UTC)[reply]
  • Relista 3-1 headcount isn't enough when several of the arguments against a move haven't been addressed. I hate to litigate the arguments here, but the fact that Cro-Magnons were people and Europe is a continent (and Upper Palaeolithic Europe a culture) is enough to suggest that more discussion is needed to clarify what the topic of the article is.User: Lực(power~enwiki,π,ν)16:38, 20 May 2021 (UTC)[reply]
  • RelistI don't think the close was necessarily wrong or improper, and it would be correct if no further participation occurs, but I see no harm in relisting for further discussion.SportingFlyerT·C17:51, 20 May 2021 (UTC)[reply]
  • Relist.The close was not improper, per se, but I agree the nomination could use further discussion.Rreagan007(talk)20:37, 20 May 2021 (UTC)[reply]
  • Overturn (Relist)(uninvolved). The close does not feel to give proper weight to topic shift implied by the move. Especially given that additional titles have been suggested above, resisting for more discussion seems reasonable.PaleAqua(talk)03:11, 22 May 2021 (UTC)[reply]
The above is an archive of themove reviewof the page listed in the heading.Please do not modify it.
The following is an archived debate of themove reviewof the page above.Please do not modify it.
Pennsylvania Dutch language(talk|edit|history|logs|links|archive|watch) (RM) (Discussion with closer)

The closer only counted noses during the move request and did not evaluate the arguments against the move, which were far stronger, relying on the weight of reliable sources, than the arguments in favor of the move which relied only on the results of Google searches and anecdotal evidence.TaivoLinguist (Taivo)(talk)10:09, 12 May 2021 (UTC)[reply]

  • But you ignored the issue ofWP:PRECISIONwhich requires that a name be accurate and not ambiguous. The use of "Dutch" (which the language is not) in the article title when the vast majority of reliable sources use "German" (which the language is) is a violation of precision. So while you did, indeed, count noses and based your move solely on unreliable sources, you ignored reliable sources and the speakers themselves which indisputably use "Pennsylvania German" as the language name. --TaivoLinguist (Taivo)(talk)10:22, 12 May 2021 (UTC)[reply]
  • As stated on my user talk, that's not whatWP:PRECISIONrequires. Both "Pennsylvania Dutch" and "Pennsylvania German" are unambiguous terms and thus equally PRECISE. (t·c)buidhe11:56, 12 May 2021 (UTC)[reply]
  • The term "Pennsylvania Dutch" is precise insofar as it refers unambiguously to one language. The fact that that term means something other than the sum of its parts makes it no less precise thanJerusalem artichokewhich, while neither an artichoke nor from Jerusalem, is precisely one thing. In fact, if one is going to invoke etymology in evaluating precision, "Pennsylvania Dutch language" ismoreprecise than "Dutch language" because "Dutch" itselfmeans"German" insofar as it comes from the German and Dutch words for theGermanlanguage, "Deutsch" / "Duits". So, thankfully, origin isn't relevant: otherwise we'd have to consider renaming "Dutch language" to "Netherlands language" or "Nederlands".
Setting origin aside as a consideration, then, "Pennsylvania Dutch" means what it meanstoday,and is a precise as well as, I believe, the common term for its referent.Largoplazo(talk)12:35, 12 May 2021 (UTC)[reply]
  • The difference between "Jerusalem artichoke" and "Pennsylvania Dutch" is that botanists and cultivators use "Jerusalem artichoke" as the common name for that plant while linguists and speakers do NOT use "Pennsylvania Dutch" as the common name for that language. Reliable, academic sources use "Jerusalem artichoke" while reliable, academic sources use "Pennsylvania German". --TaivoLinguist (Taivo)(talk)16:05, 12 May 2021 (UTC)[reply]
  • And reliable sources very commonly use "Pennsylvania Dutch".Like, even a cursory search of Google News shows that.Orngrams,if you prefer. I'm not relitigating the move - only trying to draw your attention to the implicit backing behind the cries to use the "common name". It is the most common name in reliable sources. If it's not the most common name withinacademia,that's an interesting point to add to the trivia section, but "academic" has never been a synonym for "reliable" on Wikipedia.RedSlash18:08, 19 May 2021 (UTC)[reply]
  • And as Wikipedia continues to produce materials trying to gain trust among academics and university faculty and regularly has booths at scientific conferences to promote its "usefulness" in college courses, there are Wikipedia editors (with unknown academic credentials) and policies written by them that claim that acedemics are not the most reliable sources and shouldn't be trusted above journalists who have a solid BS degree. Because of course a journalist who might write about a dozen unrelated topics every week knows more about any subject than the professor who has spent two decades researching that single subject. --TaivoLinguist (Taivo)(talk)04:51, 20 May 2021 (UTC)[reply]
  • "trying to gain trust among academics and university faculty"?‹ThetemplateFake citation neededis beingconsidered for merging.›[citation needed]x 1000000. We are not "trying to gain trust among academics". We are trying to be an encyclopedia. Encyclopedias are meant to inform the general public, not academic experts in the field, for the same reason that LeBron James is unlikely to find reading the article onbasketballto be very helpful for him. We use common names on Wikipedia. Of course, we trust theresearchacademics post--of course we do! But our job as an encyclopedia is to present their findings in relatively common English. That's... literally what encyclopedias are meant to do.RedSlash22:12, 25 May 2021 (UTC)[reply]
  • The problem with those two links is that they reflect the uses of the phrase, and most uses of the phrase are not about the language. The vast majority of the items on the Google News link, for example, are hits for "Pennsylvania Dutch folk arts", "Pennsylvania Dutch potato fillings", or "Pennsylvania Dutch apple butter". If usage in reliable sources is going to be overridden, then we need actual evidence for common usage, and not just editors mi xing up different topics. –Uanfala (talk)12:49, 20 May 2021 (UTC)[reply]
  • If we're going to use simple Google counts, then "Pennsylvania Dutch language" yields about19600 resultswhile "Pennsylvania German language" yields about39,300 results.I've never liked using raw Google searches (whether Google News or Google Scholar [98versus172"Pennsylvania Dutch language" to "Pennsylvania German language" ] or just vanilla Google), but there you are, nearly twice as many references to the specific phrase "Pennwylvania German language" than to "Pennsylvania Dutch language". Where isWP:COMMONNAMEnow? The closer in a clearly controversial move used a speedy close without allowing sufficient time for the arguments to fully develop. That's what this is about--a closer rushing to a judgement based solely on counting noses forWP:COMMONNAMEwithout evaluating the arguments is actually notWP:NPOV.--TaivoLinguist (Taivo)(talk)13:39, 20 May 2021 (UTC)[reply]
    • Exactly! So we have a situation where editors make a COMMONNAME argument based on a confusion between several topics, and not only does this blatant error not get noticed by most of those involved, but the resulting outcome is on track to get almost unanimously endorsed at move review. What are the implications of that? My past experience has been that RM discussions on language or ethnicity topics have always been hit and miss, but I've still tried to encourage people to use it for potentially controversial moves. Now, I'm finally convinced the process is practically dysfunctional, so for questions of article titles in this topic area, going forward we should probably start using the same method we use for resolving all other issues – informal talk page discussion. –Uanfala (talk)17:11, 20 May 2021 (UTC)[reply]
  • Endorseas uninvolved, but involved (in the sense of pointing OP to MR rather than continuing to litigate on Buidhe's talk) in the conversation leading up to the MR. (I've fixed the formatting for the link to that discussion, which came out botched; feel free to revert if procedurally unwanted.) The discussion assessed naming policy and use of each name in reliable sources, and came to a consensus that the suggested title was the most appropriate option at this time. It would have been a supervote to close otherwise. I am also unimpressed by the OP's behaviour in the preceding discussion, which was the sort of vague rant about "BADNACs" that keep popping up on the talks of brilliant closers who haven't taken the kick-me sign off them yet.Vaticidalprophet10:30, 12 May 2021 (UTC)[reply]
  • (involved,!voted against the outcome)I don't really see a problem with the close. AFAIK there is no policy that states usage in the discipline that studies the subject automatically trumps usage in popular parlance. I would have liked to see empirical evidence thatPennsylvania Dutchdoes in fact prevail, but the consensus seems clear, unless there was a canvassing or something that compromises the process that I'm not seeing.Nardog(talk)10:39, 12 May 2021 (UTC)[reply]
  • Overturn(uninvolved). Based on the numbers alone, there likely was a consensus to move. The issue is that nearly everyone who supported the move merely linked toWP:COMMONNAMEwith no further justification for it. Suchvague wavesare not enough to overcome the evidence given in opposition to the move. Plus, as was pointed out in the RM,WP:COMMONNAMEsays to avoid using inaccurate or ambiguous names (ambiguous here having its ordinary meaning, not the Wiki meaning).--Calidum14:27, 12 May 2021 (UTC)[reply]
  • What, in the ordinary sense of "ambiguous", is ambiguous about "Pennsylvania Dutch language"? Does that term refer to more than one thing? As for accuracy, I won't rehash everything, but please see my comments above about the implications for the English name of the language spoken in the Netherlands if accuracy is going to be assessed on an etymological basis.Largoplazo(talk)15:46, 12 May 2021 (UTC)[reply]
  • What is ambiguous is that this is not a Dutch language and scholars virtually unanimously use the term, "Pennsylvania German". The ambiguity is that you might see "Pennsylvania Dutch" when reading a Pennsylvania travel guide, but you will never see it when discussing languages of the United States. Should Wikipedia actually be a reference that uses ill-informed labels or a reference that uses accurate labels? Those who are looking for ill-informed labels can easily be directed to the accurately labelled articles. --TaivoLinguist (Taivo)(talk)16:11, 12 May 2021 (UTC)[reply]
  • "Ambiguous" means one term can be understood multiple ways. You've confused it with synonyms, multiple terms for the same thing.
When you say "this is not a Dutch language", it suggests to me that you didn't read my comments about how that's irrelevant. If you had, even if you disagreed with me, I don't think you'd just repeat what I'd already addressed as though I hadn't.Largoplazo(talk)16:23, 12 May 2021 (UTC)[reply]
  • My comment ties into my argument above although I could have made that clearer. "Jerusalem artichoke" is not a relevant issue because botanists and cultivators both use the term, while only lay persons use "Pennsylvania Dutch", but linguists and speakers alike use "Pennsylvania German". --TaivoLinguist (Taivo)(talk)16:36, 12 May 2021 (UTC)[reply]
Very few speakers use the term "Pennsylvania German", and I'm sure there must be at least a few linguists who use the term "Pennsylvania Dutch".Rreagan007(talk)07:09, 21 May 2021 (UTC)[reply]
I invite you to find a linguist who uses "Dutch" among the thousands who don't. --TaivoLinguist (Taivo)(talk)11:37, 21 May 2021 (UTC)[reply]
  • While not a definitive argument in a move discussion, this article had been stable for years (over a decade at least) at "Pennsylvania German language" without any discussion. It was not a controversial title. Stability in Wikipedia, especially when that stability is based on scientific fact and not "common knowledge", is something that should count more than a string of "me too" votes for "common name" without any reference to reliable sources or evidence of user inconvenience. --TaivoLinguist (Taivo)(talk)16:20, 12 May 2021 (UTC)[reply]
You're essentially arguing for asupervotefrom the closer. That's not how this process is supposed to work.Rreagan007(talk)06:54, 21 May 2021 (UTC)[reply]
That's exactly how this process is supposed to work because evaluating a request for move, like every other discussion on Wikipedia, isWP:NOTAVOTE.I daresay that every contentious request for move or request for comment discussion has included a warning to "bean counters" that the closer will evaluate arguments and not count noses. Are you saying that those warnings are misplaced? If so, then every closing will be a straight up and down vote and Wikipedia will never be trusted again. --TaivoLinguist (Taivo)(talk)11:37, 21 May 2021 (UTC)[reply]
No it's not. PerWikipedia:Closing discussions:"If the discussion shows that some people think one policy is controlling, and some another, the closer is expected to close by judging which view has the predominant number of responsible Wikipedians supporting it, not personally select which is the better policy."Rreagan007(talk)14:52, 21 May 2021 (UTC)[reply]
Then I fully expect you to show up at every RM to point out that arguments don't count, just noses. That way no one wastes time with evidence or logical arguments and simply states "Yea" or "Nay" and moves on. But every single controversial RM closer (especially if they are an admin) I've been involved with has made a point of noting that they arenotcounting noses, but counting the quality of the arguments under appropriate Wikipedia policies. --TaivoLinguist (Taivo)(talk)17:17, 21 May 2021 (UTC)[reply]
Just because it's not a pure majority vote doesn't mean that the count is irrelevant. How many RM discussions have you seen where over 70% of the participants supported the move where it wasn't moved? In general, if a RM discussion has over 2/3 support, it's going to be passed.Rreagan007(talk)18:28, 21 May 2021 (UTC)[reply]
But when one side has actual evidence and the other side is simply, "I think this is true", there's a problem with a drive-by closer just counting noses. As was demonstrated earlier by accurate Google searches, "Pennsylvania German language" is twice as frequent as "Pennsylvania Dutch language", but since there wasn't any evidence presented by the proponents at all, this didn't come up in a discussion. The proponents had no data to counter the reliable sources that were presented by the opponents of the move. This is no way to run an encyclopedia, where "I think this is true" becomes more important than fact. (I could make a comparison to the current US political climate, but will avoid it.) --TaivoLinguist (Taivo)(talk)18:37, 21 May 2021 (UTC)[reply]
The closer doesn't get to use their own judgment to override the judgment of the other contributors to the discussion. The closer is supposed to merely reflect the determination of the contributors to the discussion.Rreagan007(talk)19:31, 21 May 2021 (UTC)[reply]
  • Overturn(uninvolved). The proposed title may or may not be the more common name (this was asserted by many, but I'm not seeing any meaningful evidence: the difference is small in the ngrams reported by kwami, and a Google search for "Pennsylvania Dutch language" returns comparable numbers to "Pennsylvania German language" ). But even if the proposed name is indeed more common, it's still difficult to justify choosing it when it's virtually absent from the reliable sources on the topic. This is not just an issue of academic vs. non-academic sources, it's about sources dedicated to the topic (whether they're academic or not, see for instancethese publications) vs. sources that only make mentions of it. –Uanfala (talk)16:45, 12 May 2021 (UTC)[reply]
  • Endorse.The move was proper. The arguments in favor of the move were simply stronger than those opposed.Rreagan007(talk)01:21, 13 May 2021 (UTC)[reply]
  • What arguments? Just an uncritical appeal toWP:COMMONNAMEwas the only argument ever mentioned and that was just a "me too" citing by most proponents. That included myself until the better, and more solid arguments presented byUser:Kwamikagami.His arguments, based on actual reliable sources, was far more convincing. There were no convincing arguments presented in favor of the move. --TaivoLinguist (Taivo)(talk)03:38, 13 May 2021 (UTC)[reply]
An argument doesn't have to be complex to be correct.WP:COMMONNAMEis our central policy for article titles, and most people in the discussion agreed that the proposed title was the most common name for the topic and that the article should be moved based on that policy, so it was moved.Rreagan007(talk)06:31, 21 May 2021 (UTC)[reply]
But an argument requires at least one of the proponents to provide some kind of evidence other than "I say it's true". --TaivoLinguist (Taivo)(talk)11:39, 21 May 2021 (UTC)[reply]
Anecdotal evidence is some kind of evidence.Rreagan007(talk)14:45, 21 May 2021 (UTC)[reply]
  • Endorse.<uninvolved>Won't reargue the RM, but even though the RM's nom sort of lost his lunch toward the end, there was nothing wrong with this closure. Wait a year and try to move it back if you want, but right now the obvious consensus is for Penn Dutch ( "Dutch" sounds so much like "Deutsch", doesn't it?) language. Apologies to the nom, but this closure should stand tall on its own.P.I. Ellsworthed.put'r there00:36, 17 May 2021 (UTC)[reply]
  • Endorseas uninvolved. The opposers and the MRV nominator are seemingly focused onWP:CORRECTNAME... which isn't a thing(as it is very subjective - seeWP:V),so of course the closer wouldn't have considered it. Common, recognizable, concise, consistent, and precise are all either equal or in favor of the move. This close was a piece of cake.RedSlash18:03, 19 May 2021 (UTC)[reply]
  • Endorseperfectly reasonable close, given the arguments. I don't see a good reason to not defer to the common name here, nor do I see a good reason why the common name is not "Pennsylvania Dutch language".Elli(talk|contribs)10:25, 20 May 2021 (UTC)[reply]
  • Endorse- while the numeric count was close, the supporters' arguments that the common name should be used were well-grounded in policy and convention, while the opposers' arguments that non-scientific literature should be disregarded in determining the common name have no grounding in policy at all and are specifically againstWP:NPOV.Good close.Ivanvector's squirrel(trees/nuts)12:58, 20 May 2021 (UTC)[reply]
    • I don't know what NPOV has to do with the issue (unless the policy has changed so that we now assign the same weight to dedicated books on a topic as we do to passing mentions in news items).WP:COMMONNAMEexplicitly states that ambiguous or inaccurate names are often avoided even if they're used in reliable sources, and here we don't even have reliable sources to support the move in the first place as virtually all the literature on the topic uses the other term. –Uanfala (talk)13:14, 20 May 2021 (UTC)[reply]
      • The term is not ambiguous, and the POV issue is that you can only establish that it's inaccurate if you disqualify any literature which says otherwise.Ivanvector's squirrel(trees/nuts)13:54, 20 May 2021 (UTC)[reply]
        • Your POV argument is only valid if Wikipedia is just about counting noses and not about evaluating arguments. Remember that one of Wikipedia's policies isWP:NOTAVOTE.This closer rushed to move the article based solely on counting noses and not doing the harder job of evaluating the arguments. As you can clearly see from my Google numbers above searching for "Pennsylvania Dutch language" versus "Pennsylvania German language" (where the "German" variant was twice as common as the "Dutch" variant), theWP:COMMONNAMEargument wasn't even based on sound data. That's the job of the closer, which was not done in this case as they rushed to close the discussion prematurely. --TaivoLinguist (Taivo)(talk)14:21, 20 May 2021 (UTC)[reply]
          • There is no evidence that the closerrushed to close the discussion prematurely:it had run for the full seven days mandated by the requested move process, plus half a day. I'm not the first to point this out to you, and making baseless accusations of misconduct like this is a personal attack; you should withdraw those comments. As for the "Dutch" vs "German" argument, Buidhe specifically addressed this in her closing comment, and move review is not a venue for rehashing arguments that have already been considered.Ivanvector's squirrel(trees/nuts)16:38, 20 May 2021 (UTC)[reply]
            • There is no requirement that a controversial discussion must be closed after seven days and Buidhe did nothing more than count noses without considering the arguments. Allmost all of the "COMMONNAME" justifications had no evidence to support that assertion while the opponents of the move provided links to impeccable sources. Just saying "CoMMONNAME" in a move request is unacceptable behavior when there is no evidence presented for COMMONNAME even in the proposer's comment. And do I think that Buidhe made an error? Of course I did, that's why we're here. Buidhe did not do the job of a closer to do more than just count "the votes" and ignored the principle ofWP:NOTAVOTE.Buidhe did not consider that there was no evidence presented in favor of the move and ignored the solid evidence against the move that was presented. Buidhe did, indeed, just count the noses that said, "Me, too, COMMONNAME". --TaivoLinguist (Taivo)(talk)20:01, 20 May 2021 (UTC)[reply]
              • Any good closer would have done the exact same thing. Most participants in the discussion agreed that the proposed title was the common name and that the article should be moved based on that policy. And participants in a move discussion are allowed to use their own knowledge and experience when making that determination.Rreagan007(talk)07:06, 21 May 2021 (UTC)[reply]
                • Like I mentioned above (and in many other places), allowing "I say it's true because I think it's true" as evidence in Wikipedia runs directly counter to the Wikipedia Foundation's well-documented efforts to be taken more seriously by college and university professors. --TaivoLinguist (Taivo)(talk)11:44, 21 May 2021 (UTC)[reply]
                  • If our goal in article naming were "to be taken more seriously by college and university professors" then our article naming policy would be to name all articles based on their official or academic names, not their common names. Wikipedia is for the masses, not the academic elites.Rreagan007(talk)14:44, 21 May 2021 (UTC)[reply]
                    • If that is the case, then perhaps you should talk to Wikipedia Foundation and tell them to stop wasting your contributions on trying to raise the academic profile of Wikipedia. --TaivoLinguist (Taivo)(talk)17:13, 21 May 2021 (UTC)[reply]
                      • Wikipedia is a general-use encyclopedia, not an academic journal, and the Wikipedia Foundation understands that. But I'm not sure that you do.Rreagan007(talk)18:33, 21 May 2021 (UTC)[reply]
                        • Then why does the Wikipedia Foundation spend thousands of dollars a year trying to promote Wikipedia as a valuable reference for college and university classes? I said nothing about "academic journal", just a source that college and university professors would recommend as a reliable source for students to use (as they would use Encyclopedia Britannica, for example). As it is, the vast majority of professors don't allow Wikipedia as a reference because of the attitude that expertise is always trumped by common opinion. --TaivoLinguist (Taivo)(talk)18:42, 21 May 2021 (UTC)[reply]
  • EndorseConsensus is clear that the common name in the US (Pennsylvania Dutch, with Dutch being derived fromDeutsch) is what the article should be titled. The minority opinion that the name used in linguistics should be the title... is a minority opinion.User: Lực(power~enwiki,π,ν)16:40, 20 May 2021 (UTC)[reply]
  • Endorse(uninvolved). Supporters presented a strong common name argument which the close reflects.PaleAqua(talk)15:18, 21 May 2021 (UTC)[reply]
  • Endorsegood close, only available option to a closer I think.SportingFlyerT·C18:43, 21 May 2021 (UTC)[reply]
  • Endorse(uninvolved) Strong support that proposed title reflects COMMONNAME preference for “Dutch” and that this trumps academic preference for “German”. The argument that “Dutch” is “ambiguous” has been soundly refuted in the sense relevant to WP title decision-making. —-В²C13:22, 26 May 2021 (UTC)[reply]
The above is an archive of themove reviewof the page listed in the heading.Please do not modify it.
The following is an archived debate of themove reviewof the page above.Please do not modify it.
December 2011 North Atlantic cyclone(talk|edit|history|logs|links|archive|watch) (RM) (Discussion with closer)

I do not feel comfortable watching@Chicdat:insert their opinion, close the discussion and move the system to December 2011 North Atlantic cyclone as a compromise title. During the RM it was pointed out that a few years ago after a couple of requested moves, a clear consensus emerged that the name of the article should beHurricane Bawbag,even though it wasn't a hurricane as that was the most common name for the system and still is afaik. The name was stable at this title until@Buttons0603:decided to move it to Cyclone Friedhelm against the consensus on December 21, 2019, as he felt that "we should go with the official name on this one..".This was subsequently reverted by@My Name is Madness:on May 26, 2020, as the move went against the prior consensus. However, Buttons0603 then decided to revert back to Friedhelm as it is the "Official Government Issued name", however, it is debatable if it is as the name was assigned by FU Berlin's Name our Storms, which0 isn't the German Government's National Weather Service but the scheme is supported by them. Anyway this was then reverted on March 29, 2021 by@Blethering Scot:who left a note on thetalk pagestating that there was clear consensus that the article should be called Hurricane Bawbag and that a new RM would be required should anyone wish it to be called something else.@LightandDark2000:then moved it to Cyclone Friedhelm with the edit summary: "The current name isn" and left an essay on the talk page which kicked of the requested move in which I participated in strongly supporting the Hurricane Bawbag name. However, others felt that we should ignore the previous consensus and Wikipedia's policies on titles and stay with Friedhelm. I also note that since the discussion was closed that@LightandDark2000andHurricane Noah:,have decided that they also don't like the way thatdiscussionwasclosedwhich is why I am bringing it here in the hopes of getting an uninvolved admin to look over it.Jason Rees(talk)02:17, 12 May 2021 (UTC)[reply]

  • Overturn.The close of that discussion was very clearly aSupervote(specifically a Forced-compromise supervote), there was absolutely no consensus in that discussion to use "December 2011 North Atlantic cyclone" as the article title, and closers do not get to move articles to whatever title they like as a compromise. From my reading of the discussion I think the outcome of the discussion was "No consensus" - votes are fairly evenly split, reasonable arguments are being made by both sides.192.76.8.91(talk)08:16, 12 May 2021 (UTC)[reply]
  • Overturnsupervote of the forced compromise variety. Totally invalid. If there's no consensus for the proposal, it should be closed as no consensus, allowing editors to start a new RM to try a different title. The closer cannot decide the new title themselves, in an attempt to avoid the 'hassle' of having another discussion.ProcrastinatingReader(talk)10:56, 12 May 2021 (UTC)[reply]
  • Overturn- clear supervote. Even if there was no consensus, it should've been moved back to the previous consensus of Hurricane Bawbag. Further, I think there was clearly a consensus for Hurricane Bawbag - the!votes for the other name are clearly not based in policy and were another attempt byWP:WPTCto enforce a "official names only" rule on articles against the project wide consensus ofWP:COMMONNAME- this was not taken into account in the closure. Regardless, the no consensus outcome if that is what is determined should result in a move back to Hurricane Bawbag as the longstanding consensus title. -bɜ:ʳkənhɪmez (User/say hi!)06:33, 13 May 2021 (UTC)[reply]
    • @Berchanhimez:Try not to tarr the whole of WPTC with the same brush, since I am a member of WPTC and I was very firmly against using Friedhelm. I also agree if there was no firm consensus that the article should be returned to Bawbag by default.Jason Rees(talk)00:32, 17 May 2021 (UTC)[reply]
      • Wasn't attempting to tarindividualswithin the project - but it's clear that the "mentors" (i.e. more experienced editors and admins) within the project have not taken enough of a mentoring role such that this sort of behavior where personal opinion trumps policies/guidelines can take hold in the newer editors. I have my own opinions as to why this likely is but that is irrelevant - the project as a whole has a problem with it, and it's not any one editor's fault necessarily. This move request, where numerically there were a lot of people arguing contrary to policy, is just another example of it. -bɜ:ʳkənhɪmez (User/say hi!)00:39, 17 May 2021 (UTC)[reply]
  • Overturn- no consensus means take it or leave it at the longstanding title. If half the people say one new title and half say a different new title, that's one thing. But if there's no consensus to move, don't pick a third title. I'm honestly a little baffled.RedSlash18:13, 19 May 2021 (UTC)[reply]
The above is an archive of themove reviewof the page listed in the heading.Please do not modify it.
The following is an archived debate of themove reviewof the page above.Please do not modify it.
Icon(talk|edit|history|logs|links|archive|watch) (RM) (Discussion with closer)

I believe that there was a consensus to move per the reasons given on the closer's talk page namelyeven if we ignore that and assume that significance is entirely subjective and every!vote counts equally, we're still left with a unusual situation – a primary topic remains whileeverybodyagrees that one of the two criteria (usage) is not met, and a slight majority (9 out of 16) believe the other (long-term significance) isn't eitherso I think that the close should be "move".Crouch, Swale(talk)16:50, 10 May 2021 (UTC)[reply]

  • Support the close-the long discussion on the closer's pageis worth reading.Johnbod(talk)16:56, 10 May 2021 (UTC)[reply]
  • Endorse.Reasonable close. Discussions are not a vote, and PRIMARYTOPIC doesn't requirebothcriteria to be met, and never has. The change asked for here would not be a reasonable reading of the discussion, and this looks very much like the proposer wants another bite at the apple.Egsan Bacon(talk)16:59, 10 May 2021 (UTC)[reply]
  • Endorse.While I am sympathetic to the underlying request, I think "no consensus" was a reasonable close here. As Egsan Bacon points out,WP:PTOPICdoes not require both criteria (which aren't even criteria, for the record) to be met.--Calidum17:08, 10 May 2021 (UTC)[reply]
  • Endorse.No consensus for the move detectable.Ewulp(talk)22:52, 10 May 2021 (UTC)[reply]
  • Endorse“no consensus”, but the closing statement is inadequate. —SmokeyJoe(talk)23:07, 10 May 2021 (UTC)[reply]
    @SmokeyJoe- I believe by "inadequate" you mean that my closing statement should have had some statement as to why I chose this outcome. Maybe the passage I provided on my talk page as part of the after-discussion would have been good to include as part of the closing statement? The passage I refer to -- "The people are about 50/50 split between No Primary Topic and religious icon being primary. A notable third option, ofCultural iconbeig the primary topic was made. There is also a philosophical schism between current term usage vs. historical usage being more important for Wikipedia in terms of primary topic selection. There is no consensus given this variety ofvaliddiscussion points. "Thanks --User:Ceyockey (talk to me)02:03, 11 May 2021 (UTC)[reply]
    Yes. Inadequate, meaning not enough words, given that the ordinary Wikipedian who is not a skilled reader of consensus in discussions could be left mystified as to why, as is demonstrated in hindsight. I would have you put some of the words from your talk page, maybe exactly these words, into the closing the closing statement. Better there than on a user_talk page. —SmokeyJoe(talk)07:53, 11 May 2021 (UTC)[reply]
  • Like a slight majority of those commenting above, I'm involved, so I'll avoid adding a bolded comment (otherwise, this move review will begin to look like it's just us, the participants from the RM, coming to repeat our!votes). The close is easiest to justify by a head count (which I guess places a lot of emphasis on the subjective aspect of determining primary topics). Objectively, I don't believe the oppose arguments were particularly strong – they rested on etymological primacy (something that's specifically ruled out bythe guidelines), or the supposed greater importance of topics in history (the history specifically of Europe) than topics in other fields. Also, it may be true that there's nothing in the guidelines suggesting an article has to meetbothprimary topic criteria, but I believe it's obvious that there should be rough consensus that it at leat meetsoneof them. –Uanfala (talk)15:17, 15 May 2021 (UTC)[reply]
  • Endorse.The close was proper.Rreagan007(talk)17:35, 17 May 2021 (UTC)[reply]
The above is an archive of themove reviewof the page listed in the heading.Please do not modify it.