Jump to content

Wikipedia:Closure requests

From Wikipedia, the free encyclopedia

    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.

    Include a link to the discussion itself and the {{Initiated}} template at the beginning of the request. A helper script can make listing easier. Move discussions go in the 'other types' section.

    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 is not normally in itself a problem at reviews. Still, there are caveats. You may not close discussions as an unregistered user, or where implementing the closure would need 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

    [edit]

    Administrative discussions

    [edit]

    (Initiated 18 days ago on 5 December 2024) - Ratnahastin (talk) 07:18, 24 December 2024 (UTC)[reply]

    (Initiated 10 days ago on 13 December 2024) challenge of close at AN was archived nableezy - 05:22, 24 December 2024 (UTC)[reply]

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

    [edit]

    Requests for comment

    [edit]

    (Initiated 222 days ago on 15 May 2024) Discussion died down quite a long time ago. I do not believe anything is actionable but a formal closure will help. Soni (talk) 04:19, 3 December 2024 (UTC)[reply]

    (Initiated 77 days ago on 7 October 2024) Tough one, died down, will expire tomorrow. Aaron Liu (talk) 23:58, 5 November 2024 (UTC)[reply]

    (Initiated 76 days ago on 8 October 2024) Expired tag, no new comments in more than a week. KhndzorUtogh (talk) 21:48, 13 November 2024 (UTC)[reply]

    information Note: This is a contentious topic and subject to general sanctions. Also see: Wikipedia:Administrators' noticeboard topic. Bogazicili (talk) 17:26, 21 November 2024 (UTC)[reply]
    information Note: Not sure if anyone is looking into this, but might be a good idea to wait for a few weeks since there is ongoing discussion. Bogazicili (talk) 16:33, 12 December 2024 (UTC)[reply]

    (Initiated 68 days ago on 16 October 2024) Discussion seems to have petered out a month ago. Consensus seems unclear. Gnomingstuff (talk) 02:34, 11 December 2024 (UTC)[reply]

    information Note: Needs admin closure imho, due to its importance (guideline page), length (101kb), and questions about neutrality of the Rfc question and what it meant. Mathglot (talk) 21:28, 16 December 2024 (UTC)[reply]
    And in true Streisand effect fashion, this discussion, quiescent for six weeks, has some more responses again. Mathglot (talk) 01:30, 22 December 2024 (UTC)[reply]

    (Initiated 57 days ago on 28 October 2024) Participation/discussion has mostly stopped & is unlikely to pick back up again. - Butterscotch Beluga (talk) 21:15, 7 December 2024 (UTC)[reply]

    information Note: This is a contentious topic and subject to general sanctions. - Butterscotch Beluga (talk) 21:15, 7 December 2024 (UTC)[reply]
    Archived. P.I. Ellsworth , ed. put'er there 22:26, 8 December 2024 (UTC)[reply]

    (Initiated 44 days ago on 10 November 2024) Discussion is slowing significantly. Likely no consensus, personally. Bluethricecreamman (talk) 03:09, 2 December 2024 (UTC)[reply]

    Option 2 was very clearly rejected. The closer should try to see what specific principles people in the discussion agreed upon if going with a no consensus close, because there should be a follow-up RfC after some of the details are hammered out. Chess (talk) (please mention me on reply) 03:10, 6 December 2024 (UTC)[reply]
     Doing... Compassionate727 (T·C) 13:43, 12 December 2024 (UTC)[reply]
    @Compassionate727: Still working on this? — Red-tailed hawk (nest) 17:18, 18 December 2024 (UTC)[reply]
    Ugh… in practice, no. I'm still willing to do it, but it's in hiatus because of the three(!) pending challenges of my closures at AN, while I evaluate to what extent I need to change how I approach closures. If somebody else wants to take over this, they should feel free. Compassionate727 (T·C) 22:16, 18 December 2024 (UTC)[reply]
    Taking a pause is fair. Just wanted to double check. — Red-tailed hawk (nest) 00:52, 19 December 2024 (UTC)[reply]
    asking for an update if possible. I think this RFC and previous RFCBEFORE convos were several TOMATS long at this point, so I get that this might take time. Bluethricecreamman (talk) 16:34, 23 December 2024 (UTC)[reply]

    (Initiated 40 days ago on 13 November 2024) - probably gonna stay status quo, but would like a closure to point to Bluethricecreamman (talk) 06:14, 17 December 2024 (UTC)[reply]

    (Initiated 40 days ago on 13 November 2024) RfC has elapsed, and uninvolved closure is requested. — Red-tailed sock (Red-tailed hawk's nest) 15:49, 17 December 2024 (UTC)[reply]

    (Initiated 38 days ago on 16 November 2024) Very wide impact, not much heat. Aaron Liu (talk) 15:30, 23 December 2024 (UTC)[reply]

    (Initiated 34 days ago on 20 November 2024) TompaDompa (talk) 17:50, 20 December 2024 (UTC)[reply]

    (Initiated 15 days ago on 8 December 2024) No further participation in the last 7 days. Consensus is clear but I am the opener of the RfC and am not comfortable closing something I am so closely involved in, so would like somebody uninvolved to close it if they believe it to be appropriate.RachelTensions (talk) 16:00, 19 December 2024 (UTC)[reply]

    I'm not comfortable closing a discussion on a guideline change this early. In any case, if the discussion continues as it has been, a formal closure won't be necessary. Compassionate727 (T·C) 13:00, 20 December 2024 (UTC)[reply]

    (Initiated 38 days ago on 15 November 2024) This RfC expired five days ago, has an unclear consensus, I am involved, and discussion has died down. JJPMaster (she/they) 22:56, 20 December 2024 (UTC)[reply]

    (Initiated 7 days ago on 16 December 2024) RFC is only 5 days old as of time of this posting, but overwhelming consensus approves of status quo, except for a single COI editor. Bluethricecreamman (talk) 21:04, 21 December 2024 (UTC)[reply]

    The CoI editor has now accepted that consensus is for the status quo, but I think a formal close from an uninvolved editor, summarizing the consensus would be helpful, since the issue has been coming up for a while and many editors were involved. — penultimate_supper 🚀 (talkcontribs) 16:35, 23 December 2024 (UTC)[reply]
    yes, despite multiple posts to WP:BLPN, WP:NPOVN, WP:3O, several talk page discussions, and now an RFC, I doubt the pressure to remove word oligarch from the lede of that page will stop. An appropriate close could be a useful thing to point at in the future though. Bluethricecreamman (talk) 16:40, 23 December 2024 (UTC)[reply]

    (Initiated 88 days ago on 27 September 2024) Lots of considered debate with good points made. See the nom's closing statement. Kowal2701 (talk) 09:47, 24 December 2024 (UTC)[reply]

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

    [edit]

    Deletion discussions

    [edit]
    XFD backlog
    V Sep Oct Nov Dec Total
    CfD 0 0 0 1 1
    TfD 0 0 0 0 0
    MfD 0 0 2 1 3
    FfD 0 0 1 18 19
    RfD 0 0 9 27 36
    AfD 0 0 0 0 0

    Please review this discussion. --Jax 0677 (talk) 17:29, 21 December 2024 (UTC)[reply]

    The discussion has now been relisted thrice. --Jax 0677 (talk) 00:42, 23 December 2024 (UTC)[reply]

    (Initiated 22 days ago on 2 December 2024) HouseBlaster (talk • he/they) 03:45, 24 December 2024 (UTC)[reply]

     Done Compassionate727 (T·C) 15:37, 24 December 2024 (UTC)[reply]

    (Initiated 10 days ago on 14 December 2024) HouseBlaster (talk • he/they) 05:06, 24 December 2024 (UTC)[reply]

     Done Compassionate727 (T·C) 15:17, 24 December 2024 (UTC)[reply]

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

    [edit]

    Other types of closing requests

    [edit]

    (Initiated 90 days ago on 25 September 2024) Open for a while, requesting uninvolved closure. Andre🚐 22:15, 20 December 2024 (UTC)[reply]

    (Initiated 78 days ago on 7 October 2024) A merge + move request with RM banners that needs closure. No new comments in 20 days. CX Zoom[he/him] (let's talk • {CX}) 20:16, 10 December 2024 (UTC)[reply]

    (Initiated 69 days ago on 16 October 2024) Experienced closer requested. ―Mandruss  13:57, 27 November 2024 (UTC)[reply]

    (Initiated 67 days ago on 18 October 2024) This needs formal closure by someone uninvolved. N2e (talk) 03:06, 1 December 2024 (UTC)[reply]

    (Initiated 48 days ago on 5 November 2024) RM that has been open for over a month. Natg 19 (talk) 02:13, 11 December 2024 (UTC)[reply]

    (Initiated 31 days ago on 22 November 2024) Pretty simple RM that just needs an uninvolved editor to close. ―"Ghost of Dan Gurney" (hihi) 17:40, 21 December 2024 (UTC)[reply]

    (Initiated 27 days ago on 27 November 2024) Only two editors—the nominator and myself—have participated. That was two weeks ago. Just needs an uninvolved third party for closure. ~ Pbritti (talk) 18:37, 13 December 2024 (UTC)[reply]

     Doing... BusterD (talk) 20:28, 15 December 2024 (UTC)[reply]

    (Initiated 56 days ago on 29 October 2024) There are voices on both sides (ie it is not uncontroversial) so a non-involved editor is needed to evaluate consensus and close this. Thanks. PamD 09:55, 17 December 2024 (UTC)[reply]

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

    [edit]
    pFad - Phonifier reborn

    Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

    Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


    Alternative Proxies:

    Alternative Proxy

    pFad Proxy

    pFad v3 Proxy

    pFad v4 Proxy