Wikipedia:Deletion review
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:
- if someone believes the closer of a deletion discussion interpreted the consensus incorrectly;
- if a speedy deletion was done outside of the criteria or is otherwise disputed;
- if there were substantial procedural errors in the deletion discussion or speedy deletion (including information of socks participating in the discussion);
- if significant new information has come to light since a deletion that would justify undeleting the page, and previously deleted content may be helpful for writing a new version of the page – provided that an administrator declined undeleting the page and their decision is being challenged;
- if a page has been wrongly deleted with no way to tell what exactly was deleted;
- if the deleted page cannot be recreated because of preemptive restrictions on creation that cannot be removed without a consensus after removal was requested and declined. Such restrictions include creation protection and title blacklisting.
Deletion review should not be used:
- to request undeletion of a page deleted on grounds which permits summary undeletion. Place such requests at Wikipedia:Requests for undeletion. Deletion review can be used if such a request is declined. (Undeletion may also be requested there for pages which are not explicitly eligible for summary undeletion, but such a request is usually declined; it is worth trying when substantial new sources have arisen after an article was deleted.)
- to ask for permission to write a new version of a page which was deleted, unless a preemptive restriction on creation is in place for which removal was requested and declined. In the case of:
- creation protection – request removal of the protection from the protecting administrator or, if the administrator is unavailable or non-responsive, request at Wikipedia:Requests for page unprotection.
- title blacklisting – file a delisting request at MediaWiki talk:Titleblacklist.
- 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);
- to repeat arguments already made in the deletion discussion;
- to argue technicalities (such as a deletion discussion being closed ten minutes early);
- 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);
- 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);
- to request that previously deleted content be used on other pages (please go to Wikipedia:Requests for undeletion for these requests);
- to attack other editors, cast aspersions, or make accusations of bias (such requests may be speedily closed).
Copyright violating, libelous, or otherwise prohibited content will not be restored.
Instructions
Before listing a review request, please:
- 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.
- 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. |
and paste the template skeleton at the top of the discussions (but not at the top of the page). Then fill in {{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:
|
| 3. |
For nominations to overturn and delete a page previously kept, attach |
| 4. |
Leave notice of the deletion review outside of and above the original deletion discussion:
|
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
- An objection to a proposed deletion can be processed immediately as though it 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, a large language model is used to construct the request, or the page is listed at WP:DEEPER). These will usually be marked as "procedural close".
The outcome of Wikipedia:Articles for deletion/76.1 FM (2nd nomination) included arguments that would invalidate this AfD closure. In particular, arguments that the frequency articles are disambiguations or set-inddex articles would justify this page, since at least two of the stations had articles. –LaundryPizza03 (dc̄) 11:11, 13 January 2026 (UTC)
- I'm sympathetic to the argument, but did you discuss this with the closer? The discussion is a clear delete on its own, there is no way someone closing this would have been aware of the other AfD, and it seems like there's a chance this could be speedily reopened without coming here. SportingFlyer T·C 11:46, 13 January 2026 (UTC)
- Endorse. Firstly, the 76.1 FM massively-bundled AfD was closed inaccurately. Glossary definition WP:TRAINWRECK is not a valid speedy keep criterion. The nomination wasn't made in bad faith, nor does it fall into any of the other criteria of WP:SK. Did the closer mean Snow keep? I know Svartner to be a very methodical, knowledgeable AfD participant and closer. The distinction here is purely technical, as the outcome would be Keep regardless. The community has made it clear it doesn't have the appetite to handle a 340-item bundled nomination, regardless of merit. Bearcat makes a strong argument that such pages serve an important and useful purpose in directing readers to the relevant station page. That is an argument for a Keep !vote, as he did in the first AfD for the bundle, not for a "Procedural keep" as he did in the second. Which brings us to the 1368 AM AfD. None of what was said at the 76.1 FM bundled nomination "invalidates" how 1368 AM was closed. 76.1 FM was (incorrectly) closed procedurally after six hours, not by consensus on merits of such pages. Even if we wanted to treat it as a binding precedent, all it tells us is that a radio station frequency page, when nominated alongside hundreds of others, will not be deleted. If there's community consensus to retain radio station frequency pages, then let's document this consensus at WP:NRADIO. But even then, this wouldn't "invalidate" the unanimous consensus reached specifically for 1368 AM. I share the appellant's desire to see all pages of this type handled identically. Alas, our process doesn't guarantee this. When we try to discuss all such pages in aggregate, people cry "TRAINWRECK!", and when we discuss them individually, folks complain we're being inconsistent. The best venue to handle our situation is at WT:Notability (media), pinging all participants of the two AfDs and the relevant wikiprojects. If consensus is indeed to keep all such pages, a simple request at REFUND, linking to the discussion, would have the page restored. Owen× ☎ 14:27, 13 January 2026 (UTC)
- Endorse unanimous consensus to delete. The large bundled nomination being kept (correctly) without prejudice against individual nominations has no bearing on how this one individual article's AFD was closed. The closer of the bundled AFD erred is calling it a "speedy keep" rather than a "procedural close," though they have the same end result. Frank Anchor 14:37, 13 January 2026 (UTC)
- Endorse unanimous consensus to delete. Each AfD should be treated individually, especially if this was the first nomination of the subject. --Enos733 (talk) 17:02, 13 January 2026 (UTC)
- Endorse, but maybe I don't understand the logic of this Deletion Review request. If I am reading this correctly, there was a request to delete 340 station lists or station articles, and the closer, and so the community, dismissed it, either as a train wreck or as too large a request to consider at once, or for some other reason. The appellant now apparently wants to reverse the deletion of 1368 AM on this basis. If I do understand this request, I think it is frivolous litigation because the dismissal of the 340-article package did not look at any of the individual 340 articles. Also, I agree with OwenX in endorsing the close, but I think that I disagree with their criticism of the close of the 340-article package. Are they saying that we should have considered each of the 340 articles in detail? Or are they just saying that the closer should have explained their close differently? It looks to me as though the appellant is trying to confuse the jury, and I am not sure what OwenX is saying. Robert McClenon (talk) 20:12, 13 January 2026 (UTC)
- The argument is that basically the reasoning for deletion of 1368 AM was incorrect because everyone overlooked the fact it was a valid disambiguation page and not a non-notable list, based on the arguments made at the bulk AfD. The bulk AfD criticism is just that it should have been a snow keep instead of a speedy keep. It's essentially a distinction without a difference, but the criticism is correct. SportingFlyer T·C 20:29, 13 January 2026 (UTC)
- My criticism of the 340-item close was that it doesn't qualify for "speedy keep", since it doesn't meet any of the WP:SK criteria. If the community refuses to engage on merits, the massively bundled AfD can be procedurally closed with no action. A "snow keep" close could also be possible, although personally, after discarding all the !votes based solely on a glossary definition, I doubt we had quorum, let alone a "SNOW" situation. In the end, as I said, the distinction is purely academic, as the discussion wasn't headed in any useful direction. There's nothing to amend with either of the two recent AfD closes. Owen× ☎ 20:38, 13 January 2026 (UTC)
- I'm not sure these do technically fail NLIST/NOT, and if I had closed this as a delete and had been asked I'd reopen my close to allow that argument to be made based on the arguments made at the other discussion, not because the other discussion was a keep. But since there was no error by the closer and this looks likely to be endorsed, I think the correct next step would be some sort of RfC on the notability of these articles. It's clear at least some are valid pages. All of them might be valid navigational pages. And if all of them are valid, we can restore this one. But that absolutely is not the purview of DRV. (I also don't think it's the purview of AfD. Mass deletion discussions are not the best way to make decisions on the notability of article topics, because you just need one of the articles to be notable for any reason to negate the entire AfD.) SportingFlyer T·C 20:27, 13 January 2026 (UTC)
- Comment – I even sent a message to LaundryPizza saying that the closure was due to the community not being able to evaluate around 300 articles at once. It doesn't even address the merits of the issue. I understand that he already has a more in-depth analysis and judges that they are not necessary since the bundle is made in good faith, but other users need to check each case individually. Svartner (talk) 22:54, 13 January 2026 (UTC)
- User:Great Classical Poet Hazrat Maulvi Ghulam Rasool Alampuri (talk||history|logs|links|watch) (restore)
This is a draft article on a user page which was deleted under G11 for being promotional. The subject is a long dead Punjabi poet. The tone is clearly wrong and the article is unsourced, but this should not have been speeded. The subject is probably notable if rewritten and moved to article space. Secretlondon (talk) 12:14, 11 January 2026 (UTC)
- I don't think this reached G11 either, but it's an unacceptably close paraphrase of this. It's overwhelmingly likely they're independent translations from a common source. —Cryptic 12:28, 11 January 2026 (UTC)
- Endorse, based only on the appellant's statement, without having seen the deleted page. The appellant states:
This is a draft article on a user page
, but that means that it was a fake article, and the user page guideline states:Actual fake articles should be deleted as incompatible with the purpose of the project.
Draft space might have been a more appropriate place, but Cryptic notes a close paraphrase problem. There is no need to restore it to improve it, because the source exists for use as a source. This was, by the appellant's statement, a good faith misuse of user space. Robert McClenon (talk) 17:43, 11 January 2026 (UTC) - Endorse as a G12 per Cryptic. Contra Robert McClenon, using a user page itself as a sandbox isn't what FAKEARTICLE is about, but that has no bearing on this: an article on the topic would be welcome if appropriate, and promotional tone and copyright concerns are two serious issues to be avoided, in addition to demonstrating notability. Jclemens (talk) 22:59, 11 January 2026 (UTC)
- Send to AFD, provided there is anyone who is actually keen to keep this and work on it. I can't see the deleted page, but it seems G11 was overstated, the G12/WP:CLOP claim is debatable (as to underlying parent text), and contra Robert, it seems accidental creation in the wrong userspace is more likely than WP:FAKEARTICLE. All in all, while not ready for mainspace, as a misplaced userspace draft or sandbox, this isn't clear-cut enough for a speedy. However, I'd only suggest using up the community's scarce attention on discussing it further if someone actually wants it kept. So if the page creator or some other recent editor of the page, or someone who sees it here, is active and wants to rescue this, let's have a deletion discussion and hopefully let them improve it and address the concerns. If challenging the speedy, or its restoration, is just well-intentioned process wonkery but anyone with an interest in it is a long-gone drive-by editor, let's save ourselves the effort and let the deletion stand. Martinp (talk) 02:41, 14 January 2026 (UTC)
|
|---|
| The following is an archived debate of the deletion review of the page above. Please do not modify it. |
My friend and legendary game designer had his whole page deleted. A 10 year old Wikipedia page just recently because the editor decided that a game he was briefly involved with had something to do with Web3 and I guess this person is anti web 3. His career spans 40 years of industry changing moments. Can we restore this oage please, it seems out of character for Wikipedia editors to delete someone’s non-promotional biography page because of technology, especially since the game in question wasnt on the chain when he worked on it. He’s not my client, he’s a good guy who saw his whole 40 yr career get deleted overnight. Imagine how that must feel to older game developers who are being forced out for having grey hair. The editors comments are really elitest and agist to say the least. Please protect our video game history and restore William Volk’s wikipedia page. Buzzspinner (talk) 03:06, 9 January 2026 (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. |
I am requesting review of the speedy deletion under CSD G11. The criterion was misapplied. The draft was a biographical article supported by multiple independent, reliable secondary sources, including coverage in The New York Times and multiple ABC News segments, as well as additional independent business and industry publications. The article was written in an encyclopedic tone and contained no calls to action, pricing, client lists, or promotional language. Even if tone concerns existed, they would be appropriate for Articles for Creation feedback or copyediting, not speedy deletion, as substantial encyclopedic content would remain after cleanup. I respectfully request undeletion and return of the draft to the AfC process for normal review. Flea15 (talk) 16:15, 7 January 2026 (UTC)
|
| The above is an archive of the deletion review of the page listed in the heading. Please do not modify it. |
- File:9928Olongapo City Barangays Landmarks 01 e.jpg (talk||history|logs|links|watch) (restore)
I created and uploaded File:9928Olongapo City Barangays Landmarks 01 e.jpg. Administrator IronGargoyle copied it and uploaded it as File:9928Olongapo City Barangays Landmarks 01.jpg. Then they deleted the file I'd uploaded as a copy. On their talk page they explained that they did this for "to maintain continuity with the original file name". This is for context. — Ирука13 10:14, 6 January 2026 (UTC)
- What is the action you want DRV to take here, and why? Stifle (talk) 10:24, 6 January 2026 (UTC)
Endorse and speedy closedue to nominator's failure to respond to a reasonable query. Stifle (talk) 09:12, 8 January 2026 (UTC)- Do what OwenX said below. Stifle (talk) 12:29, 8 January 2026 (UTC)
- Endorse and speedy close. No substantive reason given for this vexatious nomination. Deletion was both in the letter and spirit of CSD F1. IronGargoyle (talk) 20:21, 6 January 2026 (UTC)
- Comment and suggestion, if I may answer Stifle on behalf of the appellant. I agree with IronGargoyle that blurring a portion of the image doesn't entitle the uploader to any kind of attribution. Anyone may copy it, re-upload it as their own, and delete the original. I don't know why IronGargoyle chose to do that instead of simply moving the file to the correct name, but in doing so, he effectively erased any record of the appellant's contribution, which is all the appellant is asking for. Whether copyright laws require attribution or not, we all expect some form of recognition for our work here, even if it's just a line in a page history dump. Personally, the appellant lost any sympathy I may have had for them with their rude, Karenistic
Restore my file immediately
demand. But for the sake of expediency, I think this DRV can be speedy closed to everyone's satisfaction by adding a dummy edit to the file's history, with an edit summary denoting the appellant as the file originator. Not because they deserve it, but because it's the correct, minimally disruptive way to resolve this nonsense amicably. Owen× ☎ 11:58, 8 January 2026 (UTC)- Thank you for the explanation. That all sounds good to me. Stifle (talk) 12:29, 8 January 2026 (UTC)
- I have no problem with that solution. I thought the file name was important in case Philippine freedom of panorama law changed. A more permissive change would affect the history and reimportation of this file to Commons (which might be important to import a blurred version, depending on the context of the revised law). It simply didn't occur to me to move it. I have moved a tiny handful of files in the last several years and uploaded thousands. I have no problem with Iruka13 getting credit and I have said as much on my talk page. It was a helpful edit. I question whether that is what this is about though. Iruka13 has a long history of wikilawyering confrontation and is indefinitely blocked from three projects. This request seems more about winning an argument as opposed to actually improving anything on Wikipedia or gaining credit. Indeed, if Iruka13 cared so much about credit for a creative solution, why was there no notation citing Iruka13 for the blurring edit in the revised file description at File:9928Olongapo City Barangays Landmarks 01 e.jpg?— Preceding unsigned comment added by IronGargoyle (talk • contribs) 23:12, 8 January 2026 (UTC)
- If I understand you correctly -
Anyone may copy it, re-upload it as their own, and delete the original.
- I can re-upload "my" file again and place the F1-template on the IronGargoyle's file, right? — Ирука13 08:52, 9 January 2026 (UTC)
- Thank you for the explanation. That all sounds good to me. Stifle (talk) 12:29, 8 January 2026 (UTC)
- There was a clear purpose to maintaining the original file name, which I have explained. The only purpose to doing what you propose would be disrupting Wikipedia to prove a point. IronGargoyle (talk) 13:53, 9 January 2026 (UTC)
- Overturn. Creating a copy yourself to then apply F1 is clearly aberrant, not in the spirit of speedy deletion, and should not be condoned. The complaint is completely appropriate. Separately, I dispute the idea that there is something wrong with the name of this file. Adding the "e" means edit, the name of the deleted file is fine, and there is no reason to "maintain continuity with the original file name" on Commons. Overturn this wrong speedy deletion and delete IronGargoyle's duplicate.—Alalch E. 16:44, 8 January 2026 (UTC)
- Please see my comment above about the importance of maintaining the file name in case this ever needs to be reimported to Commons. Calling this aberrant is hyperbolic and only feeds into the confrontational mindset of this nomination. Quite honestly the file in question should have been uploaded over the original file as a file revision and then the original file revision deleted, but I lost track of the FFD over the holidays and forgot to suggest that in the FFD. When I went back to check on the discussion, the original FFD had already been closed. IronGargoyle (talk) 23:24, 8 January 2026 (UTC)
- Overturn per Alalch E. * Pppery * it has begun... 22:06, 8 January 2026 (UTC)
- Comment: I think a lot of people need a nice cup of tea and a sit down. There's a lot of overreaction going on. Stifle (talk) 10:19, 9 January 2026 (UTC)
- Overturn. Speedy deletion shouldn't be used when there's a feasible alternative to deletion, and in this case moving the file would have been just that. Extraordinary Writ (talk) 01:18, 10 January 2026 (UTC)
File:Chūzumō title screen.jpg (closed)
|
|---|
| The following is an archived debate of the deletion review of the page above. Please do not modify it. |
File was tagged because it had the wrong template on it. I corrected the template and left a note on the talk page, but apparently the admin who deleted didn't review that or ask me about it. ···日本穣 · 投稿 · Talk to Nihonjoe · Join WP Japan! 19:18, 5 January 2026 (UTC)
|
| The above is an archive of the deletion review of the page listed in the heading. Please do not modify it. |
Advanced Bionics (closed)
|
|---|
| The following is an archived debate of the deletion review of the page above. Please do not modify it. |
To create a redirect for the Advanced Bionics page to resolve to the page for Sonova, as mentioned in the deletion discussion. Kerri9494 (talk) 18:21, 5 January 2026 (UTC) |
| The above is an archive of the deletion review of the page listed in the heading. Please do not modify it. |
Angela Busheska (closed)
|
|---|
| The following is an archived debate of the deletion review of the page above. Please do not modify it. |
This article was deleted in May 2023 following an AfD that concluded the subject (then an undergraduate) did not meet notability guidelines. Since that deletion, the subject has achieved significant new recognition that satisfies WP:GNG and WP:ANYBIO. Key new developments include:
Furthermore, there are substantial, independent secondary sources that did not exist during the 2023 discussion. Find some of them linked below: [1], [2], [3], [4], [5], [6], [7], [8], [9], [10], [11], [12], [13], [14], [15], [16], [17], [18], [19], [20], [21], [22], [23], [24], [25], [26], [27], [28], [29], [30], [31], [32], [33], [34], [35] I am requesting that the deletion be overturned to allow for recreation or restoration based on this new evidence. ~2025-42766-79 (talk) 00:03, 5 January 2026 (UTC)
|
| The above is an archive of the deletion review of the page listed in the heading. Please do not modify it. |
File:Coat of arms of Canada.svg (closed)
| The following is an archived debate of the deletion review of the page above. Please do not modify it. |
|
What we have is the deletion of a contentious file (for over 20 years we have been debating this) that happened over the holidays involving just 2 random editors in 6 days. This is despite previous talks that were properly advertised (1 and 2) invovling many more editors. Closer should have relized that a wider talk then just 2 new editors should have taken place. What we have here is a fast deletion that was not announced anywhere (even on the page(s) invloved) that overrides the consensus of dozens and dozens of other editors from the past 20 years. Should at the very least been relisted and advertised somewhere over what most will see as a sneaky deletion attempt by someone involved with arms debates in many places.Moxy🍁 15:36, 3 January 2026 (UTC)
|
| The above is an archive of the deletion review of the page listed in the heading. Please do not modify it. |
Module:Bar box (closed)
|
|---|
| The following is an archived debate of the deletion review of the page above. Please do not modify it. |
I closed this as keep and WP:XFDC was unable to remove the tag from the module page, so I looked at it myself and realized after closing it that it was not tagged it seems. The consensus appears to be keep, but I am unsure if I should reopen to discuss further with a proper tag at Module:Bar box/doc or if the close is fine. Casablanca 🪨(T) 03:10, 3 January 2026 (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. |
I would like to request the AfD relist or some form of discussion. My source assessment was called “false,” even though it was based only on Wikipedia:Reliable sources/Perennial sources. I believe it is unfair and dismissive to say so without justification. The discussion had very little participation, with only a small number of editors commenting, and this limited participation appears to have been treated as consensus, contrary to WP:ROUGHCONSENSUS. I do not see any indication that the full set of over 20 sources in the article was reviewed. All my valid questions raised during the AfD were not addressed. The subject meets WP:GNG and WP:SIGCOV through sustained, non trivial coverage in multiple reliable, independent secondary sources. Some objections focused on interview based coverage, but under WP:SIGCOV and WP:RS, interviews published by independent outlets remain independent when there is editorial oversight, narrative framing, and analysis. Independence is determined by authorship and editorial control, not by the presence of quotations from the subject. The coverage goes beyond routine announcements and discusses the subject’s background, career, and leadership role over time. The close does not show that these factors were weighed, and a redirect outcome appears inconsistent with how similar notable founders are handled when GNG is met. This request asks for a review of the close itself, including how consensus was determined and how the sourcing was evaluated, rather than a reargument of the article’s merits. I am not sure if I am making the request correctly. Apologies if there is a broken template somewhere. WestwoodHights573 (talk) 20:40, 1 January 2026 (UTC)
I am not talking about some made-up rules in my head WP:FINANCIALTIMES
Robert McClenon (talk) 04:36, 2 January 2026 (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. |
|
This is an old AfD I just stumbled upon (from 2012), and it seems very improperly closed. I count 6 keep votes, 4 merge, and the nomination which seems to default to delete. This was closed as merge with no rationale, which seems incorrect. This should be recreted, with no prejudice to another AfD, although frankly whas I see in the last version seems, IMHO, sufficient to estabilish notability anwyay (but anyway, here we are debating whether it was closed properly, not the article itself). PS. I found Wikipedia:Deletion_review/Log/2012_July_16#Skeptoid, which seems to suggest that a merge occurred during the process, so the closure was likely fine (just affirming what happened); what likely was improper was the (as far as I can tell) undiscussed bold merger that happened during the AfD, done by a now-blocked editor (who in edit summaries claimed to have seen consensus at it in said AfD, which IMHO obviousy wasn't the case - but that's not the closer's fault). I intend to reverse the merger in the near future, restoring the article (no prejduice if someone wants to take it to AfD in the future again). I guess we can speedy close this DRV, apologies for wasting time. --Piotr Konieczny aka Prokonsul Piotrus| reply here 02:32, 1 January 2026 (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. |
Discussion was not in favor of deleting the article because of notability, deleted due to lack of further discussion, sufficient sources exist to demonstrate notability Update6 (talk) 23:18, 31 December 2025 (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. |
This is part of a series of templates, and not having it is detrimental to WP:CITEVAR and CS1-related maintenance. See a similar rationale at Wikipedia:Templates_for_discussion/Log/2016_October_1#Template:OSTI. This should be speedily undeleted, but alas, bureaucracy is too important to overlook apparently. Headbomb {t · c · p · b} 02:21, 31 December 2025 (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. |
I don't believe the discussion should have been closed this early. The MfD itself was only open for 2 hours, nowhere near the typical 7 days that should be allotted, nor was it in WP:SNOW territory, even if consensus was almost unanimous at the time it was closed. Tenshi! (Talk page) 13:31, 31 December 2025 (UTC)
|
| The above is an archive of the deletion review of the page listed in the heading. Please do not modify it. |
- Template:List with serial comma (talk||history|logs|links|watch) (XfD|restore)
I was not a participant in this TfD, but I came across it later in a follow-up discussion, and after reading it, I came to the conclusion that a persuasive case for deletion was never made and that the template would likely have been kept if subject to broader discussion. In particular, the deletion side made three arguments:
- That the template's functionality was covered by {{enum}}. Grufo refuted that point in this comment, showing that {{enum}} cannot actually properly handle serial commas, although some later !voters may have missed it. (He explained it in more detail here; in short, it's because using {{enum}}'s parameter
|and=, andto add a serial comma would cause it to erroneously outputA, and Bin an enumerated list with only two items.) - That the template is unused. This is a weak argument because, per WP:TFDREASONS #3, a template must also have
no likelihood of being used
, and that was never demonstrated/the use case here is perfectly plausible. - General opposition to serial comma use. This is a fine personal preference to have, but is not an argument for deleting the template. Given MOS:VAR, an article that uses an enumerated list template might well have an established style of using serial commas, in which case an option to do so in the template would be needed.
I take no issue with the judgement of the closer, Izno (who suggested coming here), in evaluating the consensus at the TfD at the time. But given the limited participation in that discussion and the issues I highlighted above, I believe the template should be restored and kept. Cheers, Sdkb talk 03:19, 18 December 2025 (UTC)
- Allow restoration per above as nominator. Sdkb talk 03:29, 18 December 2025 (UTC)
- Allow restoration per Sdkb. --Grufo (talk) 13:54, 18 December 2025 (UTC)
Relist to provide the additional discussion that the appellant is requesting. Robert McClenon (talk) 02:54, 19 December 2025 (UTC)
- Since there was incomplete pinging of users here, in that I mean, that the only person pinged was the only person that wanted to keep this template, I will ping all participants of the TfD as well. @User:Zackmann08 @GhostInTheMachine @Pppery @Alalch E.. Gonnym (talk) 19:01, 19 December 2025 (UTC)
- Keep deleted per TfD and RfD. Even if this was the most important template on our site (which is not even remotely the case), at this stage, I cannot assume good faith in its existence. It was deleted, then the template restored to create a redirect (instead of creating a redirect), then sent to RfD in the hopes of getting it restored, then trying to get it restored in an unrelated template talk page, then trying to backdoor restore it at Izno's talk page, then sent here without pinging the people that would be against its restoration but pinging the only one in favor of it being restored. At some point you have to WP:DROPTHESTICK. Gonnym (talk) 19:05, 19 December 2025 (UTC)
“I cannot assume good faith in its existence”
: How about we try a different narration, and maybe even introduce the idea that at this stage there cannot be good faith in opposing the template, at least not from you? The template was created because there are no ways to create a list with serial comma on English Wikipedia (unless you want to do it by hand). Then it was deleted arguing that {{Enum}} would allow serial commas. After several users have realized that it was actually not the case, someone invited to explore the possibility of supporting serial commas as an option of {{Enum}}. Although I believed that having things like{{Enum|A|B|C|serial=yes}}would never be ideal, I thought it was an acceptable compromise and so I implemented it, I also solved a current bug, and I opened a discussion about the new implementation. But then you opposed even the {{Enum}} option on the ground that you don't like Module:Params. You had already manifested the wish to orphan that module only for the sake of doing it; how about we introduce the idea that at this stage there cannot be good faith in your opposition (because your actual goal is that of orphaning Module:Params, as you have said it yourself)? --Grufo (talk) 19:53, 19 December 2025 (UTC)- Gonnym and Grufo, this is not the appropriate venue to discuss behavioral issues around the dispute you have with each other. Please stick to discussion of whether or not having {{List with serial comma}} restored would benefit the encyclopedia, as that is what the closer will be looking to evaluate the consensus around. Sdkb talk 20:18, 19 December 2025 (UTC)
- Hi Sdkb. It is fine by me. --Grufo (talk) 20:24, 19 December 2025 (UTC)
- Gonnym and Grufo, this is not the appropriate venue to discuss behavioral issues around the dispute you have with each other. Please stick to discussion of whether or not having {{List with serial comma}} restored would benefit the encyclopedia, as that is what the closer will be looking to evaluate the consensus around. Sdkb talk 20:18, 19 December 2025 (UTC)
- Keep deleted we've been through this. This is not a venue to rehash the same arguments. WP:DROPTHESTICK and move on. I appreciate the ping by Gonnym and am also troubled by the fact that only person pinged was the one who supported keeping the template to begin with. That is essentially WP:CANVASSING. Zackmann (Talk to me/What I been doing) 00:17, 20 December 2025 (UTC)
- Question about the statement that the Oxford comma is not supported by {{enum}}. It appears from the documentation that and = ", and" will do that. Can someone explain how the and = option of {{enum}} is not sufficient? I may change my vote based on the answer. Robert McClenon (talk) 01:37, 20 December 2025 (UTC)
- @Robert McClenon: Imagine you have a template called
{{Foobar}}, and this template contains the following code:{{Enum|{{{one|}}}|{{{two|}}}|{{{three|}}}|and=, and }}. When you write{{Foobar|one=apples|two=oranges}}you get “apples, and oranges”, and it will be unnecessarily hard to remove that comma. It is actually not so rare for templates to call {{Enum}} in this way (but without the|and=parameter)—see for instance {{Underused external link template}}; these templates would have no easy way to use a serial comma if they wanted to. --Grufo (talk) 03:32, 20 December 2025 (UTC)- Okay. I understand that you are saying that the problem with the {{enum}} template and the and=", and" parameter is that it introduces an Oxford comma between two elements.
- So it seems that the reason for this request either to restore the deleted template or reopen the deletion discussion is that the template was deleted based on an incorrect assumption that {{enum}} would provide the same result. Robert McClenon (talk) 04:51, 20 December 2025 (UTC)
- Exactly. But that is not all. In that discussion only two editors argued that this template would allegedly be redundant to {{Enum}} (although one of the two switched between multiple arguments). One editor actually argued that serial commas are not needed in general (but that would go against MOS:VAR), and the last editor only wrote
“Unused template. Theoretically useful, so perhaps recreate when it might be deemed to be practically useful”
. --Grufo (talk) 05:23, 20 December 2025 (UTC)
- Exactly. But that is not all. In that discussion only two editors argued that this template would allegedly be redundant to {{Enum}} (although one of the two switched between multiple arguments). One editor actually argued that serial commas are not needed in general (but that would go against MOS:VAR), and the last editor only wrote
- @Robert McClenon: Imagine you have a template called
- Question Ignoring TFDREASON#3 for a second, do we have a documented case where the enum template's lack of support for Oxford comma broke an edit, caused a display/style issue, or caused some other technical problem? Jumpytoo Talk 07:50, 20 December 2025 (UTC)
- @Jumpytoo, there are plenty of other templates that use enumerated lists within them. There are also plenty of articles that have an established style of using an Oxford comma. Any article that uses such a template and also has an established style of using an Oxford comma will be unable to maintain that style (an issue per MOS:VAR) without functionality to add an option to use an Oxford comma. It is difficult to run a query to fetch the list of such articles given that we have no {{Use Oxford comma}} tags on articles the way we do e.g. {{Use British English}} tags (perhaps we should). Sdkb talk 18:48, 20 December 2025 (UTC)
- I see, looking at the below discussion as well, I will support allowing recreation, but recommending finding a usage for the template first before doing so Jumpytoo Talk 08:07, 23 December 2025 (UTC)
- @Jumpytoo, there are plenty of other templates that use enumerated lists within them. There are also plenty of articles that have an established style of using an Oxford comma. Any article that uses such a template and also has an established style of using an Oxford comma will be unable to maintain that style (an issue per MOS:VAR) without functionality to add an option to use an Oxford comma. It is difficult to run a query to fetch the list of such articles given that we have no {{Use Oxford comma}} tags on articles the way we do e.g. {{Use British English}} tags (perhaps we should). Sdkb talk 18:48, 20 December 2025 (UTC)
- Endorse. I was aware of everything discussed above when I !voted and I still !voted delete. The same is true for other participants, I'd say. A template being unused is not a weak reason to delete. Recreate and immediately use it; this will overcome the reason why the page was deleted.—Alalch E.
- @Alalch E.: Correct me if I am wrong, but the template can be recreated only if it is deleted on the ground that it is unused, but not if it is deleted on the ground that it is redundant. That fact that you say it is not redundant (I agree btw) and can be recreated if used might meet the opposition of others who voted delete for other reasons. --Grufo (talk) 11:06, 20 December 2025 (UTC)
- If you were to recreate the template and reasonably immediately implement it, any admin who would G4-delete would be making a mistake. That mistake would be correctable in a DRV, for example. This DRV is not useful, as there's no mistake to correct. —Alalch E. 11:25, 20 December 2025 (UTC)
- Alright. Then it seems pretty easy. Although some might hate the serial comma, it can easily become mandatory in English to avoid ambiguity:
- I saw my two brothers, Robert and Karl.
- (i.e. I saw two persons, whose names are Robert and Karl, and they are my brothers)
- I saw my two brothers, Robert, and Karl.
- (i.e. I saw four persons)
- I saw my two brothers, Robert and Karl.
- --Grufo (talk) 18:33, 20 December 2025 (UTC)
- Which article is that from? —Alalch E. 09:51, 21 December 2025 (UTC)
- Oh that was just the first example that came to my mind. Asking about ambiguous examples from articles is a bit unfair, because if editors identified possible ambiguities while they were writing they also found the solutions already, either by not using {{Enum}} or by using different words. So the research you are implicitly asking will necessarily suffer from cherry-picking (and I know you know that already). However, by looking at how {{Enum}} is most often used in articles (#1, #2)—see for instance Tyrol Schistose Alps—it is not hard to come up with made-up (yet possible) ambiguous examples:
{{enum|Croatia|Slovenia|Bosnia and Herzegovina|North Tyrol|South Tyrol}}- ↳ Croatia, Slovenia, Bosnia and Herzegovina, North Tyrol and South Tyrol
- Without serial comma I have no idea how many people will undestand that North Tyrol and South Tyrol are two different regions that belong to two different countries (Austria and Italy). Moreover, consider that the example above belongs to those cases in which the serial comma is either mandatory or almost mandatory; yet some people might want to use the serial comma just because they like it, and that is also fine. --Grufo (talk) 14:47, 21 December 2025 (UTC)
- Perhaps people click on the link? The Banner talk 17:23, 21 December 2025 (UTC)
- I agree with you, Grufo, that this is a valid real example of where a serial comma is needed and is missing due to how the enum template works by default. In the TfD it was noted that the enum template can produce a serial comma. Participants did not believe that another template is needed, functionally similar to enum (irrespective of similarity or dissimilarity of implementation). I'd take this to the talk page of enum and try to enact a consensus to change the template code to one that retains no serial comma by default but has more robust support for the serial comma than enum, so that it's resistant to the "A, and B" (B being the second and only other member of the list) scenario. I'm going to keep my !vote as endorse here, and I continue to oppose two templates. —Alalch E. 21:29, 21 December 2025 (UTC)
- @Alalch E.: Thank you for your reply. As you might have noticed, I emphasized in my previous message that we were talking about usage in articles, because there people will always find a way to write things, in a way or another. But as I mentioned earlier, the real problem (unsolvable via {{Enum}}) happens in templates. In my opinion {{Enum}} should not support the
|comma=and|and=parameters at all (we already have {{Separated entries}} if you want to specify those), and instead all these courtesy templates like {{Enum}}, {{Hlist}}, etc. should do only one thing and do it well. We even have {{Comma separated entries}}. That is also why I still prefer a separate template for serial commas. That said, supporting the serial comma via {{Enum}} will be better than not supporting it (even though not ideal if you ask me). --Grufo (talk) 21:44, 21 December 2025 (UTC)
- @Alalch E.: Thank you for your reply. As you might have noticed, I emphasized in my previous message that we were talking about usage in articles, because there people will always find a way to write things, in a way or another. But as I mentioned earlier, the real problem (unsolvable via {{Enum}}) happens in templates. In my opinion {{Enum}} should not support the
- Oh that was just the first example that came to my mind. Asking about ambiguous examples from articles is a bit unfair, because if editors identified possible ambiguities while they were writing they also found the solutions already, either by not using {{Enum}} or by using different words. So the research you are implicitly asking will necessarily suffer from cherry-picking (and I know you know that already). However, by looking at how {{Enum}} is most often used in articles (#1, #2)—see for instance Tyrol Schistose Alps—it is not hard to come up with made-up (yet possible) ambiguous examples:
- Which article is that from? —Alalch E. 09:51, 21 December 2025 (UTC)
- Alright. Then it seems pretty easy. Although some might hate the serial comma, it can easily become mandatory in English to avoid ambiguity:
- If you were to recreate the template and reasonably immediately implement it, any admin who would G4-delete would be making a mistake. That mistake would be correctable in a DRV, for example. This DRV is not useful, as there's no mistake to correct. —Alalch E. 11:25, 20 December 2025 (UTC)
- @Alalch E.: Correct me if I am wrong, but the template can be recreated only if it is deleted on the ground that it is unused, but not if it is deleted on the ground that it is redundant. That fact that you say it is not redundant (I agree btw) and can be recreated if used might meet the opposition of others who voted delete for other reasons. --Grufo (talk) 11:06, 20 December 2025 (UTC)
- Keep deleted Superfluous and at present unused. What issue does it solve? The Banner talk 15:35, 20 December 2025 (UTC)
- Keep deleted no error by the closer was identified here. This entire discussion is mere TfD-round-2-ing. * Pppery * it has begun... 16:18, 20 December 2025 (UTC)
- Comment - I have struck my Relist. We have had the discussion that the appellant requested, and it has not been persuasive. Robert McClenon (talk) 17:40, 20 December 2025 (UTC)
- Overturn This was a poorly attended discussion which did not address any of the points brought up here, and if they had been brought up this would have been kept in the absence of additional consensus. I'd change this to no consensus and allow an immediate renomination. SportingFlyer T·C 23:06, 20 December 2025 (UTC)
- 5 people at a TFD is not a poorly attended discussion. It's probably not even so for any other deletion forum at this time either. Izno (talk) 06:20, 30 December 2025 (UTC)
- Allow restoration, unless {{Enum}} can be fixed. I see nothing wrong with how the TfD was closed. But the bar for keeping a template is even lower than that for keeping a redirect. Grufo's explanation more than suffices to pass that low bar. I understand why those dealing with such issues are passionate about them, but this just isn't worth the time we've spent on it here. Zackmann08's advice to WP:DROPTHESTICK applies to everyone. Owen× ☎ 10:55, 21 December 2025 (UTC)
- There's two options here:
- Recreate the template; maybe simplify the code if that's the problem since I hear from many other of TfDs (that resulted in delete) against Grufo that a major concern was overcomplication.
- This could probably be a wrapper template around Enum.
- Fix Enum so it can say both "A and B" and "A, B, and C".
- I do not think simply modifying existing behavior with the "and" parameter is an option. The key here is "existing behavior"—I'm fairly sure there should be existing templates that rely on the "and" parameter being applied consistently as long as the number of list items is more than one. (Changing the output just for the case of "and=, " is IMO too bespoke and counterintuitive.)
- We could make a different parameter that would have this behavior, but besides being a little bespoke, I believe adding on new code for this specific use case far less common than Enum's 11,140 is overkill and unwieldy to maintain, with such a low-use feature affecting such a high-risk range.
- Recreate the template; maybe simplify the code if that's the problem since I hear from many other of TfDs (that resulted in delete) against Grufo that a major concern was overcomplication.
- Hence, I lean weak restore per Owenx. Aaron Liu (talk) 03:12, 23 December 2025 (UTC)
- Endorse. Appellant inappropriately attempts to reargue their case on the merits. This board is for procedural errors, which the appeal does not allege. Sandstein 15:20, 26 December 2025 (UTC)
- @Sandstein: That might not be completely correct. It is true that the closer found the (little) consensus required by WP:TFDCI to close the discussion, so there was no mistake from them. But a procedural error lied in the fact that consensus was based on a false premise concerning {{Enum}}'s support for serial comma, which might even have held back others from commenting in the template's favor. The very reason a redirect was kept afterwards and Sdkb initially did not want to remove it was the belief that {{Enum}} supported the serial comma. --Grufo (talk) 19:35, 26 December 2025 (UTC)
- That's not an error by the closer, which is what we are here to review. That deletion discussion participants make mistakes is routine and not grounds for deletion review. I suggest seeking consensus to amend the Enum template to support serial commas instead. If that succeeds, all should be happy, and if that fails, it confirms that this deletion reflects community consensus. Sandstein 21:48, 26 December 2025 (UTC)
- Errors by the closer might not be the only thing worth the attention of this venue. That would be point #1 of Wikipedia:Deletion review § Purpose, whereas point #3 mentions “substantial procedural errors in the deletion discussion …” (emphasis is mine). Whether we like the template or not, that discussion was pretty terrible. That might also explain why the topic was felt still pending afterwards (#1, #2). --Grufo (talk) 23:16, 26 December 2025 (UTC)
- The problem with your quote is that the only errors alleged here are substantive and not procedural. * Pppery * it has begun... 01:47, 27 December 2025 (UTC)
- How should we draw that line though? Imagine an extreme scenario: imagine someone nominated for deletion a template similar to {{See also}} and the majority argued that it is redundant to {{Strong}} (of course it isn't, they are very different templates); as such it gets deleted; would these not be considered procedural errors in the deletion discussion? Where should that discussion be challenged? --Grufo (talk) 19:57, 1 January 2026 (UTC)
- "Procedural" has a specific meaning on Wikipedia and in most places with debate rules. A procedural problem is a mistake in how a decision or process is carried out (rules, steps, timing, notice, authority, documentation, etc.). What you mentioned is a substantive debate, a disagreement about what the decision or outcome should be (facts, judegments, or merits of the issue). Aaron Liu (talk) 19:58, 2 January 2026 (UTC)
- How should we draw that line though? Imagine an extreme scenario: imagine someone nominated for deletion a template similar to {{See also}} and the majority argued that it is redundant to {{Strong}} (of course it isn't, they are very different templates); as such it gets deleted; would these not be considered procedural errors in the deletion discussion? Where should that discussion be challenged? --Grufo (talk) 19:57, 1 January 2026 (UTC)
- The problem with your quote is that the only errors alleged here are substantive and not procedural. * Pppery * it has begun... 01:47, 27 December 2025 (UTC)
- Errors by the closer might not be the only thing worth the attention of this venue. That would be point #1 of Wikipedia:Deletion review § Purpose, whereas point #3 mentions “substantial procedural errors in the deletion discussion …” (emphasis is mine). Whether we like the template or not, that discussion was pretty terrible. That might also explain why the topic was felt still pending afterwards (#1, #2). --Grufo (talk) 23:16, 26 December 2025 (UTC)
- That's not an error by the closer, which is what we are here to review. That deletion discussion participants make mistakes is routine and not grounds for deletion review. I suggest seeking consensus to amend the Enum template to support serial commas instead. If that succeeds, all should be happy, and if that fails, it confirms that this deletion reflects community consensus. Sandstein 21:48, 26 December 2025 (UTC)
- Where should this be argued? Aaron Liu (talk) 19:58, 26 December 2025 (UTC)
- In an appropriate template or project talk page, as suggested above. Sandstein 21:50, 26 December 2025 (UTC)
- I've mentioned why I believe amending Enum to be a bad idea (maintenance). On which project talk page should the recreation of the template be argued? I unfortunately can't find one. Aaron Liu (talk) 22:54, 26 December 2025 (UTC)
- As I've commented somewhere else, Module:Separated entries, which is the base module for this and other templates, should just have a
|serial=yesoption added to it. It's that simple. Gonnym (talk) 06:56, 27 December 2025 (UTC)- Though modules don't have the PEIS concerns adding text to templates does, what I've said about risk applies twohundredfold more to SeparatedEntries's 2,647,141 transclusions. Aaron Liu (talk) 17:02, 29 December 2025 (UTC)
- Because this TFD concluded that Wikipedians don't want a separate template for this purpose, the only remaining options are to amend an existing template or not support lists with serial commas, which is an entirely unimportant issue to begin with. Sandstein 19:25, 28 December 2025 (UTC)
- Actually, if you look into what this TFD concluded, two editors said serial commas are already supported by {{Enum}}, one said that serial commas are bad, one said to recreate this template as soon as it is needed. Nobody in this TFD said we have to amend an existing template. --Grufo (talk) 00:55, 29 December 2025 (UTC)
- Please stop addressing me. Gonnym (talk) 11:15, 29 December 2025 (UTC)
- Nobody is talking with you, nor addressing you, nor mentioning you. --Grufo (talk) 12:50, 29 December 2025 (UTC)
- Please stop addressing me. Gonnym (talk) 11:15, 29 December 2025 (UTC)
- Is there a reason recreation, as many here support, should not be an option when they believe we want a template for this purpose? Aaron Liu (talk) 17:05, 29 December 2025 (UTC)
- Actually, if you look into what this TFD concluded, two editors said serial commas are already supported by {{Enum}}, one said that serial commas are bad, one said to recreate this template as soon as it is needed. Nobody in this TFD said we have to amend an existing template. --Grufo (talk) 00:55, 29 December 2025 (UTC)
- As I've commented somewhere else, Module:Separated entries, which is the base module for this and other templates, should just have a
- I've mentioned why I believe amending Enum to be a bad idea (maintenance). On which project talk page should the recreation of the template be argued? I unfortunately can't find one. Aaron Liu (talk) 22:54, 26 December 2025 (UTC)
- In an appropriate template or project talk page, as suggested above. Sandstein 21:50, 26 December 2025 (UTC)
- I completely disagree with the premise of this endorse. DRV is a forum for challenging deletions, not for challenging actions of administrators. This was a lightly attended discussion, and if the rationale for deleting can be overcome, this is absolutely the correct forum. SportingFlyer T·C 03:49, 30 December 2025 (UTC)
- Not so. We regularly dismiss DRV nominations that treat DRV as a second round of XfD. Our instructions provide: "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." Sandstein 08:55, 30 December 2025 (UTC)
- I agree we regularly dismiss DRV nominations that treat DRV as a second round of XfD. I do not think this petition falls into that category at all. SportingFlyer T·C 01:06, 31 December 2025 (UTC)
- I fully concur with SportingFlyer here. This is basically the platonic ideal of why WP:NOTBURO is a policy. It boils down to this: If the template benefits Wikipedia, it should exist, and if not, it should not. It's one thing for those opposed to the template to make arguments that it should not exist. But it's another thing, when those arguments start being refuted, for them to turn to wikilawyering to try to create a situation in which there is no possible reasonable venue to contest and overturn the decision. A pedantically narrow interpretation of DR's remit does nothing but bolster that disingenuous tactic. Sdkb talk 04:32, 3 January 2026 (UTC)
- It hasn't been refuted. The current template handles serial comma, and has before this template was created with the
|and=parameter. A better solution was proposed and you didn't want it. The community was against the template you wanted. And finally, this was never the venue to relitigate everything again. Gonnym (talk) 13:53, 3 January 2026 (UTC)The current template handles serial comma
@Gonnym, then show us how. I previously asked you to do so, and you responded dismissively with an example that ignored theA, and Bissue that had been pointed out to you already (and that I stated again in opening this review). When called out on that, you disengaged. If there is a method that you have for some reason been keeping in your pocket, now is the time to lay it out. If not, and you are just repeating your claim while ignoring theA, and Bissue with it, then be advised that a deliberate failure to get the point is behavior could lead to sanctions against you. Sdkb talk 19:36, 3 January 2026 (UTC)- A good exercise would be that of pasting below a version of {{Underused external link template}} that uses the serial comma (possibly trying to stick to {{Enum}}, without Byzantine solutions, and guaranteeing the correct output for every empty parameter). --Grufo (talk) 20:23, 3 January 2026 (UTC)
- For the umpteenth time (and it would actually be helpful if you literally take a look at the code instead of ignoring anything you don't like). Here is how you can do
A, and B:{{enum|A|B|and=, and{{space}}}}-> A, and B
- This is without any changes to the current template. As I said previously, and previously and previously, changing the base module can make this cleaner, but you didn't want that.
- I'm pretty done with this discussion, but I just wanted to make sure to any closing admin that the "refuted" claim is factually incorrect, yet keeps being repeated, even when shown otherwise. Gonnym (talk) 10:09, 5 January 2026 (UTC)
“For the umpteenth time”
: Indeed you keep repeating yourself again and again, without listening to what is being replied to you n + 1 times, often with fresh new arguments on top of the previous ones. Please, try to pay attention this time:- Everywhere but in templates, when we want to have
A, B and Cwe don't write{{Comma separated entries|A|B|C|conjunction= and }}; instead we write{{Enum|A|B|C}}. Using an even stronger argument (the previous code does not change depending on the number of items, but the following does), when we want to have a list with the serial comma it makes sense that we write{{List with serial comma|A|B|C}}instead of having to distinguish manually{{Enum|A|B|C|and=, and#32;}}from{{Enum|A|B}} - In templates, as I mentioned earlier, there is simply no solution. I invite you to address this comment—
and it would actually be helpful if you literally take a look at the code instead of ignoring anything you don't like
.
- Everywhere but in templates, when we want to have
“As I said previously, and previously and previously, changing the base module can make this cleaner, but you didn't want that”
: I am not aware of Sdkb refusing anything of what you are claiming (can you please reference this?). What I saw happening instead is that you refused your own favorite idea of amending {{Enum}} to support serial commas, even though multiple users are telling you that amending {{Enum}} to support serial commas is not the best thing to do. --Grufo (talk) 12:53, 5 January 2026 (UTC)
- It hasn't been refuted. The current template handles serial comma, and has before this template was created with the
- Not so. We regularly dismiss DRV nominations that treat DRV as a second round of XfD. Our instructions provide: "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." Sandstein 08:55, 30 December 2025 (UTC)
- @Sandstein: That might not be completely correct. It is true that the closer found the (little) consensus required by WP:TFDCI to close the discussion, so there was no mistake from them. But a procedural error lied in the fact that consensus was based on a false premise concerning {{Enum}}'s support for serial comma, which might even have held back others from commenting in the template's favor. The very reason a redirect was kept afterwards and Sdkb initially did not want to remove it was the belief that {{Enum}} supported the serial comma. --Grufo (talk) 19:35, 26 December 2025 (UTC)
- Endorse. The TfD was properly run and closed correctly. - SmokeyJoe (talk) 00:23, 3 January 2026 (UTC)
- About The Banner's block: Recently, The Banner, one of the participants in this discussion (#1, #2), was indefinitely blocked (for related reasons). --Grufo (talk) 03:14, 14 January 2026 (UTC)
Draft:Sajid Akram (terrorist) (closed)
|
|---|
| The following is an archived debate of the deletion review of the page above. Please do not modify it. |
This page was deleted under G5 as a contentious-topic creation. I believe this deletion was in error because the article is about a specific criminal event in Australia (the 2025 Bondi Beach shooting) and is not related to the Arab–Israeli conflict. All content is supported by reliable sources such as Sky News, SMH, CNN, and The Guardian. The article maintains a neutral tone, follows Wikipedia BLP and crime article policies, and does not promote political viewpoints. I respectfully request that the page be reviewed for restoration. Cobaltx2015 (talk) 12:21, 18 December 2025 (UTC)
|
| The above is an archive of the deletion review of the page listed in the heading. Please do not modify it. |