This page has an administrative backlog that requires the attention of willing administrators. Please replace this notice with {{no admin backlog}} when the backlog is cleared.
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.
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.
(Initiated 7 days ago on 17 May 2024) – This discussion just got auto-archived at ANI before anyone got around to closing it, but there was a topic ban proposal in there with a decent number of votes. Could someone take a look at this? --
Licks-rocks (
talk) 09:56, 25 May 2024 (UTC)reply
Place new administrative discussions above this line using a level 3 heading
(Initiated 70 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
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 48 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 47 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.
AwesomeAasim 00:11, 8 May 2024 (UTC)reply
(Initiated 47 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 34 days ago on 20 April 2024)
An involved user has repeatedly attempted to close this after adding their arguments. It's a divisive topic and a close would stop back and forth edits.
DerVolkssport11 (
talk) 12:42, 22 May 2024 (UTC)reply
To clarify, the RfC was closed in this dif, and an IP editor unclosed it, with this statement: "involved and pushing"
In just over an hour, the above editor voiced support for the proposal.
I reclosed it, and the same IP opened the RfC again, with this message: "pushing by involved users so ask for more comments".
I reclosed once more. And then the editor who opened this requests opened it. To avoid violated WP:3RR, I have not reclosed it, instead messaging the original closer to notify them.
The proposal itself was an edit request that I rejected. The IP who made the request reopened the request, which I rejected once more. They then proceeded to open an RfC.
Redacted II (
talk) 12:58, 22 May 2024 (UTC)reply
(Initiated 48 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 18 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
(Initiated 116 days ago on 30 January 2024) Listing multiple non-unanimous merge discussions from January that have run their course.
Noah,
AATalk 13:50, 15 March 2024 (UTC)reply
(Initiated 38 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
(Initiated 22 days ago on 3 May 2024) As the proposer I presume I cannot close this. It was started more than a week ago and opinions differed somewhat.
Chidgk1 (
talk) 13:46, 10 May 2024 (UTC)reply