Knowledge talk:Criteria for speedy deletion/Archive 81

7549:, and leant weight to their creation by writing a Knowledge article about "ABN Assets" (including, quite naturally, the external link). Articles like this are almost certain to get deleted eventually, but the longer they sit there, the greater the number of people who get scammed before we catch up, and the greater the incentive to scammers to write more scam-articles. At the moment they don't quite fit any category. The nearest match is the blatant hoaxes bit of G3 (vandalism and hoaxes), but scam articles aren't vandalism, and have quite a different appearance to a hoax; a successful scam page isn't pushing belief to the very edge, with a weird tall story, it's just a rather dull page about a financial services company. Even the external link isn't necessary, because the scamee probably knows it already. The articles aren't covered by G11 unambiguous advertising, because they don't need to be written in an advertising style; they're not there to advertise, just to look solid and respectable. 5785:(replies to various people) I think we could adjust the standard of A2 to use the same "does not expand upon, detail or improve information" wording as A10 without causing any issues, and Google Translate is usually good enough to determine whether it is plausible something meets that standard or not (and if it's unclear we should be defaulting to not speedy deleting it until someone who speaks the language can look at it). That would solve most of the issues Hut 8.5 raises I think without changing the spirit of the criterion. Indeed, there would be no change to the G criteria, nor the other A criteria so copyvios, spam, incoherent foreign language material, obviously non-notable topics, etc. would still be able to be deleted as now. The only significant change would be to material that is in a foreign language and does not duplicate content that already exists elsewhere. I forgot to link to the situation that sparked this proposal - 3442:, I don't think you've considered this) At present I regularly patrol the 5+ month category, which is in roughly chronological order. Out of each group of 200, I find about 10 that I think merit further consideration. A few are those that had been declined improperly, and could be accepted; more are ones that have been properly declined, but never looked at again. Some have never even been submitted, and a few of them would be immediately acceptable, but more after a little fixing. (about 1/3 of each group are suitable for merge, rather than as separate articles--they've often been marked for merge, but nobody has merged them--dealing with most would be quite easy.) The true number rescuable is probably twice that, because I do not look at sports or popular entertainment, two fields where I'm incompetent, but many others here would be knowledgable. 4141:. I am somewhat persuaded by the notion that some drafts may be watched by non-admins, and these watchers (who might potentially help) don't get a notification that a draft is soon to be deleted, and they may not know what the draft is once it's deleted. On the other hand, I doubt this happens often enough to really worry about. Overall, I have mixed feelings about G13 vs. DRAFTPROD. I wish that there were a prod-type mechanism for submissions other than businesses, products, bands, and living people (and maybe some additional categories of almost-certain-to-be-garbage that I'd have to think about... these categories make up most of the garbage drafts, though not all). There is some good stuff that gets deleted, but I'm not sure that giving an extra week will do anything. I highly encourage others to monitor 3855:: looks to me like people who are saving drafts from deletion are saying this would be useful to them, and people who are not doing this are saying that they shouldn't find it useful. I'm going to go with the people actually doing this. Several credible use cases for this have been given, and as we already have some delay conditions in our CSDs, I don't see that this would cause any particular pain in practice (the drafts have been sat there for six months so it's not a problem for them to sit there for another week). And the OP is right that they anticipated and pre-emptively gave strong arguments against the most common objections; people should not really be opposing unless they read the initial proposal and can explain why the given counter-arguments are unsuitable. — 8029:. Any station granted a terrestrial radio broadcast license has an implicit claim to significance (given the available spectrum is finite and most countries have regulations about content, etc, they will need to be satisfied are/will be met), similarly any article about a station that has been actively rejected for such a license is also claiming significance (this would need mentioning in the article, and excludes things like non-serious and very-clearly-never-stood-a-chance applications). Low-powered stations like in the example fall into a class between regional stations (licenses are somewhat rare) and buildings (licenses are extremely common), but are often going to be notable in the context of their broadcast area so if there is content that meets 2922:'s lists of new pages for relevant articles and drafts, and adds some potential drafts to their watchlist, or tags the draft talk pages with relevant WikiProject banners. Naturally, the editor wouldn't want to interfere while the draft creator is still actively working on it. But if the creator stops editing and the draft becomes stale, the active editor is unlikely to notice until six months later, when the G13 tag is placed and the draft is almost immediately deleted. Adding a delay of, say, one week between tagging and deletion will give a chance for the active editor to take a look and maybe rescue the draft, without having to go through the hassle of a REFUND. If such a delay is implemented, it could also be integrated with the 5828:

If the answer is that it's useless then it can be speedily deleted under A2, which (unlike A10) has no time limit. Just note somewhere (in the tag, on the talk page, in your own log somewhere) that a speaker of the language has been consulted. Speedy deletion is explicitly only for pages that should obviously be deleted. If it is not obvious we should not be speedy deleting regardless of language, and the check required is significantly less overhead than would be an unjustifiable burden. The bottom line is that we should not be deleting content that is useful to another project simply because we cannot be bothered to do a little work - doing that is fundamentally at opposition to the basic goal of the project.

5812:. Google Translate renders part of the lead as "He is considered one of the greatest statisticians in the world. He has made significant contributions to the field of numerology", which is complete rubbish - he's not a statistician or a numerologist. So either Google Translate is making a mess of it or it's a very poor article, and even though the Bengali Knowledge's article on Andrew Wiles is short I'm not sure it's worth us offering it to them. Under this proposal I would have to contact someone at the Bengali Knowledge to see if they were interested in merging that article with theirs, and if they weren't interested then I would have to send it to PROD or AfD. That's a lot of overhead for not much benefit. 2810:. Many editors expressed skepticism that adding a one-week delay to G13 deletions would actually achieve the benefit that the proposal seeks. If the desired outcome is notification of editors who might be interested in the draft (e.g. WikiProjects), some editors pointed out that this notification could be sent at some point before the draft becomes eligible for G13 and that this would avoid adding unnecessary complexity to the deletion process. Some editors also expressed openness to the idea of replacing G13 with a DRAFTPROD process, but additional discussion is needed to determine whether that is something this community desires. Respectfully, 5975:

either (category C). Those in cat A get put in the main queue and given a few months to be worked on (maybe putting them in draftspace and made eligible for G13 if nobody touches them? they would need adding to a category and/or list so people know they exist but that's trivially easy to do); Category B articles get put in a transwiki queue and then A5 speedied when that is done. Category C articles get tagged for A2 speedy. Whether something that has been transwikied is useful for the destination project is entirely a matter for the destination project, they can do whatever they like with it (in accordance with their policies of course).

4968:

all the participants have recommended deletion (as in Reyk's examples above), then speedying will usually be appropriate. Though even then it's worth pausing to consider if there might not be other considerations at play: for example, has the nominator deliberately chosen an AfD over speedy tagging, for example because of a previous speedy getting declined? Also, there is a difference between the two outcomes in the case of recreation. A speedied article can usually be recreated, whereas a proper AfD that concludes the topic isn't notable can effectively put a stop to further recreations in the near future. –

3877:

has to be able to scale. I have worked with the stale draft pages daily since September 2020 and the number of aging drafts expiring each day is anywhere between 150-400 drafts, with an average of about 200-225 drafts expiring each day or at least 1500 drafts/week. So, whatever change is made won't be to one draft that might be of interest to you but has to work with hundreds of drafts, daily. By comparison, I also work with PRODs and the daily number of PRODs expiring is between 20-40 articles/day. Multiply that times 10 and that is what you will be working with.

4266:- 6 months is more than enough time for abandoned drafts to be rescued—that's the point of the six months to begin with. I'm all for efforts to save potentially useful drafts, but that would reasonably look like a task force or Wikiproject that monitors abandoned drafts that are approaching deletion and sends out notifications to interested parties who have opted-in to the task of reviewing and working on abandoned drafts, all before the 6 month deadline ever hits. Jamming up the project-wide deletion process, which is already lenient and reasonable, for 3890:) and review drafts that will be expiring soon. It would be much, much easier for editors to review the entire G13 soon list on a regular basis than to institute major changes in how stale drafts are handled when there are at least a dozen editors and admins who currently work with them. The SDZeroBot G13 soon list already gives you a week's advance notice on which drafts are due to expire which seems to be what some folks here are asking for. Final word, there might be easier alternatives to achieve your goals than scrapping the current system. 3680:. This would just make deleting these drafts even more complicated. The editor with the stale draft definitely has enough time to choose to edit it and they get a notice at 5 months. I think we need to encourage people to edit drafts. We could do this in lots of different ways (giving them another notice about the possible G13 earlier on, encouraging people to help edit promising drafts, etc.) but the deletion criteria should not be changed. I think it is fair as it is, especially as they are usually undeleted if you go to 2449:, moved to main space and, basically, immediately tagged for deletion and deleted. And yet, this is the route that I tell editors to use if they want to overcome an AFD deletion decision. In general, beyond this particular article, shouldn't AFC approval count towards keeping an article? I know some admins carefully check previous, deleted versions of tagged articles to see if problems have been addressed but I don't think this happens every time based on how quickly these pages are tagged & deleted. 2308:

draftspace, and 2) can be caught by G3. So really, this would only cover people running unrelated-to-wp personal stuff through draftspace like the fantasy sports or alternate history, and I'm not sure how much the draft space gets those, as those generally go through userspace from what I've seen. There's plenty of junk drafts where people write about their pets or minecraft servers, but those can be disposed of in six months when the G13 garbage collection truck makes its rounds. We don't need to be

31: 6939:, where it was determined that such a redirect would prevent displaying a search result in the case of multiple other pages making mention of the subject, I'm starting to think: maybe a speedy deletion criteria would save the trouble of going through RFD to get such redirects deleted? Would a speedy deletion criteria for these types of redirects be something that can be achieved at all? And if so, can we set some kind of threshold on search results for such a criteria to apply? 5261:. Common sense and good judgment should apply, and an XfD might provide a reason a page should not be deleted in spite of a CSD. However there is no such procedural technicality that an XfD precludes a CSD from being actioned. Such a thing simply doesn't exist. I haven't worked at XfD or CSD for a while, but when I did I remember these situations being somewhat common, and actioning an applicable CSD was never viewed as contentious simply because an XfD had been opened. 4905:

the hope of someone else fixing them is a bad strategy. But deleting the original page also erases information about the redirect: about when it was created (it makes a difference when handling a redirect whether it was created yesterday or has existed for a decade), what history it's had (maybe it's had a different target in the past), and who created it (relevant, for example, if it later turns out that the user in question was a purveyor of subtle hoaxes). –

2776:. Passing AfC is merely the judgment of a single reviewer that the article is like to survive a deletion discussion. It certainly doesn't exempt from afd, and it shouldn't exempt from speedy when there is a clear reason. Reviewers don't always notice everything, and if an admin see something wrong that has been overlooked , and G4 is one of the things that are very often overlooked, they ought to proceed accordingly. Naturally, they should do it carefully. As 8220:

specific uncontroversial criteria; these criteria are noted below." → "If a page has survived its most recent deletion discussion, it should not be speedily deleted unless external circumstances have changed, such as newly discovered copyright infringement or a redirect's target having been deleted; in particular, criteria A7 and G11 are never appropriate." (I used one of G8 as the second example more or less at random; I'm not even convinced we

6550:. Now, my first thought at seeing this was "Yeah, that's not how we do stuff here". But then, why not? People have used chat services to coordinate various aspects of work onwiki, so it makes sense to think about ways of bringing that activity here. Is this draft the way to do it? Most likely not, but there's nothing wrong with people experimenting. There's no harm to the project here, so I see no need to rush deleting before the G13 deadline. – 5753:

direct copy/paste of an article on a foreign language Knowledge. If that's not the case then it may well make no sense to transwiki it, as they likely won't want it if it covers a topic they already have. So under this proposal if someone were to write an original article here about Germany in German then it would have to go to AfD or PROD, because the German Knowledge already has an article on that topic. I don't think we'd gain much from this.

3946:

hours before, which is far too soon to contest it. A list of all G13 deletions doesn't help with that at all. What are they supposed to do - go through a giant list on a regular basis to see if the drafts they are interested in are listed there? I don't see how the proposed system would be any more onerous than the current one. As now you tag it and it gets deleted. No effort is required to institute the week of delay.

1371:"for non-commercial use only" (including non-commercial Creative Commons licenses), "no derivative use", "for Knowledge use only" or "used with permission". It also applies to media licensed under versions of the GFDL earlier than 1.3, without allowing for later versions or other licenses. This does not include images with a credible claim that the owner has released them under a Knowledge-compatible free license." 2666:. While such actions may be warranted, they should not be within the scope of G4, since it is always entirely possible that the subject of an article created by a COI editor and deleted at AfD may later become notable and created by a good-faith editor. Instead, another process (maybe a new CSD criterion?) is probably needed to prevent COI/paid editors from gaming the system. Re-education of admins will be needed. 4461:- I don't see how modifying a speedy deletion policy is perceived as being more difficult than re-coding a bot to add a notification to the draft page a week before deletion. The latter would probably take less than an hour's work, and wouldn't require carrying out an RfC and convincing half of Knowledge. Modifying speedy deletion policies can result in unintended consequences. Take the path of least resistance. 3910:

far without being made into articles are almost entirely hopeless. (I also do not bother with the ones still in a non-English language--if they've been copied from another WP without being even roughly translated, no work is lost if they're started over again. ) I think they and I and anyone else working here knows what the most important fix would be--the same as would fix all other problem areas in Knowledge--

7051:

has no in-depth coverage anywhere under any name, (3) isn't a useful search term for a different topic about which we do have coverage, (4) a soft redirect to e.g. Wiktionary is not thought to be superior than search results, and (4) (in some cases) it is not desirous discourage article creation by preventing red links. Given that all four are subjective, CSD is very much the wrong vehicle here.

1184:

frequently encountered situation. Finally, speed deletion is very much not to be used just because you can't see a point in it spending time at XfD. Speedy deletion is only for things that the normal deletion process is unable to handle because they occur so frequently they would overwhelm the other nominations and/or leaving them around for a week or so would cause harm. Neither applies here.

3727:- let's scrap G13 and implement DRAFTPROD instead. I don't understand the "more complicated" argument: there's already a mechanism to categorize and notify admins of PRODded and BLPPRODded articles that have been flagged for the mandated minimum time, it's merely a simple matter of adapting that to DRAFTPROD. There is presently no mechanism for "speedy-plus-mandatory-delay" deletion, 3303:, which is the just the most recent thread about this). Also the bot doesn't catch everything (I believe it's only for AFC-tagged drafts) and nor has it been particularly reliable -- the task has already changed hands between 3 operators in a short time. It's very unsettling that currently policy allows for deletion of harmless pages without a prior notice to the creator. – 4322:

change.) (2) Adding yet one more bit of complexity to a process is a bad thing unless there really is an overriding benefit, which there isn't in this case. Year by year Knowledge builds up more and more little details and complexities, with the result that editing is much more difficult for new editors to learn than it was. No, this is a reform we are better off without.

4317:, for many reasons set out by numerous editors above, so I won't repeat them all, but I will emphasise two essential points. (1) Editors have already had plenty of time to improve drafts in six months, and there's no reason to believe that an extra week is really going to make a significant difference. (Some of the editors who put time into "rescuing" drafts may 266:

deleted under this criterion", and so on - I guess ultimately it doesn't matter much. As I said back in the initial discussion in 2005, just about anything G10able is G3able vandalism too, and having the separate criterion is mostly useful as bright-line guidance. Do you really want an inexperienced new page patroller stopping to consider whether, say,

6998:#1? The spirit of the reason matches the scenario here: search results would be better than the redirect. The language of the reason refers only to "similarly named articles", but we're finding here that it could equally apply to any articles that include the search term. Let me know if this is sensible, as discussion for this would be better placed at 3028:, but unlikely to be very much), but I'm not sure that this will really solve the OP's problem. If you really want to watch certain drafts, you should not rely on seeing the notification on your watchlist (very easy to miss), but just make a list of them as a page in your userspace and check on and improve all promising drafts every once in a while. — 4106:), so I don't see how it would complicate things significantly. If even only 5-10 drafts are saved by the extra week, I still see that as a major improvement to the depth of knowledge available to readers. I'm also supportive of any alternative proposal that would notify interested parties that are watching the draft (DRAFTPROD, talk page...). 3914:. After that the system that does need rewriting from scratch is not isolated parts of the afc system, but the entire system--the AFCH. macro has been patched so many times it would best be rewritten from scratch; like many Knowledge systems it has accumulated features & special cases that sounded nice, but are almost never used. 726:, usually within a few hours of being added. There is no way to disable this, meaning that it's not possible for a non-free gallery to stick around in userspace for long. Secondly, these pages would be, if necessary, eligible for criterion under U5: a non-free media gallery is not closely aligned with Knowledge's goals of being a 💕. 2474:, some go through the deleting admin's talk page, some go through AfC, and some are just recreated in place and never challenged since the notability is obvious enough by that point. As a result, there is no consistent rule on whether community consensus is required to overturn an AfD with the presentation of additional sourcing. -- 4556:

and R3 for cases where someone created a redirect from a red link though. Like with G14 the vast majority of R2 and R3 redirects created from page moves will anyway likely be from experienced editors as opposed to those who create spam or autobiographies anyway so while I don't expect that this is much of a problem it can come up.

1115:

parent article -- that is, the article the navigational template is named after and/or clearly intended to be used on -- has been deleted or does not exist, that seems like it falls under "subpages dependent on a nonexistant or deleted page", and I don't understand why it's not already cited as an example of something fitting G8.

5150:

actually an attack page, I've a few times at RfD where something that out of context appears to be an attack is actually not when context is known). Adverts, while obviously inappropriate and undesirable, are almost never actually harmful - especially when the page has appropriate content tags and a big XfD banner at the top.

2379:). I strongly suspect that in practice it would be used to delete drafts which someone doesn't think are any good, rather than genuine cases of people not setting out to write an encyclopedia article. NOTWEBHOST violations are much more likely in user space than in draft space and U5 is widely abused in user space anyway. 3055:

interested in a draft and its deletion, and right now there isn't any workable way a watcher could be notified of an impending G13 deletion. As a regular at REFUND (which often gets backlogged) I do often see requests from people to restore recently deleted drafts, so this would reduce the amount of work there as well.

8002:(August this year). Unfortunately, only two subject-area regulars responded my query, in effect saying that licenses to broadcast were assertions of significance. It's certainly not the most intuitive assertion of significance (hence the issue with these notability-adjacent criteria, given how subjective they are). 4340:

on their talk page, but for the bot to also either post a banner on the draft or leave a notification on the draft's talk page. What I was unaware of is that the 5-month bot notification was down for 23 months and this is a major concern, as we cannot possibly expect new users to have to ask for REFUND. I refer to

5769:

spam before, for instance. Yes, I think we should try to get non-English content translated/trans-wikied to the proper place. But editors who translate content are often short in supply, and we need to recognize that sending junk content to translation is just a waste of time spent more valuable elsewhere.

3886:, who spends much of his time evaluating expiring drafts and delaying deletion of the most promising ones. I'd say that he catches probably 90-95% of promising drafts that are due to expire which is amazing to me. What we could really use is to have a couple more editors scan the daily SDZeroBot lists, (like 2591:, I wouldn't say it happens frequently but, yes, it happens. Most of the time, the page creators accept it, and I assume, don't stick around, but if they go seek solutions, they are typically referred to the deleting administrators which, from what I've seen, does not usually result in a page restoration. 4872:. Some users tried to create a new article at Chuhdary, overwriting the redirect, and near-exactly duplicated the target article. Another user tagged it with A10, an admin deleted, a user recreated Chuhdary as a redirect, and another admin protected the page. I'd say the process worked out fairly well. 8285:

G5, there's a balance between discouraging ban evasion and not deleting good content based simply on who created it. If the XFD had little participation and was closed as "no consensus" and it was found out the author was a known hoaxer I don't see a problem with applying G5 especially if some of the

7681:

I agree with SoWhy. I don't know how we can determine whether something like this is a scam without either signficant investigation or reference to reliable sources, neither of which are at all suitable to speedy deletion. If there is RS coverage then the scam might be notable and if so in some cases

6408:

Userspace - it's clearly not a draft article. It'd be U5-able there though - so you could avoid the "move to delete" and U5 it from draft-space. Note that moving pages from a namespace where they wouldn't be eligible for CSD to one where they would is generally inappropriate, unless the page actually

6215:

Unnecessary complication to rules. And it will make the categories and templates give an inaccurate calculation of whether it is G13 eligible. There is no hurry to delete. And nothing is clogged up, as there is no need to look at it unless it is submitted for acceptance. And if you want to search for

6076:

Keep it as it. This proposal adds complexity and judgement calls to the criteria with minimal benefit. There is no room to debate whether an edit came from a human or a bot, but there are definitely judgement calls in what types of human edits count and what types don't count. There's no real harm to

6028:

I am proposing that G13 be changed to exclude early speedy deletion nominations from the time count. Resetting the time for another 6 months simply because a draft was improperly tagged seems to be contrary to what this criterion is being used for. If a draft has not been edited for months other than

5959:

deadline be lifted, then you'll have to begin a discussion there as well. If that's the case, would you opt for a longer window, or would you propose that such pages be kept here indefinitely until someone comes along to do the work? And what procedure would be followed if someone determines that the

5284:

is a cautionary tale – four calls for speedy deletion (one of them coming from a regular CSD administrator) where none of the criteria apply. Given the abuse of some criteria (A7 and G11 may be the most obvious culprits), a general feeling that this page "doesn't merit a week-long discussion" or "XfD

5164:

Nonsense. That's not true at all and you know it. It's actually terrible practice to suggest that CSD-eligible articles are not to be actioned if there is an XfD open. It's a perfectly normal situation where an article at XfD can be deleted via CSD. To so arrogantly decree that no article ever may be

5106:

I have often tagged a page at MfD with U5, and/or G11. Importantly, there were no non-delete !votes, and none conceivable. If there were a a “keep” sentiment from anyone, then speedy deletion would be rude. Exceptions apply, including G10 and G12. G7 tagged should not be acted on, because it opens

5064:

If the author of a G11 eligible page at AfD turns up to defend it, the discussion should continue. An important purpose of discussion is the learning by the participants. If the discussion is underway, let it play out. Editors matter. If the author is WP:NOTHERE, block them, but if you don’t block

5020:

An XfD must specify a reason for deletion - for instance, that the person described in the article is not notable; and that is what will mainly be discussed at the XfD, although other reasons may also be brought to the table to strengthen the case for deletion. If a CSD criterion unconnected with the

4822:

I see your point, but I agree with Thryduulf that the sort of distinctions of factual accuracy that make no difference in real practice are probably not worth arguing about. I don't think you're likely to persuade people to use one term over the other, though you're absolutely free to use the correct

4555:

from a bad name so it would seem rather odd that the person who corrected the mistake but doesn't think the mistake is bad enough for R3 should be prohibited from removing the tag. The same should be done for R2 and any other criteria involving redirects created from page moves. Now we should keep R2

4339:

While I support the RFC's intention, I suggest that there's a better way to achieve the desired outcome. A process that we've already got in place is the notification of the draft's editor at the 5-month mark. I suggest that we slightly broaden what we do at this point, and not just notify the editor

4241:

I sometimes go through draftspace and look for stuff that seems reasonably promising, and add it to my watchlist. Then one day it gets deleted and I'm like, "What was that article again and do I want to do something about it?" But by then it's too late unless I want to go through the additional steps

4101:

Many of the opposes focus on that the draft creator has ample time and warnings to rescue their draft, but none of them address that other editors do not get this warning, and interested parties only get a few hours notice. It is unreasonable to ask them to monitor the entire list of drafts nearing 6

4036:

There is negligible difference between 6 months and 6 months + 1 week. If this idea will make some editors happier, then I think it's simply irrational to oppose it. But, draft space is mainly a compost heap, full of stuff that's rotten or best used as fertilizer for another article, and our sysops

3993:

Currently, a bot notifies the page creator at five months of draft inactivity. However, there is no mechanism to alert other editors who may be watching the draft or monitoring it through WikiProjects. By implementing a delay, this will allow time for editors watching the page to check the draft, and

3909:

and I seem to deliberately work in a way that complements each other; if someone wants to share the responsibility, they might want to try yet another of the overlapping possibilities. (If Liz thinks I catch this many, it's probably because the ones in sports and popular entertainments that get this

2988:

I'm talking about that bot that notifies the draft creator at five months - have that bot create a log of who was notified and what draft. That way anyone has a list available if they want to review drafts. Fundamentally, there is no problem with the speedy delete criteria, the problem is there is no

2844:

1844:

policy which explicitly is not a notability policy nor does it require proof or claims of notability. The footnote merely gives guidance about which subjects not to use A7 for and I think it can do so even as an essay. If you really feel the need to do so, you can always clarify that this is an essay

1437:

The processes for deleting F3s and F9s have just about nothing in common. For F3s, all you need to do is check if the uploader has asserted one of the insufficiently-free licenses and that there's no fair use claim. For F9s, you need to compare the image with its external source (often after having

1354:

By definition, a image licensed as "for non-commercial use only", "no derivative use", "for Knowledge use only" or "used with permission" are not considered free. So in my opinion we can just have one criterion saying "This applies to images (or other media files) that have no credible claim that the

1239:

for over six days now, it may get deleted as early as tomorrow morning (and unless the opposes suddenly arrive, it will be), so it's hardly going to "stick around and gather dust for weeks". Consider: it'll take you a month to get approval for G8 to be amended, by which time the template will be long

797:

be (part of) a good faith attempt to produce encyclopaedic content - U3 applies regardless of the motivation and does not imply intentional wrongdoing. I'm leaning towards repealing it entirely as, especially in cases where there is content other than non-free media on the page it will be, in certain

345:

Legal threats can be directed towards corporations or organizations, and one can write a page saying "My neighbour's cat is the worst! Kill her!" or a page simply saying that a certain object is bad in highly objectionable language. One could also write that "xyz is the worst subject in the world, it

8219:

This section has ballooned out of any pretense of reasonableness. It should be axed and the sentence in the lead changed appropriately: "If a page has survived its most recent deletion discussion, it should not be speedily deleted except for newly discovered copyright violations and pages that meet

6102:

The problem is there is NO room for making a judgement call. Admins simply count every edit as resetting the time no matter what since the criteria mentions any human edit. We could add a single word to it if need be to allow such calls to be made. These extra drafts can clog up backlogs at projects

5724:

Has there been any analysis of what the fate is of articles created in a foreign language? What percentage are transwikied, what percentage are translated here, what percentage are deleted under each criteria? Generally when I come across foreign language articles in NPP they are very poor - I'm not

5378:

too. But other than that, I'd just let the XfD run. The general rule is "Unless it's something with legal implications, rely on community consensus". You should also read the XfD. For example, if I think a page is G5-able in isolation, I'll delete it. But if there's already a discussion running

5330:

Pages which have been nominated at XfD can still be deleted under G7 as normal. This does happen from time to time when the creator of the page agrees with the XfD nomination. G7 is a courtesy rather than an absolute right, and G7ed pages are sometimes restored if someone else thinks they have value

5314:

But I'm struggling to understand the implications for G7. I've sometimes thought that, even if the author has requested deletion, someone else might want to finish (or at least continue) what the author had started. So does this mean if the author tags a page with G7 when an XfD is in progress, it

4920:

What's the correct thing to do if an AfD, CfD, MfD, RfD or TfD (have I missed any?) is in progress for a given page, and then it is found to meet a CSD? This could be an instance where the author has requested deletion (G7) after the XfD was raised, or a finding that it met one of the CSD all along

4321:

that this change would result in their rescuing more of them, but unless they put more time into rescue work the result would very likely be that they would just rescue different ones, not more of them. And of course putting more time in would stand to rescue more drafts with or without the proposed

4199:

per many above, particularly Stifle and S Marshall. If people want to come up with bots or other notification processes to get more attention on imminently-deleted drafts, then great. But G13 is an important and still quite high-volume process that primarily cleanses an awful lot of terrible content

3807:

Yes, I know. I also disagree with those :-) The few times I go admin'ing around most of it I do speedy (or otherwise obvious) deletions - so I can help a little, using the quite few available time I have currently - I never do categories or files because they are not really "speedy". They are prods

3003:

That might be useful for editors willing to sift through all drafts in the pool for those worth rescuing, but it doesn't solve the case in my example. Such a list would be only be practically useful if it was narrowed down to a smaller area of interest. I'm probably interested in a handful of drafts

2917:

I'm sure this has already been discussed numerous times, but what exactly has been keeping the suggestion to implement a delay between the CSD tag being placed and a draft being deleted under G13, like the current behaviour of C1, from gaining consensus? I can see clear benefits to such an approach.

2714:

Passing AfC doesn't mean something is exempt from G4, and it shouldn't. Passing AfC just means that the AfC reviewer thinks the subject is plausibly notable (if the reviewer is doing their job). However plenty of content is deleted at AfD despite somebody arguing that the subject is notable, so even

2621:

I agree with Oiyarbepsy. If a page has been accepted at AfC then it should not be speedily deleted unless G5, G7 or G12 apply. Indeed I'd be happy to explicitly codify that G4 does not apply in draft space (if it's not being improved G13 will apply, if it is G4 wont apply anyway) and that it doesn't

792:

we want to be able to delete these pages, not just remove the content, then it useful to have this around in policy in case the bot stops working for any reason or a human sees it before the bot does. U5 is not a good match as that is for content that does not align with Knowledge's goals - i.e. the

424:

Also, I noticed on one page that an edit got reverted just because it was made by a blocked or banned user in violation of a block or ban. And after looking at the edit, I noticed that the edit was actually of good quality. A constructive edit should NOT be reverted on the basis of the user who made

7866:

will also apply. I understand the logic that these kinds of stations are too rare to require A7 but then again, "frequent" is a requirement for newly proposed CSD, not existing ones. Personally, I probably would have granted the A7 since there is no reason to assume that this station is significant

7050:

I agree with Smokeyjoe, especially as there are far more occasions when a redirect is better than search results than the other way around. Generally the only times search results are preferable is where there is a topic that (1) has mentions in multiple articles by that or a very similar name, (2)

6200:

human edit resets the clock there is never any question about whether it is a substantive edit or not and it's not possible to wikilawyer it. If having a draft around for six months is harmful in some way then it should either be speedily deleted (e.g. G10) or taken to MfD. If it isn't eligible for

5883:

Investigating that Bengali content further, it seems that Google Translate is responsible for at least a large part of the problems you are seeing, e.g. it doesn't know the difference between "number theory" and "numerology". Especially given that it is supported by an apparently reliable source, I

5827:

If it's clearly not an improvement on the content elsewhere then we should delete it. If it is not clear then we should not be deleting it without it being looked at by a human who speaks the relevant language (doesn't have to be someone at that Knowledge, just look at babel boxes here or on meta).

5251:

The CSD criteria are inherently presumed to be uncontentious reasons for deletion of a page, hence why unilateral deletion is pre-emptively approved in the first place. That's literally the point. If the applicability of a CSD criterion is contentious, or if there are good arguments for keeping the

4967:

be deleted only if it's a copyvio or an attack page. For other criteria, it's up to context. If there has been any comment that recommends keeping or at least casts doubt on the rationale for deletion, then speedy deleting will obviously not be appropriate. If there has been no participation, or if

4904:

is correct to warn against deletion. Simply redirecting is better than deleting and then waiting for someone else to show up and recreate the redirect for a variety of reasons, the main of which is that you don't often get people showing up to recreate such redirects, and anyway, breaking things in

3199:

As for the DRAFTPROD idea, is this proposing to get rid of CSD G13 and replace it with DRAFTPROD only? Wouldn't this just clog up MFD with people contesting DRAFTPROD removals? That's what happens with many regular PROD removals... I go through my PROD log regularly and AFD any of my PRODs that are

3042:

Watch the creator's talk page. If they do nothing or almost nothing except create the draft you're interested in, it'll only show up on your watchlist when the draft's approaching deletion. If they're so active that their talk page pops up on your watchlist enough to be a bother, they're unlikely

3004:

which are already on my watchlist or tagged with a related WikiProject banner. Even if the bot logged notifications in a central location, nothing in my watchlist will have been touched, and the log, listing hundreds of drafts each day, is useless to me for monitoring the pages I'm interested in. --

2521:

But for how long? It obviously wouldn't be eligible for G4 after 1 second, before anyone has had the chance to improve it. If the rule is 6 months, then we don't need G4 as G13 will serve perfectly fine. If we want to set some different threshold, then we need to spell it out explicitly as CSDs are

2260:

Correct of course but any page that clearly was meant to be in a different namespace can be treated as being in that namespace, whether it's moved there or not, with the relevant criteria applying. For example, if a user page is created in draft space, you can and should move it to user space where

1930:

If I understand you right, yeah. So moving the text itself out of here and into a normal Knowledge page (and retargeting the shortcut to go to there), and then transcluding that section in the notice to keep a synced version visible to desktop users exactly as it currently appears. For mobile users

1836:

Linking to essays is not in itself problematic. It happens all the time, on a lot of policy and guideline pages. The discussion you link to objected to elevating the essay to a guideline mainly based on either it needing more work or the standards of this proposed guideline being too lax. On a side

1442:

Knowledge.From the uploader's perspective, having distinct criteria for "it said Creative Commons, I thought that's what Knowledge was?" and "I just want to put this image off the interwebz onto my article" simplifies things tremendously.The combined criterion really would need everything currently

1390:

licensed as "for non-commercial use only" (including non-commercial Creative Commons licenses), "no derivative use", "for Knowledge use only" or "used with permission", or GFDL earlier than 1.3, are not acceptable in Knowledge. Most images from stock photo libraries such as Getty Images will not be

1370:

So you are suggestion something like: "F3 Non-free images that are not fair use: This applies to any files that are non-free and not listed as fair use. This includes obviously copyrighted media, such as those from commercial stock photo libraries such as Getty. It also applies to media licensed as

1306:

It would be entirely reasonable to use G8 or G6 to get rid of a navigational template which doesn't list any extant articles, in much the same way as we would speedily delete a disambiguation page which doesn't disambiguate any extant articles. This one does have some articles in it (albeit dubious

1183:

there are no other pages on which it could be used. Which brings me on to the frequency requirement - how often does this happen? I don't follow TfD but I don't see anything listed there would meet the proposed criteria which given that it covers about three weeks of nominations suggests it's not a

815:

as unnecessary and underused, and I don't think there's any need to include it in U5 per Thryduulf above. Regardless of the existence of JJMC89's bot, the policy it's enforcing of no non-free content in userspace is still a thing. If we do run into galleries of non-free content it would be entirely

8295:

G6 redirects nominated for deletion, if the RFD was over deletion and later the redirect needs revering I don't see a problem, example if X redirects to Y and someone nominates X for deletion because they think its implausible but it isn't determined to be overly implausible and is kept, later the

6723:

It ought to be possible to come up with a suitable CSD criterion to deal with this. People often suggest expanding U5, which I don't think is a good idea (U5 is widely misapplied even in userspace). Possibly something like "Draftspace page which is not an attempt to write an encyclopedia article",

5768:

There should probably be some level of discretion here - sometimes, the non-English material is so poor as to not be worth transwiki/translate. Also likely worth clarifying that stuff in the above table that would meet any of the G criteria can still be deleted under those - I've seen non-English

5481:

A frequent issue I've run into is people tagging articles as A10 when the page being duplicated is in draftspace. This seems like quite a common thing: someone creates a draft, and instead of moving it to the mainspace, they just copy-and-paste it over (which isn't ideal, but I guess acceptable if

4994:

Admins can speedily delete any article which meets the criteria, even if the page has been nominated for deletion somewhere else. Speedy deletion is supposed to be for obvious cases only, and if there is support for keeping the page at XfD then that might be evidence that it's not an obvious case,

4733:

So what? I wasn't querying the obsoletion of the individual criteria or the reasons therefor. I was querying the obsoletion of the groups as groups. There's a big difference between an unoccupied house and a demolished house. My point was that the section you refer to seems to be confusing the

3876:

Because I spend much of my day & evening dealing with CSD G13s, I'm going to stay neutral about proposals to change the current system but I have a few comments that I hope folks pay attention to. I'm sorry that I haven't read all of the comments above this one. Whatever change is contemplated

2525:

My view is that any page which exists in its current form with the implicit endorsement of an admin is automatically ineligible for G4. If an admin consistently restores pages improperly, then we should talk about desysopping them, but before that we shouldn't reverse their actions willy-nilly. --

2452:

What is really troubling to me is when editors tag drafts for CSD G4 deletion...I've seen some admins remove the tag and say G4 doesn't apply to Draft space and other admins who just delete the draft. My point of view is that an AFD decision, especially one with limited participation (which wasn't

2121:

guidelines than draftspace, so it makes little sense to apply NOTWEBHOST to the former but not to the latter. I would certainly support, e.g., a six-month trial of making this G15, although it'll be important to clarify it should be construed narrowly and not as a catch-all. (The key word would be

7245:

I'm leaning towards this not being a good idea, certainly as proposed. WikiProject templates and (per the discussion Sdrqaz links to) talk header templates are useful, and verifying whether all discussions have been copied with full attribution is not something that we should be expecting someone

6447:

Yes, of course. If something is in the wrong namespace but wouldn't be CSDable in the right one, move it. If something is in the wrong namespace and would be CSDable in the right one, delete it. Of course when doing something like this it's best to err on the side of caution, so use common sense.

5922:

adequate for assessing the content of the article to the degree needed to determine whether someone who speaks the language needs to take a look at it as long as you understand that Google Translate has it's limitations and that it might not get all the specialised terms correct. I looked at that

4793:

Numbering will continue from T5 and/or X3. Whether the sections are present but empty or not present makes no difference to this at all, and whether the section is recreated or reinstated will be completely indistinguishable so the distinction you are attempting to make is entirely philosophical.

4589:

I hesitated, as both nominators were former functionaries and well, should know the criteria far better than I do. The thing that's tripping me up is that whether to think of a channel/station as an organisation (with a director and other personnel) or merely as a medium through which you get the

4550:

R3 currently states that it doesn't apply to redirects created from page moves unless the move was also recent, meaning either the article was recently created as a bad title or it was only recently moved there and shortly after moved back. With regards to the general rule that the author may not

4408:

Having a bot also deliver five-month notifications to the draft talk page (or post a banner on the draft itself) is an alternative solution that I would also support. I didn't imagine (and frankly still don't quite understand why) this proposal would generate so much opposition, and IIRC this bot

3945:

That list doesn't address the main situation raised by the OP: when an editor has an interest in a draft they didn't create. Maybe they made substantial contributions to it, and have it on their watchlist. Right now they won't get any notification that it's about to be deleted until at most a few

3447:

The objection that people could have rescued them before, is invalid, because almost nobody does that, because of the number to deal with--this would highlight them. The objection that the editor could always ask for them back, is invalid because most of hte time the original editor, having been

2865:

These notifications are posted at the talk page of the draft creator, and are useless for attracting the attention of other regular editors who may be interested in rescuing the draft. (Having the bot also post notifications at the draft talk pages would also work, though the delay approach seems

2650:

I strongly share Liz's concerns, and some more. Many admins are trigger-happily applying G4 over-liberally and inappropriately. I've recently (a few months ago) had to go through a DRV for a page which was newly created and bore no resemblance whatsoever to any previously deleted version, yet was

2552:

The more that I think about this, and the actions I've taken as an admin, there is a difference between articles that are repeatedly recreated (like those that appear to be paid editing) being deleted as drafts and those that are good faith efforts by editors to create better versions of articles

265:

valid outside the main namespace until that edit.)While I'm not going to concede the point - I mean, you can certainly libel and make legal threats against corporations, and if it were blps only, why specifically say "Articles about living people deleted under this criterion" instead of "Articles

7494:

I've been working with files for over a decade and can only recall a handful of instances where talk pages for files on Commons were a legitimately useful discussion venue. I'm skeptical of the WikiProject statistics use case, given that there is a heavy reliance on manual updates (i.e. someone

5149:

If there is an ongoing XfD then the page should never be speedily deleted unless keeping the page is actively harmful - copyvios and attack pages are almost always going to be the only cases where this applies (and even the latter can be overridden by good-faith arguments that the content is not

5054:

Oh yeah: that looks like an appropriate use case, at least in principle. But in practice though: something like G11 should be obvious, and if the nominator – who is apparently competent enough on Knowledge – has decided to go the difficult route of an AfD then G11 probably wasn't that obvious or

4778:

page, or the logical construct that is the group of criteria? I'm talking about the latter. If demolished, there's no possibility of a new criterion being added to it, so any re-creation would be a whole new group (and so the numbering would start again from 1). OTOH, if unoccupied, there's a

3451:

And it's worth doing: among the ones I've personally rescued in the last week are several people in major academies of science, or authors with multiple published books that have probably been reviewed, or members of legislatures, or subjects with extensive good articles in other WPs. Most would

1579:

The original rationale for it no longer applies. The reason F10 was introduced was that at the time Mediawiki didn't support rendering PDFs in articles, so PDFs had very little encyclopedic value. Mediawiki has supported displaying PDFs in articles for a long time now. Theoretically F10 could be

1114:

I see no benefit to keeping a page around and letting it spend God knows how long in XFD simply because there isn't a CSD that clearly fits it. This seems like a blatantly obvious template to delete speedily, even if it doesn't quite fit squarely into an existing G8 or other CSD category. If the

925:

looking for log entries including "U3". It indicates there have only been 6 uses of the criteria in the past year with two of them explicitly specifying a second criteria. It appears to have only been used 87 times ever. This is even lower activity than the most recent removals of T2 and T3. I'm

8554:

as the two criteria are valid under different conditions and not all pages deletable under U1 are deletable under G7, e.g. a guest book wouldn't fall under G7 if a lot of people have signed/commented on it, and a user space draft article that's been worked on by multiple people couldn't be G7'd

8299:

G6 redirects nominated for retargeting, if someone nominates X for retargeting which redirects to Y and its closed as retarget to Z and later its desired to move Y to X then there should be a RM at Talk:X to determine Y is primary for X so as to override the previous RFD. Like in the above if a

8147:

Example, a DAB page X is created listing 2 uses such as red links, DABMENTIONs or alternative/similar names such as X1 and X2, DAB page X is nominated for deletion on the grounds that the entries aren't valid/appropriate but its kept since its felt the entries are valid, X1 later has an article

6905:

As for this page, I notice G2 is getting used a lot more these days, rather like G1 was back in the day (calling something a test is at least less bitey than "nonsense"). Would it be possible to merge them like on Commons? "Test page, accidental creation, or page containing nonsense or no valid

5977:

Think of transwiki like post addressed to the house next door that's been delivered to you by mistake - if it's obviously junk mail you're not going to bother doing anything but binning it, if it's obviously important you're going to go less very slightly out of your way and give it to them, if

5974:

Without having thought about it much, I think the ideal would be something like a triage queue where articles are assessed by someone who speaks the language (probably only a 1 or 2 level needed) and rated as worth translating for en.wp (category A), worth transwikiing (category B) or not worth

5752:

A2 is much more restrictive than A10, it only applies if the article has "essentially the same content" as the other article. Whereas A10 applies if it's about the same topic and isn't an improvement. If someone writes a foreign language article here then it wouldn't fall under A2 unless it's a

3117:

that notifies authors prior to deletion. I suppose we could have the bot notify users again a week before their drafts become G13-eligible, but like others above, I don't see that significantly reducing the number of REFUND requests. For the record, I'm in favor of DRAFTPROD, even though it's

2209:

Please do not select a code for a proposed CSD criterion - we get lots of proposals, few of which succeed, and we assign codes when they are accepted and not before - otherwise we would (i) soon use up codes that will never get used for real and (ii) potentially have two or more discussions for

1174:

There are four requirements for new or amended CSD criteria listed in the big yellow box you saw when editing this page. Your proposal appears to meet only 1 of them (non-redundant). "The article the navigational template is named after and/or clearly intended to be used on" is not objective or

8340:

re F8, if the image was on Commons at the time of the discussion but was not deleted locally, then there is some reason for that and the local version should not be speedied. If the the image was not on Commons at the time of discussion then there is no reason to assume that a copy needs to be

8033:

then I'd definitely be looking to merge somewhere, taking it to prod or AfD after making sure relevant WikiProjects were tagged on the talk page, if I couldn't find a suitable target. If there is a target but no content or nothing verifiable beyond existence then I would redirect to a mention.

6827:

A comment about moving pages - it is absolutely inappropriate to move a page to another namespace purely for the purposes of getting it to "fit" a CSD criteria. Whether this is to a user sandbox to U5 it, or to the Article space so that it can be A7'd, or to any other namespace so we can put a

5898:

There's nothing wrong with that speedy deletion under the current version of the policy, and that does rather destroy your claim above that Google Translate is typically adequate for assessing the content of the article. To support this I would need to see evidence that a significant number of

4875:

However, the current language in A10 suggests that the original tagging was inappropriate, saying the tag should be used "where the title is not a plausible redirect"; here, the title was and is a very plausible redirect. Later language, "The title chosen for the vast majority..." only further

2719:

was a perfectly valid G4 - when the article was deleted at AfD the creator got it draftified, made some largely superficial changes (they only seem to have added one new reference, for example) and got it moved back to mainspace only a few months after it was deleted at AfD. Doing that doesn't

957:

I just want to make a small nit-pick that the 2500 deletions mentioned in the proposal is an extremely tiny sample size. As you can see from the list, it covers less than 32 hours worth of deletion activity on Knowledge and is not very helpful for informing a decision to repeal speedy deletion

519:

and other assorted covert spammers are generally deleted under G5, as created in bad faith. At least some of these pages may survive due to the second criterion you propose: a reasonable argument could be made in such cases (though not all) that substantial effort was needed. Some cases can be

329:

G10 wasn't really needed to get rid of that draft, which was just vandalism ("DOGS ARE STUPID AS FUCK!!!!!") but in principle I don't see why G10 can't apply to pages about animals, or even abstract concepts. If the sole purpose of the page is to disparage the subject then it's an attack page,

6201:

speedy deletion and there is no reason why MfD would delete it then having it around for another 6 months is not harmful. Such nominations are actually marginally beneficial in that they bring another set of eyes to the draft which (very slightly) increases the chance of someone improving it.

5192:

The fact that there's an XfD in progress doesn't mean that the deletion is controversial. It might do, and the reviewing admin should certainly read the XfD and decide, but in an awful lot of cases the deletion isn't controversial at all and that is obvious to anyone who reads the XfD. Speedy

6698:

Beyond the CSD issue (therefore slightly o/t), as a practical matter, I wonder if it's worth saying something at this new user's TP about this. I don't think we want to give them the impression that chatrooms are accepted here. On the flip side, I'm queasy about the impact of saying it's not

291:

to the criteria under which they've been deleted (A7s that have plenty of references, G2s that aren't actually tests, etc). Thus, I don't think anyone is going to complain about a 100% negative draft about a dog being G10'd, but clarification about the language is still probably a good idea.

155:

describes an attack page, is negative or disparaging content about an individual. But the header for this criteria states "Pages that disparage, threaten, intimidate, or harass their subject or some other entity, and serve no other purpose" and I guess I'm wondering how broad we consider the

8233:

If a consensus discussion has resulted in that page being kept, then it needs another consensus discussion in order to delete it. The only exceptions to that should be G8, G9, G12, G13, F9, U1, some G6 (temporary deletions) and some F8 (not available on Commons at the time of the discussion

7788:

I think the basic ideas are 1) In order to obtain an FM licence, you have to pay for one and pass a strict standards test, which means there are relatively few of them and they cannot be created indiscriminately. The "FM" bit is important, internet-only radio and TV can be created by anyone

4891:

There's a wider principle that's relevant here: if a page is tagged for speedy deletion, the admin should review the history and see if there's anything there before it became eligible for speedy deletion. That applies to any CSD: otherwise you'd be able to get any article deleted by simply

3054:

I would support this. The idea of a time delay is perfectly consistent with a speedy deletion criterion (e.g. F4, F5, F6, F7, F11) and it doesn't make much sense to delete a draft if there's someone still interested in it. It's also entirely possible for someone other than the creator to be

2307:

line of thinking. At least from what I've seen, U5 generally covers three general groups - 1) promotion in userspace, 2) vandalism/neonazi/conspiracy theory, and 3) occassional things such as fantasy sports leagues or alternate history games. 1) can be dealt with by G11 when it appears in

7559:

a change in the wording of G3 from "Pure vandalism and blatant hoaxes" to "Pure vandalism, blatant hoaxes and scams", with matching text in the explanatory paragraph, that it may be used for a page which is unarguably lending weight to a scam, for example by reinforcing the existence of an

4744:

So essentially, they're not demolished, but merely unoccupied. As such, while the sections on the page have been removed as they would be empty at the moment, the groups still exist as groups. As such, it would be better to describe them as "inactive groups" or "not currently in use". —

1550:

non-media files, not just non-media files. It is at least theoretically possible for non-media files to have uses in articles and to be fair use or otherwise not suitable for Commons. In combination with the usage statistics mentioned by Trialpears it seems this criterion is still useful.

7319:

already exists for this purpose, but given that any of these file talk pages with a non-trivial history should be carefully examined (locally and on Commons) by a human in all cases, I think deletion should be the exception not the norm making such a template redundant in this situation.

2261:

it belongs but if it would be deleteable in user space, it's imho okay to apply a U-criterion to it without moving it first. Gaming the system is and should be forbidden but at the same time, we shouldn't be blind to stuff sometimes being created in a wrong namespace by accident. Regards

5505:

If an article duplicates a draft then either the two pages should be (history) merged, the draft should be moved over the article (deleting the latter under G6) or the article left alone and the draft deleted (or left for G13). None of this is what A10 is for so I support your proposal.

3473:

as a seperate group as suggested above. The problem is that drafts are deleted in a blink of an eye by certain admins without allowing oversight by unconnected editors whose first sight of the drafts is at speedy deletion and where they are not given time to read even a line or two, imv

3368:

I'm finding it a bit ironically amusing and disconcerting that so many people are commenting with exactly the same arguments that I thought I had already pre-emptively refuted in the original post. (Q: "If a draft has been stale for six months, what good would an additional week do? A:

1287:

If a page is AFD deleted, any related freshly orphaned navigational templates should be deleted per G8 (I think this is already covered, even if not explicitly). In the present case, the template is not orphaned and already being discussed, so I don't see the need for the speedy (it is

3448:

once discouraged, is long gone==this is especially unfortunate when they're from editathons or similar projects. Anf nobody else knows of them once they're gone, because deleted articles are not readily even for admins, searchable unless you know they exist, or know the exact title.

7162:

Discussions ... I don't think they are always copied to Commons and I would not automatically assume they'll stay there or be appropriate there. True, I think that telling people to use the Commons talk page for Commons images would make sense but that has nothing to do with speedy

5805: 8260:

Pages in the way of moves are either going to have conensus to be moved/deleted (in which case this section doesn't apply) or be redirects. If the redirect was itself discussed then the page move needs a consensus, if the target was the page discussed then this section doesn't

8170:

A DAB is not an article so if it only was ever a DAB then it only serves as navigation so its not like anything is lost if later a primary topic is created. Users may want to support this only if there has been an express consensus (say at RM or RFD) than a meaning is primary.

5803:

More fundamentally the change wouldn't make much sense unless we have lots of reasonably good content written here in foreign languages which is suitable for other Wikipedias. Otherwise it's just not worth the overhead of dealing with it this way. For example I've just deleted

2668:

Also, agree with codifying non-applicability to pages passed through AfC, restored pages, and possibly all drafts. (Though the fact alone that this needs to be codified raises serious judgment concerns, which probably won't be resolved without addressing underlying issue.)

7246:

patrolling CSD cats to do quickly and reliably. Something like talk pages with no meaningful history (if we can objectively define "meaningful") might be doable but I'm wondering both how frequently it would get used and what benefit deletion would bring to the project?

5842:

Speedy deletion is appropriate for content which has little practical chance of being useful. Unless we have some reason to believe that these pages include a significant amount of useful content we shouldn't be changing the rules to make it much harder to get rid of it.

4344:'s experience above and would prefer to formalise a 5-months notification process for draft creators as part of the G13 process. But as I say, it's that process that we might as well broaden to achieve the objectives of this RFC rather than invent an additional process. 2015:

The talk page is the right place for this information, because this isn't of use to those following speedy delete policy, but to those wanting to change it, and we change it here on the talk page. That said, I'm gonna reformat the talk page to draw more attention to it.

7612:

Additionally, I don't see any way to make what Elemimele describes into a criterion that is objective enough to support speedy deletion without having to do and lay out research as to why you believe this is intended to support a scam. Which is precisely what deletion

2872:

While this approach would also solve the issues I raise, it seems unlikely to gain consensus, given the concerns that a more complicated approach than a straightforward CSD criterion might not be adequate in dealing with the large amount of stale drafts generated each

1714:

Sorry, I was under the impression you couldn't, but you definitely can. I don't know if we want to keep it as an option though. I feel the argument for any non-free pdf fulfilling NFCC is weak and probably should go on commons, but I'm not a file expert by any means.

5420:

I'd say G3 hoax deletions during the XFD would be acceptable. There are times when you are pretty sure its a hoax but not quite bold enough to tag as such, and then after a couple days at AFD, it because clear from further research by others that the time is a hoax.

5315:

can remain but shouldn't be actioned for the time being? And if the author blanks a page with an ongoing XfD, and there's no support (from me or given by anyone else) for keeping it, should I tag it with G7 at this point? What if there is support for keeping it? —

2136:

The question would be (in line with #3 of the requirements for new criteria): Is there really such a pressure on MFD that we need such a criterion? The example RandomCanadian mentions for example is actually not an example of what this criterion would be for because

798:

cases at least, unnecessarily bitey to delete the whole page rather than just remove the non-free content. By definition, the page is in userspace so an empty or mostly empty page is not doing any harm - and if it is then U5 and/or a G criterion will apply already.

8300:

redirect is nominated for deletion and kept and a different page is desired to be there other than the one it targeted as a result for the RFD then there should probably be a RM but its likely if the original target may be implausible it won't be too controversial.

3921:

reviewers--this should be a interesting AI project that could also work at NPP and AFD and suggested merges, etc. The wikiproject approach works well in a few fields only--and in those few fields where I know it works, like the military, I refer problems to it.

3550:

No, I wasn't notified by bot. I see that the BRFA was in 2018 and this happened in 2019, so I'm not sure what happened. Since my main issue was not being notified until the day of the deletion itself, yes this would have solved my main issue with what happened.

2720:

entitle you to get a rerun of the AfD every few months. G4 definitely shouldn't be used to delete drafts of articles deleted at AfD though, in draftspace G4 only applies to drafts deleted at MfD. This is because a draft is substantially different to an article.

1385:

Or simply, "F3 Non-free images that are not fair use: This applies to images (or other media files) that have no credible claim that the owner has released them under a Knowledge-compatible free license and are not claimed by the uploader to be fair use. Images

7847:

So, as I understand it, you're saying that FM radio stations are inherently immune from A7 because of the licensing requirements? That strikes me as bizarre, but is it true that FM licensing standards are the same in every country? And precisely what are those

7068: 5038:

It can apply for cases other than copyvios or attack pages. E.g. say a promotional article is sent to AfD, and the page creator (an SPA with a probable conflict of interest) posts a Keep comment, that wouldn't prevent an admin from deleting the page under G11.

2553:

that were AFD deleted, typically because of a lack of notability. The problem with this situation is that it does involve a subjective decision by admins which might be why there is some variability in how admins, as a group, handle these cases in Draft space.

8192:

I would always require another discussion to overturn a previous consensus, especially if that previous consensus explicitly endorsed the existence of the disambiguation page. So I would be fine with it as the natural outcome of an RM, but not a bold move. --

816:

proper, without a speedy criterion, to speedily trim the non-free content and blank the page if there's nothing else - while letting the good-faith user continue their project within policy. Any corner cases beyond this are either going to fall into G3 or U5

4759:

I see no functional difference between the section being "demolished" or "unoccupied". If a new criterion is created, the "house" can be recreated with the click of a button. In this case, there is no difference between the group being obsolete or inactive.

520:

covered by G4 and G11, but others still escape. The term you may be looking for is "bad-faith creations"; but determining if a page was created in bad faith may in several cases prove a subjective matter. In any case, I cannot support the proposed criteria.

4623:

It's not as clear-cut as that imho. Stations could be eligible for A7 as companies (unlike their programs) although in many cases, if they are sending programs that are received in large areas, we probably need to assume significance or importance. Regards

3141:

either this or DRAFTPROD. I have a slight preference for DRAFTPROD, as it gets rid of the "speedy" misnomer, and because it would allow drafts to be deleted earlier than 6 months if no one objects. But either one is preferable to the current arrangement. –

1175:

uncontestable as templates may share a name with an unrelated article and there can be multiple main articles. For it to be a valid navigation template there must also be multiple extant articles on which it could be used so G8 could only really apply when

7908:"Needs a licence" is most assuredly not a claim of significance - by that logic all houses and buildings I have ever been in and the vast majority of businesses would be banned from A7. On the specific case of Philippine stations, the links at the top of 3340:

I already covered that above. Bots can come and go. They are not required to run. And indeed this bot wasn't running for more than a year, before Firefly took it over. We should not be reliant on bots for issues that are better solved by policy changes.

997:

Mm, you're right, and it even seems like those six uses in 2020 were on the unusual side: scrolling back through the Quarry result, it looks like it's usually about 3–5 uses per year, which is definitely very rare, and I have no objections to repealing.

8247:

A5 this can never apply - if the outcome was transwiki then the discussion outcome was not "keep" but "move to another projected and then delete". If the discussion outcome was transwiki and keep (ie. copy to another project) then the transwiki part is

844:, no need to complicate the page by having criteria that refer to the wikipolitical wars of ten years ago. Can always reinstate it if it turns out these wars come back. Until then, U5, G3 and MFD should be able to take care of it even if the bot dies. — 497:

If G5 applied only when other criteria also apply then it would be completely redundant so this is effectively proposing it be abolished, which as you acknowledge does not have consensus. As Kusma notes, the rest of your proposal is in the wrong place.

8760:

Discussions which have been copied need to be verified to be properly attributed. Careful examination of page history here and file pages and talk pages at Commons is not something that can be done reliably by a single admin patrolling speedy deletion

8725: 7575:

Unnecessary and not a good idea. If it isn't a G3 hoax, and it isn't G11 advertising, and it isn't A7 "no claim of being an operating business", we can afford the week to discuss it. The example article has existed for 10 years, what's another week?

4640:

I'd say that TV channels/stations are companies and so are eligble for G7, however I would count being granted a license to broadcast as a clear assertion of significance. For the specific examples mentioned here, I would not have removed the tag from

1575:

It is widely misused. By my count 28 of the last 100 F10 deletions (linked above) are of image or sound files, which by definition don't qualify for F10. And that's just the obviously inappropriate ones, some of the other 72 deletions may not be valid

8264:

If a page was obviously created in error then it wouldn't have been kept at XfD. Redirects resulting from moving pages created in the wrong place either aren't the page that was discussed, or were kept despite being created in error and so need a new

8438:. I disagree with the outcome of that discussion and I believe it was based on very narrow assumptions about what sorts of socks are out there. Still, if we're going to revisit the issue, we'd need another RfC and a thoughtfully prepared argument. – 5923:

article and determined that it was apparently well written sourced prose that likely contains material that is not in the bn article. I don't know the scale of the issue fully, but I've seen at least two articles today so it's obviously not nothing.

6343:

G2 doesn't work since the page is clearly not a test. That said, I don't see any harm it is causing, as the user made no effort advertising their chat room, so it is doomed to become them talking to themselves until they give up and it gets G13-ed.

5524:. The only issue I do potentially see is before an A10 could be applied to a content fork, now this wording could be argued it must duplicate the majority of another article. I am fine either way, but CSD criteria are often very narrowly construed. 3073:. This would create a place where editors can see which drafts will be deleted in the upcoming week and give one final chance for anything salvageable to be worked on, not just by the draft's author, but from anyone else patrolling the G13 tags. -- 8024:

The difference is that licenses to construct a building are very common - there are tens in all but the very smallest of settlements, cities have hundreds of thousands or millions. Radio broadcast licenses are not that common - I count just 23 at

7824:

I agree with Ritchie - operating a licensed terrestrial broadcast tower is enough for a presumption of significance to survive A7. However, PROD and AFD can and do delete articles on broadcast radio stations that don't meet notability standards.

3437:

or the equivalent; it will do much better in a separate group , than in regular speedy, because of the size there are over 50/day. This is 350/7 days, and that's much too large for speedy as it presently works, which is actually quite speedy.

3707:. The proposed change does not practically provide more opportunity to rescue drafts since there is already ample notification and adding another layer of hoops to ump through does not improve the chances that these will become useful articles. 2326:

With respect to your point 3 items, "Upper Madeupistan is a country formed from Northern France after the Axis powers vanquished the Allied power in WW II..." would be subject to G3 as a blatant hoax in draft space. Ditto for fantasy games. --

8166:

a hatnote can link to the only other. This may apply if the page was moved to the base name (or a primary redirect was made) either as a result of consensus or done boldly as long as its not controversial that the use made primary is primary"

6656:

As for expanding the criteria to allow a case like this not to involve a move? It seems easier to just do the move when the situation arrives than to explain what a new criterion or the expansion of an existing one does and doesn't permit.

5862:

There is no way that we should be deleting (a) under any circumstances before it has been transwikied. There is no reason to delete (b) without getting that input - if the input is "no, that's not useful" then A2 will apply at that point.

2651:

speedily deleted by an admin who refused to reverse course. Judging from glances at other DRVs, such occurrences are way more common that they should be. (In just the past week, I see two cases of G4 deletions citing AfDs which took place

4691:

All the criteria which were formerly part of these sections have been removed, but the sections will be reinstated if a new criterion of that type is ever added. So any new template CSD would be T5 and any new temporary CSD would be X3.

7260:

I think that generally file talk pages consisting of WikiProject tags for files hosted on Commons are kinda pointless and wouldn't oppose being able to speedily delete them. Copy-and-pasted discussions is iffy for attribution reasons.

2039:

currently only applies to userspace. This seems not entirely thorough enough, since there are sometimes pages which would also fall under the criteria (which are "blatant misuse of Knowledge as a webhost") which are in draftspace, ex.

5450:

Ummm ... the benefit is that once the content has been proven to be fabricated, that we're no longer foisting false content upon the public? I know at least on my mobile interface, the various cleanup tags don't always show up well.

4384:

to consistently send out talk notifications, there's clearly no real problem to solve here. However, I'd be curious as to why it was down for several months in the first place, and more importantly, how likely is it to go down again?

3829:

though I would prefer to scrap G13 and implement DRAFTPROD instead. I don't see any practical problems with a delay from a bot tagging G13 to the article being deleted; we do something similar with some files and categories already.

2655:

or more!) G4 should only be used to prevent re-creations of deleted pages and should almost never apply to good-faith creations by different, uninvolved editors (with the possible exception of categories and some other non-articles).

5256:

be relevant context. But that has nothing to do with whether an XfD simply exists. In most cases, an XfD discussion focuses on issues not germane to a CSD nomination. In most cases, an XfD discussion is not even contentious. We are

1408:

they are merged (I'm not immediately certain either way), then it will be important to maintain the "A URL or other indication of where the image originated should be mentioned." and "Blatant infringements should be tagged with the

6739:

So basically "draftspace page which clearly belongs in another namespace"? Because it's clear that the creator here wanted to create something for Knowledge's internal usage (however misguided) and thus would probably have created

4896:? I imagine because the redirect itself was recently created and the deleting admin didn't believe it was plausible – so even before the A10-eligible content addition, the page would have been speedy-deletable, though this time by 6488:. Common sense dictates that we can treat pages clearly meant to be created in a certain namespace as if they were created in that namespace. The previous discussion about this criteria touched on this exact issue - I concur with 314:

While I'm not able to see the content of the draft, I don't see any reason why attack pages couldn't apply to a dog. All dogs have their humans, after all, and they also all go to heaven, so such a page would be inherently false.

8366:

allowed to be speedily deleted after surviving XfD. If the FfD was closed as keep with full knowledge of the existence of the Commons copy, then the local copy should not be deletable, so that case should not be in the list. --

6828:"whoops, wrong namespace, guess I'll G6 it" on it. Getting around the rules is exactly why we have such strict criteria, and why most folks on this board are hard-nosed about the criteria, following them, and creating new ones. 2715:

an exact recreation of a page deleted at AfD can still pass AfC review. As the reviewer may not be an admin it may not be possible for them to check that the content is similar to the deleted version anyway. I think the case of

7281:

I can definitely see situations for keeping local talk pages for deleted files, especially if there is a lot of valuable discussion about a particular image. Perhaps there should be a template for requesting that the talk page

4551:

remove a speedy deletion tag I suggest that this shouldn't apply to redirects created as a result of a page move as with G7 (and G5 should probably also say) since the "author" of a redirect is the person who moved the article

4123:

per S Marshall. This is just scope creep and additional complexity that won't do anything to actually improve/'save' the drafts. Ask Headbomb to add them to Article alerts or something, that would be a more meaningful change.

2780:

says also, often restoring to raft space is better. But if it's clear enough, not always. The entire afc process is too idiosyncratic for fixed rules--people engaged in any aspect of it must have good judgment, and use it. .

8435: 2453:

the case with Cheman Shaik) shouldn't be destiny and final. There should be a way to overcome an AFD deletion decision especially ones from long ago when there might have been two or three editors voting to Delete. Thoughts?

6694:

the idea of moving a page to another space in order to gain access to a CSD criterion. I'm not sure it reached the level of consensus, but there seemed to be a lot of militating against moving to user space so that U5 could

4060:

per Stifle. We have too many drafts, most of which are junk. If one editor can't get their ducks in a row quickly enough, certainly another editor will come along with the time and needed references to do the job correctly.

1995:

The box doesn't actually say that, it just says that CSD crtieria need to meet four points. Several of the existing criteria don't so it's clear that there's consensus that CSD crtiteria don't have to meet all four points.

4428:. This just adds 3.85 % to the delay of processing the compost in Draft namespace. Unlikely that any additional rescue of the very few salvageable drafts that are still lingering after six months of inactivity will occur. 1686:

in the meanwhile. Something similar could probably be done here. Something like keeping the criteria as valid, but adding a note about the current situation and allowing for quick removal when this job is done. Thoughts?

6029:

the addition of a deletion template then obviously it is has been abandoned. Resetting the timer, in this case, is simply prolonging the inevitable. I see no harm in this considering these drafts can always be refunded.

5089:

That's obvious, that a page can still be deleted if there are Keep comments at XfD. Even without a CSD, one or two people posting Keep arguments won't stop a page being deleted if there are stronger Delete arguments. —

7150: 3497:, but by the time I had read it (which was the same day), the draft was already deleted. I think that a week-delay would be useful because it will give new editors time to actually edit the draft before it is deleted. 2205:

All CSD criteria (other than the G criteria) apply only to one namespace or to one namespace and its associated talk namespace, so it would be against established practice to extend U5 (or any U criterion) to Draft:

481:

I agree with that in principle, but I believe it's important to remember here that G5 applies not only to banned but also to blocked editors. The blocking policy has a more nuanced approach to reverting such edits

346:

must be banned" in a lot more flowery language. Many of these cases can qualify for G3 as well, but I don't see why G10 won't. As long as the page only is disparaging its subject, it can be deleted under G10, IMO.

5435:

I don't see what advantages that brings? If there aren't enough !votes for a SNOW delete it's unlikely to be obvious enough for speedy deletion. Just make sure the aritcle is tagged as a hoax and wait a few days.

4409:

task had been suggested before, with no response, which is why I suggested the delayed deletion approach here. I will further inquire upon this path when this discussion ends without consensus, as seems likely. --

7867:

in any way (and neither source in the article mentions it). But this discussion shows that this is not as clear, so erring on the side of caution in most cases of FM radio stations sounds like a good idea. FWIW,

6699:

acceptable, and then not doing anything about it for six months; this violates "watch what they do, not what they say" and could confuse a new user even more about how things work around here. While wearing your

1883:

page? It has a high degree of acceptance anyway. Alternatively, move it to the first section on this page and keep it stickied? I ask because that portion is cited and useful, but mobile users cannot see it (see

5858:

Done properly, the only things that will be harder to get rid of are (a) content will (probably) be useful and (b) content that we are unable to reliably assess without input from someone who knows the relevant

5331:

or wants to work on them, but that request is usually granted if made in good faith. If someone blanks the entire article (including the XfD template) then I would take that as a G7 deletion request as normal.

8286:

keep !votes cane from suspected socks. If the XFD was "keep" or "no consensus" but with high participation I don't think its appropriate to G5. I'd agree with you that we should probably remove this exception.

5215:

CSD can apply if the chosen criterion concerns a matter that does not overlap with the issues that have been brought up at the XfD (I mentioned this at 07:36, 13 August 2021 (UTC), but not in the same words).

7534: 3095:

included in the Article Alerts list. That would go a long way toward resolving the issue. (I could conceivably support the underlying proposal, but I'd first like to see if there are any simpler solutions.)

5010:

Yes, but only if the page in question is a copyright violation or an attack page, right? Otherwise that would seem to undermine the fundamental principle of CSD: that it's for non-controversial deletion. –

590:

entry as the old wording reflected the F7a repealed in March, and for some reason never mentioned the still-used F7b. You may tweak the new language as needed, but the same wording should be used for both.

6548:

This is a place where people can chat,I created this page because Knowledge doesn't offer this,so feel free to use it,btw when chatting use a username so its easier to know who is who,mild cursing pls lmao

6043:

I would agree with all tagging (to the extent that anybody tags drafts) being excluded from the time count for the same reason. Pointing out needed improvements isn't itself an improvement to the article.

2376: 718:. Knowledge's non-free content policy prohibits the use of non-free content in userspace, even content that the user has uploaded; use of content in the public domain or under a free license is acceptable. 7569: 6652:

I concur with others that this particular page was not created with the intention of drafting an article, so it is properly moved from Draft space to the user's space, where, yes, it becomes eligible for

4362:

Note that I misspoke earlier on this page, and the bot was actually only down from March to October 2019 and then from June 2020 to February 2021 (with the exception of a two-week period in August 2020).

1980:

I don't recall seeing any disagreement that proposed new criteria need to meet these requirements? What other acceptance is required? Whether existing criteria meet the requirements is a separate issue.

8728:: should file talk pages for files on Wikimedia Commons that only consist of the following: boilerplate templates, WikiProject tags, and/or discussions which have been copied to Commons be eligible for 5603:

When content is not in English but that content exists on the relevant non-English Knowledge it can be deleted under A2 or A10, that's fine. However, A10 allows for the speedy deletion of material that

8136:

for example. This would apply only in cases where the DAB page was previously at the base name at the time of the XFD, there were and still are only 2 uses and a primary topic later is created meaning

7793:

qualify for A7. 2) There hasn't been a wave of AfDs for FM radio stations making a CSD criteria necessary to stop bogging down the works with them. It might be a PROD or AfD job, for sure, but not A7.

5165:

deleted via CSD, just because there is an XfD open, is ridiculous. CSD is for routine uncontentious technical deletions and the existence of an XfD does not inherently preclude our ability to do that.

7358:, as the documentation's long-standing instructions have shaped my opinion in that talk pages with just this template are not particularly useful, and admins routinely deleted them in the past citing 6968:. Ultimately, the decision depends on how closely tied the redirect is to its target rather than how much it appears in search results, and that is a subjective judgment which requires discussion. -- 6270: 163:

Can we consider any negative, unsourced complaining about any "thing" as being a valid page to be deleted under CSD G10 or should it be understood to be more strictly to be attack pages about people?

8251:

F8 if the file was available on Commons at the time of the discussion then there was almost certainly some reason to keep a local copy and it needs discussion to determine whether that still applies.

6239: 4200:- it is not productive to apply unnecessary extra process to it. People can and should be encouraged to save drafts, but adding an extra week's complexity is not a particularly efficient solution. ~ 4832:

I'm also not sure that in common parlance "obsolete" is regarded as a permanent status, see the number of google results for phrases like "currently obsolete" and "previously obsolete" for example.

2395:

I think G11 criteria is enough for draft namespace which advertises something, like we implement U5 criteria for userspace. I always use G11 criteria to tag draft which meet the deletion criteria.

1486:

MediaWiki already limit what type of files that can be uploaded and it is no longer possible to upload doc or zip to Knowledge. For free PDF files, they may either be moved to Commons or Prodded.--

8079:

1197. Now myself I would probably pass on such an A7 since it's unclear to me whether something like that can be considered a claim of significance but I wouldn't consider it unambiguously wrong.

7348:. Files don't suddenly become irrelevant to WikiProjects when local uploads are deleted in favor of files on Commons, they are still within the scope of those communities. I am ambivalent towards 5404:

If there is any good faith doubt or discussion about whether a CSD criterion applies then it does not, because deletion is not uncontroversial. G9 (office actions) are the only exception to this.

3258:. With there already being a six months delay after the last edit, a bot giving a message at the 5 month mark, and the fact that G13'd articles are elgible for REFUND I don't see a added benefit. 4649:

clearly made at least two assertions of significance (legal challenge to obtain license, and then obtaining a license) so it definitely would not be eligible for A7 regardless of subject matter.

2372: 135:

version in the page history to revert to. Both the page title and page content may be taken into account in assessing an attack. Articles about living people deleted under this criterion should

6297: 1840:

That being said, the footnote in question here is for A7, a criterion where erring on the side of caution is generally advised and as such, applying a laxer standard is actually in line with

7512: 4609:

A7, A9, A11 do not apply to any other subjects such as TV Channels, programs, and stations. You can delete it by list it at Proposed deletion or listing in Article for deletion discussions.

144: 373:

The discussion has been relocated after a negative response and a suggestion that this adjustment would require more general adjustment of the banning policy. It's now been raised again at

3975:

Once it's deleted, the text can no longer be seen. So most of the time people won't recall whether the content was worthy or not. Also, for new users, it isn't trivial to "just REFUND". –

1905:

Would moving it to it's own page in the Knowledge or template namespace and transcluding it from there resolve the issues? If so I think that's preferable to having it as a section on the

6136:

Most of what I have seen has been good-faith noms that nom something just before the 6 months is up and it gets reset rather than people thinking about a questionable deletion with risk.

2138: 2041: 8718: 6275: 4614: 3641:

Doesn't sound like a great idea, pages deleted under G13 do sometimes contain copyright violations, spam that could be deleted under G11, etc. The bot wouldn't be able to detect these.

4635: 1583:

It is inherently quite subjective, because of the standard of whether a PDF is useful to the encyclopedia or not. This means it isn't a great use case for a speedy deletion criterion.

7011: 5955:. Such an article that hasn't been translated within two weeks is going to be PRODded anyway (or, if ineligible, AFDed), so the transwiki window is tight. If you want to propose that 3244:. There is already a six month delay and several warnings before it expires, and G13 deletions are REFUND eligible if someone later decides it's a potentially viable article subject. 283:

I see your points, and in thinking about it there are plenty of pages that just about every admin I know (including myself) have deleted under one CSD criteria or another that didn't

6144: 6131: 2131: 1960: 8745: 8624:. Both per above and by the general issue that merging criteria makes the result more complex and less likely to be applied correctly. Have any potential benefits been identified? — 7182:

This template should be used only when a talk page requires it. There is no need to add this template to every talk page. Do not create a talk page that contains only this template.

2025: 1438:

to track down that external source yourself, when the source URL isn't provided), whether the image is freely-licensed by the source, and whether the purported source got the image

6950: 3750:

If it needs to wait a week, it ain't "speedy". Also oppose a PROD-like procedure (though there is a good chance that I am misunderstanding the concept), because a stale draft is a

1944: 1918: 8641:- there are situations where U1 would apply that G7 would not, such as those listed above or an unwanted page being created in your userspace. I see no potential benefit to this. 6225: 4977:

If you tag a page for speedy deletion, and an XfD already exists, it's good practice to add a comment to the XfD discussion noting that you've tagged the page under discussion. --

4133: 1230: 1210: 8289:

A2 and A5, with A2 and A5 its possible the foreign article was written after the EN one was at AFD but yes I agree if kept at AFD it shouldn't just be deleted without discussion.

8244:

A2 if an article in a language other than English has been kept at AfD then there was obviously some good reason for that and it should not be deleted without another discussion.

7027: 6165: 5786: 5300:

Thank you all for your input. So essentially, the right thing to do is go ahead and place the CSD tag, and while at it post a comment on the XfD to the effect. I suppose that:

3970: 1975: 551: 8214: 7197: 5346:

If there have been !votes at the XfD to do something other than delete (especially keep or merge) then the page is not eligible for G7 as deletion would not be uncontroversial.

4676:

If the former, what will happen if, in the future, it is decided to enact a new CSD that is specific to templates, or a new temporary CSD for a large-scale cleanup operation? —

4004: 3986: 2164:

Move it to userspace and then re-apply U5 (because it's just an auto-biography with links to social media?) Or you think U5 doesn't apply here for reasons other than namespace?

1580:

applied to non-media files other than PDFs, but Knowledge hasn't supported uploading them for a very long time (over a decade I think) and almost all of those have been deleted.

533: 8482: 8426: 6604:

That is exactly the other way around though – that's a platform unrelated to Knowledge that is used for Knowledge. This is Knowledge being used things unrelated to this site. ―

4909: 4512:. Adding one week is pointless when editors have had six months to work with it. Draft space is not meant to be indefinite and this change seems to be a step in that direction. 3215: 3105: 413:

I have said this before, but I think that G5 should be amended or abolished. Since people do not seem to want it abolished, here are a few suggestions for potential amendment:

4808:

It's a matter of factual accuracy. Obsolete is, by definition, a permanent status. So on this basis, the T and X groups aren't obsolete, so we shouldn't pretend they are. —

2141:

is imho clearly the attempt of creating a userpage, just in the wrong namespace. The correct course of action would imho be to move the page to this user's userspace. Regards

160:

about a draft where an editor is complaining about the family's pet dog that was suggested be deleted under CSD G10 that seems a stretch of what was meant as an attack page.

8296:

topic at Y becomes better known as X so someone boldly moves Y to X, this is OK as the RFD shouldn't prevent a future move but a page title swap could be preformed if needed.

6922: 6877: 6111: 6086: 6053: 2220:

It is deplorable practice to move a page from one namespace to another in order that a CSD criterion that did not apply in the first namespace can then be used in the second.

2191: 2122:"blatant": if there's any ambiguity at all, send it to XfD.) But if interpreted correctly, it could certainly relieve some of the pressure on MfD etc. without risking abuse. 1159: 8669: 8402: 8388: 8186: 8129: 8113: 7255: 6989: 6783: 6210: 6179: 2547: 2237: 2152: 1278: 1256: 1193: 507: 8350: 8322: 8280: 8088: 7404: 7373: 6613: 6599: 6586: 6069: 4076: 3377:) Either I'm a terrible communicator, or maybe... could it be that folks could perhaps maybe take just a little bit more time to actually read through the entire proposal? 2470:

The problem is that "substantially identical" is highly subjective. We've never had a formal process for recreation, and that's fine, but it does mean that some go through

2321: 2110: 2085: 1909:

page that we would need to keep in sync. I certainly support making it part of the policy. If it is moved then the last line of this page's edit notice will need updating.

1899: 1508:

shows we have up to 487 local PDFs. Not qualified with files, but I think it would likely be beneficial to at least look through these PDFs before removing the criteria. --

8683: 8652: 7973: 7506: 7387: 6936: 4494: 3250: 3190: 2763: 2389: 1340: 1317: 698: 8462: 8442: 8228: 7817: 7410: 7305: 7224:

Thank you for the ping. I see no reason to keep talk pages in those situations listed by Magog. Is it possible to find an example where the page should not be deleted? --

7203: 6900: 5718: 4154: 3754:

PROD announced for over six months. Creating (or improving) some process to make it easy(er) to find promising drafts would be welcome - some template and category(s)? -

3236: 2296: 2246:

and accordingly explicitly forbidden. Anyone doing that should expect serious consequences, and admin repeatedly doing so should not be surprised if they are desysopped.

1534: 778: 8585: 8241:

G5 is controversial enough at the best of times it is not possible to predict whether knowledge of the creator would have changed the course of discussion in every case.

7753: 7723: 7489: 7233: 7215: 5987: 5969: 3483: 2637: 2177: 1779: 1301: 476: 8633: 8616: 8066: 7925: 7739: 7528: 7465: 7422: 7274: 7060: 7045: 6850:. The page was created by a newcomer, and the most useful thing that could be done would be to talk to him like a person, not fill his user_talk with bitey templates. — 6666: 5228: 5144: 4471: 4052: 3742: 3509: 3013: 2998: 2983: 2966: 2255: 1064: 8807: 6859: 6568: 5798: 5780: 5568: 5536: 5466: 5445: 5413: 4453: 4418: 4357: 4258: 4174: 4093: 3719: 3626: 3429: 2564: 2495: 2426: 1728: 1709: 1032: 647: 6837: 6716: 6645: 5932: 5913: 5893: 5872: 5853: 5837: 5822: 5763: 5355: 5203: 5074: 5033: 4841: 4399: 4115: 3589: 3563: 3538: 3410: 3396: 2705: 2006: 1990: 1696: 1517: 1400: 1380: 1236: 359: 7948: 7803: 7329: 6734: 6554: 6461: 6442: 5515: 4754: 4372: 4233: 3651: 3271: 3133: 3065: 3047: 2504:- the key thing here is the phrase "for explicit improvement" - if a G4-eligible article is moved to Draft: space and then left alone, it's still eligible for G4. -- 2304: 1560: 1428: 896: 301: 278: 256: 230: 7691: 7674: 7543:, on the basis that many people accept the existence of a Knowledge article as strong evidence that a company actually exists, is reputably large, and safe to use. 6371: 6353: 5556:, with the draft being left untagged. Presumably when this is done, it is on the reasonable grounds that the article, having a newer timestamp, is the duplicate. -- 5324: 5269: 5187: 5173: 5059: 5049: 5015: 4930: 4658: 4309: 4031: 3868: 3817: 3795: 3695: 3672: 3314: 3043:

to let the draft just get deleted anyway. If they're in between, then someone who's created a promising draft and is somewhat active is probably worth mentoring. —

2272: 1667: 1643: 935: 764: 8773: 8564: 7607: 6769: 5978:

you're not certain well you take it over anyway as it's no real inconvenience to you but you're not going to get upset if it turns out it isn't important to them.

5738: 5246: 5159: 5116: 4989: 4817: 4803: 4720: 4531: 4278: 4216: 4191: 3763: 3356: 3335: 3155: 3082: 3037: 2616: 2602: 2582: 1624: 1593: 1472: 1451: 807: 324: 157: 8467:

Regarding Tiln the DAB has been moved to the former location of the hamlet "Tiln, Nottinghamshire" and then redirected to it so the history has been kept anyway.

6800: 6755: 6389: 6037: 6011: 5430: 5398: 3291:

would be good, as it would give a reliable way to see what drafts are soon becoming eligible for deletion. The few users who work on rescuing worthwhile content (

2516: 2362: 2336: 952: 490: 8011: 6818: 5341: 5099: 5005: 4972: 4885: 4827: 4702: 4432: 4331: 4292: 3901: 3610: 3463: 2678: 1679: 1505: 979:

fair, though from Trialpears' comment you can see that this really isn't used often either way. I'm not experienced with Quarry, so I did what I knew how to do.

913: 872: 267: 202: 7903: 7882: 7652: 7593: 6523: 6509: 6479: 6422: 6403: 5294: 4788: 4769: 3956: 3088: 2730: 1864: 1461:

OP appears to have a fundamental misunderstanding of the difference between NC/ND licenses and non-free content/fair-use. This proposal is unworkable as-is. -

340: 7628: 7016:

I am not opposed to the change of language, and would be willing to participate in such a discussion at the RFD Talk page. Please notify me when that happens.

6930: 6338: 6320: 4673:

Is this really the case, that these entire groups of CSD are obsolete? Or is this a misconclusion based on them being empty of active criteria at the moment?

3847: 1133: 853: 836: 445: 97: 89: 84: 72: 67: 59: 8511: 6258: 4958: 5452: 3622: 3227:

adding more rules to this is not the way to go. I'd support DRAFTPROD in addition to the current G13 process, but I don't see G13 as inherently problematic.

2067: 1795: 1007: 992: 967: 746: 271: 7993: 7857: 7842: 7641:

to warn readers that the content might not be verifiable, thus removing any benefit the potential scammers could have from the article's existence. Regards

4708: 4685: 3933: 2792: 1364: 1201:

as per Thryduulf. If the explanation of why a speedy deletion criterion isn't speedy, maybe it isn't a speedy deletion criterion, and can go through TFD.

943:, largely per Trialpears. This isn't significantly used at all, and the rare cases where this does occur can easily be/are dealt with through other means. 181:

G10s are only for living persons. Dogs, companies, or anything that does not fit that definition should not be deleted under this criteria. That being said,

8043: 6741: 5625:

I am not proposing specific wording yet as I want to get agreement on the principle first (and I'm not the best at concise language for things like this).

4995:

but ultimately it's up to the admin's judgement and there are definitely situations in which a page can be deleted even if there are Keep comments at XfD.

4571: 1837:

note, I find it problematic that the discussion about it was closed by the same person who proposed it. An accurate closure requires an independent closer.

7495:

still has to fire up AWB and go tag bombing). It shouldn't be difficult to write a bot/db query service that returns this data on a per-project basis. -

6362:

The wording seems incredibly nebulous and as a result not suited for CSD. U5 is already, in my opinion, abused and should not be expanded in this manner.

4779:

possibility of it becoming occupied again, IWC the section on the page would be reinstated and the new criterion would continue the numbering sequence. —

1761: 7730:

If anyone wishes to close this proposal, as the proposer I'm happy to admit it's a dead duck! I don't know the procedure for termination of bad ideas...

6122:: perhaps users will think twice about making a questionable deletion nomination if there's a risk that it might restart the six-month clock altogether. 2742:

Deleting the article makes no sense, though. If the patrolling admin believes that it is not good enough, then they should restore it to draft space. --

1823: 6431:

be move to its proper namespace. That is true regardless of whether the page merits deletion. If it meets a speedy deletion criterion, then delete it. ~

1633:

That list has 97 PDFs. Even if they're all useless to the project (and sister projects) it's not something which would take long to handle through FFD.

1019:: the bot removes any such images in any case, and egregious cases can be nuked under U5 if needed. Criterion is not necessary and finds almost no use. 7782: 6170:

That's significantly worse than the status quo as whether something is an "improvement" is subjective and something that can and will be argued about.

4728: 2404: 1495: 209: 6956:

CSDs must be easily defined in an unambiguous manner. The mere existence of other pages making mention of the subject is not sufficient; for example,

5884:

think your characterisation of it and speedy deletion of it, was incorrect. At the very least this needs to be seen by someone who can speak Bengali.

5307:

as such, if someone removes the XfD template before the XfD has closed, as part of a blanking that would invoke G7 or otherwise, it should be restored

5123:

In my opinion, an ongoing AfD with keep !votes other than the creator should never be speedy deleted for a notability-related criterion (e.g. A7). --

4876:

reinforces the idea that A10 shouldn't be used. I see multiple avenues for resolution here, including someone pointing out that I'm hopelessly wrong.

2946: 2886: 393: 8528:

Should deletion criterion U1 (User requests deletion) be merged into deletion criterion G7 (Author requests deletion)? 12:55, 21 December 2021 (UTC)

7036:

I strongly agree with the substance, of redirects that subvert a better search function result being bad. However, I don’t think CSD is the answer.

5899:

foreign language articles duplicating topics we have articles on are suitable for other Wikipedias. I'm not willing to support it just because these

4603: 3322:, except it doesn't, since Firefly's bot delivers a message a month in advance telling the page creator it will be eligible for deletion in a month. 2852:

Looking briefly through some past discussions, I see that some opposition to such proposals have been along the following lines, to which I respond:

2502:

content that has been moved to user space or converted to a draft for explicit improvement (but not simply to circumvent Knowledge's deletion policy)

6254:

Another is that G6 abuse (deleting non technical things with non-trivial histories) should stop, in favour of explicit specific objective criteria.

7731: 7666: 7561: 6543: 6281: 5952: 4642: 4145:. With the sorting of the chart and the inclusion of a sentence or so, you can generally quickly identify anything that is worthwhile in the list. 3991:

I presumed the purpose of this proposal was for more experienced editors watching or wanting to be notified of drafts, not for new editors, as per

2841:

This has been discussed a few times before, but I believe there are clear benefits to implementing a one-week (or similar) delay to G13 deletions.

2696:

to weigh in on the issues being discussed here, and maybe shed some light on the underlying problems and possible approaches to addressing them. --

1087: 235:

I've added the full text just for reference at the top of this thread, but "articles" being changed to "pages" makes sense because G10 is valid in

174: 8303:

G14, agree with King of Hearts, if in the case of Tiln there's a consensus to move at the RM then G14 would be acceptable, if I made a request at

7968:

if there is a reference that shows the station is licensed, my position is yes, you should need to use PROD and not CSD. In the specific case of

7617:

are for and speedy deletion is not. Either it's obvious enough to meet the current G3, G11 or A7 criteria or it requires more discussion. Regards

2182:

This guy has lots of edits to articles so U5 does not apply. Every editor has the right to a userpage with a bio and links to personal web pages.

6846:. Draftspace was created to contain the junk, and devoting new processes and heavy discussions to draftspace’s most harmless worthless things is 6288:, but doesn't seem to fall under any existing criterion. Let's add one. (Or possibly U5, if some verbiage were added there to cover Draftspace?) 5499: 5490:. I believe this codifies existing practice and just makes things clearer, but in case that wasn't the case I wanted to allow others to comment. 3604: 3522: 3168: 2859:

As described above, it would allow regular editors, who may not have noticed the draft having gone stale, to take a new look and maybe rescue it.

2819: 7682:

it will be possible to rewrite the article to be an NPOV article about the scam rather than promoting it, but all that will require discussion.

7362:. In regards to actual discussions on file talk pages, do these occur often? Is the workload of copying/importing those discussions worthwhile? 5178:

If there is active discussion about the merits of a page then deleting it is potentially controversial and so CSD cannot, by definition, apply.

2892:

Note: I've rewritten the proposal as above, seeing as the main points weren't being effectively communicated. The original post is hatted below.

8292:

F8, agree should probably have a new discussion, it may be because it became free content or permission given but yes probably needs a new FFD.

7700:

A scam is a hoax, and using Knowledge to perpetrate a scam is vandalism. If a "likely scam" is likely enough so to merit speedy deletion under

7074: 4182:

If you want to alert WikiProjects or whatever, that should just be done a weak earlier. Proposing G-13 be "6 months + 1 week" is... unhelpful.

4103: 2716: 2438: 6118:

I agree with Oiyarbepsy: this is instruction creep. Additionally, the present system has the unintended but beneficial effect of discouraging

3375:"These notifications are posted at the talk page of the draft creator, and are useless for attracting the attention of other regular editors." 8152:

so X1 is moved to X and the DAb page is moved to X (disambiguation), X (disambiguation) should then be able to be deleted under G14 because

7480:

Deleting these is a good idea. Even for existing files, the vast majority of these talk pages is useless and should not have been created. —

4270:, based on the assumption that there are probably some diamonds in the rough that maybe somebody somewhere might rescue is just Kafkaesque. 7540: 6884:

That's way too broad. It would be open to too much interpretation in mainspace, especially in topic areas commonly rubbished as "cruft". –

5578: 2442: 8757:

Pages with WikiProject templates should not be deleted, speedily or otherwise, as they remain useful to the WikiProjects that placed them.

5725:

sure making it harder to delete these usually-poor articles is going to be beneficial, so I'd love to see some actual statistics on this.

1965:

I don't think it has the kind of acceptance which justifies being made into policy, in particular lots of the existing CSD don't meet it.

143:

are met. Other pages violating the Biographies of living persons policy might be eligible for deletion under the conditions stipulated at

8123: 4915: 2573:

Hold up, someone is speedy deleting pages that were approved through articles for creation? Some serious trout slapping seems called for

769:

Based on comments below, I'm revising to say not to include this as part of U5. MfD can handle this situation just fine when it happens.

47: 17: 7545:

In the case of ABN assets, it's alleged that a scammer has set up a website that has nothing to do with the very large, similarly-named

8133: 7976:

it is affiliated with doesn't have an article. The only actual source appears to be a Facebook page. It probably should be CSD-able.

6559:

Even if so, this feature wouldn't be an article. Isn't draft space exclusively for content intended to qualify some day as an article?

3384: 3296: 3092: 2464: 6493: 2345:

on the grounds that almost anything blatant can be dealt with under other criteria, and the few that can't can go to MFD. Agree with

7909: 7450: 733:- not a single U3 among them. There is no reason to keep a redundant criterion that doesn't solve any problem that currently exists. 247:

almost entirely refer to BLPs and living subjects, which gives the implication that those are the only pages that would be eligible.

218: 213: 156:"subject" or "entity" to go beyond human beings. I guess companies and organizations fall under the rubric of "entity" but there was 4900:(recently created redirect for an implausible typo). If the title will make for a plausible redirect, then the existing wording of 7969: 7931: 6760:

Genuinely curious how long it would last in the WP space before getting sent to MFD, though that's a different matter to this one.

5281: 1606: 8104:. Assuming FM stations are spaced no closer together than 0.2 MHz, there isn't room for even 40 or so in the same reception area. 6636:

fails the first 3 of 4 NEWCSD criteria. Better to handle via existing processes and user conduct if it becomes a recurrent issue.

6329:. While I generally have no opinions on the matter, I'm not sure there's enough "new" here to justify re-opening that discussion. 4936:

You absolutely can tag an article for speedy deletion. AfDs get closed as speedy delete pretty regularly. Here are some examples:

3175:

for an example of the message given. With this in mind, adding additional steps and complexity to G13 does not make sense to me. –

6591:

That may not have been the intention of the creator of this draft, but chatrooms are sometimes used for Wiki-related activities.

4646: 4586: 2500:

The G criteria apply in all namespaces except those specifically excluded (such as User: space for G2). G4 says that it excludes

1094: 140: 128: 8072: 8026: 4610: 4102:

months, nor for them to track drafts for 6 months to avoid deletion. We have the ability to categorize CSD's by date (example:

3371:"It would allow regular editors, who may not have noticed the draft having gone stale, to take a new look and maybe rescue it." 1951:

Separately, should we change the information icon to something stronger? The edit notice on this page uses a warning triangle.

1147:

notes, expansions of the criteria are intended for situations that occur frequently. It probably would be best to take this to

616: 374: 8502:

RFC created in a misunderstanding of the difference between the two criteria, with no hope of reaching the desired consensus.

6790:

No, the fact something isn't an attempt to write an encyclopedia article doesn't mean it's appropriate for another namespace.

3663:. They've already had 6 months, how long more do they need? It just gives another chance for people to keep abandoned drafts. 3200:

removed without fixing the underlying notability issue. Could also lead to some ugly mass DRAFTPRODs and mass un-DRAFTPRODs. –

2845:

maybe rescue it before it's deleted, sparing the need to go through the WP:REFUND process. This could also be integrated into

2417:(frequent), per Hut8.5 I have severe doubts that anything not redundant to G11 would meet point 2 of NEWCSD (uncontestable). 2312:, and with a lot of the webhost stuff classifiable elsewhere, I'm not sure how frequently an extension here would be needed. 7770: 4581:

Are TV channels/stations deletable under A7? I've encountered this problem for the second time in a week – the first time I

8523: