Revision as of 02:12, 28 December 2024 editSmokeyJoe (talk | contribs)Extended confirmed users, New page reviewers, Pending changes reviewers, Rollbackers44,278 editsm →Timor-Leste: f← Previous edit |
Latest revision as of 07:38, 29 December 2024 edit undoSportingFlyer (talk | contribs)Autopatrolled, Extended confirmed users, New page reviewers, Rollbackers30,618 edits →Timor-Leste: ReplyTag: Reply |
(15 intermediate revisions by 11 users not shown) |
Line 11: |
Line 11: |
|
|
|
|
|
* '''Overturn'''. Supervote and BADNAC. I read a strong “no consensus”. Non admins should not be closing contentious discussions. A closer beginning their rationale by citing their previous closes is a plain claim to being INVOLVED in similar cases, and is an unacceptable bias to take as positive evidence. ] (]) 02:11, 28 December 2024 (UTC) |
|
* '''Overturn'''. Supervote and BADNAC. I read a strong “no consensus”. Non admins should not be closing contentious discussions. A closer beginning their rationale by citing their previous closes is a plain claim to being INVOLVED in similar cases, and is an unacceptable bias to take as positive evidence. ] (]) 02:11, 28 December 2024 (UTC) |
|
|
*'''Overturn'''. I voted "oppose" to the move of ] to ] because this country's Portuguese-language name is not its ] exonym in the English-speaking world. Nonetheless, since Misplaced Pages is consensus-based, I would not be reluctant to accept a clear majority in favor of the move, such as the majorities evident in the city name moves ] → ] or ] → ]. However, the votes do not show majority support for the move and, since moves of country names are rare and contentious (the most recent such move — ] → ] at ] — also resulted in a move review), a move of this nature should be made only if consensus is clear and unambiguous. —] <small>] • ]</small> 06:12, 28 December 2024 (UTC) |
|
|
*'''Overturn to no consensus or relist''' <small>(uninvolved)</small> Per Supervote. Yet another example of a NAC doing a contentious close, that did not indicate consensus, but rather POV of the closer themselves. ] ] 06:21, 28 December 2024 (UTC) <small>(Clarified !vote to overturn to NC or relist) ] ] 03:06, 29 December 2024 (UTC)</small> |
|
|
*'''Endorse''' I don't actually see any problem with the close, and on DRV I tend to yell BADNAC even when others don't. The closer is not an admin, but clearly has experience closing discussions, and while their final sentence isn't well worded, the rest of the close was clearly thought out. Those supporting also made a better case than those opposing, in my opinion: those supporting cite COMMONNAME, and those opposing don't really discuss how it's ''not'' the COMMONNAME but instead make a variety of differing arguments. No reason to overturn this one. ] ''<span style="font-size:small; vertical-align:top;">]</span>''·''<span style="font-size:small; vertical-align:bottom;">]</span>'' 06:27, 28 December 2024 (UTC) |
|
|
*:I'd be fine with a relist. ] ''<span style="font-size:small; vertical-align:top;">]</span>''·''<span style="font-size:small; vertical-align:bottom;">]</span>'' 07:38, 29 December 2024 (UTC) |
|
|
*'''Endorse''' <small>(partially involved - I made a general comment but didn't vote)</small>. I think the close could have absolutely been worded better, but I don't see it as a supervote - to me, I read it as a judgement after the closer read the argument and I don't think that a closer needs to explicitly say "After reading this discussion I am satisfied...". The arguments opposing the move were weak and generally related to vague claims and cherry-picked sources, or pointing to frustration with the move request in general rather than actually why the page shouldn't be moved. In contrast, support votes provided evidence and cited policy reasons for the move, which makes a move a perfectly logical conclusion. It could have been relisted for sure, but I don't think it ''needed'' to be, and closing seems fine to me. ] (]) 06:52, 28 December 2024 (UTC) |
|
|
*:You are picking at the wrong issue with being explicit, if the closer is meant to be "satisfied" they should be with the consensus and its support in policy; they are not meant to be satisfied or not that a particular argument meets a certain standard. Closing RMs is not a burden-of-evidence style judgement. ] (]) 07:28, 28 December 2024 (UTC) |
|
|
*'''Relist'''. I think the discussion hadn't quite settled into a steady state. Plenty of new participants were still coming in, based on the number who joined shortly before the closure. After the closure there were further new interested parties and further discussion, of which a good portion was helpful commentary and not just, say, only the same people repeating the same points they already made. And of course this is on a backdrop of a long history of dispute over the same proposal. No single one of these factors inherently requires a relist, but in the overall circumstances I would allow the post-close suggestions to discuss more. ] (]) 07:10, 28 December 2024 (UTC) |
|
|
*'''Overturn'''. This was a pure ], based not on the consensus of the discussion but on the closer's reading of the position. Such an argument should have been made as a !vote, not as a close. This should be changed either to no consensus or to relist, so that it can be re-closed with a rationale that is actually based on the content of the discussion rather than the closer's position on the underlying question. ''''']''''' <small>'']''</small> 09:36, 28 December 2024 (UTC) |
|
|
*'''Relist'''. This was a premature close and its rationale had supervote character. I am personally in favor of a page move and could be content with the outcome, but at that stage of the discussion, a relist would have been the most appropriate thing to do. –] (]) 10:05, 28 December 2024 (UTC) |
|
|
*'''Overturn to no consensus or relist''' Agree that the close was premature and there was not a strong consensus (which is probably needed given the number of attempts to move this article in the past). As an aside, I also find it quite odd that Ngrams were not referred to at all in the discussion, as they would usually be a key source when considering whether a common name had changed or not. The would suggest that the move should not have taken place. ] ]] 16:24, 28 December 2024 (UTC) |
|
|
*'''Relist''' - The closing statement is a statement of the closer's opinion, not a statement about the consensus of opinions of the participants. It is therefore a ]. There is no consensus, and relisting is better than just closing as No Consensus. ] (]) 20:43, 28 December 2024 (UTC) |
|
|
*'''Do not overturn to no consensus''' <small>(partially involved)</small> – there are still arguments to be made from users in the post-close discussion, and I generally believe 7-day discussions should very rarely be closed as no consensus. Relists exist to find that consensus. I made my comments about whether I think it's a good close or not on the talk page, but I don't feel strongly one way or the other; I'm not going to comment here on whether this should be relisted or endorsed. <span style="background-color: black">] ] ]</span> 21:56, 28 December 2024 (UTC) |
|
|
|
|
|
====] (closed)==== |
|
====] (closed)==== |
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)