Jump to content

Wikipedia:Closure requests: Difference between revisions

From Wikipedia, the free encyclopedia
Content deleted Content added
Line 155: Line 155:
=== [[Talk:Donald Trump#RfC on use of "convicted felon" in first sentence]] ===
=== [[Talk:Donald Trump#RfC on use of "convicted felon" in first sentence]] ===
{{initiated|21:38, 30 May 2024 (UTC)}} I estimate this discussion has received around 250 votes, over 3/4 of them within the first 24 hours, including a substantial number of votes from IP editors. Voting frequency has dropped significantly (0-5 votes per day for the past few days) and I think this merits a timely close. Because of the contentious and high profile nature of this, including news coverage [https://www.foxnews.com/media/cnn-host-suggests-trump-conviction-mentioned-prominently-enough-former-presidents-wikipedia-page] [https://slate.com/technology/2024/06/donald-trump-felony-wikipedia-debate.html] I would recommend an experienced closer or a panel. <span style="font-family:times; text-shadow: 0 0 .2em #7af">~[[User:Awilley|Awilley]] <small>([[User talk:Awilley|talk]])</small></span> 22:58, 11 June 2024 (UTC)
{{initiated|21:38, 30 May 2024 (UTC)}} I estimate this discussion has received around 250 votes, over 3/4 of them within the first 24 hours, including a substantial number of votes from IP editors. Voting frequency has dropped significantly (0-5 votes per day for the past few days) and I think this merits a timely close. Because of the contentious and high profile nature of this, including news coverage [https://www.foxnews.com/media/cnn-host-suggests-trump-conviction-mentioned-prominently-enough-former-presidents-wikipedia-page] [https://slate.com/technology/2024/06/donald-trump-felony-wikipedia-debate.html] I would recommend an experienced closer or a panel. <span style="font-family:times; text-shadow: 0 0 .2em #7af">~[[User:Awilley|Awilley]] <small>([[User talk:Awilley|talk]])</small></span> 22:58, 11 June 2024 (UTC)

:I have edited Trump's article (and related articles) before but do not think I will be [[WP:INVOLVED|involved]] for this. I have followed a fair bit of the discussion. I'm definitely not experienced enough for a solo-close, so will volunteer to help or join a panel, in case either is needed. [[User:Soni|Soni]] ([[User talk:Soni|talk]]) 23:22, 11 June 2024 (UTC)


=== Place new discussions concerning RfCs above this line using a level 3 heading ===
=== Place new discussions concerning RfCs above this line using a level 3 heading ===

Revision as of 23:22, 11 June 2024

    Use the closure requests noticeboard to ask an uninvolved editor to assess, summarize, and formally close a Wikipedia discussion. Do so when consensus appears unclear, it is a contentious issue, or where there are wiki-wide implications (e.g. any change to our policies or guidelines).

    Do not list discussions where consensus is clear. If you feel the need to close them, do it yourself.

    Move on – do not wait for someone to state the obvious. In some cases, it is appropriate to close a discussion with a clear outcome early to save our time.

    Do not post here to rush the closure. Also, only do so when the discussion has stabilised.

    On the other hand, if the discussion has much activity and the outcome isn't very obvious, you should let it play out by itself. We want issues to be discussed well. Do not continue the discussion here.

    There is no fixed length for a formal request for comment (RfC). Typically 7 days is a minimum, and after 30 days the discussion is ripe for closure. The best way to tell is when there is little or no activity in the discussion, or further activity is unlikely to change its result.

    When the discussion is ready to be closed and the outcome is not obvious, you can submit a brief and neutrally worded request for closure.

    Be sure to include a link to the discussion itself and the {{Initiated}} template at the beginning of the request. A helper script can make listing discussions easier.

    Any uninvolved editor may close most discussions, so long as they are prepared to discuss and justify their closing rationale.

    Closing discussions carries responsibility, doubly so if the area is contentious. You should be familiar with all policies and guidelines that could apply to the given discussion (consult your draft closure at the discussions for discussion page if unsure). Be prepared to fully answer questions about the closure or the underlying policies, and to provide advice about where to discuss any remaining concerns that editors may have.

    Non-admins can close most discussions. Admins may not overturn your non-admin closures just because you are not an admin, and this should not normally be in itself a problem at closure reviews. Still, there are caveats. You may not close discussions as an unregistered user, or where implementing the closure would call to use tools or edit permissions you do not have access to. Articles for deletion and move discussion processes have more rules for non-admins to follow.

    Technical instructions for closers

    Please append {{Doing}} to the discussion's entry you are closing so that no one duplicates your effort. When finished, replace it with {{Close}} or {{Done}} and an optional note, and consider sending a {{Ping}} to the editor who placed the request. Where a formal closure is not needed, reply with {{Not done}}. After addressing a request, please mark the {{Initiated}} template with |done=yes. ClueBot III will automatically archive requests marked with {{Already done}}, {{Close}}, {{Done}} {{Not done}}, and {{Resolved}}.

    If you want to formally challenge and appeal the closure, do not start the discussion here. Instead follow advice at WP:CLOSECHALLENGE.


    Other areas tracking old discussions

    Administrative discussions

    Place new administrative discussions above this line using a level 3 heading

    Requests for comment

    (Initiated 262 days ago on 18 February 2024) RfC tag has expired and there haven't been new comments in months. Vanezi (talk) 09:40, 9 June 2024 (UTC)[reply]

     Comment: The RfC starter, Youprayteas, did not include any sources when starting his request. Multiple new sources have been added since February. Bogazicili (talk) 18:42, 11 June 2024 (UTC)[reply]

    (Initiated 236 days ago on 15 March 2024) Ready to be closed. Charcoal feather (talk) 17:02, 27 April 2024 (UTC) [reply]

    new closer needed
    The following discussion has been closed. Please do not modify it.
    Before I try to close this I wanted to see if any editors believed I am WP:INVOLVED. I have no opinions on the broader topic, but I have previously participated in a single RfC on whether a specific article should include an infobox. I don't believe this makes me involved, as my participation was limited and on a very specific question, which is usually insufficient to establish an editor as involved on the broader topic, but given the strength of opinion on various sides I expect that any result will be controversial, so I wanted to raise the question here first.
    If editors present reasonable objections within the next few days I won't close; otherwise, unless another editor gets to it first, I will do so. BilledMammal (talk) 04:43, 13 May 2024 (UTC)[reply]
    I am involved in the underlying RfC, but my opinion on the issue is not particularly strong and I am putting on my closer hat now. Per WP:INVOLVED, "[i]nvolvement is construed broadly by the community". In the Rod Steiger RfC, you stated: [T]o the best of my knowledge (although I have not been involved in these discussions before) every recent RfC on including an infobox has been successful. From this it is clear that the topic is settled, and insisting on RfC's for every article risks becoming disruptive. Although the underlying RfC was on a very specific question, your statement touches on the broader question of whether editors should be allowed to contest including an infobox in a particular article, a practice that you said risks becoming disruptive because the topic is settled. That makes you involved—construing the term broadly—because answering this RfC in the affirmative would significantly shift the burden against those contesting infoboxes in future discussions. That said, if you can put aside your earlier assessment of consensus and only look at the arguments in this RfC, I don't see an issue with you closing. It wouldn't be a bad idea to disclose this at the RfC itself, and make sure that nobody there has any objections. voorts (talk/contributions) 21:43, 18 May 2024 (UTC)[reply]
    Pinging @BilledMammal. voorts (talk/contributions) 21:45, 18 May 2024 (UTC)[reply]
    if you can put aside your earlier assessment of consensus and only look at the arguments in this RfC, I don't see an issue with you closing; per WP:LOCALCON, I don't see lower level discussions as having any relevance to assessing the consensus of higher level discussions, so I can easily do so - consistent results at a lower level can indicate a WP:IDHT issue, but it can also indicate that a local consensus is out of step with broader community consensus. Either way, additional local discussions are unlikely to be productive, but a broader discussion might be.
    Per your suggestion I'll leave a note at the RfC, and see if there are objections presented there or here. BilledMammal (talk) 02:37, 21 May 2024 (UTC)[reply]
    I don’t think that !voting in an RfC necessarily equates to being too involved, but in this case, the nature of your !vote in the Steiger RfC was concerning enough to be a red flag. Is it still your contention that “every recent RfC on including an infobox has been successful. From this it is clear that the topic is settled, and insisting on RfC's for every article risks becoming disruptive”? That was wrong (and rather chilling) when you wrote it and is still wrong (and still chilling) now, as the current RfC makes rather clear. - SchroCat (talk) 03:30, 21 May 2024 (UTC)[reply]
    Is it still your contention that “every recent RfC on including an infobox has been successful. From this it is clear that the topic is settled, and insisting on RfC's for every article risks becoming disruptive”? No. I've only skimmed the RfC, but I see that while a majority have been successful a non-trivial number have not been - and the percentage that have not been has increased recently. BilledMammal (talk) 04:13, 21 May 2024 (UTC)[reply]
    Part of my problem is that you said it in the first place. It was incorrect when you first said it and it comes across as an attempt to shut down those who hold a differing opinion. As you're not an Admin, I'm also not sure that you can avoid WP:NACPIT and WP:BADNAC, both of which seem to suggest that controversial or non-obvious discussions are best left to Admins to close. - SchroCat (talk) 06:44, 21 May 2024 (UTC)[reply]
    In general, any concern that WP:IDHT behavior is going on could be seen as an attempt to shut down those who hold a differing opinion. I won't close this discussion, though generally I don't think that raising concerns about conduct make an editor involved regarding content.
    However, I reject BADNAC as an issue, both here and generally - I won't go into details in this discussion to keep matters on topic, but if you want to discuss please come to my talk page. BilledMammal (talk) 07:53, 21 May 2024 (UTC)[reply]
    There was no IDHT behaviour, which was the huge flaw in your comment. You presumed that "every recent RfC on including an infobox has been successful", which was the flawed basis from which to make a judgement about thinking people were being disruptive. Your opinion that there was IDHT behaviour which was disruptive is digging the hole further: stop digging is my advice, as is your rejection of WP:BADNAC ("(especially where there are several valid outcomes) or likely to be controversial"), but thank you for saying you won't be closing the discussion. - SchroCat (talk) 08:10, 21 May 2024 (UTC)[reply]

    (Initiated 217 days ago on 4 April 2024) This RFC was kind of a mess and I don't think any consensus came out of it, but it could benefit from a formal closure so that interested editors can reset their dicussion and try to figure out a way forward (context: several editors have made changes to the lead image since the RFC discussion petered out, but these were reverted on the grounds that the RFC was never closed). Note that an IP user split off part of the RFC discussion into a new section, Talk:Ariana Grande#Split: New Met Gala 2024 image. Aoi (青い) (talk) 22:52, 1 June 2024 (UTC)[reply]

     Doing... Chess (talk) (please mention me on reply) 22:18, 11 June 2024 (UTC)[reply]

    (Initiated 214 days ago on 7 April 2024) Three related RFCs in a trench coat. I personally think the consensus is fairly clear here, but it should definitely be an admin close. Loki (talk) 14:07, 6 May 2024 (UTC)[reply]

    (Initiated 213 days ago on 8 April 2024) Discussion appears to have died down almost a month after this RfC opened. Would like to see a formal close of Q1 and Q2. Awesome Aasim 00:11, 8 May 2024 (UTC)[reply]

    (Initiated 212 days ago on 8 April 2024) Clear consensus for change but not what to change to. I've handled this RfC very badly imo. User:Alexanderkowal — Preceding undated comment added 11:50, 1 May 2024 (UTC)[reply]

     Comment: The RfC tag was removed the same day it was started. This should be closed as a discussion, not an RfC. voorts (talk/contributions) 22:03, 18 May 2024 (UTC)[reply]

    (Initiated 210 days ago on 11 April 2024) ☆SuperNinja2☆ TALK! 09:41, 21 May 2024 (UTC)[reply]

    See Talk:Mukokuseki#Close Plz 5/21/2024 Orchastrattor (talk) 20:34, 21 May 2024 (UTC)[reply]

    (Initiated 204 days ago on 17 April 2024) This was part of DRN process (Wikipedia:Dispute_resolution_noticeboard/Archive_245#Climate_change). It is ready to be closed [1] [2]. Bogazicili (talk) 18:39, 11 June 2024 (UTC)[reply]

    (Initiated 189 days ago on 2 May 2024) RfC template has been removed by the bot. TarnishedPathtalk 13:21, 3 June 2024 (UTC)[reply]

    (Initiated 187 days ago on 3 May 2024) Discussion has slowed with only one !vote in the last 5 days. TarnishedPathtalk 11:09, 2 June 2024 (UTC)[reply]

    (Initiated 183 days ago on 7 May 2024) Archived Request for Comment. 73.219.238.21 (talk) 23:32, 4 June 2024 (UTC)[reply]

    (Initiated 183 days ago on 8 May 2024) Last !vote was 27 May, 2024. Note: RfC was started by a blocking evading IP. TarnishedPathtalk 11:23, 3 June 2024 (UTC)[reply]

    (Initiated 160 days ago on 30 May 2024) I estimate this discussion has received around 250 votes, over 3/4 of them within the first 24 hours, including a substantial number of votes from IP editors. Voting frequency has dropped significantly (0-5 votes per day for the past few days) and I think this merits a timely close. Because of the contentious and high profile nature of this, including news coverage [3] [4] I would recommend an experienced closer or a panel. ~Awilley (talk) 22:58, 11 June 2024 (UTC)[reply]

    I have edited Trump's article (and related articles) before but do not think I will be involved for this. I have followed a fair bit of the discussion. I'm definitely not experienced enough for a solo-close, so will volunteer to help or join a panel, in case either is needed. Soni (talk) 23:22, 11 June 2024 (UTC)[reply]

    Place new discussions concerning RfCs above this line using a level 3 heading

    Deletion discussions

    XFD backlog
    V Aug Sep Oct Nov Total
    CfD 0 0 0 0 0
    TfD 0 0 7 0 7
    MfD 0 0 1 0 1
    FfD 0 0 2 0 2
    RfD 0 0 28 0 28
    AfD 0 0 1 0 1

    (Initiated 219 days ago on 2 April 2024) * Pppery * it has begun... 22:35, 31 May 2024 (UTC)[reply]

     Closed by editor Tavix. P.I. Ellsworth , ed. put'er there 14:17, 11 June 2024 (UTC)[reply]

    (Initiated 217 days ago on 3 April 2024) * Pppery * it has begun... 22:53, 31 May 2024 (UTC)[reply]

    (Initiated 214 days ago on 6 April 2024) * Pppery * it has begun... 22:53, 31 May 2024 (UTC)[reply]

    (Initiated 214 days ago on 7 April 2024) This one has been mentioned in a news outlet, so a close would ideally make sense to the outside world. HouseBlaster (talk · he/him) 13:56, 17 May 2024 (UTC)[reply]

    (Initiated 213 days ago on 7 April 2024) * Pppery * it has begun... 22:53, 31 May 2024 (UTC)[reply]

    (Initiated 213 days ago on 8 April 2024) * Pppery * it has begun... 22:53, 31 May 2024 (UTC)[reply]

     Closed by editor HouseBlaster. P.I. Ellsworth , ed. put'er there 14:32, 10 June 2024 (UTC)[reply]

    (Initiated 213 days ago on 8 April 2024) * Pppery * it has begun... 22:53, 31 May 2024 (UTC)[reply]

    (Initiated 212 days ago on 9 April 2024) mwwv converseedits 18:02, 29 May 2024 (UTC)[reply]

    (Initiated 212 days ago on 9 April 2024) * Pppery * it has begun... 22:35, 31 May 2024 (UTC)[reply]

     Closed by editor Tavix. P.I. Ellsworth , ed. put'er there 14:14, 11 June 2024 (UTC)[reply]

    (Initiated 208 days ago on 12 April 2024) * Pppery * it has begun... 22:53, 31 May 2024 (UTC)[reply]

    (Initiated 207 days ago on 13 April 2024) * Pppery * it has begun... 22:53, 31 May 2024 (UTC)[reply]

    (Initiated 206 days ago on 15 April 2024) * Pppery * it has begun... 22:53, 31 May 2024 (UTC)[reply]

    (Initiated 202 days ago on 18 April 2024) * Pppery * it has begun... 22:35, 31 May 2024 (UTC)[reply]

    (Initiated 196 days ago on 24 April 2024) * Pppery * it has begun... 22:53, 31 May 2024 (UTC)[reply]

    (Initiated 196 days ago on 24 April 2024) * Pppery * it has begun... 22:35, 31 May 2024 (UTC)[reply]

     Closed by editor Tavix. P.I. Ellsworth , ed. put'er there 14:12, 11 June 2024 (UTC)[reply]

    (Initiated 194 days ago on 26 April 2024) * Pppery * it has begun... 22:53, 31 May 2024 (UTC)[reply]

    (Initiated 194 days ago on 26 April 2024) * Pppery * it has begun... 22:53, 31 May 2024 (UTC)[reply]

    (Initiated 194 days ago on 27 April 2024) * Pppery * it has begun... 22:53, 31 May 2024 (UTC)[reply]

     Closed by editor HouseBlaster. P.I. Ellsworth , ed. put'er there 14:29, 10 June 2024 (UTC)[reply]

    (Initiated 192 days ago on 28 April 2024) * Pppery * it has begun... 22:53, 31 May 2024 (UTC)[reply]

    (Initiated 190 days ago on 30 April 2024) * Pppery * it has begun... 22:35, 31 May 2024 (UTC)[reply]

    (Initiated 184 days ago on 6 May 2024) If the consensus is to do the selective histmerge I'm willing to use my own admin tools to push the button and do it. * Pppery * it has begun... 17:07, 24 May 2024 (UTC)[reply]

    Place new discussions concerning XfDs above this line using a level 3 heading

    Other types of closing requests

    (Initiated 232 days ago on 19 March 2024) Merge discussion which has been occurring since 19 March 2024. Discussion has well and truly slowed. TarnishedPathtalk 14:34, 31 May 2024 (UTC)[reply]

     Done Charcoal feather (talk) 15:03, 11 June 2024 (UTC)[reply]

    (Initiated 204 days ago on 16 April 2024) - Discussion on a talkpage template, Last comment 6 days ago, 10 comments, 4 people in discussion. Not unanimous, but perhaps there is consensus-ish or strength of argument-ish closure possible. Gråbergs Gråa Sång (talk) 07:24, 23 April 2024 (UTC)[reply]

    It doesn't seem to me that there is a consensus here to do anything, with most editors couching their statements as why it might (or might not) be done rather than why it should (or should not). I will opine that I'm not aware there's any precedent to exclude {{Press}} for any reason and that it would be very unusual, but I don't think that's good enough reason to just overrule Hipal. Compassionate727 (T·C) 01:01, 13 May 2024 (UTC)[reply]
    Fwiw, one more comment in discussion since this comment. Gråbergs Gråa Sång (talk) 18:09, 11 June 2024 (UTC)[reply]

    (Initiated 188 days ago on 2 May 2024) Please review this discussion. --Jax 0677 (talk) 01:42, 11 May 2024 (UTC)[reply]

    (Initiated 163 days ago on 28 May 2024) Latest comment: 3 days ago, 79 comments, 37 people in discussion. Closing statement may be helpful for future discussions. Gråbergs Gråa Sång (talk) 10:29, 11 June 2024 (UTC)[reply]

    (Initiated 157 days ago on 3 June 2024) - Only been open three days but consensus appears clear, and the earlier it is resolved the easier it will be to clean up as edits are being made based on the current result. BilledMammal (talk) 08:06, 6 June 2024 (UTC)[reply]


    Place new discussions concerning other types of closing requests above this line using a level 3 heading