Misplaced Pages

talk:Requested moves: Difference between revisions - Misplaced Pages

Article snapshot taken from Wikipedia with creative commons attribution-sharealike license. Give it a read and then ask your questions in the chat. We can research this topic together.
Browse history interactively← Previous editContent deleted Content addedVisualWikitext
Revision as of 15:23, 15 October 2005 editPBS (talk | contribs)Autopatrolled116,854 edits →Should Current notices be in a sub page← Previous edit Latest revision as of 13:02, 24 December 2024 edit undoBagumba (talk | contribs)Autopatrolled, Administrators173,917 edits →Request: Implement a form for requests at WP:RM/TR: ReplyTag: Reply 
Line 1: Line 1:
{{talkheader|wp=yes|noarchive=yes|search=no|shortcut=|WT:RM}}
==Archives==
{{tmbox|text='''NOTE:''' This is '''not''' the place to request moves.</big> Please follow the instructions given on the ]. If you seek instruction on closing existing requests, please see the ].}}
* ]
{{notice|1=Please use the ''']''' process for contested move request closes.}}
* ]
* ] {{central|text=most subpages of ] that are unused have talk pages that redirect here.}}
{{old moves
* ]
| list =
*RM, WP:Requested moves → WP:Proposed moves, '''No consensus''', ]
*RM, WP:Requested moves → WP:Proposed moves, '''Not moved''', ]
*RM, WP:Requested moves → WP:Articles for renaming, '''Not moved''', ]
*RM, WP:Requested moves → WP:Requested title changes, '''Not moved''', ]
}}
<!-- {{bots|allow=Cluebot III,MiszaBot I,MiszaBot II}} -->
<inputbox>
type=search
namespaces=Talk
break=no
default=insource:move intitle:
searchbuttonlabel=Search for "move"
</inputbox>
<inputbox>
type=search
namespaces=Talk
break=no
default=insource:"requested move" intitle:
searchbuttonlabel=Search for "requested move"
</inputbox>
{{center|Enter the title (or part of a title) to search for after "intitle:", then click "search"}}
{{center|Try other variants (e.g. "move discussion") to broaden or narrow your search}}


{{archive box|search=yes|bot=lowercase sigmabot III|age=30|index=/Archive index|auto=short|
For the page history of any text before this time stamp please see the Archives ] 16:36, 29 August 2005 (UTC)
*] (2005)
*For why RM was created, see:
**]
{{cot|Archives by date|bg=#e0d2a3|bg2=#f8eabb}}
#]
#]
#]
#]
#]
#]
#]
#]
#]
#]
#]
#]
#]
#]
#]
#]
#]
#]
#]
#]
#]
#]
#]
#]
#]
#]
#]
#]
#]
#]
#]
#]
#]
#]
#]
#]
{{cob}}
}}
{{User:MiszaBot/config
|archiveheader = {{Automatic archive navigator}}
|maxarchivesize = 225K
|counter = 36
|minthreadsleft = 5
|algo = old(30d)
|archive = Misplaced Pages talk:Requested moves/Archive %(counter)d
}}{{User:HBC Archive Indexerbot/OptIn
|target=/Archive index
|mask=/Archive <#>
|leading_zeros=0
|indexhere=yes}}


== Move the article of ] to ] ==
==Footnote regarding the correct implementation of approval voting==


I want to move the article based on the Chinese name format where the surname placed first. In motorsport, he always called by Yifei Ye than Ye Yifei, but to make it consistent with other Chinese figures, and people his name has to be Ye Yifei. It's not Zedong Mao, it's Mao Zedong for example. Hope someone can accepts the changes. Thank you. ] (]) 06:37, 21 November 2024 (UTC)
I do not think it is necessary.
:{{u|Thfeeder}}, please see ] for how to start a move request at the article's talk page. ] (]) 13:10, 23 November 2024 (UTC)
* Because if there are only two options by far the most common then the 60% rule is enough.
* I think the wording above is very confusing. This idea that a bank proposal should be added does not make sense to me.
* Details of how approval voting is done is coverd by the link to that page. It does not have to be duplicated possibly incorrectly on this page ] 11:48, 25 August 2005 (UTC)


== Overcomplication ==
Of course the footnote is necessary, while preventing people to try and steer votes like you did on ]. No offense intended, I can perfectly see this happened in good faith. Why I'm nonetheless defending correct application of the procedure as it was fixed after long, and not always easy, debate above, is that a wishy-washy application of the procedure will probably (as usual) not be able to come nearer to a solution accepted by many parties over a longer period of time. And is that not what we want most? Or is this really about trying to prove ''right'' whatever the cost? I'd really think sorry you'd lose your taste for wikipedia over that in the end, while, indeed, I'd think that the consequence of not trying to solve issues by a ''consensus'' type of approach. --] 12:32, 25 August 2005 (UTC)


Making move requests is way too overcomplicated, this page should be handled like the protection request page. ] (]) 18:01, 24 November 2024 (UTC)
== Polling for requested page move ==
*Protections aren't generally controversial, so the format isn't very useful for something that typically requires debate. There is ] for uncomplicated moves that no one will object to. ] (]) 16:49, 25 November 2024 (UTC)
*:What I mean is that there isn't an "add topic" button or something like this on this page, unlike the protection request page, you would have to edit the page manually, which you can't do as an IP user, because this page is semi-protected. ] (]) 18:46, 25 November 2024 (UTC)
**:There is no reason to edit it. ] has no protection. Regular RMs are made on article talk pages and transcribed here. ] (]) 18:50, 25 November 2024 (UTC)
**::I mean the move request page, not ]. ] (]) 19:46, 25 November 2024 (UTC)
**:::Do you find using a single template on the talk page of an article difficult? See ] -- there is only two parameters: the requested new name and your reason. ]&thinsp;] 21:01, 25 November 2024 (UTC)
**::::But you still need to edit this page, there is no "add topic" button even though there should be one. ] (]) 12:54, 26 November 2024 (UTC)
**:::::As ] stated, they are very different applications, used in different places. The "add topic" is used on the ] page, and that discussion is not included on the article talk page -- its not necessary since it is specifically "discussed on the article talk page". However, by contrast, regular moves are discussed on the talk page, so a simple button on the ] would be impossible to work currently, as it would require backend changes to the Mediawiki software or requiring people to otherwise run untrusted Javascript. However, an example of a tool talk might help you specifically is to look over at ] and make a request on that talk page. That is a tool that would add an extra navigation tab at the top of your browser that would let you do RMs when viewing the article itself. ]&thinsp;] 19:24, 26 November 2024 (UTC)


== Move cleanup ==
:See ] for the previous discussion on this issue.


{{section link|Misplaced Pages:Requested_moves/Closing_instructions#Cleaning_up_after_the_move}} reads: {{tq2|You should not close any move if you are unwilling to do the necessary clean up tasks described at ]}} Maybe I just more notice and remember the cases where this isn't done, but to what extent does the community consider this a closer requirement versus some ] laundry list that anyone can volunteer to do, not necessarily the closer. I'm trying to have the proper perspective on this. —] (]) 04:25, 27 November 2024 (UTC)
:Kim Bruning edited WP:RM removing the votes line in the "Create a place for discussion" on the talk page so leaving only one section.I presume under the noble wikipedia idea ]. With only a discussion section recommended one of the first controversial pages formatted this way became confusing. See the history of ] ]


:The line is pretty clear, if an editor wants to close a move, they should be willing to do the postmove cleanup, such as fixing bypass redirects in templates or retargeting links and cleaning up leads.
Ohkay, if you have to, but people had added a poll that wasn't according to polling guidelines. Actually are you sure you want to normally have a poll there by default? That's kinda broken. ] 16:23, 29 August 2005 (UTC)
:The only general exception I'd see to that is if some editors in the discussion have volunteered preemptively that they will do some of the cleanup if it's not just ordinary cleanup. Like say an alternative result of a split or so that requires more than routine cleanup. ] (]) 04:34, 27 November 2024 (UTC)
:My perspective has been that editors should avoid closing articles if they cannot complete the task within a reasonable amount of time, say an hour or so. The exception to this that I can think of have been in RMnac situations where sometimes an experienced editor can perform most (but not all) of the necessary close steps (such as a delay such as waiting for a CSD to make room) or they might be closing the discussion, and then asking requesting a technical move, etc. But in these cases, they should be monitoring for those changes to take place and promptly go about finishing up any cleanup work, which I'd AGF and gracefully give many hours (but not multiple days) for this to be accomplished (e.g. an Admin performs their action while the closer is now asleep). However, at this point, I would say it would be acceptable for another experienced editor to jump in and help out as well with wrapping up the cleanup tasks. However, if any RM closer is consistently dropping the ball with regards to cleanup tasks, do AGF and use their talk page. ]&thinsp;] 08:55, 27 November 2024 (UTC)
::{{tq|However, at this point, I would say it would be acceptable for another experienced editor to jump in and help out as well with wrapping up the cleanup tasks|q=yes}}: Yeah, I'm sure nobody would mind if a non-closer volunteers to help cleanup. But my original question was about the expectation of closers to cleanup their moves, such as old titles that got usurped or links in navboxes. —] (]) 13:21, 27 November 2024 (UTC)
:::Right, I think my initial statement that if you cannot commit to doing the cleanup tasks, then you should avoid closing an RM. ]&thinsp;] 05:44, 4 December 2024 (UTC)


== Participating in a RM after relisting ==
In my opinion, Support-Oppose is a good guideline, rather than looser guidelines. But the wording could be changed, e.g "vote -> opinion". I'll make such example (and if you are dissatisfied, you of course reverse). ] 16:40, 29 August 2005 (UTC)


These texts don't seem to align:
<div style="font-name:arial;background-color:#eeeeee;width:480px;margin:0px 0px 0px 10px;float:none;border:1px solid #888888;padding:10px">
<nowiki>==Requested move==</nowiki>


*] - "While there is no consensus forbidding participation in a requested move discussion after relisting it, many editors consider it an inadvisable form of supervote."
''<nowiki>The reasons for move copied from the entry on the ] page</nowiki>''<br>
<nowiki>===Polling===</nowiki><br>
<nowiki>:''Add *'''Support''' or *'''Oppose''' followed by an explanation of your opinion, then sign your opinion with &lt;nowiki&gt;~~~~&lt;/nowiki&gt;''</nowiki>
<nowiki>===Discussion===</nowiki><br>
<nowiki>:''Add any additional comments''</nowiki>
</div>


*] - "A relister may later become a participant or closer in the requested move discussion or survey."
: Almost agree, I changed it above for you. The explanation must not be optional, and preferably should actually be longer than one sentence. :-) ] 16:53, 29 August 2005 (UTC)


Should either or both be removed/changed to become aligned on whether participating in an RM after relisting is allowed/not allowed/encouraged/discouraged/etc? ] 14:07, 1 December 2024 (UTC)
When we moved from having the votes on the WP:RM page to the talk page as you will see from the archive, I originally proposed a more proscriptive solution but the opinion at the time was that was too much ]. The format we have been using for about 9 months seems to have worked well in the vast majority of cases. Particluarly since the agreement to count the proposer as a vote in favour of the change and a 60% threshold (see ]), so no votes 100% consensus in favour of the move, one oppose 50/50 no consensus, One support and one oppose 2/3 so consensus to move.


:I think the current guidelines are good enough as they are.
The recent change which ] are IMHO better but I am going to remove the header "===Polling===". The other header "===Cast votes===" had snuck in without me noticing when I cut and pasted back what I thought was the original. Having a header between the proposer and an "opinion/poll" section could re-open the argument that "No one has voted in the poll section for the change, so no change should take place". This would be a pity because many page moves do not attract many votes and keeping it simple has worked well for those moves over the last few months. The idea behind what was as a compromise, to keep instruction creep to a minimum, while making sure that an administrator can easily work out what the result is without opening up a can of worms. (see ] which sparked the ] section mentioned above). ] 17:47, 29 August 2005 (UTC)
:While it's rare, sometimes someone clerking at RM may be relisting something neutrally and thereafter some arguments are made by editors and the person who relisted it will often be following threads as well a week later to potentially close it, but sometimes new arguments are made since relisting (since that's the point) and as experienced editors, sometimes then instead of closing a discussion as say no consensus based on the presented arguments, that editor may instead decide to become a party of the discussion and present new evidence as a participant, which, while rare, is not entirely unheard of, since the people that relist/close sometimes have more experience with regards to ] policies and if such evidence wasn't presented in an RM, it can be useful to present it instead of just letting an RM play out resulting in potentially a wrong move. ] (]) 16:47, 1 December 2024 (UTC)
:They seem to say the same thing. Many editors consider many acceptable things inadvisable, but PAG is based on consensus. But the way the first sentence is structured implies that the opinions of many editors outweighs the lack of editor consensus. Perhaps it could be changed to read, "While many editors consider it an inadvisable form of supervote, there is no consensus forbidding participation in a requested move discussion after relisting it." ] (]) 17:35, 1 December 2024 (UTC)
::The first sentence discourages against participating after relisting, the second one says it's allowed. I think some clarity, on both pages, is needed if it's allowed, discouraged or both. ] 18:59, 1 December 2024 (UTC)
:The lines from ] about supervote are wrong and should be '''removed'''. A supervote is when a closure reflects the closer's own preference, which should have been a vote, but instead is a super-powered vote that gets the last word and shuts down rebuttal. A relist does none of that. It doesn't stop other people from discussing. It doesn't stop other people from closing ("there is no required length of time to wait before closing a relisted discussion"). All it is is one person's non-binding opinion that a discussion wasn't ready for closure at a particular time. Participating after relisting is no big deal. ] (]) 09:29, 3 December 2024 (UTC)
:The underlying idea is that there are always enough participants for a discussion without relying upon the input of involved editors. The lines effectively discourage adding a !vote at the same time as relisting, which would usually be disruptive in practice if not in theory (most closers wait for resisted discussions to expire even though that is not required). With that in mind I think it is best for both lines to be retained. The general practice should be discouraged, and it is noted that it is not explicitly forbidden in special cirumstances. ]<small>]</small> 13:14, 3 December 2024 (UTC)
:While I can see what you bring up, they're not exactly conflicting, but they could introduce confusion, especially for those who never look at the closing instructions so regular participators in the RM might feel that it is inappropriate. However, at the end of the day I believe that most closers properly understand how much weight to place on the relisting editor -- which is basically almost zero. However, we still want to discourage the general practice of people relisting and !voting, as it might give the appearance of trying to game the system, especially when their !vote is running in contrary to what otherwise might appear to be consensus forming. ]&thinsp;] 05:50, 4 December 2024 (UTC)


== Best way to handle a complicated move? ==
I had an edit clash so I will also answer the last comment by kim Bruning. Yes the comment should be optional and yes it should only be one sentence long. Take a look at a vote like ] and compare that with ] to see why. ] 17:47, 29 August 2005 (UTC)


I need help with something, if you don't mind. I came across a weird situation with ] and ]. The original list has been pretty static for a long time, and the sorted list is fuller, better cited, and better maintained. I proposed merging them and have ], but it's not really a merge, because other than a couple of citations that needed to be copied over (which I've already done), all of the content will come from the sorted list. So it seems counter-productive to copy and paste it over the original list--the history should be with the content. How is this sort of thing handled? Move the original list to a subpage to preserve ''it's'' history, maybe, and then move the sorted list to ]? Thanks! ] 02:09, 4 December 2024 (UTC)
The subtitle "polling" (or, earlier, "cast votes") should be kept, since it helps the actual editing process. With it, a voter (an "opinionator") needs not take the whole length into the edit window, when writing the vote. The size of edit window is important to many, with lesser net capacity. You have seen that the discussion portion could be '''somewhat''' full and long in certain cases. ] 18:06, 29 August 2005 (UTC)
:Redirect the former page to the latter, tag it with {{t|r from merge}} and {{t|r with history}}, make sure to add all of the appropriate talk page attribution templates (e.g. {{t|merged from}}) and call it a day. Just because there isn't actually any text being merged doesn't mean that the pages can't be merged. ] (]) 11:19, 4 December 2024 (UTC)
::And if you want ] to go to ] after the merge, a ] will be required, which can be performed by a page mover or administrator. <span class="nowrap">&#8212;''']'''</span> <sup class="nowrap">(] • {]•]})</sup> 17:33, 4 December 2024 (UTC)
:::Thanks. Is that better than using the templates to point to the history? I have now completed the merge, so right the history of what is now ] is at ], which is a redirect. ] 00:09, 5 December 2024 (UTC)
::::''sigh'' you did exactly the opposite of what I was suggesting, though in fairness my statements were based on the (sorted) version being the final target. I have sorted everything out though. ] (]) 12:55, 5 December 2024 (UTC)
:::::Sorry! I misunderstood. But thank you for fixing it! I think having one list instead of two will be a lot clearer to readers. ] 00:08, 6 December 2024 (UTC)
::::::No worries, I should have been clearer and it was a fairly simple fix. ] (]) 12:47, 6 December 2024 (UTC)


== Potentially inexperienced user closing RMs ==
We should make a convention to admins that the proposer is counted as supporter (if not explicitly stated otherwise - there are submissions where the original proposer has forgotten to list it, but an opponent or a bystander desires to have a conclusion to a "tagging"). When closing admins know it, it should not be a problem - besides, in difficult cases, proposers themselves also seem often to register a separate vote, just to be sure. ] 18:06, 29 August 2005 (UTC)


It looks like a potentially inexperienced user (@]) has tried to help with closing RMs today and and then brought , which shone light on it.
I am in favor of trying to limit the main explanation - there are always people who write an "Agatha Christie" novel to give their reasons and much more else. It would be good to have main explanation of a couple of sentences, and all the else in commentaries-section. Perhaps it would be good to require at least one sentence, on the other hand. ] 18:06, 29 August 2005 (UTC)
Their ] appears to be lighting up with already 4 (, , , ) as well as one challenge at .


I'm sure the editor means well to help, but it might require someone reviewing all of them and potentially vacating the RM closes. ] (]) 01:28, 10 December 2024 (UTC)
:No the sentence should remain be optional (we don't want an arguments over "That vote does not count because you did not comment"). Fair point about the block edit. However I would suggest that it could be retrofitted (like proposals are) if the discussion starts to get large. But if we have a second header as you suggest, then we ought to have a section on WP:RM explaining that in a simple vote (only 2 options) the proposal counts as a vote. Perhaps we should have that section in the article anyway and formalise the talk page. ] 18:19, 29 August 2005 (UTC)


:It looks like there are also a lot of closes that ''weren't'' contested and none have ended up at ]. This should be handled on a case-by-case basis by the standard procedures if discussion participants have issues. Feeglgeef definitely needs more practice writing close rationales, but I don't think a public flogging here will be productive. ] </span>]] 09:07, 10 December 2024 (UTC)
I don't like the polling section myself; I think polling should only happen when discussion is just going around in circles so much you can't gauge consensus by it, and that "support" and "oippose" is useless without explanation. I don't want to read novels for each opinion, myself, but better a novel than nothing at all. ] ] 02:00, 1 September 2005 (UTC)
:I was surprised by the close as well, as there was only overwhelming consensus for only one of the two moves. My guess is that perhaps in their inexperience conflated partial consensus for full consensus, but it wasn't anything that was really going to concern me until I saw his talk page with multiple other people talking about other closing actions. Admittedly I remember when I first began doing NAC closures back in the beginning and not quite getting it right, perhaps some simple coaching if they're open to it is all that's needed. ]&thinsp;] 18:53, 10 December 2024 (UTC)


== Move ] to ] ==
:To be honest it takes long enough to sort these requests, and to have to wade through vast discussions takes even longer. ] ] 07:41, 1 September 2005 (UTC)


The them "]" previously served as the title of a disambiguation page, currently at ]. However, it currently redirects to ] as this seems to be the primary use of the term as information about ] seems to be sparse and out of date. Secondary sources indicate the Minnesota institution might actually be named "Virginia Secondary School". ] (]) 04:10, 11 December 2024 (UTC)
== 60% ==
:See ] for how the number came to be included in the WP:RM page. ]


:First reaction is that this was a bad idea to change before discussing it, but that is still acceptable. At the very least, you need a hat note so people can find the other school, and them I would suggest opening a RM formally for the Minnesota school, given that passes, then that would clear the way for an RM to make the school in Virgina for probably PT and drop the PARENDIS. Either way theirs is a question for discussion if the PrimaryRedirect is appropriate. ]&thinsp;] 06:29, 12 December 2024 (UTC)
The "rough consensus (60%)" comment is laughably incorrect. I only hope that no-one is applying it. It's such an amazingly vile violation of policy that I'm surprised that I'd not noticed it before, but then I suppose I can't go around expecting people to actually understand policy and word things correctly. :-(
::Broadly agree; it's not worth reverting the dab move just yet, but an RM will certainly make sure there is consensus that it ''was'' the right move. ] (]) 14:23, 12 December 2024 (UTC)
:::It looks like @] performed a revert of the redirect, so it now goes to the DAB page once again. @] if you still believe the move has merit, you're welcome to start a ] discussion in the appropriate way. ]&thinsp;] 14:53, 12 December 2024 (UTC)


== Move ] to ] in place of redirect page ==
] ] 14:40, 31 August 2005 (UTC)


<nowiki>{{</nowiki>'''subst''':'''requested move'''|VP-40|reason=The current page for the modern squadron VP-40 occupies the page VP-40 (1951-Present). It should be moved to the page VP-40 to match the uniformity of other squadron pages however ]<nowiki> is currently a redirect page}}</nowiki> ] (]) 04:32, 18 December 2024 (UTC)
:I don't have time to really start the discussion now, though I do hope to come back this. However, in the mean time, would you care to list which "policies" it is a violation of? The community has long resisted defining consensus. The closest we have is the "guideline" at ], which says (among other things) that 66% is the typical minimum threshold for consensus in VFD. ] 14:59, August 31, 2005 (UTC)


:@]: This is because there are/were two squadrons by the name ]. So, the squadron meeting ] criteria will stay at ], the other will be disambiguated using the parentheses. You will need to present a case of why the current VP-40 is the primary topic over the older one. Then, the other editors will deliberate over it, and a conclusion will be reached. <span class="nowrap">&#8212;''']'''</span> <sup class="nowrap">(] • {]•]})</sup> 18:30, 18 December 2024 (UTC)
::Which policy? ] states "''Misplaced Pages:No original research is one of three content policies. The other two are "Misplaced Pages:Neutral point" of view and "Misplaced Pages:Verifiability".''


== Request: Implement a form for requests at ] ==
::See the archive above but the reason for the 60% was to help administrators with a simple rule for all moves so that people could not quibble over what a "rough consensus" is. It was set at 60% because that number works well when there are only a few people (<6), expressing an opinion. Some in the previous discussion (including my self) would have liked a higher %age for larger votes but it was agreed to stick with one %age to keep the instruction creep to a minimum. I still agree with the argument presented by ] during the last discussion:
::"''Moving a page is not nearly as "big a deal" as setting policy, deleting a page, or promoting an admin - things that do require "rough consensus". Even though the title is the most visible part of the page, changing it isn't much different from changing content - something anyone can do. In fact, most of the time, any logged in user who's not completely new can just move a page. So I don't think we need to require a high threshold for moving pages listed here.''"
::and I agued that "''on pages like Zürich to Zurich the WP:RM serves another purpose and I think simple majority voting would not serve the wikipedia community as well consensus voting does by putting those types of debates to bed for a few months.''"--] 18:14, 31 August 2005 (UTC)


As part of my work at ], I review a lot of redirects, often working from the back of the queue. Pages which are turned into redirects by users who are not autopatrolled are automatically put into the queue for review, and I find a lot of cut and paste moves happening, which I of course revert and leave warnings about. These aren't just from newer users either unfortunately, and I've been thinking for a while that it could be easier to request page moves.
== too complicated polling tools ==


Which leads me to my suggestion: There should be a form, similar to those at ] (]), to make requesting the moves simpler and more straightforward. Let's face it, some people are offput by trying to use the template, and why not make life easier? I believe this would reduce the issues we have with cut and paste moves and make it easier to direct newer users to make such requests. Suggested fields would be current page title, target page title, reason for move.
Please see what sort of voting table has been introduced into use at ]. I am quite certain that it is not from here, as RM page proposes much simpler things. I have understood that "instruction creepism" has been deemed bad by you, and you have desired to keep pollings simple. Particularly wrt what participants need to do in order to participate in the polling.


I'd also be for making requested moves easier in a similar fashion, because I do think we'd make Misplaced Pages easier to get into with more form usage, but I figure one step at a time. ] (]) 15:10, 22 December 2024 (UTC)
That table itself seems a too complicated thing to me. It presumably drives from taking part in discussion to mechanical voting. (Actually, several Dutch voters in the table have not uttered anything to the discussion, so their reasons remain unclear and are not helpful to build any sort of consensus).


:Last month @] mentioned that the current process is complicated. I admit to quickly dismissed the critique as I find it easy enough and the process is used in many other places. However on your mention here it has caused me to pause and think more about it. I think this does have some merit and your proposal is slightly better than theirs. Either way it would probably result in a fundamental change to how RM are created and managed. As well as impact bots. It’s unfortunate that each of these sorts of things are handled differently depending on the area, RPP, SPA, YFA, etc. But probably still worth consideration and talking about it. Although I’m not certain what would be required as it would be a significant change to workflow and possibly impact how things are accessed and researched historically. ]&thinsp;] 15:44, 22 December 2024 (UTC)
Complications are a bad thing. What next: is someone entitled to demand that participants stood on their heads in order to be eligible to participate in a poll?
::I don't really see how this proposal would fundamentally alter much. OP doesn't seem to be talking about controversial moves, just generic cut-and-paste stuff. As far as I can see, all it would change if implemented is that the request button on ] would direct you to a Javascript form instead of a hidden note telling you how to list the RMassist template. ] (]) 01:56, 23 December 2024 (UTC)
:::@]: That is indeed my primary intent with this, though I do also think we could make requesting moves which require discussion easier for newcomers than we currently do. ] (]) 13:34, 23 December 2024 (UTC)
:On ] under "XFD", there's an RM option with "Uncontroversial technical request" available. The whole RM capability is not mentioned at ], but the functionality is referenced at ]. —] (]) 10:09, 24 December 2024 (UTC)
::not everyone installs twinkle by default though. It is worth looking into. I have some free time this holiday, I will look into this. ] (]) 12:07, 24 December 2024 (UTC)
:::Yes, this is where I'm at on the matter. ''I'' don't have an issue initiating these requests or RMs, but based on how much difficulty some users have, we have a hump that we can help them get over in order to help with retention and reduce cut and paste moves. Thanks @], I appreciate it. ] (]) 12:41, 24 December 2024 (UTC)
:::Yes, I wasn't implying that Twinkle precludes a standalone solution. It was more FYI in case others weren't aware (I didn't even know the WP:RM/TR feature was on Twinkle). Best. —] (]) 13:02, 24 December 2024 (UTC)


== 100+ thoughtless RMS by ] ==
I cannot avoid an impression that someone has too much technical interests (perhaps too little interest in actual substance contents), has built an elaborate table, and that results in all others being forced to be guinea pigs to use that tool. I do not oppose if someone wants to maintain an extra table to show polling situation, but tob demand participants themselves to use such goes too far. ] 15:03, 2 September 2005 (UTC)


] filed more than 100 RMs yesterday on US colleges and universities , apparently wanting them all renamed according to the way they're referred to in sports coverage, with all the idiosyncratic inconsistencies inherent in that e.g. ''San Francisco State University → SFSU'' and ''California State University Channel Islands → CSU Channel Islands'' and ''California State University, Northridge → Cal State Northridge''. All of these have been universally opposed on the various article talk pages e.g. -- and see also . Is there a way to snow close them all right now on a mass basis, before more editor time is wasted? From other comments at the last link this editor has been doing this in at least one other topic area, so it may be necessary to ban this editor from RMs completely before this is over. ]] 14:45, 23 December 2024 (UTC)
:The WP:RM request for that page was done by ] while a change in the WP:RM guidelines was in place for a day or so (see above: ]) when the new format made it difficult to see who was supporting what, Francis introduced his own polling table. Since the WP:RM page guidlines reverted back to the previouse guidlines, something made possible to do with little argument thanks to the mess on ] page, Francis has continued to use the guidlines as layed out eg the more recent ]. ] 16:38, 2 September 2005 (UTC)


:My first reaction was that it's sometimes blurry how to balance being bold with ]. On the cautious side though, this user was also banned before with their sock {{u|23prootie}}, and the last of that user's blocks was re: move warring. —] (]) 09:54, 24 December 2024 (UTC)
== History description ==
:I closed these a little while ago. ] (]) 10:38, 24 December 2024 (UTC)

Nitpicking alert: I note that the description of moves in the page history has changed from "PageName moved to NewPageName" to "PageName '''has been''' moved to NewPageName'''.'''" Is this an improvement? I think it reads worse - the previous version was more grammatically neutral, so it made equal sense when viewed in user contributions, recent changes, and page histories; also, the full stop at the end is just wrong. It's in ] if anyone feels like looking at it. ] ] 09:13, 12 September 2005 (UTC)
:I agree, and have reverted it. ] ] 19:43, 14 September 2005 (UTC)
::Sweet. ] ] 20:51, 14 September 2005 (UTC)

== Possible clarification of instructions? ==

I misunderstood part of the instructions under "copying the following is suggested". Instead of putting this text in:

:''Add *'''Support''' or *'''Oppose''' followed by an optional one sentence explanation, then sign your vote with <nowiki>~~~~</nowiki>''

I did what it said: that is, I added '''Support''', and signed my vote. ] kindly informed me that you can't vote for your own move request, which I suppose makes sense; only, it doesn't say that anywhere in the instructions. Perhaps someone could reword the instructions slightly so that other folks don't make the mistake I did? &mdash;] 18:42, 14 September 2005 (UTC)
:Maybe just template the thing, with instructions to type <nowiki>{{subst:Reqmove|Reasons for moving - ~~~~}}</nowiki> with a couple of variants for multiple page moves or a move with multiple options? - ] 18:56, 14 September 2005 (UTC)

== lots of confusion over redirect policies ==

Dear Wikipedians: Please note, that a similar question arose for ], as arose for ]. At NBC, it was suggested that it be moved to ]. At Public Broadcasting Service, it was suggested that it be moved to PBS. '''IN EACH CASE, THE SAME JUSTIFICATION WAS GIVEN FOR COMPLETELY OPPOSITE DECISION'''. Namely, with PBS, because "Public Broadcasting Service" is "clearly predominant", that most people "know what it stands for", this is used as justification that it STAY at Public Broadcasting Service, and that PBS redirect to the full name. Yet, at the discussion at NBC, the article title "NBC" is kept because "about 99,999 people out of 100,000 will be looking for the National Broadcasting Company, not the Newfoundland Barbering Commission or the National Bowling Congress.", and "it will be the name most people are likely looking for". I believe this is evidence of one of 2 things:

*The redirect and renaming policies are unclear or confusing.
*The policies are clear, but people ignore them and just invoke them to support whatever they think is best.

Which is it? ] 21:44, 14 September 2005 (UTC)

== How are noncontroversial moves made? ==

I'm sorry, but Wik is still a horrible chaos for normal users. I have been unable to find any-thing on normal moves (Misplaced Pages:moves gets re-directed hither). This article should have a link (Wik articles are usually way overloaded with links) to a straight-forward explanation of how noncontroversial moves are made. ] 04:40, 25 September 2005 (UTC)

:Normal moves are made using the tab at the top of every page, between the tab and the (or ) tab. ] 04:43, 25 September 2005 (UTC)

::Thank You. {{Unsigned|Kdammers|05:03, 25 September 2005}}

:: Probably the instructions at the top of this page ought to mention this; I'll add it (and a link to ]) if they don't already. (I know, I know, "Instruction creep", but if we're getting questions...) ] ] 19:00, 28 September 2005 (UTC)

==Repairing cut-and-paste moves==

I've gotten a number of requests recently to help repair cut-and-paste moves, something I have some experience with. Since cut-and-paste moves (a big no-no, they separate the ] from the content, which we want to avoid for ] reasons) seems to be something that happens a fair amount, I'm going to try and rejuventate the ] to deal with them; I have signed up on ] to maintain it. I'm going to add a ''brief'' note to WP:RM mentioning it; hope that's OK. ] ] 19:00, 28 September 2005 (UTC)

== Backlog ==

I did my best to delete those requests from the list which had already been fulfilled, but that doesn't change anything about the fact that there's still a backlog of moves to be done. ] ] ] 11:06, 29 September 2005 (UTC)

==Backlog redux==
There's still a horrendous backlog here. Can I propose a couple of mechanisms that might help cut it down?
#Make improper formulation of a request (current examples: ] and ], which are lacking the talk-page boilerplate) grounds for flagging {notmoved} after a week or so (combined with a polite note on the talk page inviting its correct relisting).
#Place the onus on fixing "what links here" redirects, etc. on the ''person proposing the move,'' rather than on the poor overworked admin who makes the move. There are a couple of current listings with clear consensuses in favour, but a daunting amount of incoming links and redirects. Plus, the requester should be better acquainted with the subject matter and better qualified to make correct decisions on what goes where.
Comments? ] 02:45, 14 October 2005 (UTC)

Yep - I made a template for #1 - <nowiki>{{Notmovedmalformed}}</nowiki> which produces:

{{Notmovedmalformed}}

<small>] <sup><font color="#6BA800">]</font> | <font color="#0033FF">]</font> | <font color="#FF0000">]</font></sup></small> 08:37, 15 October 2005 (UTC)

About #2 - I added a bit about that. It may be a bit too much though... remove it if it is :). <small>] <sup><font color="#6BA800">]</font> | <font color="#0033FF">]</font> | <font color="#FF0000">]</font></sup></small> 08:55, 15 October 2005 (UTC)

== Approval voting is not consensus building ==

I question the current recommendations of this page. The idea that ] is a good way to build ] is completely flawed, especially when it's set at a measly 60%. ].

I also question the status of this page as anything other than a user tool and a way to contact admins to help move articles that can't be moved by normal users. This page is ''not'' an arbitrator of official policy, does not hold sway over consensus achieved in pages such as WikiProjects and especially not if it works by the idea that majority decisions can decide article titles on Misplaced Pages.

] <sup>]</sup> 22:40, 14 October 2005 (UTC)

So... what do you propose? There are plenty of complaints already, and meanwhile the backlog keeps growing :\. <small>] <sup><font color="#6BA800">]</font> | <font color="#0033FF">]</font> | <font color="#FF0000">]</font></sup></small> 23:15, 14 October 2005 (UTC)

A page is blocked from being moved a person proposes a move. Two others express an opinion. One for one against. You are the administrator after five days do you move it or not?

Next day a page is blocked from being moved a person proposes a move. Two others express an opinion. Both disagree with the move. You are the administrator after five days do you move it or not?

This is a decision that the overworked administrators who look at this page have to make all the time. The 60% or more rule is simple to follow and reduces conflict for the adminstrators by giving them some protection from them being accused of acting in an abitary manner. See the history of the WP:RM talk pages for examples. It also makes WP:RM moves sticky in that a 20% change in the rough consensus has to take place before a new WP:RM request can overturn a previous one.

Peter also look at the bottom of the WP:RM page. WP:RM activly suggests informing WikiProjects of page moves which effect pages in their domain to try to stop WP:RM being used as an underhand way to get around project guidelines. If you think that a particular WikiProject is missing which you think should be added to the list then why not add it? --] 23:58, 14 October 2005 (UTC)

:If an administrator is unsure whether there is consensus or not, and all the appropriate guidelines have been weighed in, the answer is very self-evident; don't move the page. This is the standard practice in all other similar situations concerning article content or article status. The solution is ''not'' to set unacceptably low standards for what consensus actually is.
:I've made amendments to the guidelines that actually follow the recommendations of ] and hard policies such as ]. If you look at the rewording, you'll notice that the idea that people should give proper time for discussion and consensus to build up would discourage the current system of ''first'' plopping a full-fledged vote on unsuspeciting talkpages (with a horrendously low percentage for approval). If people don't make proper attempts to discuss before requesting moves, I think admins should simply remove the request (and any attempts of voting) until this is actually done. Just demand that people actually take time to ask around, start discussions and check the proper guidelines and policies before dumping the request here to simmer Admins should not be forced to make the kind of decisions they're currently making.
:I've also removed the 60% figure, because it has no support in the practices of Misplaced Pages in general and has nothing to do with genuine consensus building. If people demand set percentages, then they should be informed that this is not the place to enforce such standards. And, btw, I don't think that individual WikiProjects should be linked to. There's just way too many of them.
:] <sup>]</sup> 13:42, 15 October 2005 (UTC)

== guidence requested ==

OK - I took care of quite a few days, but I ran into some distintly difficult cases:
#There was no notice/template on the talk page but there was in entry here. In this case I turned down the request
#:did you leave a comment explaining why?
#*There was another one like the above only this time with more approval on talk page - in this case I moved
#:Yep I guess.
#Another one where there was notification on the talk page, but the only comment/vote was from an anon not to move. In this case I didn't move it.
#:I think you should have moved it. But as the administrator who delt with it I support your decision.
#One where an anon nominated but a logged in user with a comment from several months ago disagreed
#:I would not have moved it. ] 09:17, 15 October 2005 (UTC)

Some of the above has drawn strong complaints. What would you do :)? <small>] <sup><font color="#6BA800">]</font> | <font color="#0033FF">]</font> | <font color="#FF0000">]</font></sup></small> 02:52, 15 October 2005 (UTC)

For the first one I made the template outlined above (but on the requests in question just gave an explanation). Thanks a million for your thoughts/opinions! <small>] <sup><font color="#6BA800">]</font> | <font color="#0033FF">]</font> | <font color="#FF0000">]</font></sup></small> 09:22, 15 October 2005 (UTC)

==ch-ch-changes==

===How big should the introduction be===

See previous debates on this talk page about this. I am in favour of keeping the introduction as short a possible otherwise the trees get lost in the wood. ] 14:53, 15 October 2005 (UTC)

:Well, on AfD they move stuff to subpage. Maybe we could have something like ] if it gets too big? Otherwise I agree of course.... <small>] <sup><font color="#6BA800">]</font> | <font color="#0033FF">]</font> | <font color="#FF0000">]</font></sup></small> 15:00, 15 October 2005 (UTC)

===Should Current notices be in a sub page===

I am of a mind that they should remain on this page otherwise this page does not get monitored like it should and probably does not get read. It has the effect of removing the instructions form the action. ] 14:53, 15 October 2005 (UTC)

Hmmm.... I was going for an AfD-style layout. Someone suggested a subpage for content too on ]. <small>] <sup><font color="#6BA800">]</font> | <font color="#0033FF">]</font> | <font color="#FF0000">]</font></sup></small> 14:46, 15 October 2005 (UTC)

I'm not sure that AFD has anything to reccomend it. ] 14:53, 15 October 2005 (UTC)

:Ryan, the AfD-style layout isn't bad, but it doesn't seem necessary as long as the backlog doesn't get absolutely overwhelming. I'd prefer to have the requests on the same page until it ''really'' starts to get huge.
:Philip, I'm not sure this kind of discussion granulating is especially helpful. If you only have a few sentances worth of post, just keep it under one header.
:] <sup>]</sup> 14:58, 15 October 2005 (UTC)

:I did it because they are two distinct issues. I agree with you on keeping the requests on the same page. But do you agree with me that the introduction should be kept short and susinct? (please relply to that in the section above) ] 15:23, 15 October 2005 (UTC)

===#History merges===
The reason I removed that is because its in the admin instructions... right now it doesn't point to anything. Maybe that part needs to be here someplace (maybe it's not admin-specific?)? <small>] <sup><font color="#6BA800">]</font> | <font color="#0033FF">]</font> | <font color="#FF0000">]</font></sup></small> 15:00, 15 October 2005 (UTC)
:Well, I fixed that link to point to the admin page. A little clumsy, but it works. <small>] <sup><font color="#6BA800">]</font> | <font color="#0033FF">]</font> | <font color="#FF0000">]</font></sup></small> 15:07, 15 October 2005 (UTC)

Latest revision as of 13:02, 24 December 2024

This is the talk page for discussing Requested moves and anything related to its purposes and tasks.
Shortcut
NOTE: This is not the place to request moves. Please follow the instructions given on the project page. If you seek instruction on closing existing requests, please see the closing instructions.
Please use the Misplaced Pages:Move review process for contested move request closes.
To help centralize discussions and keep related topics together, most subpages of Misplaced Pages:Requested moves that are unused have talk pages that redirect here.
This page has previously been nominated to be moved. Please review the prior discussions if you are considering re-nomination.

Discussions:

  • RM, WP:Requested moves → WP:Proposed moves, No consensus, 7 June 2007
  • RM, WP:Requested moves → WP:Proposed moves, Not moved, 11 February 2018
  • RM, WP:Requested moves → WP:Articles for renaming, Not moved, 19 September 2018
  • RM, WP:Requested moves → WP:Requested title changes, Not moved, 22 July 2024
Enter the title (or part of a title) to search for after "intitle:", then click "search" Try other variants (e.g. "move discussion") to broaden or narrow your search

Archives
Index 1, 2, 3, 4, 5, 6, 7, 8, 9, 10
11, 12, 13, 14, 15, 16, 17, 18, 19, 20
21, 22, 23, 24, 25, 26, 27, 28, 29, 30
31, 32, 33, 34, 35, 36
Archives by date
  1. Oct 2004 – Jan 2005
  2. Jan 2005 – Feb 2005
  3. Feb 2005 – Mar 2005
  4. Mar 2005 – Aug 2005
  5. Aug 2005 – Dec 2005
  6. Dec 2005 – Jun 2006
  7. Jun 2006 – Sep 2006
  8. Sep 2006 – Feb 2007
  9. Feb 2007 – May 2007
  10. May 2007 – Nov 2007
  11. Nov 2007 – May 2008
  12. Jun 2008 – Oct 2008
  13. Nov 2008 – Jan 2009
  14. Jan 2009
  15. Jan 2009 – Jun 2009
  16. Jun 2009 – Oct 2009
  17. Oct 2009 – Jun 2010
  18. Jun 2010 – Oct 2010
  19. Oct 2010 – Jan 2011
  20. Jan 2011 – Sep 2011
  21. Sep 2011 – Jan 2012
  22. Jan 2012 – Apr 2012
  23. Apr 2012 – Aug 2012
  24. Aug 2012 – Dec 2012
  25. Dec 2012 – Dec 2013
  26. Dec 2013 – Nov 2014
  27. Nov 2014 – Apr 2015
  28. Apr 2015 – Jun 2016
  29. Jun 2016 – May 2017
  30. May 2017 – Mar 2018
  31. Mar 2018 – May 2019
  32. May 2019 – Jun 2020
  33. May 2020 – Mar 2022
  34. Mar 2022 – Jan 2023
  35. Jan 2023 – Jun 2024
  36. Jul 2024 –

This page has archives. Sections older than 30 days may be automatically archived by Lowercase sigmabot III when more than 5 sections are present.

Move the article of Yifei Ye to Ye Yifei

I want to move the article based on the Chinese name format where the surname placed first. In motorsport, he always called by Yifei Ye than Ye Yifei, but to make it consistent with other Chinese figures, and people his name has to be Ye Yifei. It's not Zedong Mao, it's Mao Zedong for example. Hope someone can accepts the changes. Thank you. Thfeeder (talk) 06:37, 21 November 2024 (UTC)

Thfeeder, please see WP:RM#CM for how to start a move request at the article's talk page. Primefac (talk) 13:10, 23 November 2024 (UTC)

Overcomplication

Making move requests is way too overcomplicated, this page should be handled like the protection request page. RaschenTechner (talk) 18:01, 24 November 2024 (UTC)

  • Protections aren't generally controversial, so the format isn't very useful for something that typically requires debate. There is WP:RMTR for uncomplicated moves that no one will object to. Nohomersryan (talk) 16:49, 25 November 2024 (UTC)
    What I mean is that there isn't an "add topic" button or something like this on this page, unlike the protection request page, you would have to edit the page manually, which you can't do as an IP user, because this page is semi-protected. RaschenTechner (talk) 18:46, 25 November 2024 (UTC)

Move cleanup

Misplaced Pages:Requested moves/Closing instructions § Cleaning up after the move reads:

You should not close any move if you are unwilling to do the necessary clean up tasks described at WP:POSTMOVE

Maybe I just more notice and remember the cases where this isn't done, but to what extent does the community consider this a closer requirement versus some WP:NODEADLINE laundry list that anyone can volunteer to do, not necessarily the closer. I'm trying to have the proper perspective on this. —Bagumba (talk) 04:25, 27 November 2024 (UTC)

The line is pretty clear, if an editor wants to close a move, they should be willing to do the postmove cleanup, such as fixing bypass redirects in templates or retargeting links and cleaning up leads.
The only general exception I'd see to that is if some editors in the discussion have volunteered preemptively that they will do some of the cleanup if it's not just ordinary cleanup. Like say an alternative result of a split or so that requires more than routine cleanup. Raladic (talk) 04:34, 27 November 2024 (UTC)
My perspective has been that editors should avoid closing articles if they cannot complete the task within a reasonable amount of time, say an hour or so. The exception to this that I can think of have been in RMnac situations where sometimes an experienced editor can perform most (but not all) of the necessary close steps (such as a delay such as waiting for a CSD to make room) or they might be closing the discussion, and then asking requesting a technical move, etc. But in these cases, they should be monitoring for those changes to take place and promptly go about finishing up any cleanup work, which I'd AGF and gracefully give many hours (but not multiple days) for this to be accomplished (e.g. an Admin performs their action while the closer is now asleep). However, at this point, I would say it would be acceptable for another experienced editor to jump in and help out as well with wrapping up the cleanup tasks. However, if any RM closer is consistently dropping the ball with regards to cleanup tasks, do AGF and use their talk page. TiggerJay (talk) 08:55, 27 November 2024 (UTC)
However, at this point, I would say it would be acceptable for another experienced editor to jump in and help out as well with wrapping up the cleanup tasks: Yeah, I'm sure nobody would mind if a non-closer volunteers to help cleanup. But my original question was about the expectation of closers to cleanup their moves, such as old titles that got usurped or links in navboxes. —Bagumba (talk) 13:21, 27 November 2024 (UTC)
Right, I think my initial statement that if you cannot commit to doing the cleanup tasks, then you should avoid closing an RM. TiggerJay (talk) 05:44, 4 December 2024 (UTC)

Participating in a RM after relisting

These texts don't seem to align:

Should either or both be removed/changed to become aligned on whether participating in an RM after relisting is allowed/not allowed/encouraged/discouraged/etc? Frost 14:07, 1 December 2024 (UTC)

I think the current guidelines are good enough as they are.
While it's rare, sometimes someone clerking at RM may be relisting something neutrally and thereafter some arguments are made by editors and the person who relisted it will often be following threads as well a week later to potentially close it, but sometimes new arguments are made since relisting (since that's the point) and as experienced editors, sometimes then instead of closing a discussion as say no consensus based on the presented arguments, that editor may instead decide to become a party of the discussion and present new evidence as a participant, which, while rare, is not entirely unheard of, since the people that relist/close sometimes have more experience with regards to WP:AT policies and if such evidence wasn't presented in an RM, it can be useful to present it instead of just letting an RM play out resulting in potentially a wrong move. Raladic (talk) 16:47, 1 December 2024 (UTC)
They seem to say the same thing. Many editors consider many acceptable things inadvisable, but PAG is based on consensus. But the way the first sentence is structured implies that the opinions of many editors outweighs the lack of editor consensus. Perhaps it could be changed to read, "While many editors consider it an inadvisable form of supervote, there is no consensus forbidding participation in a requested move discussion after relisting it." Safrolic (talk) 17:35, 1 December 2024 (UTC)
The first sentence discourages against participating after relisting, the second one says it's allowed. I think some clarity, on both pages, is needed if it's allowed, discouraged or both. Frost 18:59, 1 December 2024 (UTC)
The lines from Misplaced Pages:Requested moves about supervote are wrong and should be removed. A supervote is when a closure reflects the closer's own preference, which should have been a vote, but instead is a super-powered vote that gets the last word and shuts down rebuttal. A relist does none of that. It doesn't stop other people from discussing. It doesn't stop other people from closing ("there is no required length of time to wait before closing a relisted discussion"). All it is is one person's non-binding opinion that a discussion wasn't ready for closure at a particular time. Participating after relisting is no big deal. Adumbrativus (talk) 09:29, 3 December 2024 (UTC)
The underlying idea is that there are always enough participants for a discussion without relying upon the input of involved editors. The lines effectively discourage adding a !vote at the same time as relisting, which would usually be disruptive in practice if not in theory (most closers wait for resisted discussions to expire even though that is not required). With that in mind I think it is best for both lines to be retained. The general practice should be discouraged, and it is noted that it is not explicitly forbidden in special cirumstances. Dekimasuよ! 13:14, 3 December 2024 (UTC)
While I can see what you bring up, they're not exactly conflicting, but they could introduce confusion, especially for those who never look at the closing instructions so regular participators in the RM might feel that it is inappropriate. However, at the end of the day I believe that most closers properly understand how much weight to place on the relisting editor -- which is basically almost zero. However, we still want to discourage the general practice of people relisting and !voting, as it might give the appearance of trying to game the system, especially when their !vote is running in contrary to what otherwise might appear to be consensus forming. TiggerJay (talk) 05:50, 4 December 2024 (UTC)

Best way to handle a complicated move?

I need help with something, if you don't mind. I came across a weird situation with List of mandolinists and List of mandolinists (sorted). The original list has been pretty static for a long time, and the sorted list is fuller, better cited, and better maintained. I proposed merging them and have heard no objections, but it's not really a merge, because other than a couple of citations that needed to be copied over (which I've already done), all of the content will come from the sorted list. So it seems counter-productive to copy and paste it over the original list--the history should be with the content. How is this sort of thing handled? Move the original list to a subpage to preserve it's history, maybe, and then move the sorted list to List of mandolinists? Thanks! blameless 02:09, 4 December 2024 (UTC)

Redirect the former page to the latter, tag it with {{r from merge}} and {{r with history}}, make sure to add all of the appropriate talk page attribution templates (e.g. {{merged from}}) and call it a day. Just because there isn't actually any text being merged doesn't mean that the pages can't be merged. Primefac (talk) 11:19, 4 December 2024 (UTC)
And if you want List of mandolinists (sorted) to go to List of mandolinists after the merge, a WP:PAGESWAP will be required, which can be performed by a page mover or administrator. —CX Zoom 17:33, 4 December 2024 (UTC)
Thanks. Is that better than using the templates to point to the history? I have now completed the merge, so right the history of what is now List of mandolinists is at List of mandolinists (sorted), which is a redirect. blameless 00:09, 5 December 2024 (UTC)
sigh you did exactly the opposite of what I was suggesting, though in fairness my statements were based on the (sorted) version being the final target. I have sorted everything out though. Primefac (talk) 12:55, 5 December 2024 (UTC)
Sorry! I misunderstood. But thank you for fixing it! I think having one list instead of two will be a lot clearer to readers. blameless 00:08, 6 December 2024 (UTC)
No worries, I should have been clearer and it was a fairly simple fix. Primefac (talk) 12:47, 6 December 2024 (UTC)

Potentially inexperienced user closing RMs

It looks like a potentially inexperienced user (@Feeglgeef) has tried to help with closing RMs today and has closed several RM discussions today and then brought some to RMTR, which shone light on it. Their User talk page appears to be lighting up with already 4 (, , , ) as well as one challenge at RMTR.

I'm sure the editor means well to help, but it might require someone reviewing all of them and potentially vacating the RM closes. Raladic (talk) 01:28, 10 December 2024 (UTC)

It looks like there are also a lot of closes that weren't contested and none have ended up at Move review. This should be handled on a case-by-case basis by the standard procedures if discussion participants have issues. Feeglgeef definitely needs more practice writing close rationales, but I don't think a public flogging here will be productive. Toadspike 09:07, 10 December 2024 (UTC)
I was surprised by the close as well, as there was only overwhelming consensus for only one of the two moves. My guess is that perhaps in their inexperience conflated partial consensus for full consensus, but it wasn't anything that was really going to concern me until I saw his talk page with multiple other people talking about other closing actions. Admittedly I remember when I first began doing NAC closures back in the beginning and not quite getting it right, perhaps some simple coaching if they're open to it is all that's needed. TiggerJay (talk) 18:53, 10 December 2024 (UTC)

Move Virginia High School (Virginia) to Virginia High School

The them "Virginia High School" previously served as the title of a disambiguation page, currently at Virginia High School (disambiguation). However, it currently redirects to Virginia High School (Virginia) as this seems to be the primary use of the term as information about Virginia High School (Minnesota) seems to be sparse and out of date. Secondary sources indicate the Minnesota institution might actually be named "Virginia Secondary School". Bernardgeorgeh (talk) 04:10, 11 December 2024 (UTC)

First reaction is that this was a bad idea to change before discussing it, but that is still acceptable. At the very least, you need a hat note so people can find the other school, and them I would suggest opening a RM formally for the Minnesota school, given that passes, then that would clear the way for an RM to make the school in Virgina for probably PT and drop the PARENDIS. Either way theirs is a question for discussion if the PrimaryRedirect is appropriate. TiggerJay (talk) 06:29, 12 December 2024 (UTC)
Broadly agree; it's not worth reverting the dab move just yet, but an RM will certainly make sure there is consensus that it was the right move. Primefac (talk) 14:23, 12 December 2024 (UTC)
It looks like @Nardog performed a revert of the redirect, so it now goes to the DAB page once again. @Bernardgeorgeh if you still believe the move has merit, you're welcome to start a WP:RM discussion in the appropriate way. TiggerJay (talk) 14:53, 12 December 2024 (UTC)

Move VP-40 (1951-present) to VP-40 in place of redirect page

{{subst:requested move|VP-40|reason=The current page for the modern squadron VP-40 occupies the page VP-40 (1951-Present). It should be moved to the page VP-40 to match the uniformity of other squadron pages however VP-40 is currently a redirect page}} Chilichongoes (talk) 04:32, 18 December 2024 (UTC)

@Chilichongoes: This is because there are/were two squadrons by the name VP-40. So, the squadron meeting WP:Primary topic criteria will stay at VP-40, the other will be disambiguated using the parentheses. You will need to present a case of why the current VP-40 is the primary topic over the older one. Then, the other editors will deliberate over it, and a conclusion will be reached. —CX Zoom 18:30, 18 December 2024 (UTC)

Request: Implement a form for requests at WP:RM/TR

As part of my work at NPP, I review a lot of redirects, often working from the back of the queue. Pages which are turned into redirects by users who are not autopatrolled are automatically put into the queue for review, and I find a lot of cut and paste moves happening, which I of course revert and leave warnings about. These aren't just from newer users either unfortunately, and I've been thinking for a while that it could be easier to request page moves.

Which leads me to my suggestion: There should be a form, similar to those at WP:RFPP (direct link to a form), to make requesting the moves simpler and more straightforward. Let's face it, some people are offput by trying to use the template, and why not make life easier? I believe this would reduce the issues we have with cut and paste moves and make it easier to direct newer users to make such requests. Suggested fields would be current page title, target page title, reason for move.

I'd also be for making requested moves easier in a similar fashion, because I do think we'd make Misplaced Pages easier to get into with more form usage, but I figure one step at a time. Hey man im josh (talk) 15:10, 22 December 2024 (UTC)

Last month @RaschenTechner mentioned that the current process is complicated. I admit to quickly dismissed the critique as I find it easy enough and the process is used in many other places. However on your mention here it has caused me to pause and think more about it. I think this does have some merit and your proposal is slightly better than theirs. Either way it would probably result in a fundamental change to how RM are created and managed. As well as impact bots. It’s unfortunate that each of these sorts of things are handled differently depending on the area, RPP, SPA, YFA, etc. But probably still worth consideration and talking about it. Although I’m not certain what would be required as it would be a significant change to workflow and possibly impact how things are accessed and researched historically. TiggerJay (talk) 15:44, 22 December 2024 (UTC)
I don't really see how this proposal would fundamentally alter much. OP doesn't seem to be talking about controversial moves, just generic cut-and-paste stuff. As far as I can see, all it would change if implemented is that the request button on WP:RM/TR would direct you to a Javascript form instead of a hidden note telling you how to list the RMassist template. Nohomersryan (talk) 01:56, 23 December 2024 (UTC)
@Nohomersryan: That is indeed my primary intent with this, though I do also think we could make requesting moves which require discussion easier for newcomers than we currently do. Hey man im josh (talk) 13:34, 23 December 2024 (UTC)
On Twinkle under "XFD", there's an RM option with "Uncontroversial technical request" available. The whole RM capability is not mentioned at Misplaced Pages:Twinkle/doc, but the functionality is referenced at Wikipedia_talk:Twinkle/Archive_42#RM_requests. —Bagumba (talk) 10:09, 24 December 2024 (UTC)
not everyone installs twinkle by default though. It is worth looking into. I have some free time this holiday, I will look into this. – robertsky (talk) 12:07, 24 December 2024 (UTC)
Yes, this is where I'm at on the matter. I don't have an issue initiating these requests or RMs, but based on how much difficulty some users have, we have a hump that we can help them get over in order to help with retention and reduce cut and paste moves. Thanks @Robertsky, I appreciate it. Hey man im josh (talk) 12:41, 24 December 2024 (UTC)
Yes, I wasn't implying that Twinkle precludes a standalone solution. It was more FYI in case others weren't aware (I didn't even know the WP:RM/TR feature was on Twinkle). Best. —Bagumba (talk) 13:02, 24 December 2024 (UTC)

100+ thoughtless RMS by User:TheParties

User:TheParties filed more than 100 RMs yesterday on US colleges and universities , apparently wanting them all renamed according to the way they're referred to in sports coverage, with all the idiosyncratic inconsistencies inherent in that e.g. San Francisco State University → SFSU and California State University Channel Islands → CSU Channel Islands and California State University, Northridge → Cal State Northridge. All of these have been universally opposed on the various article talk pages e.g. -- and see also . Is there a way to snow close them all right now on a mass basis, before more editor time is wasted? From other comments at the last link this editor has been doing this in at least one other topic area, so it may be necessary to ban this editor from RMs completely before this is over. EEng 14:45, 23 December 2024 (UTC)

My first reaction was that it's sometimes blurry how to balance being bold with WP:CAREFUL. On the cautious side though, this user was also banned before with their sock 23prootie, and the last of that user's blocks was re: move warring. —Bagumba (talk) 09:54, 24 December 2024 (UTC)
I closed these a little while ago. Extraordinary Writ (talk) 10:38, 24 December 2024 (UTC)