This is an old revision of this page, as edited by Locke Cole (talk | contribs) at 05:27, 29 September 2024 (→Attempted assassination of Donald Trump in Florida: Reply). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.
Revision as of 05:27, 29 September 2024 by Locke Cole (talk | contribs) (→Attempted assassination of Donald Trump in Florida: Reply)(diff) ← Previous revision | Latest revision (diff) | Newer revision → (diff)< 2024 August | Move review archives | 2024 October > |
---|
2024 September
Attempted assassination of Donald Trump in Florida
- Attempted assassination of Donald Trump in Florida (talk|edit|history|logs|links|archive|watch) (RM) (Discussion with closer)
WP:RMCI, Further, any move request that is out of keeping with naming conventions or is otherwise in conflict with applicable guideline and policy, unless there is a very good reason to ignore rules, should be closed without moving regardless of how many of the participants support it.
The relevant naming convention is WP:NCE, which fairly explicitly limits the omission of years from the title (WP:NOYEAR) to matters that can be evaluated with historic perspective
. Such perspective does not exist after just a couple of weeks. Also consider WP:BLPCRIME (raised at the RM as well) which seems to unambiguously disallow this type of article title where we name a BLP as we have in this instance. Additionally, WP:BADNAC #2, given the contentious nature of this subject, an administrator really should have been the one to close this. Finally, User_talk:Compassionate727#Non-admin_closures where the closer was asked to not close discussions that could be contentious in the future (from May 1, 2024). At best, the outcome should be "no consensus" with no prejudice to starting a new RM that considers existing naming conventions and content policies. —Locke Cole • t • c 05:15, 26 September 2024 (UTC)
- Relist due to bad non-admin close. Robert McClenon (talk) 05:55, 27 September 2024 (UTC)
- Relist while I can see where the closer's head was at with the closure. I would agree with the nom that an nc close without prejudice, as in just a quick read through this discussion looks like a WP:TRAINWRECK to me.--estar8806 (talk) ★ 20:07, 27 September 2024 (UTC)
- Endorse (uninvolved) as a reasonable interpretation of consensus. Also I note that WP:BADNAC is an essay (i.e. the opinion of one or more individual editors) and is as such not a consensus-backed guideline or policy. In my opinion, adminship shouldn't grant a user any more ability to close contentious RMs than anyone else. Per WP:ADMIN, Admins are no more important than any other editor, they just have access to more tools. Bensci54 (talk) 01:54, 28 September 2024 (UTC)
Admins are no more important than any other editor
More important, agreed. But admins are also typically much more versed in how to interpret consensus and are aware of issues such as WP:LOCALCON and are more likely to follow the instructions at WP:RMCI. WP:IAR exists, but no argument was made at the RM that would have merited invoking IAR. —Locke Cole • t • c 05:59, 28 September 2024 (UTC)
- Endorse (uninvolved) Just skimming through the RM, 5 different editors (including Locke Cole and estar8806 who both commented here) mentioned WP:NOYEAR/WP:NCE or WP:BLPCRIME, while at least 30 different editors supported a title that included the words 'assassination attempt'. The NOYEAR/NCE/BLPCRIME arguments were made early on in the discussion and did not gain traction, meanwhile many of the latter votes were to support the move. The RM wasn't contentious and the closer did not supervote, so these vague handwaves at the WP:BADNAC essay aren't convincing. Some1 (talk) 02:42, 28 September 2024 (UTC)
- @Some1 The principle that the quoted section from WP:RMCI is based upon is WP:LOCALCON, which is sitewide policy (and has made it into the principle of an RFAR). Would you like to adjust your !vote in light of this? —Locke Cole • t • c 05:58, 28 September 2024 (UTC)
- WP:RMCI is an explanatory essay, and this RM closure does not conflict with 'global consensus', so no, I'm not changing my !vote. Some1 (talk) 11:00, 28 September 2024 (UTC)
- WP:NCE is not an essay, and neither is WP:LOCALCON. —Locke Cole • t • c 15:04, 28 September 2024 (UTC)
- WP:NCE/WP:NOYEAR says
Some articles do not need a year for disambiguation when, in historic perspective, the event is easily described without it.
The month or days should not be used in the title unless other descriptors are insufficient to establish the identity of the incident...
And more importantly,As this is a judgement call, please discuss it with other editors if there is disagreement.
The please discuss it with other editors part is the Requested Move, and only three editors (including you and estar8806) cited WP:NCE/NOYEAR in the RM, while a vast majority of the participants in the RM supported titles that omitted the year. Some1 (talk) 16:26, 28 September 2024 (UTC)please discuss it with other editors if there is disagreement
Neat. Can you point to comments in the RM that addressed WP:NOYEAR? —Locke Cole • t • c 05:27, 29 September 2024 (UTC)
- WP:NCE/WP:NOYEAR says
- WP:NCE is not an essay, and neither is WP:LOCALCON. —Locke Cole • t • c 15:04, 28 September 2024 (UTC)
- WP:RMCI is an explanatory essay, and this RM closure does not conflict with 'global consensus', so no, I'm not changing my !vote. Some1 (talk) 11:00, 28 September 2024 (UTC)
- @Some1 The principle that the quoted section from WP:RMCI is based upon is WP:LOCALCON, which is sitewide policy (and has made it into the principle of an RFAR). Would you like to adjust your !vote in light of this? —Locke Cole • t • c 05:58, 28 September 2024 (UTC)
Symphony station (Sound Transit)
- Symphony station (Sound Transit) (talk|edit|history|logs|links|archive|watch) (RM) (Discussion with closer)
The WP:COMMONNAME in use by reliable third-party sources such as the Seattle Times (1, 2, 3), for the past 30+ years, is "Symphony Station" capital-S proper noun.
This common name went completely unchallenged in the requested move. Not a single WP:SOURCE was provided showing "Symphony" or "Symphony station" usage.
We have a guideline at WP:USSTATION to specifically cover this case. The top item in the naming convention is Generally, U.S. station articles should be titled by their common name, followed by "station" if not already part of the name.
It goes on to say In cases where the word "Station" is part of the proper name, it should be capitalized.
and in cases where "station" is not part of the proper name, or is not usually capitalized in sources, it should be in written in lower case
. I'm not sure to which the "proper name" refers, but both the WP:COMMONNAME and WP:OFFICIALNAME are "Symphony Station" and it is usually (always) capitalized in sources.
Rather than following the two guidelines above, the closer instead went with their interpretation of "the spirit" of the guideline: The spirit of WP:USSTATION would point to this being non-capitalized.
But the actual guideline shows that "Symphony Station" should be capitalized and has a piece written specifically to cover this case.
Closer also wrote in their close Indeed, the station does not even use "station" it its signage, which would indicate it is just a regular station, as opposed to "named transit center" to quote the guideline.
. This is not true. While some platform signs do show the abbreviated "Symphony", other signs show "Symphony Station". Such as the signs at the recent renaming of the station, where officials stood at a "Symphony Station" podium underneath a permanent "SYMPHONY STATION" sign in front of the transit facility. Also unclear what "a regular station"
is and why that WP:OR should be considered.
In our required discussion prior to this MR, closer wrote Anyways, on Misplaced Pages there is a pretty high bar for whether something is considered a proper noun: "consistently" capitalized, not just usually. I believe another user was able to find sources that did not capitalize it, so in cases like that Misplaced Pages defaults to not capitalizing.
Other users actually did not provide any reliable source showing "Symphony station" in use. Comment from an oppose voter that stated both "Symphony Station" and "Symphony station" are equally correct ways to refer to it
should have been disregarded, as again not a single source was presented in the RM showing uncapitalized usage. Upon this being pointed out, closer said I concede that you are correct in that none of the links provided actually included a lowercase "Symphony station."
There is a WP:CONSISTENT argument in the close and discussion, which I agree with. But the solution to achieve consistency should be to subsequently move the other Sound Transit stations to match their common names (which in all/most cases will be "Station"). Moving the other station articles based on the result of this RM was supported by several participants, and even both of the oppose voters were open to moving the Seattle stations and/or all US stations.
Finally, the closer wrote Further, the article as currently named maintains consistency with the current capitalization of the majority of US stations, and OP claims to not want to shift the guideline for the entire US. Arguments that Seattle stations are somehow different do not seem to hold water, as similar arguments could be made for many other cites.
Seattle stations are different per their cited usage in reliable third-party sources, which consistently capitalize "Station". I don't think though it's valid to require the massive scope of all US rail stations to be consistent amongst each other at the expense of disregarding their WP:COMMONNAMES, and this point of view was supported by others in the RM: Expanding the scope of this discussion to the entire country is an unnecessary escalation and does not result in productive reasoning here.
. PK-WIKI (talk) 17:24, 24 September 2024 (UTC)
- Endorse. Sense of the group was not to move. Arguments against can not be discounted. The closer's summary and explanations don't matter. The outcome was reasonable.—Alalch E. 22:06, 24 September 2024 (UTC)
- Endorse a no-consensus outcome here, if not the current "not moved" close. However, while the closer's commentary may have been intended to summarize the discussion, it happened to look quite a bit like a new comment in opposition to the move; such closing comments may make things more likely to end up here. The close suggests that the official name is determinative in choosing an article name. Further, the user talk comment stating that "on Misplaced Pages there is a pretty high bar for whether something is considered a proper noun: 'consistently' capitalized, not just usually" is a questionable interpretation of WP:MOS-CAPS. The guideline actually states that Misplaced Pages capitalizes when terms are "consistently capitalized in a substantial majority of independent, reliable sources". That is, the guideline requires evidence that a substantial majority of RS capitalize the term systematically. This equates pretty accurately to "usually capitalized in RS" rather than "always capitalized in RS". Dekimasuよ! 01:26, 25 September 2024 (UTC)
Attempted assassination of Donald Trump in Pennsylvania (closed)
|
---|
The following is an archived debate of the move review of the page above. Please do not modify it. |
I was not a participant of this RM, but there are several issues with this closure.
These issues were discussed on the closer's talk page, and the closer did not seem willing to reopen. Natg 19 (talk) 02:22, 19 September 2024 (UTC)
|
The above is an archive of the move review of the page listed in the close of this review. Please do not modify it. |
LGBTQ (closed)
|
---|
The following is an archived debate of the move review of the page above. Please do not modify it. |
I and others would like an opportunity to comment on the discussion. I want the conversation re-opened to give more space and time for additional comments, and then re-evaluated based on a more complete discourse. The discussion on the talk page is not representative of the discourse, and it is apparent from other discussion including Wikipedia_talk:WikiProject_LGBT_studies#Now_that_the_main_article_has_been_moved_to_LGBTQ,_all_sub-articles_(including_the_Wikiproject)_can_follow_suit that there are people who have more to say and other people who want to give comment. The move from LGBT -> LGBTQ would affect 50,000 links, so is a very high impact change, but the move discussion lasted 10 days and included about 20 people, so was very small relative to the consequences. There were several previous move discussions, and participants in those discussions were not notified. Because this is such a complex move affecting so many articles, there is no reason to act in haste, and nothing would be lost by opening the discussion for a while longer to advertise it and let everyone say what they want to say. I do not object to the the move closure as an interpretation of the comments considered, but it is apparent now that thousands of articles are going to be affected that there are more people who would have commented, had they known the discussion was happening. It is problematic and an error that now that 10-day discussion is shutting down conversation as instead of debating the name, some people are arguing on the basis of the matter being settled on the basis of representative consensus discussion being reached. That small group was not the fullness of discussion. Thanks for considering. Bluerasberry (talk) 21:06, 2 September 2024 (UTC)
|
The above is an archive of the move review of the page listed in the close of this review. Please do not modify it. |