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, 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:
- 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.
Examples of opinions for an article that had been deleted:
- *'''Endorse''' The original closing decision looks like it was sound, no reason shown here to overturn it. ~~~~
- *'''Relist''' A new discussion at AfD should bring a more thorough discussion, given the new information shown here. ~~~~
- *'''Allow recreation''' The new information provided looks like it justifies recreation of the article from scratch if there is anyone willing to do the work. ~~~~
- *'''List''' Article was speedied without discussion, criteria given did not match the problem, full discussion at AfD looks warranted. ~~~~
- *'''Overturn and merge''' The article is a content fork, should have been merged into existing article on this topic rather than deleted. ~~~~
- *'''Overturn and userfy''' Needs more development in userspace before being published again, but the subject meets our notability criteria. ~~~~
- *'''Overturn''' Original deletion decision was not consistent with current policies. ~~~~
Remember that deletion review is not an opportunity to (re-)express your opinion on the content in question. It is an opportunity to correct errors in process (in the absence of significant new information), and thus the action specified should be the editor's feeling of the correct interpretation of the debate. Deletion review is facilitated by succinct discussions of policies and guidelines; long or repeated arguments are not generally helpful. Rather, editors should set out the key policies and guidelines supporting their preferred outcome.
The presentation of new information about the content should be prefaced by Relist, rather than Overturn and (action). This information can then be more fully evaluated in its proper deletion discussion forum. Allow recreation is an alternative in such cases.
Temporary undeletion
Admins participating in deletion reviews are routinely requested to restore deleted pages under review and replace the content with the {{TempUndelete}}
template, leaving the history for review by everyone. However, copyright violations and violations of the policy on biographies of living persons should not be restored.
Closing reviews
A nominated page should remain on deletion review for at least seven days, unless the nomination was a proposed deletion. After seven days, an administrator will determine whether a consensus exists. If that consensus is to undelete, the admin should follow the instructions at Wikipedia:Deletion review/Administrator instructions. If the consensus was to relist, the page should be relisted at the appropriate forum. If the consensus was that the deletion was endorsed, the discussion should be closed with the consensus documented.
If the administrator closes the deletion review as no consensus, the outcome should generally be the same as if the decision was endorsed. However:
- If the decision under appeal was a speedy deletion, the page(s) in question should be restored, as it indicates the deletion was not uncontroversial. The closer, or any editor, may then proceed to nominate the page at the appropriate deletion discussion forum, if they so choose.
- If the decision under appeal was an XfD close, the closer may, at their discretion, relist the page(s) at the relevant XfD.
Ideally all closes should be made by an administrator to ensure that what is effectively the final appeal is applied consistently and fairly but in cases where the outcome is patently obvious or where a discussion has not been closed in good time it is permissible for a non-admin (ideally a DRV regular) to close discussions. Non-consensus closes should be avoided by non-admins unless they are absolutely unavoidable and the closer is sufficiently experienced at DRV to make that call. (Hint: if you are not sure that you have enough DRV experience then you don't.)
Speedy closes
- Objections to a proposed deletion can be processed immediately as though they were a request at Wikipedia:Requests for undeletion
- Where the closer of a deletion discussion realizes their close was wrong, and nobody has endorsed, the closer may speedily close as overturn. They should fully reverse their close, restoring any deleted pages if appropriate.
- Where the nominator of a DRV wishes to withdraw their nomination, and nobody else has recommended any outcome other than endorse, the nominator may speedily close as "endorse" (or ask someone else to do so on their behalf).
- Certain discussions may be closed without result if there is no prospect of success (e.g. disruptive or sockpuppet nominations, if the nominator is repeatedly nominating the same page, or the page is listed at WP:DEEPER). These will usually be marked as "administrative close".
Existential threat (closed)
|
---|
The following is an archived debate of the deletion review of the page above. Please do not modify it. |
User:Someone-123-321 nominated this redirect for deletion earlier today but then withdrew it less than an hour later. At the time of withdrawal, there was one "keep" !vote and no "delete" !votes. Subsequently (after the withdrawal), this redirect was deleted per G4. I think this redirect should at least temporarily be restored given that there was opposition to deletion and the discussion only existed for less than an hour. Presidentman talk · contribs (Talkback) 15:03, 29 January 2025 (UTC)
|
The above is an archive of the deletion review of the page listed in the heading. Please do not modify it. |
Harsh Beniwal (closed)
|
---|
The following is an archived debate of the deletion review of the page above. Please do not modify it. |
The closure of this deletion discussion interpreted consensus. I believe meeting WP:NACTOR is usually enough to keep a standalone article. As Harsh has played significant roles in multiple television shows, such as Campus Diaries, Who's Your Daddy? (2020 TV series), and Heartbeats (TV series). Also as per WP:NYOUTUBE(Subscriber count helps meet the second criteria of WP:ENT.) he meets 2nd criteria of WP:ENT As he has over [16 Million] subscribers in his YouTube channel. Jitujadab90 (talk) 23:11, 27 January 2025 (UTC)
|
The above is an archive of the deletion review of the page listed in the heading. Please do not modify it. |
Baku Dialogues (closed)
|
---|
The following is an archived debate of the deletion review of the page above. Please do not modify it. |
The closure of this deletion discussion incorrectly interpreted consensus. The discussion included one vote to delete, one to keep, and two to merge, which does not clearly indicate a consensus to merge. Additionally, significant sources from reputable organizations such as the Atlantic Council, The Washington Institute, and Central Asia-Caucasus Institute were provided, demonstrating the journal's academic notability and relevance. These were not adequately addressed. I believe this warrants a review of the closure. Wiseuseraze (talk) 22:12, 27 January 2025 (UTC)
|
The above is an archive of the deletion review of the page listed in the heading. Please do not modify it. |
|
---|
The following is an archived debate of the deletion review of the page above. Please do not modify it. |
Afd was attended by only the nominater who aruged that it failed BLP1E however on examing the article i find it had 17 sources which covered not only his win but his other 3 appearences as well furthmore they are both primariy and secondary sources so the article not only doesnt meet the 3 requirements for BLP1E but it passes GNG as there is significant Coverage with secondary sources on more then 1 event on a side note I don't think it's fair to have to "make improvments" when there was 0 adequate discossion on whether the page shouldve been redirected or not — Preceding unsigned comment added by Wwew345t (talk • contribs) 14:15, 24 January 2025 (UTC)
|
The above is an archive of the deletion review of the page listed in the heading. Please do not modify it. |
|
---|
The following is an archived debate of the deletion review of the page above. Please do not modify it. |
This page was chosen to be merged for lack of noteworthiness, however the consensus was reached before multiple knowledgeable editors updated the page with over 40 references. Deletion discussion centers around lack of noteworthy sources, where users are not willing to accept sources that are not major media companies. This coin is an example of the ability of AI to relate to humans in an infectious and viral way. The name Fartcoin was conceived by a jailbroken Large Language Model as the ideal meme coin to relate to humans. It plays a major role in the creation of the first ever AI crypto millionaire, in which 2% of the token supply was sent to the crypto wallet of the Truth Terminal AI agent that named the coin. It also has connections to Marc Andreesen as one of the most prolific Venture Capitalists, when Marc sent $50k to the Truth Terminal agent's wallet after seeing it reach viral status on X.com social media site. I request that moderators review the sources shown in the article as there are dozens of mentions in the media landscape about Fartcoin and its encapsulation of the absurd and hyper-speculative nature of crypto. The connection to AI as the ideal meme coin name, followed by its successful capture of human attention and creation of an AI millionare, is noteworthy enough to have its own page. In less than a month it garnered 27,000 pageviews. EveSturwin (talk) 22:25, 22 January 2025 (UTC)
|
The above is an archive of the deletion review of the page listed in the heading. Please do not modify it. |
|
---|
The following is an archived debate of the deletion review of the page above. Please do not modify it. |
Discussion with closer. This is unfortunate timing for an RfD as the status quo kept shifting about all over the place. First there was no mention of the Gulf of America at Gulf of Mexico, then there was a mention in the lede and body and a hatnote to Nakhodka Bay, then that mention was removed from the lede and took an amble through various parts of the article at some point resulting in the hatnote being removed, and now Gulf of Mexico#Name actually directs readers to Nakhodka Bay in its text. The point is – it's not the easiest discussion to evaluate consensus for, but the disambiguate result appears to be a supervote or based about the drafting of a disambiguation page, which in RfDs is standard procedure and is meant to further discussion rather than prejudice the RfD's result. Overturn to keep or no consensus, and refine the redirect to Gulf of Mexico#Name as the vast majority of (later) participants did not express support for disambiguation, instead preferring a conflicting action. J947 ‡ edits 20:34, 22 January 2025 (UTC)
|
The above is an archive of the deletion review of the page listed in the heading. Please do not modify it. |
Admin did a "Procedural close", stating that it was because the page was swapped out with one from draft space during the discussion. However,
- That's not what happened; the discussion was closed, then the page was swapped with clear consensus from both Keep and Delete !voters, then the discussion was reopened following a January 3 deletion review.
- That shouldn't matter because both articles were on the same subject (a specific TV cast member) and the discussion was all about notability (i.e., the subject) and not content (the article.)
Discussion on this has been extensive and should be allowed a proper close. Nat Gertler (talk) 14:50, 19 January 2025 (UTC)
- Agree. In this case, a closing admin should be able to make a whatever closing outcome they find reasonable based on the comments at hand. I don't think we need another week of discussion, 2 relists are enough, but an "actual" close, either by last closer @Liz herself or another willing admin. The post-close "swapping" can be seen as encouraged during-afd improvement. Ping "swapper" @PrimeHunter and afd-starter @Pppery if they wish to comment.
- This subject has been in a kind of "development hell" for quite awhile. The draft was pending for review (again), and someone decided during that pending to make a new version and put it in main-space, and that version was taken to afd. Then the afd closed, the "swapping" happened, there was a DRV, and the afd was reopened, then closed by Liz. So IMO, the closer should also consider if a no consensus close here means
- no consensus = back to draft
- or
- no consensus = stays in main-space. Gråbergs Gråa Sång (talk) 15:44, 19 January 2025 (UTC)
- Endorse the procedural close as a procedural close. I agree with the appellant that the discussion was extensive and deserved a proper close, but the discussion had been about two versions of the article, and I agree with the closer that this made a consistent close impossible. The closer said that a new AFD would be the way to resolve the biographical notability issue. Robert McClenon (talk) 21:11, 19 January 2025 (UTC)
- Comment - The MFD notice on a draft or project page says not to blank, merge, or move the page, or remove the notice. The AFD notice on an article says not to remove the notice. I have been saying for several years that the AFD notice should say not to blank, merge, or move the page, or remove the notice. An editor moved the page by replacing it with another page, and that confused things. I have mostly been concerned about bad-faith moves of nominated articles, but this was a misguided good-faith move that should not have been done because it made a consistent closure impossible. Robert McClenon (talk) 21:11, 19 January 2025 (UTC)
- Comment I am not invested in this closure and I came to the decision of a procedural close after reviewing the discussion again. The AFD was started with one version of the article on this subject and, after several relistings of the discussion, it came time to close the discussion but it was now about a different version of the article than when it started. I looked at the possible options for closure and none of them seemed appropriate as they would all be ignoring the fact that the AFD had covered two different versions of an article on the same subject.
- I realize that the AFD is about the subject but this still seemed like a highly unusual situation so a procedural close was done and, if editors wished to do so, a fresh AFD could be started if there were those who still sought deletion. This seemed like the only resolution that would abide by the spirit of our guidelines. I review most open AFDs on a regular basis and if I had noticed that the articles had been switched out (main space>draft, draft>main space) earlier in the process, I would have closed this discussion sooner before it had gone on so long. I have closed hundreds (thousands?) of AFD discussions over the past four and a half years and this is the first time I've seen a situation like this happen. I'm glad this review is happening, not to second guess myself but because I'm curious what other solutions DRV regulars think might have been suitable for an AFD where the article that has been nominated is switched midway through the discussion with a different draft version. If the consensus is that my closure was incorrect, I accept that determination and welcome the community's guidance on how to handle situations like this should they ever come up again in the future. Liz Read! Talk! 21:45, 19 January 2025 (UTC)
- I personally think that if an article is re-written during an AFD, that does not invalidate the !votes, since AFD arguments usually address the subject's notability rather than the state of the wikitext. I was expecting a keep close for this particular AFD. Not sure how much more editor time we should spend on this though. It's been to deletion review twice now. I would not have personally taken this to deletion review. –Novem Linguae (talk) 22:49, 19 January 2025 (UTC)
- This is the second time this user insists on starting a deletion review on this article in a short time. He asked the closer but gave very little time for a reply before starting this second deletion review. Why this painful rush? Why force the community to spend all this time? Is it really a life or death situation to achieve just the exact and precise sort of close? I wholeheartedly agree with the above endorse (=leave the close as "good enough") in that in the bigger picture some sort of status quo close was realistically all that would be had from that discussion, so "procedural" is just fine. I strongly advise against a backdoor delete; it is not appropriate to reinterpret "no consensus" to mean back to draft; that is explicitly against what both keep and delete !voters meant and intended when they made their comments. If "keep" starts to mean "keep or possibly back to draft" then every Wikipedian needs to be made aware of that and we need a new term for "keep and only keep". To me, "no consensus" needs to keep having the meaning "we could not agree to make a change, so we keep the status quo" Regards CapnZapp (talk) 23:29, 19 January 2025 (UTC)
- Please note that the above poster who is criticizing me is a very involved editor who "insists" on dealing with this matter by insisting that those questioning specific claims inconvenient to his stance remain silent. The appropriateness of the first deletion review should be apparent in its success. As for rushing, I waited approximately a day and saw that the admin involved had responded to a number of other matters without responding to concerns posted by multiple people on their Talk page... and that admin has now expressed that she is "glad this review is happening". If this is found to be an appropriate close, I'd be interested in seeing where the limits are (WP:AFD says "If you wish for an article to be kept, you can directly improve the article", and that is largely what the swap was, as the draft article was basically a superset of the information in the article-space article, with better sourcing; cutting and pasting the entire draft article would seem within the letter of that, but the swap maintained edit history better than such pasting would've.) -- Nat Gertler (talk) 01:08, 20 January 2025 (UTC)
- Stop mischaracterizing my comment as "insisting" you "remain silent", User:NatGertler. I asked you to not shade Vanamonde's comment by pretending he was in the business of creating exceptions when good faith would assume he was not.
I think if Vanamonde93 wants to define an exception, it's up to them where the line is they are arguing for.
is a strong case of gaslighting and I wasn't letting you get away with it - to me he was definitely not trying to create exceptions and your demand that they draw lines is unreasonable. Telling you to stop diminishing another user's comment is very clearly not the same thing as "insisting" you "remain silent" - you are free to express yourself in a million ways; including ways where you put your thumb in the eye of a user that might not meet your stringent precision requirements. If, that is, you accept you might receive push-back from random users like me. Also, your comparison with Friends (each of the six Friends actors deserves equal notability while apparently there's this invisible line between the fifth and sixth main actor of Young Sheldon, which only excludes Revord). You somehow think it's okay to arbitrarily downplay actors (she is probably 6th in quantity of screen presence
,She's a regular, yes, but she's supporting cast.
) - no, Nat, there's zero weight in arguing her screen credit is less valuable than, say, Jordan's or Pott's. Finally, the context for what Nat is accusing me: Another user tried to defuse the situation by the very reasonable interpretation of Vanamonde's comment (Perhaps we can agree on "a main [cast] actor"?
) but no, you doubled down - and when I didn't fold, that's how you end up in situations where your only recourse, apparently, is to think people "insist" you "remain silent" when in reality, they are merely asking you assume good faith. CapnZapp (talk) 10:05, 20 January 2025 (UTC)- I see a lot of electrons have been sacrificed arguing over my intended meaning - I wish I had been pinged! For clarity, I am aware that Missy Cooper isn't the main character of the show, and "a main character" is what I intended to write. Also, for the record, I have not watched the show, would not describe myself as a fan, and am only aware of it because of how often it is mentioned in articles on the internet. Vanamonde93 (talk) 18:53, 20 January 2025 (UTC)
- Thank you for confirming what we all (but one) knew: that you intended to write "a main character" is the obvious good faith interpretation. Cheers CapnZapp (talk) 12:12, 27 January 2025 (UTC)
- By "we all (but one)", you seem to mean precisely you. (Only one other editor beside you and me was in the discussion that followed Vanamonde9's comment, and they just asked a question, rather than making claims about V's intent.) And no, "good faith" does not call on assuming that people don't mean the thing they say but mean the thing that would agree with you. Your repeated use of that technique in a recent discussion does not come off as a reflection of "good faith". -- Nat Gertler (talk) 14:19, 27 January 2025 (UTC)
- This whole row started because you decided to not leave Vanamonde93's !vote alone. I told you to not undermine other people's !vote based on bad faith interpretations of their arguments when a better faith interpretation is reasonable and readily available. You now refusing to conceding the point even after the original poster has established that my good faith interpretation was correct speaks volumes. CapnZapp (talk) 14:23, 29 January 2025 (UTC)
- By "we all (but one)", you seem to mean precisely you. (Only one other editor beside you and me was in the discussion that followed Vanamonde9's comment, and they just asked a question, rather than making claims about V's intent.) And no, "good faith" does not call on assuming that people don't mean the thing they say but mean the thing that would agree with you. Your repeated use of that technique in a recent discussion does not come off as a reflection of "good faith". -- Nat Gertler (talk) 14:19, 27 January 2025 (UTC)
- Thank you for confirming what we all (but one) knew: that you intended to write "a main character" is the obvious good faith interpretation. Cheers CapnZapp (talk) 12:12, 27 January 2025 (UTC)
- I see a lot of electrons have been sacrificed arguing over my intended meaning - I wish I had been pinged! For clarity, I am aware that Missy Cooper isn't the main character of the show, and "a main character" is what I intended to write. Also, for the record, I have not watched the show, would not describe myself as a fan, and am only aware of it because of how often it is mentioned in articles on the internet. Vanamonde93 (talk) 18:53, 20 January 2025 (UTC)
- Stop mischaracterizing my comment as "insisting" you "remain silent", User:NatGertler. I asked you to not shade Vanamonde's comment by pretending he was in the business of creating exceptions when good faith would assume he was not.
- Please note that the above poster who is criticizing me is a very involved editor who "insists" on dealing with this matter by insisting that those questioning specific claims inconvenient to his stance remain silent. The appropriateness of the first deletion review should be apparent in its success. As for rushing, I waited approximately a day and saw that the admin involved had responded to a number of other matters without responding to concerns posted by multiple people on their Talk page... and that admin has now expressed that she is "glad this review is happening". If this is found to be an appropriate close, I'd be interested in seeing where the limits are (WP:AFD says "If you wish for an article to be kept, you can directly improve the article", and that is largely what the swap was, as the draft article was basically a superset of the information in the article-space article, with better sourcing; cutting and pasting the entire draft article would seem within the letter of that, but the swap maintained edit history better than such pasting would've.) -- Nat Gertler (talk) 01:08, 20 January 2025 (UTC)
- Endorse This is a unique but excellent close. I agree above that AfDs are about notability, not about what should happen to a specific article, but I think "no consensus" is the strongest close here, it's been at AfD for awhile, and a "no consensus" creates possible issues with draft space, so a procedural close both allows it to be kept in main space, at least temporarily, and allows for a new conversation. I would give it a couple weeks and then start a fresh AfD. SportingFlyer T·C 00:27, 20 January 2025 (UTC)
- Overturn I would still have nominated regardless of what the text of the article said, as I would not have allowed an article created in open contempt of process to survive without an AfD. And I still won't allow it, and will renominate this version for AfD as well as soon as practical. Hence nothing has addressed the actual reason for my nomination, and the procedural close was improper. * Pppery * it has begun... 04:04, 20 January 2025 (UTC)
- That's why I'm hoping for an "actual" close instead of the procedural, it would hopefully spare us that new afd. Gråbergs Gråa Sång (talk) 10:54, 20 January 2025 (UTC)
- I would suggest a little casualness in starting a new AFD, for the simple reason that there is currently material bubbling up through tabloid sources regarding an online persona that, should it reach the level of better coverage in the next few days, could push the subject past the WP:NACTOR concern, at least for me, and would leave the article in a state that would likely have been accepted if submitted from Draft. See Talk:Raegan Revord for details. -- Nat Gertler (talk) 17:28, 20 January 2025 (UTC)
- Endorse
closing, including the SuperTrout({{Whale}}) for User:PrimeHunter for disrupting the AfD. Ask User:Pppery to wait at least two weeks after the close of this DRV to renominate. While some have a sense of outrage, there is no reason to rush. —SmokeyJoe (talk) 04:47, 20 January 2025 (UTC)- @SmokeyJoe, look at the timeline again. When PrimeHunter did their thing, the afd was closed as keep, then it was re-opened, and then Liz closed it again. This trouting thing is quite unfair, and disappointing from an 18 year + Wikipedian. Not to mention an admin/arb. Gråbergs Gråa Sång (talk) 09:17, 20 January 2025 (UTC)
- Ok, Gråbergs Gråa Sång, I withdraw endorsement of the SuperTrout, it does appear unfair. Is he an Arb, didn’t know, but that’s irrelevant. Looking at the state of things around 10am 3 January 2025, the AfD was closed, and looked reasonably closed on my pass, and explicitly raised the possibility of a page swap of the article for the better older draft, which User:PrimeHunter carried out. That was ostensibly the perfect thing to do, so apologies to PrimeHunter. I’m tempted now to criticise User:OwenX for relisting. OwenX did not reverse the pageswap, and from then onwards, the process had failed. —SmokeyJoe (talk) 11:54, 20 January 2025 (UTC)
- @SmokeyJoe Thanks! "admin/arb" referred to Liz, maybe I should have said "from an admin/arb". When she says stuff, people are likely to listen, for good reason, but IMO she should correct her closing statement. Agree with "ostensibly the perfect thing to do".
- On reverting the swap, I see your point, but I also think that would have been a bad idea from the BLP-perspective, changing [1] back to [2]. Gråbergs Gråa Sång (talk) 12:03, 20 January 2025 (UTC)
- The pageswap should not have reversed, meaning that the AfD should not have been relisted. SmokeyJoe (talk) 12:47, 20 January 2025 (UTC)
- You're absolutely right to criticize me, SmokeyJoe. I noticed something was fishy when I reverted the NAC, since the linked page under review didn't have the AfD template in its history. But I figured I'd leave things for the WP:GNOMES and bots to clean up, and thought things were fine once I saw user:cyberbot I attach the missing template. I routinely un-move pages that are moved during AfD, and should have dug deeper and unswapped in this case as well. Mea culpa, and a well deserved self-trout. Owen× ☎ 12:43, 20 January 2025 (UTC)
- It is a strange case, and you’re a pleasure to work with. SmokeyJoe (talk) 12:50, 20 January 2025 (UTC)
- It is a strange case. Gråbergs Gråa Sång (talk) 12:54, 20 January 2025 (UTC)
- It is a strange case, and you’re a pleasure to work with. SmokeyJoe (talk) 12:50, 20 January 2025 (UTC)
- Ok, Gråbergs Gråa Sång, I withdraw endorsement of the SuperTrout, it does appear unfair. Is he an Arb, didn’t know, but that’s irrelevant. Looking at the state of things around 10am 3 January 2025, the AfD was closed, and looked reasonably closed on my pass, and explicitly raised the possibility of a page swap of the article for the better older draft, which User:PrimeHunter carried out. That was ostensibly the perfect thing to do, so apologies to PrimeHunter. I’m tempted now to criticise User:OwenX for relisting. OwenX did not reverse the pageswap, and from then onwards, the process had failed. —SmokeyJoe (talk) 11:54, 20 January 2025 (UTC)
- @SmokeyJoe, look at the timeline again. When PrimeHunter did their thing, the afd was closed as keep, then it was re-opened, and then Liz closed it again. This trouting thing is quite unfair, and disappointing from an 18 year + Wikipedian. Not to mention an admin/arb. Gråbergs Gråa Sång (talk) 09:17, 20 January 2025 (UTC)
- Comment - I have raised the question of forbidding the moving, merging, or blanking of an article during AFD at Wikipedia:Village_pump_(proposals)#Forbid_Moving_an_Article_During_AFD. Robert McClenon (talk) 06:38, 20 January 2025 (UTC)
- User:Robert McClenon: sure, as long as we agree that doesn't apply to this particular article - as stated above it was only moved after the AFD was closed (and before it was reopened). Cheers CapnZapp (talk) 10:14, 20 January 2025 (UTC)
- I don't particularly see a issue with the swap, especially since it technically happened while the AFD was closed? More generally, significant rewires, including total replacements, do not totally void an AFD discussion, and therefore page swaps shouldn't either. On the other hand, the close is essentially a no consensus without prejudice closure, and the AFD is enough of a confusing trainwreck to justify that (the bludgeoning does not help, though I suppose this is not a conduct forum). I would endorse the close in this specific case, and unusual closes that creatively get around issues (the trainwreck) more generally, though absent the trainwreck I would recommend that a page swap not be considered to preclude substantive closes.
- As an retrospective on earlier administrative actions, the WP:REOPEN statement could possibly have been a bit more detailed, though of course I do not know if an exhortation to be more focused and provide analysis would actually have been effective. I agree with Robert McClenon, Liz, SportingFlyer and Pppery that a new AFD would be appropriate (in a couple of weeks). I would encourage participants of said new AFD to clearly link their arguments to the relevant guidelines, and if making an argument to IAR, clearly explain why the exception would make for a suitable article in this case. Alpha3031 (t • c) 07:45, 20 January 2025 (UTC)
- Liz is completely correct that you can't understand and parse a discussion when two separate iterations of an article are being discussed. Really, I don't think you can effectively hit a moving target when making changes during an AfD, which is why I rarely do. However, while Novem Linguae may be correct in theory, too many editors only look at and comment on the current state of the article--they don't do any research themselves nor engage with additional sourcing brought up by others in the course of an AfD. This is yet another topic that could stand to be clarified. Jclemens (talk) 07:53, 20 January 2025 (UTC)
- In this particular case, I think you can understand and parse. It's a bit complex, though.
- In the first part of the afd, you have a bunch of keep, and they are saying keep to this version. 2 editors, me and @NatGertler, are indicating doubt, Nat Gertler with an !vote.
- In the later part of the afd, after the first relist that came after the close-swapwithmuchbetterandmucholderdraft-DRV-reopen sequence of events, editors are now commenting on this version. Now, consider this speculation on my part if you will, but that change would not have made the keeps do a 180, the improvement is quite obvious.
- Nat Gertler commented extensively in the later part of the afd, if he had changed his mind he would have said so. As for myself, I wrote an !vote, so readers will know what I thought. Gråbergs Gråa Sång (talk) 09:56, 20 January 2025 (UTC)
- I believe it would be uncontroversial to say there was universal consensus for "the second version is superior to the first" in both !keep and !delete camps. Everybody seemed to think PrimeHunter's "swapwithmuchbetterandmucholderdraft" was a good idea, which makes his current supertrouted (whalesquished, even) status all the more poignant. CapnZapp (talk) 10:23, 20 January 2025 (UTC)
- And to be clear, much of my argument in the pre-original-closure made it clear that even then I was looking at the draft version, because I repeatedly argued that the draft version is the one that should be kept if there was a keep result. My delete concerns were based on notability, not on the content of a specific version of the article. -- Nat Gertler (talk) 17:12, 20 January 2025 (UTC)
- So, my cautionary advice stands: Just because one can follow what's happened, doesn't mean we should expect the average participant and closer to do so. The contrarian in me notes that if we made AfDs more confusing we might get fewer drive-by !votes, but reducing participation is almost never a good idea. Jclemens (talk) 05:23, 22 January 2025 (UTC)
- Average closer? Perhaps no. Called-in-for-re-close-after-first-DRV-admin Liz? Perhaps. Gråbergs Gråa Sång (talk) 05:39, 22 January 2025 (UTC)
- Endorse (involved, voted keep). Very difficult close by a very skilled closing admin. There were two different versions of the same article that were being discussed. While a no consensus close would have been fine, this probably works better as some may have considered a NC close to mean to send the article back to draft space for improvement. As the keep close is on procedural grounds, anyone is free to renominate it. I would recommend waiting at least a month after this DRV closes, in an attempt for tempers to cool down and to possibly allow for perspective from different users. Frank Anchor 13:31, 20 January 2025 (UTC)
- Overturn closure (mostly to undo the Liz's incorrect WP:TROUT of PrimeHunter). Should probably be re-closed as a simple keep and the WP:TROUT should be applied to Liz and to OwenX who reopened the AFD without saying so and without noticing that the page had been moved . —Kusma (talk) 15:12, 20 January 2025 (UTC)
- Doesn't [3] count as saying so? Gråbergs Gråa Sång (talk) 15:17, 20 January 2025 (UTC)
- ok, yes, it is in the relisting bit that I never look at. Trout for me too I guess (tasty!) —Kusma (talk) 15:45, 20 January 2025 (UTC)
- Doesn't [3] count as saying so? Gråbergs Gråa Sång (talk) 15:17, 20 January 2025 (UTC)
- With all due respect to Liz, who does excellent work at AfD, I don't believe a procedural close was needed here, and a lot of the procedural argument is quite unnecessary. If this is kept - and it seems it will be - the material in draftspace should just be merged to mainspace, and the draftspace title redirected to preserve history. If "credit" becomes important (why would it? DYK? GAN?) anyone who contributed substantively is logically entitled to credit in the same they would normally be if something were drafted in talk- or user-space. I !voted "weak keep", but either a "keep" or a "no consensus" could be justified here: there are substantive arguments for both outcomes, and many "keep"s acknowledge that notability is borderline/somewhat based on IAR. I would be fine with striking the trout to PrimeHunter - if I am reading the sequence of events correctly they acted while the AfD was closed, and as such their actions were reasonable. Vanamonde93 (talk) 18:53, 20 January 2025 (UTC)
- Tangential comment The reason "credit is important" is that editors (technically) retain copyright to their contributions, but license them under CC BY-SA, which requires attribution. If you can't figure out who wrote what, then we're in violation of the license terms. It's a little hard to imagine such a thing coming to trial, but it's a point of hygiene that the community takes seriously. --Trovatore (talk) 22:57, 20 January 2025 (UTC)
- @Trovatore: Our copyright and licensing choices require us to preserve the history of content we host. They do not in any way require us to preserve it at the same title, otherwise merges from draftspace/userspace to mainspace would not be possibly (they are in fact routine). If the page is kept, we need to preserve the history of both versions - but we do not need to waste more time over which title which version exists at. Vanamonde93 (talk) 17:04, 21 January 2025 (UTC)
- Tangential comment The reason "credit is important" is that editors (technically) retain copyright to their contributions, but license them under CC BY-SA, which requires attribution. If you can't figure out who wrote what, then we're in violation of the license terms. It's a little hard to imagine such a thing coming to trial, but it's a point of hygiene that the community takes seriously. --Trovatore (talk) 22:57, 20 January 2025 (UTC)
- Meh. Liz is correct that the AfD should be restarted because it is a mess, but wrong to blame PrimeHunter. There is clearly no consensus to delete in the closed discussion and I doubt that one would develop in a fresh one so perhaps it's best to wait a while before renominating. Eluchil404 (talk) 06:15, 21 January 2025 (UTC)
- Not sure you meant the implication here, but if you did - the reason to wait is not for a consensus to delete to develop. To the best of my knowledge everyone involved in reopening the AFD have done so because they feel it has been improperly closed (twice). At least I hope they aren't trying to keep it open until a delete outcome emerges, because - at least to me - the clear outcome, if the AFD we're discussing is reopened, would be "no consensus" (meaning "no consensus to delete", mind you, it is after all an "articles for deletion" discussion and not an "articles for keeping" discussion so "no consensus" must and should be taken to mean no consensus to take the discussed action), and - assuming we're not spammed with AFDs until people get tired of responding - I see no reason to expect a different outcome of a future AFD; unless obviously, sources appear that move the needle towards a clear keep result. CapnZapp (talk) 14:14, 29 January 2025 (UTC)
- Consensus? My reading of the above comments is Anyone who think they should can open a new afd, but give it awhile. Which is, sort of, what Liz said in her close. I also think there is support above that @Liz should strike/rewrite her closing comment regarding PrimeHunter, since the "in the midst of this AFD discussion, User:PrimeHunter moved the main space article to Draft space and the Draft space version to main space" is incorrect and PrimeHunter didn't deserve any kind of trout, super or otherwise. On a sidenote, afaict the ongoing Talk:Raegan_Revord#They/Them_Pronouns discussion has so far not produced any more GNG-good sources for the Revord article. Gråbergs Gråa Sång (talk) 19:50, 24 January 2025 (UTC)
- To clarify, are you saying you believe there is consensus to let Liz' close stand and have the AFD remain closed, User:Gråbergs Gråa Sång? On the sidenote, not sure why you expected that discussion to impact the notability issue? It's TikTokers with a weak sense of verifiability that get annoyed Wikipedia isn't mirroring the latest gossip - they aren't interested in our notability guidelines...? And on that topic, yes, Revord's notability is weak, but is it non-existent? Before the AFD was closed, it to me clearly was heading for a no consensus result (meaning "no consensus to delete", mind you, it is after all an "articles for deletion" discussion and not an "articles for keeping" discussion so "no consensus" must and should be taken to mean no consensus to take the discussed action) Regards CapnZapp (talk) 14:30, 29 January 2025 (UTC)
- Yep, my reading of the above is that there is no general taste to undo the close, but several have said "start a new afd". @Pppery said they intended to at some point. And IMO, in a new afd, we wouldn't have the "what does no consensus mean in this situation" issue. On the sidenote, the pronoun thing could have (might still) resulted in some usable sources, like the car crash, and those sources could have had some WP:N value. I think Nat Gertler had a similar thought at [4]. Gråbergs Gråa Sång (talk) 20:03, 29 January 2025 (UTC)
- I for one thing Liz's criticism of PrimeHunter is completely right - PrimeHunter's action was the but-for cause of this tangle. * Pppery * it has begun... 20:05, 29 January 2025 (UTC)
- @Pppery, when PrimeHunter did their thing, the afd was closed as keep, then it was re-opened, and then Liz closed it again. There was no reason at the time to think "Oh, this close will only last 36h." This I know because I didn't either. Gråbergs Gråa Sång (talk) 20:08, 29 January 2025 (UTC)
- I for one thing Liz's criticism of PrimeHunter is completely right - PrimeHunter's action was the but-for cause of this tangle. * Pppery * it has begun... 20:05, 29 January 2025 (UTC)
- Yep, my reading of the above is that there is no general taste to undo the close, but several have said "start a new afd". @Pppery said they intended to at some point. And IMO, in a new afd, we wouldn't have the "what does no consensus mean in this situation" issue. On the sidenote, the pronoun thing could have (might still) resulted in some usable sources, like the car crash, and those sources could have had some WP:N value. I think Nat Gertler had a similar thought at [4]. Gråbergs Gråa Sång (talk) 20:03, 29 January 2025 (UTC)
- To clarify, are you saying you believe there is consensus to let Liz' close stand and have the AFD remain closed, User:Gråbergs Gråa Sång? On the sidenote, not sure why you expected that discussion to impact the notability issue? It's TikTokers with a weak sense of verifiability that get annoyed Wikipedia isn't mirroring the latest gossip - they aren't interested in our notability guidelines...? And on that topic, yes, Revord's notability is weak, but is it non-existent? Before the AFD was closed, it to me clearly was heading for a no consensus result (meaning "no consensus to delete", mind you, it is after all an "articles for deletion" discussion and not an "articles for keeping" discussion so "no consensus" must and should be taken to mean no consensus to take the discussed action) Regards CapnZapp (talk) 14:30, 29 January 2025 (UTC)