Wikipedia:Move review
 |
| Formal review processes |
|---|
|
|
|
For RfCs, community discussions, and to review closes of other reviews: |
| Administrators' noticeboard |
| In bot-related matters: |
|
|
| Discussion about closes prior to closing: |
Move reviewis a process to formally discuss and evaluate a contested close of Wikipedia page move discussions, includingrequested moves(RM),categories for discussiondiscussions (CfD), andredirects for discussiondiscussions (RfD), to determine if the close was reasonable, or whether it was inconsistent with the spirit and intent of Wikipedia common practice, policies, or guidelines.
Prior to submitting a review of a page move's close, please attempt to resolve any issueson the closer's talk page.Seestep onebelow.
While the page move close is under review, any involved editor is free to revert any undiscussed moves of a nominated page without those actions being considered a violation ofWikipedia:No wheel warring.
What this process is not
[edit]This review process should be focused on the move discussion and the subsequent results of the move discussion, not on the person who closed the discussion. If you have ongoing concerns about a closer, please consult with the closer or post atWikipedia:Administrators' noticeboard/Incidents.Move review requests whichcast aspersionsor otherwiseattackother editors may be speedily closed.
Do not request a move review if someone hasboldlymoved a page and you disagree. Instead, attempt to discuss it with the editor, and if the matter continues to be unresolved, start a formalWP:RMdiscussion on the article's talk page.
Do not request a move review simply because you disagree with the outcome of a page move discussion. While the comments in the move discussion may be discussed in order to assess therough consensusof a close, this isnota forum to re-argue a closed discussion.
Disagreements withWikipedia:Requested moves/Closing instructions(WP:RMCI),WP:Article titles,theManual of Style,a naming convention or thecommunity norm of consensusshould be raised at the appropriate corresponding talk page.
CfDs[1]andRfDscan only be reviewed here if the relevant discussion was limited in scope to renaming; CfDs or RfDs[2]involving deletion should be reviewed atWikipedia:Deletion review.
Instructions
[edit]Initiating move reviews
[edit]Editors desiring to initiate a move review should follow the steps listed below. In the reason parameter, editors should limit their requests to one or both of the following reasons:
- [Closer] did not follow the spirit and intent ofWP:RMCIbecause [explain rationale here] in closing this requested move discussion.
- [Closer] was unaware of significant additional information not discussed in the page move discussion: [identify information here] and the discussion should be reopened and relisted.
Editors initiating a move review discussion should be familiar with the closing instructions provided inWP:RMCI.
Steps to list a new review request
[edit]| 1. |
Before requesting a move review:please attempt to discuss the matter with the closer of the page move discussionon the closer's talk page.Move review is a process that takes several days, sometimes weeks, to close. On the closer's talk page, you can probably resolve the matter much more quickly. There could have been a mistake, miscommunication, or misunderstanding, and a full, formal move review may not be needed. Such discussion also gives the closer the opportunity to clarify the reasoning behind a decision. If things don't work out, and you decide to request a review of the closure, please note in the review that you did first try discussing the matter with the closer. To clarify:You absolutely MUST attempt to discuss the matter with the closer FIRST,and give them a few days to respond. |
| 2. |
Follow this link to this month's logand paste the template skeletonat the topof the discussions (but not at the top of the page). Then fill inpagewith the name of the contested move page,rm_pagewith the name of the move discussion page if needed,rm_sectionif needed,closerandcloser_sectionwith the post-move discussion information, andreasonwith the reason why the page move should be reviewed. For example: Copy this template skeleton for most pages:
{{subst:move review list
|page=
|rm_page= <!--Not needed if the move discussion is on the talk page of the page-->
|rm_section= <!--Name of the section with the move request-->
|closer= <!--User name of editor who closed the move request-->
|closer_section= <!--Name of the section of closer's talk page where discussion took place-->
|reason=
}} ~~~~
If either the
are correctly filled in, the result will include a "Discussion with closer"link to that discussion. If the |
| 3. |
If you have not done so already, inform the closer of the Move review discussion by adding the following on their user talk page:
|
| 4. |
Leave notice of the move review in the same section as, but outside of and above the closed original move discussion. Use the following template: |
| 5. |
If the current month discussions are not already included in the discussion section below. Add the new log page to the top of theactive discussionssection.
|
| 6. |
The discussion with closer and notices required above are sufficient notification; you are not required to individually notify participants in the prior move discussion of the move review. However, if you individually notifyanyof them, you must individually notifyallof them by posting a message about the move review on each participant's respective user talk page. |
Commenting in a move review
[edit]In general, commenters should prefix their comments with eitherEndorseorOverturn(optionally stating an alternative close) followed by their reasoning. Generally, the rationale should be an analysis of whether the closer properly followedWikipedia:Requested moves/Closing instructions,whether it was within closer's discretion and reasonably interpretedconsensusin the discussion, while keeping in mind the spirit of Wikipedia policy, precedent and project goal. Commenters should be familiar withWP:RMCI,which sets forth community norms for closers of page move discussions.
If the close is considered premature because of on-going discussion or if significant relevant information was not considered during the discussion, commenters should suggestRelistfollowed by their rationale.
Commenters should identify whether or not they were involved or uninvolved in the RM discussion under review.
The closer of the page move under discussion should feel free to provide additional rationale as to why they closed the RM in the manner they did and why they believe the close followed the spirit and intent ofWP:RMCI.
Remember that move review is not an opportunity to rehash, expand upon or first offer your opinion on the proper title of the page in question – move review is not a do-over of theWP:RMdiscussion but is an opportunity to correct errors in theclosing process(in the absence of significant new information). Thus, the action specified should be the editor's analysis of whether the close of the discussion was reasonable or unreasonable based on the debate and applicable policy and guidelines. Providing evidence such as page views, ghits, ngrams, challenging sourcing and naming conventions, etc. to defend a specific title choice is not within the purview of a move review. Evidence should be limited to demonstrating that the RM closer did or did not follow the spirit and intent ofWP:RMCIin closing the page move discussion.
Closing reviews
[edit]A nominated page should remain on move review for at least seven days. After seven days, an uninvolved editor will determine whether aconsensusexists to either endorse the close or overturn the close. If that consensus is toOverturn Close,the MRV closer should take the appropriate actions to revert any title changes resulting from the RM close. If the consensus was torelist,the page should be relisted atWikipedia:Requested moves,Wikipedia:Categories for discussion,orWikipedia:Redirects for discussion.If the consensus is toEndorse Close,no further action is required on the article title. If the MRV closer finds that there isno consensusin the move review, then in most cases this has the same effect asEndorse Closeand no action is required on the article title. However, in some cases, it may be more appropriate to treat a finding of "no consensus" as equivalent to a "relist"; MRV closers may use their discretion to determine which outcome is more appropriate.
Use {{subst:move review top}} and {{subst:move review bottom}} to close such discussions.
Also, add a result to the{{move review talk}}template on the talk page where the original discussion took place, e.g.{{move review talk|date=April 24 2015|result=Closure endorsed}}.
Typical move review decision options
[edit]The following set of options represent the typical results of a move review decision, although complex page move discussions involving multiple title changes may require a combination of these options based on the specific details of the RM and MRV discussions.
| MRV closer's decision | RM closer's decision | Move review closed as | Status of RM after MRV close |
|---|---|---|---|
| 1. Endorse | Moved / Not moved | No action required | Closed |
| 2. Overturn | Not moved | Option 1: (If RM consensus is unclear or significantly divided) Reopen and relist RM | Open |
| Option 2: (If consensus to move to a new title is clear) Move title to new title and close RM | Closed | ||
| Moved | Move title back to pre-RM title, and reopen and relist RM if appropriate | Open | |
| 3. Relist | Moved / Not moved | Reopen and relist RM and if moved, move title back to pre-RM title | Open |
Notes
[edit]- ^Those that involve renames (Template:Cfr), for all other types of CFDs usedeletion review.
- ^Generally for those that don't involve any proposed or suggested deletion, where only the redirect's target was being discussed or if the redirect should be a disambiguation page, for other (even those that were retargeted where deletion was proposed or considered) use deletion review.
Active discussions
[edit]- England in the Late Middle Ages(talk|edit|history|logs|links|archive|watch) (RM) (Discussion with closer)
Closer appears to have weighed arguments contrary toWP:RMCI,giving equal weight to comments that are unsubstantiated opinion against those that are made with reference to prevailing P&G and evidence of usage.Cinderella157(talk)01:40, 26 November 2024 (UTC)
- Endorse(involved).The closer got it right, so no need to reargue the discussion about the names of time eras here. The essay RMCI has no function as a guideline, and is irrelevant because the closer knows their rules and regs.Randy Kryn(talk)15:08, 26 November 2024 (UTC)
- ButWP:DETCONdoes and the two are quite consistent.Cinderella157(talk)04:06, 27 November 2024 (UTC)
- Weak endorse(uninvolved)— Although I do concur that there was consensus to not move, the closer should have left a more comprehensive closing statement. Besides that, I do not see a problem.
- 𝚈𝚘𝚟𝚝(𝚝𝚊𝚕𝚔𝚟𝚝)19:08, 26 November 2024 (UTC)
- EndorseI think "no consensus" would have been a more precise result, but this is a move review. I do believe the evidence suggests that early and late should not be capitalised in most style guides and would have supported this option myself, but this is not a situation in which the evidence is so strong that we can discount the opinions of others. I also might suggest an RfC based on the suggestion that this should be standardised across the site.SportingFlyerT·C22:46, 26 November 2024 (UTC)
- Evidence of style guides was introduced by one editor. Of the six guides presented, they report one would cap, two would lowercase, one would probably lowercase and two were silent on the matter. Nonetheless, they opposed the move because they
[didn't] like the CMoS approach
- ie their conclusion was contradicted by the evidence presented. The evidence of usage in sources indicated by ngrams clearly shows a minority of capitalisation in both cases. The opinions of others (opposers) arepersonal opinionsnot supported by evidence and flatly contradicted by the relevant P&G.Cinderella157(talk)00:26, 27 November 2024 (UTC)
- Evidence of style guides was introduced by one editor. Of the six guides presented, they report one would cap, two would lowercase, one would probably lowercase and two were silent on the matter. Nonetheless, they opposed the move because they
- SportingFlyer,unless I'm mistaken it is standardized uppercased across the project, at least in the historical or geological eras. This RM was a poke at that, and the closer came to the correct conclusion.Randy Kryn(talk)01:00, 27 November 2024 (UTC)
- Endorse- There was both a numerical majority and a consistency reason for Not Moving. Maybe the numerical majority reflected the respect of the participants for the consistency in capitalization argument.Robert McClenon(talk)05:55, 28 November 2024 (UTC)
- Endorse– The oppose arguments in this RM could not be lightly discarded by a closer (WP:DISCARD), as requested by the nominator. Essentially, the opposers argued that the exception in bold at the top ofWP:NCCAPSapplies: "...unless the title is a proper name." This argument does not "flatly contradict established policy" and was correctly not discarded by the closer. A longer closing statement might've been nice and a no-consensus close would also have been okay, but the result is no different, so I endorse the close.Toadspike[Talk]14:41, 28 November 2024 (UTC)
- The established P&G goes on to tell us how to determine if something is a proper noun. It is not based on unsubstantiated opinion that is contradicted by evidence of usage.Cinderella157(talk)21:30, 28 November 2024 (UTC)
|
|---|
| The following is an archived debate of themove reviewof the page above.Please do not modify it. |
|
Estar8806 closed the discussion based onWP:SNOW.This is the first move request since 2018, and it was closed after less than twelve hours. The closure has been treated like a vote, with the fact all comments before the closure opposed the move being used as evidence that it had no chance of succeeding. I believe that estar8806 has also misunderstood the 'support' argument. While it is unlikely that the page would have been moved, SNOW requires certainty and I do not think this threshold was met. At the very least, leaving the discussion open for a week or so would potentially have allowed a more in-depth discussion of the possible names of the article to take place.A.D.Hope(talk)10:01, 12 November 2024 (UTC)
|
| The above is an archive of themove reviewof the page listed in the close of this review.Please do not modify it. |
This was closed asnot moved,without any actual consensus to not move. The opposing side was asking for consensus to make an exception to the guideline, and while that kind of consensus can sometimes be found if the numbers are lopsided enough, it can't be created out of nothing in an evenly-matched discusssion.* Pppery *it has begun...16:21, 8 November 2024 (UTC)
- Overturn tono consensusorrelist(uninvolved): there's no consensus here for ano moveclosure, per appellant; especially in the case of what—at least to me—appear to be stronger policy arguments, for the exact scenario as described above.Bobby Cohn(talk)18:43, 8 November 2024 (UTC)
Endorse-ish.Overturn to movedI think "no consensus" is probably a more precise result, but for moves, I view "no consensus to move" and "not moved" as equivalent, whereas an AfD a "no consensus" is quite a bit weaker than a "keep." Also, after reviewing the policy guidelines, I am not completely convinced this is a situation where those wishing for a move have a stronger policy argument, as the guidelines are vague about this specific scenario.SportingFlyerT·C18:48, 8 November 2024 (UTC)
- I went back and looked atWP:PRIMARYFILMagain, and I think I mis-interpreted it the first time: I believe it says if the film's name is not the primary topic, itmustbe disambiguated,even ifit is far and away the primary topicas far as films are concerned.I'm not sure I agree, but the last discussion strongly opposed changing this. In that case there's not much room here for argument, even though the discussion itself was clearly a "no consensus."SportingFlyerT·C06:30, 10 November 2024 (UTC)
- The problem with those endorsing this discussion is that this is one of the areas where policy is - I wouldn't say it's necessarily clear, but it is specific perWP:PRIMARYFILM.Simply looking at the consensus without looking at whether the arguments were in line with what we traditionally do in this situation is not the correct way to approach this move review.SportingFlyerT·C19:59, 12 November 2024 (UTC)
- Also, the admission by the closer this was their first RM close may further demonstrate an obscure but agreed upon rule wasn't correctly applied here.SportingFlyerT·C01:31, 27 November 2024 (UTC)
- The problem with those endorsing this discussion is that this is one of the areas where policy is - I wouldn't say it's necessarily clear, but it is specific perWP:PRIMARYFILM.Simply looking at the consensus without looking at whether the arguments were in line with what we traditionally do in this situation is not the correct way to approach this move review.SportingFlyerT·C19:59, 12 November 2024 (UTC)
- Endorse.Advise the nominator to put more rationale into the nomination statement. If you don’t, it is often a trainwreck, and a net waste of time.SmokeyJoe(talk)21:59, 9 November 2024 (UTC)
- Regarding others’!votes to overturn, I share a feeling of dissatisfaction with the result, but I dont agree there is a consensus to move evident in the discussion. It could be relisted, but I think it should wait two months for a better nomination.SmokeyJoe(talk)09:55, 10 November 2024 (UTC)
- Feedback noted. I should have done a better job explaining that there.* Pppery *it has begun...02:56, 12 November 2024 (UTC)
- Regarding others’!votes to overturn, I share a feeling of dissatisfaction with the result, but I dont agree there is a consensus to move evident in the discussion. It could be relisted, but I think it should wait two months for a better nomination.SmokeyJoe(talk)09:55, 10 November 2024 (UTC)
- Overturn to moved<uninvolved>.Personally I disagree withWP:PRIMARYFILM,but it very specifically prohibits incomplete disambiguation evenwhen it's otherwise allowed,and so farthere's been consensus against changing that.Perthe closing instructions,closers generally have to avoid a title that's "out of keeping with naming conventions...regardless of how many of the participants support it". Changes to the guideline should be made by RfC, not RM.Extraordinary Writ(talk)22:52, 9 November 2024 (UTC)
- If you think there's no consensus, the logical thing to do would be to relist so a consensus can form. I'd support that as an alternative.Extraordinary Writ(talk)06:40, 28 November 2024 (UTC)
- Endorse.< uninvolved >Agree with editor SmokeyJoe above.In this case"not moved" is synonymous with "no consensus", and the latter may or may not have been a more precise closure decision. Again, in this case the result is the same whether "no consensus" or "not moved" is used; however, that isnot alwaysthe case. There have been exceptions. Open for two weeks I see no reason to relist, as it is doubtful that the outcome would be altered. I would recommend that editors strengthen their arguments to move the page, and try again in a few months to garner consensus for a rename. I think that this closure was then a reasonable end to the survey and discussion.P.I. Ellsworth ,ed.put'er there13:17, 12 November 2024 (UTC)
- Endorse< uninvolved >.The nominator and proponents of the move did not make a compelling case. Maybe it should have been closed as no consensus, but that's really splitting hairs. ~~Jessintime(talk)17:39, 12 November 2024 (UTC)
- Endorse.The primary film guideline is in conflict with the broader sitewide guideline allowing partially disambiguated titles for very clear cases. And mamy participants in this debate felt this warranted that and that the sitewide guideline should be applied in this case. As above, the discussion could and probably should have been closed as no consensus, but the practical difference between those outcomes is negligible. —Amakuru(talk)07:43, 17 November 2024 (UTC)
- I really don't agree here - none of those opposing appliedWP:PRIMARYFILMcorrectly, once you understand the premise - the argument is that is the primary film title of all of the films named Carousel, andWP:PRIMARYFILMsays to disambiguate that with a year. There's no specific reason argued by those opposing whyWP:PRIMARYFILMshouldnotapply. WhileWP:PRIMARYFILMdoes go against the gravity of everything else on the site, the consensus has been reaffirmed relatively recently. Unlike notability, move reviews are an area where the rules are a bit more clear cut...SportingFlyerT·C03:46, 19 November 2024 (UTC)
- Overturn to no consensus.I agree with Amakuru. Although I've bolded it as "overturn", I agree with the remarks that there's no difference here for practical purposes.Adumbrativus(talk)08:27, 17 November 2024 (UTC)
- Endorse(the closer)— I can agree with almost everyone here that there really is not much of a difference betweennot movedandno conensus,and I'd consider them synonyms with each other. As this was my first RM closure, I didn't really give any weight between the two. That said, I still found consensus to not move.
- 𝚈𝚘𝚟𝚝(𝚝𝚊𝚕𝚔𝚟𝚝)14:28, 18 November 2024 (UTC)
- Endorse(involved),'not moved' (another term for 'no consensus') reflects an accurate result of the discussion.Randy Kryn(talk)09:20, 26 November 2024 (UTC)
- Overturn to No Consensus- So what? There was no consensus. But No Consensus has the same effect as Not Moved.Robert McClenon(talk)05:50, 28 November 2024 (UTC)
Perspiration(closed)
[edit]
|
|---|
| The following is an archived debate of themove reviewof the page above.Please do not modify it. |
|
When including all comments from the initial discussion, regardless of whether they were directly about the proposal, the vote was evenly split at 50/50 (4:4). The closing message was 'no consensus', which is accurate based on the numbers alone. However, sinceWP:RMCIrequires evaluating arguments as well as numbers, I will briefly summarize these: opposers preferred 'perspiration', feeling it sounded more encyclopedic (WP:TONE) and less ambiguous than 'sweat', referring to both the fluid and the process, thereby avoiding confusion about the article's focus. Supporters, on the other hand, emphasized the statistical prevalence of'sweat' over 'perspiration'(WP:COMMONNAME,WP:MEDTITLE), refuted the claim that 'sweat' describes a different phenomenon than 'perspiration' when referring to the fluid, and advocated for a clear focus on either the fluid or the process. Overall, this decision appears to contrast factual arguments (statistics) with personal preferences. –Tobias(talk)13:00, 4 November 2024 (UTC)
|
| The above is an archive of themove reviewof the page listed in the close of this review.Please do not modify it. |
Israel–Hamas war(closed)
[edit]
| |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| The following is an archived debate of themove reviewof the page above.Please do not modify it. | |||||||||||||||
|
There was a broad consensus for a move of the title away from Hamas and towards Gaza based on increasing and converging use of Gaza by RS. While initially a move toIsrael-Gaza warfound mixed support, I proposed a compromise fora movetoGaza War,which found great support among editors as a middle ground solution. Despite this the move was closed as no consensus, and there wereattemptsby several editors to discuss a rereview with the closing editor, to which they did not agree with. To add to that,three editorswho had voted against were found to be sockpuppets. This really needs a rereview to accurately reflect the established consensus.Makeandtoss(talk)10:44, 4 November 2024 (UTC)
Note some users!voted in both sections but most only!voted in one section.VR(Pleasepingon reply)17:48, 4 November 2024 (UTC)
References
| |||||||||||||||
| The above is an archive of themove reviewof the page listed in the close of this review.Please do not modify it. |
For clarity, this request was ultimately closed byUSER:Vpab15.It wasinitiallyclosed (in good-faith) byUSER:Asukite,andre-opened at my request.USER:Vpab15ultimately closed it (in good-faith) ostensibly on-behalf ofUSER:Asukite,with a consensus of 3 (three) in-favor of KEEPING "AIM-174B" and 2 (two) in-favor of moving to "AIM-174." (full disclosure, I am the original author of the AIM-174 article)My position is that the article should be MOVED/REVERTED to “AIM-174.”My rationale for a MR:
1. "AIM-174 air-to-air missile"was movedto "AIM-174B",in good-faith, but without discussion, as perWP:RM.WP:BOLDdoes not exempt one from WP. At the very least the page should be reverted, perWP:RMUM.This was my rationale for attempting to move it on my own, originally, but was unable to do so for technical reasons, and ultimately beganthismove discussion. I recognize that "air-to-air missile" is unneeded due toWP:CONCISE.
2. The term “AIM-174” is freely-used -- admittedly alongside "AIM-174B" -- among sources[1][2][3]and is easily recognizable.
3.WP:CONCISEandWP:PRECISEemphasize titles should be concise and precise, obviously. The title “AIM-174” is sufficiently precise to cover the entire missile family, including the AIM-174B variant. It avoids unnecessary complexity and redundancy.
4.WP:CONSISTENT,virtually all missiles -- andALLU.S. air-to-air-missiles -- use the base model as their article title. While the AIM-174B is the only known operational variant, does that mean we should change the AIM-54 Phoenix article to "AIM-54C," given that, at the end of the Phoenix's life, it was the only operational variant? PerWP:CONSISTENT,see:AIM-4 Falcon,AIM-26 Falcon,AIM-47 Falcon,AIM-9 Sidewinder,AIM-7 Sparrow,AIM-54 Phoenix,AIM-68 Big Q,AIM-82,AIM-95 Agile,AIM-97 Seekbat,AIM-120 AMRAAM,AIM-132,AIM-152 AAAM,AIM-260
5.WP:DISAMBIG,WP:PRECISE;the current title “AIM-174B” may imply that there are multiple significant variants that require disambiguation. However, the primary subject of the article is the AIM-174 missile as a whole, with the AIM-174B being a variant, in-line withUS missile naming conventions.Using “AIM-174” as the title encompasses all possible variants without the need for additional disambiguation or future discussion.FOR EXAMPLE: All AIM-9Xs are AIM-9s. All AIM-7Cs are AIM-7s.etc.
6. No one has made any attempt at editing the body or lead, which opens with "AIM-174." Indeed, as it stands currently, "AIM-174B" is not mentioned until the end of the intro. (and intro which, in full disclosure, I wrote) Indeed, I would argue that as acompromise,we could move the mention of the "AIM-174B" up to within the first sentence or two.
MWFwiki(talk)23:40, 30 October 2024 (UTC)
References
- Involved editor comment- I just want to note that I regret reverting my closure in this case as it has likely made the situation worse and now involved another editor who was inevitably dragged into this - thanks, in any case, and sorry for that.
- I won't offer any opinion as to the close, but will note that of the prevalent voices in the discussion, there was an imbalance in civility and a clear lack of consensus.ASUKITE03:34, 31 October 2024 (UTC)
- Overturn to no consensus, move to AIM-174This is a very tricky discussion, because the original page was "AIM-174 air-to-air missile", it was moved unilaterally to "AIM-174B" recently in September (note the suffix), and the move discussion was to move it from "AIM-174B" to "AIM-174." In short, we have two different moves here: whether to remove "air-to-air missile" and whether the suffix should be used. In terms of dropping the "missile" part, I think there's clear consensus in that discussion to shorten the name. I donotsee any consensus as to whether it should be AIM-174 or AIM-174B, though, but rather two opposing arguments without a clear policy winner. As a result, it should revert to whatever the status quo is, which in this case would be "AIM-174" without the "missile" part. If anything, I'm not sure discussion doesn't favour the shorter title - one opposer wants to maintain the status quo, but there isn't a status quo, and one of the non-specifically-voting commenters says it's unnecessary without being completely supportive of it.SportingFlyerT·C05:08, 31 October 2024 (UTC)
- I think your analysis of the separation of the problems with the RM identifies the issue I have parsing the RM and this MRV. I do think that there are two issues that may have individually been separated and could be read as consensus against the longer disambiguator but no consensus for B/no B. I take issue with the participating mover's interpretation of policy "Unfortunately for you, a no consensus decision will result in this article staying here"in the RM, and would instead endorse your idea that aligns with policy, that a no consensus would take us back the original title, sans extra disambiguatotr. This is definitely a policy argument that is splitting hairs, but I think you've correctly identified the issues at play here.Bobby Cohn(talk)14:52, 31 October 2024 (UTC)
- Yes, I saw that and completely disagree that a "no consensus" result would validate a recent page move.SportingFlyerT·C17:26, 1 November 2024 (UTC)
- I'm also surprised other people think therewasconsensus here.SportingFlyerT·C07:15, 7 November 2024 (UTC)
- Not the strongest consensus but the view that the close was not outside the scope ofWP:RMCIis reasonable and good faith interpretation. The outcome could have swung either way here, to be honest. I've refrained from bolding my opinion here as well. You win some, you lose some. The view that I wanted to make sure I endorsed in my reply to your!vote above was the idea that the procedure may be complicated on the reversal and I stand by that, in the event the decision is reversed or vacated, thatshould bethe proper policy procedure.Bobby Cohn(talk)15:40, 7 November 2024 (UTC)
- I'm also surprised other people think therewasconsensus here.SportingFlyerT·C07:15, 7 November 2024 (UTC)
- Yes, I saw that and completely disagree that a "no consensus" result would validate a recent page move.SportingFlyerT·C17:26, 1 November 2024 (UTC)
- I think your analysis of the separation of the problems with the RM identifies the issue I have parsing the RM and this MRV. I do think that there are two issues that may have individually been separated and could be read as consensus against the longer disambiguator but no consensus for B/no B. I take issue with the participating mover's interpretation of policy "Unfortunately for you, a no consensus decision will result in this article staying here"in the RM, and would instead endorse your idea that aligns with policy, that a no consensus would take us back the original title, sans extra disambiguatotr. This is definitely a policy argument that is splitting hairs, but I think you've correctly identified the issues at play here.Bobby Cohn(talk)14:52, 31 October 2024 (UTC)
- Endorse.The RM starter was not happy with a certain element of a bold move, while the other part was non-contentious. He contested said element of the move and failed, as the consensus was to keep the specific contested change made to the name. The bold move was therefore taken over by a consensus at RM: implicit consensus concerning the non-contentious element + explicit consensus concerning the remaining contentious element = consensus for the entire thing. The closer correctly recognized this.—Alalch E.23:39, 3 November 2024 (UTC)
- Endorse.It's easy to see both sides of this issue, and I tend to agree with Alalch E. that the closer correctly read the RM survey and discussion. This closure was reasonable and in line with theclosing instructions.P.I. Ellsworth ,ed.put'er there05:00, 4 November 2024 (UTC)
Nationality law of North Macedonia(closed)
[edit]
|
|---|
| The following is an archived debate of themove reviewof the page above.Please do not modify it. |
The move request for renamingNationality law of North Macedoniato "North Macedonian nationality law" was closed as not move, (although with votes 3-2 in favour of my proposal), and the closer relied the decision on a statement ofWP:MOSMACthat is not part of the community consensus reached in the2019-RFC.This statement tells usArticle names, categories, and templates should avoid adjectival use altogether. There are two main problems with this statement and the closure of the move request: 1) A recent move request for renamingMacedonian denarto "Denar of North Macedonia" was rejected, and the followed-up move review was rejected unanimously, and none of the editors was convinced about the above statement, which I include in the move review. The two different decisions made in these two recent move requests tell us that decisions are made without considering wikipedia policiesWP:NCand guidelinesWP:MOSMAC.If there is a guideline that tells us to avoid adjectives in article titles, thenMacedonian denarshould be renamed to "Denar of North Macedonia". If this is not true, thenNationality law of North Macedoniashould be renamed to "North Macedonian nationality law". Either way is okay, but my brain cannot accept double standards by pointing to the same guideline/exception/statement. One of the participants in the two move requests opposed Denar of North Macedonia but then strongly defended Nationality law of North Macedonia, pushing double standards in a non-scientific way. 2) I will share here some research that I did and already discussed with the closer and shows that the closer was trapped (me too as well a few weeks ago) by a statement, the validity of which has been raised inTalk:2019 North Macedonian presidential election#Article title moveand includes a discussion about the statement:Article names, categories, and templates should avoid adjectival use altogetherstarted by an editor, FlavrSavr, who was involved in the RFC 2019 and who opposed "North" in all cases (shown in the votes in all questions). Editors Teratix and Number 57 participated in the long discussion with FlavrSavr. FlavrSavr said:The actual policy clearly states that Article names, categories, and templates should avoid adjectival use altogether. and specifies in which cases "North Macedonian" may be used. Number57 said:Then whoever has formulated the policy has ignored the outcome of the RfC. Perhaps this needs to be flagged up at WP:AN or somewhere, as it's not really acceptable for a clear outcome from a community discussion to be ignored when translating it into policy. FlavrSavr then responded to Number 57 with a long message that includes:The sentence in question was proposed by me and inspired by Argean's and other comments in the RfC - this really was a no-brainer for most of us as it seems to be a natural and neutral resolution, and this wasn't opposed by anyone. MJL (main contributor ofWP:MOSMAC) joined the discussion and added:Actually, on a second read through, I have become very concerned by Number 57's comments. Future Perfect at Sunrise joined the discussion and added:The sentence in question... was not covered by the original RfC but was written into the draft unilaterally by MJL – certainly with the best of intentions.and...And if there are groups of articles where local editors consider adjectival titles preferable for WP:CONSISTENCY reasons, we definitely have a problem and I'm not sure at all we should treat that WP:NCMAC sentence as authoritative. qedk (one of the three editors in the closing of RFC 2019) commented:Since, the LOCALCONSENSUS surrounding the inclusion of that singular sentence has certainly changed, either it should be removed, or reframed in a manner, where it doesn't sound like policy. And given, WP:LOCALCONSENSUS explicity states — Consensus among a limited group of editors, at one place and time, cannot override community consensus on a wider scale, this particular statement cannot be held above the policy formed at the behest of the community. With thanks. Argean joined the discussion and said:This particular sentence was proposed by FlavrSavr to be added in Future Perfect at Sunrise's first draft and was never questioned by anybody until now. To remind you that FlavrSavr was involved in the RFC 2019 and opposed "North", so the idea of adding this special statement toWP:MOSMACwas a way to avoid the community consensus as much as possible and was proposed by an editor who disagrees with "North Macedonian", and this was done only after the RFC 2019. Not fair at all in my opinion. One of the last comments of this discussion was by qedk,who is one of the three closers of the RFC 2019. qedk said:To note for posterity's sake, the post-RfC drafting was mostly done by FPaS and MJL, and with SilentResident, Argean, Khajidha, FlavrSavr chipping in. Now, if out of those we already have two editors (FPaS and Khajidha in contention, on different things), you cannot say that the LOCALCONSENSUS persists. Noting again, that Teratix and Number 57 do not see it as an accurate summarization as well. I do not mean to question it when you say that it's in good intent and that it's meant to prevent conflicts but what I am saying is, you cannot have it override community consensus, which in this case, was clear and not a LOCALCONSENSUS. All these prove that the statement about articles has been disputed by multiple editors already, but was not removed fromWP:MOSMACalthough suggested by the closing panel of the RFC 2019. The argument of the closer of this move request about this statement that doesn't allow adjectives in titles is incorrect, and couldn't be correct becauseWP:LOCALCONSENSUScannot override community consensus achieved in2019-RFC,in whichThe closing panel agrees that there is consensus forBoth "North Macedonian" and "... of North Macedonia", where a similar form would be used for other countries. e.g. the North Macedonian Government or the Government of North Macedonia.forState-associated and other public entities. The second argument of the closer about implicit consensus on theWP:MOSMACguidelines (discussed in the talk page) because nobody removed this incorrect sentence against community consensus is also incorrect because we have multiple examples of article titles that use the adjective, seeNorth Macedonian passport,2019 North Macedonian presidential election,2020 North Macedonian parliamentary election,2024 North Macedonian presidential election,and2024 North Macedonian parliamentary election.As already mentioned in the move review for Macedonian denar, the reasonWP:MOSMACwas used in these examples but not in Macedonian denar and Nationality law of North Macedonia is the lack of experienced editors and the law participation that are eliminated by editors with double standards. The experienced editors @Number 57and @Teratixhave been consistently usingWP:MOSMACfor years in pages of North Macedonian elections, and I don't understand why we need to use double standards enforced by a single editor in other pages. Nationality law of North Macedoniais completely inconsistent with all other pages ofCategory:Nationality_lawand should be moved all in line withWP:CONSISTENTandWP:MOSMACand2019-RFCcommunity consensus. Thank you all for your time. Cheers!Open Free Eye(talk)22:44, 30 October 2024 (UTC)
|
| The above is an archive of themove reviewof the page listed in the close of this review.Please do not modify it. |
Macedonian denar(closed)
[edit]| The following is an archived debate of themove reviewof the page above.Please do not modify it. |
|
I opened a move request forMacedonian denarand proposed to move it toDenar of North Macedonia(like in the case ofCategory:Nationality_lawwhere North Macedonia follows a different format) or to North Macedonian denar which is the most common name backed-up with reliable sources -- 70%. The move request was closed today as "not moved". In my humble opinion, multiple wikipedia policies have been overlooked. I list my arguments below. 1. Wikipedia tells us whatConsensusmeans: Consensus on Wikipedia neither requires unanimity (which is ideal but rarely achievable),nor is it the result of a vote. and Wikipedia tells us how consensus is formed: editors open a section on the associated talk page and try to work out the dispute through discussion, usingreasons based in policy,sources,andcommon sense;they can alsosuggest alternative solutions or compromises that may satisfy all concerns. 2. North Macedonia's policiesWikipedia:Naming conventions (Macedonia)#Adjectival form of North Macedoniatell us what name to use: However, in line with the reliable sources, adjectives may still be used when referring to such institutions in generic terms (e.g. the Greek and North Macedonian prime ministers), especially where the possessive form would be grammatically cumbersome or unnatural. While reliable sources continue to use both plain "Macedonian" and "North Macedonian" in such contexts,the majority opinion in the RfC favored the fuller form, "North Macedonian". Article names, categories, and templates should avoid adjectival use altogether. The use of neutral formulations such as "of North Macedonia", "in North Macedonia," etc. is preferred. In my humble opinion, the general wikipedia's policies about consensus, and the specific North Macedonia's policies make clear that the editors have set default rules in favour ofNorth Macedonian denar(or perhapsDenar of North Macedoniabecause of the last clause). 3. On the top of the already clear consensus and naming policies, the talk page ofMacedonian denarhides an old move request that is backed-up by a long listTalk:Macedonian denar/Archive 2of reliable sources that was collected by users who agreed and opposed, and the closer found a clear consensus, and I quote here the summary of their study: List of Reliable Sources (North Macedonian denar: 135 findings, North Macedonia denar: 57 findings, Macedonian denar: 89 findings) Therefore, North Macedonian denar isWP:COMMONNAMEand this is backed-up with reliable sources that show:70% of reliable webpages include "North"(48% is North Macedonian denar) and only 30% use "Macedonian denar". 4.WP:COMMONNAMEtells us what common name means: Generally, article titles are based on what the subject is called inreliable sources.When this offers multiple possibilities, editors choose among them by considering several principles: the ideal article titleprecisely identifies the subject;it isshort,natural,distinguishable and recognizable;andresembles titles for similar articles. North Macedonian denaris the most common name in reliable sources (70%), precisely identifies the currency of North Macedonia, it is as short as the name of the country, it is the natural adjective in the english language, it is the best distinguishable and recognizable option, and it resembles titles for similar articles, and the most important criterion is that "North Macedonian" was agreed for State-associated and other public entities inWikipedia:Naming conventions (Macedonia)#Adjectival form of North Macedonia. 5. Similar discussions have been made for years under the talk pages of2019 North Macedonian presidential election,2020 North Macedonian parliamentary election,2024 North Macedonian parliamentary election.There the wikipedia policies for North Macedonia naming were used, because there were experienced editors who protected the pages. In the case ofMacedonian denar,the lack of experienced editors involved in the discussion for the move request leads to a messy situation. 6. To see the issue from a different point of view. If an editor thinks there is no clear consensus forNorth Macedonian denarshould wonder if there is clear consensus forMacedonian denar.North Macedonia's policies tell us the default rules to use unless a clear consensus is made against them. I don't see any clear consensus forMacedonian denar,I see only 30% using plain Macedonian. Clear consensus perhaps means 80% or at least 70% but definitely not 30%. 7. To close this discussion, I am convinced that all wikipedia policies suggestNorth Macedonian denar,and if someone believes there is no clear consensus (because of counting votes instead of using policies and sources) then the answer is found at a wikipedia policy fromWikipedia:Naming conventions (Macedonia)#Adjectival form of North Macedonia. In the absence of a clearer consensuson which of the two to prefer, it is recommended touse the longer formwhere ambiguity might be an issue(especially on first introducing the topic). Sorry for the long comment, I had to do some research to find this information and perhaps it is worth sharing it with editors who are interested but perhaps not aware of it. Thank you everyone for taking the time to read this. Hopefully, after this discussion wikipedia will be improved. Cheers!Open Free Eye(talk)21:00, 13 October 2024 (UTC)
Comment to All:Two editors have commented so far and none of them responded to my quotes for wikipedia policies. We continue playing the same game that started with the move request. People don't see, people don't know, people don't understand, people have all these skills required to overlook wikipedia policies. As a non-experienced user I accept my mistake and the wrong way of expressing my thoughts in the move request, and I opened this move review as suggested by the closer. If editors intentionally avoid discussing wikipedia policies, I recommend to everyone to close this move review ASAP, because we are wasting our time, and we don't help wikipedia becoming better. By avoiding discussing if the closure was correct while ignoring the wikipedia policies written above gives a bad example to editors who have a bias, and from my personal experience I can tell you that you don't help me to learn how I can contribute to wikipedia if its policies are not used. I am not here to bother people, and my experience so far is too much "bureaucracy". People play ping pong and move the ball from the one side to the other without answering my question which by the way is very simple: why North Macedonia's policiesWikipedia:Naming conventions (Macedonia)#Adjectival form of North Macedoniathat are in favour of "North" are not used for the currency of the country, while reliable sources confirm 70% use "North"? If experienced, not biased, and uninvolved editors don't know the answer, then who knows? Please help me! Cheers!Open Free Eye(talk)05:38, 16 October 2024 (UTC)
Consensus among a limited group of editors, at one place and time, cannot override community consensus on a wider scale. For instance, unless they can convince the broader community that such action is right, participants in a WikiProject cannot decide that some generally accepted policy or guideline does not apply to articles within its scope
|
| The above is an archive of themove reviewof the page listed in the close of this review.Please do not modify it. |
| Year | Jan | Feb | Mar | Apr | May | Jun | Jul | Aug | Sep | Oct | Nov | Dec |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2024 | Jan | Feb | Mar | Apr | May | Jun | Jul | Aug | Sep | Oct | Nov | Dec |
| 2023 | Jan | Feb | Mar | Apr | May | Jun | Jul | Aug | Sep | Oct | Nov | Dec |
| 2022 | Jan | Feb | Mar | Apr | May | Jun | Jul | Aug | Sep | Oct | Nov | Dec |
| 2021 | Jan | Feb | Mar | Apr | May | Jun | Jul | Aug | Sep | Oct | Nov | Dec |
| 2020 | Jan | Feb | Mar | Apr | May | Jun | Jul | Aug | Sep | Oct | Nov | Dec |
| 2019 | Jan | Feb | Mar | Apr | May | Jun | Jul | Aug | Sep | Oct | Nov | Dec |
| 2018 | Jan | Feb | Mar | Apr | May | Jun | Jul | Aug | Sep | Oct | Nov | Dec |
| 2017 | Jan | Feb | Mar | Apr | May | Jun | Jul | Aug | Sep | Oct | Nov | Dec |
| 2016 | Jan | Feb | Mar | Apr | May | Jun | Jul | Aug | Sep | Oct | Nov | Dec |
| 2015 | Jan | Feb | Mar | Apr | May | Jun | Jul | Aug | Sep | Oct | Nov | Dec |
| 2014 | Jan | Feb | Mar | Apr | May | Jun | Jul | Aug | Sep | Oct | Nov | Dec |
| 2013 | Jan | Feb | Mar | Apr | May | Jun | Jul | Aug | Sep | Oct | Nov | Dec |
| 2012 | Jan | Feb | Mar | Apr | May | Jun | Jul | Aug | Sep | Oct | Nov | Dec |
 | Search Move review archives
| |