Notice: file_put_contents(): Write of 461750 bytes failed with errno=28 No space left on device in /opt/frankenphp/design.onmedianet.com/app/src/Arsae/CacheManager.php on line 36

Warning: http_response_code(): Cannot set response code - headers already sent (output started at /opt/frankenphp/design.onmedianet.com/app/src/Arsae/CacheManager.php:36) in /opt/frankenphp/design.onmedianet.com/app/src/Models/Response.php on line 17

Warning: Cannot modify header information - headers already sent by (output started at /opt/frankenphp/design.onmedianet.com/app/src/Arsae/CacheManager.php:36) in /opt/frankenphp/design.onmedianet.com/app/src/Models/Response.php on line 20
Wikipedia:Deletion review - Wikipedia Jump to content

Wikipedia:Deletion review

From Wikipedia, the free encyclopedia

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

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

Purpose

Deletion review may be used:

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

Deletion review should not be used:

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

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

Instructions

Before listing a review request, please:

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

Steps to list a new deletion review

 
1.

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

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

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

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

For nominations to overturn and delete a page previously kept, attach <noinclude>{{Delrev|date=2025 October 12}}</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 October 12}}</noinclude>
  • If the deletion discussion's subpage name is different from the deletion review's section header, then use <noinclude>{{Delrevxfd|date=2025 October 12|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 "procedural close".
Template:Authority control (arts) (talk|edit|history|logs|links|watch) (XfD|restore)

Per User_talk:Vanderwaalforces#Template:Authority_control_(arts), there was never really a consensus to merge here. * Pppery * it has begun... 22:59, 10 October 2025 (UTC)[reply]

  • Vacate BADNAC No way that shows a clear enough consensus for a NAC--I'd argue it hadn't reached consensus at all, so either an admin reclose or relist would both be fine. Jclemens (talk) 05:13, 11 October 2025 (UTC)[reply]
  • Meh I don’t agree that this is a badnac. Some XFDs have to operate in an environment with nacs because there are simply no admins interested in that area who understand it well enough to interpret those arguments. That said it, despite being open two months, I wouldn’t like to have to find a consensus there - but see my previous comment. The argument that we are removing a redundancy has some attraction to me though so I’m firmly in the meh camp. Spartaz Humbug! 10:03, 11 October 2025 (UTC)[reply]
    While that claim was definitely true of TfD in the past, these days TfD has at least 3 active regular admin closers and most discussions are closed by admins. * Pppery * it has begun... 22:12, 11 October 2025 (UTC)[reply]
  • Endorse the outcome, though it would have probably been better to be left to an administrator. Policy-based votes show a rough consensus to replace, considering the main “keep” argument is that it would take a considerable effort to replace the thousands of instances across Wikipedia. The closer correctly gave that argument less weight as there is no deadline to complete this task. Frank Anchor 14:40, 11 October 2025 (UTC)[reply]
  • Overturn to no consensus, or re-open There was never really an explanation of the technical merit of merging. Put the other way, what technical debt or problem is incurred leaving it in place as a shortcut? I wouldn't readily dismiss the argument that a substantial number of edits are required on a merge either; that's not determinative, but it's a relevant consideration. Local Variable (talk) 04:53, 12 October 2025 (UTC)[reply]
The following is an archived debate of the deletion review of the page above. Please do not modify it.
Battle of Vinland (talk|edit|history|logs|links|watch) (XfD|restore)

Was not originally part of the deletion discussion, but added late into the discussion. Open to recreation instead with different contents. This was an dab page to two pages that both redirected to Vinland. A battle in Vinland is already specified at these points in the Vinland article. The existence of these sentences where never brought up in the deletion discussion.

Saga of the greenlanders: "The explorers were then attacked in force, but managed to survive with only minor casualties by retreating to a well-chosen defensive position, a short distance from their base. One of the local people picked up an iron axe, tried it, and threw it away." This is also mentioned in chapter 6 of Saga of the greenlanders, https://www.snerpa.is/net/isl/graens.htm , in Icelandic. I was also able to find another battle in chapter 4, although that one was started with an ambush by the explorers.

Saga of Erik the Red: "One day, the local traders were frightened by the sudden arrival of the Greenlanders' bull, and they stayed away for three weeks. They then attacked in force, but the explorers managed to survive with only minor casualties, by retreating inland to a defensive position, a short distance from their camp." This is also mentioned in chapter 11 of Saga of Erik the Red, https://www.snerpa.is/net/isl/eirik.htm , in Icelandic

My proposal is to have the page as an redirect to Vinland#The Vinland Sagas, which is the parent chapter for both of the quotes. Snævar (talk) 00:43, 10 October 2025 (UTC)[reply]

 Done -- Tavix (talk) 01:57, 10 October 2025 (UTC)[reply]
The above is an archive of the deletion review of the page listed in the heading. Please do not modify it.
File:Burj Khalifa logo.svg (talk|edit|history|logs|links|watch) (XfD|restore)

Discussed with deleting admin. I believe the there was a significant doubt in the freedom of the file, brought by Altenmann. The precise integration of the tower silhouette and bilingual lettering may reflect a degree of creative authorship (unique layout, proportions, negative space, etc). Whilst Arabic calligraphy isn't protected, constraining it to a space and adjusting it in a way is, in my opinion. Either way, this is a borderline case, and per WP:NOCONSENSUS we should err on the side of caution. —Matrix ping mewhen u reply (t? - c) 19:18, 9 October 2025 (UTC)[reply]

  • Endorse keep closure. The closing administrator closed on the strength of arguments and most importantly clear US Copyright Office policy, which the nominator here has disregarded in favor of an appeal to aesthetics. The closing administrator mentioned following the precautionary principle, which requires significant doubt to kick in (note also that this is a higher standard than is required as it is a may not a must under the discussion of WP:PRPR at WP:NOCONSENSUS). IronGargoyle (talk) 20:36, 9 October 2025 (UTC)[reply]
  • Endorse, the keep argument was clear as to why this is PD in the US, and is correct. The "tower" logo is text arranged in a simple geometric shape (a triangle), and the US Copyright Office has been very clear that things like that are not eligible for copyright. Seraphimblade Talk to me 22:36, 9 October 2025 (UTC)[reply]
    @IronGargoyle and Seraphimblade: Calling this a "simple geometric shape" is dubious at best. The USCO text linked by Cryptic reads:

    Pictorial or graphic elements that are incorporated into uncopyrightable characters or used to represent an entire letter or number may be registrable. Examples include original pictorial art that forms the entire body or shape of the typeface characters, such as a representation of an oak tree, a rose, or a giraffe that is depicted in the shape of a particular letter

    Looking at File:Burj Khalifa.jpg, we can see the tower isn't a triangle. It is a essentially bunch of bundled tubes. The logo reflects this - if you look very carefully, the logo fans out in bumps, which reflects the towers real design. Whilst the Arabic text isn't copyrightable, constraining it in this way is copyrightable, or at least makes this a borderline call in which case we should err in caution. —Matrix ping mewhen u reply (t? - c) 17:25, 10 October 2025 (UTC)[reply]
    It is not more stylized than the Best Western crown, and that was found ineligible. Sorry, but I stand by my assessment. Seraphimblade Talk to me 19:29, 10 October 2025 (UTC)[reply]
    Agree with Seraphimblade about comparable ineligible logos. I also see no correspondence between the "bundled tubes" of the real Burj Khalifa and the edges of the triangle in the logo. Using Arabic characters to form a triangle is naturally going to produce edge lines which are not perfectly smooth, but this doesn't appear to be intentional. IronGargoyle (talk) 21:17, 11 October 2025 (UTC)[reply]
  • Calligraphy, even intricate calligraphy, is specifically ineligible for copyright in the US. Artistic elements which are not integral to the calligraphy may be copyrightable; but an isosceles triangle with two slightly curved sides is not. The guidelines published by the United States Copyright Office on the subject are in sections 906.1 and 906.4 of this document.
    I do agree with the nominator that we're often too liberal in deciding whether something's PD-simple when we really should only be making that call when there's no realistic chance a judge might disagree. I have no problem making that call here. In contrast, the flame outline of File:Al Jazeera Calligraphy.svg, which was raised in the FFD (and is visible, albeit in a small rendering, here), might or might not be determined to be copyrightable, so it's reasonable for us to treat it as copyrighted and usable only under our stricter non-free use standards. —Cryptic 01:13, 10 October 2025 (UTC)[reply]
The following is an archived debate of the deletion review of the page above. Please do not modify it.
List of albums containing a hidden track (talk|edit|history|logs|links|watch) (XfD|restore)

Covers the listed article and its 29 related pages. The AfD was closed before significant improvements to pages A and B could be discussed. In post-closure conversation, the closer stated, "I disagree that notability alone should determine inclusion...Consensus was that while the subject of hidden tracks was certainly notable...no sourcing would overcome the consensus that the list itself is unencyclopedic." Respectfully, this interpretation seems to contradict WP:NLIST. Furthermore, after a list of potential sources was identified to meet NLIST, there were an equal number of recommendations to keep and delete. While opinions are not votes, this suggests that there was no consensus that this topic was not encyclopedic. Also, all of the articles included in this AFD were not tagged, meaning involved editors may not have been notified of the AfD per proceedure.Rublamb (talk) 15:02, 9 October 2025 (UTC)[reply]

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

Since the last deletion discussion in 2018, Lopez has received significant coverage, most recently due to the SEC investigating him (CBS News and NYMag for starters) for running a Ponzi scheme. Nighfidelity (talk) 21:42, 7 October 2025 (UTC)[reply]

Go to WP:REFUND and request draftification. Use WP:AfC to improve the draft with your new sources. Submit the draft to see if an AfC reviewer agrees.
Why did you come here to Deletion Review?
-SmokeyJoe (talk) 21:49, 7 October 2025 (UTC)[reply]

AccesRail (closed)

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

There has been significant coverage of AccesRail's air-rail programme in multiple partner airlines and news articles, which serves as secondary sources of the subject. Examples include [1] [2] [3] [4] [5]— Preceding unsigned comment added by Miklcct (talkcontribs) 14:46, 7 October 2025 (UTC)[reply]

Wrong forum. Endorse the 2020 AfD as properly run and closed. Send the applicant to WP:AfC, but first read WP:CORP and WP:THREE. DRV is not for giving advice on sources. SmokeyJoe (talk) 21:38, 7 October 2025 (UTC)[reply]
The above is an archive of the deletion review of the page listed in the heading. Please do not modify it.
The following is an archived debate of the deletion review of the page above. Please do not modify it.
Josh Wilbur (talk|edit|history|logs|links|watch) (XfD|restore)
Text generated by a large language model (LLM) or similar tool has been collapsed per relevant Wikipedia guidelines. LLM-generated arguments should be excluded from assessments of consensus.
The following discussion has been closed. Please do not modify it.

The article “Josh Wilbur” was deleted in an AfD in 2018. The deletion rested on objections about lack of notability and uncertainty over whether he personally won a Grammy. Since then, independent, verifiable new evidence has surfaced that directly addresses those objections. I respectfully request that this deletion be reviewed under Wikipedia:Deletion review, and that the page be restored or userfied so it may be rebuilt using reliable sources.

Evidence & Argument

Grammy recognition now confirmed The official Recording Academy website lists Josh Wilbur as a Grammy artist/winner: → https://grammy.com/artists/josh-wilbur/7728 Trade/press credits on major releases Billboard credits him as producer on Lamb of God – Resolution: https://www.billboard.com/music/music-news/allbum-review-lamb-of-god-resolution-1067149/ Billboard interview mentions his ongoing role with Lamb of God: https://www.billboard.com/music/rock/lamb-of-god-vii-randy-blythe-interview-6568867/ In Wikipedia itself, the Wrath (Lamb of God album) page lists Josh Wilbur as producer: https://en.wikipedia.org/wiki/Wrath_%28Lamb_of_God_album%29 The The Order of Things album page also credits him: https://en.wikipedia.org/wiki/The_Order_of_Things_%28album%29 Biographical / industry profiles NAMM Oral History: profiles Wilbur as a significant recording engineer: https://www.namm.org/library/oral-history/josh-wilbur URM Podcast EP 293: interview with Wilbur discussing his career, philosophy, credits: https://urm.academy/urmpc293-josh-wilbur/ Genelec “One on One” interview: refers to him as a “Grammy Award-Winning Producer” and discusses his studio approach: https://www.genelec.com/-/grammy-award-winning-producer-josh-wilbur-dials-into-the-8351s

How this evidence addresses the 2018 objections

The key 2018 objection — whether he had personally won a Grammy — is now clearly resolved by the Recording Academy listing. His producer/engineer credits on high-profile albums documented in Billboard and internal Wikipedia pages show he is not a peripheral or trivial contributor. The biographical sources give credible third-party narrative around his career, not just bare credit listings. Collectively, this meets WP:MUSICBIO and the general notability standard: he has substantial coverage and verifiable contributions in the music industry.

Proposed plan if restored / userfied

If the page is restored or moved to user space, I will expand it using the above sources into sections such as: Early life & education Career highlights & major credits Awards & recognition Selected discography / engineering credits Media coverage & interviews This prevents it reverting to a short stub and ensures it addresses earlier criticism about lack of depth.

Anticipated objections & responses

Objection Policy-based response “He’s just a behind-the-scenes producer, not a solo artist — not notable.” Under WP:MUSICBIO, significant producers/engineers with documented credits on major works qualify. His roles are central (not peripheral). “We already had consensus in 2018; no need to reopen.” DRV policy explicitly allows review when new, relevant evidence arises post-deletion. That is exactly what this case presents. “This seems promotional / PR fluff.” The cited sources (Billboard, NAMM, URM, Genelec) are third-party, editorial, and independent. They are not self-published press releases. “I don’t trust the Grammy listing.” The Recording Academy is the authoritative body on Grammy awards. Its own site is a primary source for confirming winners/nominees.

Call to action & closing

I respectfully ask that the Deletion Review community reconsider the 2018 decision in light of this new, verifiable evidence. Please restore or userfy the “Josh Wilbur” title so we may reconstruct a fully sourced article. Thank you for your time and evaluation. — Michele Lu — Preceding unsigned comment added by Michelelu (talkcontribs) 17:50, 6 October 2025 (UTC)[reply]

The above is an archive of the deletion review of the page listed in the heading. Please do not modify it.
  • Tonal whiplashReclose as delete. I closed the AfD in the belief that a reasonable alternative to deletion existed: community opinion here has made it clear that that ATD has less support and more barriers than I believed, and that the appropriate closure would have been to delete. As it is within my discretion to amend my own closure, and nobody else has explicitly supported it here, I'm going to do so. Vanamonde93 (talk) 16:23, 6 October 2025 (UTC) Vanamonde93 (talk) 16:23, 6 October 2025 (UTC)[reply]
The following is an archived debate of the deletion review of the page above. Please do not modify it.
Tonal whiplash (talk|edit|history|logs|links|watch) (XfD|restore)

Listed result was to create a Wiktionary page and to target a soft redirect there. However, this was only discussed as a possibility, and as far as I know no action had/has been taken to create such a target (wikt:Tonal whiplash does not currently exist). The actual votes in the discussion called for deletion of the existing page regardless of what may or may not go down at Wiktionary, and that the page still exists, seemingly untouched since the end of the discussion, reads as the opposite of that consensus to me. I think the result should've been deletion with the possibility of recreation as a redirect, not to leave a consensus-delete page sitting around and waiting for a redirect target that may never exist. QuietHere (talk | contributions) 16:29, 5 October 2025 (UTC)[reply]

  • Unless things have changed recently, Wiktionary categorically rejects transwikification of pages from Wikipedia, so this wasn't a valid closing option to begin with. If at some point, someone wants to create wikt:tonal whiplash (note capitalization; it makes it be a different page over there) with the help of what used to be here, we can provide the deleted content and attribution to them. —Cryptic 16:47, 5 October 2025 (UTC)[reply]
  • @QuietHere: You know, you could have discussed this with me...of the four participants, two clearly preferred a wiktionary entry, and your objection was a practical one, that would be obviated by the creation of a wiktionary entry. As such I stand by my reading of consensus as favoring a wiktionary entry over deletion. But I wasn't aware of a prohibition against transwikification, and we cannot redirect without a target. If @ReaderofthePack: or @Metallurgist: don't wish to create a wiktionary entry, I would delete this page. A full-fledged DRV is not a good use of time. Vanamonde93 (talk) 16:59, 5 October 2025 (UTC)[reply]
    @Vanamonde93 apologies if it was inappropriate for me to not have contacted you first. I don't believe I've ever participated in a deletion review, so I'm unfamiliar with the formalities. However, I stand by my assessment of the discussion, and I'm not sure why this review is such a big deal. I hold no ill will toward you for your judgment. It's not an unreasonable assessment of the discussion, just not the best immediate solution for the situation. QuietHere (talk | contributions) 17:21, 5 October 2025 (UTC)[reply]
    @QuietHere: It isn't a big deal, and if you haven't participated before it's not an unreasonable thing to do. But it's typically seven-day discussion soliciting opinions from the community: so if the matter can be handled by discussing it with the administrator, that is preferable from the standpoint of community time.
    We're in agreement here that the continued existence of the page in mainspace isn't ideal. My proposed solution is to allow the two editors I pinged, the ones who supported a wiktionary entry, a little time to create such an entry, to redirect this title to that entry if it is created, and to delete it otherwise, as I believe that would follow from the AfD result absent a wiktionary entry. Is that agreeable to you? Vanamonde93 (talk) 18:03, 5 October 2025 (UTC)[reply]
    I would support overturn and deletion. I did speculate on using wiktionary, but that was not my !v. I would think DRV is the appropriate venue for this and is not meant to be a slight at a closer. Putting such a concern on the closer talk page is far less public. Metallurgist (talk) 19:22, 5 October 2025 (UTC)[reply]
    Altho I can see how my commentary could be construed as supporting that. It was essentially delete and someone can put it there. I think reclosing this as delete and if someone wants to create it on wikt, they can, or ask an admin to get the info later. Or save it. Metallurgist (talk) 19:24, 5 October 2025 (UTC)[reply]
  • Maybe draftify? That would honor the clear consensus against keeping the page in mainspace, while allowing the content to still be referred to for creating a Wiktionary entry, which is presumably why it's still there. A soft redirect can be created whenever the entry is ready. Left guide (talk) 08:53, 6 October 2025 (UTC)[reply]
  • Overturn and delete We are concerned with this project's policies for inclusion, not other projects. I am concerned by a closing rationale like this, because it's a tacit endorsement that the page *is appropriate* for wict, but that will depend on that project's criteria, of which I know very little. If a user gets into trouble over there for creating bad entries, it'd be no answer to say the folks at enwiki did it by consensus. In the interests of inter-project harmony, I don't think we should be debating its suitability for wict on enwiki. It's entirely up to them. Local Variable (talk) 12:15, 6 October 2025 (UTC)[reply]
Overturn (to delete) per Cryptic. The transwiki won’t happen, and so the close devolves to “keep”, which is contrary to the discussion. If someone wants to try to transwiki, or to put the content to any worthwhile use, allow draftification. SmokeyJoe (talk) 13:49, 6 October 2025 (UTC)[reply]
The above is an archive of the deletion review of the page listed in the heading. Please do not modify it.


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

Please can I have the Extra Credits article restored into my personal draft space? The article, in the form it was deleted, was awful but there was at least one better version in the history. I found quite enough valid sources to make a decent short article about it (slightly more than a stub) and having the old article and it's history, poor though most of it was, would make that easier than starting from scratch even if the new article would need to actually follow the sources and not bear much resemblance to old one. Thanks. DanielRigal (talk) 11:12, 2 October 2025 (UTC)[reply]

I see no reason to oppose this request, especially when coming from a respected, longstanding editor such as you. But why didn't you simply ask the closing admin to do this before bringing it here? I doubt Salvio giuliano would deny this request. If I see no objection here, I'll restore to draft. Owen× 12:24, 2 October 2025 (UTC)[reply]
OwenX, no objection at all. I would have done so myself if asked, and only refrained because this DRV had already been started. —  Salvio giuliano 12:27, 2 October 2025 (UTC)[reply]
The above is an archive of the deletion review of the page listed in the heading. Please do not modify it.
The following is an archived debate of the deletion review of the page above. Please do not modify it.
File:Haldhar Nag Kutir before renovation, in June 2005.png (talk|edit|history|logs|links|watch) (article|XfD|restore)

This image was deleted because it was placed in an inappropriate location. In this revision, I have placed it in the correct location. Please undelete it. Thyj (talk) 11:41, 2 October 2025 (UTC)[reply]

  • Dismiss the appeal as a misrepresentation of the facts. The image was deleted per WP:NFCC#8. The misplacing of the image in a gallery was only brought up as an aside, and was not the reason for the deletion. Will reconsider if the appellant amends their appeal to state the facts honestly. Owen× 12:06, 2 October 2025 (UTC)[reply]
  • Endorse the fact it was in a gallery was only a subsidiary point. The main problem was the fact it's not contextually necessary, and that's plainly correct, and I don't think it's even arguably wrong. It can be adequately explained in text. I don't think it's ideal to direct link to a copyrighted photograph as a reference either, per the external link policy, the reference should be to the web page it's hosted on. Local Variable (talk) 14:29, 2 October 2025 (UTC)[reply]
  • The non-free-use rationale was invalid too; it was largely cut-and-pasted from a rationale for a website screenshot. —Cryptic 00:48, 3 October 2025 (UTC)[reply]
  • So that non-admins can participate: Do we not have a free picture of the location from before the renovation? Can someone point me to the image in question? It does seem within the scope of NFCC#8 if no free image exists. Text, or a line drawing, can only do so much if the place is notable enough to warrant an article (which seems questionable to me, but whatever), we should provide the context we can. If this were, say, the White House, and there were no free version from before a major renovation, I'd think we'd allow a non-free version to provide the needed context. But I'm willing to be educated about why NFCC#8 is an issue. Clearly the "Before" part is described in reasonable detail in the article. I'll note I also cannot see the non-free rational, so I can't judge that... Hobit (talk) 03:24, 5 October 2025 (UTC)[reply]
    • I've temp-undeleted the file description page only. The image was from sometime during the slow zoom-in on the white building starting about a half second after the timestamp linked to in the given source. —Cryptic 04:01, 5 October 2025 (UTC)[reply]
  • The provided justification for no free use is poor (the renovation should be mentioned too), but otherwise it appears to meet all of NFCC including #8 (per my comments above). overturn This is exactly when we should be using non-free material. It's not replaceable by text, no free version exists, and I struggle to see commercial impact. Those arguing otherwise need to explain more than just saying "NFCC#8". If the building is notable enough to have an article, it's not unreasonable for the history of the building to be covered (which it is). And showing what it looked like before a major renovation seems important--text just isn't going to cut it. Nor a line drawing. Hobit (talk) 03:44, 7 October 2025 (UTC)[reply]
  • Endorse We should only be using non-free material if they genuinely add to the reader's knowledge; this screenshot is of such poor quality that it does not. Black Kite (talk) 21:08, 8 October 2025 (UTC)[reply]
  • Endorse: I'm pretty much in agreement with what Cryptic posted above in that I don't see how the inclusion of this particular before renovation screenshot/image significantly improves the reader's understanding of the building's appearance to extent that not seeing it would be detrimental of the understanding per WP:NFC#CS. I also have concerns about the quality of the three sources cited in support of the content describing the building prior to its renovation: one is to a YouTube video, one is to a photo and one is to a non-English article about the building. Citing the video might be OK since it doesn't appear to be a copyvio per WP:YOUTUBE, but the cited photo has zero value as a reliable source (at least in my opinion); moreover, according to Google Translate, the cited non-English article doesn't really meet WP:RSCONTEXT for the content about the building's appearance and doesn't seem to be anywhere near enough to meet WP:NFCC#8 on its own. -- Marchjuly (talk) 00:50, 9 October 2025 (UTC)[reply]
The above is an archive of the deletion review of the page listed in the heading. Please do not modify it.
The following is an archived debate of the deletion review of the page above. Please do not modify it.
Electroimpact (talk|edit|history|logs|links|watch) (XfD|restore)

The Electroimpact article was deleted on March 31, 2025 after an AfD discussion concluded that it lacked significant, non-local coverage and did not meet WP:ORGCRIT.

Since that time, a completely rewritten draft has been prepared using only independent, reliable sources from national news and aerospace industry publications. The draft addresses both achievements and controversies in a neutral tone, resolving previous concerns about neutrality and conflict of interest.

The draft can be reviewed here: User:Pollluxo/sandbox

Independent sources now establishing notability:

  • Reuters – National coverage of DOJ settlement.
  • Forbes – Independent company profile.
  • SME.org – Aerospace industry coverage.
  • KNKX/NPR affiliate – Context on Boeing/Airbus rivalry.
  • CompositesWorld – Reporting on Electroimpact's role in Rocket Lab’s Neutron rocket project.
  • The Columbian – Reporting on workforce scale and operations.

With these sources, the article now clearly meets WP:ORGCRIT and demonstrates broad, non-local coverage. I am requesting that the deletion decision be overturned or that the page be restored to allow recreation using the new draft. Pollluxo (talk) 00:36, 30 September 2025 (UTC)[reply]

  • Then go ahead and create the article if you believe it is “ready.” The title is not WP:SALTed, so any user in good standing can re-create it at any time, though it could be subject to another AFD discussion. I will not evaluate the references you provided because DRV is not a content-evaluation forum. We can have a procedural close on this discussion. Frank Anchor 01:59, 30 September 2025 (UTC)[reply]
  • Comment I note the article and DRV statement seem LLM generated. But as Frank said there is nothing actionable at DRV, the editor can send their AI slop back into mainspace which will likely be deleted again. Jumpytoo Talk 05:05, 30 September 2025 (UTC)[reply]
The above is an archive of the deletion review of the page listed in the heading. Please do not modify it.
Archives, by year and month
Year Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2025 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2024 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2023 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2022 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2021 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2020 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2019 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2018 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2017 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2016 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2015 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2014 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2013 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2012 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2011 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2010 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2009 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2008 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2007 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2006 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec