Wikipedia:Requested moves

Page semi-protected
Source: Wikipedia, the free encyclopedia.

For the current list of potentially controversial requested moves, see § Current discussions.
"Wikipedia:RM" redirects here. For other uses, see Wikipedia:RM (disambiguation).
For detailed guidance on how and when to move a page, see Wikipedia:Moving a page.
Click here to purge this page
Shortcuts

Requested moves is a process for requesting the retitling (moving) of an article, template, or project page on Wikipedia. For retitling files, categories and other items, see When not to use this page.

Please read the article titling policy and the guideline regarding primary topics before moving a page or requesting a page move.

Any autoconfirmed user can use the Move function to perform most moves (see Help:How to move a page). If you have no reason to expect a dispute concerning a move, be bold and move the page. However, it may not always be possible or desirable to do this:

  • Technical reasons may prevent a move; for example, a page may already exist at the target title and require deletion, or the page may be protected from moves. See: § Requesting technical moves.
  • Requests to revert recent, undiscussed, controversial moves may be made at WP:RM/TR. If the new name has not become the stable title, the undiscussed move will be reverted. If the new name has become the stable title, a requested move will be needed to determine the article's proper location.
  • A title may be disputed, and discussion may be necessary to reach consensus: see § Requesting controversial and potentially controversial moves. The requested moves process is not mandatory, and sometimes an informal discussion at the article's talk page can help reach consensus.
  • A page should not be moved and a new move discussion should not be opened when there is already an open move request on a talk page. Instead, please participate in the open discussion.
  • Unregistered and new (not yet autoconfirmed) users are unable to move pages.

Requests are generally processed after seven days. If consensus to move the page is reached at or after this time, a reviewer will carry out the request. If there is a consensus not to move the page, the request will be closed as "not moved". When consensus remains unclear, the request may be relisted to allow more time for consensus to develop, or the discussion may be closed as "no consensus". See Wikipedia:Requested moves/Closing instructions for more details on the process.

Wikipedia:Move review can be used to contest the outcome of a move request as long as all steps are followed. If a discussion on the closer's talk page does not resolve an issue, then a move review will evaluate the close of the move discussion to determine whether or not the contested close was reasonable and consistent with the spirit and intent of common practice, policies, and guidelines.

When not to use this page

Shortcuts

Separate processes exist for moving certain types of pages, and for changes other than page moves:

Undiscussed moves

Shortcuts

Autoconfirmed editors may move a page without discussion if all of the following apply:

  • No article exists at the new target title;
  • There has been no previous discussion about the title of the page that expressed any objection to a new title; and
  • It seems unlikely that anyone would reasonably disagree with the move.

If you disagree with a prior bold move, and the new title has not been in place for a long time, you may revert the move yourself. If you cannot revert the move for technical reasons, then you may request a technical move.

Move wars are disruptive, so if you make a bold move and it is reverted, do not make the move again. Instead, follow the procedures laid out in § Requesting controversial and potentially controversial moves.

Requesting technical moves

Shortcuts
Shortcuts

If you are unable to complete a move for technical reasons, you can request technical help below. This is the correct method if you tried to move a page, but you got an error message saying something like "You do not have permission to move this page, for the following reasons:..." or "The/This page could not be moved, for the following reason:..."

  • To list a technical request: edit the Uncontroversial technical requests subsection and insert the following code at the bottom of the list, filling in pages and reason:

    {{subst:RMassist|current page title|new title|reason=edit summary for the move}}

    This will automatically insert a bullet and include your signature. Please do not edit the article's talk page.
  • If you object to a proposal listed in the uncontroversial technical requests section, please move the request to the Contested technical requests section, append a note on the request elaborating on why, and sign with ~~~~. Consider pinging the requester to let them know about the objection.
  • If your technical request is contested, or if a contested request is left untouched without reply, create a requested move on the article talk and remove the request from the section here. The fastest and easiest way is to click the "discuss" button at the request, save the talk page, and remove the entry on this page.

Technical requests

Uncontroversial technical requests

Requests to revert undiscussed moves

Contested technical requests

@Jkasutoro: The bracketed dab seems to be the standardised dab if you looked through Category:Mountains_of_Japan_by_prefecture. I have reverted your move back to the bracketed version as it is a mispelling as well. Do open a move discussion if you wish to update the disambiguator for all mountain dabs. – robertsky (talk) 09:34, 15 September 2024 (UTC)[reply]
  • Hollywood blacklist → Hollywood Blacklisting (move · discuss) – First, the word "blacklist" should be capitalized. Second, the article is not merely a list of those who were blacklisted, but rather a documentation of the entire phenomenon. Thus, it should be named "Hollywood Blacklisting", as it refers to the lead up, diedown, and specific people and grander background politics involved. Narfhead4444, Gamer Ordinare 17:31, 14 September 2024 (UTC)[reply]
    @Narfhead: Per MOS:CAPS, blacklist would be capitalized here if consistently capitalized in a substantial majority of sources. Google Ngrams shows that "Hollywood blacklist" is instead the most common form. I also don't see how adding -ing would expand the scope of the article. If you would like to request this move anyway, you can begin a requested-move discussion by clicking "discuss" on your request. You can remove this request after opening a discussion (or if you do not want to continue). SilverLocust 💬 14:55, 15 September 2024 (UTC)[reply]

Administrator needed

Requesting controversial and potentially controversial moves

Shortcuts

The discussion process is used for potentially controversial moves. A move is potentially controversial if either of the following applies:

  • there has been any past debate about the best title for the page;
  • someone could reasonably disagree with the move.

Use this process if there is any reason to believe a move would be contested. For technical move requests, such as to correct obvious typographical errors, see Requesting technical moves. The technical moves procedure can also be used for uncontroversial moves when the requested title is occupied by an existing article.

Do not create a new move request when one is already open on the same talk page. Instead, consider contributing to the open discussion if you would like to propose another alternative. Multiple closed move requests may be on the same page, but each should have a unique section heading.

Do not create a move request to rename one or more redirects. Redirects cannot be used as current titles in requested moves.

Requesting a single page move

Shortcut

To request a single page move, click on the "New section" (or "Add topic") tab of the talk page of the article you want moved, without adding a new subject/header, inserting this code: 

{{subst:requested move|New name|reason=Place here your rationale for the proposed page name change, ideally referring to applicable naming convention policies and guidelines, and providing evidence in support where appropriate. If your reasoning includes search engine results, please prioritize searches limited to reliable sources (e.g. books, news, scholarly papers) over other web results. You don't need to add your signature at the end, as this template will do so automatically.}}

Replace New name with the requested new name of the page (or with a simple question mark, if you want more than one possible new name to be considered). The template will automatically create the heading "Requested move 16 September 2024" and sign the post for you.

There is no need to edit the article in question. Once the above code is added to the Talk page, a bot will automatically add the following notification at the top of the affected page:

Unlike other request processes on Wikipedia, such as Requests for comment, nominations need not be neutral. Make your point as best you can; use evidence (such as Google Ngrams and pageview statistics) and refer to applicable policies and guidelines, especially our article titling policy and the guideline on disambiguation and primary topics.

WikiProjects may subscribe to Article alerts to receive RM notifications. For example, Wikipedia:WikiProject Biography/Article alerts/Requested moves is transcluded to Wikipedia talk:WikiProject Biography. RMCD bot notifies many of the other Wikiprojects listed on the talk page of the article to be moved to invite project members to participate in the RM discussion. Requesters should feel free to notify any other Wikiproject or noticeboard that might be interested in the move request, as long as this notification is neutral.

Single page move on a different talk page

Occasionally, a move request must be made on a talk page other than the talk page of the page to be moved. For example, a request to rename Wikipedia:WikiProject Articles for creation/Resources to Wikipedia:WikiProject Articles for creation/Reviewing and templates would need to take place at Wikipedia talk:WikiProject Articles for creation because the talk page of the project page to be moved, Wikipedia talk:WikiProject Articles for creation/Resources, is a redirect to that centralized discussion page. In this type of case, the requested move should be made using the following code: 

{{subst:requested move|reason=(the reason for the page move goes here).|current1=(present title of page to be renamed)|new1=(proposed title of page)}}

The |1= unnamed parameter is not used. The |current1= and |new1= parameters are used similar to multiple page moves described below.

Requesting multiple page moves

Shortcut

A single template may be used to request multiple related moves. On one of the talk pages of the affected pages, create a request and format it as below. A sample request for three page moves is shown here (for two page moves, omit the lines for current3 and new3). For four page moves, add lines for current4 and new4, and so on. There is no technical limit on the number of multiple move requests, but before requesting very large multi-moves, consider whether a naming convention should be changed first. Discuss that change on the talk page for the naming convention, e.g., Wikipedia talk:Naming conventions (sportspeople).

To request a multiple page move, edit at the bottom of the talk page of the article you chose for your request, without adding a new header, inserting this code: 

{{subst:requested move
| current1 = Current title of page 1
| new1     = New title for page 1 with the talk page hosting this discussion
| current2 = Current title of page 2
| new2     = New title for page 2
| current3 = Current title of page 3
| new3     = New title for page 3
| reason   = Place here your rationale for the proposed page name change, ideally referring to applicable naming convention policies and guidelines, and providing evidence in support where appropriate. If your reasoning includes search engine results, please prioritize searches limited to reliable sources (e.g. books, news, scholarly papers) over other web results. You don't need to add your signature at the end, as this template will do so automatically.
}}
See also: Template:Requested move/extended blank

For example, to propose moving the articles Wikipedia and Wiki, put this template on Talk:Wikipedia with current1 set to Wikipedia and current2 set to Wiki. The discussion for all affected articles is held on the talk page of the article where the template is placed (Talk:Wikipedia). Do not sign the request with ~~~~, since the template does this automatically (so if you sign it yourself there will be two copies of your signature at the end of the request). Do not skip pairs of numbers.

RMCD bot automatically places a notice section on the talk page of all pages that are included in your request except the one hosting the discussion, to call attention to the move discussion that is in progress and to suggest that all discussion for all of the pages included in the request should take place at that one hosting location.

For multi-move discussions hosted on a page which is itself proposed to be moved, it is not necessary to include the |current1=Current title of page 1 for the page hosting the discussion, as its current title can be inferred automatically. Occasionally the discussions for significant multi-move requests may be hosted on WikiProject talk pages or other pages in Project namespace, in which case it is necessary to include |current1= to indicate the first article to be moved.

Request all associated moves explicitly

Shortcut

Please list every move that you wish to have made in your request. For example, if you wish to move Cricket (disambiguation) to Cricket because you do not believe the sport is the primary topic for the search term "Cricket", then you actually want to move two pages, both Cricket (disambiguation) and Cricket. Thus you must list proposed titles for each page affected by your request. For example, you might propose:

If a new title is not proposed for the sport, it is more difficult to achieve consensus for a new title for that article. A move request that does not show what to do with the material at its proposed target, such as:

is incomplete. Such requests may be completed as a request to decide the best new title by discussion.

If a disambiguation page is in the way of a move, the request may be completed as proposing to add (disambiguation).

Template usage examples and notes
Talk page tag Text that will be shown (and usage notes)
{{subst:Requested move|new|reason=why}}
links talk edit
Requested move 16 September 2024

Wikipedia:Requested moves → New – why Example (talk) 07:07, 16 September 2024 (UTC)[reply]

Use when the proposed new title is given.
Do not sign this template—this tag is auto-signed when substituted. Be sure to use the subst:.
This tag should be placed at the beginning of the section containing the relevant discussion.

{{subst:Requested move|?|reason=why}}
Requested move 16 September 2024

Wikipedia:Requested moves → ? – why Example (talk) 07:07, 16 September 2024 (UTC)[reply]

Use when the proposed new title is not known.
Do not sign this template—this tag is auto-signed when substituted. Be sure to use the subst:.
This tag should be placed at the beginning of the section containing the relevant discussion.

{{subst:Requested move|new|reason=why|talk=yes}}
Requested move 16 September 2024

Wikipedia:Requested moves → New – why Example (talk) 07:07, 16 September 2024‎ (UTC)[reply]

Survey
Feel free to state your position on the renaming proposal by beginning a new line in this subsection with *'''Support''' or *'''Oppose''', then sign your comment with ~~~~. Since polling is not a substitute for discussion, please explain your reasons, taking into account Wikipedia's policy on article titles.
Discussion
Any additional comments:



This template adds subsections for survey and discussion.
Do not sign this template—this tag is auto-signed when substituted. Be sure to use the subst:
Click the "New Section" tab on the talk page and leave the Subject/headline blank, as the template by default automatically creates the heading.

{{subst:Requested move|new1=x|current2=y|new2=z|reason=why}}
Requested move 16 September 2024

– why Example (talk) 07:07, 16 September 2024 (UTC)[reply]

Do not sign this template—this tag is auto-signed when substituted.
Be sure to use the subst: and place this tag at the beginning of the section containing the relevant discussion.
Add additional related move requests in pairs (|current3= and |new3=, |current4= and |new4=, etc.).

{{subst:Requested move|new1=?|current2=y|new2=?|reason=why}}
Requested move 16 September 2024

– why Example (talk) 07:07, 16 September 2024 (UTC)[reply]


Commenting on a requested move

Shortcut

All editors are welcome to contribute to the discussion regarding a requested page move. There are a number of standards that Wikipedians should practice in such discussions:

  • When editors recommend a course of action, they write Support or Oppose in bold text, which is done by surrounding the word with three single quotes on each side, e.g. '''Support'''.
  • Comments or recommendations are added on a new bulleted line (that is, starting with *) and signed by adding ~~~~ to the end. Responses to another editor are threaded and indented using multiple bullets.
  • The article itself should be reviewed before any recommendation is made; do not base recommendations solely on the information supplied by other editors. It may also help to look at the article's edit history. However, please read the earlier comments and recommendations, as well as prior move requests. They may contain relevant arguments and useful information.
  • Vested interests in the article should be disclosed per Wikipedia:Conflict of interest § How to disclose a COI.

When participating, please consider the following:

  • Editors should make themselves familiar with the article titling policy at Wikipedia:Article titles.
  • Other important guidelines that set forth community norms for article titles include Wikipedia:Disambiguation, specific naming conventions, and the manual of style.
  • The debate is not a vote; please do not make recommendations that are not sustained by arguments.
  • Explain how the proposed article title meets or contravenes policy and guidelines rather than merely stating that it does so.
  • Nomination already implies that the nominator supports the name change, and nominators should refrain from repeating this recommendation on a separate bulleted line.[a]
  • Do not make conflicting recommendations. If you change your mind, use strike-through to retract your previous statement by enclosing it between <s> and </s> after the bullets, and de-bold the struck words, as in "• Support Oppose".

Please remember that reasonable editors will sometimes disagree, but that arguments based in policy, guidelines, and evidence have more weight than unsupported statements. When an editor offers an argument that does not explain how the move request is consistent with policies and guidelines, a reminder to engage in constructive, on-topic discussion may be useful. On the other hand, a pattern of responding to requests with groundless opinion, proof by assertion, and ignoring content guidelines may become disruptive. If a pattern of disruptive behavior persists after efforts are made to correct the situation through dialogue, please consider using a dispute resolution process.

Closing a requested move

Any uninvolved editor in good standing may close a move request. Please read the closing instructions for information on how to close a move request. The Simple guide to closing RM discussions details how to actually close a requested move discussion.

Relisting a requested move

Shortcut

Relisting a discussion moves the request out of the backlog up to the current day in order to encourage further input. The decision to relist a discussion is best left to uninvolved experienced editors upon considering, but declining, to close the discussion. In general, discussions should not be relisted more than once before properly closing.[b] Users relisting a debate which has already been relisted, or relisting a debate with a substantial discussion, should write a short explanation on why they did not consider the debate sufficient to close. While there is no consensus forbidding participation in a requested move discussion after relisting it, many editors consider it an inadvisable form of supervote. If you want to relist a discussion and then participate in it, be prepared to explain why you think it was appropriate.

Relisting should be done using {{subst:RM relist}}, which automatically includes the relister's signature, and which must be placed at the very end of the initial request after the move requester's signature (and subsequent relisters' signatures).

When a relisted discussion reaches a resolution, it may be closed at any time according to the closing instructions; there is no required length of time to wait before closing a relisted discussion.

If discussion has become stale, or it seems that discussion would benefit from more input of editors versed in the subject area, consider more widely publicizing the discussion, such as by notifying WikiProjects of the discussion using the template {{RM notification}}. Banners placed at the top of the talk page hosting the move request can often be used to identify WikiProjects suitable for notification.

Notes

  1. ^ A nominator making a procedural nomination with which they may not agree is free to add a bulleted line explaining their actual position. Additional detail, such as sources, may also be provided in an additional bullet point if its inclusion in the nomination statement would make the statement unwieldy. Please remember that the entire nomination statement appears on the list on this page.
  2. ^ Despite this, discussions are occasionally relisted more than once.

Current discussions

Shortcut
This section lists all requests filed or identified as potentially controversial which are currently under discussion.

This list is also available in a page-link-first format and in table format. 56 discussions have been relisted.

September 16, 2024

  • (Discuss) – Theros Block (Magic: The Gathering) → Theros Block – There is no other "Theros Block" article or topic for which the disambiguation (Magic: The Gathering) is needed as an appendage to the article name. Also, "Theros Block (Magic: The Gathering)" with the parenthetical is not the official name for the content if that is what we wanted to represent, nor is the parenthetical the way that the content is most commonly described when reliable sources or even street usage is discussing the subject. 67.220.13.43 (talk) 13:41, 8 September 2024 (UTC) — Relisting. Reading Beans 04:28, 16 September 2024 (UTC)[reply]

September 15, 2024

  • (Discuss) – The dress → The Dress (meme) – The idea that this article was moved to the current place per WP:DIFFCAPS is flummoxing to me, since media call it both "The dress" and "The Dress" (even numerous sources used in this article), and there is no clear distinction that would allow for it to be a primary topic. The dress should simply be redirected to The Dress. As the article says, "The image became a worldwide Internet meme across social media", so I think (meme) is a valid disambiguation given that the entire phenomenon is centered around the optical illusion created by the image itself. However, I can also support (viral phenomenon) or (Internet phenomenon). ᴢxᴄᴠʙɴᴍ (ᴛ) 20:24, 15 September 2024 (UTC)[reply]
  • (Discuss) – Fredi Beleri → Fredis Beleris – "Fredis Beleris" is the name that Beleris chose to use for himself as proved by the official website of the EU parliament. "Fredi Beleri" is common only in Albania because Albanian authorities systematically removed, and still remove, the "S" from all names of the members of the ethnic Greek Minority, without giving the option to people to choose. Please note that I am not talking about the official name which includes the name "Dionysios". My point is that Fredis Beleris is a person who should be called with the name he chose and not with an incorrect name that is enforced in Albanian documents although Beleris has already made effort to write his name in a different way in the Greek documents. Beleris is neither a town nor a mountain so that wikipedia calls him with the name other people chose for him. Beleris is a human and became popular because he aims at protecting the violation of human rights of the ethnic Greek Minority in Albania, and "being called" with his correct name is one of them. In Beleris' case, the official name in Greece and EU matches the one he uses for himself, so there is no doubt about official versus common. The only doubt is about using a name enforced by Albanian authorities 50 years ago or accepting the name he likes for himslef. Open Free Eye (talk) 18:35, 15 September 2024 (UTC)[reply]
  • (Discuss) – Pornography laws by region → Restrictions on pornography – Someone may have a better idea for a rename, so I'm seeking input. The current formulation — "laws" – is not sufficiently precise (WP:PRECISION), limiting the scope of addressing, in addition to "laws" in the sense of de jure aspects, also the enforcement situation by governments. For instance, South Korea is listed in the table as a country where production and distribution are prohibited, but appears nonetheless green in the accompanying map; China does not formally criminalise possession, yet there was a controversial 2002 incident of police breaking into a couple's home whilst they watched pornography, fining and jailing them (article in Chinese); in Egypt, there have been some statements by courts and prosecutors following the growth of Islamist politics in the immediate aftermath of the 2011 revolution, yet internet pornography is not blocked, unlike in some other Arab countries. Clearly, the article has been — and should be better — addressing both the de jure and quasi-legal situations. The present title yields undesired ambiguity. Similar Wikipedia titles include Restrictions on TikTok in the United States and Restrictions on cell phone use while driving in the United States. It would make little sense to prefer e.g. "Legality of TikTok"/"Laws on TikTok in the United States" over its present title. Y. Dongchen (talk) 13:57, 15 September 2024 (UTC)[reply]
  • (Discuss) – Tropical Storm Conson (2021) → Tropical Storm Conson – Can this page be moved to just Tropical Storm Conson? As Daniel boxs stated above, the name was retired after the 2021 Pacific typhoon season. While there was a more notable iteration of Conson last 2010, it was a typhoon. This is the only page that is named "Tropical Storm Conson"— the 2004 and 2010 iterations were typhoons, and the 2016 iteration redirects you to the 2016 typhoon page, so it's a little distinctive compared to the previous Conson iterations. Bugnawfang (talk) 08:28, 8 September 2024 (UTC) Bugnawfang (talk) 08:32, 8 September 2024 (UTC) — Relisting. Bobby Cohn (talk) 12:27, 15 September 2024 (UTC)[reply]
  • (Discuss) – Tropical Storm Kompasu (2021) → Tropical Storm Kompasu – This is the worst incarnation of "Kompasu" out of the four times the name had been used, with 15 more deaths than its 2010 usage. The 2004 and 2016 tropical storms were also insignificant, for that matter; clicking on these links will redirect you to the years' Pacific typhoon season pages. I'd say this page shouldn't have the year in it; when Kompasu formed 3 years ago, it was very large and caused extensive flooding across PH, too. This incarnation was clearly more notable. Bugnawfang (talk) 11:32, 15 September 2024 (UTC)[reply]
  • (Discuss) – 2019 El Paso shooting → 2019 El Paso Walmart shooting – Per WP:UCRN. Though at the time of the shooting (around 2019) the shooting was more commonly referred to as something in the vein of "El Paso shooting" by reliable sources, in recent years reliable sources trend towards calling it something akin to "El Paso Walmart shooting". Out of 50 articles published since 2020 about the incident, 42 mention Walmart in the title while 8 do not. The 'Walmart' aspect appears to be part of a commonly recognised naming convention, which should be reflected in the page's title. Reliable sources that tended to include 'Walmart' in their titles include CNN, PBS, BBC News, ABC News, AP News, The Independent, the Washington Post, NBC News and others. Local news sources, such as the Texas Tribune and El Paso Times, tended to also refer to 'Walmart' in their titles. I recommend '2019 El Paso Walmart shooting' as it fits other naming conventions. If needed, I can provide several of the referenced articles, though they can be found by Google search. Macxcxz (talk) 11:02, 15 September 2024 (UTC)[reply]

September 14, 2024

  • (Discuss) – Eric XI of Sweden → Erik Eriksson (king) – The WP:COMMONNAME for this king is "Erik Eriksson". * Ngram shows that Erik Eriksson has been more common in the literature since 1910 or so. However, "Erik Eriksson" is also a common name for other people, so the full curve for "Erik Eriksson" cannot be attributed to the king. The decline in the use of "Eric XI" is more clear. * Reliable sources usually use the name Erik Eriksson. See e.g. GBooks search for Erik+1222+1250. Typical example is the Cambridge History of Scandinavia. Britannica does not have a dedicated page for him, but the "Learn more page" is titled Erik Eriksson. *There are a lot of other Erik Erikssons (dab page), and the king is not the primary topic. For disambiguation, I suggest the parenthetical disambiguation, which would be a concise choice. I don't believe our hands are tied very strongly by WP:NCROY here since its applicability to medieval Sweden is somewhat dubious. These patronymic names are not of the "common stock", and Sweden was not a hereditary monarchy at the time. — Jähmefyysikko (talk) 04:50, 31 August 2024 (UTC) — Relisting. Extraordinary Writ (talk) 06:44, 7 September 2024 (UTC) — Relisting. Reading Beans 11:19, 14 September 2024 (UTC)[reply]
  • (Discuss) – Willem II (football club) → Willem II Tilburg – Per WP:NATURAL: Using an alternative name that the subject is also commonly called in English reliable sources, albeit not as commonly as the preferred-but-ambiguous title, is sometimes preferred. As the football cannot be located at the title Willem II, it would be better to use natural disambiguation over parenthetical. The official name of the club is "Willem II Tilburg BV" (source), and English-language media and sport websites often use this as an alternative name for the club (examples: Telegraph, Sky Sports, The Guardian, BBC, Eurosport, FourFourTwo, TNT Sports, UEFA). The club uses it on their social media as well (Instagram, Facebook). I'm not saying "Willem II Tilburg" is the common name (links can still be piped to display "Willem II" on other articles), but the name is preferable to a parenthetical disambiguation. S.A. Julio (talk) 06:49, 14 September 2024 (UTC)[reply]

September 13, 2024

  • (Discuss) – Flood control → Flood management – A researcher has informed me that the terminology in this article around flood control and flood mitigation is incorrect. It's a confusing matter as these terms are often used interchangably, but they are in fact distinct. I'll be making some edits soon in an attempt to resolve this - apparently flood control is technically more about physical barriers to directly manage flood water while flood mitigation encompasses both flood control measures (physical barriers) as well as non-structural aspects like flood insurance, flood prediction, etc. I proposed this article "Flood control" is moved to "Flood management" as a more general term which would encompass flood control and flood mitigation as well as flood risk management etc. (See also Wang et al., 2020). TatjanaClimate (talk) 14:20, 30 August 2024 (UTC) — Relisting. SilverLocust 💬 21:49, 13 September 2024 (UTC)[reply]
  • (Discuss) – Eryholme–Richmond branch line → ? – Either Richmond branch or Richmond branch line – The line does not have any reliable references calling it Eryholme–Richmond branch line. Plenty of Mirrors and those who have used the name of the article in their webpages.[1][2] The railway was built in 1845 when the junction with the East Coast Main Line was Dalton Junction. This was re-named in 1901 to Eryholme Junction,[3] so by way of comparison, for the first 56 years of its existence, it would not have been called the Eryholme–Richmond branch line. There are different names, but those that state just Richmond branch with a lower case 'b' are: *[4][5][6][7][8][9][10][11][12][13] The North Eastern Railway Civil Engineering Drawings List held at the National Railway Museum, has 22 references to Richmond, 17 of which state Richmond Branch (both capitalised), and others stating Richmond to Darlington, or Richmond to Eryholme.[14] *Just Richmond Branch Railway:[15][12] *Hansard refers to the the line when it was under threat of closure as the Darlington–Richmond Line.[16] Regards. The joy of all things (talk) 21:17, 13 September 2024 (UTC)[reply]
  • (Discuss) – Yeh Shuhua → Shuhua – Proposing moving the above pages from their current full names to their mononym as per WP:COMMONNAME. The subjects of the above articles are most commonly known mononomously as their given name and have never used their full name in any professional capacity. Additionally, it is unnecessary to disambiguate these articles by using their family names because there are no other mononymous singers with Wikipedia articles that share those same given names. For Cho Mi-yeon, Jeon So-yeon, and Soojin (singer), the articles with the new names currently exist but are simply redirects to the disambiguation page for people that use the hyphenated version of that name (ex. Soyeon redirects to So-yeon). However, none of the people on those disambiguation pages are specifically commonly known without the hyphen except for the people included in this move request. I believe the best course of action here would be to include a note at the top of the articles saying, for example: "This article is about the singer. For other people with this name, see So-yeon" RachelTensions (talk) 17:57, 13 September 2024 (UTC)[reply]
  • (Discuss) – Kim Woo-jin → Kim Woojin – Move from Kim Woo-jin to Kim Woojin per WP:COMMONNAME. While on paper the official romanization of his name is "Kim Woo-jin", Kim has never used a hyphen in his name professionally and has never been commonly referred to that way. Kim is most commonly known as either "Kim Woojin" or, during his period with Stray Kids, mononymously as just "Woojin". Proposing removing the hyphen from article title to properly reflect the most common way Kim's name is presented. RachelTensions (talk) 15:44, 13 September 2024 (UTC)[reply]

September 12, 2024

  • (Discuss) – Moggy → Domestic cat (landrace) – Wikipedia is a worldwide resource. Cats are found worldwide. There is no place for a localized colloquialism to be a MAIN page reference on Wikipedia. I am located in the United States and never once have I ever heard the term “moggy” used to refer to a cat. The merging of Domestic short-haired cat and Domestic long-haired cat was an appropriate move as the only difference is the gene for hair growth. However, I don’t understand why a slang term page was revived from like, 2007 to merge the two pages together. Wikipedia Manual of Style in the Opportunities for Commonality section states that as an international English-speaking Wikipedia, using universally accepted terms is much more appropriate. For example, “to mog” or “mogging” in Gen Alpha terms - see mog. Nobody outside of Britian or Australia even knows what a moggy is. To make things messier, there were previous merges and fights about “moggy” vs. “moggie.” Y’all do not need a page for your local colloquialism. Wikipedia:Manual of Style#Opportunities for commonality bullet points 1-4. My new write-up for the beginning of the new article also explains this landrace breed, using hyphenation glossing as is suggested by the Manual of Style: A Domestic shorthair or Domestic longhair cat, sometimes regionally referred to as a moggy, is a landrace breed of cat reproducing without human intervention for type. The vast majority of cats worldwide lack any pedigree ancestry. The landrace can include cats living with humans or in feral colonies. Gene flow moves between the two populations as feral cats are tamed, housecats are released, and free-roaming unneutered cats breed freely. Simmy27star (talk) 11:37, 4 September 2024 (UTC) — Relisting.  ASUKITE 16:03, 12 September 2024 (UTC)[reply]
  • (Discuss) – Springfield, Ohio cat-eating hoax → Springfield, Ohio, cat-eating rumor – – Per WP:NDESC and WP:RS. Reliable secondary sources predominantly describe this topic as a "claim", "rumor", or "conspiracy theory" rather than a hoax, and describe it as baseless or unsubstantiated rather than false. (As I write this, the only major WP:RSPSS I've found describing it as a "hoax" is New York.) Although the definitions of "hoax" and "rumor" overlap to some degree, the word "hoax" insinuates a deliberate and malicious trick, and the supposed event has not been and potentially may never be definitively proven as such. Per my older edition of Webster's New Collegiate Dictionary, one definition of "rumor" is "a statement or report current without known authority for its truth", which I think summarizes the topic better than "claim" or "conspiracy theory". Carguychris (talk) 14:09, 12 September 2024 (UTC)[reply]
  • (Discuss) – Whitewashing (censorship) → Whitewashing (propaganda) – It's not a censorship practice, which is a direct suppression of material, usually by force or threat of force by some entity with power such as a government. It's a propaganda or public relations practice, and that is what the article talks about. Whitewashing is pretty closely related to spin (propaganda) really. "Whitewashing (coverup)" would be reasonable too maybe, and sugarcoat, launder, excuse, and other terms could be in play too; there's no one perfect term, but it says here that "Whitewashing (propaganda)" is the best term. Herostratus (talk) 04:00, 12 September 2024 (UTC)[reply]
  • (Discuss) – Gyat → Gyatt – "Gyatt" is potentially the more common spelling, at least in my experience online (The provided sources seem split). The disambiguation page currently present at "Gyatt" contains an alternate spelling for guyot that is unsourced and mentioned nowhere on the target article. "Gyat" could merge to "Gyatt", guyot should be removed, and the USS Gyatt linking should be a note at the top. DrewieStewie (talk) 02:24, 12 September 2024 (UTC)[reply]

September 11, 2024

  • (Discuss) – One-wall handball → Wallball – Wallball is the name now used by most of the major organisations involved in governing the sport in countries across the globe, such as GAA Handball, UK Wallball, the United States Handball Association etc - they have moved away from referring to the game as 'one-wall handball', instead using the name 'Wallball' for the sport. N.B. the United States Handball Association (USHA) uses both names albeit they are used for two different codes of American handball - they use the name 'One-wall handball' to describe the code played with the smaller, harder rubber ball normally used in the four-wall code of American handball and the name 'Wallball' to refer to the game played with the bigger, softer rubber ball, very similar to a racquetball, that this article talks about. The name 'Wallball' was also introduced by the organisations above, to differentiate itself from the game of handball currently played in the Olympics, that is similar to the sport of soccer, but played with one's hands. Indeed a few weeks ago, the World Wallball Championships took place in Limerick, Ireland, with 13 countries taking part, as can be seen in the name of the event itself, being 'World Wallball Championships' rather than 'World One-wall Handball Championships', as it used to be called. Rhubarb500 (talk) 18:25, 1 September 2024 (UTC) — Relisting. SilverLocust 💬 05:59, 11 September 2024 (UTC)[reply]

September 10, 2024

  • (Discuss) – Transnistria → Pridnestrovie – In connection with the new laws adopted in the Republic of Pridnestrovie regarding the names of this state, the need to rename this article has become obvious. Let me remind you that the Parliament of Pridnestrovie amendments adopted to the laws, according to which the use of the term "Transnistria" in relation to Pridnestrovie entails arrest for up to 15 days with possible reclassification under a criminal article. The reason is that the word "Transnistria" is extremely offensive to the people of Pridnestrovie and has repeatedly become a cause of conflicts. In general terms, this is interpreted as a wish for genocide to Pridnestrovians. The current title of the article is absolutely incorrect. WP:COMMONNAME in this case cannot justify it, since the overwhelming majority of cases of using the term Transnistria in English-language texts refers either to the administrative division of Moldova (the autonomous entity Stinga Nistrului), or to the so-called territory of the left bank of the Dniester not controlled by Chisinau ("breakaway region of Moldova"), but not to the Pridnestrovian Republic, which is described in this article. Such naming is, apparently, an invention exclusively of Wikipedia. There is not a single Wikipedia article about a geographical or political entity whose name directly offends its population or would be prohibited by law in this country, except for this one. It would be absurd to leave an article with such a name. I would also like to remind you that the article about the former Nagorno-Karabakh Republic was renamed Republic of Artsakh following a referendum in that republic, although the old name was unconditionally dominant in all non-Armenian texts and was not offensive at all. This did not meet with any objections in Wikipedia community. Of course, this cannot be a precedent, and we must be guided by the rules, however, in the case of the term "Transnistria", apparently, there is a circle of interested parties defending this absurd vicious practice in their own political interests (WP:POV). This also needs to be paid attention to. The following suggestions: # Rename the article Transnistria to Pridnestrovie. # On the Transnistria page, put a template about a polysemantic term and list the articles it may refer to: Stinga Nistrului, Transnistria Governorate, Pridnestrovie, etc. Why "Pridnestrovie" and not "Pridnestrovian Moldavian Republic"? According to WP:OFFICIALNAMES and for the same reasons that articles are called "Moldova" and not "Republic of Moldova", "Russia" and not "Russian Federation", etc. Links: *The presidential initiative on the inadmissibility of using the term "transnistria" in relation to Pridnestrovie was adopted unanimously *Transnistria must be vanished  :2A03:F680:FE04:45D2:2C72:43DD:63F1:682C (talk) 11:03, 10 September 2024 (UTC)[reply]

September 9, 2024

  • (Discuss) – Macedonia (ancient kingdom) → Kingdom of Macedonia – Per WP:NCDAB, there's every reason for this page to be at the naturally disambiguated title of "Kingdom of Macedonia" – a title for which this page is the unambiguous primary topic (it redirects here) – and very little reason for it to have a parenthetically disambiguated title given that the naturally disamiguated title exists. There was a previous RM on this, but it appears to have overlooked both the preference towards natural disamiguatiom at WP:NCDAB and modern usage patterns, with the Wikinav chart of the undisambiguated base term showing the vast gulf between traffic to North Macedonia versus any other "Macedonia". It is the same in page views. The proposed term is also abundant in scholarship. Given all of this context, and the reality that the current title is in any case tantamount to "Macedonia (kingdom of)", we may as well just flip the title and remove the brackets. Iskandar323 (talk) 20:41, 9 September 2024 (UTC)[reply]
  • (Discuss) – Wi-Fi 6 → IEEE 802.11ax – So this article was moved to the Wi-Fi 6 title in 2021, citing WP:COMMONNAME. However, all the other Wi-Fi articles (Wi-Fi 7, Wi-Fi 8, Wi-Fi 5) use the IEEE technical name, rather than the "Wi-Fi x" marketing name. Thus I suggest moving this article to IEEE 802.11ax (without the "-2021" at the end, as it's not needed - WP:CONCISE; also the later articles don't have "-year" in the title either) to be WP:CONSISTENT with all these other Wi-Fi articles that are titled under the IEEE name. I'd say No one but advanced experts in this field would be searching for this article by its IEEE number, nor know what this article is about from its IEEE number. (from the previous RM) is not much of an issue anymore, as these Wi-Fi articles all now have a neat navigational template at the top clearly showing the "Wi-Fi x" marketing designations of each IEEE WLAN standard. Also, that's what redirects are for. — AP 499D25 (talk) 10:06, 29 August 2024 (UTC) — Relisting. ModernDayTrilobite (talk • contribs) 18:38, 9 September 2024 (UTC)[reply]

Elapsed listings

Shortcut
The 7-day listing period has elapsed. Items below may be closed if there's a consensus, or if discussion has run its course and consensus could not be achieved.

Backlog

Shortcut
Elapsed listings fall into the backlog after 24 hours. Consider relisting 8-day-old discussions with minimal participation.
  • (Discuss) – Altaic languages → Altaic hypothesis – Per above This article has been a constant struggle to get the academic consensus to be the focus of the article, particularly in light of many people simply not realizing the Altaic hypothesis isn't actually widely accepted as fact. "Altaic hypothesis" is heavily used in the literature (i.e. here) and allows us to differentiate the sprachbund and language family arguments more clearly in the body of the article. It also means someone looking up the topic on Wikipedia who isn't familiar with it isn't going to be met with the same heading we use for language families followed up immediately by a statement that it isn't likely a genetic language family. Warrenᚋᚐᚊᚔ 09:27, 4 September 2024 (UTC)[reply]
  • (Discuss) – 2023 Hamas-led attack on Israel → 7 October Hamas-led attack on Israel – I believe that enough time has passed since the last RM (which proposed the simpler "7 October attacks" name and closed with consensus to retain the current title) to re-propose a title change for this article. I believe that "7 October Hamas-led attack on Israel" is the WP:COMMONNAME for this event, as seen in sources such as: * Al Jazeera: "... counter the October 7 Hamas-led attack on Israel, which saw ..." * Bloomberg: "... trapped in Gaza since the Oct. 7 Hamas-led attack on Israel, which prompted ..." * CBC: "... around the world since the Hamas-led attacks on Israel of Oct. 7 but are now ..." * CNN: "... from the October 7 Hamas-led attack on Israel being held ..." * Euracitiv: "... triggered by the 7 October Hamas-led attack on Israel in which ..." * France24: "Before the October 7 Hamas-led attack on Israel that triggered ..." * ISW: "... spokesperson claimed that the October 7 Hamas-led attack on Israel was retaliation ..." * Middle East Eye: "Following the 7 October Hamas-led attack on Israel and subsequent ..." * NPR: "... Palestinian armed groups since the Oct. 7 Hamas-led attack on Israel that set off the war ..." * NYTimes: "... including some who participated in the Oct. 7 Hamas-led attack on Israel, and that ..." * Reuters: "... were involved in the Oct. 7 Hamas-led attack on Israel that precipitated ..." * Times of Israel: "... during and after the October 7 Hamas-led attack on Israel." * The Conversation: "... participated in the October 7 Hamas-led attack on Israel, which resulted ... " * WaPo: "Since the Oct. 7 Hamas-led attack on Israel, restrictions have ..." Many sources simply say "7 October" or "October 7 attacks" instead of spelling out the full name, but I believe that while "7 October attacks" could be a more COMMON name, I think that it fails WP:AT#Precision in favor of "7 October Hamas-led attack on Israel." DecafPotato (talk) 00:43, 15 June 2024 (UTC) — Relisting.  — Amakuru (talk) 14:09, 9 July 2024 (UTC) — Relisting. FOARP (talk) 07:27, 3 September 2024 (UTC)[reply]
  • (Discuss) – Sloboda → Sloboda (settlement) – Everything I said three months ago in #Requested move 22 May 2024 still holds, we just had so little interest. In summary, there is no primary topic here. I believe I addressed the sole complaint. Here's hoping we'll get more people to read this now. In the meantime, the usage statistics continue to show the same picture of a lack of a primary topic, the topics most commonly navigated to are consistently not about the settlement meaning.
    Clickstreams from the last three months

From meta:Research:Wikipedia clickstream: :clickstream-enwiki-2024-05.tsv:  :* Sloboda Sloboda_Ukraine link 28  :* Sloboda Sloboda_(disambiguation) link 12  :* Sloboda Boyar link 12  :* total: 52 to 3 identified destinations :clickstream-enwiki-2024-06.tsv:  :* Sloboda Sloboda_Ukraine link 32  :* Sloboda Sloboda_(disambiguation) link 12  :* Sloboda Boyar link 12  :* total: 56 to 3 identified destinations :clickstream-enwiki-2024-07.tsv:  :* Sloboda Sloboda_(disambiguation) link 17  :* Sloboda Sloboda_Ukraine link 16  :* Sloboda Boyar link 13  :* total: 46 to 3 identified destinations Even if we're unsure, I say we should move it and then do the same measurements again later, and see if reader behavior indicates we need to keep or revert. -- Joy (talk) 08:14, 24 August 2024 (UTC) — Relisting. BilledMammal (talk) 07:10, 1 September 2024 (UTC)[reply]

  • (Discuss) – Sophia Howe → Sophia Waller, 2nd Baroness Howe –

    DrKay and I have found ourselves in disagreement over the title of this article. At creation, this article was named like it currently is: Sophia Howe. Since she was a peeress suo jure (having inherited the barony from her father), I moved the article to Sophia Howe, 2nd Baroness Howe, which is generally the format for articles on peers – unless they disclaim the title, or don't use it (like for instance author Nicholas Mosley). DrKay moved it back to Sophia Howe with the comment Remove unnecessary parentheses/disambiguator: mismatch of her maiden name and a title she inherited after her marriage. I can buy that her surname wasn't Howe when she inherited the barony, but I find it peculiar that DrKay nevertheless kept it, while removing the title, which was correct. It seems to me that it flies in the face of his own edit summary. As I said, I totally buy that her surname wasn't Howe when she inherited the barony, so I then moved the article to Sophia Waller, 2nd Baroness Howe; Waller being her surname when she inherited the title. DrKay has now moved the article back to Sophia Howe again, with the edit summary bizarre use of unknown surname! What's bizarre?, I ask. DrKay complains the Howe wasn't her surname when she inherited the title, I move it to the surname that she had when she inherited the title, and DrKay moves it back again (never mind referring to WP:RMUM after they have done it themselves ... ). I don't know if anyone is move-warring here, but if so, it certainly isn't me. I have acted in good faith. So, what should the article title be? # Sophia Howe (with or without "2nd Baroness Howe"), this lastname is her maiden name. # Sophia Curzon (with or without "2nd Baroness Howe"), this is the lastname from her 1st husband. # Sophia Curzon-Howe (with or without "2nd Baroness Howe"), #1 and #2 combined, which is what her son, who inherited the barony from her, chose. # Sophia Waller (with or without "2nd Baroness Howe"), this is the lastname from her 2nd husband. Vote 1a, 1b, 2a, 2b, etc, with a=with "2nd Baroness Howe", and b=without the title. My vote is 4a.

    HandsomeFella (talk) 18:44, 29 August 2024 (UTC)[reply]

Malformed requests

See "Bot considerations"

Possibly incomplete requests

See "Request all associated moves explicitly"

References

References generally should not appear here. Use {{reflist-talk}} in the talk page section with the requested move to show references there.
  1. ^ "Eryholme–Richmond branch line". TriplyDB: The Network Effect for Your Data. Retrieved 13 September 2024.
  2. ^ "A Walk to Easby Abbey » Two Dogs and an Awning". Two Dogs and an Awning. 2 October 2015. Retrieved 13 September 2024.
  3. ^ Hoole, Kenneth (1985). Railway stations of the North East. Newton Abbot: David and Charles. p. 65. ISBN 0-7153-8527-5.
  4. ^ Body, Geoffrey (1989). Railways of the Eastern Region volume 2. Wellingborough: Patrick Stephens. p. 68. ISBN 1-85260-072-1.
  5. ^ Haigh, A. (1979). Yorkshire railways: including Cleveland and Humberside. Clapham: Dalesman Books. p. 24. ISBN 0-85206-553-1.
  6. ^ Young, Alan (2015). Lost stations of Yorkshire; the North and East Ridings. Kettering: Silver Link. p. 33. ISBN 978-1-85794-453-2.
  7. ^ Hoole, Kenneth (1985). Railway stations of the North East. Newton Abbot: David and Charles. p. 48. ISBN 0-7153-8527-5.
  8. ^ Suggitt, Gordon (2007). Lost railways of North and East Yorkshire. Newbury: Countryside Books. p. 46. ISBN 978-1-85306-918-5.
  9. ^ Burgess, Neil (2011). The Lost Railway's of Yorkshire's North Riding. Catrine: Stenlake. p. 13. ISBN 9781840335552.
  10. ^ Blakemore, Michael (2005). Railways of the Yorkshire Dales. Ilkley: Great Northern. p. 54. ISBN 1-905080-03-4.
  11. ^ "RID mileages". railwaycodes.org.uk. Retrieved 13 September 2024.
  12. ^ a b Lloyd, Chris (1 July 2017). "90 years ago three million people headed north by rail to witness one of the biggest events of the year - a total eclipse of the sun". The Northern Echo. Retrieved 13 September 2024.
  13. ^ Shannon, Paul (2023). Branch Line Britain. Barnsley: Pen & Sword. p. 127. ISBN 978-1-39908-990-6.
  14. ^ "North Eastern Railway Civil Engineering Drawings List" (PDF). railwaymuseum.org.uk. Retrieved 13 September 2024. Various pages - use the search function for Richmond
  15. ^ "List of North Yorkshire & North Riding plans of railway lines..." (PDF). archivesunlocked.northyorks.gov.uk. p. 5. Retrieved 13 September 2024.
  16. ^ "Darlington-Richmond Line (Closure) Volume 774: debated on Wednesday 4 December 1968". hansard.parliament.uk. Retrieved 13 September 2024.

See also

The current Wikipedia time is:
07:07, Monday, 16 September 2024 (UTC)
To update time purge the cache!
    Retrieved from "https://en.wikipedia.org/w/index.php?title=Wikipedia:Requested_moves&oldid=1243705348"