This is the current revision of this page, as edited by Tiggerjay (talk | contribs) at 19:13, 6 January 2025 (→2024 Israeli invasion of Syria: comment). The present address (URL) is a permanent link to this version.
Revision as of 19:13, 6 January 2025 by Tiggerjay (talk | contribs) (→2024 Israeli invasion of Syria: comment)(diff) ← Previous revision | Latest revision (diff) | Newer revision → (diff)< 2024 November | Move review archives | 2025 January > |
---|
2024 December
2024 Israeli invasion of Syria
- 2024 Israeli invasion of Syria (talk|edit|history|logs|links|archive|watch) (RM) (Discussion with closer)
User closed the move request of 19 December, while it was still being actively discussed, with no reasons whatsoever given. User then on started a new move request a minute later on a different article which involved the original article as well. When others tried to inquire about the move closure on the user's talk page they made no attempt to communicate whatsoever. In turn, I believe that this is a BADNAC. Zinderboff (talk) 20:57, 29 December 2024 (UTC)
- Relist (involved). Bad NAC, unresponsive closer. With zero explanation offered for the close, we cannot even attempt to formulate arguments for or against whether it was an appropriate interpretation of consensus. I'm taking no position with regards to how it *should* have been closed here, but I will at least point out that relisting will get more visibility on a discussion that seemingly lacks many of the participants I'd expect to see given the subject matter area (though perhaps the pending ARBPIA5 has something to do with that). ⇒SWATJester 21:24, 29 December 2024 (UTC)
- Relist (uninvolved) per SUPERVOTE, BACNAC, no rationale, also no correspondence even though they have edited WP since being pinged. Not the first time they've had a questionable NAC. TiggerJay (talk) 01:48, 30 December 2024 (UTC)
- Endorse (uninvolved) It is difficult to make the case that any other closer would decide differently to either moved or even no consensus when there are only 8 !votes in favor (including nom) and 11 !votes against. Kenneth Kho (talk) 08:32, 30 December 2024 (UTC)
- Actually 7 because the nom voted in addition, and 11 oppose, isn’t a huge spread, and with one less on each side for being non EC. TiggerJay (talk) 09:28, 30 December 2024 (UTC)
- Consensus is not about counting votes, but counting arguments, WP:NHC. TurboSuperA+ (talk) 12:28, 30 December 2024 (UTC)
- That wasn’t the basis for my decision and !vote but rather just commentary on the numbers as presented by the other user. However, identifying non-ec users are material. TiggerJay (talk) 15:28, 30 December 2024 (UTC)
- Exactly. — Preceding unsigned comment added by Rc2barrington (talk • contribs) 21:19, 31 December 2024 (UTC)
- Consensus is not about counting votes, but counting arguments, WP:NHC. TurboSuperA+ (talk) 12:28, 30 December 2024 (UTC)
- Actually 7 because the nom voted in addition, and 11 oppose, isn’t a huge spread, and with one less on each side for being non EC. TiggerJay (talk) 09:28, 30 December 2024 (UTC)
- Relist(uninvolved) also possible administrative action against the closer? Or at least a warning. Rc2barrington (talk) 21:19, 31 December 2024 (UTC)
- I don't think a bad NAC merits administrative action, they just need to not do it again until they're familiar with the process and can give the level of responsiveness necessary. ⇒SWATJester 21:44, 31 December 2024 (UTC)
- Relist (uninvolved): close was done nearly
832 hours early and was not clear enough of a consensus to justify that. think I got the math right now? Skynxnex (talk) 03:45, 3 January 2025 (UTC)
- Relist (uninvolved) - This is not only a bad non-administrative close, but a blatant bad non-administrative close because it is a bad close that fails both administrator accountability and involvement.
- The closer did not respond to questions about their close, and has not responded at Move Review. They may have taken a break; an editor should not take administrative actions that may need discussion afterward if they plan to be out of touch afterward.
- The closer immediately started a related Requested Move, which indicates that they were becoming involved and were voting or supervoting rather than assessing consensus.
- The Requested Move was in the area of a contentious topic, so that an even greater degree of judgment is required than otherwise. Being extended-confirmed, as the closer is, does not provide sufficient experience to close Requested Moves in a contentious topic. Contentious move requests, like contentious XFDs, should be left to administrators.
- I am not the only editor who has concerns about whether a warning is in order, but Move Review is a content forum. The closer should treat this close as an admonition. Robert McClenon (talk) 18:48, 6 January 2025 (UTC)
- Comment for what it's worth it does look like this editor has returned from a short wikibreak (diff) showing they're at least online, and had the opportunity to see this and other discussions on their talk page. 10 hours after that edit, no response anywhere regarding the moves, their talk page or this MR. TiggerJay (talk) 19:13, 6 January 2025 (UTC)
Timor-Leste (closed)
|
---|
The following is an archived debate of the move review of the page above. Please do not modify it. |
This discussion was not closed by an assessment of the discussion, but by a supervote: "I am satisfied that "Timor Leste" is now the dominant term". The close contained not only the individual analysis leading to this view, but also pointed towards commentary made at another close to bolster the argument. What the close does not have is any evaluation of the participants' discussion. There has been some post-close commentary about a potential relisting, but either way the move request should be re-closed with an assessment of consensus. CMD (talk) 01:39, 28 December 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. |
Murder of Zvi Kogan (closed)
|
---|
The following is an archived debate of the move review of the page above. Please do not modify it. |
Since there are suspects in custody, I don't think the close correctly assessed the interplay of WP:COMMONNAME and WP:DEATHS with WP:BLPCRIME as required by WP:RMCIDC. The closer said that they did not consider the five IP supporters per WP:PIA (Israel says the suspects worked for Iran). Even so, many supporters gave little to no explanation. Some of the arguments that did address BLPCRIME conflated murders where there are live suspects and ones where there are not while others rely too much on the official, non-judicial pronouncements. Given that most non-Israeli sources only use "murder" in the context of the charges or quotations from officials, it seems like we should be erring on the side of caution given the BLP concerns. This should either be overturned to move the page to Killing of Zvi Kogan per WP:DEATHS or relisted/restarted. -- Patar knight - /contributions 01:00, 12 December 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. |