Wikipedia:Deletion review

Skip to:

Active discussions
Recent discussions
Archive
(purge cache)

WP:DRVWP:DRV

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

Shortcut

WP:DRVPURPOSEWP:DRVPURPOSE

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 significant new information has come to light since a deletion that would justify recreating the deleted page;
if a page has been wrongly deleted with no way to tell what exactly was deleted; or
if there were substantial procedural errors in the deletion discussion or speedy deletion.

Deletion review should not be used:

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);
(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.)
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 repeat arguments already made in the deletion discussion;
to argue technicalities (such as a deletion discussion being closed ten minutes early);
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);
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.)
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

Shortcut

WP:DELREVDWP:DELREVD

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.	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 July 6}}</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 July 6}}</noinclude>` If the deletion discussion's subpage name is different from the deletion review's section header, then use `<noinclude>{{Delrevxfd\|date=2025 July 6\|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".

Active discussions

6 July 2025

1 July 2025

Functional Decision Theory

Summary: the article was recreated and speedy deleted without meeting speedy deletion criteria.

In more details: The article was originally deleted at Wikipedia:Articles_for_deletion/Functional_Decision_Theory in January, with the main reason being insufficient proof of notability. A few weeks ago, I came up on a recent news article talking about "Functional Decision Theory" from Wired, so I searched for the concept on Wikipedia and realized the page was deleted. I created a new one from scratch, with additional sources to establish notability. It was immediately draftified by User:David Gerard as he claimed it is substantially similar to the previous one. I brought up that it doesn't meet the criteria for speedy deletion as per WP:G4, since it "applies to sufficiently identical copies, having any title, of a page deleted via its most recent deletion discussion. It excludes pages that are not substantially identical to the deleted version, and pages to which the reason for the deletion no longer applies". He responded that "has the same bad referencing: the sources about the topic are primary sources, and the reliable sources aren't actually about FDT". While I disagree (some of the new non-primary sources are about FDT), I added 4 new non-primary references talking about FDT, including a published book, and moved the article back to mainspace. He then speedy deleted it again. I contest this speedy deletion, as I think the article is now substantially different to at least merit a new AfD debate AND some of the added sources were published after the last AfD was closed. 7804j (talk) 17:52, 1 July 2025 (UTC)[reply]

Temp Undelete to evaluate G4, please. Jclemens (talk) 19:07, 1 July 2025 (UTC)[reply]
- Now available at Draft:Functional_Decision_Theory - David Gerard (talk) 19:30, 1 July 2025 (UTC)[reply]
  - That's not how we do temp undeletes for DRV. If you're not able to do it properly, please ask another administrator to do it. Jclemens (talk) 05:07, 2 July 2025 (UTC)[reply]
Comment from deleting admin - if any admin feels this isn't a deletion recreation and wants to recreate it, that's fine by me - David Gerard (talk) 19:30, 1 July 2025 (UTC)[reply]
Endorse - there are certainly OR issues with the draft that DG has undeleted above. Many of the references don't mention this concept, and the author has SYNTHed them together in my opinion. That said, as the WIRED article (briefly) states, this is a thing. In fact if one searches for Timeless Decision Making which the WIRED article says is another term, there are more peer reviewed sources. However the issue is that these sources are almost all simple mentions which point back to an unreviewed paper and/or one on arXiv. So there's not really much to go on to write a page without writing an OR essay. Without getting into the weeds as to understanding what this is about it seems like peer reviewed papers are mentioning this as a FRINGE idea and not bothering to explain or critique it. If all of that is stripped away this only really leaves the WIRED and a self-published paper, which isn't enough to write a WP page in my opinion. If there ever is an extensive peer reviewed paper on topic, this could change. JMWt (talk) 19:53, 1 July 2025 (UTC)[reply]
Leave SALTed to force going through AfC. I may be mistaken, but it looks like the four sources added are either primary or include only perfunctory mentions of the topic. But whether or not this qualified for G4, the appellant's behaviour comes across as sealioning - civilized and soft-spoken, while effectively ignoring David Gerard's sound advice, and engaging in what I can only describe as an edit-war against an admin who was trying to enforce the consensus reached at the AfD. I see no value in wasting the community's time with another AfD to review those four added sources. An AfC reviewer can do the job, and decide whether the draft is ready for mainspace. Owen× ☎ 20:21, 1 July 2025 (UTC)[reply]
Technically, Overturn G4. The version that was G4ed is not sufficiently identical to the version deleted at AFD. I find the newer version to be of considerably lower quality than the older one, and I believe it would stand no chance at AFD due to the WP:OR and WP:SYNTH concerns brought up by JMWt. To that effect leave in draft space to allow for any good-faith improvement. Frank Anchor 20:31, 1 July 2025 (UTC)[reply]

Also unsalt to allow an improved draft to be submitted back to article space (with or without AFC approval), at that point any editor can move the discussion back to AFD. Frank Anchor 16:48, 3 July 2025 (UTC)[reply]

Article aside, is this specific type of situation becoming a problem? It's probably not a G4, it's just different enough and most importantly has new sources, but I'd be surprised as socks if it has any chance of actually being kept at AfD. (This isn't relevant in this instance, but I think if an article is deleted at AfD, and is re-created with exactly the same sources but entirely different prose, G4 can still apply.) SportingFlyer T·C 20:40, 1 July 2025 (UTC)[reply]
Leave SALTed per the rationale of OwenX. Repeatedly creating an article based on unreliable and/or superficial sources is a waste of the community's time. Stepwise Continuous Dysfunction (talk) 22:20, 1 July 2025 (UTC)[reply]
Comment or Question - If I understand correctly, what is visible as the draft is the submitted new article, and what is visible in the history as of 21 January 2025 is the article that was nominated for deletion and deleted. I don't see a G4 in the log. What I see is that the new draft (which may have been deleted) is less complete than the deleted article, but not a proper subset of it. If I understand correctly what is what, then the G4, if there was a G4, should be overturned, because the draft is not a repost, but will itself be deleted. Are my understandings correct? Robert McClenon (talk) 22:24, 1 July 2025 (UTC)[reply]
Restore and consider desysop of David Gerard for multiple issues:
1. Draftifying the re-created article as was done by David Gerard on June 26th violates multiple parts of WP:DRAFTNO. Further, the edit summary stated that AfC was required, which appears to be incorrect as a statement of policy unless there was an admission or substantiated assertion that 7804j had a conflict of interest with respect to the topic. I have been unable to locate any such assertion.
2. Self-designating and deleting the re-mainspaced new version of an article under CSD G4 after being the original AfD nominator is an WP:INVOLVED violation as the prior interaction was not purely in an administrative role. This is further codified in WP:DGFA#Deciding whether to delete clause 3.
3. Applying G4 inappropriately, as the new version was not substantially identical. Note that David Gerard had actual notice that G4 was not applicable per the edit summary, but even had that edit summary not been made, it was incumbent upon the deleting admin to verify that a new version was substantially identical.
4. Unilaterally create protecting an article when it had not deleted but repeatedly recreated; the single re-creation appears to have been appropriate and in good faith. Again, this is a separate WP:INVOLVED violation.

This is high-handed administrator abuse of process, regardless of the merits of the article. If I'm reading the datestamps correctly, the unilateral G4-like deletion was less than two hours after the article was moved back into mainspace. The discussion at User talk:David Gerard#Draftification of Functional Decision Theory shows that David Gerard misstated policy and acted on the misstated policy even after correctly challenged on it. The concurrent contribution history shows no attempt to bring in another administrator to act as an intermediary or sanity check on this process. David Gerard has been around enough and held administrator tools long enough to know better. Jclemens (talk) 05:42, 2 July 2025 (UTC)[reply]

- WP:ADRC is available if you wish to propose a desysop; may I suggest that discussion here be confined to the article in question. Stifle (talk) 08:01, 2 July 2025 (UTC)[reply]
I believe OwenX has summarised the situation very well and I concur with his recommendations as the best way forward, notwithstanding that it is slightly at odds with policy. Stifle (talk) 08:03, 2 July 2025 (UTC)[reply]
Overturn speedy. First, let's lower the temperature here a bit. I see no reason to disbelieve that everyone here is trying to improve the encyclopedia.

Summary: The article was first created by a SPE, Luiguit, in 2022, in Draft, then moved to main. Luiguit has disappeared. DG found the article in January 2025, PRODded it, after PROD was removed took it to AFD as nonnotable. AFD was not particularly well attended, but concluded delete. A few days ago, 7804j, a long-term and non-single purpose editor, rewrote the article from scratch in main space, with different wording, many of the same and some additional sources. It was tagged G4 and that tag was declined (as not sufficiently similar) by A.B. Minutes later, DG moved it to Draft as "recreation with minor changes - needs to go through AFC at a minimum". 7804j added a bit more, then moved to main space, in edit summary explaining why an AFD discussion (x2) might be appropriate but SD or Draftification was not. Nevertheless, DG deleted as "repeated recreation of AFDed article" and protected. 7804j filed this DRV, where in response to a 3rd party request for a temp undelete, DG undeleted into Draft. Bottom line is 7804j wants their version in mainspace, subject to AFD x2 if someone wants, and DG feels it should stay deleted or at least out of main space.

Way forward: I think we need to i) overturn this G4 as the recreation is not sufficiently similar; ii) recommend to 7804j that notability still feels very suspect (if I read correctly, we essentially have just a few preprints, a few medium and one lesswrong article, and maybe some passing mentions) and that it would be a lot safer to incubate further in Draft space. iii) nevertheless (and contra Owen's suggestion above), if 7804j (an established and not inexperienced user) wants his rewrite to take its chances in mainspace with AFD, unsalt and let that happen; iv) trout DG (not desysop!) for crossing the line from finishing up mopping the same mess to having tunnel vision (i.e. ending up involved not by crossing some bright line but by being too emotionally involved in enforcing his view) and being overeager with speedy deletion. v) Optionally, it may make sense to have a policy discussion to make G4 broader, referring not just to article text but also its sourcing, if this type of issue is more frequent. Martinp (talk) 18:09, 2 July 2025 (UTC)[reply]

Whilst this isn't wrong, it feels like this is a long bypass to end up in the same place. The text might be different but the sources are necessarily much the same other than a recent mention in a WIRED article. Do we really have to restore to mainspace only to quickly AfD and delete it? It wouldn't survive AfD, it likely wouldn't survive AfC. If there's some argument that this meets the GNG, I'm not seeing it. What is gained from restoring it to mainspace? JMWt (talk) 19:06, 2 July 2025 (UTC)[reply]

From the above discussions and opinions, it seems clear that the article will require at least some changes to be more likely to survive AfD. So if this speedy deletion is overturned, I would like to incubate further in draftspace.

At this point, I am no longer requesting that the article be returned to mainspace. I would be satisfied if we could return it to Draft (overturning the incorrect speedy deletion) and UNSALT the page so that I can move it back to mainspace later, once I feel it is ready.

I think this page is a bit of an unusual case, because while there isn't much "non-primary peer-reviewed sources with in depth coverage", the topic itself is mentioned by hundreds of papers, widely discussed by hundreds of people in various forums in the space of Effective Altruism, AI Safety, etc. and even described in detail by media (Wired article). The challenge is this is an "academic" topic published outside of academia, by non-academics, so much of the sources are themselves published outside of academia. This is the reason why I was more keen than usual to trigger a proper AfD review: I felt these arguments were not brought up the first time.

But again, given the consensus above, I no longer plan to immediately bring it back to mainspace. 7804j (talk) 19:45, 2 July 2025 (UTC)[reply]

We’ve all wasted too much time on this wikilawyering already. It’s not up to you to “decide” when it’s ready for mainspace, it can only move to mainspace when there are sufficient reliable sources to meet the GNG. That’s it. JMWt (talk) 20:18, 2 July 2025 (UTC)[reply]

No, that's not how it works. Anyone can put an article into mainspace. If it qualifies for CSD, it may get deleted that way. If not, it may get sent to AfD. But yes, it is up to each individual editor what to put into mainspace. The community has processes if we disagree with them putting it into mainspace. Hobit (talk) 21:49, 2 July 2025 (UTC)[reply]

Ok that's fair. I guess I was thinking of the current SALT situation and that there needs to be good refs to show a reason to unSALT, but fair enough I was wrong. JMWt (talk) 08:23, 3 July 2025 (UTC)[reply]

The current SALT situation was created by the same involved administrator whose actions led us to this point, unfortunately. Jclemens (talk) 22:06, 3 July 2025 (UTC)[reply]

Excellent. We are making progress. Appellant no longer wishes to overturn to having article as-is in mainspace, but wants to improve it in draftspace. Can we reach consensus to draftify, i.e. leave the "temporary deletion" DG made into draftspace in place, not re-delete at the end of this DRV? By the way, this history now includes the original 2022 article as well, which I think has useful material to scavenge if indeed this topic is notable (which I am still not convinced of, but no matter.)

That leaves the question of SALTing. I think it was inappropriate and should be undone. An established, previously uninvolved editor rewriting from scratch an article that was deleted for insufficient sourcing, with what they feel is better sourcing, does not warrant salting. Even if ~~original deleting admin~~the admin who originally nominated for deletion feels the sourcing is still not up to par. Especially if there is no pattern of tendentious recreation. And that admin's tagging of the recreation for SD as a G4 was rejected by an uninvolved admin in the meanwhile. It feels like the deleting admin was in gatekeeper mode, not janitor mode. Absent a broader pattern, anyone editing the draft should feel free to use AFC or move a new and improved article into mainspace -- and take the risk of AFD or policy-based SD nuking their efforts if their judgment is off. Martinp (talk) 22:55, 2 July 2025 (UTC)[reply]

overturn As to the merits of the article--we don't speedy things that don't meet a CSD rule. This doesn't. So we overturn. In addition, DG appears to have handled things poorly. We want people to make new articles. The editor in question has created many such articles. We want to keep such people happy and pleased to continue to contribute. We shouldn't WP:BITE editors, be they newcomers or regulars. I believe that DG made an editorial decision to move the article to a draft. Then incorrectly speedied it (both a CSD issue and an INVOLVED issue). And then moved it back to draft after restoring it (a clear violation of WP:DRAFTIFY which specifically calls such a thing edit warring). David is a very experienced admin--I think it would be ideal if he would acknowledge the problematic behavior. I mean that's a fair number of WP:XXX things to be getting wrong--some quite serious. Hobit (talk) 21:48, 2 July 2025 (UTC)[reply]

Overturn Speedy and send to AfD. SmokeyJoe (talk) 22:23, 2 July 2025 (UTC)[reply]

AfD is the best forum for evaluating new sources.

AfD is the best forum for making a rule that the topic in future must go through AfC. SmokeyJoe (talk) 22:41, 2 July 2025 (UTC)[reply]

I suppose the issue for me is whether we are going to have a continual cycle of AfD discussions about the. The nom says

The challenge is this is an "academic" topic published outside of academia, by non-academics, so much of the sources are themselves published outside of academia. This is the reason why I was more keen than usual to trigger a proper AfD review: I felt these arguments were not brought up the first time.

So it is clear that they understand that there will always be a charge that the sources are not reliable including the "various forums" where the subject is discussed. We all understand that sources beyond academia can be considered to show notability against the inclusion criteria, but equally fora, self-published and arXiv papers are unlikely to be enough. We don't need multiple AfD discussions to establish this. JMWt (talk) 08:35, 3 July 2025 (UTC)[reply]

That’s a !vote that belongs at AfD, not DRV.

This DRV should have been speedy closed with the deleting admin sending it to AfD. SmokeyJoe (talk) 08:58, 3 July 2025 (UTC)[reply]

Overturn speedy and nominate at AfD per Martin and SmokeyJoe. DG deserves a trout for misapplying the speedy deletion policy; the article creator deserves a slightly smaller trout for re-creating an article deleted at AfD that seems unlikely to survive another AfD, but I suppose that trout should be suspended until the new AfD is closed. Toadspike [Talk] 10:30, 3 July 2025 (UTC)[reply]
Close the speedy was incorrect and should be overturned, however I am no longer requesting that the article be returned to mainspace. I would be satisfied if we could return it to Draft so close this and unsalt so the editor can improve and restore. At that point, any established editor would be welcome to file an AfD if they see merit. Star Mississippi 13:29, 3 July 2025 (UTC)[reply]
I second this. You could probably add a caveat that David Gerard would be clearly WP:INVOLVED in a dispute if they take further action with the article. SportingFlyer T·C 21:06, 3 July 2025 (UTC)[reply]

I third (not a new voice, I commented above). I note the author's switch to wanting a return to Draft, not mainspace, is currently their last edit on en.wiki. As is DG's if any admin feels this isn't a deletion recreation and wants to recreate it, that's fine by me, above. Star Mississippi is an admin. And since DG moved the article to Draft in the first place (2x), presumably they don't object to it being there. So I *think* all involved parties would be OK with this resolution. As to whether this is enough for a speedy-ish close, or if should keep open a full 7 days (there are early participants in the discussion here who favoured endorsing and salting), that's above my pay grade. Martinp (talk) 14:55, 4 July 2025 (UTC)[reply]

Spinny (company) (closed)

Spinny (company) – Speedy endorse as disruptive. I have not SALTed as there isn't consensus for that and some good reasons why it might not be effective. Star Mississippi 13:33, 3 July 2025 (UTC)[reply]

The following is an archived debate of the deletion review of the page above. Please do not modify it.

This page had many good articles but still it got removed. Why it was deleted? Just because before it was not notable? That don’t seem fair. Please don’t do like this. I saw in AfD many top level sources were there but still some editos didn’t cared about them. This is not right. How can so many good articles about the company not matter? Please check properly and do fair thing. 2409:40D0:BE:E670:C57E:19E6:F357:9A87 (talk) 07:52, 1 July 2025 (UTC) -->[reply]

Endorse, sockpuppet limit breached. Plus, while it wasn't a G11 - there were about four neutral sentences hidden between marketing drivel like "Spinny operates a digital-first model integrated with physical retail touchpoints, offering services across several major Indian cities." and "It also offers additional policies such as a five-day return period and a certification program named 'Spinny Assured.'" - it was pretty close. —Cryptic 08:30, 1 July 2025 (UTC)[reply]
Endorse. After discarding socks, COI SPAs, and those clearly canvassed off-wiki, we're left with one legitimate, P&G-based argument to keep. The bogus, shameless source analysis table is particularly offensive. Title-gaming to evade a SALT is never a good way to recreate an article. Owen× ☎ 08:43, 1 July 2025 (UTC)[reply]
Endorse clear consensus to delete once the socks, SPAs, etc. are discarded. Frank Anchor 14:03, 1 July 2025 (UTC)[reply]
Endorse - The closer used good judgment in ignoring the Keep votes from start-up accounts and IP addresses that were probably canvassed. As per OxenX, any article that is created with a gamed title is suspect from the start, and this was no exception. The original title is not salted in draft space, and a good-faith editor can recreate a draft for review rather than trying to evade the salting. Robert McClenon (talk) 14:33, 1 July 2025 (UTC)[reply]
Salt the disambiguated title in article space. Robert McClenon (talk) 14:33, 1 July 2025 (UTC)[reply]
Endorse although a bit reluctantly. I thought User:Afstromen was making a sincere effort to engage with the GNG and shouldn't be lumped in with IP and possible COI editors. Their last div in the discussion wasn't really refuted. I accept that there are issues with Indian media and PR puffery, but at the same time we now have a situation where it is almost impossible to have any Indian business meeting the standard for inclusion. I don't know how this can be resolved. JMWt (talk) 15:03, 1 July 2025 (UTC)[reply]
Yes, it was a somewhat reluctant close on my part, for similar reasons. Speaking of Afstromen's participation, @OwenX, I count two good ones, Afstromen and @HighKing, but they're outnumbered more than 2:1 on deletes. In particular, HighKing's endorsement gave me pause, since he is usually quite strict on interpretations of WP:ORGTRIV. I suspect that the issues raised by @Cryptic and @Robert McClenon had some influence on the discussion and that an actually good article on the topic would have fared better at AfD. But I think it would have been a real stretch to close the discussion as it happened as "no consensus". -- asilvering (talk) 16:25, 1 July 2025 (UTC)[reply]

Hi @JMWt, I fully respect the admin’s decision on this AfD and have no objections. I also want to clarify that I have no connection with the IPs involved. Creating the article about Salt was my first and last mistake. When I created the article, I left a note on the talk page explaining my action, but I understand the admin who had protected the title wasn’t satisfied and I accept that. It was a careless mistake, and I’ve already apologized to the admin. I genuinely wasn’t aware of the correct procedure in such cases. I assure you this won’t happen again, and I sincerely apologize for my actions. I also want to mention that I was only sharing my thoughts in the AfD, as I believed there were a few good-quality sources supporting notability. That said, I respect the final decision and don’t wish to pursue this further. Afstromen (talk) 17:29, 1 July 2025 (UTC)[reply]
I think you should continue as you are, friend. I don't see any issues with your edits. And certainly nothing serious to apologise for. JMWt (talk) 17:37, 1 July 2025 (UTC)[reply]

I have been watching articles and drafts with gamed titles in various forums for more than a decade, and I an always deeply wary of any such article, and this is one. I would have endorsed the deletion even if the votes by good-faith and good-standing editors were roughly even. I think that any editor who advances such an article is likely to be either a paid editor, a sockpuppet, a canvassed pop-up editor, an ultra, or an inexperienced editor who does not understand about the frequency of the gaming of titles. I see that User:Afstromen was an inexperienced editor, and that they see that they made a good-faith mistake. Robert McClenon (talk) 21:52, 1 July 2025 (UTC)[reply]

If Afstromen or any other good-faith editor thinks that the company is notable, they should submit a draft with the original title, Draft:Spinny for review, and the reviewer can decide whether to request that the title be desalted. Robert McClenon (talk) 21:52, 1 July 2025 (UTC)[reply]

Speedy endorse and salt the disambiguated title (involved). An IP address bringing an appeal of a discussion riven with sockpuppetry is not something we need to deal with in good faith. (I would still have endorsed, but not speedily, had HighKing or Afstromen brought the appeal. I generally trust HighKing's assessment but the one source they proffered that I could see was not SIGCOV in my view.) Dclemens1971 (talk) 19:57, 1 July 2025 (UTC)[reply]
Yes, an unregistered editor bringing an appeal of a discussion where there was sockpuppetry is not worth dealing with. Robert McClenon (talk) 21:52, 1 July 2025 (UTC)[reply]
- Salting isn't likely to be effective if people are already adding unnecessary disambiguators, and I'd normally be wary of blacklisting a term this simple. Surprisingly few hit for it, though - besides this, its previous title Spinny, a version in draft, and an image, there's only ever been Spinny & SpikeSpinny & Spike, Spinny chairSpinny chair, Spinny ship, and a bunch of unrelated user- and usertalk pages. Nothing like what's at Spinney. Maybe create a protected redirect there and blacklist; wikt:spinny gives it as an alternative spelling, and redirects usually don't need the sort of associated pages like talk archives and GA reviews and AFDs that normal articles do. —Cryptic 20:26, 1 July 2025 (UTC)[reply]
Endorse and while Cryptic makes a good point, perhaps a salt is a good idea. SportingFlyer T·C 20:42, 1 July 2025 (UTC)[reply]
Endorse as the closer seems to have "read the room" properly: the arguments that were not chaff add up to a consensus for deletion. Stepwise Continuous Dysfunction (talk) 22:53, 1 July 2025 (UTC)[reply]
Endorse accurate decision. If this turns up again, I would expect a WP:DEEPER listing and/or a title-blacklisting. Stifle (talk) 08:05, 2 July 2025 (UTC)[reply]

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

30 June 2025

Vittorio Mancini (wrestler)

Closed by a non admin as redirect, discussed here. I believe the consensus here is delete not redirect. LibStar (talk) 00:47, 30 June 2025 (UTC)[reply]

Pinging AfD participants: @Let'srun, @UtherSRG , @Gjb0zWxOb , @Kingsif LibStar (talk) 00:52, 30 June 2025 (UTC)[reply]

Revert and delete - consensus was to delete. Closer should get a trout. I haven't checked, but if this is has happened before by them, upgrade the trout to a haddock and pban them from AFD. - UtherSRG (talk) 00:59, 30 June 2025 (UTC)[reply]
This is not the only controversial close I have seen from this non-admin. While I believe they are working in good faith, I would encourage them to step back from closing close AfD's. Let'srun (talk) 14:36, 30 June 2025 (UTC)[reply]
Endorse. Redirect is a valid ATD for Olympians and this outcome has occurred probably over a thousand times by this point. I don't see why this is necessary, or why it shouldn't be redirected. And suggesting the closer deserves a pban for this is utterly nonsensical. BeanieFan11 (talk) 01:13, 30 June 2025 (UTC)[reply]
Revert and delete (involved): Consensus was clear to delete the article based on a lack of significant coverage. Let'srun (talk) 01:30, 30 June 2025 (UTC)[reply]
I would also be okay with a revert and relist. Let'srun (talk) 14:35, 30 June 2025 (UTC)[reply]
Endorseish. No reason for not redirecting was articulated, so the outcome is correct. But a relist or an admin closure would both have been preferable to a borderline NAC. Jclemens (talk) 03:16, 30 June 2025 (UTC)[reply]
Weak Endorse as per Jclemens, because this would have been a valid close by an admin. However, as a non-admin close, the optics are wrong. It looks like the non-admin is trying to make a close that they can make. A Relist, which they also can make, would have been more prudent. Robert McClenon (talk) 03:41, 30 June 2025 (UTC)[reply]
Comment from closer: Unless someone can explain why the redirect is invalid, I see no policy-based reason to delete and then create a valid redirect. That is needlessly hiding page history and obstructing editors looking to re-create the article should the subject become notable in future. I would have closed this the same way even if I had the ability to delete, and I believe any responsible admin should have done the same. Toadspike [Talk] 06:38, 30 June 2025 (UTC)[reply]
Since you are not an admin, you should not be making any controversial closures (especially since you couldn't close it as delete). There were 4 votes to delete while only one to redirect, so closing as redirect is effectively a supervote. The redirect vote came after the 4 delete votes, thus either a relist (to ask the other delete voters regarding how they felt about the proposed AtD) or a delete closure by an admin should have been the only considerations here. Let'srun (talk) 14:34, 30 June 2025 (UTC)[reply]
Not so. There's no consensus for delete there, just a nose-counting plurality. That's not how a rough consensus works. Jclemens (talk) 01:40, 1 July 2025 (UTC)[reply]
Endorse Where a valid alternative to deletion is presented, it doesn't need to have the highest !vote count - any closer can determine that. Kingsif (talk) 08:31, 30 June 2025 (UTC)[reply]
Endorse. Technically, this was a BADNAC, since deletion was a possible outcome, therefore it should have been left to an admin to close. That said, with a valid ATD proposed, those calling to delete must provide a compelling reason to erase the history, not merely outnumber the minority ATD !voter(s). I see no argument about the page history violating policy, nor any argument that would stand up at an RfD to remove this useful redirect. Toadspike shouldn't have closed this, but the close itself is correct. Owen× ☎ 09:40, 30 June 2025 (UTC)[reply]
Shouldn't it have been relisted at the very least to ask the four delete voters how they felt about the AtD, especially since the redirect vote came very late in the discussion? Especially since, as you noted, this was a bad NAC? Let'srun (talk) 14:50, 30 June 2025 (UTC)[reply]
Not necessarily, because consensus is not required to perform an ATD instead of deletion. If the four delete !voters strongly feel the ATD is inappropriate, then they are welcome to list the redirect at RFD. Frank Anchor 15:31, 30 June 2025 (UTC)[reply]

@Let'srun: fair point; a relist would have also been acceptable. Personally, I don't see any valid reason to erase the history behind the redirect, but if any of the AfD participants (all of whom were pinged here) can see such a reason, they (or anyone) are welcome to present their argument here, or as Frank Anchor said, start an RfD. I see no harm in keeping the history behind the redirect in place while we debate this. BADNAC or not, I see no reason to undo a close just to redo it by an admin. While I respect the process, the correct outcome takes precedence. Owen× ☎ 16:09, 30 June 2025 (UTC)[reply]
Sure, but that decision could have simply been made through a relist and (at least temporary) restoration of the article. It appears that the community wishes to endorse the close, and I respect that, but I hope that the closer understands WP:XFD#CON when closing discussions. Let'srun (talk) 03:02, 1 July 2025 (UTC)[reply]
Endorse per the above. Redirects are pretty much standard for Olympians at this point and no compelling reason for deletion of the history was presented. Eluchil404 (talk) 09:48, 30 June 2025 (UTC)[reply]
Endorse. No argument was made against redirecting and consensus is not required to use an WP:ATD as opposed to deletion. Frank Anchor 13:06, 30 June 2025 (UTC)[reply]
Endorse. WP:ATD is policy, and the AfD nominator was at fault, failing WP:BEFORE for not explaining why a redirect should not be done. —SmokeyJoe (talk) 14:31, 30 June 2025 (UTC)[reply]
Endorse probably best left to an admin, but absolutely the correct result. SportingFlyer T·C 15:11, 30 June 2025 (UTC)[reply]
Endorse The close should have been left to an admin, but WP:ATD is policy. As OwenX says above "I see no argument about the page history violating policy," so there is no need to delete the underlying history. --Enos733 (talk) 16:21, 30 June 2025 (UTC)[reply]
Endorse - not seeing the problem here. JMWt (talk) 20:15, 30 June 2025 (UTC)[reply]
Endorse unless anyone can elaborate on why they need the history revdeled. Alpha3031 (t • c) 06:48, 1 July 2025 (UTC)[reply]
Endorse No delete !vote discussed why a redirect was inappropriate. If there is some reason, bring it to RfD. Hobit (talk) 14:28, 1 July 2025 (UTC)[reply]
Endorse. I would have closed this as redirect, and I'm honestly pretty irritated to see people calling this a WP:BADNAC. Let non-admins do things they have the tools to do. -- asilvering (talk) 16:27, 1 July 2025 (UTC)[reply]

Comment. With regards to this close being a WP:BADNAC,I didn't call it one in my initial comment above and I don't think it is one under policy, but it is a close that I probably wouldn't make myself as a non-admin and wouldn't really encourage other non-admins to make. Partly, that's because of the (unfair) criticism that comes with making even clear calls against pure numbers at AfD or non-admins exercising even correct judgement when deletion is a possible (but clearly inferior) alternative close, but mostly it's because closing this kind of discussion as a non-admin is actually often counter productive. It's bound to be challenged and brought to DRV even though you were perfectly correct, so closing it actually creates more administrative backlog than leaving it open for a admin to evaluate would. It is a frustrating part of wiki culture, but it is definitely real and worth understanding. Eluchil404 (talk) 21:43, 1 July 2025 (UTC)[reply]

29 June 2025

Category:Wikipedians by medical condition – Non-admin closure overturned and XfD reopened both in my individual capacity as an admin per WP:BADNAC, and also per consensus in this discussion. Controversial closures, as this one clearly was, should be left to admins. Sandstein 07:35, 1 July 2025 (UTC)[reply]

The following is an archived debate of the deletion review of the page above. Please do not modify it.

This was closed as a clearly inappropriate supervote. The closure claims that the UCoC clause "People having a particular physical or mental disability may use particular terms to describe themselves" somehow preempts this discussion, however deleting categories in no way stops people from doing so, and the rest of the closer's lengthy argument is their own opinion that should have been in a !vote, not a closure. * Pppery * _{it has begun...} 21:09, 29 June 2025 (UTC)[reply]

Speedy overturn NAC supervote based on the UCoC is not OK. The people who're trusted to make such interpretations are the admin corps. Jclemens (talk) 21:37, 29 June 2025 (UTC)[reply]

As I just explained to Marcocapelle here - I used my good judgement as a human that can see non-uniform application of rules and that given the existing treatment of other such categories existing and somehow singling out Wikipedians with medical conditions/disability from not having one (and having read some of the explanations from users explaining why such categories can be relevant) is a clear mistreatment of a group of people. I cited the UCoC, because they conveniently even spelled it out. I don't believe the close is a supervote as I carefully considered the existing practice and therefore the nomination as it stood on the basis of singling out a particular characteristic group, rather than saying "we should delete all Wikipedians by X" falls in lack of Mutual Respect/discrimination territory (Also just to clarify, I don't think there was any malice on the nominators part, just a missed observation or accident in noticing it), so in the interest of the community, a procedural close looked entirely appropriate.

However as I explained in the longer response to @Trilletrollet when they asked about the CfD from last year, I think you will be very hard pressed in light of the user groups around religion, gender, ethnicity and co and the social norm of these having existed for a long time around this. To use maybe the most polarizing example - Religion was nominated for deletion in 2007 and the closer noted that, that category could have been deleted based on the arguments, it was still kept because there's a lot of people who feel strongly about their religion and voted because they don't like the idea of their category being deleted.

So my close was founded in the established social norm of these usercats of defining characteristics of Wikipedians existing with the history of that the standard for such characteristic groups are condoned, and such CfDs have typically been popularity contest, it can't be in the interest of the editing community to waste time on discussing any such sub-section of "Wikipedians by X" flavor of the day every couple days/weeks/months/years.

If you want to change the project-wide norm and standard that no such categories exist, that's a matter for a WP:CENT RfC. But when it's a nomination of a marginalized subgroup, whether because someone may not like it individually, or by oversight, and the rules are not uniform, then you're by definition in discrimination territory (intentional or not).

Given that I closed this, and still firmly believe, that the heart of this is one of mistreatment/"different treatment" of a group, I did so on those grounds procedurally. The history of these discussions have either been a popularity contest, or it needs to be a separate discussion - there is no "yeah we're fine deleting this group because we don't like it", but "that other one is fine because it has a large enough following to steamroll any rationale based points".

Due to that DRV is not the right venue of this and you are welcome to argue why singling out of this group is okay in your opinion to U4C if you believe that that is a good use of stewards time, rather than taking the opportunity to take a step back and realize that maybe the WP:USERCAT guidelines could indeed use an update to lay out the uniform application of established project-wide norms of such usercats and avoid the re-litigation of such repeated cases. Raladic (talk) 21:47, 29 June 2025 (UTC)[reply]

Speedy close and overturn. What on earth? That close in no way represents a consensus; this is a WP:BADNAC and an admin should undo it in their individual capacity. Dclemens1971 (talk) 02:28, 30 June 2025 (UTC)[reply]

Overturn procedural close and leave for an admin to close. The closer has made a plausible argument as a vote to Keep the categories. At the same time, an argument can also be made that the UCOC does not require keeping the category, only allowing users to self-identify, and I think that argument is stronger. So the closer's argument, while a valid vote, is a seriously incorrect procedural close. The closer says that DRV is not the right venue for this, but I don't see a suggestion as to what the proper venue is. It appears that the closer does have the right to appeal to the U4C, but only by arguing that the English Wikipedia is refusing to enforce the UCOC, and we are not refusing to enforce the UCOC, but interpreting it as not mandating the category and so not requiring the procedural close. Robert McClenon (talk) 04:18, 30 June 2025 (UTC)[reply]
Comment - The closer is probably right that the applicable guideline should be reviewed. That doesn't validate the closure or invalidate this DRV. Robert McClenon (talk) 04:18, 30 June 2025 (UTC)[reply]
Comment to User:Raladic - Thank you for filing the RFAR. I don't think that filing an appeal to the U4C will be a useful idea. Robert McClenon (talk) 04:18, 30 June 2025 (UTC)[reply]
Speedy overturn and relist – the closer's rationale is a completely inappropriate supervote. Whatever their opinions on the UCoC, they should be presented and discussed as a !vote, not used to speedily shut down a rational, policy-based discussion. Toadspike [Talk] 12:00, 30 June 2025 (UTC)[reply]
Endorse on principle I would be happy with getting rid of user categories completely, to be honest, but I actually agree with the closer here in the sense this is a rare instance in which the code of conduct applies and as such the discussion should either be reverted and advertised more widely, or moved to a different forum. CfDs are low participation discussion areas. SportingFlyer T·C 15:17, 30 June 2025 (UTC)[reply]
Overturn on the basis that the NAC makes no sense. It seems clear to me that there's a debate to be had regarding userpage badge choices and whether every user is aware that this means they'd be put in a searchable category. It may well be that users should should be able to self-identify in various ways under the UCoC. That doesn't mean that therefore the category should have to exist. JMWt (talk) 20:25, 30 June 2025 (UTC)[reply]
Eh, it's a poorly formed CfD ("What do you think?") with a number of related-but-unrelated categories, and the UCoC argument is a valid one that I would have missed. Honestly I would have closed as a no consensus trainwreck and let anyone immediately renominate specific categories. SportingFlyer T·C 21:16, 30 June 2025 (UTC)[reply]
By my reading, the closer is suggesting a larger discussion with many more categories. In contrast, you're suggesting smaller nominations of specific categories. (I'm not trying to sway your position, just to point out that, if the close is upheld, the next step would be unclear to me.) RevelationDirect (talk) 00:31, 1 July 2025 (UTC)[reply]
The next step as I suggested in the close and follow up comments, and made here would be that a discussion is held to address the points I raised. Some people (even some who voted overturn here) have suggested/agreed that maybe an outright deletion of all such user cats is one of the possible outcomes. Or the other alternative being that the community workshops an update to the current usercat guidelines that creates a framework for uniform (non-popularity contest) rules with regards to "Wikipedians by X" type usercats.

Since the point I raised with my procedural close has now been acknowledged/agreed by several other editors, I believe the reasonable next step is that CfD discussions on the "Wikipedian by X" are paused/injunct until the community either had time to vote (probably most appropriate in a RfC, given the possible project-wide impact) on which of the two options we should go, or maybe someone has another third or further suggestion to get away from the current state of affairs that has resulted in a shotgun approach and basically popularity vote on retention of such categories, which is not in the interest of the project (like I pointed out above with the Religion one as an example - the closer's hand was basically twisted, while other categories that may not have had such a big following get randomly nixed).

So, I believe my procedural close was correct as I effectively identified a gap in guideline and uniform enforcement thereof. So we should let the wider community now go from here and decide which path to take to fix the problem to update/clarify the guidelines to bring their current non-uniform treatment for such categories out of conflict with the UCoC, which are policy level, and thus, the policy takes precedent per WP:POLCON - As a temporary measure, if a guideline appears to conflict with a policy, editors may assume the policy takes precedence. - so for the time being, CfDs for such "Wikipedians by X" should be paused, the community address the issue, and then we go from there.

Would it not be for my procedural point and closure, I would also agree with SportingFlyer on the point of the CfD in question itself had a rather scatterball mix of categories in it, some of which may very well be deleted, but that would be incredibly difficult for a closer to discern if editors suggested "keep X, Y, Z, delete A, B, C" for any closer to come to any better close than a likely no-consensus WP:TRAINWRECK that even @Pppery mentioned on the actual CfD discussion, so arguably, someone may even procedurally just decided to close it preemptively on trainwreck grounds, invoking WP:COMMONSENSE, rather than wasting editors time for a week on a quite-likely foregone conclusion close. Raladic (talk) 01:52, 1 July 2025 (UTC)[reply]
My interpretation of that reply remains that you do not favor breaking down the existing nomination into separate discussions for each subcategory but correct me if I'm mistaken.
I reached on your talk page partially to better understand what changes to WP:USERCAT you were contemplating hoping that we could maybe write a draft to reword it away from the back and forth. I'm not sure if that would work because, in some places, it sounds like the the CFD nomination process itself is what's being objected to. But I'm willing to try, and the offer still stands. I'm always happy to collaborate here, there, or wherever.
But, since we don't currently have any affirmative proposals to discuss at an RFC, if the close is upheld the next step would be unclear to me. RevelationDirect (talk) 03:14, 1 July 2025 (UTC)[reply]
You’d be somewhat correct that I don’t think it is fruitful right this very moment to break down this CfD as I think the systemic question is more relevant right now. But thereafter, I’d say that yes breaking it down would be the right path (and I can totally see that quite several of the cats in the original proposal won’t see the light of day). So to clarify in case it wasn’t clear (getting thoughts out of my brain and across effectively is sometimes/often tricky as I’ve learned over the years and is still a work in progress, but that’s a story for a different time in the future) - I’m not objecting to CfD as a process itself in general or that any and all such categories should exist, but the current guidelines in particular to the “Wikipedians by X” type are too fuzzy as past discussions have shown and were subject to the wit of the moment).

And with regards to your comment on my user talk page, I’ll see if I can come up with a starting point in regards to that and get back on that when I find a moment. Raladic (talk) 04:15, 1 July 2025 (UTC)[reply]

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

Recent discussions

28 June 2025

Westlake, Washington

Westlake is a former incorporated settlement and now has a paragraph in the Moses Lake article. Most uses of the term still refer to the former town rather than the Seattle neighborhood. Sounder Bruce 04:44, 28 June 2025 (UTC)[reply]

Relist given the limited discussion, for you to make that argument. SportingFlyer T·C 09:13, 28 June 2025 (UTC)[reply]
[Closer's notes] The outcome was a Retarget. I closed on 27th, and mention was added at the redirect's previous target article on 28th. Appellant didn't discuss with me regarding the close. Jay 💬 09:44, 28 June 2025 (UTC)[reply]
- My apologies. I was directed here when I asked for some advice on how to undo the decision (as I did not have time to respond to the discussion due to an extremely busy week). Next time I will just contact the closer directly. Sounder Bruce 18:28, 28 June 2025 (UTC)[reply]
Relist. There was limited discussion and not a quorum to do anything. The nom statement that there is No mention in article [Moses Lake, Washington] has been addressed with the addition of sourced content. A relist would allow this content to be evaluated. Frank Anchor 11:47, 28 June 2025 (UTC)[reply]
No action. This could have been resolved with the appellant directly contacting the closing admin, who is responsive and receptive to such requests. While this isn't strictly required by policy, I see no reason to waste the community's time on something that could have been settled within minutes between the two of them. I doubt relisting would achieve a clearer consensus than what we have, but Jay is welcome to relist and administratively close this DRV as moot. Owen× ☎ 12:23, 28 June 2025 (UTC)[reply]
Relist I am convinced that a relist is appropriate in this situation. I don't think the close was wrong, but per deletion review point 3, new information has come to light, that should be evaluated by the community. --Enos733 (talk) 17:15, 28 June 2025 (UTC)[reply]
Comment - There is something wrong with the listing of the RFD log. When I view the RFD log for June 18, I see Westlake as the last entry in the Table of Contents, but I don't see it when I view the log. I do see it when I edit the source for the log, and it isn't obvious to me what has made it invisible, and I don't have time for a few hours to search for the misplaced commands and fix it. I think that the listing should be corrected regardless of the outcome of this DRV. Robert McClenon (talk) 18:21, 28 June 2025 (UTC)[reply]
- I don't think that the problem is with this RFD log, because I am also seeing MFD listings disappear. I will be inquiring at the Help Desk. Robert McClenon (talk) 15:57, 29 June 2025 (UTC)[reply]
Endorse as the correct outcome; the Westlake neighborhood in Seattle would be the PRIMARYTOPIC no matter how you slice it. Jclemens (talk) 21:17, 28 June 2025 (UTC)[reply]

26 June 2025

List of Dance Dance Revolution songs – Decision endorsed * Pppery * _{it has begun...} 04:17, 4 July 2025 (UTC)[reply]

The following is an archived debate of the deletion review of the page above. Please do not modify it.

Admin who closed the AFD doesn't reach back to users who have concerns about an AFD result, so hence why I'm using this route. I was under the impression that an AFD wasn't decided on "popular vote" or "opinion poll" or survey, rather than all sides all heard, and if one side (especially if the arguments seem like hit and run posts etc.) has incorrect arguments, due to the minority side having the correct arguments, then at best case, the minority site is correct, and then at worst case, the AFD needs to be relisted. etc. Article was deleted per AFD, but I totally disagree. Article falls under Wikipedia guidelines as a list article. Correct sources for the page have been added. Is part of a very popular Video Game/Music/Media franchise (Dance Dance Revolution), doesn't fall under WP:NOTDATABASE as it doesn't contain trivial information, rather music/songs/tracks (licensed or otherwise) are an integral part of DDR history. Article was nominated rather quickly after article was reworked and organized much better, with added sources. The consensus argument on deletion was mainly that it was an unencyclopedic database article, which is not true, and also featured drive by/hit and run votes on the AFD discussion.☼Phrasia☼ (talk) 23:39, 26 June 2025 (UTC)[reply]

Admin who closed the AFD doesn't reach back to users who have concerns about an AFD result Where did you give Liz a chance to explain the close to you? Per this note, you stated you were taking this directly to DRV. In any case, endorse as the consensus at the AFD was quite clear. -- Whpq (talk) 00:01, 27 June 2025 (UTC)[reply]

In that argument that I should have waited for the admin in question to contact me, you have a point, but I also have a point, by looking at the admins talk page history, and seeing handfuls of users who reached out to them in regards to an AFD result or resolution, with radio silence respectively. I mentioned this on the admin's talk page, that if it wasn't for their history of not reaching back to users over AFD concerns, I would have possibly talked it over with them first, but I didn't see a point, I humbly apologize. So supposing my situation wouldn't have been any different, and I messaged the admin with a gripe/concern over the AFD and heard nothing, we would be down this avenue anyways.☼Phrasia☼ (talk) 00:02, 27 June 2025 (UTC)[reply]

Endorse. While a late “keep” can sometimes trigger a relist so participants can engage with the rationale, there was already a robust consensus and the appellant’s argument was a greatest hits list of WP:ATA. Liz’s close was correct. Dclemens1971 (talk) 03:23, 27 June 2025 (UTC)[reply]

Endorse - Not entirely sure what the appellant is saying, but either a Delete or a Relist were valid exercises of judgment by the closer. Robert McClenon (talk) 03:40, 27 June 2025 (UTC)[reply]
Endorse. This falls into the "But no one came back to refute my argument!"-category of appeals. The appellant's main argument at the AfD was WP:OTHERSTUFFEXISTS, which means that there was a unanimous P&G-based consensus not to retain the page. Owen× ☎ 07:20, 27 June 2025 (UTC)[reply]
Endorse clear consensus for deletion. SportingFlyer T·C 09:52, 28 June 2025 (UTC)[reply]
I might have relisted it, but I can't really fault the close. I would certainly have relisted if Phrasia's comment came in right near the end, but it was up for a few days and no one felt a need to agree with it, so. -- asilvering (talk) 16:37, 1 July 2025 (UTC)[reply]

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

25 June 2025

List of music considered the worst – Procedurally and/or speedily closed. Consensus is that GogoLion is wasting our time with a request that is not within the scope of DRV and that appears to be AI-generated. I am warning GogoLion that repeated disruptive DRV requests like this one may result in sanctions. Sandstein 20:45, 25 June 2025 (UTC)[reply]

The following is an archived debate of the deletion review of the page above. Please do not modify it.

I am requesting a serious re-evaluation of "List of music considered the worst" in this Deletion Review, as the article continues to raise fundamental concerns that have not been properly addressed in the multiple prior AfDs. While editors have repeatedly pointed to the presence of reliable sources, that argument has continually overlooked the key issue: the article violates core Wikipedia content policies, specifically WP:NOR (No Original Research), WP:SYNTH, and WP:NPOV (Neutral Point of View).

Key policy concerns:

Synthesis and Original Research (WP:SYNTH, WP:NOR)

The article compiles negative opinions from individual reliable sources and presents them as if they form a cohesive, broadly agreed-upon classification of certain songs or albums as “the worst.” However, no source makes this comprehensive claim. The list is a synthesis of disparate critical takes, which produces a conclusion not explicitly made by any cited source. This is a textbook case of original research, violating Wikipedia's core content policy.

Minimal, Subjective Sourcing (WP:NPOV, WP:UNDUE)

While the sources used are mostly reliable, many entries rely on only one or two subjective reviews, often rooted in :personal taste or cultural context. This minimal sourcing does not support the wide-reaching claim implied by inclusion in a list of "the worst." Moreover, music criticism is inherently subjective and genre-sensitive. What may be negatively received in one context can be valued in another. The article gives undue weight to isolated critiques while ignoring broader audience reception, fanbases, or historical re-evaluations.

Lack of Defined Inclusion Criteria (WP:LISTN, WP:V)

The list does not adhere to any clearly defined or consistently applied criteria for what qualifies a work as one of "the worst." Some entries are based on critical reception, others on commercial failure or online memes. This arbitrary inclusion makes the list editorially driven rather than encyclopedic. Without explicit inclusion standards and consistent application, the article fails the basic standard expected of a list on Wikipedia.

Non-Neutral Framing and Presentation (WP:TONE, WP:TITLE)

The framing of the article, both in its title and its narrative lacks neutrality. Declaring works as “the worst” carries an implicit judgment that Wikipedia should not make. Even if retitled to something like “Music that received negative critical reception,” the article would still need to demonstrate balanced coverage and contextual depth, which it currently lacks.

Conclusion: This article has now gone through six AfDs, but none have adequately addressed these foundational policy issues. Repeated survival at AfD does not override persistent violations of Wikipedia's core content guidelines. The presence of a few reliable sources does not justify a synthesized, judgmental, and inconsistently sourced list. I respectfully urge deletion or, at minimum, a formal consensus to require a full rewrite in strict adherence to WP:NOR, WP:NPOV, and WP:LISTN standards. — Preceding unsigned comment added by GogoLion (talk • contribs) 14:55, 25 June 2025 (UTC)[reply]

Please read up on what WP:DRV is. It's not the place to continue a (years ago closed) deletion discussion or start a new one, its to discuss whether or not prior deletion discussions were closed correctly, which none of that appears to even begin to address. Sergecross73 msg me 15:19, 25 June 2025 (UTC)[reply]

Procedural close. The appellant is aware the article has survived six AfDs, but doesn't seem to dispute any specific one of them. Instead, they hope DRV will invoke a form of certiorari to somehow vacate the consensus reached in the AfDs. They are doing this instead of renominating for a seventh AfD as a form of forum-shopping. This is not what DRV is for. Like it or not, the community has spoken clearly and repeatedly about this type of list. Owen× ☎ 15:21, 25 June 2025 (UTC)[reply]
Procedural Close - This isn't an argument that there was anything wrong with the 2019 deletion discussion, but that the article should be deleted. The arguments made in this filing are a good case for another AFD, but this is not Articles for Deletion because it is Deletion Review.
- I don't see an earlier 5 AFDs. The article may have had other names for the earlier five AFDs. However, that doesn't matter at DRV, because this is not a proper DRV filing.
- There has been a history of edit-warring. That doesn't matter at DRV.
- In 2019, a DRN request about one entry in the list was filed at Wikipedia:Dispute_resolution_noticeboard/Archive_174#List_of_music_considered_the_worst, seeking moderated discussion among 21 editors when an RFC had already had No Consensus, was declined.
- This article has a long, controversial, and weird history. I do not know whether or where there is a forum to discuss it, but DRV is not that forum.

Robert McClenon (talk) 16:14, 25 June 2025 (UTC)[reply]

Yes, I've watched over the article since stumbling upon it a decade past. It's a constant magnet for arguments, with editors either mad music they like is on there, or mad they don't have the sourcing to add their personally hated music on there. But that's not a reason for deletion in itself, and the community has been consistently against deleting it (and similar articles covering films, games, etc) so I've focused on mediating disputes and watching over proposed changes. Sergecross73 msg me 16:26, 25 June 2025 (UTC)[reply]

To clarify, the comment about "editors being mad" was in reference to various etalk page discussions over the years, not GogoLion, who has seemingly taken offense to the comment. My only problem with GogoLion is their repeated failure to handle things at the correct venues. Sergecross73 msg me 17:31, 25 June 2025 (UTC)[reply]

Endorse and speedy close. Clear consensus to keep in five separate AFDs, plus a sixth that closed as no consensus. Appellant is making arguments as to why the article should be deleted rather than addressing concerns with the AFD result. The correct venue for these arguments is a seventh AFD. Frank Anchor 16:36, 25 June 2025 (UTC)[reply]
Irrelevant Question - What are the other five AFDs? Robert McClenon (talk) 18:23, 25 June 2025 (UTC)[reply]
Here you go:
Owen× ☎ 18:47, 25 June 2025 (UTC)[reply]
Endorse and Speedy close with a non-trivial sanction for wasting our time, not once but twice, with this AI bullshit. I'm quite willing to listen to a case for deleting that article, if anybody actually wants to write one, but I have zero tolerance for those who expect Wikipedia's editors and administrators to serve as gimps for their stupid robot. --DanielRigal (talk) 19:17, 25 June 2025 (UTC)[reply]

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

24 June 2025

Backyard History – "Delete" closure endorsed. Sandstein 08:24, 3 July 2025 (UTC)[reply]

The following is an archived debate of the deletion review of the page above. Please do not modify it.

I don't believe there was thorough consensus; a nominator somewhat erroneously categorised the sources as irrelevant but there was functionally no votes except mine (as author) to "Keep", and two attempts to re-list the XFD resulted in a single vote each, one that was Keep but changed to Delete and one that was Merge changed to Delete - leaving a total of three votes. I'd appreciate fuller review before deleting the article on one of the most prominent New Brunswick media outlet/projects that is widely syndicated in 10-30 newspapers, resulted in three non-fiction books under the same title, a podcast and a television show, etc.

Fundy Isles Historian - J (talk) 20:55, 24 June 2025 (UTC)[reply]

Comment - The deletion discussion was Wikipedia:Articles for deletion/Backyard History. The appellant did list the deletion discussion, but it doesn't show up in the listing. Robert McClenon (talk) 22:31, 24 June 2025 (UTC) [reply]
Relist - After a discussion of redirect targets and a change of a vote, more discussion and more viewers would be useful. Robert McClenon (talk) 22:31, 24 June 2025 (UTC)[reply]
Endorse Sorry, but Cunard is one of our more thoughtful and thorough AfD contributors, well versed in alternatives to deletion, and to the extent that Cunard was eventually unpersuaded to support such an ATD suggests that a delete closure was well within administrator discretion. Jclemens (talk) 01:58, 25 June 2025 (UTC)[reply]

Endorse. Properly deleted. There was a consensus to delete. There is no need for a “thorough consensus”, whatever that is. There is, however, a need to bring deletion discussions to close after a reasonable amount of time. SmokeyJoe (talk) 09:48, 25 June 2025 (UTC)[reply]
Endorse Sorry, there was indeed a consensus to delete the article, and the appeal doesn't make clear that there were missed sources. I also agree with Jclemens - Cunard is one of our best at finding sources, though sometimes I disagree with them about their interpretation of the sources, the fact they settled on a !delete vote in a limited discussion is a decent indicator that there weren't enough sources for a complete encyclopedia article on the subject. SportingFlyer T·C 09:57, 28 June 2025 (UTC)[reply]
Endorse Consensus was clear at the end. Hobit (talk) 14:36, 1 July 2025 (UTC)[reply]

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

Debangshu Bhattacharya – DRV is not needed when there is a replacement draft and you do not need permission here to write a new draft. You may submit to AfC Star Mississippi 01:09, 25 June 2025 (UTC)[reply]

The following is an archived debate of the deletion review of the page above. Please do not modify it.

I am requesting a review of the deletion of the article "Debangshu Bhattacharya", which was deleted after an AfD discussion in September 2024. Since then, several major developments have occurred: he was fielded as a Lok Sabha candidate by the All India Trinamool Congress in the 2024 general elections, which received extensive national media coverage (NDTV, Hindustan Times, The Hindu, Business Today, Times of India, etc.).

I have rewritten the article in my userspace, ensuring a completely neutral tone, strict sourcing, and a stronger focus on encyclopedic value and independent notability (especially around his role in popularizing the "Khela Hobe" slogan, and his role as TMC IT Cell head). Kindly review the new version and consider undeleting or allowing resubmission.

Draft: User:KXM26X/Debangshu_Bhattacharya

KXM26X (talk) 19:39, 24 June 2025 (UTC)[reply]

Endorse the 2024 AFD and its close, but see also:
Deletion review should not be used:… 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
. Either submit the userspace draft for review, or don't submit it for review. Robert McClenon (talk) 22:26, 24 June 2025 (UTC)[reply]

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

23 June 2025

Pedro Carlos of Orléans-Braganza

I took a look at the discussion about the article Pedro Carlos of Orléans-Braganza and I mostly disagree with the arguments presented, which seem biased to me. I would like to know how and where I can reopen this discussion so that the article can be rewritten and with new sources (which I provided, by the way).

I don't know if I should argue here, but in case it's useful: the mere previous existence of the article and the discussion about whether or not it is relevant due to its connection to the former Brazilian monarchy are proof that the topic of the article is, in fact, relevant. After all, it's been almost 140 years since the fall of the Brazilian monarchy, and its heirs are still being discussed. The argument that initiated the deletion process seems to me to be entirely based on the fact that the republic is well established in Brazil and the monarchist movement is weak, but I don't see how that is relevant to the topic of the article, whose purpose is ultimately to inform. Furthermore, I disagree that a person cited in so many international and mainstream newspapers such as The New York Times, ABC, Estadão, G1, El País, etc., and who lives in an old imperial palace in the middle of the Brazilian republic, is so totally irrelevant that he doesn't deserve an article.

And as I mentioned, based on the arguments for deletion, such as the lack of sources that are directly about the person in the topic, in this case Pedro Carlos of Orléans-Braganza, I took care to add new sources specifically about him and that are reliable, for example:

^[1] This one from Vanity Fair about his marriage.
^[2] This one from about the dispute for the headship of the House of Orléans-Braganza.
^[3] This one had already been mentioned in the pre-deletion article and used in the argument for deletion as "it's about the sales of historical objects that Pedro Carlos made", and it's true. What the argument tries to expose is that it's from a mainstream Brazilian newspaper, O Globo, which calls him "Dom (D.)", which is an honorific, recognizes him as a member of the imperial family (extinct or not) and says that he lived in the former imperial palace of Grão-Pará. Three points that, together, make the topic of the article, the person of Pedro Carlos, worthy of note, at the very least.
^[4] Finally, this source was already mentioned and the argument for deletion goes as "Prince Pedro Carlos visited a museum". This clearly demonstrates his notability, since there would be no news, or even an article, about a visit by a non-notable person to a museum in the official media of the city of Juiz de Fora. It is worth remembering that Pedro Carlos is not a historian or museologist, so his notability comes from his ancestry and this does indeed confer notability on the individual.

^ P., D. (9 December 2021). "Se casa el príncipe Pedro Carlos, primo carnal del rey Juan Carlos y pretendiente del trono de Brasil" (in Spanish). Retrieved 20 June 2025.
^ Dellorme, Philippe (23 July 2022). "Au Brésil, le très disputé titre de chef de la maison impériale". Pointe de Vue (in French). Retrieved 20 June 2025.
^ "A realeza brasileira ao alcance das mãos - Brasil - Estadão". Estadão (in Portuguese). 9 April 2017. Retrieved 20 June 2025.
^ Ribeiro, Vinícius (8 Mar 2019). "Museu recebe a visita do príncipe Pedro Carlos de Orleans e Bragança". Prefeitura de Juiz de Fora (in Portuguese). Retrieved 20 June 2025.

Von Burgundy (talk) 15:22, 23 June 2025 (UTC)[reply]

~~Speedy close~~ (changed !vote, see below). No valid ground has been advanced to overturn the prior deletion decision. However, the discussion was four years ago and not particularly well-attended; the title is not salted and the page may be recreated if the appellant believes sources will support standalone notability. I would recommend that @Von Burgundy use the articles for creation process to minimize the chances of a return trip to AfD. Dclemens1971 (talk) 21:21, 23 June 2025 (UTC)[reply]

The Vanity Fair article is alright, but the second and third sources are passing mentions and the fourth is a non-independent governmental source. If you choose to refund this article you'll need to find more sources of significant coverage directly of Pedro Carlos himself, and covering more than just his wedding, to get to GNG. JoelleJay (talk) 23:20, 23 June 2025 (UTC)[reply]

What's GNG and what's the criteria for which sources are alright or not? I obviously avoid/would avoid biased sources or sources from unreliable sources. But regarding sources that only cite the person in the article, in this case Pedro Carlos, and are not "per se" about him, I don't see why they are any less valid, especially when there are so many of them, which is a clear attribution of recognition to their relevance. Especially given the context of these sources; he may not be the central topic of the articles, but his name is not mentioned "en passant" either. It is relevant, in the sources, who he is for the text presented. Von Burgundy (talk) 02:38, 24 June 2025 (UTC)[reply]

Question - Is the appellant asking to overturn the 2021 AFD, or is the appellant asking to overturn the 21 June 2025 G4? The failure of this appeal to say what the appellant wants overturned appears to be the reason why Dclemens1971 calls for a Speedy Close, and I agree with that unless the question can be answered in a timely manner. Robert McClenon (talk) 00:08, 24 June 2025 (UTC)[reply]
I didn't see the G4 in the logs until you pointed it out and was going off the appeal, which only noted the 2021 discussion. If the article is substantially the same as the 2021-deleted one, the G4 should stand, but a different article would not be G4 eligible. Obviously I can't see the histories of the two to know. Dclemens1971 (talk) 02:00, 24 June 2025 (UTC)[reply]

I'm asking to overturn the 21 June 2025. I re-created the article providing some new sources and it was promptly deleted again arguing about its previous deletion in 2021. Von Burgundy (talk) 02:32, 24 June 2025 (UTC)[reply]
@Von Burgundy: Looking at the version comparison supplied by @Cryptic below, you had several passages that were copied nearly verbatim from the previously deleted version without attribution. Copying within Wikipedia requires attribution to the original creator. Dclemens1971 (talk) 10:57, 24 June 2025 (UTC)[reply]
Well, I copied parts of the text of the former deleted article, yes. Partially because my point is that that article shouldn't have been deleted to begin with. Either way, how shall I credit the original author? I kept his sources, though. Von Burgundy (talk) 15:45, 24 June 2025 (UTC)[reply]
@Von Burgundy See here for instructions: Wikipedia:Copying_within_Wikipedia#Proper_attribution_to_the_author_and_the_page. If deletion is overturned, you can use a WP:DUMMYEDIT to add attribution through an edit summary. Dclemens1971 (talk) 04:16, 25 June 2025 (UTC)[reply]
Temp undelete, please so we can assess whether the mos recent version is eligible for G4. Jclemens (talk) 04:27, 24 June 2025 (UTC)[reply]
Comment - I concur with the request for a temporary undelete, but would also advise the appellant that submitting a draft via AFC may be an alternate useful approach. Robert McClenon (talk) 04:30, 24 June 2025 (UTC)[reply]
Diff from the version deleted at afd. Endorse and blacklist. —Cryptic 04:43, 24 June 2025 (UTC)[reply]
Overturn G4 and list at AfD. Separate from the attribution failure mentioned above, this is not a valid G4; the articles had some shared passages but were not substantially identical. This article needs to go through a new round of AfD. Dclemens1971 (talk) 11:00, 24 June 2025 (UTC)[reply]

Use AFC strictly G4 shouldn’t be used for good faith attempts to try again but its clear from this discussion that a) there are inadequate sources to avoid BLP1E and b) that if the Nom doesn’t understand what the GNG is then they lack the experience to handle a BLP sensitively. AFC ensures that if barriers to recreation are overcome there will be some oversight of what gets published. Spartaz ^Humbug! 13:03, 24 June 2025 (UTC)[reply]

AFC is not mandatory, so while I think it would entirely reasonable to specify some cases where AFC might be made to be mandatory in the future--and this might be such a case--I think it's premature to have such expectations in this specific case. Jclemens (talk) 01:54, 25 June 2025 (UTC)[reply]

Overturn G4 and send to AfD, which can not only consider the sourcing, but whether, if deleted, create protection should also be imposed to forestall future issues. Jclemens (talk) 01:54, 25 June 2025 (UTC)[reply]
"future issues" being people trying to argue on why the article is worth to be listed in an encyclopedia? Don't you think that's too harsh?

My point in trying to re-create the article four or almost four years after its deletion is that, precisely. I didn't simply returned the former article from the dead, I created a new one, with differing content and sources (while keeping the original ones I thought useful). Von Burgundy (talk) 00:28, 27 June 2025 (UTC)[reply]
I am not stating there are issues the should lead to create protection ("salting"), but noting that DRV, here, is not the place to assess them. A new AfD should. Jclemens (talk) 03:52, 28 June 2025 (UTC)[reply]
Overturn G4. Not even close to being sufficiently identical to the version deleted at AFD, including several sources which were published after the AFD closed. This can be taken to AFD if desired. Frank Anchor 12:09, 25 June 2025 (UTC)[reply]
Endorse G4 per Cryptic's diff and salt. This would not be kept at a new AfD and pretending otherwise is a waste of everyone's time. SportingFlyer T·C 09:59, 28 June 2025 (UTC)[reply]
So, this has multiple paragraphs moved around, zero words of new reliably-sourced content, and a single new prima facie usable source - which last is something, but it doesn't verify anything in the article. It was even identified, correctly, as copyright infringement by a bot. If this is the standard for significant change, then you're going to have a hard time finding any deletion labelled G4 that you'd approve of. I'd suggest going to WT:CSD to remove it from policy is a better approach than trying to annul the policy piecemeal at DRV. —Cryptic 08:40, 1 July 2025 (UTC)[reply]
Send to AfD. Which is not the same as "overturn G4", because if this is enough to invalidate a G4, as Cryptic says, well, AfD won't know what hit it. This is well over my own G4 bar and I think I'm one of the more conservative folks handling CSDs. (As irritated AfDers have made clear.) These paragraphs are basically identical! What's been added is "dynastic position", etc, which are not things AfD participants have much sympathy for at all. But heck, if we've got a bunch of AfD regulars saying to send this to AfD, we can send it to AfD. You'd all better vote, though. -- asilvering (talk) 16:51, 1 July 2025 (UTC)[reply]
Endorse G4 per Cryptic's analysis above, or, if there is not consensus here to do that, send to AfD again. However, that would be a waste of community time: I closed the original AfD and can't see a new AfD come to a different conclusion. Sandstein 09:43, 2 July 2025 (UTC)[reply]
Endorse I see Cryptic's articulation as more confincing here. I expressly disagree with Asilvering's comment before; sending this to AfD would necessarily involve overturning the G4 as the two are inseperable. * Pppery * _{it has begun...} 06:10, 6 July 2025 (UTC)[reply]

Randy Cooper (Model maker) (closed)

Randy Cooper (Model maker) – Deletion endorsed. Daniel (talk) 01:37, 1 July 2025 (UTC)[reply]

The following is an archived debate of the deletion review of the page above. Please do not modify it.

I closed this discussion as "delete", but have been challenged by the article creator on my talk page. As a deletion review is a better location for this, I am bringing the discussion here. Ritchie333 ^(talk) ^(cont) 14:35, 23 June 2025 (UTC)[reply]

I don't think there is a consensus for delete. There are 3 Keeps and one draftify to 5 deletes. Most of those deletes came after the 3-week mark, after I had asked 2 administrators to close, but neither one of them did. Most of the deletes come from inexperienced editors. I said that, and the administrator decided to punish me. I was not bludgeoning or insulting anyone, just disagreeing. I was very much doing that within limits. Wikipedia:Don't bludgeon the process. "Everyone should have the chance to express their views within reasonable limits. Sometimes, a long comment or replying multiple times is perfectly acceptable or needed for consensus building." Orlando Davis (talk) 16:18, 23 June 2025 (UTC)[reply]
The deletion nomination for the article was kept open longer than the ideal amount of time. And it's hard to know if there wasn't vote stacking going on. The Randy Cooper article includes a source from Fine Scale modeler and the Evening Independent that are both highly reliable and independent. Additionally, it has many interview sources. Orlando Davis (talk) 16:27, 23 June 2025 (UTC)[reply]

Most of the deletes come from inexperienced editors.
Delete !voter edit counts: 265810, 25756, 14476, 138, 1659, 84573, 10645. What exactly is your threshold for "experienced"? A cutoff of 10000 edits would leave us with 5 delete to 1 keep and 1 draftify... JoelleJay (talk) 23:51, 23 June 2025 (UTC)[reply]
Fair enough. In my view, it is a combative move to even participate in an AFD unless it's your article. Why do it unless you enjoy arguments? The person who wrote the article should be given some slack from a bunch of people ganging up on him or her. Orlando Davis (talk) 00:14, 24 June 2025 (UTC)[reply]
That's how to treat someone whose spent many hours working for Wikipedia for free? Orlando Davis (talk) 00:17, 24 June 2025 (UTC)[reply]
Another thing. We don't have any subject matter experts on model making here. That is essential for a fair review. Orlando Davis (talk) 00:20, 24 June 2025 (UTC)[reply]

I did not "punish" you. You're bludgeoning here like you bludgeoned there. Endorse close and consider sanctions for @Orlando Davis if the disruption continues. I'm just maintaining the articles that I have already written and this is the only one I really need to do. is not an attitude condusive to collaborative editing. FWIW, to my knowledge I've had no interaction with them prior to my relist of the AfD which was normal log clerking. Star Mississippi 00:18, 24 June 2025 (UTC)[reply]
Maybe they should sanction you also since you don't really keep a cool head yourself. I don't think you are understanding what bludgeoning is or isn't. Orlando Davis (talk) 00:24, 24 June 2025 (UTC)[reply]
Feel free to open a discussion if you think I should be sanctioned @Orlando Davis Star Mississippi 00:53, 24 June 2025 (UTC)[reply]
As a participant of the discussion, while I appreciate his input, I don't believe Randy Kryn's status of being 20 most active editors gives his opinion or, more pertinently, interpretation of the policies and guidelines, any more weight than mine, Theroadislong's, Oaktree's or Reader's, as Orlando seems to want to. Perhaps a mere ten thousand edits isn't much these days, but I'd like to assure everyone that my input is carefully considered when I offer them. The outcome of a deletion discussion is not punishment, nor are deletion discussions a grand battle between deletionists and inclusionists. Or, at least, they are not supposed to be treated as one.
Finally, deletion discussions are not an admin suggestion box. Administrators, when closing a discussion, are empowered to exercise judgement to disregard or reduce the weight of arguments that contradict policy, are based on personal opinion only, or show no understanding of the matter of issue. The closing administrator does not have the discretion to disregard comments they find to exhibit deletionist bias, or to ignore our policies and guidelines. I would endorse both Star Mississippi's valiant (though unfortunately ultimately unfruitful) attempt to keep the discussion rooted in the relevant PAG as appropriate administrative actions, as well as Ritchie's close as the only possible close supportable by a reasonable interpretation of the discussion. There is no other closure within an allowable level of discretion. I will leave the discussion of conduct to another venue if Orlando wishes to continue it. Alpha3031 (t • c) 16:49, 23 June 2025 (UTC)[reply]
Alpha3031, I'm one of the 20 most active editors? Didn't know that, is there a list somewhere. Thanks. Randy Kryn (talk) 23:09, 24 June 2025 (UTC)[reply]

I'm not sure edit counts really matter in this discussion. Oaktree b (talk) 00:26, 25 June 2025 (UTC)[reply]
Ah, I think the mistake is that it's 200, not 20. And of course the number of an editor's edits don't matter in background discussions. Randy Kryn (talk) 00:47, 25 June 2025 (UTC)[reply]
Endorse. A clear consensus to delete is ultimately present in the discussion. A "No Consensus" close might have been reasonable at an earlier point, but relisting was not an abuse of discretion. The majority of the contested sources look like interviews, and there is a reasonably broad consensus that those count less for notability than non-interview profiles. The close is not so manifestly in error that I can recommend an IAR, restore. Eluchil404 (talk) 17:40, 23 June 2025 (UTC)[reply]
Endorse as the correct close. None of the Keeps addressed the issue of SIGCOV, and some didn't bring up any P&G-based argument. After five rejections at AFC, I see little point in sending this back to draft yet again. The repeated, combative moves into mainspace are a form of edit-warring, and should be handled as such. If Orlando Davis isn't happy with our existing tagging system, they are welcome to start an RFC to change it. Disruptive editing to make a WP:POINT isn't helpful. Owen× ☎ 20:05, 23 June 2025 (UTC)[reply]
Thank you for your response. I concede that the consensus thus far is for delete. However, I resent being told I was combative, when I had every right to bring up the article myself as an extended confirmed user and never had any obligation to take it up to the Articles of creation any of the other times. I initially preferred that route as I was trying to not be combative and work out issues in private space. I took it up myself to articles of creation over and over again when I never had to. How is that edit warring? Denial at Articles of creation is no big deal since many articles are rejected and later accepted by other editors, sometimes with little change, despite multiple rejections, as opinions between reviewers vary. I've had a couple of editors reject me and another accept me several times. This time I ran out of patience and preferred to bring it up myself since improving the article had peaked in my opinion.

Wikipedia is in itself very combative as many media sources have pointed out unfair bias in Wikipedia, and one of the founders of Wikipedia has left due to its bias. So there must be something to my point of view. I don't want to dedicate the time to an RFC as I only came back to Wikipedia for this article. I no longer edit Wikipedia very much. Orlando Davis (talk) 21:23, 23 June 2025 (UTC)[reply]
I resent being told I was combative, when I had every right to bring up the article myself as an extended confirmed user - the fact that your account technically allows you to engage in disruptive editing does not mean you have "every right" to do so any more than I have the right to use my admin tools to force my view in a content dispute. WP:BRD applies as much to article creation as it does to revising. The extended confirmed bit, like the sysop bit, can be revoked if it is used to bypass collaborative editing. Your interaction with the other editors involved was decidedly combative. And your declaration that you only came back to Wikipedia for this article presents you as a WP:SPA - not a good look. I strongly suggest you do not abuse your privileges as an extended confirmed editor, and start working with other editors instead of against them. Owen× ☎ 21:40, 23 June 2025 (UTC)[reply]
I'm not a single purpose account. I'm just maintaining the articles that I have already written and this is the only one I really need to do. That's not the same thing. You go ahead and do what you gotta do. I really don't care anymore. Orlando Davis (talk) 21:46, 23 June 2025 (UTC)[reply]
Endorse as clear consensus to delete. Electing to relist the discussion is well within the scope of administrator action, the fact that 2 admins elected to do so indicates an independent consensus to continue the discussion. The "experience of editors" is irrelevant to the substance of the argument put forth, which is concerns regarding whether the sources are sufficient to meet GNG. Suggestions of "vote stacking" are WP:ASPERSIONS at best. Also of note is the WP:IAR argument brought up during the discussion by some keep !voters, in which case the WP:ONUS is on the argument maker to demonstrate why an exception should be made for WP:GNG. — 🪫Volatile ^{📲T | ⌨️C} 21:06, 23 June 2025 (UTC)[reply]
Additional note: those seeking to overturn should look into conducting an independent source review, addressing WP:GNG concerns would go a long way in convincing others the page should be kept (or for a non-disruptive recreation of the page, as noted by Owen). — 🪫Volatile ^{📲T | ⌨️C} 21:06, 23 June 2025 (UTC)[reply]
Endorse. Keep arguments clearly failed to convince the majority of !voters that the topic meets our notability requirements. We have 6 policy-based delete !votes including the nominator (and discounting one drive-by), plus a comment from an admin that reads as additional opposition to keeping. Meanwhile one keep !vote carries no valid rationale at all and the other two assert sufficient sourcing without demonstrating such. JoelleJay (talk) 23:38, 23 June 2025 (UTC)[reply]
Endorse. Had I participated in the discussion, I probably would have landed on a "keep" based on ~~WP:NFILM~~ WP:NCREATIVE _{(typed the wrong damn policy)} (and I'm surprised no one brought it up), but this is not AfD round two and there is no defect in Ritchie's close. Dclemens1971 (talk) 00:09, 24 June 2025 (UTC)[reply]
Endorse as a reasonable reflection of consensus. Stifle (talk) 07:48, 24 June 2025 (UTC)[reply]
endorse as the only possible outcome. @Orlando Davis: your conduct here and on the AFD was so suboptimal that I am suprised you were not blocked for disruption. Take heed of this warning please. Spartaz ^Humbug! 13:11, 24 June 2025 (UTC)[reply]
I have to answer multiple times because I don't think of everything at once. For example, I just now figured out, thanks to DClemens, that Cooper qualifies based on NP creative. Also, that it matters that there are no subject matter experts on model making in this forum. What difference would it make if I got blocked? This forum doesn't care about a word I have said, and I don't get paid. And I doubt that would happen; it's an empty threat because I have done nothing wrong. If I go to a restaurant and get treated badly, I can give a bad review. I can give Wikipedia a bad review for treating me badly, too. Any smart organization knows not to offend since bad reviews can be destructive.

I am being bated into an emotional reaction by being accused of bludgeoning, so if I am, well, that is what set that in motion. Being accused falsely. The majority in this forum is wrong, and it is a fallacy of the majority to assume otherwise, which is why I have the right to debate disproportionately if I am in the minority. If Wikipedia rules don't allow for that, they should. Within reason, as I have done. I never used insults or said anything that wasn't logical, nor did I answer more than necessary to adequately make my points. Orlando Davis (talk) 13:52, 24 June 2025 (UTC)[reply]
@Orlando Davis, you have indeed verged toward bludgeoning in this debate. No one is trying to bait you to do anything. You could simply WP:COAL, knowing that you have already expressed your views. You do not have the right to debate disproportionately if [you are] in the minority, since WP:CONSENSUS and WP:CIVIL are core policies. None of us are getting paid to be here; we are here because we think this is a valuable project worth our volunteer time. And while I do think there was a case for notability for the subject, not everyone would likely agree with me. Instead of trying to overturn a valid consensus, you could rewrite a draft using reliable sources to demonstrate the significance of Cooper's roles in the production of notable films, then submit it using articles for creation. The independent review there can improve the article and help it avoid deletion in the future. However, I strongly urge you to avoid WP:ASPERSIONS like being accused falsely before you exhaust the patience of others in this discussion. Dclemens1971 (talk) 15:55, 24 June 2025 (UTC)[reply]
Please don't say I am bludgeoning because this is new information. I did more research and found out additional information. Here is an article about how Randy Cooper and his friend worked on the Iron Man 2 models. https://archive.sltrib.com/story.php?ref=/ci_15025239 Also, I found another movie credit of him in Gentleman Broncos by a suitable source. https://www.tcm.com/tcmdb/title/737404/gentlemen-broncos#overview] I have others by IMDB and fandom that I was told by the articles of creation are not usable. I also found out that Boss Films was nominated for an Oscar for Alien 3, and Cooper worked on that film for Boss Films. Orlando Davis (talk) 17:45, 24 June 2025 (UTC)[reply]
Endorse - A valid conclusion by the closer. I cannot recall AFDs or DRVs where repeatedly stating the minority position has been useful. Pinging the participants in the AFD and the AFC reviewers: @Theroadislong, Oaktree b, Agnieszka653, Alpha3031, Randy Kryn, Moritoriko, BD2412, Dorsetonian, and Stifle: @Jamiebuba, Dan arndt, Anuwrites, RangersRus, and Timtrent: Robert McClenon (talk) 22:19, 24 June 2025 (UTC)[reply]
@Robert McClenon I don't recall reviewing this and cannot find it in my logs. I have no opinion nor insight to offer I am afraid. I concur with your second sentence. Doing that is generally unhelpful. Those who say the least in defence of an article often make the most impact in its favour. 🇵🇸‍🇺🇦 Fiddle^Timtrent Faddle^Talk to me 🇺🇦‍🇵🇸 22:39, 24 June 2025 (UTC)[reply]
User:Timtrent - The history shows that you draftified this on 10 February 2025. Robert McClenon (talk) 23:33, 24 June 2025 (UTC)[reply]
@Robert McClenon So I did. Thank you. It had no sources. I did not follow out after that so cannot comment. 🇵🇸‍🇺🇦 Fiddle^Timtrent Faddle^Talk to me 🇺🇦‍🇵🇸 06:26, 25 June 2025 (UTC)[reply]
Endorse (involved). Orlando Davis, you put up a good defense for the page, commendable. I favored keeping because of the detailed extent of Cooper's work, which seemed to be enough for GNG, and the fact that publications in his field of endeavor interview him as a peer. But a move review takes into account only the close to determine if it is a reasonable and accurate summary of the discussion. A ~~move~~ (deletion) review is not a rehashing of the arguments but a judgement call on the close. In this AfD it is a valid summary, hence the number of endorsements here. As you settle into Wikipedia the ropes, nudges, and cooperative nature of the volunteers becomes more obvious, and knowledge of things like Move Review play a part. Thanks, and hopefully there will be fuller articles and accolades and the article can be brought back at some point (Cooper's work is memorable and some of it is almost iconic, but it takes more than a few editors on this website realizing that, but unimpeachable sources which echo his notability). Randy Kryn (talk) 23:22, 24 June 2025 (UTC)[reply]
User:Randy Kryn - This is a Deletion Review rather than a Move Review. The two processes are similar in that they review the judgment of the closer and are not rehashes of AFD or RM, so your points are applicable. Robert McClenon (talk) 23:33, 24 June 2025 (UTC)[reply]
Thanks Robert McClenon, my main experience in close reviews is with moves and not deletions and came on your ping, hence the mix-up. And thanks for the pings, not everyone does that. Randy Kryn (talk) 23:37, 24 June 2025 (UTC)[reply]
p.s. Robert McClenon, I think you inadvertently deleted Orlando's post. Randy Kryn (talk) 23:40, 24 June 2025 (UTC)[reply]
Endorse (involved). I am not sure why my reply did not go through so I will repost. I will follow Randy Kryn's lead and concede that the close was a reasonable and accurate summary of the discussion even though I also believe Cooper's work is notable and iconic but the results are beyond my ability to change. I would like to thank everyone involved in this discussion for their patience, as it is only my second AFD discussion, and I am still learning. Orlando Davis (talk) 23:42, 24 June 2025 (UTC)[reply]
Endorse I saw this article was up for deletion and added it to my watchlist before it was closed. I considered commenting in favor of its deletion. There seemed to be such a strong consensus for deletion that I didn't feel it was necessary to pile on. The editor who is making about a dozen comments in a discussion when most people are making one is definitely bludgeoning. Asparagusstar (talk) 00:17, 25 June 2025 (UTC)[reply]
Several editors already made allegations of bludgeoning. So over and over again I am being accused of bludgeoning. I would consider that to be group bludgeoning which is also bludgeoning. I already endorsed deletion. Give it a rest. Orlando Davis (talk) 00:43, 25 June 2025 (UTC)[reply]
Yes, based on the comments of many editors, it would appear that there is a strong consensus of obvious bludgeoning behavior. One way to react to this consensus, other than continuing to bludgeon, would be to refrain from further problematic behavior. This does not require a further response, as this would just be further bludgeoning. Thank you. Asparagusstar (talk) 01:26, 25 June 2025 (UTC)[reply]
Endorse. Historyexpert2 (talk) 02:13, 25 June 2025 (UTC)[reply]
Endorse - Very clearly a correct call, including the closing comments and the guidance given by the relisting admin. The suggestion that those !voting delete lacked experience is disingenuous. There was one delete !voter who did indeed lack experience and no evidence that the admin gave any weight to what was essentially a vote on their part. It was a clear delete all the same. Sirfurboy🏄 (talk) 08:01, 25 June 2025 (UTC)[reply]
I am responding to sirfurboy. I have to apologize for that. That was something I said in the heat of the moment. However, I was referring more to article writing than the number of edits and ratings of those articles. For example, to me, an editor who has written several featured articles has in some cases done more than an editor who has made thousands of edits and no articles or articles but none of them are featured articles. It depends on context. It varies. That's not to say that the volunteer work that editors do isn't valuable, but that was what I was talking about. However, I myself am not a very experienced editor. So that was not something that made sense to say. So again, I apologize. I don't think you should ignore the things I said that do make sense because that statement didn't. Orlando Davis (talk) 13:44, 25 June 2025 (UTC)[reply]
Again, I apologize; I should have been better than that. But this conversation was closed due to a lack of civility, but this whole AFD process is a disgusting lack of civility towards the subject of the article (I don't know him, never met him). And as far as lack of civility, I wasn't the only one. Star Mississipi's condescending tone at a point where the conversation was very civil escalated the argument. And Moritoko made fun of my writing and implied that craftsmen are not as important as designers. Orlando Davis (talk) 07:20, 26 June 2025 (UTC)[reply]
Endorse – The delete arguments are stronger in both quality and quantity. Quantity has been addressed above. In terms of quality, the keep side did not adequately address the superficial coverage noted in the nomination, nor the niche nature of the sources — a concern raised later in the discussion. gidonb (talk) 14:15, 26 June 2025 (UTC)[reply]
And since the consensus is obviously delete, I ask that this article be deleted quickly. Orlando Davis (talk) 16:29, 26 June 2025 (UTC)[reply]
You're responding too much. Sit back and learn how to respond to AfDs — and when not to open deletion reviews. Take a deep breath and learn from your mistakes. Just the other day you closed an AfD yourself that you had opened, without allowing a third party to summarize at closing time. People make mistakes. If you learn from them this reduces the waste. gidonb (talk) 16:37, 26 June 2025 (UTC)[reply]
It's a free country. I can respond however much I want to. Orlando Davis (talk) 17:02, 26 June 2025 (UTC)[reply]
Wikipedia operates by community consensus and established guidelines. We try to be patient, but persistent disruption isn't tolerated. Continued nuisance behavior does lead to sanctions. gidonb (talk) 18:48, 26 June 2025 (UTC)[reply]

@Orlando Davis this is your final warning. Stop being disruptive or you will be blocked and it won't only be about this subject either. Star Mississippi 01:54, 27 June 2025 (UTC)[reply]

To be fair to Orlando, Ritchie was the one who opened this DRV. Alpha3031 (t • c) 04:56, 27 June 2025 (UTC)[reply]
But, see User talk:Ritchie333#Wikipedia:Articles for deletion/Randy Cooper (Model maker). Dorsetonian (talk) 06:15, 27 June 2025 (UTC)[reply]
Indeed, I procedurally opened the deletion review because Orlando Davis asked me to, after asking my views on the article (as an uninvolved closing admin, I didn't have any). Ritchie333 ^(talk) ^(cont) 12:21, 27 June 2025 (UTC)[reply]
Orlando had it reopened. The original decision to close as delete was sound. A lot of community time has been wasted, first at the AfD, now again in this discussion, and in between on Ritchie's page. I will add that not all of Orlando's observations on Ritchie's page are wrong. I do see a group of mostly newer editors (traditionally, that would be JPL) who make the most random deletion claims at AfDs. That said, there are many deletionists, especially longer-serving ones, who make well-reasoned arguments. This entire line was totally irrelevant, given that there was an overwhelming consensus for deletion, and for very good reasons. gidonb (talk) 15:56, 28 June 2025 (UTC)[reply]

Yes, I did look at the discussion on Ritchie's talk (and my original comment was actually largely a response to that, in fact) I just wanted to point out that Orlando did not wander here entirely unprompted. Personally, I'd hope we're willing to extend some latitude to someone who appears mostly unfamiliar with the typical and expected conduct in projectspace discussions, and would just like it over with at this point (especially given that if this were opened by them, I'd consider it eligible for withdrawal given the unanimous endorses so far). Perhaps it might not compare to our most infamous of stressful discussions (ANI, RfA, etc), I couldn't (and probably shouldn't) say, but it probably isn't pleasant if one sees it as continued scrutiny of oneself as an editor. Alpha3031 (t • c) 13:12, 29 June 2025 (UTC)[reply]

Not knowing is not the main problem. Main problem is not caring. gidonb (talk) 14:29, 29 June 2025 (UTC)[reply]

Endorse There's a clear consensus to delete this article. I've also looked at the temporarily undeleted version of the article and would also have !voted delete, which is irrelevant at DRV apart to note that I do not believe any clear error was made by those !voting to delete the article. SportingFlyer T·C 10:01, 28 June 2025 (UTC)[reply]

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

22 June 2025

Template:Transl

The RfD closure failed to account for the fact that Template:Transl, unlike the other redirects bundled in that nomination, was the long-standing name of Template:Transliteration since 2007, which was moved away from that title only in 2022. Although replacement by bot was mandated, deletion still broke a lot of historical references. While there may have been consensus to delete the three other redirects, several participants !voted specifically to keep Template:Transl, and I do not believe consensus was in support of deleting it. --Paul_012 (talk) 09:01, 22 June 2025 (UTC)[reply]

Issue raised with closer DMacks here. Note that the closure was also challenged by jlwoodwa here and by jacobolus here. --Paul_012 (talk) 09:06, 22 June 2025 (UTC)[reply]
Indeed, this was a serious mistake of discussion closure which substituted the closer's personal preference for community consensus, and caused (and will continue to cause) harm to Wikipedia, especially since our software has never properly handled transclusions when viewing historical versions of pages, so now almost 2 decades of historical permalinks are going to have broken transliterations on them. –jacobolus (t) 11:01, 22 June 2025 (UTC)[reply]
I stand by my closure (I think I responded to each concern raised on my talkpage there, with specificity...can find the links later if needed). While it's definitely true that not all four involved templates had equally strong support, I saw the general concern did apply to all of them and was more supported than not by the guidelines and their weighting of pros/cons/etc mentioned. I have not been involved in this template-area and do not feel I raised new concerns or other judgement of my own on the issues beyond evaluating what others stated. As I have said, I made no prejudice against non-ambiguous forms. I'm having trouble finding where preserving the original/complete viewability of historial revisions is mentioned (and prefereably pointing to a policy or guideline) by a comment in the DRV. DMacks (talk) 11:33, 22 June 2025 (UTC)[reply]
- The harm in deleting such redirects is, I believe, described by the second main consideration under WP:R#HARMFUL. Such deletions aren't prohibited, but should only be considered when the concerns are demonstrably outweighed by the harm caused by the existence of the redirect. --Paul_012 (talk) 12:40, 22 June 2025 (UTC)[reply]
- Regarding the talk page responses, I already linked the archived discussions above. Apologies on my part for not responding further before starting the DRV, but the discussion had already been archived and given our conflicting opinions I don't think further discussion could have preempted the need for DRV. --Paul_012 (talk) 12:48, 22 June 2025 (UTC)[reply]
Comment - This is a train wreck. Robert McClenon (talk) 01:43, 23 June 2025 (UTC)[reply]
Might tagging it {{deleted template}} be an acceptable compromise? —Cryptic 02:32, 23 June 2025 (UTC)[reply]
If preserving historical revisions is a concern, this may be a valid solution that could've been implemented without a deletion review. —CX Zoom[he/him] ^{(let's talk • {C•X})} 19:45, 23 June 2025 (UTC)[reply]
Unbundle - Put the four trains on four tracks by splitting this into four RFDs.
- Relist Template:Transl, which is the one that is being contested. The closure does not seem to have reflected consensus.
- Leave the three uncontested template redirects in an open state so that they can be closed or relisted by any admin.

Robert McClenon (talk) 04:45, 23 June 2025 (UTC)[reply]

Comment I'm not familiar with the usual standards for deleting template redirects, but it seems like the "it's been in use since 2007" argument should have been accorded more weight here. Jclemens (talk) 05:52, 23 June 2025 (UTC)[reply]
- Overturn transl only We don't need a specific guideline that says "don't break historical stuff without a really good reason" for that to be considered a valid reason to not delete a redirect and it appears that such was the case here. Jclemens (talk) 23:38, 26 June 2025 (UTC)[reply]
Overturn transl to either keep or no consensus. I don't see consensus to delete that template. The editors who weighed in on it separately from the rest generally favored keeping this template, while several who !voted to delete all seemed not to understand the purpose of the discussion. I don't think a relist would be helpful – better to close as no-consensus and have a completely fresh discussion on this one template. Toadspike [Talk] 19:34, 23 June 2025 (UTC)[reply]
Those who did favour keeping the template mostly argued on the basis of length of "transliteration" compared to "transl". This, however, is not a policy-based ground to keep ambiguous redirects, and there have been shorter redirects created for this exact purpose ({{tlit}}, {{xlit}}), which mooted the length argument anyway. Some other arguments pointed to the historic usage of Transl, but again that is not an enshrined policy, and TfDs have previously deleted hundreds, if not thousands, of redundant/replaced/renamed/substituted templates as well. Few other keep arguments were made due to general frustration with the numerous <<See RfD>> links in the articles, some of which were rescinded, the others weren't until closure. This last line of argument stemmed from a fundamental misunderstanding of what the process is for, and should be discarded altogether. —CX Zoom[he/him] ^{(let's talk • {C•X})} 19:56, 23 June 2025 (UTC)[reply]
"Few other keep arguments were made due to general frustration with the numerous <<See RfD>>" – These arguments were made on both sides, cf. Duyneuzaenasagae's comment. I agree with you that they should be discounted, though.

I don't see any arguments to keep on the basis of length. I'm also not seeing any evidence that keep !voters were unaware of the shorter redirects or that they were opposed to their use. In fact, jacobolus's argument, which is close to a keep, even suggests mass-replacing the ambiguous terms with the shorter redirects.

"other arguments pointed to the historic usage of Transl, but again that is not an enshrined policy" – well, unless this argument explicitly runs counter to policy, editors are allowed to make it and the closer shouldn't discount it. Toadspike [Talk] 08:53, 5 July 2025 (UTC)[reply]
Overturn “transl” to no consensus and leave the others as is. There was not consensus to delete that template as there was for the others. No objection to an immediate renomination focused on just the one template. Frank Anchor 02:03, 24 June 2025 (UTC)[reply]
Endorse (involved) per my above comment. Despite being numerous in number, the arguments made are not a part of any standard policy or guideline. —CX Zoom[he/him] ^{(let's talk • {C•X})} 12:11, 24 June 2025 (UTC)[reply]
Overturn "transl" to no consensus and relist. I think this was ambiguous enough that I wouldn't want to say good/bad close without getting out a fine-toothed comb and doing the work of closing it myself. But it does look to me like this topic needs more discussion, so we should let that happen. -- asilvering (talk) 17:01, 1 July 2025 (UTC)[reply]

v t e Wikipedia community
For a listing of current collaborations, tasks, and news, see the Community portal. For a listing of ongoing discussions and current requests, see the Dashboard.
General community topics	Administration News The Signpost Goings-on In the media Meetups Mailing lists Wikipedians Statistics The Wikipedia Library Centralized discussion Village pump Idea lab Policy Proposals Technical Miscellaneous WMF Holidays Bots
Contents and grading	Requested articles Most-wanted articles Images needing articles Articles needing images Articles for creation WP:AFC/R WP:AFC/C Creating articles Help Vital articles Articles for improvement Peer review Good article nominations Featured article candidates Lists Pictures Topics Article translation Pages Main Page Errors
WikiProjects and collaborations	Directory Culture and the arts Geographical History and society Science, technology and engineering Wikipedia assistance and tasks Patrols Recent changes Counter-Vandalism Unit Accessibility Organizations category
Awards and feedback	Reward board Contests A nice cup of tea and a sit down Charitableness WikiLove Compliment before criticism Kindness Campaign Thanks!
Maintenance tasks	Task Center Open tasks Backlog Category Admin category Edit requests Category Database reports Category tracker Dusty articles Special pages New pages Recent changes Controversial issues
Administrators and noticeboards	Administrators' noticeboard Incidents Edit warring Vandalism Admin dashboard Admin requests Closure Page protection User permissions Sockpuppets Open proxies Revision deletion Oversight Request Usernames Changing Title blacklist OTRS Bureaucrats' Requests for adminship and bureaucratship Arbitration Committee Requests Enforcement
Content dispute resolution	Requests for comment Third opinion Dispute resolution noticeboard Biographies of living persons Conflict of interest External links Fringe theories Neutral point of view No original research Reliable sources
Other noticeboards and assistance	Regional notice boards Requests for help Category Asking questions Teahouse Help desk Reference desk Adopt-a-user Copyright assistance Copyright investigations Text problems Media questions Resource requests Mergers History mergers Moves Page importation Spam Blacklist Whitelist Bots Education General sanctions Editor sanctions Long-term abuse
Deletion discussions	Guide Admin Today Articles Templates Files Categories Redirects Miscellany Speedy Proposed BLP Review Undeletion Arguments to avoid Arguments to make Article Rescue
Elections and voting	Requests for comment (meta) Wikimedia Foundation elections WP Democracy Milestones
Directories, indexes, and summaries	Departments Edit summary legend Editor's index Essays FAQs Glossary Abbreviations Help Manual of Style Simplified Rules Five pillars Policies Guidelines Shortcuts Templates Citation templates Tips Today Tools Wiki markup
Media Category Templates

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