Wikipedia:Deletion review
Deletion discussions |
---|
|
Articles |
Templates and modules |
Files |
Categories |
Redirects |
Miscellany |
Speedy deletion |
Proposed deletion |
Formal review processes |
---|
|
For RfCs, community discussions, and to review closes of other reviews: |
Administrators' noticeboard |
In bot-related matters: |
|
Discussion about closes prior to closing: |
Deletion review (DRV) is for reviewing speedy deletions and outcomes of deletion discussions. This includes appeals to delete pages kept after a prior discussion.
If you are considering a request for a deletion review, please read the "Purpose" section below to make sure that is what you wish to do. Then, follow the instructions below.
Purpose
Deletion review may be used:
- if someone believes the closer of a deletion discussion interpreted the consensus incorrectly;
- if a speedy deletion was done outside of the criteria or is otherwise disputed;
- if 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, 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:
- 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
If your request is completely non-controversial (e.g., restoring an article deleted with a PROD, restoring an image deleted for lack of adequate licensing information, asking that the history be emailed to you, etc), please use Wikipedia:Requests for undeletion instead. |
1. |
{{subst:drv2 |page=File:Foo.png |xfd_page=Wikipedia:Files for deletion/2009 February 19#Foo.png |article=Foo |reason= }} ~~~~ |
2. |
Inform the editor who closed the deletion discussion by adding the following on their user talk page:
|
3. |
For nominations to overturn and delete a page previously kept, attach |
4. |
Leave notice of the deletion review outside of and above the original deletion discussion:
|
Commenting in a deletion review
Any editor may express their opinion about an article or file being considered for deletion review. In the deletion review discussion, please type one of the following opinions preceded by an asterisk (*) and surrounded by three apostrophes (''') on either side. If you have additional thoughts to share, you may type this after the opinion. Place four tildes (~~~~) at the end of your entry, which should be placed below the entries of any previous editors:
- Endorse the original closing decision; or
- Relist on the relevant deletion forum (usually Articles for deletion); or
- List, if the page was speedy deleted outside of the established criteria and you believe it needs a full discussion at the appropriate forum to decide if it should be deleted; or
- Overturn the original decision and optionally an (action) per the Guide to deletion. For a keep decision, the default action associated with overturning is delete and vice versa. If an editor desires some action other than the default, they should make this clear; or
- Allow recreation of the page if new information is presented and deemed sufficient to permit recreation.
- Some consider it a courtesy, to other DRV participants, to indicate your prior involvements with the deletion discussion or the topic.
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.
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 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".
20 May 2024
Shane and Friends
This podcast page definitely deserves to be restored. It was one of the biggest podcasts of the 2010s. How could it possible not meet notability standards? Nokia621 (talk) 18:28, 20 May 2024 (UTC)
Category:Estonian numismatists
This was closed as "merge all" but there was no actual consensus to merge all (as opposed to merging only the ones that still have one member). Discussion with the closer at Wikipedia talk:Categories for discussion/Working has failed to resolve matters. * Pppery * it has begun... 16:41, 20 May 2024 (UTC)
Category:Roman villas in Germany
This was closed as "merge" but there was no actual consensus to merge. Neither side provided any clear guidelines to back up their position, and the numbers were equal. This should have been a "no consensus" * Pppery * it has begun... 16:41, 20 May 2024 (UTC)
- Pppery, for this one, the keep !votes referred (implicitly) to the deprecated WP:SMALLCAT guideline. The nom referred to Wikipedia:Categorization by saying it's not useful for navigation, which I felt was reasonable enough. — Qwerfjkltalk 17:26, 20 May 2024 (UTC)
- "Useful for navigation" seems like a wholly subjective term to me, not a basis in which one can declare one side or the other right. * Pppery * it has begun... 17:34, 20 May 2024 (UTC)
19 May 2024
1996 Abakan Ilyushin Il-76 crash
Whilst not a contentious topic, I believe that the the non-admin closer closed the discussion with insufficient evidence and rationale. At first, the closer did not provide a rationale and upon asking for one [1], they stated "The noms contention that this was a "run of the mill event" is not accepted" [2]. Upon inquiring even further pointing out that I had cited multiple policy-based guidelines, they simply stated that they had nothing to else add. Whilst there were no votes supporting a delete, I believe that, either, at the very least, the discussion be relisted to provide a clearer consensus and be closed by a more experienced editor or admin, or the result be overturned as I believe that the closer did not correctly interpret the results. Aviationwikiflight (talk) 10:06, 19 May 2024 (UTC)
- Endorse There is unanimous consensus to keep. Skyshiftertalk 10:25, 19 May 2024 (UTC)
- Per WP:CLOSEAFD, Consensus is not based on a tally of votes, but on reasonable, logical, policy-based arguments. The strength of the arguments given depends more than the number of votes cast on either side. Aviationwikiflight (talk) 10:40, 19 May 2024 (UTC)
- Comment. I closed this. There were no delete votes in this second AfD nor the first AfD which can be found here Wikipedia:Articles for deletion/RA-78804. Desertarun (talk) 10:38, 19 May 2024 (UTC)
- This is slightly misleading. Although there weren't any delete votes in the first AfD, there were merge votes. [1] Aviationwikiflight (talk) 10:44, 19 May 2024 (UTC)
- And you ignored the first AfD result and renominated it for deletion again...The first AfD closed less than a month ago. Desertarun (talk) 10:49, 19 May 2024 (UTC)
- I agree that that was my fault for renominating it as I didn't know that a renomination should normally take place after six months.
- At the same time, you closing the first discussion as keep with four in favour (including a sock) vs three favouring a merge is contentious as both sides provided strong arguments. Aviationwikiflight (talk) 11:09, 19 May 2024 (UTC)
- And you ignored the first AfD result and renominated it for deletion again...The first AfD closed less than a month ago. Desertarun (talk) 10:49, 19 May 2024 (UTC)
- This is slightly misleading. Although there weren't any delete votes in the first AfD, there were merge votes. [1] Aviationwikiflight (talk) 10:44, 19 May 2024 (UTC)
- Overturn This AFD was not properly closed and the rationale for closing is not valid. - UtherSRG (talk) 11:27, 19 May 2024 (UTC)
- Weak endorse. Firstly, renominating within a month of the previous Keep AfD puts the appellant on weak footing here. I believe them when they say it was an honest mistake, but in cases of rapid renomination of a substantially identical page, I think a closer may look at the views in the previous XfD, and determine consensus based on both (or all, if more than two) AfDs combined. This is the natural and most effective way to discourage the type of tendentious litigation we see in some perennially nominated pages. In our case, this would lead to a clear consensus to keep.
- Secondly, while no policy forbids it, I find it in poor taste for the same closer, admin or not, to close two subsequent XfDs for the same page, especially in such rapid succession. I'm not saying Desertarun has any bias here, but the appearance of impartiality, and the opportunity to give another closer a chance to examine consensus, are also important. Looking at the second, appealed AfD by itself, I agree with the appellant that the Keep views are exceptionally weak, and do little to refute the nominator's P&G-based concern. I would advise the non-admin closer to either relist such marginal cases, or to leave them for an admin to close. Owen× ☎ 12:51, 19 May 2024 (UTC)
- Having closed a discussion, there will be a bias to close the same discussion repeated, the same way, especially if there is no substantial new information or arguments that make the second close a reevaluation of the first. This makes the closer INVOLVED forever, or at least for a long time, on similar questions on that topic. If WP:INVOLVED doesn’t say this, it should. SmokeyJoe (talk) 00:02, 20 May 2024 (UTC)
- I fully agree, hence the weakness of my endorsement. Owen× ☎ 13:10, 20 May 2024 (UTC)
- It would be nigh on impossible for the admins that close many AfDs per week/month to remember everything they'd previously closed. So changing WP:Involved as mooted would be giving a stick to disgruntled users. Desertarun (talk) 14:27, 20 May 2024 (UTC)
- Having closed a discussion, there will be a bias to close the same discussion repeated, the same way, especially if there is no substantial new information or arguments that make the second close a reevaluation of the first. This makes the closer INVOLVED forever, or at least for a long time, on similar questions on that topic. If WP:INVOLVED doesn’t say this, it should. SmokeyJoe (talk) 00:02, 20 May 2024 (UTC)
- Endorse. There was a clear consensus to keep. Everything was done correctly. The closer stated that the nominator's rationale was "not accepted" (by consensus), which is fine. This is not a BADNAC, as the non-admin closer has not demonstrated a potential conflict of interest, or lack of impartiality, the outcome was not a close call or likely to be controversial, the non-admin has a lot of experience editing Wikipedia generally and has had much previous participation in deletion discussions, and the result did not require action by an administrator. Maybe something about this close could have been better but NACs don't have to be absolutely fabulous to stand, discussions don't have to be fabulous for NAC to be applicable when they're entirely one-sided and can't be closed any other way, and DRV is not about technicalities and not about through-expermentally workshopping could-have-been optimal closing statements and sharing thoughts about what ideal closes by which preferred closers would lead to our satisfaction.—Alalch E. 13:09, 19 May 2024 (UTC)
- I don't understand how the given rationale is fine. Saying that the result depended on one of my arguments not being accepted doesn't exactly make sense. In the discussion, I provided multiple policy based guidelines demonstrating why the article should be deleted. But because one of my arguments which was that the event was a run-of-the-mill was not accepted means that my entire argument is now baseless? Aviationwikiflight (talk) 13:31, 19 May 2024 (UTC)
- An AfD is not a formal debate. As consensus, not merely being right is needed to delete, your initiative to delete the article failed through a lack of consensus to do so. Since no one even !voted delete, but multiple people !voted keep, the outcome can not be "no consensus" and can only be "keep". Relisting would have been inappropriate as there was a normal level of participation and the comments were not "lacking arguments based on policy". An argument that the page is not WP:NOT, for example, is not an argument not based in policy in an AfD. An editor can ignore complaints that notability isn't met and say that the page is suitable for inclusion as being within scope, citing NOT, and that is a perfectly policy-based argument to keep. If you cite a guideline that says that events about "common, everyday, ordinary items" may not be notable, and someone says "no, this is not a common, everyday, ordinary item", that's a policy-based argument. Try with a more complete nomination next time that in addition to WP:LASTING also includes WP:INDEPTH and WP:GEOSCOPE, and explain why some sources may be unreliable and why those that are reliable lack in-depth coverage etc., and also explain how WP:GNG isn't met. —Alalch E. 14:08, 19 May 2024 (UTC)
- Consensus isn't determined based on the tally votes and by counting heads, but by looking at the strength of arguments and cited recorded consensus and on reasonable, logical, policy-based arguments.
- I too can also ignore the fact that the article was not WP:NOT and cite guidelines that it fails. That too is a policy-based argument against a keep.
- And just saying that the article should be kept because of the number of deaths is not a policy-based argument, nor is saying that an article should be kept because another one has less deaths. Arguing against someone saying that the article is not run-of-the-mill and demonstrating why it is run-of-the-mill is also a policy-based argument. If users do little to refute issues cited regarding policies and guidelines, where does that leave the result? Aviationwikiflight (talk) 14:41, 19 May 2024 (UTC)
- You said,
I too can also ignore the fact that the article was not WP:NOT and cite guidelines that it fails. That too is a policy-based argument against a keep.
That is correct, and indeed, no one here is claiming that your arguments are not based on policy or guidelines. The fact that no one refuted your argument does not, by itself, automatically turn your legitimate view into a supervote. Here at DRV, we often get appeals that essentially boil down to, "Everyone except me was wrong!". The problem with that is that even if true, that still leaves your opinion alone. We do not delete an article based on a single, contested opinion, except in the clear cases spelled out in WP:CSD. Owen× ☎ 14:56, 19 May 2024 (UTC)- I'm not trying to make my views equal to a supervote but the problem that I have is with the closing rationale since it is implying that the discussion was closed as keep because one of my arguments was not accepted even though there were plenty other of arguments. Aviationwikiflight (talk) 16:04, 19 May 2024 (UTC)
- The AfD was closed as a Keep because no one other than you suggested it not be kept. The fact that you're still arguing about it tells me you aren't clear on our basic principle of WP:CONSENSUS. Owen× ☎ 16:23, 19 May 2024 (UTC)
- I'm not trying to make my views equal to a supervote but the problem that I have is with the closing rationale since it is implying that the discussion was closed as keep because one of my arguments was not accepted even though there were plenty other of arguments. Aviationwikiflight (talk) 16:04, 19 May 2024 (UTC)
- You said,
- An AfD is not a formal debate. As consensus, not merely being right is needed to delete, your initiative to delete the article failed through a lack of consensus to do so. Since no one even !voted delete, but multiple people !voted keep, the outcome can not be "no consensus" and can only be "keep". Relisting would have been inappropriate as there was a normal level of participation and the comments were not "lacking arguments based on policy". An argument that the page is not WP:NOT, for example, is not an argument not based in policy in an AfD. An editor can ignore complaints that notability isn't met and say that the page is suitable for inclusion as being within scope, citing NOT, and that is a perfectly policy-based argument to keep. If you cite a guideline that says that events about "common, everyday, ordinary items" may not be notable, and someone says "no, this is not a common, everyday, ordinary item", that's a policy-based argument. Try with a more complete nomination next time that in addition to WP:LASTING also includes WP:INDEPTH and WP:GEOSCOPE, and explain why some sources may be unreliable and why those that are reliable lack in-depth coverage etc., and also explain how WP:GNG isn't met. —Alalch E. 14:08, 19 May 2024 (UTC)
- I don't understand how the given rationale is fine. Saying that the result depended on one of my arguments not being accepted doesn't exactly make sense. In the discussion, I provided multiple policy based guidelines demonstrating why the article should be deleted. But because one of my arguments which was that the event was a run-of-the-mill was not accepted means that my entire argument is now baseless? Aviationwikiflight (talk) 13:31, 19 May 2024 (UTC)
- Endorse per Alalch E. Perfectly fine NAC, entirely obvious consensus. Jclemens (talk) 16:13, 19 May 2024 (UTC)
- Endorse per Alalch E. No error in the close - also not a bad NAC. The nomination was based on WP:EVENT and Wikipedia:Run-of-the-mill. While WP:EVENT is a guideline, it is not, by itself an exclusion criteria - as a subject can still pass GNG and merit an article. WP:Run-of-the-mill is an essay. In this case, as GNG was not questioned. While passing GNG does not mean an article must be created, the question in an AFD is whether a stand-alone page should exist. Since the other participants all said that the subject was not an ordinary event (a policy-based argument), keep was the only appropriate outcome. --Enos733 (talk) 16:57, 19 May 2024 (UTC)
- Endorse completely normal AfD here, with complete consensus to keep. Furthermore I do not see any particular reason to delete which was ignored by the participants. SportingFlyer T·C 17:34, 19 May 2024 (UTC)
- Endorse as the correct reading of consensus to Keep. I would have !voted Keep on account of significant coverage of 23 lives lost, but DRV is not AFD round 3. Robert McClenon (talk) 20:37, 19 May 2024 (UTC)
- Endorse. WP:SLAP User:Aviationwikiflight for renominating too soon after an AfD consensus to not delete, and doing so without a better nomination that last time, noting that they !voted in the first AfD and therefore were aware of it. Desertarun (talk · contribs) should not be closing an AfD on the same topic twice, after closing once you are forever WP:INVOLVED in that topic. I would have requested speedy closure at WP:ANRFC, and !voted “speedy close as too soon after the AfD1 consensus to keep”. —SmokeyJoe (talk) 23:56, 19 May 2024 (UTC)
- No action I can not go as far as endorsing an WP:INVOLVED NAC, but this is the correct result. There was unanimous consensus (outside the nominator) to keep this article. Frank Anchor 10:19, 20 May 2024 (UTC)
18 May 2024
Paulin Basinga
I don't believe this closure was appropriate. I provided legitimate points to clarify the raised issues to keep the page, there are as many "Keep" same as "Delete". None of the votes for "delete" replied to the comments. I recommend this AFD be reopened. 12eeWikiUser (talk) 09:53, 18 May 2024 (UTC)
- Speedy endorse as a bad-faith appeal. The appellant says,
there are as many "Keep" same as "Delete"
. That is an outright lie. Even going by nose count alone, there are two Keeps and four Deletes. We could go into the weakness of those two Keep arguments, but I don't think DRV should entertain dishonest appeals even if they have merit, which this one doesn't. Owen× ☎ 10:19, 18 May 2024 (UTC)
- Endorse clear consensus to delete. However I do not believe this DRV was made in bad faith. Frank Anchor 17:00, 18 May 2024 (UTC)
- Endorse - The only possible closure. There is a strange question about how and whether to Assume Good Faith. Is the appellant misstating the numbers of Keeps and Deletes, or is the appellant unable to count, which is only a competency issue? Robert McClenon (talk) 23:44, 18 May 2024 (UTC)
- (edit conflict) I think we've completely missed here. The close was absolutely correct based on the discussion, but I'm convinced we've deleted an article on a notable topic. I can't see the deleted article, so it's possible it was written promotionally, and some very experienced editors participated at this AfD, so I understand I'm arguing up hill here. Still, I did my own WP:BEFORE search and not only do I not see any promotional sources (the Nigerian ones I've found so far wouldn't count because they're interviews, but he's clearly being interviewed as an expert - and he worked in Nigeria, so it's not surprising that he'd be discussed there), I think he pretty clearly satisfies WP:NPROF with many published articles, many references to those articles in books, and international press coverage (probably routine). AfD is getting a lot more difficult as fewer people participate and we've always had issues with notability outside specific areas, especially with African topics. Perhaps the deleted article's not worth restoring, but I think he's absolutely notable enough to write an article on, so even if this is endorsed I have no problem if someone wants to write a new draft here. SportingFlyer T·C 23:54, 18 May 2024 (UTC)
- If anyone thinks he is notable, request draftication and follow to advice at WP:THREE. SmokeyJoe (talk) 04:57, 19 May 2024 (UTC)
- NPROF requires substantially more citations--by academics in academic RS--of the subject than would be seen for the average professor in their subfield, and for Dr Basinga I believe it is TOOSOON. He had one quite well-cited first-author paper, but NPROF C1 needs several extremely highly-cited papers. FWIW, I ran my Scopus metrics test on ~100 of his senior-research-position coauthors who had 15+ papers (to exclude those who are not in senior researcher/professor positions and thus not comparable for "average professor" purposes):
- Total citations: average: 5183, median: 2459, Basinga: 1385; Total papers: 125, 88, 36; h-index: 32, 28, 20; Top papers: #1: 766, 308, 372; #2: 380, 198, 158; #3: 280, 158, 68; #4: 205, 128, 62; #5: 174, 108, 54.
- As you can see, Dr Basinga is not well above the average professor in this high-citation-rate field (he publishes alongside the likes of Agnes Binagwaho, Megan B. Murray, and John Owusu Gyapong), so his notability needed to be assessed via GNG and that was also found lacking. In the course of running my test I did come across a few red-linked researchers whom I believe do qualify for pages through C1: Françoise Portaels (19364 citations, h-index 73), Susheela Singh (14609, 60), Janneke van de Wijgert (8715, 50), Sodiomon Sirima (7649, 50), Ayola Akim Adegnika (6833, 44), and Joanna Schellenberg (12180, 62), among others. JoelleJay (talk) 05:19, 19 May 2024 (UTC)
- The one time I think WP:NPROF might be satisfied... SportingFlyer T·C 07:41, 19 May 2024 (UTC)
- Thank you JoelleJay, I am now satisfied. I apologize for being too desperate for not deleting the page, I am happy to learn about NPROF test I did not know much on it. 12eeWikiUser (talk) 09:39, 20 May 2024 (UTC)
- Endorse. There was a consensus to delete for lack of notability and promotion.—Alalch E. 11:13, 19 May 2024 (UTC)
17 May 2024
Elephant population
This was speedy deleted out of process. The admin who performed the deletion has defended it at User talk:Pppery#Elephant population with their opinion on the merits of the redirect, and while I disagree with their opinion admins don't have the right to push the delete button because of their opinions but instead by must follow standard deletion procedures. * Pppery * it has begun... 23:07, 17 May 2024 (UTC)
- Overturn clear mis-application of G6. Not a “technical deletion” in any way, shape, or form. It can be taken to RFD if anyone desires. Frank Anchor 23:50, 17 May 2024 (UTC)
- Background - This page was created with the text;
It was recently confirmed by reliable source(s) that the elephant population has increased dramatically. This source says that the elephant population in Africa has tripled in the last six months and that if the population continues at this rate of increase, in two to five years the earth will be overrun by these giganic mamels. in that case, the source believes that elephant hunting will be legal soon. "it is only a matter of time," says source," Until congress will pass the law for elephant hunting and even promote this dangerous sport. Looks like my stash of ivory wont be illegal for long!" source exclaims with the sparkle of triumph in his eyes.
The Kato institute reports elephant populations have indeed increased despite liberal allegations. In a study by renowned palientologist Howard Berkman it was revealed that in the last 6 months there has been a 600% increase in the rural West African Great White Tusk elephant. For more see http://www.ericblumrich.com/thanks.html
- As this was clearly nonsense, it was tagged for speedy deletion. The proper procedure at the time would have been to just delete the page. However, there was instead a common (though very much 'out of process') practice of making indefinitely protected redirects, since these had the added 'benefit' of preventing recreation. As such, the page was redirected to Elephant and indefinitely protected "for now". That was clearly always meant to be a temporary solution, but got lost in the shuffle. Eighteen years later I removed the protection and deleted the page. To me, this seems like a standard G6 maintenance issue... finally implementing the proper / intended solution. Further, in the 18 years of its existence, no article on the site ever incorporated this redirect. It simply doesn't make sense to type 'Elephant population' to get to 'Elephant'. Thus, I feel the page should remain deleted... based on both 'benefit' to the encyclopedia AND process. --CBD 00:14, 18 May 2024 (UTC)
- Like your earlier claim that "we don't have redirects from <title> <word> to <title>", your implication that "no incoming links from articles" is a reason to delete is simply untrue. Close to two thirds of mainspace redirects have no incoming links, and this argument is explicitly called out at WP:RFD#KEEP #2. —Cryptic 00:40, 18 May 2024 (UTC)
- Overturn, and optionally List - Even if this had been done six months after the redirection, it would not have been a non-controversial maintenance deletion. The existence of a concept of non-controversial maintenance implies that there is also controversial maintenance, and this is controversial maintenance, and can be debated at RFD if there is a nomination. Robert McClenon (talk) 01:55, 18 May 2024 (UTC)
- Speedy undelete and list at XfD, which should be immediately done on any reasonable request by and user in good standing. If there is anything to debate, the forum for the debate is XfD. If the allegation is that an admin is repeatedly misusing speedy deletion, that’s another matter. —SmokeyJoe (talk) 13:33, 18 May 2024 (UTC)
- Overturn The cited text is fictitious and ludicrous, but because it can clearly be understood by a reasonable person to be exactly that... it's not nonsense. But nor does G6 apply. Great candidate for a non-speedy process. Jclemens (talk) 13:37, 18 May 2024 (UTC)
- Close with no action. What exactly is the remedy sought by the appellant here? I agree that G6 was incorrectly applied. But what do we gain by overturning it? A wiki search for "Elephant population" gives Elephant as the sixth result. This isn't a plausible typo, although after 18 years, it's clearly not a recently created one to fall under R3. Yes, it shouldn't have been summarily deleted out of process, and no, we don't need that redirect back just to be re-deleted at RfD. At most, I'd go for a half-hearted TROUTing of the deleting admin, along with a quiet Thank you for trying to save us the trouble of a pointless XfD, and get back to more important matters. Owen× ☎ 16:33, 18 May 2024 (UTC)
- The remedy sought is it to overturn the deletion, undelete the page, and allow anyone who wishes it nominate it at RfD to do so. I would have thought that was obvious. And I am not convinced this would have been deleted at RfD in the first place. This ends-justify-the-means reasoning is contrary to deletion policy, and you can't IAR around it either per WP:IARUNCOMMON since this logic appears to apply just as well to anything any admin personally thinks would likely be deleted at a deletion discussion, which is a common scenario. * Pppery * it has begun... 22:51, 18 May 2024 (UTC)
- Undelete and list at XfD puts the situation back on the track it should have been on, and provides a clear example to observers, and gives re-education to the admin misapplying G6. SmokeyJoe (talk) 23:32, 18 May 2024 (UTC)
- In Victor Hugo's last novel, Ninety-Three, a sailor risks his life to secure a loose cannon on deck, the cannon that he himself failed to secure earlier. The captain awards him a medal for his bravery, and then proceeds to execute him for dereliction of duty. My question is, must we revive this redirect just to kill it again? The G6 was wrong, and IAR doesn't apply here, but DRV is a content forum, not a disciplinary one. It seems pointless to retrace our steps just to end up where we started, and we're not here to educate anyone. We don't know what a future RfD would decide, but we don't need to leave this for RfD. Policy gives DRV the authority to adjudicate the matter, not just to relist it. Just because a useless redirect has been in place for 18 years is no reason to keep it, and certainly no reason to resurrect it. Owen× ☎ 02:19, 19 May 2024 (UTC)
- DRV is not XfD. The merits of the redirect are out of scope for DRV. The automatic links, tools, logging, etc, are set up to work from XfD. We are only still here because an admin is obstinately sticking by their bad G6. The purpose of this DRV is to establish consensus that the G6 was wrong and the redirect if it must be deleted must go through xfd. SmokeyJoe (talk) 03:29, 19 May 2024 (UTC)
- The authority to delete is spelled out by our deletion policy, not by Twinkle or some template. DRV may overturn an XfD or a speedy to any other outcome. Specifically, it may overturn an incorrect speedy deletion to a consensus Delete. RfD doesn't provide any automatic links; we have all the information we need to decide this here and now, without listing it, and we don't need XFD Participation tool to voice our opinion, nor XFDcloser to carry out the result. I agree with you that CBDunkerson could have--and by this point should have--saved us from continuing this debate by undoing his G6. But he didn't, and now we have the choice between undoing it here and keeping the redir, undoing and sending to RfD, or leaving the page deleted while acknowledging G6 was a mistake. If you don't wish to adjudicate on the redir itself, it's certainly your prerogative to !vote "Overturn and list", but it's also the prerogative of those who don't see the need for the extra wonkery to !vote "Overturn to delete", which is basically no action beyond an implied finger wag at the out-of-process speedy. Owen× ☎ 06:42, 19 May 2024 (UTC)
- I don’t wish to adjudicate on the redir itself, not here and now.
- I am curious to see the history behind the redirect. I recall the Stephen Colbert call to edit elephant from around the time, and it might be funny or interesting to read. I considered requesting a temp undeletion, but haven’t because that information has no bearing on my opinion that the G6 was improper and must be reversed. If this goes to RfD, undeleted, I will examine the history before expressing an opinion on whether it is better kept available or hidden from nonadmins.
- I am not sure that is can be justifiably asserted that there is a consensus to delete the history. SmokeyJoe (talk) 09:32, 19 May 2024 (UTC)
- I agree; I, too, see no consensus to delete, sadly. It seems some here are more concerned with Righting Great Wrongs, in this case, teaching that admin a lesson, than they are in giving that page the disposition I believe it deserves. I doubt any participant here would have created Elephant population as a redirect had it not existed, which means that the only reason they're now opting to restore it is that it already existed, and was deleted out of process. I don't believe that's a valid reason to keep--or restore--a page, but it seems I'm in the minority here. Owen× ☎ 13:03, 19 May 2024 (UTC)
- Thanks. Let’s not say “Righting Great Wrongs”. I see this as filing rough edges in the cogs of deletion policy, in a place and a way that doesn’t stop anything else. G6 misuse diminishes the respect of WP:CSD, and disenfranchises the ordinary community in favour of an admin class in some aspects of the management of the community. SmokeyJoe (talk) 23:42, 19 May 2024 (UTC)
- I agree; I, too, see no consensus to delete, sadly. It seems some here are more concerned with Righting Great Wrongs, in this case, teaching that admin a lesson, than they are in giving that page the disposition I believe it deserves. I doubt any participant here would have created Elephant population as a redirect had it not existed, which means that the only reason they're now opting to restore it is that it already existed, and was deleted out of process. I don't believe that's a valid reason to keep--or restore--a page, but it seems I'm in the minority here. Owen× ☎ 13:03, 19 May 2024 (UTC)
- The authority to delete is spelled out by our deletion policy, not by Twinkle or some template. DRV may overturn an XfD or a speedy to any other outcome. Specifically, it may overturn an incorrect speedy deletion to a consensus Delete. RfD doesn't provide any automatic links; we have all the information we need to decide this here and now, without listing it, and we don't need XFD Participation tool to voice our opinion, nor XFDcloser to carry out the result. I agree with you that CBDunkerson could have--and by this point should have--saved us from continuing this debate by undoing his G6. But he didn't, and now we have the choice between undoing it here and keeping the redir, undoing and sending to RfD, or leaving the page deleted while acknowledging G6 was a mistake. If you don't wish to adjudicate on the redir itself, it's certainly your prerogative to !vote "Overturn and list", but it's also the prerogative of those who don't see the need for the extra wonkery to !vote "Overturn to delete", which is basically no action beyond an implied finger wag at the out-of-process speedy. Owen× ☎ 06:42, 19 May 2024 (UTC)
- DRV is not XfD. The merits of the redirect are out of scope for DRV. The automatic links, tools, logging, etc, are set up to work from XfD. We are only still here because an admin is obstinately sticking by their bad G6. The purpose of this DRV is to establish consensus that the G6 was wrong and the redirect if it must be deleted must go through xfd. SmokeyJoe (talk) 03:29, 19 May 2024 (UTC)
- In Victor Hugo's last novel, Ninety-Three, a sailor risks his life to secure a loose cannon on deck, the cannon that he himself failed to secure earlier. The captain awards him a medal for his bravery, and then proceeds to execute him for dereliction of duty. My question is, must we revive this redirect just to kill it again? The G6 was wrong, and IAR doesn't apply here, but DRV is a content forum, not a disciplinary one. It seems pointless to retrace our steps just to end up where we started, and we're not here to educate anyone. We don't know what a future RfD would decide, but we don't need to leave this for RfD. Policy gives DRV the authority to adjudicate the matter, not just to relist it. Just because a useless redirect has been in place for 18 years is no reason to keep it, and certainly no reason to resurrect it. Owen× ☎ 02:19, 19 May 2024 (UTC)
- Overturn. The "intended solution" was exactly what was done: removing inappropriate content and turning the page into a redirect, and that was done because it's at least a somewhat plausible redirect; someone thinking that this redirect makes some sense is the precondition to this solution. If it hadn't made at least some sense to someone, the page wouldn't have been redirected but deleted. This is a common reason redirects are created and protection isn't important; current protection practices differing from those xx years ago have nothing to do with the deletion/retention of the redirect. Today this same redirect could be created under the same circumstances, but the page would not be protected.—Alalch E. 23:28, 18 May 2024 (UTC)
- As a non-admin, I can't tell exactly what has happened here. SportingFlyer T·C 04:56, 19 May 2024 (UTC)
- Elephant was persistently vandalized in August 2006, apparently at the behest of Stephen Colbert. When that article was protected, it inevitably spilled over into new titles. Since there's some value in this one, it was redirected to Elephant and then protected, and lived happily on for almost eighteen years when CBDunkerson "uncontroversially" deleted it. —Cryptic 05:06, 19 May 2024 (UTC)
- Overturn In that case, it should be overturned, even though if I agree with the spirit of the deletion. SportingFlyer T·C 22:56, 19 May 2024 (UTC)
- Elephant was persistently vandalized in August 2006, apparently at the behest of Stephen Colbert. When that article was protected, it inevitably spilled over into new titles. Since there's some value in this one, it was redirected to Elephant and then protected, and lived happily on for almost eighteen years when CBDunkerson "uncontroversially" deleted it. —Cryptic 05:06, 19 May 2024 (UTC)
- Overturn as an out-of-process deletion. Extraordinary Writ (talk) 18:53, 19 May 2024 (UTC)
Akiko Kitamura
I don't believe this closure was appropriate. I provided a legitimate argument for deletion, and this was a PROD that had been removed. None of the votes for "keep" commented on the merits of the article and instead cast aspersions on my work. I recommend this AFD be reopened. Bgsu98 (Talk) 20:50, 17 May 2024 (UTC)
- Endorse. The AfD ran for a full week, during which not a single participant supported your call for deletion. Whether or not you did a proper WP:BEFORE search is no longer relevant. There was no consensus to delete, and no compelling reason to relist it. I can't fault other editors for being suspicious of your nominations, seeing your poor track record. The ten examples that JTtheOG provided tell a damning story. Go for quality nominations, not for quantity. Owen× ☎ 21:15, 17 May 2024 (UTC)
Weak overturn to no consensusEndorse with no prejudice against immediate re-nomination (citing very low attendance). While there is clearly not anything close to consensus to delete, the keep !votes are attacking the nominator and do nothing to claim the subject is notable. I recommend this option rather than resisting because a potential future AFD can focus on the article rather than the nominator. If Bgsu98 wishes to renominate, I recommend this user take the advice at WP:RENOM and put together a stronger case as to why this particular article should be deleted. Frank Anchor 22:05, 17 May 2024 (UTC)- Comment - In the past six years, there have been three ArbCom cases involving deletion discussions, and in those three cases I have proposed that ArbCom institute discretionary sanctions, now known as contentious topics, for conduct in deletion discussions. ArbCom has evidently considered and not accepted that idea. This is another illustration of behavior in deletion discussions that appears to be disruptive. Robert McClenon (talk) 01:43, 18 May 2024 (UTC)
- Weak Endorse - There was no error by the closer. The nomination was properly listed, and at least two editors saw it, and two editors commented, opposing deletion. Relist would have been a valid action. No Consensus would not have been a valid close. Robert McClenon (talk) 01:43, 18 May 2024 (UTC)
- Comment - There should be a Skating list at Deletion Sorting, especially since the appellant is nominating large numbers of figure skaters for deletion. Robert McClenon (talk) 02:01, 18 May 2024 (UTC)
- Comment: there are currently 52 open AfDs in the newly created WP:DELSORT/Skating, of which 51 were nominated by Bgsu98, most using a copy-pasted nomination text. The exception was WP:Articles_for_deletion/Nordic_cross_skating, which isn't about a skater, and arguably may not be about skating at all.
- Did the appellant believe their chances are better with 51 separate nominations than with one, 51-entry discussion? Either way, DRV, as a second instance forum, may aggregate all 51 into a single merged AfD, for a more meaningful discussion about WP:NSKATE and related guidelines. Leaving all 51, minimally-attended individual AfDs to the luck of who saw the AfD will result in inconsistent outcomes, encouraging more BEFORE-less nominations. Owen× ☎ 13:22, 18 May 2024 (UTC)
- Endorse Bad AfD conduct as noted by the participants--too many at once, copy/paste rationale, no or inadequate BEFORE--are all rebuttals to the presumed good faith of the nominations. This is a perfectly fine reason to reject an AfD: if the nominator didn't pay the encyclopedia and community due respect, then no return consideration is necessary. Otherwise, shotgun XFD nominations would be a WP:FAIT unless specifically and carefully rebutted. Jclemens (talk) 13:43, 18 May 2024 (UTC)
- Endorse with no prejudice against immediate re-nomination This underlying discussion is not a great example of what a deletion discussion should look like. On one hand, WP:NSKATE, as part of WP:NSPORT, is largely depreciated and I believe should be seen more like WP:OUTCOMES. However, since it still is an SNG, the community still thinks there is value in NSPORT, there is no obvious error in the nominator to nominate individuals who do not meet the criteria in WP:NSKATE. That said, failing the SNG does not mean that a subject must be deleted - as the subject can still merit an article by meeting GNG, and the nominator should review the existing sources. For the subsequent comments in this deletion discussion, there was no attempt to find or provide sources to show that the subject meets GNG. Instead, the points raised were to procedurally keep the article. While quick nominations are usually frowned on by the community, entering them in quick succession is not necessarily a problem, especially if the nominator did their homework prior to the nomination. And, just because other nominated articles in the same sequence may have sources, does not necessarily mean that this nomination was in error. All of this means to me that the close should be seen as a procedural keep and any editor could re-nominate the article. --Enos733 (talk) 15:30, 18 May 2024 (UTC)
- Endorse and allow immediate re-nomination the reason to delete was possibly not well thought through, the reasons to keep were procedural and not policy-driven, so it's basically like the discussion didn't happen at all. No problem with a new AfD, and if nominated by the same user, clear evidence of a WP:BEFORE search would be wise. SportingFlyer T·C 04:55, 19 May 2024 (UTC)
16 May 2024
|
---|
The following is an archived debate of the deletion review of the page above. Please do not modify it. |
Buna ziua, a fost stearsa pagina creata de mine pt firma de proiectare Vasa Proiect. Administratorul Gikü a invocat motivul A7 “nici o indicatie a importantei”. Nu mi-a oferit nici o oportunitate sa ii raspund si mi-a sters pagina. I-am explicat ulteriror ca este vorba despre o firma renumita de proiectari din Sibiu care a facut numeroase cladiri, care au fost mentionate in detaliu in sectiunea portofoliu a paginii Wikipedia. I-am explicat ca am inclus referinte la cladirile construite pe baza proiectelor Vasa Proiect si la numeroasele companii, inclusiv internationale, cu care a colaborat Vasa Proiect, in masura in care acestea exista online. Dar, avand in vedere natura domeniului de actvitate, si anume proiectarea pt constructia de cladiri, importanta firmei o demonstreaza cladirile construite si nu toate sunt mentionate in presa/ online etc. De aceea am fost limitata in numaraul de referinte care l-am putut include. Deasemenea am vazut alte firme de proiectare din Romania care au pagini similare pe Wikipedia, chiar cu mai putine referinte decat Vasa Proiect, si care nu au fost sterse. Doresc sa mentionez si ca Gikü mi-a criticat pagina invocand probleme de copyright pt logoul firmei si imaginile caldirilor, pt ca proveneau de pe siteul siteul Vasa Proiect (http://vasaproiect.ro/). Aceasta este o critica absurda pt ca acesta este siteul nostru, pozele si logul ne apartin, de aceea le-am inclus de pe pagina noastra de Wikipedia. Deci nu are sens sa se invoce o problema de copyright. Consider ca stergerea pagingii si motivele invocate sunt incorecte. Va rog sa ma ajutati. Va multumesc. Danawiki2024 (talk) 15:59, 16 May 2024 (UTC)
|
The above is an archive of the deletion review of the page listed in the heading. Please do not modify it. |
15 May 2024
Mitslal Kifleyesus-Matschie
I'd like to request a deletion review for the subject. It is a notable subject and remained there for almost a year. I would really appreciate a constructive dialog on said matter. Thank you! — Preceding unsigned comment added by 103.188.92.234 (talk • contribs)
- Endorse the G5 but allow recreation by any editor in good standing. The article was created and substantially only edited by a confirmed sock of User:Wrathofyazdan, and deleted as such. A quick look didn't reveal any independent SIGCOV about the subject, but I might have missed something. I see no reason to forbid recreation, ideally as a draft, by a legitimate editor. Owen× ☎ 16:08, 15 May 2024 (UTC)
- Endorse G5 per OwenX. As the reason for this deletion is due to a blocked user being its only substantial author, and not due to content, recreation by any user in good standing is explicitly allowed. Frank Anchor 13:14, 16 May 2024 (UTC)
- Endorse the G5 per above, you are welcome to re-create the article if notable though. SportingFlyer T·C 23:05, 17 May 2024 (UTC)
14 May 2024
|
---|
The following is an archived debate of the deletion review of the page above. Please do not modify it. |
This page was speedily deleted under G6 midway through an MfD discussion in which multiple editors had argued in favour of keeping it. The deletion was therefore not
|
The above is an archive of the deletion review of the page listed in the heading. Please do not modify it. |
13 May 2024
|
---|
The following is an archived debate of the deletion review of the page above. Please do not modify it. |
Disputed closure of bio article. 170.167.196.16 (talk) 15:58, 13 May 2024 (UTC) |
The above is an archive of the deletion review of the page listed in the heading. Please do not modify it. |
12 May 2024
'phone (closed)
|
---|
The following is an archived debate of the deletion review of the page above. Please do not modify it. |
Seems like a flawed nomination. See wikt:'phone. 1234qwer1234qwer4 17:40, 12 May 2024 (UTC)
|
The above is an archive of the deletion review of the page listed in the heading. Please do not modify it. |
Ami Dror (closed)
|
---|
The following is an archived debate of the deletion review of the page above. Please do not modify it. |
This is a extremely contentious Afd that was closed by the admin with a simple keep as though they were closing an Afd opened by mistake. None of the problem inherent in the Afd discussion were addresed. From the canvassing at the beginning, to the the whole course of the keep !votes being based on false premises, hand-waving and wilful (supposed) ignorance of policy, particularly ignorance of the WP:O Note d, i.e. the idea that interviews can prove a person notable. These arguments have been given false creedence that has lead to a false keep !vote. It should have been delete, or at the worst no consensus. Now we have been left with a group that thinks its ok to use interviews to prove notability. I think the whole thing feels staged. scope_creepTalk 13:52, 12 May 2024 (UTC)
Robert McClenon (talk) 17:36, 13 May 2024 (UTC)
|
The above is an archive of the deletion review of the page listed in the heading. Please do not modify it. |
11 May 2024
|
---|
The following is an archived debate of the deletion review of the page above. Please do not modify it. |
The argument that the article do not meet WP:SUSTAINED has not been attended by the closer. There are no reliable sources on the article subject other than within the last 2 months in 2023, and no such sources were presented during the deletion discussion. More on it at User talk:Cocobb8/Archives/2024/May#Bogdan Khmelnitsky Battalion . ManyAreasExpert (talk) 19:30, 11 May 2024 (UTC)
|
The above is an archive of the deletion review of the page listed in the heading. Please do not modify it. |
|
---|
The following is an archived debate of the deletion review of the page above. Please do not modify it. |
Meets notability guidelines for being an incredibly well-known cosmetics brand and considering the high level of controversy at this year's Eurovision Song Contest, the sponsorship of which by Moroccanoil is a major contributor of, an article is definitely both topical and necessary. Kapitan110295 (talk) 04:11, 11 May 2024 (UTC)
|
The above is an archive of the deletion review of the page listed in the heading. Please do not modify it. |
10 May 2024
|
---|
The following is an archived debate of the deletion review of the page above. Please do not modify it. |
This draft was nominated under WP:BLPREQUESTDELETE, and - after the discussion had been open for over a week - it was procedurally closed by a non-admin after their moving of the draft to mainspace. As I mentioned on the closer's talk, I believe that this was a bad close for several reasons:
I therefore believe that the closure should be overturned, and the page moved back to draftspace pending the outcome of the MfD. All the best, —a smart kitten[meow] 11:29, 10 May 2024 (UTC)
|
The above is an archive of the deletion review of the page listed in the heading. Please do not modify it. |
9 May 2024
|
---|
The following is an archived debate of the deletion review of the page above. Please do not modify it. |
A contentious AfD closed by a non-admin as a "no consensus / leaning keep", four days after it being relisted. Closing rationale makes it clear the closer was aware of the contentiousness, yet chose to ignore it. I reverted the close as an obvious BADNAC, with a polite notice on the closer's Talk page. The closer chose to lash back at me and re-close. I believe this one is best left for an admin to close, once the seven days since the last relist are up. Owen× ☎ 11:14, 9 May 2024 (UTC)
|
The above is an archive of the deletion review of the page listed in the heading. Please do not modify it. |
8 May 2024
|
---|
The following is an archived debate of the deletion review of the page above. Please do not modify it. |
|
The above is an archive of the deletion review of the page listed in the heading. Please do not modify it. |
6 May 2024
|
---|
The following is an archived debate of the deletion review of the page above. Please do not modify it. |
Communicated with the closer user:Ganesha811 prior to posting this comment here for deletion review. The closer respectfully disagrees, but has not posited any specific evidence or points to bolster their reason for interpreting the "consensus" as they did beyond stating, "I appreciated your reasoned arguments in favor of keep, but after re-reading the linked policies and considering the !votes for deletion as well as those explicitly for merge, I felt that a merger which retained large parts of the material reflected the overall consensus." The page Woke mind virus in fact had dozens of sources that were reliable and clearly and unambiguously separated the word "Woke mind virus" out as distinct from woke. More importantly for this deletion review, I feel that the largest body of consensus, both in terms of !votes as well as most importantly in terms of WP policy arguments, all pretty clearly favored a Keep close of the AfD. This is my first time ever requesting a AfD that closed in a manner that I feel was inconsistent with the apparent consensus to be reviewed. It seemed that most recently too near the time of close even more Keep !votes had been emerging, and therefore the close was both premature and not representative of the actual consensus as I understood the varied arguments and commentary. Iljhgtn (talk) 12:48, 6 May 2024 (UTC)
|
The above is an archive of the deletion review of the page listed in the heading. Please do not modify it. |
1 May 2024
Chloe Lewis (figure skater)
I think this is the right avenue for this. I saw this but never voted in it, I think it should be kept and I later noticed @Hameltion: bring this up somewhere. There's actually good sourcing from the Oregonian and also Colorado Gazeette. She is also a Youth Olympic silver medalist. So I think it should kept instead. Coop (talk) 09:26, 1 May 2024 (UTC) Blocked sock. Frank Anchor 12:53, 2 May 2024 (UTC)
- Endorse. Both sources are already included in the current draft being worked on. Nothing more to be done here; suggest a withdrawal and speedy close. Owen× ☎ 11:04, 1 May 2024 (UTC)
- Endorse' - What OwenX said. -- Whpq (talk) 11:28, 1 May 2024 (UTC)
Endorseper OwenX. I have no objection to the draft being spun out to an article in its current state, but that is not in the scope of the DRV discussion. Frank Anchor 14:19, 1 May 2024 (UTC)
- Changed to relist. It has come to my attention that delete voter Big Money Threepwood was indef blocked. Striking that vote, there is not a WP:QUORUM, meaning it must be relisted or closed as no consensus (with no prejudice against immediate renomination) or soft delete (subject to immediate restoration upon any good faith request such as this DRV). Relisting is probably the best option here, citing added visibility from this DRV. I will add that the Sandstein closed the AFD correctly based on information known at the time. Frank Anchor 19:00, 1 May 2024 (UTC)
Endorse as a valid close, but this isn't the right avenue.Some editors, including the current appellant, reasonably think that DRV is the right avenue to consider a new draft when an article was deleted, but DRV is not necessary in such cases. The article was deleted but not salted, and the draft will be reviewed. Robert McClenon (talk) 14:34, 1 May 2024 (UTC)- I'll just note for posterity how unsatisfying the AfD was: these adequate sources were already in the article, but none of the delete !voters addressed why they felt they were insufficient, and the nominator didn't understand the subordinate role of an SNG vs GNG. But no one was making those points at the time, so the closer went along with unsubstantiated claims of sourcing problems. The draft should just be moved back into mainspace at this point. Hameltion (talk | contribs) 16:54, 1 May 2024 (UTC)
- I share your frustrations, but as an admin, I can tell you that it's damned if you do, and damned if you don't. If you discard perfunctory !votes that constitute a numerical majority and close based on guidelines, you're accused of supervoting. And if you don't discard perfunctory !votes, you're accused of counting noses and ignoring guidelines. We love quoting WP:NOTAVOTE, but in practice, things aren't as simple. Owen× ☎ 17:27, 1 May 2024 (UTC)
- I understand, hard to close a discussion when there are no good policy-backed !votes. Hameltion (talk | contribs) 17:43, 1 May 2024 (UTC)
- The right thing to do if you're looking at closing a discussion where you disagree with the participants' interpretation of guidelines is to comment instead of closing. —Cryptic 19:26, 1 May 2024 (UTC)
- I understand, hard to close a discussion when there are no good policy-backed !votes. Hameltion (talk | contribs) 17:43, 1 May 2024 (UTC)
- I share your frustrations, but as an admin, I can tell you that it's damned if you do, and damned if you don't. If you discard perfunctory !votes that constitute a numerical majority and close based on guidelines, you're accused of supervoting. And if you don't discard perfunctory !votes, you're accused of counting noses and ignoring guidelines. We love quoting WP:NOTAVOTE, but in practice, things aren't as simple. Owen× ☎ 17:27, 1 May 2024 (UTC)
- "Endorse" and "the draft can be turned into an article right now as it is" aren't compatible; the changes from the version deleted at AFD and now are almost entirely cosmetic. —Cryptic 17:17, 1 May 2024 (UTC)
Substantialcontent was added to the draft on 20 April. However, even if that was not the case, my opinion is akin to “I would have voted keep, but consensus disagreed with me, so I endorse the result.” DRV is not AFD part 2, but I’m sure you already know that. Frank Anchor 17:47, 1 May 2024 (UTC)- Would this "substantial content" be the changes to the infobox, the removal of the statement that she's a freshman in college, or the six new tables that give unreferenced statistics of the exact same competitions as the table that was already there? AFC isn't AFD part 2 either; if this is moved into mainspace I'll speedy it. —Cryptic 18:12, 1 May 2024 (UTC)
- I retract the "substantial" part, as I looked more at the quantity of the content than the quality. Thanks for finding my error. Frank Anchor 19:13, 1 May 2024 (UTC)
I just noticed one of the delete voters are banned does their vote still count? Coop (talk) 17:50, 1 May 2024 (UTC)Blocked sock. Frank Anchor 12:53, 2 May 2024 (UTC)In addition, the nominator even said she never should have been nominated for deletion.Can we just move this from draft now? Coop (talk) 18:03, 1 May 2024 (UTC)Blocked sock. Frank Anchor 12:53, 2 May 2024 (UTC)
Oh okay, I didn't know there was already another draft in progress. I'm fine with closing and withdrawing if someone knows how to do that. Coop (talk) 17:49, 1 May 2024 (UTC)Blocked sock. Frank Anchor 12:53, 2 May 2024 (UTC)
- Comment - Deletion Review is not AFC, and does not move a draft into mainspace. But ...
- Relist after discounting the sockpuppet !vote. The appellant is advised to improve the article while the deletion discussion is resuming, to try to get a Heymann result. Robert McClenon (talk) 02:37, 2 May 2024 (UTC)
- Relist per everyone above. The delete closure was fine at the time it was made, but now that it's been reasonably challenged and one of the deleters was a sock a relist is reasonable. * Pppery * it has begun... 03:29, 2 May 2024 (UTC)
- I don't think we needed a participant to later be blocked for socking to have overturned this - a deletion discussion that waves away those sources with no more than "fails WP:SIGCOV" is defective, not just an outcome being disagreed with. But, as I mentioned above, we do need to overturn it, not just wave it away as "the deletion discussion was correct, but you can go ahead and move some stuff around in the WP:REFUNDed article and just dump it back in mainspace". —Cryptic 03:44, 2 May 2024 (UTC)
- Endorse I also wouldn't move the draft into mainspace any time soon, to be honest. The DRV nom has just been blocked, and the two articles we're basing this on fail WP:YOUNGATH (one is from her home metro area and the other is from her dance partner's metro area), and there's no other clear sourcing available yet. SportingFlyer T·C 06:25, 2 May 2024 (UTC)
- Comment The "keep" !vote makes a policy-based argument for Redirect without deletion of the edit history, which is not refuted in the AfD. 2603:6011:8241:6E00:243F:DBC7:2745:2359 (talk) 09:26, 2 May 2024 (UTC)
- Close as moot. Nom is also a sock. The extant draft can go through AfC like any other and if substantially improved, it will not be a G4. Star Mississippi 11:51, 2 May 2024 (UTC)
Nom is also a sock
does not excuse the fact that the article was later found to be deleted without a quorum. In addition, there are multiple good-faith votes to not endorse the result, so the DRV must run its course. Frank Anchor 12:42, 2 May 2024 (UTC)- Absolutely correct. However five more days here to kick it back to AfD for ~ 7 or more seems silly when there's a path to mainspace in less time and there's no guarantee a relist will result in retention. To be clear though, my opinion not policy. Star Mississippi 01:24, 3 May 2024 (UTC)
- User:Star Mississippi writes:
there's a path to mainspace in less time and there's no guarantee a relist will result in retention.
Yes, but there's no guarantee that AFC will result in promotion back to mainspace either. I would decline the current draft because it does not speak for itself and does not describe significant coverage by reliable sources. The idea of moving the draft into article space in its current state is well-meaning but silly. So I also think that a relist will very likely repeat the deletion. There is no quick path to resolve this. The article isn't ready for mainspace; the draft isn't ready for mainspace. The proponents of an article need to work on the draft. Robert McClenon (talk) 17:00, 4 May 2024 (UTC)
- User:Star Mississippi writes:
- Absolutely correct. However five more days here to kick it back to AfD for ~ 7 or more seems silly when there's a path to mainspace in less time and there's no guarantee a relist will result in retention. To be clear though, my opinion not policy. Star Mississippi 01:24, 3 May 2024 (UTC)
- Relist due to socking issues. Stifle (talk) 08:43, 3 May 2024 (UTC)
- Relist; no fault, but tainted by socking. Queen of Hearts (talk) 05:26, 10 May 2024 (UTC)