Jump to content

Wikipedia:Closing discussions

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Rasteem (talk | contribs) at 00:04, 6 October 2024 (Reverted 1 edit by 2405:9800:B910:D46A:84ED:3787:F89A:A0DC (talk): Disruptive edits). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Consensus is Wikipedia's fundamental model for editorial decision-making. Policies and guidelines document communal consensus rather than creating it. Consensus is typically reached as a natural and inherent product of the wiki-editing process; generally someone makes a change to a page content, and then everyone who reads the page has an opportunity to either leave the page as it is or change it. Editors begin discussions to resolve disagreements that cannot be easily resolved through the normal wiki-editing process. Many community discussions and decisions happen on project pages that are specifically designed for that purpose. If discussions involve several individuals, the discourse can become lengthy and the results hard to determine. After a while, it is time to close the discussion so that the community can move on.

This page offers guidance on how and when discussions should be closed. There are no policies that directly dictate how to close a discussion. These information documents the customary practices that have evolved at Wikipedia in the years since it was started. These customs are grounded in the core principles of Wikipedia etiquette such as assuming good faith, creating consensus, and maintaining civility.

Closers may wish to read Wikipedia:Advice on closing discussions for guidance on actually determining consensus and writing closes.

Which discussions need to be closed

Many informal discussions do not need closing. Often, consensus is reached in the discussion and the outcome is obvious. Disagreements in articles are often solved by further edits. For example, two or more individuals may disagree about how a section of text in an article is written and start a discussion on the talk page. An uninvolved party might come up with a creative solution that addresses the concerns raised in the discussion. If it is a good solution, nothing needs to happen. There will be nothing more that is said, and everyone moves on. When this is the case, it often helps to leave a comment that the issue was resolved and perhaps link the edit that resolved the issue. On some pages, such as Wikipedia:Administrators noticeboard, the {{resolved}} template is used to note that an issue has been resolved. The template is added to the beginning of the section, with notes that indicate what action was taken. This helps shorten the reading needed to scan the page. Similarly, the {{unresolved}} template may be used to indicate that a dispute about an important issue has not found its solution, inviting more people to weigh in their ideas and opinions.

When a discussion involves many people and the outcome is not clear, it may be necessary to formally close the discussion. This is always the case in discussions at Wikipedia:Articles for deletion (AfD), Wikipedia:Categories for discussion (CfD) and the other XfDs. Observe however that intervening to close a discussion where this mode of resolution is not customary may prove to be incendiary instead of clarifying. Here, adding the {{unresolved}} template may be a better option or informing all parties about the possibility of requesting mediation.

It may be useful to close some Requests for comments; see that page for criteria to consider.

Closing vs archiving

Closing discourages people from continuing to post comments, while leaving the discussion on the page, so that editors can read it. This may be accomplished by placing templates such as {{Archive top}} and {{Archive bottom}} or {{Closed rfc top}} and {{Closed rfc bottom}} around a discussion. In addition to formal closes that analyze the consensus of a discussion, discussions may also be closed where someone, usually an administrator, decides that the discussion is irrelevant or disruptive. This practice is used quite often on pages that attract heated dispute, although there are no rules in place governing its use, and there are times when closing a discussion can create even more strife than had existed before.

Summarizing documents the outcome of the discussion (e.g. "The result was to keep the page"). Outside of the various deletion processes, most discussions are neither closed nor summarized.

Archiving is when the discussion is moved into an archive area. This is usually done automatically by a bot, when no new comments have been added for a defined length of time. Most discussions go into Talk page archives with no need for a summary. However, sometimes an active issue will be archived while waiting for an uninvolved editor to write a summary statement. The recommended procedure at WP:PREMATUREARCHIVE is to copy-paste the discussion back onto the original page and delete the discussion from the Talk archive. The discussion may then be summarized as normal. This enures that the summary of the discussion's outcome will be visible to the editors watching that page.

When to close discussions

  • Not too soon or too late: Some processes, especially deletion-oriented pages, have a specified minimum length, typically of 7 full days. Other processes, especially Requests for Comments (RfCs), have typical lengths but no mandatory minimum. It is unusual for anyone to request a formal closure by an uninvolved editor unless the discussion has been open for at least one week.[1] Similarly, if the discussion stopped, and editors have already assessed the consensus and moved on with their work, then there may be no need to formally close the discussion unless the process (e.g., Wikipedia:Articles for deletion) requires formal closure for other reasons.
  • When the discussion is stable: The more contentious the subject, the longer this may take. Two signs of achieving this state are the same editors repeating themselves, and the rate of other editors joining the conversation is slowing.
  • When further contributions are unlikely to be helpful: If additional comments, even weeks or months later, might be helpful, then don't close the conversation. Most conversations do not need to be closed. On the other hand, when further responses are likely to result in little more than wasting everyone's time by repeating the same widely held view, then it should be closed sooner rather than later. In between, wait to see whether enough information and analysis has been presented to make the outcome (including an outcome that editors do not agree) clear.

How to determine the outcome

Consensus

Many closures are based upon consensus. Consensus can be most easily defined as agreement. The closing editor or administrator will determine if consensus exists, and if so, what it is. To do this, the closer must read the arguments presented.

The desired standard is rough consensus, not perfect consensus. Closers are also required to exercise their judgment to ensure that any decision complies with the spirit of Wikipedia policy and with the project's goals. A good closer will transparently explain how the decision was reached.[2]

Consensus is not determined by counting heads or counting votes, nor is it determined by the closer's own views about what action or outcome is most appropriate. The closer is there to judge the consensus of the community, after discarding irrelevant arguments: those that flatly contradict established policy, those based on personal opinion only, those that are logically fallacious, and those that show no understanding of the matter of issue.[3] If the discussion shows that some people think one policy is controlling, and some another, the closer is expected to close by judging which view has the predominant number of responsible Wikipedians supporting it, not personally select which is the better policy. The closer is not expected to decide the issue, just to judge the result of the debate, and is expected to know policy sufficiently to know what arguments are to be excluded as irrelevant. If the consensus of reasonable arguments is opposite to the closer's view, they are expected to decide according to the consensus. The closer is not to be a judge of the issue, but rather of the argument.

If you believe that it is necessary to make an explicit statement about whether consensus was reached, it may be helpful to consider three broad categories for summarizing the result of a discussion:

  • Consensus in favor of (something)
  • No consensus for or against (something)
  • Consensus against (something)

If you write only "There was no consensus", then editors may be confused about whether you meant that no general agreement was reached or if you were trying to find a gentle way to indicate that an idea was rejected. They may also disagree later about what, exactly, wasn't agreed to.

Policy

Many closures are also based upon Wikipedia policy. As noted above, arguments that contradict policy are discounted.

Wikipedia core policies, which requires that articles and information be verifiable, avoid being original research, and be written from a neutral point of view, as well as legal policies that require articles not violate copyright or be defamatory, are not negotiable, and cannot be superseded by any other guidelines or by editors' consensus. A closer must determine whether any article violates policy, and where it is very unlikely that an article on the topic can exist without breaching policy, it must be respected above individual opinions.[3]

Closure procedure

Most discussions don't need closure at all, but when they do, any uninvolved editor may close most of them – not just admins.[4] Generally, if you want to request closure by an uninvolved administrator, it's expected that the discussion will have already been open at least a week, and that the subject is particularly contentious or the outcome is unclear.

Requesting a close

If consensus remains unclear, if the issue is a contentious one, or if there are wiki-wide implications, a request for a neutral and uninvolved editor to formally close a discussion may be made at Wikipedia:Closure requests. Please ensure that any request there seeking a close is neutrally worded, and do not use that board to continue the discussion in question.

Marking a closed discussion

Closing a discussion means putting a box around it for the purpose of discouraging further contributions to that discussion. Please do not close a discussion if you believe that further contributions (rather than starting a fresh discussion on the same subject) would be appropriate.

To close a discussion, use the {{archive top}} and {{archive bottom}} templates (although some particular types of discussion, such as those which concern whether to delete or rename a page, have their own specialized templates). For example:

==Discussion heading==
{{archive top}}
Discussion text...
{{archive bottom}}

The closed discussion will then look like this:

Discussion heading

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.


Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.

The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

The closed discussion can also be collapsed to save space. This is achieved by using the templates {{hidden archive top}} and {{hidden archive bottom}}. Because of the short name of the first of those templates – {{hat}} – performing such a closure is referred to as hatting.

Writing a summary

Sometimes, it is helpful for an editor to provide a summary statement of the outcome, if any, when closing the discussion. This optional statement may include both points of consensus and points that are not yet resolved.

{{Archive top
|status = withdrawn
|result = I've decided my idea needs some work.  Thanks to everyone for the advice.  ~~~~
}}
{{lorem ipsum}}
{{Archive bottom}}

which will look like this:

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.


Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.

The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Additional summary format

This format is designed specifically for closes involving written analysis or conclusions of the discussion. Either this format or the former is acceptable for closes involving analysis (which chosen is at the closers discretion), but this format should not be used for closes involving no summarization.

{{Discussion top|I've decided my idea needs some work.  Thanks to everyone for the advice.  ~~~~ }}
{{lorem ipsum}}
{{Discussion bottom}}

which will look like this:

The following discussion is closed. Please do not modify it. Subsequent comments should be made in a new section. A summary of the conclusions reached follows.
I've decided my idea needs some work. Thanks to everyone for the advice. User:Example (talk) 17:24, 15 August 2018 (UTC)[reply]

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.

The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Challenging a closure

All discussion closures are subject to review. Usually, reviews are initiated because someone disputes the outcome stated by the closing editor (e.g., a summary statement that some editors find confusing or incorrect), rather than the decision to discourage further discussion.

Depending on the type of discussion, a review will take place at one of several review boards, and distinct criteria are used for each board. In general, deletions are discussed at WP:Deletion review, moves are discussed at WP:Move review, and other closures (including requests for comment[5]) are discussed at WP:AN. Specific instructions about each case are described in the subsections below. Any editor may participate in a discussion reviewing a close.

Remember that most contentious discussions benefit from a formal closing statement, and that closers undertake to assess consensus to the best of their abilities.

Challenging a deletion

For reviewing a closure of a deletion discussion, the Deletion review process is used.

Deletion review (DRV) is for reviewing speedy deletions and outcomes of deletion discussions. This includes appeals to delete pages kept after a prior discussion.

If you are considering a request for a deletion review, please read the "Purpose" section below to make sure that is what you wish to do. Then, follow the instructions below.

Purpose

Deletion review may be used:

  1. if someone believes the closer of a deletion discussion interpreted the consensus incorrectly;
  2. if a speedy deletion was done outside of the criteria or is otherwise disputed;
  3. if significant new information has come to light since a deletion that would justify recreating the deleted page;
  4. if a page has been wrongly deleted with no way to tell what exactly was deleted; or
  5. if there were substantial procedural errors in the deletion discussion or speedy deletion.

Deletion review should not be used:

  1. because of a disagreement with the deletion discussion's outcome that does not involve the closer's judgment (a page may be renominated after a reasonable timeframe);
  2. (This point formerly required first consulting the deleting admin if possible. As per this discussion an editor is not required to consult the closer of a deletion discussion (or the deleting admin for a speedy deletion) before starting a deletion review. However doing so is good practice, and can often save time and effort for all concerned. Notifying the closer is required.)
  3. to point out other pages that have or have not been deleted (as each page is different and stands or falls on its own merits);
  4. to challenge an article's deletion via the proposed deletion process, or to have the history of a deleted page restored behind a new, improved version of the page, called a history-only undeletion (please go to Wikipedia:Requests for undeletion for these);
  5. to repeat arguments already made in the deletion discussion;
  6. to argue technicalities (such as a deletion discussion being closed ten minutes early);
  7. to request that previously deleted content be used on other pages (please go to Wikipedia:Requests for undeletion for these requests);
  8. to attack other editors, cast aspersions, or make accusations of bias (such requests may be speedily closed);
  9. for uncontroversial undeletions, such as undeleting a very old article where substantial new sources have subsequently arisen. Use Wikipedia:Requests for undeletion instead. (If any editor objects to the undeletion, then it is considered controversial and this forum may be used.)
  10. to ask for permission to write a new version of a page which was deleted, unless it has been protected against creation. In general you don't need anyone's permission to recreate a deleted page, and if your new version does not qualify for deletion then it will not be deleted.

Copyright violating, libelous, or otherwise prohibited content will not be restored.

Instructions

Before listing a review request, please:

  1. Consider attempting to discuss the matter with the closer as this could resolve the matter more quickly. There could have been a mistake, miscommunication, or misunderstanding, and a full review may not be needed. Such discussion also gives the closer the opportunity to clarify the reasoning behind a decision.
  2. Check that it is not on the list of perennial requests. Repeated requests every time some new, tiny snippet appears on the web have a tendency to be counter-productive. It is almost always best to play the waiting game unless you can decisively overcome the issues identified at deletion.

Steps to list a new deletion review

 
1.

Click here and paste the template skeleton at the top of the discussions (but not at the top of the page). Then fill in page with the name of the page, xfd_page with the name of the deletion discussion page (leave blank for speedy deletions), and reason with the reason why the discussion result should be changed. For media files, article is the name of the article where the file was used, and it shouldn't be used for any other page. For example:

{{subst:drv2
|page=File:Foo.png
|xfd_page=Wikipedia:Files for deletion/2009 February 19#Foo.png
|article=Foo
|reason=
}} ~~~~
2.

Inform the editor who closed the deletion discussion by adding the following on their user talk page:

{{subst:DRV notice|PAGE_NAME}} ~~~~
3.

For nominations to overturn and delete a page previously kept, attach <noinclude>{{Delrev|date=2025 January 13}}</noinclude> to the top of the page under review to inform current editors about the discussion.

4.

Leave notice of the deletion review outside of and above the original deletion discussion:

  • If the deletion discussion's subpage name is the same as the deletion review's section header, use <noinclude>{{Delrevxfd|date=2025 January 13}}</noinclude>
  • If the deletion discussion's subpage name is different from the deletion review's section header, then use <noinclude>{{Delrevxfd|date=2025 January 13|page=SECTION HEADER AT THE DELETION REVIEW LOG}}</noinclude>
 

Commenting in a deletion review

Any editor may express their opinion about an article or file being considered for deletion review. In the deletion review discussion, please type one of the following opinions preceded by an asterisk (*) and surrounded by three apostrophes (''') on either side. If you have additional thoughts to share, you may type this after the opinion. Place four tildes (~~~~) at the end of your entry, which should be placed below the entries of any previous editors:

  • Endorse the original closing decision; or
  • Relist on the relevant deletion forum (usually Articles for deletion); or
  • List, if the page was speedy deleted outside of the established criteria and you believe it needs a full discussion at the appropriate forum to decide if it should be deleted; or
  • Overturn the original decision and optionally an (action) per the Guide to deletion. For a keep decision, the default action associated with overturning is delete and vice versa. If an editor desires some action other than the default, they should make this clear; or
  • Allow recreation of the page if new information is presented and deemed sufficient to permit recreation.

Examples of opinions for an article that had been deleted:

  • *'''Endorse''' The original closing decision looks like it was sound, no reason shown here to overturn it. ~~~~
  • *'''Relist''' A new discussion at AfD should bring a more thorough discussion, given the new information shown here. ~~~~
  • *'''Allow recreation''' The new information provided looks like it justifies recreation of the article from scratch if there is anyone willing to do the work. ~~~~
  • *'''List''' Article was speedied without discussion, criteria given did not match the problem, full discussion at AfD looks warranted. ~~~~
  • *'''Overturn and merge''' The article is a content fork, should have been merged into existing article on this topic rather than deleted. ~~~~
  • *'''Overturn and userfy''' Needs more development in userspace before being published again, but the subject meets our notability criteria. ~~~~
  • *'''Overturn''' Original deletion decision was not consistent with current policies. ~~~~

Remember that deletion review is not an opportunity to (re-)express your opinion on the content in question. It is an opportunity to correct errors in process (in the absence of significant new information), and thus the action specified should be the editor's feeling of the correct interpretation of the debate. Deletion review is facilitated by succinct discussions of policies and guidelines; long or repeated arguments are not generally helpful. Rather, editors should set out the key policies and guidelines supporting their preferred outcome.

The presentation of new information about the content should be prefaced by Relist, rather than Overturn and (action). This information can then be more fully evaluated in its proper deletion discussion forum. Allow recreation is an alternative in such cases.

Temporary undeletion

Admins participating in deletion reviews are routinely requested to restore deleted pages under review and replace the content with the {{TempUndelete}} template, leaving the history for review by everyone. However, copyright violations and violations of the policy on biographies of living persons should not be restored.

Closing reviews

A nominated page should remain on deletion review for at least seven days, unless the nomination was a proposed deletion. After seven days, an administrator will determine whether a consensus exists. If that consensus is to undelete, the admin should follow the instructions at Wikipedia:Deletion review/Administrator instructions. If the consensus was to relist, the page should be relisted at the appropriate forum. If the consensus was that the deletion was endorsed, the discussion should be closed with the consensus documented.

If the administrator closes the deletion review as no consensus, the outcome should generally be the same as if the decision was endorsed. However:

  • If the decision under appeal was a speedy deletion, the page(s) in question should be restored, as it indicates the deletion was not uncontroversial. The closer, or any editor, may then proceed to nominate the page at the appropriate deletion discussion forum, if they so choose.
  • If the decision under appeal was an XfD close, the closer may, at their discretion, relist the page(s) at the relevant XfD.

Ideally all closes should be made by an administrator to ensure that what is effectively the final appeal is applied consistently and fairly but in cases where the outcome is patently obvious or where a discussion has not been closed in good time it is permissible for a non-admin (ideally a DRV regular) to close discussions. Non-consensus closes should be avoided by non-admins unless they are absolutely unavoidable and the closer is sufficiently experienced at DRV to make that call. (Hint: if you are not sure that you have enough DRV experience then you don't.)

Speedy closes

  • Objections to a proposed deletion can be processed immediately as though they were a request at Wikipedia:Requests for undeletion
  • Where the closer of a deletion discussion realizes their close was wrong, and nobody has endorsed, the closer may speedily close as overturn. They should fully reverse their close, restoring any deleted pages if appropriate.
  • Where the nominator of a DRV wishes to withdraw their nomination, and nobody else has recommended any outcome other than endorse, the nominator may speedily close as "endorse" (or ask someone else to do so on their behalf).
  • Certain discussions may be closed without result if there is no prospect of success (e.g. disruptive or sockpuppet nominations, if the nominator is repeatedly nominating the same page, or the page is listed at WP:DEEPER). These will usually be marked as "administrative close".



DJ Hollygrove (talk|edit|history|logs|links|watch) (XfD|restore)

DJ Hollygrove grammy winner https://www.gettyimages.com/detail/news-photo/hollygrove-of-the-chopstars-sir-the-baptist-aaron-dubba-news-photo/1463285516?adppopup=true — Preceding unsigned comment added by 2600:1700:F991:9E50:F923:CBAA:724D:8AFE (talk) 01:50, 11 January 2025 (UTC)[reply]

https://www.gettyimages.com/detail/news-photo/larry-jenkins-jr-sir-the-baptist-aaron-dubba-aa-lockhart-news-photo/1463266133?adppopup=true 2600:1700:F991:9E50:F923:CBAA:724D:8AFE (talk) 01:52, 11 January 2025 (UTC)[reply]
  • Yeah, this is always the problem when an AfD is curtailed because the article is suitable for speedy deletion (which it was at that time). Whilst the processes were wrong, even the last (and best) version of this was sourced to four unreliable sources (IMDB, last.fm, MySpace and his own website) and wouldn't have survived an AfD. Still, I don't see a problem with Recreate as a redirect to The Chopstars and then see if anyone can create an article which shows notability. Black Kite (talk) 16:36, 11 January 2025 (UTC)[reply]
The following is an archived debate of the deletion review of the page above. Please do not modify it.
Fil-Products Group (talk|edit|history|logs|links|watch) (article|XfD|restore)

A WP:BADNAC: The page creator closed the discussion as "keep" on the same day it was opened with the only !votes for "delete." Requesting an uninvolved administrator to relist the discussion. (Mea culpa: I originally reverted the non-admin closure erroneously, seeing it as disruptive, before I had reviewed the provision at WP:NAC stating inappropriate early closures of deletion debates may either be reopened by an uninvolved administrator, and I have self-reverted.) Dclemens1971 (talk) 16:47, 8 January 2025 (UTC)[reply]

The above is an archive of the deletion review of the page listed in the heading. Please do not modify it.
The following is an archived debate of the deletion review of the page above. Please do not modify it.
Guite people (talk|edit|history|logs|links|watch) (XfD|restore)

I am not convinced that notability was adequately established. The article subject is a WP:CASTE topic, where many print sources are low-quality, partially based on oral tradition, or ethnically biased — so the nom's statement in a reply that the existing information "is all folklore and no authentic sources are available" is credible. See also WP:RAJ for more background.

Not all of the existing references were checked, but we identified several that are clearly unreliable, and two users failed to find substantive online sources. One user claimed to find various print sources, but did not identify any by name. None of the Keep !votes provided new sources that prove notability, or asserted the reliability of existing references; some users made unjustified assertions of the subject being "well-known". –LaundryPizza03 (d) 04:38, 7 January 2025 (UTC)[reply]

This was open for three weeks, and I certainly do not see a consensus to delete. I suppose I could have closed it as no consensus, but the end result is the same, so it's unclear to me what we are doing at DRV. Beeblebrox Beebletalks 06:41, 7 January 2025 (UTC)[reply]
  • Endorse Not a single person besides the nom put in a !vote for deletion. There were suggestions, and some indication that a sizeable minority of the references were not RS, but lots of people thought it was OK to keep, even if weakly. While there were a few commentators noting issues, not one, including the appellant, came out and said "This should be deleted". Hard to close it any other way, and I think Beeblebrox is being overly charitable--I don't see no consensus within reach here. Jclemens (talk) 07:08, 7 January 2025 (UTC)[reply]
  • Endorse. Deletion review is a venue to challenge failures to follow the deletion process. It is not a venue to seek a second bite at the cherry when the deletion discussion did not go your way. Stifle (talk) 09:11, 7 January 2025 (UTC)[reply]
  • Endorse: Well I see that there was surely no consensus for deletion and this is not the venue for doing these things.Also WP:RAJ is an essay not a policy. Mithilanchalputra(Talk) 11:21, 7 January 2025 (UTC)[reply]
  • Endorse and procedurally close per WP:DRVPURPOSE. The appellant made no claim that consensus wasn't read correctly, nor presented any significant new information to overturn the close. No one is obliged to convince the appellant that notability was adequately established. Owen× 14:13, 7 January 2025 (UTC)[reply]
  • Endorse there's simply no way to close that discussion as delete, even if you completely down-weight all of the keep !votes. SportingFlyer T·C 20:52, 7 January 2025 (UTC)[reply]
  • Endorse. Ridiculous DRV nomination. Read advice at WP:RENOM. SmokeyJoe (talk) 12:38, 8 January 2025 (UTC)[reply]
  • Endorse - The only possible closure. Does the appellant have some reason why they think that the AFD was handled erroneously? On its face, it appears that they simply disagree with the community, but that is not what DRV is for. Robert McClenon (talk) 20:16, 8 January 2025 (UTC)[reply]
  • Endorse. The comments toward the end (only after the second relist and the request to review individual sources) look like the start of a WP:BEFORE. They don't look like arguments for deleting the page, more like preparatory work for such arguments. Too little too late.—Alalch E. 03:03, 10 January 2025 (UTC)[reply]
  • Endorse - I didn't !vote for deletion, but I did ask for consideration for renaming (moving) this. The admin did the correct thing. Bearian (talk) 04:24, 11 January 2025 (UTC)[reply]
The above is an archive of the deletion review of the page listed in the heading. Please do not modify it.
The following is an archived debate of the deletion review of the page above. Please do not modify it.
STONEX India (talk|edit|history|logs|links|watch) (XfD|restore)

It seems a bit too early to close this discussion, especially when three relatively new editors, who may not be fully familiar with the notability guidelines, have voted to keep the article with very vague rationales - "plenty reliable sources are present", "added two books that provide significant coverage." (which do not actually provide significant coverage), and "I found sufficient coverage in reliable sources to justify keeping the page on Wikipedia." While I suspect UPE activity, that is a matter for another day. Requesting a re-list of this discussion. Jeraxmoira🐉 (talk) 20:06, 6 January 2025 (UTC)[reply]

The above is an archive of the deletion review of the page listed in the heading. Please do not modify it.
The following is an archived debate of the deletion review of the page above. Please do not modify it.
Mink (manga) (talk|edit|history|logs|links|watch) (XfD|restore)

Wikipedia:Articles for deletion/Mink (manga) shows that the article was deleted in 2009 due to lack of sources establishing notability. I have since found some sources for the article, such as reviews from Anime News Network (1, 2) and Da Vinci (1). I have also found an old interview from 2000 from the creator of the series here. I have done a full rewrite as a draft. The admin who deleted the article has not been active since May 2024 and the person who nominated the article for deletion is no longer active on Wikipedia since 2010. lullabying (talk) 03:20, 6 January 2025 (UTC)[reply]

The above is an archive of the deletion review of the page listed in the heading. Please do not modify it.


The following is an archived debate of the deletion review of the page above. Please do not modify it.
Donald President (talk|edit|history|logs|links|watch) (XfD|restore)

Consensus has been reached, but could use review. — Preceding unsigned comment added by 2025 2601:483:400:1cd0:a1a4:fd62:9508:f4eb (talkcontribs) 02:40, 5 January (UTC)

The above is an archive of the deletion review of the page listed in the heading. Please do not modify it.
The following is an archived debate of the deletion review of the page above. Please do not modify it.
Raegan Revord (talk|edit|history|logs|links|watch) (XfD|restore)

While I'm suspecting that the result of closure will not be changed, I'm asking that an admin review the closure, as its the manner is troubling in two ways.

  • This was a non-admin closure on a discussion that was not uncontentious, with, in addition to the original deletion request, my !vote for delete and Gråbergs Gråa Sång, who did not !vote, arguing that the article did not meet WP:GNG
  • The closure explanation begins "I would say that judging by the votes below, she just about passes the notability criteria." which suggests that the closer was treating it as an actual vote and that they feel that the arguments paint the subject as not actually passing the notability criteria, which suggests a misunderstanding of "consensus". Nat Gertler (talk) 15:47, 3 January 2025 (UTC)[reply]
  • Overturn and Relist - This was a possibly contentious closure by a non-admin. After one week, a relist was reasonable, and the closer's statement is a little too much like a vote or a supervote. I see no need to vacate the close and let an admin close it when we, Deletion Review, can decide that it should be relisted. Robert McClenon (talk) 16:09, 3 January 2025 (UTC)[reply]
The above is an archive of the deletion review of the page listed in the heading. Please do not modify it.
The following is an archived debate of the deletion review of the page above. Please do not modify it.
Category:Fulbright Scholars (talk|edit|history|logs|links|watch) (XfD|restore)

The discussion page shows a problem. The reasoning given for deleting this category was that it's nondefining for a scholar--that if they receive this, they're already alumni of the school that awarded it. See https://fulbrightscholars.org/ for Scholar and Distinguished Scholar awards, and https://us.fulbrightonline.org/fulbright-us-student-program for the studentships that the original nominators for this category deletion confused for the Fulbright Scholar Award.

A Fulbright Scholar Award or Distinguished Scholar Award goes to senior academics and practitioners, and is career-defining--the kind of thing that goes in one's obituary. It is not the same thing as a Fulbright studentship which is scholarship money awarded to grad students who would be listed as alumni of a given school. While a scholarship would typically be money granted to a grad student and a fellowship would be for senior academics, it's the opposite here. Typical Fulbright Scholars include James Galbraith, Donald Regan, Robert Rotberg, etc.

There is already a partial of notable Fulbright Scholars but it's serving as a backdoor to this now-missing category. The Fulbright Program page includes it, along with a clear distinction between the two main categories of Scholar grants and Student grants.

Fulbright Study/Research Fellows or Students (those younger grad students the original deleters of this category were speaking of) typically would not have Wikipedia pages or be notable yet. Some extremely notable Fulbright Scholars and Distinguished Scholars don't appear on that page, such as Richard Rosecrance, John Lewis Gaddis, Shaun Gabbidon, Alejandro de la Fuente, and so forth. This list should also include the incomplete list found at https://en.wikipedia.org/wiki/Category:Fulbright_Distinguished_Chairs.

It would be a service to this wiki to include Fulbright Scholars and Fulbright Distinguished Scholars via category rather using the original name of "Category:Fulbright Scholars" than in the scattershot way of hoping someone had listed them under the notables on the original page.

RubyEmpress (talk) 05:11, 3 January 2025 (UTC)[reply]

  • Endorse. The close correctly reflected unanimous agreement at the CfD. The appellant says that some Distinguished Scholar Award recipients are notable. This is true, but does not contradict the claim that most award recipients are not notable, and that the award itself is non-defining. In fact, of the three examples of "Typical Fulbright Scholars" examples she gives, none mention the award. The appellant has not presented significant new information per WP:DRVPURPOSE#3. This is just another kick at the can. Owen× 08:34, 3 January 2025 (UTC)[reply]
  • Endorse. Deletion review is a venue to address failures to follow deletion process. It is not a venue for re-arguing the deletion discussion because it did not go your way. Stifle (talk) 15:10, 3 January 2025 (UTC)[reply]
  • Question - Are deletions of categories different from deletions of articles as to when they can be reviewed? Are deletions of categories effective for five years or ten years or forever rather than six months? Is that why need a Deletion Review? Or is there some way that Consensus Can Change? Are we really locked in to a three-year-old decision? Is taking another look at a three-year-old decision really another kick at the can?Robert McClenon (talk) 15:57, 3 January 2025 (UTC)[reply]
    The lapse of time itself is irrelevant, if no significant new information is presented. This appeal only claims that the CfD participants erred in their assessment, which isn't a valid DRV claim, not to mention that she hasn't even established the veracity of that claim. Based on the argument she presents here, there is no more of a case for keeping that category today than there was when it was deleted three years ago. Owen× 16:40, 3 January 2025 (UTC)[reply]
  • Question - Is this an appeal to overturn a three-year-old deletion decision, or is this a request to create a new category three years after the category was deleted? This appears to be a request to create a new category three years after the deletion. Do we need Deletion Review for the purpose? Can the appellant just do it? Is DRV unnecessary? Robert McClenon (talk) 15:57, 3 January 2025 (UTC)[reply]
  • Endorse It's difficult to endorse an old discussion with only three participants, so I'm treating this DRV more like a new CfD because I'm not sure what else to do - but I do agree it's non-defining especially per Owenx and that it would be deleted again if it were re-created for the same reason it was deleted before. SportingFlyer T·C 17:33, 3 January 2025 (UTC)[reply]
  • Comment This isn't policy but for practical purposes, I've found that CFD decisions are considered valid forever. Unlike article deletions which have a Draft space where editors can work on improving the content of a recreated article, that possibility doesn't exist for categories. I've seen categories CSD G4'd from decisions that occurred years and years ago. I'm not a frequent participant there any longer but my perception is that CFD decisions are rarely reviewed and reassessed. I would like this to change because CFD decisions are usually determined by a very small number of editors and shouldn't last forever but I'm not sure that if this discussion would be setting any precendent for the future. Liz Read! Talk! 06:56, 4 January 2025 (UTC)[reply]
    I don't think it should change. G4 should apply indefinitely, and recreation should be allowed via DRV provided some new fact, and changes of the PAG landscape, of recent practices, examples of other categories kept at CfD in the meantime can also be significant new facts. —Alalch E. 17:31, 4 January 2025 (UTC)[reply]
    I agree with Liz that there needs to be an appropriate venue to review CfD discussions, but Alalch E.'s comment highlights the problems with using DRV to do so: Everyone's opining "nothing has changed" which may be true, but does not consider "was this even the right decision in the first place?" Three people opined, and the closer and some other number of people looked at it and didn't participate. That doesn't seem to be enough discussion to make a category G4-able forever since, unlike articles, categories cannot be changed to be not substantially similar to what was previously deleted. Jclemens (talk) 00:05, 6 January 2025 (UTC)[reply]
  • Endorse. Everything the DRV nom states was the same at the time of the 2021 CfD, so there are no new facts based on which to allow recreation consistent with WP:DRVPURPOSE#3.—Alalch E. 17:39, 4 January 2025 (UTC)[reply]
  • Endorse as a correct reading of consensus. I feel the same way I did in the DRV Cryptic linked: "I'm sympathetic to the argument that editors should be able to 'test' an old consensus every once in a while (along the lines of WP:CCC), but in this case it's very clear to me that a new CfD will lead to the same result, so I think !voting to [allow recreation] would be an exercise in futility." Extraordinary Writ (talk) 00:11, 5 January 2025 (UTC)[reply]
  • No Opinion at this time. The idea that category deletions last forever makes things problematic. Robert McClenon (talk) 06:12, 5 January 2025 (UTC)[reply]
  • relist A) apparently we don't allow recreation even 3 years later so a relist is the only way to restore it B) IMO the two arguments show an utter lack of a clue. This can very much be defining, and per the nom, often shows up in orbits. It's a lot more than just a scholarship. Two !votes 3 years ago shouldn't make it impossible to restore this. A relist is the only way forward apparently. Hobit (talk) 05:24, 10 January 2025 (UTC)[reply]
The above is an archive of the deletion review of the page listed in the heading. Please do not modify it.
The following is an archived debate of the deletion review of the page above. Please do not modify it.
Category:Trees of the Eastern United States (talk|edit|history|logs|links|watch) (XfD|restore)

An extension of the proposal was brought up and sought comments from earlier participants, but the discussion was closed less than 15 minutes later. –LaundryPizza03 (d) 04:18, 31 December 2024 (UTC)[reply]

I read MtBotany's comment as supporting a single Trees of Northern America, given they opposed a "trees of the United States". Compassionate727 implied that keeping the originally nominated category might be a viable alternative, but explicitly stopped short of opposing the proposal. MtBotany's comment opposed having any sort of "US" division, which I interpret as supporting a triple merge. The Bushranger explicitly wanted a triple merge (explicitly). You wanted to rename, which would have kept the US categories but combined together. Finally, WP:RELISTed discussions can be closed whenever consensus is achieved, to say nothing of twice-relisted discussions which have been past the seven-day mark for over 24 hours.
I am going to stand by this closure, though I will hold off on implementing it until this DRV is closed. If you need anything else from me, let me know. Best, HouseBlaster (talk • he/they) 05:17, 31 December 2024 (UTC)[reply]
The above is an archive of the deletion review of the page listed in the heading. Please do not modify it.
  • Patrik Kincl – While not the fault of the closer of AfD2 reading that discussion in isolation (as noted by SportingFlyer's comment), consensus of editors below is that AfD2 reached the wrong outcome — in the context of timing & AfD1, as well as a level of contention regarding representations made by the AfD2 nominator on the topic of sources. Consensus here at DRV is to overturn the deletion at AfD2 and restore the article. Regarding a potential renomination at AfD3, if any interested editor wishes to do so, please see the comments below from experienced editors & administrators. Daniel (talk) 08:24, 12 January 2025 (UTC)[reply]
The following is an archived debate of the deletion review of the page above. Please do not modify it.
Patrik Kincl (talk|edit|history|logs|links|watch) (XfD|restore)

The first nomination was closed by OwenX as Keep without prejudice against early renomination, while the second was closed by Xplicit as simply Delete.

The second nominator incorrectly claimed that the "good faith" sources that told about Kincl's "personal life" in the first nomination were not reliable and independent. It may be true or not. Of the five sites, those are secondary in my view. Deník is one of the most frequently used sources for Czech Republic-related Wikipedia articles, so as a daily newspaper, it is reliable and secondary. From what I remember, there seem to be not more than five secondary sources before the page's deletion, then their opinion is asked without using a translator at least first.

⋆。˚꒰ঌ Clara A. Djalim ໒꒱˚。⋆ 12:23, 31 December 2024 (UTC)[reply]

  • Overturn It looks like a unanimous delete, but the result here is clearly wrong (not the fault of the closer, though). The second discussion started a day after the first ended so you have to view the first together, none of the participants from the first discussion were pinged, and there were a number of sources listed in the first discussion which weren't discussed or even acknowledged in the second discussion. The simple fact here is that there are many sources if you search in Czech, from all of the top newspapers. This is a list of articles where he's mentioned on only one Czech website: [3], and the other sources in the first AfD were from one of the top Czech news websites, though they appear paywalled. These were incorrectly discounted, and the article should be restored and marked for improvement. SportingFlyer T·C 03:15, 1 January 2025 (UTC)[reply]
  • Comment as Discussion Starter: The article was nominated for deletion by the fact it failed WP:NMMA, as the person has not been ranked in the world top 10 by either Sherdog or Fight Matrix websites. Even if they meet SNG, all articles of sportspeople or any other public figures must meet the whole WP:GNG for the best and most important. ⋆。˚꒰ঌ Clara A. Djalim ໒꒱˚。⋆ 14:40, 1 January 2025 (UTC)[reply]
  • Overturn per Clariniie's above comment. Anything can always meet GNG and be notable, until and unless we agree to change N to say otherwise, and SportingFlyer has made a compelling case that that general coverage was inadequately assessed. Jclemens (talk) 01:01, 2 January 2025 (UTC)[reply]
  • Question - What are we at Deletion Review being asked to do? The AFD was closed as Delete. What is the appellant asking for? Robert McClenon (talk) 07:15, 2 January 2025 (UTC)[reply]
    To fix the mess. —Alalch E. 17:23, 4 January 2025 (UTC)[reply]
  • Destroy the 2nd AfD. Faulty process. It should never be like this. Immediate renomination that bypasses the recent discussion that resulted in keep with a nomination that waves away the arguments which led to the consensus to keep is bad. The whole second AfD should be voided as if it had never existed, and the first AfD should be amended to erase the words "without prejudice against early renomination, if source analysis warrants it". That part of the first AfD's close which creates consequences in the future negatively affects the overarching process of getting to a decision on whether to keep or delete the article. It negatively affects precisely because it enabled a non-constructive AfD like the second one. Currently, the decision is to keep. To start a new AfD, WP:RENOM should be followed.—Alalch E. 17:21, 4 January 2025 (UTC)[reply]
    Would you have found a "No consensus" close for the first AfD more acceptable? Consensus to keep was marginal at best. There was no valid reason to shut the door on a justified early renomination. And a N/C close would have practically resulted in the same outcome here - an immediate second AfD. WP:RENOM is a widely-followed essay meant to prevent excessive churn at AfD. When the outcome is a marginal, a renomination is well justified. Owen× 17:33, 4 January 2025 (UTC)[reply]
    The deletes didn't meet the burden to delete. There was a decent effort early on, but through the relist periods and in totality there was not enough argumentation on the delete side. What about the late sources? That had to be a keep. it was a WP:ROUGHCONSENSUS. It was an imperfect AfD but it was still roughly representative of what we want to see in AfD. It was pretty average, not requiring any special measures via the close in addition to the simple outcome. Allowing an early renomination was just asking for someone who for whatever reason disagrees with this article existing to skirt around the discussion and the rough consensus reached. Even with a 'no consensus' close, the article should generally not be immediately renominated, and administrators are justified in shutting down such discussions as non-constructive, instructing interested editors to wait. —Alalch E. 17:51, 4 January 2025 (UTC)[reply]
  • No Opinion at this time until I understand what we are supposed to be doing here. If I don't understand what is being asked, then I shouldn't either vote or !vote. Robert McClenon (talk) 06:15, 5 January 2025 (UTC)[reply]
  • Take no action. The review request is largely unintelligible and does not indicate which if any action we are requested to take. The "overturn" opinions above likewise do not indicate what other closure of the deletion discussion they would consider correct. Accordingly, I would decline to take action. Sandstein 16:43, 8 January 2025 (UTC)[reply]
    I'd either vacate the second AfD or allow the article to be restored, without prejudice for a third AfD. If you take the two AfDs together (considering one started a day after the other finished) there is no consensus to delete. SportingFlyer T·C 23:37, 8 January 2025 (UTC)[reply]
  • Overturn: while there was nothing wrong with the speedy renomination here, it's not fair to do so without notifying the previous participants. Since it's been eight months, the most straightforward solution would be to relist in a new AfD, pinging everyone from AfD 1 and AfD 2. I'd also be fine with restoring (to either mainspace or draftspace). Extraordinary Writ (talk) 06:47, 9 January 2025 (UTC)[reply]
  • Overturn AfD2 due to too soon nomination and failure to notify participants from the prior AfD.
Chastise User:OwenX for inviting an early renomination. That was a bad call. It is rarely a good idea. After a long running AfD, the few interested editors are exhausted, and time is needed for everyone to take a few breaths. Following a “keep” the standard is six months wait to renominate, stick with that unless you have good reason not to, and the close gave no explanation as to why the might be any such good reason. SmokeyJoe (talk) 21:55, 11 January 2025 (UTC)[reply]
The above is an archive of the deletion review of the page listed in the heading. Please do not modify it.
Archives, by year and month
Year Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2025 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2024 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2023 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2022 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2021 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2020 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2019 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2018 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2017 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2016 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2015 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2014 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2013 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2012 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2011 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2010 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2009 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2008 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2007 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2006 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec

Challenging a move

For reviewing a closure of a page move discussions, the Move review process is used.

Move review may be used:

  1. if an editor believes the closer did not follow the spirit and intent of WP:RMCI in closing this requested move.
  2. if the closer was not made aware of significant additional information not discussed in the RM, and the RM should be reopened and relisted.

Challenging other closures

For other procedures, whether formal RfCs or less formal ones such as merging or splitting, contact the editor who performed the closure and try to resolve the issue through discussion. If you are unable to resolve the issue through discussion with the closer, you may request review at the Administrators' Noticeboard. Before requesting review, understand that review should not be used as an opportunity to re-argue the underlying dispute, and is only intended for use when there is a problem with the close itself.

Closures will often be changed by the closing editor without a closure review:

  1. if significant additional information or context was left out of the discussion and the closer was not aware of it.
  2. if the discussion was undertaken under modified procedural rules that the closer was not aware of.
  3. if an early closure is followed by multiple editors asking that it be reopened for further discussion, or a single editor has brought forth a compelling new perspective to the already closed discussion.

Closures will rarely be changed by the closing editor, but can be challenged in a closure review:

  1. if you believe the closure was not a reasonable summation of the discussion
  2. if the closing editor may have become inextricably involved through previous experience in the conflict area.

Closures will rarely be changed by either the closing editor or a closure review:

  1. if the poll was close or even favored an outcome opposite the closure, if the closure was made on the basis of policy. Policies and guidelines are usually followed in the absence of a compelling reason otherwise, or an overwhelming consensus otherwise, and can only be changed by amending the policy itself.
  2. if the complaint is that the closer is not an admin.[6]

After discussing the matter with the closing editor, you may request review at the Administrators' noticeboard. For reviews of requests for comment closures, you may use {{subst:RfC closure review}} to start a review (refer to instructions in that template). In your reasoning, you should give a concrete description of how you believe the close was an inappropriate or unreasonable distillation of the discussion. You are more likely to succeed in your AN request if you focus on 1. an "underlying policy/guideline" and 2. "strength of argument". (See WP:ROUGHCONSENSUS) For example, continue your AN request opening with something like: The issue the closer was to decide was (describe issue). In closing, they applied policy X. I believe that policy Y should have been taken more into account / policy X never intended to apply to issues such as this.

Users who try to subvert consensus by appealing to other venues than WP:AN should be aware of WP:FORUMSHOP.

See also

References

  1. ^ Some common causes for rapid closure include:
    • The discussion was withdrawn by the person who started it.
    • Stopping discussions that are happening in multiple places or otherwise in the wrong place. (example).
    • Stopping disruptive or misguided discussions (example).
  2. ^ Wikipedia:Guide to deletion § Closure
  3. ^ a b Wikipedia:Deletion guidelines for administrators § Rough consensus
  4. ^ In uncontentious circumstances, even an involved editor may close a discussion. For example, if you propose something, and it's obvious to you that nobody agrees with you, then you can close the discussion, even though you're obviously an "involved" editor.
  5. ^ See this discussion
  6. ^ A request for comment discussed how to appeal closures and whether an administrator can summarily overturn a non-administrator's closure. The consensus was that closures should not be reverted solely because the closer was not an administrator.