Wikipedia talk:Deletion policy/Archive 51

Prefatory material on alternatives
I see a lot of discussions where it seems to be assumed that an alternative outcome is assumed to be preferable to deletion. I don't agree with this; I think any outcome suggested has to stand on its own merits. But in any case the matter needs to be spelled out. Mangoe (talk) 03:02, 25 October 2023 (UTC)
 * I agree that it needs to be spelled out. I disagree that what you wrote accurately reflects consensus, and have modified it appropriately. No hurt feelings if someone else reverts it entirely and goes back to the prior status quo... but what you wrote isn't consensus. Jclemens (talk) 04:38, 25 October 2023 (UTC)
 * It seems to me that your addition was contradicted by the very next paragraph of WP:ATD, which states If editing can improve the page, this should be done rather than deleting the page, as well as WP:PRESERVE. –&#8239;Joe (talk) 05:55, 25 October 2023 (UTC)\
 * Preserve is one of those constantly-misapplied and misinterpreted policies, so it's important to be extremely cautious when citing it. It says to consider alternatives; it's entirely reasonable for that consideration to end with "no, we're best deleting it." Certainly it is not equivalent to the flat statement that those alternatives must be considered. Likewise, the other bit you quoted has an obvious unspoken secondary aspect (which perhaps we should make explicit, but which is clearly there) - if the article has been improved to the point where it can't be improved further, and the problem is still there, then it should be deleted. All that it says, in other words, is that we shouldn't delete articles for problems that are reasonably fixable; it certainly doesn't mandate prioritizing redirection over deletion or anything like that. This proposal would go far beyond that and would make every alternative to deletion a hard requirement even in situations where deletion is clearly the best option. --Aquillion (talk) 04:25, 10 November 2023 (UTC)
 * Did you mean this to come off as a condescending, out-of-nowhere accusation that I don't understand core policies, or...? –&#8239;Joe (talk) 06:44, 11 November 2023 (UTC)
 * No, I just mean that it's important to be careful when bringing it up because people see things like this and it fuels the misuse of an already often-misapplied policy. It's narrow and cautiously-worded; I can understand why you'd cite it, but doing so in this particular context (where we're discussing something vastly more sweeping and aggressive) ultimately feeds into the "PRESERVE means you can't delete what I added without satisfying me first" misinterpretation of it, even if that wasn't your intent. Obviously a policy that says to try to fix problems and to consider alternatives is not the same as a sweeping proposal for a policy change that would mandate taking an option other than deletion. --Aquillion (talk) 17:08, 11 November 2023 (UTC)
 * An alternative outcome is generally preferable to deletion although there are obviously exceptions. If we are changing the status quo (and I'm not presently convinced of a need), then Jclemens' wording is significantly better than Mangoe's. It's not perfect, e.g. while I might think that merging X to Y is a good idea and justifiable on its merits, I wouldn't do it if the AfD hadn't showed a consensus against a stand-alone article and that seems to go against the "in the absence of the discussion" part. Thryduulf (talk) 12:33, 25 October 2023 (UTC)
 * I also disagree with the addition at issue (and have re-reverted it) because it asserts that alternatives "are intrinsically preferable to deletion". That is not so; for material that does not belong on Wikipedia (WP:NOT) deletion is generally the best and only option. Also, the statement that "If you would not take the action in the absence of the discussion, then it's probably not a good outcome" simply makes no sense to me; it is unintelligible.  Sandstein   16:57, 25 October 2023 (UTC)
 * If there is a viable alternative to deletion then that alternative is preferable to deletion. Something being NOT does not always preclude there being alternatives, e.g. in some cases the content can be merged and/or redirected to a relevant article or soft-redirected (or occasionally transwikied) to a sister project. Thryduulf (talk) Thryduulf (talk) 17:41, 25 October 2023 (UTC)
 * There is wording to the effect that editing and discussing is preferable to deletion. That does not apply to merging, deletion, incubation, and transwiki-ing, since it does not appear in the relevant sections for them or in a preamble to ATD. It makes sense that it would be like this - editing and discussing essentially result in keeping the article in mainspace, whilst none of the other ones do. FOARP (talk) 17:47, 9 November 2023 (UTC)
 * How does a redirect happen? An editor clicks the edit button and replaces a page with a #REDIRECT directive. The idea that 'editing' excludes redirection or merging is novel and unsupported by the plain meaning of the word's usage within the Wikimedia interface. Jclemens (talk) 05:53, 10 November 2023 (UTC)

WP:RFCBEFORE discussion about proposed addition to Deletion policy
I am starting an WP:RFCBEFORE discussion to get feedback about adding this paragraph to the introduction of Deletion policy: "When there is a viable alternative to deletion, that alternative is preferable to deletion. Alternatives to deletion include editing and discussion, tagging, merging, redirection, incubation, or transwikiing to another project. Despite there being an alternative to deletion, a page's history may still be deleted if it contains only biographies of living persons violations, copyright violations, vandalism, and hoax material." Is this wording clear enough? Should anything be added or changed? After receiving feedback, I plan to start an RfC to add this wording to the policy. There have been numerous previous discussions about Deletion policy at Deletion review. This includes Deletion review/Log/2022 January 28, where I shared my thoughts about this policy. This includes Deletion review/Log/2023 January 15, where wrote, "policy needs to give clearer guidance on this issue so we don't keep having to relitigate it at DRV every six months. I don't think we've had an RfC on weighting ATD arguments since 2011: it's absolutely time for another one". The last RfC I found discussing this was in 2015. Cunard (talk) 23:08, 29 October 2023 (UTC)


 * Your last list should probably have a catchall that says "or content that otherwise is WP:NOT." (and while I would link to TNT, that's an essay, and better not to tempt that). Even though you've worded it that there are other reasons why we delete, I can easily see some will game that to same "You're suggesting a reason to delete not given in DP#Alts! You can't do that!" M asem (t) 23:23, 29 October 2023 (UTC)
 * I agree that a catchall would be useful, but I've had trouble coming up with a good wording for that. or content that otherwise is not appropriate for an encyclopedia – linking to WP:NOT would include articles that violate Wikipedia is not a dictionary and Wikipedia is not a newspaper. It might be useful to merge articles that violate WP:NOTNEWS or WP:NOTDICT into another article, but the policy could be read as supporting deletion over merging in those cases. See also Thryduulf's here. I am open to other wordings as I think we should have a catchall. Cunard (talk) 23:49, 29 October 2023 (UTC)
 * Introductory paragraphs usually clarify and summarise existing content, but this proposal seems to represent a change of policy. All viable alternatives should certainly be considered seriously, but is there prior consensus that they are always preferable to deletion? Certes (talk) 23:31, 29 October 2023 (UTC)
 * There emphatically is not. What constitutes an improvement to a page is a matter of editorial judgement, not how well you time your "redirect to vaguely related target" vote minutes before an afd becomes closeable.  The single word "viable" is far too narrow a fig leaf to cover this.  Mangoe's version is a far more accurate representation of practice, and if you think differently, I can show you hundreds of deletions every day to show you're wrong, starting with virtually every G11. —Cryptic 23:52, 29 October 2023 (UTC)
 * I am open to suggestions from editors about stronger wording than "viable" to exclude alternatives to deletion that are unreasonable. Cunard (talk) 00:15, 30 October 2023 (UTC)
 * Mangoe's version is a much less accurate representation of the principles enshrined by existing policies and guidelines than any of the other suggestions I've seen in the past few days. That pages get deleted under G11 does not change this, because either they are so bad that editing them to be neutral or merging them to existing content elsewhere is not viable or they are being deleted incorrectly. Nothing that has a viable alternative to deletion should be being speedily deleted, if you know otherwise then please talk to the deleting admin and list them at DRV. Thryduulf (talk) 01:04, 30 October 2023 (UTC)
 * The problem arises in, again, the phrase "If editing can improve the page". That kind of decision has always, always been a matter of editorial judgment, subject to and requiring consensus on a case-by-case basis.  Compressing it to "viable" exacerbates the problem, and the rest of the proposed addition even more so.  The deletions I'm talking about are correct.  The policy change being pushed for here would make them incorrect.An example: the most recent G11 speedy when I started writing this was Draft:Deverrand.com.  That could have been chopped down to its first sentence to not be a G11 anymore, and - though it would have then been utterly useless as a draft, and an A7 if it had been in mainspace - it wouldn't be speedyable.  More to the point, it could have been changed to a redirect to, say, List of companies of India or Employment website, even had it been created in mainspace instead.  When you consider G11s of people, the targets start looking like List of Hondurans and Category:Indian children.  Since you're a regular at RFD, you know as well as I do that redirects like those would be deleted there, but also that they wouldn't be speedyable; and people who one would think would know better do propose or create such redirects (SmokeyJoe's 22:56, 7 February 2022 comment in this DRV sticks out in my memory).And the Deverrand draft isn't isolated or unusual; the most recent G11 speedy when I got a chance to work on this comment again was Draft:The Slink, which could've been reduced to its first and perhaps second and fourth sentences (again an A7 in mainspace but not a speedy in draft) or redirected to List of companies of Nigeria or Talent agent or Event management.  The most recent as I finish it up isn't a good G11, so I'll skip it; the one before that is Draft:Catalyst Sheep, which could've been stubbified to the first five words of its first sentence plus the second paragraph and not even been an A7 in mainspace.  Similar analyses hold for most G11s - there's a minority where not a single sentence is salvageable unchanged, but just about all could be turned into a bad but not speedyable redirect.  Other speedy criteria are worse - every single G13, for example, can be turned into a non-G13able draft simply by appending a period.  That doesn't make any of them bad deletions.But all this is a sideshow.  Speedy deletions aren't the target of this policy change, just particularly stark examples of how badly it conflicts with actual practice.  By saying, in essence, that any alternative to deletion is always preferable to deletion, like Cunard's version strongly implies and Jclemens's version said outright, we're giving a veto to every article creator who knows to say "redirect" - or, eventually, if this is successfully rammed through, "keep and edit as an WP:ATD" - six days and 23 hours into their pet article's afd, and at minimum, forcing another 7+ days at RFD.  It hasn't been until the last year or two that afd closers have stopped recognizing this tactic as the blatant gaming of the system that it is. —Cryptic 22:47, 30 October 2023 (UTC)
 * As others have pointed out, writing rules well is difficult. If an article says that Elvis Priestly is alive on the moon, and I fix the spelling, I have "improved the page", but not enough to make it a Keep. Certes (talk) 10:26, 31 October 2023 (UTC)
 * Deletion policy says in the "Editing and discussion" subsection, "If editing can improve the page, this should be done rather than deleting the page." This quote supports the view that viable alternatives to deletion are preferred over alternatives to deletion. There have been disagreements in past deletion reviews over this. Some editors (including I) think the policy does prefer viable alternatives to deletion, while some other editors do not. The introductory paragraph gives clearer guidance on the issue. Cunard (talk) 23:49, 29 October 2023 (UTC)
 * viable alternatives to deletion are preferred over alternatives to deletion Do you mean "preferred over deletion"? -B RAINULATOR 9 (TALK) 03:45, 30 October 2023 (UTC)
 * You are correct. I've fixed my comment. Cunard (talk) 05:21, 30 October 2023 (UTC)
 * Is any WP:ATD not covered under the umbrella of 'editing'? I do not believe any are, to include redirection and merging, and hence support Cunard's wording as adding nothing new to longstanding policy, just clarifying that the directive to use deletion as a last resort really does mean last resort. Jclemens (talk) 07:40, 30 October 2023 (UTC)
 * There's good reasons to believe that "editing" in the phrase "If editing can improve the page, this should be done rather than deleting the page" presently in the "Editing and discussion" section of WP:ATD does not include redirection/merging/incubation/transwiking. They include:
 * "Editing and discussion" and "Redirection"/"Merging"/"Incubation"/"Other Projects" are entirely different sections of ATD, all at the same level. "Editing and discussion" is not the preamble to the rest of the ATD section, it only relates to a specific alternative to deletion: editing and discussion, and tells us that this is preferable to deletion.
 * Logically, deleting the whole page and redirecting it to another page (a necessary step in both redirection and merging) is not simply editing the page to improve it, it is effectively deleting the page. Incubation also involves effectively deleting the page from mainspace, as does Transwikiing. A perfectly viable interpretation of "If editing can improve the page, this should be done rather than deleting the page" is that it tells us that "Editing and discussion" is preferable to deletion, or alterantively that it is preferable to all of the other ATDs as well as deletion, and not that all ATDs are preferable to deletion. FOARP (talk) 12:27, 9 November 2023 (UTC)

Assuming that an article does not meet one of the many Speedy Deletion criteria, deletion is not always the best approach to dealing with article content problems. Chief among the alternatives is Discussion and Editing. If editing can improve the article, this should be done rather than deleting the article.
 * Drop first subsection and craft into preamble is my alternate suggestion in a nutshell. This non-headered section can become something like the following.  Note that I'm focusing the section on articles as that is the focus of most general editors. --User:Ceyockey ( talk to me ) 01:08, 30 October 2023 (UTC)

If editing of the article has led to disputes among editors over article content, such disputes are not usually dealt with by deleting the article—except in the most severe of cases. Discussion on the article's talk page, pursuing dispute resolution methods and raising a Request for Comment are key ways forward from the dispute.

Some types of article or page content problems should be dealt with through alternatives to deletion as the first resort, among these being:
 * Vandalism: content added as vandalism can be reverted by any user (as long as the page is not protected from editing—yes protected and semi-protected pages can suffer from vandalism)
 * Verifiability: the article for an otherwise notable topic which severely fails verifiability should generally be reduced to a stub but could be discussed through the Articles for Deletion process.
 * Neutral Point of View: Some editors have been topic-banned or worse for repeated creation of biased articles. Biased articles can often be addressed through alternatives to deletion, sometimes involving moving the article due to a clearly biased title.  The goal would not be to quash a point of view, but to present the article topic in an unbiased manner.
 * Disagreements over policy or guideline: Typically this is not dealt with through deletion of the policy or guideline, or deletion of articles that adhere to a disputed policy or guideline.
 * Inappropriate user pages: These are usually dealt with through discussion with the user.
 * Violations of living person and copyright policies: These article content issues are usually dealt with through editing the article AND deleting specific old-versions of the article

Following are sections detailing several alternatives to deletion beyond the baseline discussion and editing approach.
 * --User:Ceyockey ( talk to me ) 01:08, 30 October 2023 (UTC)
 * Some of this goes too far in the other direction by excluding speedies entirely. I do think there is near-universal consensus, for example, that reversion to a non-speedyable version of a page is always preferable to deletion - sometimes accompanied by revdelling the intervening versions (such as copyvios or extreme vandalism), yes, but never the entire page. —Cryptic 02:17, 30 October 2023 (UTC)
 * I like a lot of the ideas expressed this proposed wording, especially "Violations of living person and copyright policies: These article content issues are usually dealt with through editing the article AND deleting specific old-versions of the article". I think it would be for the policy to include both some of this wording and the wording I proposed. Cunard (talk) 05:21, 30 October 2023 (UTC)


 * Comment. I think there are competing issues here that shouldn't be tackled together for procedural reasons. Any proposed introduction must come directly from the current approved language in WP:ATD and not add to or alter that language or shift nuance/emphasis. Otherwise its doing something other than summarizing. If the goal is to change content in ATD, than that should happen in an RFC discussing the language in the body of ATD and not in an RFC on a proposed summary. Best.4meter4 (talk) 06:41, 30 October 2023 (UTC)
 * I planned to propose this addition in an RfC. Do you think the proposed addition "add[s] to or alter[s] that language or shift nuance/emphasis"? If it does, where and how could this language about "preferring alternatives to deletion over deletion except in certain cases like BLP and copyright violations" be added to the body of the ATD? Cunard (talk) 06:47, 30 October 2023 (UTC)
 * @ I personally don't like the proposed language "preferring alternatives to deletion over deletion" because in my opinion it purposefully weakens all deletion arguments based on notability policy across the board by expressing a preference against deleting articles in policy language in favor of future editing that may or may never happen. One of my biggest pet peeves at AFD is WP:THEREMUSTBESOURCES arguments where sources are not actually found and produced. I can see ATD with this language allowing article to be kept because they "will get better with editing" someday, somehow, and by some unknown person who will find and add those sources that must exist somewhere even if in reality those sources don't exist and that editor never appears. I wouldn't support any language that places our options into some sort of hierarchal order. Each article should be evaluated individually with our options open to pursue deletion or an alternative on an equal footing.4meter4 (talk) 16:38, 30 October 2023 (UTC)
 * Look, if you don't want to work here, you don't have to, but the existing policy language preferring improvement over deletion is a longstanding part of Wikipedia that was here when I started 17 years ago. You're trying to suggest that the existing policy (If editing can improve the page, this should be done rather than deleting the page.) isn't policy and this clarification is somehow raising the bar to delete an article. The relevant policy goal is now, and has always been, per my paraphrase, "Improve stuff that sucks, delete stuff that doesn't belong in the encyclopedia even if it were to be improved, and organize topics into pages that makes sense." Deletion is not a way to improve overall article quality; that would be editing. Jclemens (talk) 19:25, 30 October 2023 (UTC)
 * @ Please remain WP:CIVIL and avoid personal attacks and overly hostile/aggressive tone. Given your history of WP:WIKIHOUNDING me in the past, I won't be responding to your comments further, other than to say I agree with your quoted summary of policy in the vernacular but disagree that the quoted text has the same nuanced meaning. Lastly, telling editors who have a different point of view then you to work elsewhere isn't in alignment with the collaborative spirit of wikipedia's guiding principles or supported by our policy at how an editor should behave in a WP:CONSENSUS building discussion. If this sort of behavior continues, I will report you to WP:ANI for a continuing pattern of harassment. 4meter4 (talk) 20:21, 30 October 2023 (UTC)
 * When you started editing Wikipedia, you agreed to join a collaborative project. The project had expectations, including the longstanding deletion policy wording I quoted. The fact that you disagree about the plain sense of words or the implications thereof isn't unique, but that doesn't mean it's correct, either. The fact that you see my post as a personal attack suggests you are too focused on how your opinions are received, rather than building an encyclopedia that necessarily relies on suboptimum and incomplete articles as building blocks for better articles. The immediately prior sentence, BTW, is far more of a personal attack than anything I wrote above. By all means, please report me to ANI for the torrid incivility in these posts. I'll bring the popcorn. If you choose to not (which would be a prudent choice, I believe), then please stop accusing me of various hypothetical high crimes and misdemeanors which have never happened... except, perhaps, in your own perception of my conduct. Jclemens (talk) 00:27, 31 October 2023 (UTC)
 * As I recall, I already reported you once before for WikiHounding me across several pages about a year ago and you were given a warning by an admin to leave me alone. Please stick to that.4meter4 (talk) 00:52, 31 October 2023 (UTC)
 * If you insist on posting to policy talk pages, you consent to interaction with all interested editors here. If you keep on focusing on your dislike of my policy-based argumentation and pretending that such constitute personal attacks, someone will likely tell you to knock it off. And, finally, if you post I won't be responding to your comments further, please do everyone a favor and comport yourself consistently with your freely chosen statements. Jclemens (talk) 18:30, 31 October 2023 (UTC)


 * If there are to be two proposals – one to change policy and one to summarise it – then they should occur in that order. To evaluate the summary properly, we need to know whether it explains current or revised policy. Certes (talk) 09:44, 30 October 2023 (UTC)
 * The disconnect, I suspect, is that some editors who disagree with policy as written believe that the proposal to summarize it is a proposal to change it. Jclemens (talk) 00:27, 31 October 2023 (UTC)
 * The concern I have about this proposal is the colossal impact it would have on our ongoing efforts to clean up after Lugnuts.—S Marshall T/C 10:03, 30 October 2023 (UTC)
 * Lugnuts is just one of several such efforts affected. Geostubs are another, with a "redirect" proposal to some larger geographical entity being often made as though it were required by ATD. As the instigator of this, my problem with the current wording of ATD is that IMO it encourages an "article rescue" perspective on the various alternatives. I'm not opposed an alternative when it makes sense, but to make sense, it has to be reasonable outside of the context of imminent deletion, and it seems to me that a lot of times this isn't the case. I don't think adding the word "viable" is enough, because everyone thinks their proposal is viable and we really don't have a standard addressing when it isn't except to argue over each case. The most typical problem with a geostub is that the article mischaracterizes the place in question, and that the real nature of the place tends force the application of GNG; thus people propose redirects when the enclosing place doesn't mention the place and is not likely to ever do so, or does list the place now— repeating the mischaracterization. Mangoe (talk) 22:25, 30 October 2023 (UTC)
 * That's not my perception at all. A few months back, I advocated that AfD be renamed 'discussion' precisely because that's what we've started doing: when an article is brought up, multiple alternatives are considered rather than deletion or keeping it unchanged. This is a good thing. As far as geostubs, I don't have any real knowledge of that area, and would welcome some explanation of why redirecting the article of some insignificant place that showed up in a database once, to the larger area or region in which that insignificant place appears, is a bad default. As always "Delete and don't redirect because this [isn't mentioned at the target|is confusing|is erroneous]" are always reasonable AfD entries. All ATDs do is expect that a discussion consider all, not just boolean, alternatives to make the encyclopedia a better place. Jclemens (talk) 00:35, 31 October 2023 (UTC)
 * Well, that's the thing: yes, those are reasonable responses to a "redirect" proposal. And I find myself having to make them constantly, and I find my objection on that grounds being ignored frequently. That's the origin of my "it has to be an reasonable/viable/consensus-able action in its own right, and not just as a defense against deletion" wording attempts: in the geostubs discussions when we are not arguing over WP:GEOLAND, we get "redirect" proposals which come across as "well, I can suggest some redirect, so you can't delete this." And there really is no consensus about this as a whole: in some discussions it works, and in some it doesn't, and much of the time it's not brought up at all.


 * Or to put the issue another way: it has seemed to me for a long time that the alternatives section comes with the implicit assertion that the most important thing is to avoid deletion, when (again, it seems to me) deletion is an outcome on equal standing with the others. Mangoe (talk) 13:14, 1 November 2023 (UTC)
 * Something like Lugnuts cleanup can be put into an IAR rational with community consensus - we have to delete it rather than consider other options because the community agreed there were major problems with them. M asem (t) 00:31, 31 October 2023 (UTC)
 * WP:LUGSTUBS and WP:LUGSTUBS2 resulted in the articles being moved to draftspace. Deletion policy is listed as an alternative to deletion in the current policy and in the proposed addition to the policy. This addition would not prevent continued efforts to move Lugnuts stubs to draftspace through community consensus. Cunard (talk) 07:25, 31 October 2023 (UTC)
 * The Carlossuarez46 Iranian "village" stubs were bulk-deleted. If this change had been made then, we would have had to have looked at every single one of the 13,157 "village" articles that were deleted to see if there was a viable redirect for them. FOARP (talk) 11:51, 9 November 2023 (UTC)


 * Editors have raised concerns about the wording of the proposed addition. The first concern is that "viable" in "a viable alternative to deletion" is not strong enough wording to prevent unreasonable alternatives to deletion from being adopted. Cryptic's comment sums up this concern very well. The second concern is that the wording would result in WP:THEREMUSTBESOURCES arguments being given weight in policy as 4meter4 discussed. The third concern is that the list after "a page's history may still be deleted if it contains only" needs a catchall. WP:NOT was proposed by Masem, but I think it's too broad because content that violates WP:NOTNEWS and WP:NOTDICT could still be useful in a merge as Thryduulf noted. Would editors help come up with drafting a wording that addresses these concerns while keeping the general idea that deletion should be avoided when there are reasonable alternatives to deletion? Cunard (talk) 07:25, 31 October 2023 (UTC)
 * "Even where a page is kept, there are various reasons why a sysop might need to delete one or more previous revisions".—S Marshall T/C 09:03, 31 October 2023 (UTC)
 * Is there more guidance we can give admins? "various reasons" gives admins broad discretion to delete previous revisions and could lead to more disagreements at deletion review. Maybe the wording could discuss factors like whether the history contains sensitive information that should be hidden from the public or whether the history contains information that editors find useful. Cunard (talk) 09:48, 31 October 2023 (UTC)
 * "Even where a page is kept, there are various reasons why a sysop might need to delete one or more previous revisions".—S Marshall T/C 10:44, 31 October 2023 (UTC)
 * WP:CRD is a good policy to link. Thank you, S Marshall. Cunard (talk) 09:29, 2 November 2023 (UTC)


 * @ I think a reference to WP:NEXIST would be helpful in determining WP:ATD’s application in regards to future editing and notability policy and sourcing; meaning that if sources are identified (as in a WP:BEFORE search) but not currently in the page that problem can be solved through future editing rather than deletion. However, if sources are not identified then deletion is preferable per GNG. At a bare minimum we need to acknowledge a preference for deletion in cases that do not meet the sourcing requirements at WP:SIGCOV. Obviously merge and redirects are ATDs that can be utilized in those cases when appropriate, but keeping the article because of a “future editing” argument is not an ATD that should be invoked in cases where sources have not been identified. Otherwise anybody can claim sources exist, not produce them, and have an article kept based on no evidence. 4meter4 (talk) 09:00, 31 October 2023 (UTC)
 * Deletion policy says, "If an article on a notable topic severely fails the verifiability or neutral point of view policies, it may be reduced to a stub, or completely deleted by consensus at Wikipedia:Articles for Deletion." This could be expanded to add a sentence before it, "If an article is on a topic where the existence of suitable sources cannot be found, it may be completely deleted by consensus at Wikipedia:Articles for Deletion when an alternative to deletion like a redirect or merge is not viable." Cunard (talk) 09:48, 31 October 2023 (UTC)
 * I would support that. One more side issue . Ever since we added ATD I am seeing more and more merge proposals brought to AFD without properly made deletion arguments. For example, right now we have Articles for deletion/France in the Junior Eurovision Song Contest 2020. As you can see from my stated opinion there I voted closing per WP:WRONGFORUM. I think we need to make it clear that AFD is not WP:MERGEPROP and we only take nominations where a valid deletion argument is made by the nominator based on either notability policy, WP:NOT, or deletion policy. Nominations that are essentially merge proposals will be closed as WP:WRONGFORUM. I also think we need to tell people to take all redirect proposals to MERGEPROP; even if there is no desire to merge content by the nominator (there could be by someone else). We really only need to take cases to AFD that involve deleting articles outright in the initial proposal. 4meter4 (talk) 10:03, 31 October 2023 (UTC)
 * Merge and redirect discussions on talk pages are more difficult to get consensus than AfD. Instead, we should centralize all contested merges, redirects, and deletions to the same venue. I don't support the proposal though because alternatives to deletion (even "reasonable" ones) are not necessarily superior to deletion. (t &#183; c)  buidhe  16:39, 31 October 2023 (UTC)
 * I'm not necessarily opposed to the idea, although it could have an unintended consequence of editors not bringing merge proposals forward, and it does limit a second venue for continued discussion in cases where a deletion attempt failed but a merge attempt might later succeed. I can see an editor wanting content merged in a nomination, only to find someone making a successful deletion argument after that. Hypothetically that kind of scenario could make editors wary of bringing forward merge props if they are afraid content might get deleted instead. On the other hand, it would raise the visibility of merge discussions, increase community participation, provide a more formal closing procedure, and create a more centralized and streamlined process for all the potential actions that could be taken with a given article. There would need to be some fundamental changes to the AFD nom process. The nom template would have to be updated to include the nominator's proposed action whether it be delete, merge, redirect, draftify, or undetermined, and we would need to reconsider renominations of articles under different action proposals and how to handle that. There would also need to be considerable amount of changes made on a variety of merge and deletion policy pages; all of which would need notifications placed on a future RFC discussion. It's certainly an idea worthy of wider discussion at an RFC. I honestly don't know whether there would be community support for this idea, or not. That said, under the current system we do need to clarify a separation between WP:MERGEPROP and WP:AFD that articulates AFD only considers nominations made with a deletion rationale based in policy for deletion; and merges are only considered in context to articles that have been properly nominated for deletion. WP:ATD isn't a substitute for WP:MERGEPROP; at least not yet.4meter4 (talk) 14:14, 1 November 2023 (UTC)
 * A couple of months ago there was a discussion I was involved in (and unfortunately I can't immediately find it) where it was suggested that the way forwards is a new central venue, with formal closes, for merges and splits that avoids them languishing for months or longer on poorly watched talk pages. This venue could be a discussion venue on the model of XfD or a listing venue on the model of RM, but I think it would avoid most of the issues 4meter4 brings up above. It would also avoid adding more workload to AfD (which is a common argument made against making it Articles for Discussion rather than Deletion). I think BilledMammal was also involved in that discussion so maybe they can remember more. Thryduulf (talk) 14:26, 1 November 2023 (UTC)
 * I remember that discussion, but I can't remember where it took place. I think my suggestion was for merges and splits to be included at WP:RM, but a new venue could also work. BilledMammal (talk) 14:31, 1 November 2023 (UTC)


 * that alternative is preferable to deletion. Is it though? This seems like something that should be discussed on a case by case basis (i.e. AFD) rather than something that should be prescribed by policy. – Novem Linguae (talk) 01:02, 9 November 2023 (UTC)
 * If editing can improve the page, this should be done rather than deleting the page. is longstanding, existing policy. Is there any ATD mentioned in this policy which does not fall under "editing" as used within the scope of this policy page? I note that "can" doesn't require that such improvement actually be done, nor does "should" preclude exceptions. Jclemens (talk) 03:18, 9 November 2023 (UTC)
 * You're the one hellbent on neutering "if editing can improve the page". You don't get to say language is longstanding policy is a reason to remove it. —Cryptic 03:33, 9 November 2023 (UTC)
 * I have no idea what you mean by that. I consider a redirection or a merger to be an improvement in cases where the policy-based alternative (note: Precludes TNT, which is a widely misused essay that actually says some sensible things and is a perfectly good essay absent its over/mis-use) is deletion. Including mergers and redirections under the heading of "editing" cuts both ways. Jclemens (talk) 04:00, 10 November 2023 (UTC)
 * There are some invisible words here, which are a Bad Thing in policy documents. Obviously the statement means "if editing can improve the page to a standard where it merits keeping ..." but it doesn't say that. Certes (talk) 09:58, 9 November 2023 (UTC)
 * Right. Our present standard does not deprecate deletion relative to redirecting/merging since these are also not editing the page so it can be kept, since redirection/merging are also not keeping the article. It does say that editing the article so that it can be kept is preferable, but that's it. FOARP (talk) 12:05, 9 November 2023 (UTC)
 * Those words aren't there, and I disagree that they were ever implied. Obviously, if you're going to insert words that aren't there into your understanding of policy, you're going to have disagreements with those who never understood them to be there. Jclemens (talk) 04:00, 10 November 2023 (UTC)
 * Since they’re in the section of ATD which deals specifically with editing and discussion the most natural reading is that this is what it refers to. Extending it to the other sections of ATD, that all involve effectively deleting the article from mainspace, does not seem a very logical reading to me. FOARP (talk) 08:30, 10 November 2023 (UTC)
 * Essentially agree with Mangoe, BilledMammal - deletion is a perfectly good outcome for an AFD discussion, and should not be deprecated relative to redirection/merging/etc.. Saying otherwise simply forces any redirect regardless of whether the target makes sense, and any merger regardless of whether there is any actual content to merge. A stand out example of this mindset can be seen at Close at Articles for deletion/Harry Oppenheim, a non-notable Austrian football player who was *not called Harry Oppenheim* (he seems to have gone as Heinrich, just called Harry on one database), yet we redirected "Harry Oppenheim" to a list of players on which this name does not appear, despite the existence of other "Harry" Oppenheims who were equally non-notable. Rather than encouraging such pointless redirection/merging, which merely serves to hinder clean-up of mass-created articles such as the LUGSTUBS, Carlossuarez46, and Antartica article-sets, we should instead discourage redirection/merging where it is merely being done as an alternative to deletion and not because it makes any actual sense. FOARP (talk) 09:53, 9 November 2023 (UTC)
 * You're noting a perfectly good case where redirection wasn't an appropriate outcome. I could list dozens--hundreds, over time--where deletion was used when there was a perfectly good redirect target. Can we agree that all articles that should be redirected rather than deleted should be redirected, and all articles that should be deleted rather than redirected should be deleted? Jclemens (talk) 04:00, 10 November 2023 (UTC)
 * I am noting a case where redirection was viable. FOARP (talk) 08:27, 10 November 2023 (UTC)
 * I do not see the situation as you describe it being a viable redirect--that is, one that preserves useful history, sends a reader somewhere sensible, and in general meets the goals and expectations of WP:R. No one is arguing that a pointless or worthless redirect be created when there's nothing to be gained over deletion, and that's why I disagree that the situation as you described it should be considered a viable redirect and hence it should not have been enacted as an ATD. Jclemens (talk) 23:43, 10 November 2023 (UTC)
 * No, this would be a drastic change in policy. The lead should be a summary; this is in no way a summary of current policy or practice. It's also vaguely worded, and to the extent that I can parse a meaning from it that meaning is awful and would represent an extremely undesirable change in policy and practice - what does "viable" mean? We can always theoretically rewrite or redirect an article; whether we do so or delete should depend on what the best option is (eg. how valuable would a redirect be?) Saying that we have to choose another option if it is "viable" for some vague handwavy notion of viability amounts to saying that we should redirect even if every editor agrees it would be a worse option, as long as someone asserts it is a "viable" one, which is total nonsense. More importantly, nobody has identified what problem this is trying to solve. As others have pointed out, the main problem we are facing is a flood of automatically or semi-automatically generated articles, which this would be moving in exactly the wrong direction on. I don't think there's anything productive being suggested here; I strenuously oppose the proposed change or any attempt to craft an alternative. --Aquillion (talk) 04:19, 10 November 2023 (UTC)
 * I also do not think this is a good idea. Deletion is a fine option for many articles. Wikipeida is already full of articles that, for various reasons, should not be there. Throwing more obstructions into the deletion process is NOT the way to improve the encyclopedia. - Donald Albury 16:17, 10 November 2023 (UTC)

Revising "If editing can improve the page"
WP:Deletion policy (permalink) reads: If editing can improve the page, this should be done rather than deleting the page. As pointed out by Certes (diff) and Aquillion (diff) above, this statement has unwritten qualifications. Cunard's original proposal lists a few exceptions, acknowledging this. Masem suggested adding a catch-all to cover any "other reasons why we delete".

I believe it is redundant to specify exceptions when they are already enumerated as WP:Deletion policy, one section up. I propose a change like this: If editing can address all reasons for deletion, this should be done rather than deleting the page.

To be clear, I am gauging interest before drafting an RfC. Flatscan (talk) 05:31, 11 November 2023 (UTC)
 * I like it. It ties "improvement" to deletability. I'm mulling over whether "all" might be better as "any applicable" or "all relevant," but that's a solid proposal. Jclemens (talk) 05:52, 11 November 2023 (UTC)
 * I support adding "applicable", "relevant", or a similar adjective to my original proposal as a second choice behind Cryptic's wording. Flatscan (talk) 05:20, 12 November 2023 (UTC)
 * The wording I'd been mulling proposing was "If editing can fully address the reasons for deletion, ...". In particular, I don't know that it's helpful to link further up the page to #Reasons for deletion, since it itself says it's not exhaustive. —Cryptic 06:23, 11 November 2023 (UTC)
 * My question then would be, what's the "reason for deletion"? It makes it sound like there's already a nomination and a specific problem identified, but ideally ATD should be applied before the deletion process has started. FWIW, I've always read this section as being a lot more basic than all that. Experienced editors take it for granted that we don't delete pages that, for example, are in need of copyediting, but this isn't actually self-evident to users unfamiliar with the wiki model – who maybe expect pages to be hidden in some backstage area until they're 'finished'. That's why the section goes on to explain things that are also obvious to all of us (disputes are settled by discussion, disagreeing with a policy isn't a reason to delete it). It's not trying to outline specific circumstances in which editing can overcome the del reasons (because these are all deliberately worded so as to be not addressable by editing), it's warning newbies that deletion is never our first resort. –&#8239;Joe (talk) 06:48, 11 November 2023 (UTC)
 * The reason is whatever the person contemplating deletion is contemplating deletion for, and got them to come and look at Deletion policy; whether or not we, as more experienced users, think it's valid in that case, or could ever be valid in any case. I don't think either proposed wording or the current wording are any more or less applicable than each other to, say, someone who's about to stick a delete tag on an article because "all it has on it now is a picture of pornography". —Cryptic 07:08, 11 November 2023 (UTC)
 * Cryptic's wording is my first choice, albeit with the link. It adds context, especially for a reader linked to ATD who may not know to scroll up. Flatscan (talk) 05:20, 12 November 2023 (UTC)
 * I changed my mind to lean away from "the" due to Joe Roe's comment. Flatscan (talk) 05:35, 20 November 2023 (UTC)


 * Comment. This would in effect nullify WP:TNT and places an unnecessary barrier to one of the best options at ATD, draftifying. I would prefer that we clarify that articles with significant editing issues such as tone, POV issues, major copyediting, or lack of sourcing, etc. are not always kept in mainspace simply because they may be improved through editing (although that is an option). In such cases, draftifying is an acceptable and encouraged outcome per WP:ATD and articles can be required to go through the WikiProject Articles for creation/Submissions process rather than simply languishing in main space in a horrible state in perpetuity. If no editor steps forward in a six month window to fix the draft, then the article will die a natural death as we delete old drafts. Stubifying would also be an option. I would like to see draftifying encouraged more overtly in policy language; particularly in cases where future improvement arguments are made at AFD. Future improvement is great if and when someone takes it on. We can encourage further editing and improve encyclopedia quality by taking care of those issues in draft space. I also note that this would be a useful tool to deal with the Lugnuts situation. Many of his articles could be draftified and remain there for interested editors to work on. A few would probably make it back to mainspace in a much better state, but others would likely time out and be deleted in routine draft deletion after enough time has elapsed. 4meter4 (talk) 16:47, 11 November 2023 (UTC)
 * All of WP:ATD - including draftifying - are subcategories of "editing". This shouldn't affect it. —Cryptic 17:17, 11 November 2023 (UTC)
 * I don't think that flows naturally from the present wording of the guideline. The sentence is only in the section on "Editing and discussion". The other ATDs involve essentially deleting the article from mainspace. FOARP (talk) 21:48, 12 November 2023 (UTC)
 * Also, in terms of page history, redirection was originally listed as a solution for "Problem articles that may require deletion", and Transwiki-ing was original listed as an outcome requiring deletion - i.e., both were originally considered a form of deletion. FOARP (talk) 22:04, 12 November 2023 (UTC)
 * I think most people view draftification as separate from deletion and therefore not covered by that sentence. Beyond that, I would say that the gap between If editing can improve the page, this should be done rather than deleting the page and TNT is perhaps bridged by the idea that the level of editing required to avert a valid TNT situation goes beyond what can reasonably just be called "editing" in the colloquial sense and requires completely replacing the entire page, ie. TNT is a situation that can't be resolved by actual editing because it doesn't treat "first step, erase all the existing text" as editing even if it's an edit in the technical sense. I suppose if it's a serious problem it could say something like reasonable editing or editing (as opposed to complete replacement) or if editing can use an existing article as a basis for a version that... or the like; and even without that I think it's plain that the sentence imagines a scenario where it is possible to repair the article by editing what is already there rather than replacing it wholesale. (It might also be useful to add another sentence somewhere noting that the situation where "unreasonable" editing would be needed to avert deletion is somewhat different than other types of deletion in that it should at most result in draftification or deletion without prejudice towards the creation of a new article.) --Aquillion (talk) 17:21, 11 November 2023 (UTC)
 * I think both of you are underestimating the type of editors that argue policy at AFD discussions and the sorts of arguments they will successfully make with the above language. The opening statement as written will place a hierarchy in decision making which will become an impediment to draftifying articles as an outcome at AFD. I've seen enough parsing of policy language in discussions to know that this will happen and will be effective. We need to outright state what the options are and not place an emphasis on a particular option such as future editing in main space. As written, this is not a policy language I would support. We need to clarify specifically what types of actions can be done and avoid prescriptive overarching statements that could be parsed to prevent other types of reasonable and useful options.4meter4 (talk) 17:29, 11 November 2023 (UTC)
 * Do you really think the current wording that only says "if editing can improve the page" is better? It seems to be a clearly lower bar to me. —Cryptic 17:35, 11 November 2023 (UTC)
 * Redirection/Merging/etc. are not "editing and discussion". FOARP (talk) 09:20, 22 November 2023 (UTC)
 * Sure they are. I've said so multiple times above, and have yet to see a convincing rebuttal. Editing is anything that doesn't require the admin tools. To make a redirect, including a merge, you click on the 'edit' button and change the page. That's editing. Jclemens (talk) 09:47, 22 November 2023 (UTC)
 * "Editing is anything that doesn't require the admin tools." - When was the last time you saw someone with no tools at all draftify something?
 * More essentially, every ATD but "editing and discussion" involves deleting the article so that there is no longer an article with that name on Wikipedia from the perspective of the average reader. This is reason enough by itself to distinguish between "editing and discussion" and the other ATDs. Indeed, I'd question why anyone would want to put "editing and discussion" at the same level of preferability as redirection, since for "editing and discussion", if viable, we still have an article, whereas with redirection the article is essentially no more. In the original guide redirection and transwikiing were listed as was of dealing with "problems that may require deletion" so it's simply not true that these have always just been considered versions of editing. FOARP (talk) 12:42, 22 November 2023 (UTC)
 * Oookay. Some large part of disagreement here is that you're using the same words I am, but we're meaning very, very different things by them. We've both been on-Wiki for well over 15 years, so it's puzzling to me that this is the case... but it is. As far as draftifying needing tools, it LOOKS like it works for me with the full non-admin toolset, but I'm not going to try to move something out of mainspace to test. I understand that a non-admin moving a page from mainspace to draft would need to tag the redirects as G2 rather than deleting them directly, but I still 1) wouldn't really call that an admin action and 2) note that the existing policy wording predates the implementation of draftspace. So basically... it's still editing.
 * As far as deletion goes, absolutely not. Redirection or merging allow non-admins to see the page history, even if they have to work at it and know what they're doing. The page may not exist any longer, but the content is just one edit away from coming back. Admins can delete/undelete/revdel things, not the editor corps at large. To cast a 'delete' vote in AfD means "I want only admins to be able to see this content when this is concluded" and that is why I find straight deletion as an often unnecessarily hostile outcome. We absolutely want to delete every bit of G10-11-12 content: burn it with fire. But most non-notable content doesn't rise to that level of harmfulness. Someone did a big list article that we don't need, but it might work somewhere else? Great, let them fetch it from the page history and reuse it elsewhere.
 * As far as order of preference goes, I don't know that I've asserted order among the non-delete options, but now that you mention it, yes, I agree: editing the text should be preferable to merging or redirection. Jclemens (talk) 03:15, 23 November 2023 (UTC)
 * (EC) I tend to agree that flat "do this" statements should generally be avoided in policy unless it is absolutely necessary (ie. for core policies, or for vital stuff like WP:BLP) - whether we delete borderline pages is definitely not one of the situations where we need that. But, as Cryptic says, the current version of the text is already being interpreted that way, so the proposed edit (which merely adds a qualifier to avoid absurd situations where editing could rearrange the deck chairs, so to speak, without being able to address a core reason for deletion) would still be an improvement, even if it doesn't solve everything. If you think we also need a qualifier to point to in situations where someone argues against deletion or even draftification because they could theoretically blank the page and then write something totally different in its place (without being willing to actually do it, because if they actually did it then the deletion discussion would be moot)... then try and think of some other wording to avoid that problem. I made a few vague suggestions in that direction. --Aquillion (talk) 17:39, 11 November 2023 (UTC)
 * I think a simple addition “If editing in either main space or draft space can improve the page…” would solve the issue. We can then add a sentence about making the decision to edit in main space versus draft space.4meter4 (talk) 17:49, 11 November 2023 (UTC)
 * Stubifying has advantages over draftifying, in that incoming redirects stay intact and incoming links, including dab page entries, stay blue. If an article is moved to draftspace, all the effort editors may have put into creating redirects is wasted, links from other articles will quite probably be unlinked by editors who dislike seeing red links, and any dab page entry will be deleted as invalid, just as with deletion. Stubifying, if the article has a couple of RS enough to show notability, can be a much more useful outcome: remove the unsourced / promotional / POV/ incomprehensible etc stuff and leave the reader with something better than nothing. Pam  D  18:22, 11 November 2023 (UTC)
 * Well said. Draftifying is backdoor delayed deletion in that it removes an article from the encyclopedia's radar and sets a timer for automatic deletion. It's an option, but nowhere near as preferred as stubbifying, redirecting, or merging. Jclemens (talk) 09:07, 12 November 2023 (UTC)
 * Agree that moving to draft with essentially automated G13 is just delayed deletion unless an editor agrees to improve it, in which case why not userify? Stubbing is definitely a preferable option in most cases. Espresso Addict (talk) 12:05, 12 November 2023 (UTC)
 * I agree with Cryptic and Aquillion that we should move forward with the change as proposed and consider 4meter4's concerns in another iteration. Aquillion wrote a few good ideas for TNT; an alternative is adapting from if practical in WP:Deletion policy (permalink). Flatscan (talk) 05:20, 12 November 2023 (UTC)

I tweaked the proposal to add "relevant" as suggested by Jclemens: If editing can address all relevant reasons for deletion, this should be done rather than deleting the page. If I made this edit, would anyone object and/or revert? Flatscan (talk) 05:35, 20 November 2023 (UTC)


 * I would certainly oppose any edit of the guidelines that deprecates deletion relative to the other ways of resolving article problems that are not "Editing and discussion". FOARP (talk) 09:20, 22 November 2023 (UTC)
 * Then you're arguing for a policy change, because deletion is already deprecated by the current wording, no matter how much several editors don't like that it is. Jclemens (talk) 09:48, 22 November 2023 (UTC)
 * "deletion is already deprecated by the current wording" - relative to "Editing and discussion", yes, but not to the other ATDs. If it meant to say otherwise, it would say otherwise. FOARP (talk) 12:27, 22 November 2023 (UTC)
 * FOARP, would you clarify the connection between your comment and the proposal? I am not following how the edit – confined to one clause in the Editing and discussion subsection – does what you're concerned about. Flatscan (talk) 05:32, 23 November 2023 (UTC)
 * If that is where it is going to be done then I have no objections. FOARP (talk) 09:18, 23 November 2023 (UTC)

I made the change after seeing no new objections in two weeks. Flatscan (talk) 05:25, 5 December 2023 (UTC)

Use alternatives to deletion wording from AfD editnotice as inspiration
Template:Editnotices/Group/Wikipedia:Articles for deletion says: "When discussing an article, remember to consider alternatives to deletion. If you think the article could be a disambiguation page, redirected or merged to another article, or moved to draftspace for incubation, then consider recommending 'Disambiguate', 'Redirect', 'Merge', or 'Draftify' instead of deletion. Similarly, if another editor has proposed an alternative to deletion but you think the article should be deleted instead, please elaborate why." I recommend using this wording as inspiration for drafting an introduction for Deletion policy. The wording reminds AfD participants to consider alternatives to deletion. It does not take a position on whether deletion or alternatives to deletion should be preferred. What do editors think? Cunard (talk) 12:12, 17 November 2023 (UTC)
 * This isn't a bad start. I do think the presumption should be in favour of an ATD unless those opposing it have adequately explained why they believe deletion is preferable to that alternative. "Adequately" is the tricky word here, but if the argument doesn't convince anyone else or doesn't make sense according to policy/precedent or it's just an "I don't like it" then it obviously isn't adequate, conversely something like "redirection isn't suitable here because several similar redirects have been deleted at RfD" or an argument that convinces multiple people who were in favour of the alternative then it obviously is adequate. Thryduulf (talk) 11:00, 18 November 2023 (UTC)
 * Noting, for the record, that the sort of case that makes me see red isn't where a suggested ATD hasn't been opposed; it's where there hasn't been a chance to oppose - such as being suggested shortly before an AFD is closed, or not having been mentioned before the AFD closer took it upon themself to do it without anyone at the AFD mentioning it. If you see an AFD that reads delete (with normally-acceptable reasoning), delete (ditto), delete (ditto again), delete (yet again), and a bare "redirect to some other article ", it's unacceptable to halt the discussion there and say there's consensus to redirect.  Even if you know that DRV hardly ever overturns anything to delete no matter the provocation. —Cryptic 00:37, 19 November 2023 (UTC)
 * Certainly if we require those opposing an ATD to adequately explain why they oppose it they must be given the opportunity to do so. A last minute ATD !vote should lead to relisting, but several deletes and an ATD in the first couple of day or so followed by multiple days of silence can be closed in favour of the ATD (note not must be so closed). Thryduulf (talk) 16:49, 20 November 2023 (UTC)
 * @Thryduulf - This is why "any ATD is better than deletion regardless of how tenuous the case for it is or how clear the consensus in favour of deletion is" is just a massive spanner in the works at AFD. It means repeated relists as we struggle to agree on a redirect/merge that essentially Does. Not. Matter. because we're already in agreement that the article has to go. It often results in the third most supported option at AFD being the one that passes, simply because it's not deletion per se even if it has practically the same effect.
 * "Merge" closures for articles that have no actual sourced content that is worth mentioning at the merge-target are something that needs to die. Articles for deletion/17 km, Sakhalin Oblast was a particularly bad example of this - 7 delete !votes and 4 keep !votes, then 4 merge !votes (after re-lists made it obvious that the closers weren't going to close as delete) for a merge that ultimately no-one carried out because there was no mergeable content, to a merge-target that made no sense at all given that it is a much larger city of hundreds of thousands of people and we were talking about a place that was essentially a single house with two people in it. Because of the repeated relists this process took weeks of time when the consensus that the article had to go was already very clear no later than by the end of the first relist, and it was only the idea that we had to find a merge/redirect rather than simply delete that made this happen.
 * Editor time is a valuable resource. Don't waste it with this kind of snipe hunt. FOARP (talk) 09:43, 22 November 2023 (UTC)
 * You say massive spanner in the works like it's a bad thing. We can't delete sucky articles to achieve a good product--we have to create a collaborative environment that entices people to fix the sucky articles. Just the other day we had a valued contributor complain that their improvement work was lost with a redirection during AfD. That's the sort of work we don't want to stomp on while fixing sucky articles, because if those folks inclined to fix them leave, then we are well and truly screwed. Jclemens (talk) 10:00, 22 November 2023 (UTC)
 * If multiple people are supporting an ATD then deletion is not the correct outcome, even if you personally would prefer deletion. Merges not being done is a problem, but not one that is particularly relevant to this discussion (as it's much broader). If there is no mergeable content (and in my experience that's claimed far more often than it is true) then a redirect is appropriate as it maintains the link people desire. I also agree with Jclemens. Thryduulf (talk) 11:40, 22 November 2023 (UTC)
 * @Thryduulf - "If multiple people are supporting an ATD then deletion is not the correct outcome" - Forgive me for possibly being too literal here, but simply because a number of votes for merge/redirect have been cast in a discussion that is two or greater, is not a reason why deletion is not a perfectly good outcome for that discussion. Two or more people can totally be wrong about something, simply having a couple of drive-by merge/redirect !votes in an AFD is not a reason not to just close it as delete if there's already a consensus in favour of that.
 * Merges not being done is a problem because it means that merges are being !voted for that can't/won't be done because either there's no actual sourced content, or the merge target is basically wrong. It renders the whole process of arguing out the merge at AFD a completely wasted effort.
 * AFD is already clogged and already understaffed, why make things even worse? Just delete where there is already a consensus to delete, and in the limited number of cases where there was mergeable content, if the information truly is relevant to the page that it could be added to, someone will add it there eventually.
 * @Jclemens - "We can't delete sucky articles to achieve a good product". Strong disagree here. We absolutely totally can straight delete articles and achieve a better product by doing so, when those articles detract from the quality of the product. Redirection is, anyway, effectively deletion from a reader's POV since the article is no longer there, it just takes us much longer to arrive at and do. FOARP (talk) 12:25, 22 November 2023 (UTC)
 * Redirection is not deletion from a reader's point of view. A redirect takes people to content relevant to the search term they used but deletion gives them nothing. Search results (which may be multiple clicks or taps away, depending on the combination of the method they were using to find the content, what device they are using, whether they have the permission to create a page at the given title, etc) might or might not be relevant, or even available at all. Thryduulf (talk) 12:50, 22 November 2023 (UTC)
 * "A redirect takes people to content relevant to the search term they used" - Does it always? Or does it sometimes land people on pages where the topic is not mentioned at all because "Redirect/merge per WP:PRESERVE" is apparently a more valid !vote at AFD that any amount of explanation as to why the article should be deleted? FOARP (talk) 13:35, 22 November 2023 (UTC)

This is better as it does not deprecate deletion relative to redirection/merging etc. FOARP (talk) 16:34, 20 November 2023 (UTC)
 * This is talking about talking about articles. Policy still favors ATD over deletion, even if the instructions to participants don't call out that explicitly. Jclemens (talk) 09:51, 22 November 2023 (UTC)
 * "Policy still favors ATD over deletion, even if the instructions to participants don't call out that explicitly." - The thing about policies that ain't written anywhere is, they ain't policies. It may be that some closers favour all ATDs over deletion, but that's on them. The guideline we have right now only does this for "Editing and discussion". FOARP (talk) 12:30, 22 November 2023 (UTC)
 * Interesting perspective, but the first section is the general guidance for the entire ATD process. the next several sections of ATD are clearly editing actions: Tag something? Gotta edit it to add a tag. Merging and redirection? Same thing. WP:ATD-E links to WP:E which includes the entire section WP:PRESERVE. I get where you might be thinking that based purely on hierarchy levels... but then where it the general ATD principle? How would the proposed interpretation be consistent with WP:DGFA, specifically the When in doubt, don't delete directive? Jclemens (talk) 03:26, 23 November 2023 (UTC)
 * That's about assessing the consensus, with no-consensus outcomes resulting in the article being kept, not about all ATDs being superior outcomes to deletion. Realistically, the same "when in doubt, don't" also applies to redirection, merging etc. - if you doubt whether there's a consensus in favour of these, then default to keep. Interpreting it otherwise means assuming that in a doubtful situation between keeping and another ATD, we can draftify/redirect etc., but closers don't do this.
 * "the first section is the general guidance for the entire ATD process" - it says "Editing and discussion" right there above it. It's very clear what it's talking about. It only discusses two cases in that section ("Editing and discussion" and "deletion"). If it was intended as a general statement about all ATDs it would include the other ATDs, but it doesn't.
 * More basically, keeping should always be favoured as an outcome to all of the other ATDs and deletion where it is viable and it makes sense to interpret it this way. Draftification/trans-wikiing mean we no longer have the information on that page in main space. Redirection means we no longer have the information on that page unless it happens to exist on the target page (and it may well not). Merging means we no longer have an article with that title that is easily discoverable. All of the ATDs other than "Editing and discussion" result in us no longer having an actual encyclopaedia article with that title.  FOARP (talk) 09:12, 23 November 2023 (UTC)
 * So I think that, despite serious disagreements remaining, we're converging on a consensus that, when appropriate and in line with our content policies, editing the content of the page is better than merging or redirecting, which are in turn better than transwiki'ing or draftifying, which are in turn better than outright deletion. Jclemens (talk) 17:05, 23 November 2023 (UTC)
 * I wouldn't necessarily rank them that way, I'd say that keeping where viable is better than deleting, but the others really depend on the context of the article. I wouldn't say redirection is really that different to deletion in 90%+ of the cases discussed at AFD in terms of outcomes for the reader, except that redirection takes far more time to achieve. Draftification also is very often exactly the same as deletion - I've been open about supporting it in the LUGSTUBS case for exactly that reason. Merging, in the way it is so often !voted for simply as something that is "not-deletion", is little different to deletion. Transwikiing is something I've almost never seen actually happen, but when it's voted for it's always just as a way of getting rid of the articles.
 * WP:PRESERVE abjures us to preserve what we can preserve, but there's different ways of doing that and they needn't go into a hierarchy. FOARP (talk) 14:15, 24 November 2023 (UTC)

"Other issues" section
The first image in "Other issues" section has wrong caption. This type of page is also seen by normal users. Sarangem (talk) 09:37, 10 December 2023 (UTC)
 * No, non-admins will not see the "view X deleted revisions" link. Primefac (talk) 10:08, 10 December 2023 (UTC)

Want
We shouldn't be so eager to delete stuff, it makes people not want to edit Wikipedia. I've heard this from so many of my friends, too. Benjamin (talk) 12:15, 3 January 2024 (UTC)
 * Do you have a suggestion? Primefac (talk) 12:18, 3 January 2024 (UTC)

==Discussion at Wikipedia:Village pump (policy) § RfC: Should a special PROD category, similar to WP:BLPROD, be created for unreferenced tagged articles?== You are invited to join the discussion at Wikipedia:Village pump (policy) § RfC: Should a special PROD category, similar to WP:BLPROD, be created for unreferenced tagged articles?. 0x Deadbeef →∞ (talk to me) 15:40, 10 January 2024 (UTC)

Discussion at Wikipedia:Village pump (proposals) § RfC: allow soft deletion of unopposed nominations
You are invited to join the discussion at Wikipedia:Village pump (proposals) § RfC: allow soft deletion of unopposed nominations. House Blaster talk 01:19, 13 January 2024 (UTC)