Wikipedia talk:Criteria for speedy deletion/Archive 62

Requiring taggers to notify page creators
Currently the policy reads Users nominating a page for speedy deletion [...] should notify the page creator and any major contributors. I propose we change this to read Users nominating a page for speedy deletion [...] must notify the page creator and should notify any major contributors or something similar, maybe only for certain criteria where notification is useful (like G12, G11, A7, A9, A11 etc.). There is a current discussion at AN/I about one user nominating >500 pages in a month for speedy deletion without notifying a single user which imho highlights the problem. As points out at AN/I, not notifying users can both be BITEy and lead them to repeat their mistakes over and over again because no one told them otherwise. With plenty of tools doing the job of tagging and notifying at the same time (like Twinkle), there is no real reason why we can't change the policy to require such notifications. Regards  So Why  19:16, 29 January 2017 (UTC) *Support It should be easy to just remove the option to not notify from twinkle. -- Iazyges   Consermonor   Opus meum  19:46, 29 January 2017 (UTC)
 * Support I know Wikipedia doesn't like absolutes, but with so many available tools this is a no-brainer. Primefac (talk) 19:23, 29 January 2017 (UTC) Stricken, see below. Primefac (talk) 00:54, 30 January 2017 (UTC)
 * Support this; I've seen similar- although less extreme- cases to the one under discussion, and it's really a case of by doing one small thing (here), we can avoid ourselves more AN/I threads (there) in the future, thusly saving everyone a lot of time and trouble- both the reported and the reporters. O Fortuna!  ...Imperatrix mundi.  19:43, 29 January 2017 (UTC)
 * Changing to Oppose as currently written, it should not cover obvious vandalism. -- Iazyges   Consermonor   Opus meum  20:44, 29 January 2017 (UTC)


 * Support because Twinkle makes this very easy. Enterprisey (talk!) 19:52, 29 January 2017 (UTC)
 * Does Twinkle identify and notify major contributors?-- S Philbrick (Talk)  20:23, 29 January 2017 (UTC)


 * "where notification is useful". A look through ClueBot's talk page history will show some occasions where it's a bit silly to require notification. There's also dynamic IP addresses who create drafts and talk pages. Say there's an image talk page containing only spam or copyvio, created by a dynamic IP address two years ago - it's nonsensical to require notification. Needs refinement. -- zzuuzz (talk) 19:57, 29 January 2017 (UTC)
 * As I said, it was just a suggested wording. If there is sufficient support for such a change, we can then work out the details. I agree that there could be language for those situations you mention and I'm happy for a different wording suggestion. Regards  So Why  20:18, 29 January 2017 (UTC)
 * Hence I'm not opposing. Though I don't think there much ambiguity in the word "should", it is indeed good for normal, good faith editors to receive notification where useful. It's just finding a succinct unambiguous way to put that I have concerns about (I also agree things like G3, G5, and G10, bad usernames, and repeated notifications should be left completely out of it). -- zzuuzz (talk) 20:30, 29 January 2017 (UTC)
 * Oppose as written. We should not require notification for G5 (as that would feed the trolls) and G7 (that would even more confused a newbie who tried to delete a page by blanking it) and possibly others. Also the page creator is not necessarily the article creator, e.g. a page expanded from a redirect. Mandatory notification of major contributors would cause excessive bureaucracy for some articles. If the creator is blocked, e.g. for adding many copyvio articles, and a user finds another G12 candidate by them, it ought not to be required to notify them yet again about a reason they have already been made aware of. Iazyges' suggestion of removing the ability not to from Twinkle is ill-thought-out. This proposal is a good example of why IAR is a policy. BethNaught (talk) 20:19, 29 January 2017 (UTC)
 * I'm all for IAR in the right places but the current wording makes it okay for users not to notify good-faith editors. As I have written above, I wouldn't mind it to be restricted to those criteria that usually need notifications and I'm more than happy to accept proposed wordings. Since this is not a simple yes-or-no-question, maybe someone with more language skills can create some different worded proposals for us to discuss? Regards  So Why  21:20, 29 January 2017 (UTC)
 * That would make things even more complicated, and would lead to a lot of discussions about when it is and is't ok to ignore this unnecessary bureaucratic rule. Proposing a major policy change because one person is behaving in a way you don't liek is seldom a good idea. Beeblebrox (talk) 23:35, 29 January 2017 (UTC)


 * Oppose as written. (per BethNaught) I'm very sympathetic to the goal, but like BethNaught, I think this needs a little more work. The word "must" and a policy statement is a very strong statement implying that there are no exceptions. Anyone failing to do a notification, whether inadvertently, or deliberately with what they believe to be a good reason is guilty of a policy violation which we normally treat seriously. It is easy to imagine finding some article which qualifies as a CSD, then doing further investigation, and learning they are using an automated or semi automated process to create hundreds of inappropriate articles. While some notification should occur, it is easy to imagine that the hundreds of other examples might be mass notified and mass deleted without notification. It would be absurd to treat that as a policy violation. If nothing else, language such as "may be only for certain criteria" needs a lot of tightening before can be approved as policy. I preferred an approach that identifies notification as a best practice, and put the burden on the editor not doing notification to explain if asked, but creating an absolute rule requires a lot more investigation.-- S Philbrick  (Talk)  20:38, 29 January 2017 (UTC)
 * Would this also apply to administrators, requiring them to inform users of reasons for deletion when they see a speedy-delectable page and just go ahead and delete it without a nomination? I can't be the only one who does this all the time,and there is no automated tool for notifications-after-the-fact, and I'm not going to jump through the hoop of nominating soemthing I know I'm going to delete five seconds later. Beeblebrox (talk) 21:49, 29 January 2017 (UTC)
 * I also think we should explicitly discourage notification when nominating attack BLPs, a warning to stop crating such pages (without reproducing the name of the page or encouraging them to explain why it isn't an attack page) is a more appropriate response. Beeblebrox (talk) 21:52, 29 January 2017 (UTC)


 * Oppose, while notification should be encouraged, I don't think it is a good idea to make it mandatory. Who is going to enforce this and how? Are you asking for deleting admins to check for notification before deletion? I am not going to do that. If a user mass-nominates pages that should be deleted, fine. If a user mass-nominates pages that should not be deleted, that should be caught by admins, not via notification to page creators. —Kusma (t·c) 21:55, 29 January 2017 (UTC)
 * The inevitable result of such a rule is that automated tools become a de-facto requirement for requesting speedy deletion; the result of that, in turn, is to further reduce the already-vanishingly-rare practice of notifying major contributors that weren't the original author. —Cryptic 21:56, 29 January 2017 (UTC)
 * Support this. It only makes sense, because last time I checked, page authors were encouraged to vote on any AfDs of their work (if the page gets that far) so why is this different? Besides, if they don't see the reason given for deleting, they won't know what they did wrong and might repeat the mistake. I wouldn't support notifying creators of attack pages though. White Arabian Filly  Neigh 22:57, 29 January 2017 (UTC)
 * Mixed support CSDs of good–faith article should have notifications, especially of long standing articles. CSDs of bad–faith articles (attack, blatant hoaxes/vandalism, etc.) that are discovered during curation or are new articles can do without, as long as there is a warning placed on the user's talk. Sockpuppetry cannot be proven by the normal user so do not see why that would exclude a notification/warning.-- &#9790;Loriendrew&#9789;  &#9743;(ring-ring)  23:29, 29 January 2017 (UTC)
 * Sockpuppetry can be proved by normal users in some circumstances (to a sufficient level of evidence to block, at least). If not, why would there be non-admin SPI clerks? BethNaught (talk) 23:58, 29 January 2017 (UTC)
 * Oppose As discussed, there are many good reasons to not notify the page creators. If the article meets the criterion for CSD, you don't need to talk to us, you need to talk to the admins that deleted those articles. Chris Troutman  ( talk ) 23:39, 29 January 2017 (UTC)
 * Oppose as written I agree with the principle that, at a minimum, a page's creator should be notified if it is tagged for deletion but a simple, prescriptive "must" causes more problems, as others have mentioned above, than it solves. On the other hand, the nomination should show up on the watch lists of interested editors. What I think we should require though is an edit summery which clearly states a deletion tag has been places. I firmly believe that, whether intentional or not, failing to note that a deletion tag was placed in an edit is avoiding scrutiny. J bh  Talk  00:07, 30 January 2017 (UTC)
 * Comment - I commend the intent here, but the current wording makes it very clear that notification is the norm, and is worded in such a way as to allow for exception for G5, G7, and the like, per WP:IAR. If we have users who refuse to follow this commonly accepted practice then they should be appropriately sanctioned or barred from nominating articles for speedy deletion.- MrX 00:51, 30 January 2017 (UTC)
 * I can agree with this. In thinking about it, most users do follow best practices and either use Twinkle or manual means of notifying the creator/contributors about an XFD/CSD. Individual cases (such as the one that spurred this nomination) can be dealt with on an ass-needed basis. Primefac (talk) 00:54, 30 January 2017 (UTC)
 * Everyone needs one and only one ass. Excess asses are detrimental to the project.  J bh  Talk  01:11, 30 January 2017 (UTC)
 * Heh, whoops. Slight typo! Primefac (talk) 01:15, 30 January 2017 (UTC)
 * An ass is a donkey. If you need one, two are better. Are you to speaking of arses?  --SmokeyJoe (talk) 12:11, 30 January 2017 (UTC)
 * Oppose per above. Difficult to enforce, there are situations where the creator should not be courtesy notified, and because this fosters an unhealthy degree of process creep.  -  F ASTILY   01:09, 30 January 2017 (UTC)
 * Weak Oppose: If it's a newbie creating a page, we should notify the page creator. Vandals and trolls won't get notified either per WP:DENY. I'll alternatively support requiring an edit summary explaining why the CSD tag was in place.  KGirlTrucker81 huh? what I've been doing 01:16, 30 January 2017 (UTC)
 * What good would an edit summary do? If the page is still there, the CSD tag explains the reason, and if it's been deleted the creating user won't be able to see it but would be able to see the logged reason for the deletion. Beeblebrox (talk) 01:34, 30 January 2017 (UTC)
 * It helps informs creators of the deletion nomination rather notifying it (especially if the creator looks at the page history or on their watchlists). KGirlTrucker81 huh? what I've been doing 02:42, 30 January 2017 (UTC)


 * Oppose. It's process creep. It may be a nice thing to do, but it shouldn't be a requirement. While inactive users aren't usually an issue for CSD, I have no doubt that a requirement here will be used as a precedent for making it mandatory in AfD, making more process creep. Niteshift36 (talk) 01:45, 30 January 2017 (UTC)
 * Oppose . The idea is worthy, but in the vast majority of cases, CSD is done using a script such as Page Curation (or in some cases, Twinkle) which does this automatically anyway. is correct in the fact that admins will occasionally immediately delete some pages, an act which does not leave a message for the creator, and  such cases are often followed by a block. This is perfectly legitimate - trolls, vandals, and spammers will understand soon enough why their page has been deleted.
 * What we do need and what the community should be looking at, is to repair the gaping gap in patroller competency left by the rollout of the New Page Reviewer right, in which templating for deletion can still be wrongly done by very newbies and totally inexperienced users - a practice that continues unabated and with a high rate of inaccuracy. Kudpung กุดผึ้ง (talk) 01:49, 30 January 2017 (UTC)
 * The thing that's not really being said in this proposal is that this is a reaction to one specific user who nominates a lot of new articles for speedy deletion and more often than not doesn't bother to notify. It's at ANI right now. I tend to agree with your perspective, that changing policy over one user while ignoring issues with dozens if not hundreds of other users is not a good approach. Beeblebrox (talk) 02:36, 30 January 2017 (UTC)


 * Support in principle while some of the bugs need to be worked out, the fact that the EASIEST way to do this currently notifies page creators should inform our discussion. We need to identify and implement 'major contributor' discussion, too.  For example, I started Bella Ramsey, but as a redirect.  User:Sandstein came along a week later and expanded it into its substantially current form once more RS became available.  That sort of thing should not be hard to identify based on number of edits, percentage of article size contributed, and the like. Jclemens (talk) 01:53, 30 January 2017 (UTC)
 * Yes, redirects need to be separable from the main edit history. There are multiple reasons for this, but too much to explain here.  Unscintillating (talk) 01:22, 21 February 2017 (UTC)


 * Oppose - Notifications should ideally be mandatory when we're dealing with good faith attempts at contribution to the encyclopaedia. They should not be offered, let alone mandated, for articles that meet G3 - "vandalism", G5 - "Created by banned/blocked users", and most especially G10 - "Attack page" criteria. It would also be entirely redundant to make them mandatory for G7 deletions as well - "Author requests deletion". Mr rnddude (talk) 02:17, 30 January 2017 (UTC)
 * I agree with you, inasmuch as we're talking about correct tagging. G3/5/10 have been applied on multiple occasions to articles that in no way met the respective criteria. Jclemens (talk) 02:30, 30 January 2017 (UTC)
 * You bring up a valid point. Improper use of the CSD rationales is an issue which plagues Wikipedia. I have done some CSD myself (about 100 tags) and occassionally the rationale I use did not align with the deletion rationale the deleting admin used; one that comes to mind for me is a G10 article that I tagged as G3 because I was unsure if it was an attack page or just plain vandalism - Jack Smithson. I don't remember the content of the page. I use twinkle so it automatically notified the creator. This is one of those situations where it is difficult to really meet all possible situations within a single statement. I favour letting editors use their heads and work out what needs a notification and what doesn't. It's unfortunate that many take the recommendation to mean "please ignore this" instead of "use your bleeming head". It's even more unfortunate that many former patrollers and current CSD taggers don't have a good enough grasp of the policy to do so. You know, it occurs to me that rather than creating a new set of permissions or what not for CSD, AfD, or XfD, it'd be far simpler to create a quiz which tests your knowledge of the process instead. If you demonstrate competency in it, then you may have access to the relevant XfD, if not, then you'll be required to get more experience (say 1-3 months with 500 mainspace edits) before being allowed to resit the test. Mr rnddude (talk) 04:01, 30 January 2017 (UTC)
 * Oppose as it is too strict. I have noticed that the curation tool for example will tag for delete but almost always fail to notify the page creator. There are also admins that delete copyright violations and other problem pages on sight without tagging or notification, is this still permitted? Anyway we could have a stronger statement than "should". Experienced editors will be expected to notify, and failure to do so will be mis-conduct. As mentioned above, for bulk deletes or where the creator should expect the content to be removed (eg socks, trolls, hoaxers and vandals) notification should not be mandatory. However if there is a possibility that the speedy delete is in error, or could be fixed, eg db-spam, or that the page creator will be educated, then notification will be expected. G6 and X1 nominations do not require notification either. Graeme Bartlett (talk) 02:22, 30 January 2017 (UTC)
 * Oppose. – SD is for pages that should be deleted on sight, without discussion. Administrators can do this themselves, and do it without advance notice, but non-admins can only flag them for administrator attention. Requiring users to give advance notice when flagging something for immediate action strikes me as oxymoronic. Sometimes when an administrator deletes such pages, on their own initiative or in response to a request, they will initiate a conversation or send a notice along the lines of "thanks for trying but that was deleted because...", or along the lines of "that was unacceptable and if you do it again there will be consequences". It is generally a Good Thing™ for administrators to do so if the contributor(s) might not already be aware of the situation and were not obviously acting in bad faith. Administrators can exercise their judgment on whether there is any point in attempting to communicate with spam bots and other bad-faith actors. It is not appropriate to require regular users to do so when flagging a page for administrator attention. ~ Ningauble (talk) 16:09, 31 January 2017 (UTC)
 * Actually, per note 1 on the policy page: In this context, "speedy" refers to the simple decision-making process, not the length of time since the article was created. Thus SD means it can be done without lengthy discussion. It does not - except in certain cases, like G10 - mean however that it has to be done immediately. Regards  So Why  16:47, 31 January 2017 (UTC)
 * If what I wrote could be construed to have referred to the time since the article was created then I apologize: such was not my intent. My use of the term immediate was intended to refer to taking action upon discovery, "without waiting for any discussion". ~ Ningauble (talk) 18:07, 31 January 2017 (UTC)
 * Oppose - the purpose behind using should in the wording of deletion guidelines is to strongly encourage, but not require, notification of interested users. A very good reason for not requiring notification (replacing "should" with "must") is that it creates a silly loophole whereby users can argue that a deletion decision is invalid on the sole grounds that particular users were not notified. The problem is: how do you determine who is a significant contributor who is required to be notified of a discussion, and how do you ensure that these users are notified? Before you start coming at me with your own definition of a significant contributor, understand that it varies from editor to editor as well as from topic to topic, such that we can never create a universal definition that some user will not argue about in a deletion review, and that is the problem with any wording requiring notification in deletion discussions. I'm opposed to the proposal as worded and you can assume I oppose any rewording under this thread, unless I comment otherwise. Ivanvector (Talk/Edits) 16:54, 31 January 2017 (UTC)
 * Oppose per Ivanvector. Notifications should be mandated where it is likely that the content was contributed in good faith and where positive behavior and/or content modification is likely, but this is subjective, difficult and shouldn't be policy. I also oppose restricting the requirement to certain criteria -- I have deleted thousands of pages under A7, G11 and U5 whose authors had no intention to contribute to the encyclopedia whatsoever. MER-C 06:23, 2 February 2017 (UTC)
 * MER-C has it right here. This is too complex a situation for a "must" and the ANI instruction is not a good analogue, as with that there are no ifs, buts, fuzzy lines or grey areas. If an editor is habitually not doing what they "should" in cases where they plainly "should" have done, they can still be called to account for that Noyster (talk),  10:39, 2 February 2017 (UTC)
 * Oppose One of the worst ideas ever is requiring people to show people who are trying to make things worse how they can make them even worse. Hipocrite (talk) 22:08, 2 February 2017 (UTC)
 * Oppose, per Hipocrite just above this, also because the first editor has no special right, because determinig "good-fait editors" is a near impossible task, because deletion nominators should not be forced to make a extensive set of edit just make a nomination (i.e. nomination should not be so hard as to discourage most nominations), because creating a policy based in one editor's behaviour or two is a poor idea. - note that I would support a MediaWiki feature that changed the deletion process including *automatic* notification of, e.g., editors watchlisting an article. Nabla (talk) 11:06, 11 February 2017 (UTC)
 * Oppose. Say a user creates copyvios, spam, pure vandalism, blatant hoaxes and/or articles qualifying for A7/A9 (lack of notability) en masse. Should we notify the user of every page created by it that is tagged for speedy deletion? That is a notification that is, like the page creation, en masse, and therefore is absurd. A concrete example of such a user is, that created tons of WP:CRYSTALBALL articles, was blocked, and got all of its articles prodded, speedied or nuked. That user evaded the block creating two sock puppets (User:22nd Century and Beyond, User:After2099ad) that did exactly the same thing. For more information, click here (a notification I've added to the first sock in 2017-02-01). I notified because I didn't realise the account was a sock. Otherwise, I wouldn't notify. Luis150902 (talk | contribs) 17:24, 15 February 2017 (UTC)
 * Oppose. While an editor in general should notify the page creator, I don't see a need to codify it as must, and having a "you must X excluding situations Y,Z, etc." is always going to have problems with additional instruction creep for each situation that can pop up. Better to have a "you should do X, except in Y,Z you must" type statement. The page creator already would automatically have the page watchlisted. Plus, uninvolved editors (admins in this case) are the ones really deciding if the page is truly notable or not. For CSD though, it's really up to the admins in the end. Kingofaces43 (talk) 16:49, 19 February 2017 (UTC)

Require notification for good-faith edits
Since opposition to requiring a notification for all pages is high and most indicate they might support a less strict proposal (which I already suggested above), how about this:
 * Users nominating a page for speedy deletion [...] must notify the page creator when using the criteria A1, A2, A3, A7, A9, A11, G11, G12, G13, U2, U3 and U5 as well as any file-related criteria. This does not apply if the page creator has been blocked/banned from editing indefinitely or is already aware of the requested deletion.

For those who mentioned cases where redirects were turned into articles, those cannot be deleted anyway since SD requires that all revisions meet a criterion. If an admin deletes such a page, it's already in error and we probably should remind admins about that. Regards  So Why  07:47, 30 January 2017 (UTC)
 * This is terrible. I didn't even get done reading it before i gave up trying to understand it. Beeblebrox (talk) 10:49, 30 January 2017 (UTC)
 * I don't claim to be Shakespeare and English is, after all, not my native language but it would probably be helpful if you articulated specific concerns instead. Also, as usual, I am open to different wording. Regards  So Why  11:21, 30 January 2017 (UTC)
 * This is one of those situations were a little bit more explanation and little bit less jargon would help, might I suggest a reword to; Users nominating a page for speedy deletion [...] must notify the page creator and should notify major page contributors, except when the page nominated meets criteria relating to pure vandalism, blatant hoaxes and/or attack page(s), or where the creator is a blocked or banned user. It's still overbloated, and I'm not sure that it is a viable solution anyhow. Mr rnddude (talk) 11:24, 30 January 2017 (UTC)
 * I found the first one quite clear, but think that A10 and G3 hoax and vandalism ought to be in there. A10s sometimes have a good reason that's not immediately obvious, and some G3 hoaxes and vandalism (as tagged) also aren't when explained. Might it be easier to list the ones you don't have to notify about? It is nice to see notifications on a user's page when deciding whether to block them of not (other checks are, of course, made...). PS Writing in Shakespeare's English wouldn't be a good idea. Quite a few English natives have trouble with his wordings... Peridon (talk) 11:54, 30 January 2017 (UTC)
 * Might it be easier to list the ones you don't have to notify about? - given that this would encompass a total of four criteria at most (three if we exclude G3 - G5, G10 and, if common sense allows, G7), it would be far easier to list those than the other 20 or so you would have to notify about. That said, the listing of each criteria presumes that each criterion "codename" is immediately identifiable to each person. I can identify only G2 - test page, G3 - vandalism/hoax, G10 - attack page, and A3 - no content, on command. Everything else, I have to hit the reference book, WP:CSD, to check. E.g. A7 - notability is actually A7 - no claim of importance. Very different things. So the wording should be both clear and easy to understand - i.e. as little jargon as possible. That said, I still managed to forget that hoaxes were part of G3. Mr rnddude (talk) 12:24, 30 January 2017 (UTC)
 * Instead of adding the wording to the lede, we can always add the requirement to the criteria themselves instead. I just listed them for easier discussion. Regards  So Why  12:33, 30 January 2017 (UTC)


 * I think it is perfectly logical. Always notify whenever a good faith mistake can be assumed.  --SmokeyJoe (talk) 12:06, 30 January 2017 (UTC)
 * One might think so but we wouldn't have this discussion if it were so simple. But I'd be fine if we used a less strict language. How about this:
 * Users nominating a page for speedy deletion [...] must notify the page creator unless the page creator has been blocked/banned from editing indefinitely, obviously has not created the page in good faith or is already aware of the requested deletion.
 * Regards  So Why  12:33, 30 January 2017 (UTC)
 * I like SoWhy's version, although maybe a note about retired editors could be made. I also wouldn't be opposed to a sentence somewhere noting that if you are unsure whether the contribution was in good faith it is best to notify, and there is no penalty for notifying where it is not required. — Preceding unsigned comment added by Thryduulf (talk • contribs) 14:00, 30 January 2017 (UTC)
 * Perhaps this then?:
 * Users nominating a page for speedy deletion [...] must notify the page creator unless the page creator has stopped editing indefinitely, obviously has not created the page in good faith or is already aware of the requested deletion.


 * Tazerdadog (talk) 01:37, 31 January 2017 (UTC)


 * I don't seem to have gotten any answer to my previous question of how this applies to admins who see a page that obviously qualifies for speedy deletion and they just go ahead and delete it. In most cases, at least speaking for myself, a post-deletion warning or notice can be dropped not heir talk page, but there is no explicit mention of a deletion nomination because there wasn't a nomination. Beeblebrox (talk) 22:48, 30 January 2017 (UTC)
 * I would think the way it should work is: if an admin speedily deletes a previously-unnominated page, they should be obligated to notify the user iff they would have to notify the user under this proposal if they had simply tagged the page. By my reading, the proposal doesn't address this explicitly, which may be a flaw in the wording of this proposal.  Obviously, the text of a was deleted notification versus a tagged for speedy deletion notification should be slightly different.  Tazerdadog (talk) 23:12, 30 January 2017 (UTC)
 * I think it (partly?) depends on why the page is being speedy deleted. For example, many G6 deletions don't really require a notification, all F7 and U3 deletions do. Thryduulf (talk) 23:31, 30 January 2017 (UTC)
 * How about adding this
 * The same applies if an admin deletes a previously untagged page, except maintenance deletions.
 * As usual, I welcome better wording. Regards  So Why  15:23, 31 January 2017 (UTC)

This is all completely pointless - notifying someone you've nominated their article for speedy deletion is a nice thing to do but in most cases will prove to be pointless, the user probably won't know how to quickly make the changes needed to avoid deletion or they'll return after the deletion has occurred. Notification for PROD and XfD is both nice, sensible and could easily be made a requirement since there's likely to be a week of discussion time available for an article to potentially be fixed and made compliant with our policies. There's absolutely no point in having an administrator notify users during the deletion process, as users can't see their own deleted contributions. The most sensible solution here (and one which is probably going to deal with the CSD nomination notification issue that is the root cause of all this) is to automate clear and understandable notifications for deletions, making log entries easier to find, and possibly providing users with access to their own deleted user contributions. Nick (talk) 19:25, 31 January 2017 (UTC)


 * The point of such notifications is less that the user might be able to prevent the deletion but rather so that they understand why the page was tagged for deletion and can strive to prevent making the same mistake again. Your alternative would solve this problem at least but would just shift the work to admins performing the deletions. That said, I personally wouldn't mind if admins were tasked with such notifications instead but this would not help in those cases where the creator is still online and could address the concerns before deletion. Regards  So Why  20:10, 31 January 2017 (UTC)


 * still oppose per myself in the previous section, plus instruction creep. Nabla (talk) 11:10, 11 February 2017 (UTC)

Reworded simple good faith proposal
Per above discussion, my current proposal, taking into account the various suggestions, would be this:
 * Users nominating a page for speedy deletion for non-maintenance reasons [...] must notify the page creator unless the page creator has stopped editing indefinitely, obviously has not created the page in good faith, is already aware of the requested deletion or it can be safely assumed that they are not interested in being notified. The same applies if an admin deletes a previously untagged page.

This would address both the case of a retired user as well as users that for various reasons (bots, deceased etc.) can safely be assumed not to be interested in such notifications. Thoughts? Regards  So Why  15:43, 31 January 2017 (UTC)
 * Support I am reasonably happy with this. Tazerdadog (talk) 15:47, 31 January 2017 (UTC)


 * Strong Oppose I don't know about you, but I seem to have misplaced my telepathy hat and so am unable to judge how "obvious" the faith, good or otherwise, is of another editor. Since this implicitly asks us to ignore WP:AGF and determine who created a page in earnest mistake and who created it in bad faith, it asks every CSD nominator and page patroller to somehow climb into the heads of  page creators. That means it creates yet another outlet for disagreements and drama without substantially improving anything.Eggishorn (talk) (contrib) 18:11, 31 January 2017 (UTC)
 * Support Makes sense, notification should be allowed. I interpret this as excluding blatant vandalism. If you can't identify obvious vandalism, you shouldn't be tagging articles. ThePlatypusofDoom  (talk) 18:28, 31 January 2017 (UTC)
 * I don't generally tag articles. My objection has nothing to do with my own activity, but with what it asks of those who do.  I agree that the proposer likely intends it to apply blatant vandalism.  From what I have seen of how things work here, however, I see it as opening an invitation to be used as a WP:POINTy tool.  Not everything needs a rule, and the current standard already generates enough heat.  Eggishorn (talk) (contrib) 19:11, 31 January 2017 (UTC)
 * Is there a way to word it better to remove some of the areas where disagreements will occur? Perhaps we could explicitly call out blatant vandalism and attack pages, which are the two main situations that phrase was meant to cover?Tazerdadog (talk) 01:13, 1 February 2017 (UTC)
 * This isn't a bad idea, but it's an unnecessary idea, no matter how the text is tweaked. We really shouldn't make project-wide rules or rule amendments to deal with the actions of one user. Whether the OP really is proposing this to deal just with that one user's edits or just was inspired by the discussions around them (and I assume it's the latter), the effect is the same. It's using blunderbusses to kill flies, and there is always collateral damage and unintended consequences from such an approach.   Eggishorn (talk) (contrib) 16:33, 1 February 2017 (UTC)
 * Problems might always exist but that does not mean we shouldn't have clear rules, especially when the vague wording is precisely the argument some users make for not notifying good-faith users. For example, WP:ANI has a clear "When you start a discussion about an editor, you must notify them on their user talk page." policy and it still has not been burned to the ground (so to speak) because of that rule, so we know that such rules do actually work. I do agree with you on principle though and I do believe that the problem is mostly with wiki-lawyering, i. e. arguing the wording over the spirit of the "should notify" rule. Maybe it might be sufficient to append this rule (e. g. "Should means do it to unless you have a good reason not to do it") but I doubt it based on this discussion. Fastily mentions WP:CREEP below but the reason we need such a change is precisely that we cannot admonish users for not doing something that is not required. Funny enough, I always read "should" in the German legal sense ("sollen" = "shall"); in our legal system when a law says "... shall be done" it means "you have to unless in special circumstances". That's why I was kind of surprised that so many users believe that "should" means it's just a suggestion. Regards  So Why  16:52, 1 February 2017 (UTC)


 * Strong Oppose. As Eggishorn said, the current policy causes enough heat as is, and adding this proposed clause will aggravate that situation.  This also reeks of process creep, which is something I am generally opposed to.  -  F ASTILY   22:48, 31 January 2017 (UTC)
 * Oppose. While I agree they're a useful practice, I don't think CSD notifications, even for supposedly good-faith contributions, are ever truly necessary. I also concur in Eggishorn's concerns that judgments about good faith would be a source of contention and bureaucracy. Rebb  ing  11:25, 2 February 2017 (UTC)
 * Oppose as one of the first users to have run headlong into the "not notifying people you are deleting their shit," squad, I'm happy to finally codify that notifications are optional. Hipocrite (talk) 22:07, 2 February 2017 (UTC)
 * Oppose (1) the creator of the page has no more "ownership" in it than any other editor (see WP:OWN), so why only notice to him or her? (see WP:CANVASS) (2) most of the speedy categories are such that the author is well aware of his or her transgressions (attack, vanity pages, utter nonsense, nearly empty pages, jokes and lies) and often only want to see what can be slipped through or what drama ensues (like real editors ripping each other over whether the article on someone's new dog is or isn't speediable) and finally (3) WP:IAR and WP:Don't feed the trolls both apply. Carlossuarez46 (talk) 02:31, 3 February 2017 (UTC)
 * Notifying the creator of a page about it being nominated for deletion is not canvassing. I'd even go as far to say that it is never canvassing (regardless of if they are the only contributor to the page that is notified). It is a standard accepted practice, so much so, that it is a streamlined option within twinkle. Furthermore, a good faith original author likely believes their creation is appropriate, which is the opposite viewpoint of someone nominating something for deletion. — Godsy (TALK CONT ) 03:47, 3 February 2017 (UTC)
 * You're simply wrong. Why the creator is any more important to be notified than every other editor who contributed is precisely selecting someone who one supposes has a "pro" bias toward an article he or she created and ignores other editors who, pro or con or totally unbiased, tried to improve the encyclopedia by either improving the article, identifying the article's shortcomings, stub sorting, or asking for the deletion of the article. Carlossuarez46 (talk) 21:00, 6 February 2017 (UTC)
 * Firstly, notification is more important for deletion discussions. Unlike them, if something meets criterion(s) for speedy deletion, it will likely be deleted regardless of input from its creator. That aside, should the creator be notified of a speedy deletion the vast majority of the time? Yes, it serves the purpose of making sure they know that the page was deleted and helps them learn what type of pages are inappropriate; Should it be mandatory? No, especially in certain cases. It is a good practice that is adequately recommended by the current wording. Lastly, it is generally very hard to discern if an editor has "stopped editing indefinitely" or that "it can be safely assumed that they are not interested in being notified". — Godsy (TALK CONT ) 03:19, 3 February 2017 (UTC)
 * still oppose per myself in the previous sections Nabla (talk) 11:12, 11 February 2017 (UTC)
 * Oppose for the same reasons as my previous comment in the above section. Kingofaces43 (talk) 16:50, 19 February 2017 (UTC)

RFC currently in progress regarding tagging "unencyclopedic" files for deletion with a 7-day wait
Watchers of this page may be interested in participating in an ongoing discussion at Wikipedia talk:Files for discussion. The discussion is a proposal to have certain files deemed "unencyclopedic" tagged and deleted with a new process similar to WP:PROD or existing file-related WP:CSD criteria with a 7-day delay after tagging for the file to be deleted. Steel1943 (talk) 22:42, 24 February 2017 (UTC)

New criterion: Article created to evade salted titles
I propose that articles which are created with titles specifically intended to evade salting be subject to speedy deletion. The specific example that has come up recently is Deletion review/Log/2017 February 22, where Steve Salis had been repeatedly deleted and eventually salted, so a user just re-created it under a different capitalization, i.e. Steve salis, to evade the salting. I'm not sure if this should be done by broadening the criteria of an existing case (any of WP:G4, WP:G5, or WP:G6 might work), or creating a new case completely. Before we get into haggling over the exact wording, I'd like to see if there's agreement in principle. -- RoySmith (talk) 13:31, 26 February 2017 (UTC)
 * Currently, what criteria is being used to speedily delete these pages?--John Cline (talk) 14:33, 26 February 2017 (UTC)
 * If the content is substantially the same as the one in the salted article, wouldn't that be a case for G4 speedy deletion? If it's not substantially the same content, why would we need speedy deletion?  Sandstein   14:45, 26 February 2017 (UTC)
 * G4 would only apply in this case if there was a deletion discussion involved. The example linked was repeatedly recreated, but only after CSD's, which would make it ineligible for G4. &mdash; Train2104 (t • c) 16:26, 26 February 2017 (UTC)
 * These cases (ought to) fall under WP:G3 blatant vandalism: deliberately creating a page at an inappropriate title to defeat a community protection level. In practical terms there's very little chance that such a creation is not done by a sockpuppet so I would be comfortable assuming WP:G5 also applies.
 * I have had a similar experience at Talk:Ramin Amiri. Definitely support in principle, even though other csd criteria applied in that case. Tazerdadog (talk) 17:06, 26 February 2017 (UTC)


 * Oppose as unnecessary. Just use whatever criterion it was deleted before if it still applies, G4 if it was a discussion. -- Tavix ( talk ) 17:10, 26 February 2017 (UTC)
 * Oppose. A G4 deletion is still applicable if the title is different (but not in a different namespace); if the old criterion (or any other) applies to the new page, it can be deleted by current policy. Otherwise, it shouldn't be speedy deleted. עוד מישהו Od Mishehu 18:15, 26 February 2017 (UTC)
 * Oppose per those above. Already covered by adequately by existing criteria. — Godsy (TALK CONT ) 18:56, 26 February 2017 (UTC)
 * Oppose We should not be deciding if an article belongs based on its title. We should be using the content and potential content to determine if we should have an article. If there was an article deleted multiple times 5 years ago as A7 and the title was salted indefinitely, that does not mean an article today should be automatically deleted just because someone created an article under a different name to bypass the salt. - GB fan 19:13, 26 February 2017 (UTC)
 * Oppose WP:CREEP and redundant per all previous replies. Beeblebrox (talk) 19:24, 26 February 2017 (UTC)
 * Oppose. Salting, especially unilateral salting, doesn't substitute for a deletion discussion. --SmokeyJoe (talk) 20:31, 26 February 2017 (UTC)
 * Snow Oppose: We already have G4 if its deleted at XFD etc. No need for another criterion. KGirlTrucker81 huh? what I've been doing 20:38, 26 February 2017 (UTC)
 * Comments (unsure) - The question is whether salting is about an article title or an article content/subject. The technical extent of it is, of course, the title, but presumably the intention of salting is more often based on the content or subject. Perhaps the community doesn't want salting to be a subject-based remedy, in which case this should be opposed, or a discussion determining as much should be a prerequisite. Otherwise, however, there should probably be some tweak in the language of G4 along these lines. Several people have opposed on the basis that G4 covers this, but it only applies if there's been a deletion discussion and if the content is sufficiently identical to the version deleted via that discussion. If there's been sufficient discussion that we shouldn't have such an article and recreation has been disruptive enough that a salt was considered necessary, but those discussions didn't take place at XfD, then G4 doesn't apply, even if the content is identical. If the discussions did take place at XfD, but the prose has changed or a source is swapped out, who knows whether an admin will interpret it as "identical" (anecdotally, some clearly do not - and thus G4 wouldn't apply). We shouldn't be salting encyclopedic topics except short-term protections to avoid short-term disruption, and should only salt on an indefinite or long-term basis when there's enough discussion/research to find that it's extremely unlikely it could possibly be recreated in an appropriate way with extant sourcing (or in extreme cases of long-term abuse, I suppose). If sourcing changes in the future, the next step is to request unsalting and not to sidestep the salt. Perhaps an alternative to changing CSD is to document somewhere that if an alternative title is salted, a new article should be moved to draftspace for review rather than CSDed, and rather than sending back to XfD... &mdash;  Rhododendrites talk  \\ 21:56, 26 February 2017 (UTC)
 * Oppose (it's starting to look wintery). If the content is substantially the same as something that has been deleted via a deletion discussion it can and should be deleted under G4, so this is redundant. If the content is substantially the same as something that has been deleted under a different speedy deletion criterion then either (1) that speedy deletion criterion will still apply and can be used again. in which case this is redundant, (2) a different speedy deletion criterion will apply, in which case this is redundant or (3) no speedy deletion criterion will apply, in which case it should be speedy deleted. If you think it should be deleted but no speedy deletion criterion applies, nominate it at AfD (if it is recreated yet again, G4 will then apply - this criteria is then redundant). If you don't think it should be deleted then there is nothing to discuss here. It is also worth noting that evading salted titles is also done by people writing different articles to the one deleted and articles about subjects that are now notable but previously weren't but who don't know how to request unprotection of the title - these articles should not be deleted in most cases, let alone speedily. Thryduulf (talk) 22:50, 26 February 2017 (UTC)
 * I was going to support, but I'll endorse a Snowed Oppose. I presume there's a good reason a title was salted, and evasion of a salt makes a really good case that the salt should be implicitly extended. However I'm seeing really good arguments that a valid salt pretty well implies that some other delete criteria would apply anyway, and if no other criteria applies then there's a credible case that maybe speedy shouldn't be applied. This is buried under opposes, and converting intended-to-support to oppose. This is SNOWed and done. I'll suggest an alternate proposal below. Alsee (talk) 13:40, 27 February 2017 (UTC)

Alternate proposal
Text should be added somewhere to the CSD page to the following effect: Admins could already deem salting warranted in this case, but it would be good to have a policy basis for it. I believe this more effectively addresses the issue here, as well as the concerns raised.
 * If a page is being speedily deleted under existing CSD criteria;
 * and the page is evading an existing salt;
 * and the title has no likelihood of usage independent of the salted title;
 * a discretionary salt may be applied to the new title.

Note: Any page that would more properly belong at the salted title is presumptively evading that title. I don't think we really need to explain that on the policy page, but I wanted to make my intent explicit for this discussion. Alsee (talk) 13:40, 27 February 2017 (UTC)
 * Oppose. Excessive admin actions and time in place of talking to a newcomer. Repeated creation means someone wants or needs a discussion. --SmokeyJoe (talk) 13:59, 27 February 2017 (UTC)

G11 v. Under-Construction Template
I have a question. The question is whether the Under-Construction or In-Use templates, in any of their subspecies, should preclude tagging for G11. My assumption is that a reasonable administrator should defer to the In-Use template when an article has been tagged as any of the forms of A7, because the author may be working to establish notability. (I personally do not think that any grace period of time or any request for a grace period using a template should be honored, because articles should be built in user space or draft space, but I am aware that I am in a minority, and that a modest amount of time is allowed for A1 and A7 in general, and somewhat longer when the template is used.) My question is whether the request via the In-Use template should also apply to an article that is currently purely promotional. Should the author be allowed time to make the article no longer promotional, or should one go ahead and tag the article for G11 and let the author contest the nomination? Robert McClenon (talk) 04:08, 27 February 2017 (UTC)
 * If the article is good enough that one could potentially save it from G11 by adding to it, then userfy/draftify the article. If it's so bad that no addition could possibly save it (generally the case with G11s), just delete it. עוד מישהו Od Mishehu 05:26, 27 February 2017 (UTC)
 * You write: "If it's so bad that no addition could possibly save it (generally the case with G11s), just delete it."  I can't.  I am not an administrator.  The question is about whether I should tag it.  Robert McClenon (talk) 14:43, 27 February 2017 (UTC)
 * In all cases I'd tag it as promotional and leave a note on the talk page (if this hasn't been done already). I have seen an article created as a whole slew of pro and then a whole slew of anti and then merged into something approaching NPOV (all by one author over a good dozen edits) so it is possible. Thryduulf (talk) 12:35, 27 February 2017 (UTC)


 * Note, עוד מישהו, that unilateral draftification of some else's page has been repudiated, somewhere at WT:Drafts. It's a backdoor pseudodeletion, and once in draftspace the newcomer won't get any help. --SmokeyJoe (talk) 14:06, 27 February 2017 (UTC)
 * A borderline promotionally toned page is only irretrievably a G11 once it is revealed to be based on promotional sources. Once it is unambiguous there is no point delaying. If it is not unambiguous, it should not be speedied, but tagged per Thryduulf or AfD-ed. --SmokeyJoe (talk) 14:06, 27 February 2017 (UTC)

Semi-protected edit request on 28 February 2017
Two lines say "Not all numbers are used as some criteria have been repealed." Would you add a comma after "used" in both situations, to make it easier to read? 208.95.51.115 (talk) 16:04, 28 February 2017 (UTC)
 * A comma doesn't belong there, and it's easy enough to read.--Bbb23 (talk) 16:14, 28 February 2017 (UTC)
 * I disagree—I think a comma there to separate the clauses works well, and clarifies the sentence. I found myself reading it as "Not all numbers are used as some criteria" before getting tripped up by the second clause and having to go back to re-read the whole thing over. I have added the comma in each case. It certainly doesn't hurt the sentence. — Gorthian (talk) 21:56, 28 February 2017 (UTC)
 * I also agree, a comma improves the flow there.Tazerdadog (talk) 23:09, 28 February 2017 (UTC)
 * I too find the suggested comma improves the sentence. DuncanHill (talk) 23:13, 28 February 2017 (UTC)
 * Comma has been restored Noyster (talk),  08:06, 1 March 2017 (UTC)

Discussion about applicability of G6 to page move redirects
There is currently a discussion at WP:AN which concerns the application of G6 to redirects left behind by page moves. Editors watching this guideline page may be interested in the discussion. Thanks. Ivanvector (Talk/Edits) 14:33, 10 March 2017 (UTC)

A4 and A6
Why are there no criterions with the labels A4 and A6?? Georgia guy (talk) 01:29, 9 March 2017 (UTC)
 * They were superseded by other criteria, see Criteria for speedy deletion for details. -- Tavix ( talk ) 01:41, 9 March 2017 (UTC)
 * This kind of question is why I've supported having something in the repealed spots, e.g. "A4. Repealed; see below", but I've been reverted when I've tried to do that.  Nyttend (talk) 02:31, 12 March 2017 (UTC)

Foriegn Language Articles Not On Other Wikis
Does that fall under any CSD criteria? South Nashua (talk) 19:32, 12 March 2017 (UTC)
 * These fall under the longer process described at WP:PNT. AllyD (talk) 19:40, 12 March 2017 (UTC)
 * Thanks. South Nashua (talk) 20:41, 12 March 2017 (UTC)

G11 interpretation / clarification with regard to revisions
If an earlier revision of a given article exists which is not ‘exclusively promotional’ should the existence of such a revision protect the article from speedy deletion under G11? The recent speedy deletion of Givewell under G11 and subsequent deletion review discussion (Deletion review/Log/2017 March 9) show how this issue can arise. Years ago I saw a similar thing happened to the guitar maker article Travis Bean, where promotional content was added, then the article was G11’ed, and it is likely that other cases exist. G11 does include the wording ‘if a subject is notable and the content could plausibly be replaced with text that complies with neutral point of view, this is preferable to deletion’. An article can plausibly be replaced by an older version of the same article, but perhaps G11 should spell this out, or have stronger guidance than 'is preferable'.Dialectric (talk) 21:07, 14 March 2017 (UTC)
 * The lede of this policy clearly states that "A page is eligible for speedy deletion only if all of its revisions are also eligible.". It also makes sense that this should be the case.  No comment on the specific cases you have listed. Tazerdadog (talk) 22:14, 14 March 2017 (UTC)
 * Thank you for pointing that out. There is no need for the G11 wording to cover this case if it is already addressed generally, so this discussion can be closed.Dialectric (talk) 01:33, 15 March 2017 (UTC)

Speedy deletion per BLPDELETE needs documentation
It comes up from time to time, and it has come up again at Deletion_review/Log/2017_March_14. --SmokeyJoe (talk) 23:01, 15 March 2017 (UTC) I think all that is needed is to clarify that G4 includes "pages deleted pursuant to WP:BLPDELETE unless a consensus for recreation has been shown". I think it important to bear in mind that BLP is an area in which ArbCom has authorised the use of discretionary sanctions. I would expect that a user who repeatedly recreated content deleted per WP:BLPDELETE without consensus would be sanctioned. I don't agree that there is no place to discuss recreation. If anything, there are too many options - article talkpage, AfD, DRV etc - and it may make sense for one of these to be suggested in the policy. It should be a requirement that such a discussion should advertised at Biographies of living persons/Noticeboard. WJBscribe (talk) 11:50, 16 March 2017 (UTC)
 * There is consensus support for WP:BLPDELETE, which covers deletion of a BLP of a person who requested deletion of their biography due to privacy and accuracy concerns. It apparently authorises speedy deletion of re-creations, even where G4 and G10, or any other CSD, do not apply.
 * Some believe that WP:BLP overrides other documented policies? If so, document it.
 * I think the solution is to rewrite BLPDELETE, to the extent that it authorises speedy deletion, here at WP:CSD, in a more objective form.
 * Perhaps a small addition to G4, like "or an article on the subject was deleted per WP:BLPDELETE" (this needs to be improved, but the gist of the meaning may be clear, and no new criterion or too much creep is needed). Fram (talk) 07:22, 16 March 2017 (UTC)
 * This is an issue that needs much more debate and examination. The whole concept of not allowing re-creation of a deleted article is not a simple matter. I have considerable sympathy with the view that articles deleted at AfD should not be re-created soon after in an essentially identical form, especially when the subject is a BLP. We would normally delete such a re-creation uncontroversially and that is what G4 documents. However, at the other extreme, an inadequately sourced BLP, or a BLP of a not-yet-notable individual will be properly deleted, yet might profitably be re-created at a later time when better or newer sources become available. G4 also recognises that such a re-creation is not only common practice, but may often be of benefit to the encyclopedia. Unfortunately BLPDELETE makes no realistic attempt to cater for this scenario, because it demands prior consensus. That is almost always a mistake because it runs against the Wikipedia ethos of WP:BOLD. It also ignores the fact that until an article is re-created, there is really no place to discuss a consensus for its re-creation, which probably ought to take place on the associated talk page. Perhaps it is worth asking what he had in mind on that point when he added "it should not be re-created unless a consensus is demonstrated in support of re-creation" to BLPDELETE?
 * I disagree strongly that BLPDELETE overrides core policies such as WP:N and WP:NPOV: we should not let process prevent an article on a notable subject from being created, particularly as notability may be acquired with the passage of time. Making BLPDELETE a CSD criterion beyond what G4 already documents will effectively prevent the re-creation of any BLP that has previously been deleted via AfD. That is not a desirable result of changing CSD. One possible compromise is to have an agreed and documented procedure whereby any re-creation of a BLP deleted via AfD on the grounds of BLPDELETE would need to first take place in user: or draft: space and consensus developed on the talk page (or perhaps a central venue?), via RfC if necessary, before it was allowed to be moved into article space. This hopefully would imply that articles re-created without satisfying BLPDELETE should be userified as a matter of course, rather than speedy deleted. Of course, material that was libellous or a copyvio shouldn't enjoy such considerations, but neither should good-faith re-creations of notable, or even "borderline-notable" BLPs be automatically be consigned to the trash as if doing so is uncontroversial. It is not. --RexxS (talk) 10:06, 16 March 2017 (UTC)
 * I hope you don't really believe WP:N is "core policy". --SmokeyJoe (talk) 11:27, 16 March 2017 (UTC)
 * I hope you don't think that the policy which determines whether or not an article should exist on Wikipedia is anything other than core. --RexxS (talk) 13:42, 16 March 2017 (UTC)
 * His point was that N is a guideline, while BLPDELETE is part of BLP policy. Guidelines don't trump policy. Patar knight - chat/contributions 13:57, 16 March 2017 (UTC)
 * I know what his point was, but that's process wonkery. In reality, WP:N is not trumped any any other policy or guideline. You can't name a single article (out of the 5,359,538 on Wikipedia) that exists contrary to WP:N, so it's simply nonsense to say some other policy has precedence over it. --RexxS (talk) 14:04, 16 March 2017 (UTC)
 * Obviously all articles that exist meet (or should meet) N, but meeting N by itself is in come circumstances not a sufficient reason to keep. An article can be notable but still deleted if it's a borderline notable BLP whose subject has requested deletion (WP:BLPDELETE, WP:BLPDELETEREQUEST) or because it's an attack page, spam, or copyvio deletable under various CSD criteria. Patar knight - chat/contributions 14:45, 16 March 2017 (UTC)
 * Of course the fact that WP:N determines that an article could exist doesn't mean that it should exist, and WP:N says just that. I'll assume you're familiar with the wording. So deletion of an article is not a test of the practice documented at WP:N. Nevertheless you quibbled with my assertion that WP:N is a core policy and yet you've not shown a single case of another policy "trumping" what is documented at WP:N, have you? --RexxS (talk) 21:01, 16 March 2017 (UTC)
 * It's not just wonkery, it's not just the importance of getting terminology right so others can follow the conversation. WP:N is a simplistic guideline for establishing a rebuttable presumption. Topics can be deleted while meeting WP:N, and deleted despite passing WP:N. WP:N is blind to many things, including privacy, and biased coverage. --SmokeyJoe (talk) —Preceding undated comment added 21:11, 16 March 2017 (UTC)
 * It's complete wonkery and it's the sort of thinking that leads the ignorant into asserting that guidelines are optional at their whim, but policies must be followed. WP:N is actually a comprehensive guideline to determine whether an article could exist, but makes it clear that it doesn't guarantee that it must exist. If you read it, you'll see that it clearly states that it does "not limit the content of an article or list", but that the actual content is subject to the core content policies WP:V, WP:OR, WP:NPOV, etc. If you still think that the policy determining whether an article may exist is not core, then we have a different meaning of the word. --RexxS (talk) 21:33, 16 March 2017 (UTC)
 * I think I have read WP:N.  It is an unusual guideline in that it is enforceable by the policy, WP:DEL.  It is not, however, "comprehensive".  The Michael Cole case may be very borderline, and this point doesn't really apply to it, but many pretty bad articles, WP:COATRACKs for example, can be very strongly asserted as notable due to sources meeting the WP:GNG.  My point is that WP:Notability is often necessarily a strong argument to use against WP:BLPDELETE.  --SmokeyJoe (talk) 23:41, 16 March 2017 (UTC)
 * Once the article is deleted, the talk page goes as well, so the article talk page is not an available venue. AfDs are closed with the wording "No further edits should be made to this page." so AfD is not an available venue. I doubt whether anyone will take seriously a DRV if the AfD is years old, but it is a possibility, although I've never seen DRV used for anything other than undeletion of the deleted article, which is not what would be required. I simply can't agree with you that "there are too many options". --RexxS (talk) 13:42, 16 March 2017 (UTC)
 * But you could recreate the talkpage for purpose of the discussion, or start a new AfD surely? Those seem fairly minor issues with a discussion in one of those forums. I'm pretty sure I've seen such a discussion before, but I can't remember if the discussion took place at AfD or DRV... WJBscribe (talk) 13:50, 16 March 2017 (UTC)
 * Thinking about it, I'm pretty sure it was at DRV. One of the purposes of DRV is "Deletion Review may be used... if significant new information has come to light since a deletion that would justify recreating the deleted page". I think that would apply to the scenario we're discussing? WJBscribe (talk) 13:52, 16 March 2017 (UTC)
 * Any talk page re-created to discuss the issue would deleted as WP:G8 by the Vogons in the blink of an eye. "Examples of this criterion include talk pages with no corresponding subject page ..." I have no idea how anyone would start a new AfD for an article that is already deleted – has anyone ever seen that done? I know that one of the stated purposes of DRV is to justify re-creating the deleted page if fresh information came to light, but I'm thinking about the case where a completely new article is proposed (admittedly the title would be the same), not the undeletion of the previously deleted article. Nevertheless, perhaps folks would be willing to accept that as an outcome at DRV – it's just that I've never seen it used for that. --RexxS (talk) 14:15, 16 March 2017 (UTC)
 * If the issue isn't primarily over policy, but over the actual content, it may make more sense to take it to AfD. For example, I restored David Letele, which I had G4'ed, and sent it to AFD, not DRV, after someone challenged my close. This was because the issue was primarily one of whether newer achievements/sources were enough to meet our notability guidelines, which is a venue for AFD. Since BLPDELETES are more complex and policy-focused, I would prefer making a draft and submitting it to DRV, instead of creating a the page and then AFDing it. Patar knight - chat/contributions 14:45, 16 March 2017 (UTC)
 * I would always recommend going to AfD first, rather than DRV whenever fresh content is being considered for deletion, even when BLPDELETE is the primary focus. That way, it allows the possibility of appeal via DRV in case mistakes are made at AfD. That's part of our normal checks-and-balances and I can't see a good reason to bypass them because the issues are more complex. YMMV. --RexxS (talk) 21:06, 16 March 2017 (UTC)
 * This makes sense, but it (and BLPDELETE) should explicitly list a prefered venue. I would prefer it to be at DRV, which explicitly focuses on reviewing deletions with a heads up at BLPN, which should be fine though. Patar knight - chat/contributions 13:57, 16 March 2017 (UTC)


 * It should be a requirement that any proposal to reverse a WP:BLPDELETE deletion should advertised at Biographies of living persons/Noticeboard. --SmokeyJoe (talk) 12:14, 16 March 2017 (UTC)
 * I think that's a sensible venue, but how will folks judge whether or not it should be re-created if they can't see what is proposed? Surely there must be at least a draft available before anyone can assess it? --RexxS (talk) 13:42, 16 March 2017 (UTC)
 * Has anyone objected to the user proposing recreation presenting a draft? WJBscribe (talk) 13:50, 16 March 2017 (UTC)
 * It's common for temporary versions of articles to be restored for assessment at WP:DRV, or for the proposer to draft a new article with reliable sources they think justify recreation. This is more complicated because it's dealing with WP:BLPs who requested deletion, but that may be an option as long as there's nothing libellous/defamatory in the material. Patar knight - chat/contributions 13:57, 16 March 2017 (UTC)
 * Has anyone objected to the user proposing recreation presenting a draft? If you read the very DRV that sparked this thread, Deletion_review/Log/2017_March_14, you'll see that the argument to justify speedy deletion (G4) of Michael Cole (public relations) rests solely on the wording you inserted at BLPDELETE. Is there anything there to make you think exactly the same thing would not happen to Draft:Michael Cole (public relations), which would still be a re-creation prior to gaining consensus? --RexxS (talk) 14:31, 16 March 2017 (UTC)
 * I actually did not remember adding the wording to the policy - it was some years ago. Is there anything to make me think that a draft would not be deleted? Yes. It would be a draft, not an article, and have been created specifically for the purpose of seeing if a consensus exists for recreation. Crucially, it wouldn't be in the article namespace, which is public and indexed by google until after such a consensus had been established. WJBscribe (talk) 16:37, 16 March 2017 (UTC)
 * I'm very encouraged by that to think that a solution is possible which discourages multiple re-creations of non-notable topics, while allowing a later, fresh draft made in good faith to test whether a re-creation would be desirable. If you do write into policy that G4 is applicable to any article re-creation following a BLPDELETE, then I think you'd also have to explicitly write into the policy that drafts of re-creations are excluded until consensus is settled. --RexxS (talk) 21:01, 16 March 2017 (UTC)
 * Instead of discussion procedures that are adding complexity, perhaps the wording "Even if the page is not protected against re-creation, it should not be re-created unless a consensus is demonstrated in support of re-creation." should be changed to not prevent recreation. Instead it should permit creation again if the issue is addressed. Eg if the subject has become famous, or subject now wants the article to exist. If a discussion is needed then WP:DRV is the place for it. At WP:UNDELETE we may send requestors to DRV, especially if the create action is protected. The other simple option is to ask the deleting/protecting admin about re-creating, and provide a proposed draft. G4 should only be used to redelete a BLP page if its rules apply, ie it is substantually the same or does not address issues in the discussion. A draft should not normally be deleted as a G4 unless a MFD or AFD explicitly decided "no drafts" (or sandboxes).
 * Already the secion under discussion says the page should be improved or rectified as the first option. The problems mentioned are "unsourced negative material or is written non-neutrally". So recreation should only be permitted if all of these problems are fixed in line with the "improve" option first mentioned. Graeme Bartlett (talk) 23:18, 16 March 2017 (UTC)

Speedy Deletion Emblem on Template:Db-meta
At Template:Db-meta/sandbox, I added the speedy deletion emblem, which is used on other wikis hosted by Wikimedia. Should we add it to Template:Db-meta? Ups and Downs 1234 16:58, 20 March 2017 (UTC)
 * As far as I know we do not use this at all on this project, so we should either not add it to just this one or we should add it to all of the templates. Personally I'm not at all sure I see the point but I'm willing to be convinced if you can provide a reason why this would be beneficial. Beeblebrox (talk) 21:11, 20 March 2017 (UTC)
 * We don't but the OP is proposing that we should. I agree with you though that there seems no benefit. It looks nice but especially on mobile devices it looks weird and it might make it harder for users with disabilities who rely on screen readers to parse. Regards  So Why  08:07, 21 March 2017 (UTC)
 * "just this one" Beeblebrox, this is db-meta, the template around which other speedy-deletion templates are built. It's analogous to Infobox; we don't use it directly on pages, but it's the basis for other templates that get a lot of use.  Add a totally new component to this template, and it shows up on all the other templates.  Nyttend (talk) 11:20, 21 March 2017 (UTC)
 * I think that the template with the speedy deletion emblem looks better on desktop, but the concerns about the mobile view and screen readers need to be addressed before I can fully support it. That said, it looks more aesthetically pleasing is (or at least should be) a good enough reason to make the change iff the change doesn't break anything. Tazerdadog (talk) 08:44, 21 March 2017 (UTC)
 * As far as I can see it doesnt infringe any accessibility guidelines. Its one colour with a clear design - so even with the colourblind who have issues with Red will see it. I just checked on my mobile (Samsung Galaxy) and it displays okay (but thats subjective). RE Screen readers - someone should run it through a couple of the more popular ones to check. Only in death does duty end (talk) 11:58, 21 March 2017 (UTC)
 * I can reproduce SoWhy's funny image on my iPad. Tazerdadog (talk) 21:31, 21 March 2017 (UTC)
 * My laptop's able to view mobile pages. If I click the "looks weird" link, it doesn't look particularly weird; the icon and the "Contest this speedy deletion" box are on the same line, but the only significant difference in the whole thing (aside from the icon's appearance, of course) is that the rest of the content is shifted rightward by a bit.  Everything's still easily readable, and there's plenty of white space on both sides, just as should be expected.  In case you wonder, my screen's 13.6×7.6 inches.  Nyttend (talk) 22:24, 21 March 2017 (UTC)


 * Please be aware that had already requested this at Template talk:Db-meta. -- Red rose64 &#x1f339; (talk) 10:18, 24 March 2017 (UTC)

file. deletion
Why do you want to delete. My file? Leshanbrockjosephgage (talk) 07:21, 25 March 2017 (UTC)
 * This is the talk page for discussing improvements to the Criteria for speedy deletion page. You should return to the page which has the speedy deletion tag on it; once there, press the "Contest this speedy deletion" button, and make your comment. -- Red rose64 &#x1f339; (talk) 07:52, 25 March 2017 (UTC)

G6 should not be used to create permanent redlinks in namespace 1
There's a (meandering) discussion at WP:AN#Possible improper use of page move redirect suppression that has finally come up with a proposal for clarifying WP:G6, see WP:AN#Possible update to CSD:

Add Talk pages of main namespace pages should only be deleted as G6 if the talk page is being temporarily deleted to allow a move over it.

This is mainly to address the problem of redirect creation being improperly suppressed, as MediaWiki:Movepagetext refers to Page mover, which in turn refers to WP:G6. But G6 is also sometimes used directly to the same effect. This covers both scenarios.

Most of us feel that it should be unnecessary, as the creation of the resulting long-term redlinks in the article talk namespace is controversial, and so not covered by G6 in any case. But the one dissenting voice is an admin who claims to have created hundreds of these redlinks, and also claims that this is sanctioned by G6. And over the years I have come across many such redlinks created by other admins, but they have not objected to me fixing them, up until now.

So this needs to be clarified, and with regret at complicating the policy with another clause, I can't think of a better way to do it. We have a rough consensus at WP:AN (one dissenter as noted), but without much participation on the specific proposal, and of course the decision needs to be made here. Andrewa (talk) 05:03, 16 March 2017 (UTC)
 * Are there examples of problematic deletions? Jo-Jo Eumerus (talk, contributions) 16:09, 16 March 2017 (UTC)
 * Good question! Yes, see:
 * the talk:Kremlin log for the disputed one referred to above, discussed at User talk:Jenks24.
 * User talk:Tassedethe for discussion of the other recent example.
 * But it's not a new issue... I've seen many such over the years but not recently (please don't ask me to dredge back years!) and the admins concerned have always agreed that in hindsight they were controversial and so not G6. What brought it to a head was not just these two, but the statement I've made hundreds of these moves in five years as an admin and you are the only person who has complained.
 * The reason I did not cite the examples before is there seems some sensitivity on the part of the admins concerned... I'd prefer not to provide diffs for that claim, and it's not a behavioural issue, just a different good-faith interpretation of G6. And in my experience and apparently also of the admin cited in the first example, not a new or uncommon one. Andrewa (talk) 18:29, 16 March 2017 (UTC)


 * Thanks for the examples—I wasn't entirely sure what you were referring to. I don't do page moves nearly as often as I do, but I would fairly routinely make such deletions and consider them quite defensible. Surely we can all agree that pages and their talk pages shouldn't be out of sync. The way I see it, you can do three things with such redirects:
 * Delete them as housekeeping, assuming you have the privileges to do so
 * Edit them to point to the talk page of where the main page redirects to (i.e., Talk:Foo to Talk:Bar)
 * Replace with with talk page of redirect
 * I have seen such matters as housekeeping and have taken option 1, somewhat assuming that editors who do the others perhaps aren't capable of deleting them. "Kremlin" is one thing, but so many of these titles are not going to be places a user is ever going to try to directly access a talk page. So ultimately, I don't think it's a matter of great importance. I don't like to invoke WP:CREEP, but I think it might apply if you're suggesting we decide upon a mandated course of action for such redirects. --BDD (talk) 19:11, 16 March 2017 (UTC)
 * Agree that pages and their talk pages shouldn't be out of sync, with the proviso that the talk page of a redirect shouldn't necessarily itself be a simple hard redirect. If not, it should probably always contain a link (not technically a soft redirect but the same idea) to the talk page of the target, as a convenience (but it's not hard to navigate there even if it doesn't). Andrewa (talk) 21:26, 16 March 2017 (UTC)


 * I think if there's any likelihood the talk page might have meaningful incoming links (incl. external ones) then it shouldn't be deleted. I guess this is the case if it has some sort of content. Conversely, most of the time a talk page would only contain a project tag or two, and redirects to these had better be deleted. When landing on a redirect in the course of maintenance work, it's really helpful to see whether there are any discussions on its talk page – if the "Talk page" link is red, then there aren't. This convenience is taken away if such talk pages get kept. – Uanfala (talk) 19:27, 16 March 2017 (UTC)

Interesting... comparing the discussion above to that at WP:AN, I'd like to make two observations: Am I missing something? Andrewa (talk) 20:33, 16 March 2017 (UTC)
 * These deletions are common, as claimed.
 * These deletions are in principle controversial.


 * I don't understand what is controversial. I couldn't make heads or tails of the discussion at WP:AN, so I didn't comment there. Talk pages with substantive discussions should not be deleted. They may need to be archived or merged. Talk pages of redirects are mostly useless in my experience, although where an article was moved and the talk page has a long history with numerous incoming links, there is value indicating the current location of the redirect's talk page as an artifact of the page move. older ≠ wiser 01:06, 17 March 2017 (UTC)


 * I don't understand what is controversial either. But it is. Some of us see a redlink as valuable and useful, and apart from their having become accustomed to working in this way I cannot see why, there are far better ways of working that do not rely on this unreliable signal. Others dislike having our links (which include watchlists, contributions pages, edit summaries, and off-wiki links, typically from alderspace and its companion wikis in my case) broken for no apparent benefit.


 * I appreciate that you and others do not value and use these links. But some of us do, so much that we even have trouble understanding why others do not miss them.


 * Would you not call that controversial? Andrewa (talk) 06:23, 17 March 2017 (UTC)
 * I'm not sure I understand the "broken links" issues. We're talking about talk page redirects that get left behind from page moves, right? In that case, both watchlists and contributions pages follow the new title. If the redirect is suppressed then the only broken link I can think of would appear in the move log entry, but then it will be immediately followed by a link to the new title, so I don't see the problem here. Of course, that's leaving aside the obvious case where the talk page has meaningful incoming links from the talk/project namespace, in which case of course there are links that get broken. –  Uanfala (talk) 12:25, 17 March 2017 (UTC)
 * Quite correct. It creates a mess, with some links maintained and others broken. Sorry I didn't make that clear. See the talk:Kremlin case above for an example of a redlink making it difficult and time-consuming to find the discussion. Andrewa (talk) 14:53, 17 March 2017 (UTC)
 * , I think it is unreasonable to attempt to maintain the integrity of links from outside Wikipedia to pages within Wikipedia. Simply keeping internal affairs in order is a monumental task without burdening it with responsibility for backward compatibility of links that editors have no visibility to or any control over. For articles that have long history at a particular title that have moved, I can understand we might want to ensure there is some sort of breadcrumb trail, but for talk pages where the only content was project tags, I can't see any possibility of controversy. older ≠ wiser 12:58, 17 March 2017 (UTC)
 * It's not a possibility of controversy, it's an actual controversy. In both of the cases I mentioned above, there's a rough consensus at WP:AN that the redlink was a bad idea. But some see it as justified by WP:G6. Is that controversial, or not?
 * The principle that it is unreasonable to attempt to maintain the integrity of links from outside Wikipedia to pages within Wikipedia needs scoping down a little IMO. Historically we have considered this, although not at the highest level of priority. See Redirect: 4. You risk breaking incoming or internal links by deleting the redirect. For example, redirects resulting from page moves should not normally be deleted without good reason. Andrewa (talk) 14:53, 17 March 2017 (UTC)
 * Rough consensus, hmmm, I see a couple of folks agreeing in what is an otherwise hard to follow discussion. TBH, I do not think either deletion at the time was in any way controversial. You as an editor who finds them useful in some way are of course free to recreate them or to request undeletion, but I don't agree any general prohibition is desirable. older ≠ wiser 17:09, 17 March 2017 (UTC)
 * Yes, by "controversial" do we mean that everyone isn't 100% in agreement or that this could cause real friction? Going back to my three options above, I wouldn't even blink if a page like that got recreated pointing to the right place or with the right template. Wikipedians can certainly war over rather trivial matters, but I'm disinclined to try to solve this one unless the problems become more serious. --BDD (talk) 18:36, 17 March 2017 (UTC)
 * No, of course we don't mean everyone isn't 100% in agreement. But nor do we mean this could cause real friction. What I mean is simply that some good-faith editors disagree with it. One would be enough in many cases. This disagreement is commonly (and thankfully) quite without friction. What do you mean by controversial? Andrewa (talk) 22:05, 17 March 2017 (UTC)
 * Exactly, a couple of folks agreeing, me plus several others, and one dissenter as noted above. Would you not call that a rough consensus? I know the discussion is hard to follow!
 * I'm not looking for a new or general prohibition. I'm looking for a clarification of what the policy already says, but is very widely misunderstood. I think the discussion just above as to exactly what is meant by controversial may be the key to this.
 * Agree that neither deletion at the time was in any way controversial, in that the admins followed a widespread interpretation of G6, and a practice that they'd seen many others do and had often done themselves. But that very popular misinterpretation does not stand up to careful scrutiny. Andrewa (talk) 22:05, 17 March 2017 (UTC)

Taking another tack, we might also consider either following or changing the advice at Redirect: ''5. Someone finds them useful. Hint: If someone says they find a redirect useful, they probably do. You might not find it useful—this is not because the other person is being untruthful, but because you browse Wikipedia in different ways.'' Andrewa (talk) 14:53, 17 March 2017 (UTC)
 * And another similar hint: If a good-faith editor says that something is controversial, it probably is. Andrewa (talk) 22:05, 17 March 2017 (UTC)
 * I'm afraid I still don't really understand the rationale for prohibition -- and yes, it does appear you are seeking a new prohibition under the guise of clarification. As far as I can make out in the convoluted discussions, the rationale looks more like a variation of WP:ILIKEIT than anything based in policy or general utility. There is so much dreck and detritus accumulated over the past decade and a half of Wikipedia editing, I generally applaud any editors that bother to try making the space a bit less cluttered with debris. Talk pages of redirects where the only edits were to add project tags are totally worthless. older ≠ wiser 22:26, 17 March 2017 (UTC)
 * They're not just worthless – they add unreasonably to the workload when these redirects are retargeted. Of course, the extra work they create should be weighed against any potential benefit they might have, but such benefits have not been shown in the discussion so far. – Uanfala (talk) 09:06, 18 March 2017 (UTC)

To me this discussion shows very clearly that these talk pages do not qualify for G6 speedy deletion. G6 is explicitly only for "uncontroversial maintenance". "uncontroversial" links to Consensus. There is no consensus in this discussion that they should be routinely deleted and there is certainly no consensus to this effect in the linked discussion at AN. If there is no consensus that the page should be deleted, then the deletion cannot possibly be "uncontroversial". Thryduulf (talk) 10:33, 19 March 2017 (UTC)
 * Well, what I see in the discussion so far is that the current practice is to delete such redirects, that there are good reasons for doing so (e.g. reducing the workload when the corresponding article redirect gets retargeted). On the other hand, the rationales that I recall were given for keeping them were two. The first is that the redirect could be expanded with project tags to aid article alerts: except in the extremely unlikely case where a redirect would have project tags that are not found on its target, this is redudant as the article alerts already use the project tags on the target article. The second reason for keeping them is to ensure the integrity of watchlits and lists of contributions, but these follow the article that has been moved, so preserving a talk page redirect at the old title isn't necessary. Correct if I'm wrong or if I'm missing anything, but neither of these rationales for keeping stand up to scrutinty. I'd be happy to accept keeping talk page redirect remnants, but only if there is a reason for that. – Uanfala (talk) 11:00, 19 March 2017 (UTC)
 * Just because you disagree with the reasons to keep these redirects does not mean there is a consensus to delete them. Yes a few people have been routinely deleting them under the impression there was consensus, but now it has been discussed it is clear that that impression is incorrect. Previous deletions were in good faith, but that does not apply going forwards. In my view, explicit project tags are always better than inferred ones as they allow people view the redirect to see who to notify when they want to discuss the redirect, it allows users who cannot create pages to discuss the redirect, allows everyone to view the page history without needing to access, read and understand logs and it allows the possibility of redirects to have project banners that differ from those at the target (whether that is broader or narrower). Thryduulf (talk) 21:11, 19 March 2017 (UTC)
 * Thank you for the reply, . Explicit project tags [..] allow people view the redirect to see who to notify when they want to discuss the redirect: fair enough, but anyone with enough knowledge of wikipedia to be able to get to the talk page of a redirect would also know how to view the much more easily accessible talk page of the target. it allows users who cannot create pages to discuss the redirect – from what I see at WP:HTCAP anyone who can edit a talk page can also create one. Allows everyone to view the page history without needing to access, read and understand logs – erm, after a move, the page history doesn't stay at the old title. Allows the possibility of redirects to have project banners that differ from those at the target – no-one objects to such talk pages being created and kept in these rare circumstances, but just because some redirects talk pages make sense doesn't mean that all redirect talk pages do. – Uanfala (talk) 22:00, 19 March 2017 (UTC)
 * Several of those comments assume that everybody browses Wikipedia in the same way that you do, which is not true. For example after navigating to a redirect page, the talk page of that redirect is far more accesible than is the talk page of the target. Also, from the top of this page, It must be the case that almost all pages that could be deleted using the rule, should be deleted, according to consensus. (emphasis in original). There is clearly no consensus that almost all of these pages should be deleted, therefore routine speedy deletion is inappropriate and speedy deletion under criterion G6 doubly so. Thryduulf (talk) 23:30, 19 March 2017 (UTC)


 * This proposal is far broader than the problem it purports to address. There are situations where you might want to use G6 on a talk page that don't involve moving another page to that title or suppressing a redirect following a page move. This proposal would ban them for no particular reason.  Hut 8.5  11:04, 19 March 2017 (UTC)
 * Please give some examples so that we can see whether there is consensus for such deletions, and if there is reword this proposal so it does not encompass them. A vague wave is unhelpful. Thryduulf (talk) 21:11, 19 March 2017 (UTC)
 * I think you've got that backwards - it is the responsibility of people proposing policy changes to show that they are necessary. I think it should be fairly obvious that "uncontroversial maintenance" extends beyond page moves with regards to the talk namespace and that "Deleting pages unambiguously created in error or in the incorrect namespace" (one of the suggested use cases) applies to the talk namespace as any other. If you want to prevent people from using G6 in some situation then write a proposal forbidding use of G6 in that situation, rather than writing one which bans use of G6 in all other situations and adding as many exceptions as you can think of.  Hut 8.5  07:50, 20 March 2017 (UTC)
 * , I agree with respect to the onus of proof, but it would still strengthen and clarify your argument if you could also give an example or two. The goal here is consensus, and that is aided when we understand exactly what your point is. And it seems a bit vague to me without any examples. Andrewa (talk) 17:25, 20 March 2017 (UTC)
 * Here are some specific examples of recent deletions of pages in the article talk namespace which I think your proposal would forbid:
 * Talk:Drega
 * Talk:Lal Sena/GA1
 * Talk:Salomão (surname)
 * Talk:Elektronika MK-52
 * Talk:The Code (film)
 * Talk:Ill Slim Collin
 * Talk:Credibility gap
 * Not really covered in that list is the situation I described above in which a page is obviously created in the wrong namespace, which happens to be the talk namespace. Incidentally while compiling the above list I found an awful lot of examples of people deleting talk page redirects created by page moves using G6, which suggests to me that this proposal may not be a good idea (policy is meant to reflect practice).  Hut 8.5  21:56, 20 March 2017 (UTC)
 * Awesome, thank you! And to clarify, are these all pages that you think are better as redlinks? I note for example that Talk:Lal Sena/GA1 now has 37 broken incoming links (here are 17 of them). Or maybe it's better to discuss all these in below. Very relevant either way, so again thank you. Andrewa (talk) 23:31, 20 March 2017 (UTC)
 * That GA review page should definitely have been deleted. The incoming links are places that mention it as an article which has been nominated for GA but where the review hasn't started yet. The page was deleted because someone had created it with content that wasn't a GA review, so the blue link status falsely indicated that the review was in progress. The page is better as a redlink until someone actually starts the review properly, even with the incoming links.  Hut 8.5  07:42, 21 March 2017 (UTC)
 * Thank you, agree that this was uncontroversial, and therefore a valid G6. My proposal was not intended to cover such pages, and I'm not sure it does. Andrewa (talk) 14:19, 21 March 2017 (UTC)
 * Your proposal was Talk pages of main namespace pages should only be deleted as G6 if the talk page is being temporarily deleted to allow a move over it. This is a page in the article talk namespace which was deleted as G6 for a reason other than a temporary deletion to allow a move. I suppose you could quibble over whether your proposal applies to talk subpages as well as talk pages but that doesn't apply to the other pages I mentioned (or many others I could have cited). I'm sure that you didn't intent to prohibit the deletion of these pages, but nevertheless that's what your proposal does. It will need to be redrafted. I'd suggest just saying "G6 cannot be used on talk pages in situation X" rather than "G6 can only be used on talk pages in situation Y".  Hut 8.5  18:47, 21 March 2017 (UTC)
 * Good point... How about Deletion (or suppression) of talk pages of main namespace redirects is controversial, and not covered by G6 - if a hard redirect is inappropriate, it may be replaced by pointers to the relevant talk pages.? Andrewa (talk) 23:05, 22 March 2017 (UTC)


 * Comment - redirects are deleted by admins who favor red-links over blue-links. In my opinion, these unsupported speedy deletions should be made to cease at the earliest convenience. Not only is it a clear point of contention between differing schools of thought, due notifications are bypassed as well when deletions are simply accomplished without ever tagging the page with any CSD rationale.


 * Trolls and vandals are afforded the opportunity of notification when pages they create are tagged for CSD deletion but notifications for creations by good faith editors are often circumvented by the overreaching actions of good faith admins who wrongfully believe their actions are in accordance with policy although they, at times, are not.


 * Consider the following which are merely samples from my own creations where speedy deletions were accomplished without the courtesy of a notification or invitation to correct discrepancies if such corrections were otherwise possible:
 * Priddis Records
 * High Vaultage Records
 * Tumbleweed Records
 * Robyn Michele Levy
 * Thank you.--John Cline (talk) 11:17, 19 March 2017 (UTC)
 * This proposal only addresses the suppression of talk page redirects and does not directly address any actions in other namespaces. older ≠ wiser 12:08, 19 March 2017 (UTC)


 * If you read G6, it provides examples of uncontroversial maintenance. No where does it mention any specific examples of things that G6 isn't for. Nor should it. If something is controversial, G6 shouldn't be used, it's as easy as that. Therefore, I oppose any such additions of negative language into G6, and WP:CREEP is relevant here. -- Tavix ( talk ) 18:26, 20 March 2017 (UTC)
 * Strongly agree that If something is controversial, G6 shouldn't be used, it's as easy as that. Exactly. But doesn't that mean that, in hindsight at least, G6 does not cover the deletions I gave as examples (and many more)? That's all I want to address. Clarifying G6 was the best idea we could come up with at WP:AN. Other ideas welcome. Andrewa (talk) 22:43, 20 March 2017 (UTC)
 * Simple: if a G6 action is objected to, it should be restored. Nothing needs to be clarified -- Tavix  ( talk ) 22:46, 20 March 2017 (UTC)
 * Isn't that a simple recipe for chaos? In that almost anything a user or admin can do can be reversed, we could similarly just delete all policies and guidelines. The ultimate solution to instruction creep! Andrewa (talk) 23:10, 20 March 2017 (UTC)
 * I do not care to indulge in fallacies and hypotheticals. -- Tavix ( talk ) 23:18, 20 March 2017 (UTC)
 * I wasn't serious. But it seemed the best way to express the logical absurdity of your post. To put it positively, you've avoided the question. If there are actions that are regularly occurring, contrary to guidelines, and contrary to the best reader experience, then we should look at clarifying the guidelines. To plead instruction creep in such a case on the grounds that such actions are easily reversed is... I'm afraid I'm stuck for the right word here. Andrewa (talk) 01:07, 21 March 2017 (UTC)

Another tack
We seem to be meandering a bit above.

Both the examples given above, Talk:Kremlin and Talk:David Williams (footballer), have been recreated, and there seems no move to delete them. I think the results are already better than a redlink. But some editors above have expressed the opinion above that redlinks are preferable.

I'd like to seek a consensus that, in these specific cases, the redlinks are not a good idea, but rather that there's something useful that should be there (whether that's what we have or something better I don't care).

If we can't get consensus on that, then I will withdraw my suggestion, and we can close this.

But if we can get consensus on that (as I hope) then that doesn't automatically mean we need to update anything. We can't cover every possibility (and if we could we'd just automate it and leave it to the bots). It's just a first step towards seeing whether we can improve G6, either by my suggestion or some other. Andrewa (talk) 18:20, 20 March 2017 (UTC)
 * I've had a look at Talk:Kremlin: it was deleted after Kremlin was moved to Kremlin (fortification) and then the old title was redirected to Moscow Kremlin. As the talk page has incoming links, it falls outside the scope of what I was talking about above. I don't know what is the optimal solution in this case. Retargeting to sync with the Kremlin would be inappropriate as the incoming links are all intended for Kremlin (fortification). Creating with just project tags would be utterly confusing. Deleting was probably the easiest sensible course of action because a pointer is left in the deletion log entry (seen by anyone clicking on the link) to the new target. The only circumstances where this could get problematic is if in future the talk page is created for some other reason and this pointer is lost. In light of this it does seem like Andrewa's action of creating the talk page with a plain sentence indicating the new target seems best, as that will stay on the talk page regardless of any future content. However, I'm not sure if it will be doable to ask people to follow this example. – Uanfala (talk) 18:52, 20 March 2017 (UTC)


 * There's no question that deleting the talk page is easiest, but I have two issues with it. Firstly and most important, it's not best. Secondly, I don't think it's a valid use of G6 even as it stands. In hindsight, the deletion of Talk:Kremlin was neither the best action nor uncontroversial. But the reason I did not cite that example until asked for it was exactly that this is hindsight. It was not the fault of the admin concerned, who quite correctly protested that such deletions are standard practice.


 * As to whether it's doable, why not? We admins do have some level of commonsense too. Andrewa (talk) 22:55, 20 March 2017 (UTC)

So far the only answer to the question I asked in this section has been that, in the case of Talk:Kremlin, a redlink was not the best outcome. , I hope that is not misquoting you?

Any other opinions on either of the two examples?

If not, we most certainly should have a look at the other examples very helpfully supplied by above. But I'd prefer we had agreement on those two first. Andrewa (talk) 23:26, 20 March 2017 (UTC)
 * In the case of Kremlin, deletion, even if not ultimately the best option, was a very good option nevertheless. If G6 had been modified to explicitly exclude cases like this, then instead of deleting the page, the admin would have most likely kept is a redirect synced with the article – and that, as we saw, is a bad idea. I echo Andrewa's invocation of the need of common sense, but I think their proposal, even if refined, is more likely to put obstacles in the exercise of this common sense than to guide users towards it. If any change is necessary, then instead of a policy prohibition, I think it should rather be an addition to the documentation (in the instructions for moving articles?) so that editors are aware of the issues involved in cases like Kremlin. – Uanfala (talk) 19:27, 21 March 2017 (UTC)


 * The mind boggles as to how something that was not ultimately the best option can still be a very good option. Let's see, we didn't want it deleted, but it was good to delete it? Huh? Sounds like something out of Nineteen Eighty-Four to me.
 * I think that what you're getting at is that the admin made a reasonable decision in the circumstances. Exactly. And I'm seeking to change those circumstances so that admins can get it right first time around.
 * But changing the instructions for moving articles would do that, yes. Misapplication of G6 is the common problem, whether the redirect is suppressed or later deleted, but if we could get admins to fix the talk page redirect rather than suppressing it or leaving it pointing to the wrong place, then problem solved. Andrewa (talk) 10:41, 22 March 2017 (UTC)

Second attempt
Deletion (or suppression) of talk pages of main namespace redirects is controversial if the intent is to leave a long-term redlink, and so not covered by G6. If the talk page redirect created by a page move is inappropriate, it may be replaced by pointers to the relevant talk pages, rather than suppressing its creation.''

This is in response to an example given above, of a talk page subpage which looked like a GA nomination but wasn't. The redlinks this created were entirely appropriate.

Better? I'm afraid it's longer, but can't see any way to shorten it. I think it's accurate! Andrewa (talk) 02:42, 23 March 2017 (UTC) Andrewa (talk) 03:03, 23 March 2017 (UTC)
 * I'm still highly skeptical this is needed at all, no matter how you word it. -- Tavix ( talk ) 02:45, 23 March 2017 (UTC)
 * Noted. But do you see the point that both the examples originally given (and many more like them it is I think generally agreed), while they were deleted in good faith and trying to follow the guidelines, were actually both controversial and better kept (and now have been)? Andrewa (talk) 02:52, 23 March 2017 (UTC)
 * That's frankly irrelevant. G6 doesn't need an exhaustive listing of everything that may be considered controversial. Let's not start now. -- Tavix ( talk ) 02:55, 23 March 2017 (UTC)
 * Why is it irrelevant? Agree G6 doesn't need an exhaustive listing of everything that may be considered controversial. But in this case, the very issue of whether it's controversial is itself controversial. So guidance is needed. Andrewa (talk) 03:00, 23 March 2017 (UTC)
 * And I rather strongly disagree. You're making a mountain out of a molehill, the situation is not a big enough deal to start inserting prohibitions into G6. -- Tavix ( talk ) 03:07, 23 March 2017 (UTC)
 * Noted. So it not being a mountain is the reason that the examples are irrelevant, is that your thinking?
 * I'd still be interested in knowing whether you think the examples are controversial. If they are (as I believe), then the existing guideline is widely misinterpreted. That seems a big enough deal to me. But I respect there are other views. Andrewa (talk) 03:30, 23 March 2017 (UTC)
 * I've added the word so for clarity. Andrewa (talk) 03:03, 23 March 2017 (UTC)
 * Perhaps we could just insert something into the criterion along the lines of "Consensus has been reached that G6 should not be used in certain cases - a list of these consensuses can be found here Tazerdadog (talk) 04:22, 23 March 2017 (UTC)
 * That would be perfect. My only agenda is to achieve a reasonable consistency in the way admins interpret G6 with respect to redirect suppression when mainspace pages are moved. There is patently no such consistency at present.
 * The only problem I see is, how do we assess this consensus? I fear that we may get too many no consensus outcomes to make it work, and even no consensus as to whether no consensus means keep or delete. But definitely worth a try. Andrewa (talk) 05:34, 23 March 2017 (UTC)
 * I do not see this as the "perfect" solution for what is otherwise an imperfect assertion, attesting, (imperfectly), that the controversial use of redirect suppression should be corrected by the focused preemption of talk page deletions within CSD G6.


 * If the problem arises from the occasional misuse of redirect suppression, it should be mitigated where redirect suppression is most fully expounded, not within criteria that properly invites its occasional use as a tool. It is instruction creep to disproportionately insert such preemption here, where nothing written gives the slightest hint of rise to any of its improper use.--John Cline (talk) 13:32, 23 March 2017 (UTC)


 * Agree that a change to wp:page mover could be used instead of a change to G6. But a change to G6 seems neater, as there's no problem with that guideline as it stands. The only problem is misinterpretation of G6, in that it is being applied to controversial deletions.
 * an imperfect assertion, attesting, (imperfectly), that the controversial use of redirect suppression should be corrected by the focused preemption of talk page deletions within CSD G6... I'm not completely sure what this means, but I get the impression that you oppose any change to G6 for any reason. Noted! And you're not the only one I also note.
 * nothing written gives the slightest hint of rise to any of its improper use... Agree. It's a long-standing problem. But it's certainly not occasional misuse of redirect suppression (my emphasis). It's quite common, as seems generally agreed, and otherwise I would just continue to fix the ones I find and leave the others for others to fix. It's common enough to be worth addressing. Andrewa (talk) 23:25, 23 March 2017 (UTC)
 * I agree with you that CSD G6 is susceptible to misinterpretation, and misapplication there born, ( I have said as much ). This susceptibility, however, is not the result of poorly written criterion, and attempts at mitigation by writing more or changing that which is not defective are already known, in such cases, to be folly.


 * I, most certainly, am not predisposed to resist change, (here or elsewhere), and did not mean to imply that I was. I simply lament seeing your good intentions and selfless effort squandered by misplacing them here where nothing can reasonably be gained. Nevertheless, I wish you the best and hope that you ultimately prevail, in the right place and time, as your complaints are not without merit.--John Cline (talk) 11:52, 25 March 2017 (UTC)

A question
I admit I'm puzzled that there is not more support for this. Let me ask all (both for and against any change) to look at this recent RM, which reads in part The article <> should be the redirect page, or deleted (my emphasis).

This is not a talk page, so it's broadening the issue. It's just an example that came to my notice just now (for obvious reasons).

Now in closing that I would have liked to point out that there's no justification for deleting the redirect (or so I believe). This should be clear from policy and guidelines (I believe). But is it? Where? Andrewa (talk) 03:19, 26 March 2017 (UTC)
 * Redirect items 1-5. Siuenti (talk) 06:54, 26 March 2017 (UTC)

Does G4 apply to categories too?
Basically this category was re-created earlier today, despite being deleted at CfD a few days ago. Thanks.  Lugnuts  Precious bodily fluids 09:19, 26 March 2017 (UTC)
 * Can't think of a reason it wouldn't. I am guessing the question is whether to first delete or first empty. Jo-Jo Eumerus (talk, contributions) 09:42, 26 March 2017 (UTC)
 * Thanks. I've emptied it and will tag it now for deletion.  Lugnuts  Precious bodily fluids 10:24, 26 March 2017 (UTC)
 * Generally speaking, the G criteria apply to all namespaces, unless specifically excluded (such as G1 and G2 for user space). -- Red rose64 &#x1f339; (talk) 16:50, 26 March 2017 (UTC)

Draft classifier template and extending G13 to non-AfC drafts
A proposal that would create a new draft classifier template and extend G13 to non-articles for creation drafts is taking place at Wikipedia talk:Drafts. Interested editors are welcome. Thanks, — Godsy (TALK CONT ) 08:11, 27 March 2017 (UTC)

Create a template for pointing out additional necessary information preserved in the page history
In regards to this comment, I propose that there be a template telling the deleting administrator of a CSD'ed page that there is some information left over from changing the "unspecified" template to a criteria template that might need to be checked before deletion. ToThAc (talk) 22:38, 29 March 2017 (UTC)
 * Can you clarify what you mean by that? Just reading your post above I really couldn't understand it at all. Looking at the talk page section you linked to, and then following that up by checking the history of your deleted edits, I got the impression that you mean that a template should warn administrators that someone such as you may have removed relevant content that another editor has put in a speedy deletion tag. If that is not what you mean then you really do need to explain more clearly, as that is the only interpretation I can think of. If, on the other hand, that is what you mean, then I disagree, for two reasons. (1) Administrators are already warned to do several things when they are about to delete a page, including checking the editing history of an article. Specifying each individual thing they could check for in the editing history is not only unnecessary, but also likely to be counter productive, because the longer and more complex instructions become the more likely it is that essential points will be missed. (2) Editors who persistently remove such content without good reason, even after being warned, should just be blocked, exactly like editors who persist in any other kind of disruptive editing. Letting them carry on doing it and posting messages letting people know that they may have done it is not the best way to deal with the problem. The editor who uses the pseudonym "JamesBWatson" (talk) 14:35, 30 March 2017 (UTC)
 * I can't really make sense of it either, but it looks like you are asking us to change something because a user asked you to stop doing something unhelpful. Beeblebrox (talk) 20:47, 30 March 2017 (UTC)

G6 and redirects ending in "(disambiguation)"
Presently one of the bullets at G6 states Deleting a disambiguation page that links to zero articles or to only one extant article and whose title includes "(disambiguation)"

Per WP:AN, Redirects for discussion/Log/2017 March 9 and Redirects for discussion/Log/2017 March 10 it is not uncontroversial that these should be speedily deleted when (a) they are the result of a page move, and/or (b) they point to a set index article.

To reflect this I propose that those cases be explicitly excluded from the G6 criteria by changing it to the following:
 * Deleting a disambiguation page that links to zero articles or to only one extant article and whose title includes "(disambiguation)". This does not apply if the sole link is to a set index article, the page is a redirect to a set index article and/or the page is a redirect resulting from a page move.}}

I am involved with the RfD discussions, but I think even an uninvolved editor would agree that these situations no longer meet point 2 of the requirements for CSD criteria ("It must be the case that almost all pages that could be deleted using the rule, should be deleted, according to consensus." [emphasis in original]). Thryduulf (talk) 13:53, 11 March 2017 (UTC)
 * I don't agree. I'd prefer to see the criteria updated to explicitly clarify that such redirects CAN be speedily deleted. There may be rare cases where an edit history can't be merged, but those should be exceptional, and likely should be moved to a sub page or to some other title. Prior to WP:INTDAB, such redirects would have had no reason for existing. Unless there is consensus that there is no meaningful difference between disambiguation pages and set indices or other list articles, keeping such redirects only compounds the confusion. older ≠ wiser 14:12, 11 March 2017 (UTC)
 * Those are arguments for RfD. I disagree with them but that's why this is not suitable for speedy deletion as "all pages that could be deleted using the rule, should be deleted" clearly does not uncontroversially apply here. Thryduulf (talk) 20:22, 11 March 2017 (UTC)
 * The cases where deletion of these are legitimately (IMO) debatable are few and far between. WP:INTDAB is why such redirects exist. That some advanced users have glommed on to this for other purposes is not a good reason for keeping such redirects. Keeping them only serves to further confuse the already murky distinctions between disambiguation pages and non-disambiguation pages. If everything and anything may be considered to function like a disambiguation page, then let's just get rid of WP:DAB and WP:MOSDAB altogether and start over with a different conceptual basis, whatever that might be. older ≠ wiser 20:32, 11 March 2017 (UTC)
 * Again, I (and others in the other venues) disagree with you which is why speedy deletion is not appropriate - there is not consensus for their being deleted in every case they could be. Thryduulf (talk) 21:53, 11 March 2017 (UTC)
 * I disagree as well, primarily per WP:CREEP. G6 is for uncontroverisal maintainence. If a speedy deletion is causing controversy, it's a red flag that it shouldn't be deleted via that criterion. I feel those redirects should be deleted per WP:SIANOTDAB. If it needs to be at RfD until the controversy subsides, so be it. -- Tavix ( talk ) 15:22, 11 March 2017 (UTC)
 * Exactly my point. They're controversial so the CSD criteria should make is clear that they are excluded - this is about tightening the criteria not broadening it. Thryduulf (talk) 20:20, 11 March 2017 (UTC)
 * No it shouldn't, and I pretty strongly disagree that it's "tightening" anything. There's tons of things that G6 doesn't include, but note that none of them are explicitly included in that section. Start listing things the criterion doesn't include, and more will WP:CREEP in. If someone objects to a G6 deletion, it should be reversed and discussed at the proper forum. -- Tavix ( talk ) 20:25, 11 March 2017 (UTC)
 * The problem with that is that they currently are mentioned as the second bullet point example of things that are covered. I would support removing the mention completely if you want to propose that, but I don't think that is necessary. Thryduulf (talk) 21:53, 11 March 2017 (UTC)
 * No it's not. You're confusing disambiguation pages and redirects (see Uanfala's comment). -- Tavix ( talk ) 22:41, 11 March 2017 (UTC)
 * I'm not sure the current wording applies to redirects. After all, if it's a a disambiguation page that links to zero articles then it's, well, a page that links, rather than redirects, to an article. – Uanfala (talk) 16:15, 11 March 2017 (UTC)
 * I've not seen that interpretation before, but I can't say that I'm opposed to it. Thryduulf (talk) 20:20, 11 March 2017 (UTC)
 * There are two kinds of pages with " (disambiguation)" in their titles: redirects and dab pages. That bullet point at WP:G6 says nothing about redirects, so applies only to actual dab pages. — Gorthian (talk) 02:17, 12 March 2017 (UTC)
 * Um, by definition a redirect is not a disambiguation page. When we're talking about a type of page, the title is irrelevant (as long as we exclude namespace prefices), and when a speedy deletion criterion says that it applies to one sort of page, you mustn't speedy other types of pages under that criterion unless it's really an IAR situation.  Uanfala's point should have been needless to say.  Nyttend (talk) 03:58, 12 March 2017 (UTC)
 * , I was basically agreeing with Uanfala, and just trying to clarify the point. (Perhaps I have muddied it instead?) I have always assumed that Db-disambig did not apply to redirects. — Gorthian (talk) 05:25, 12 March 2017 (UTC)
 * No, sorry; I guess I did the indents wrongly. I was responding to the idea at the top, not to you, since I could see that you understood it.  Nyttend (talk) 11:59, 12 March 2017 (UTC)

OK it seems the consensus is that the bullet about "(disambiguation)" pages does not apply to redirects, but the AN discussion and linked RfD discussions make it clear that I'm not the only one who thought differently. Would anyone object therefore to a clarification note that "This does not apply to redirects"? Thryduulf (talk) 12:47, 12 March 2017 (UTC)
 * Yes, I object. It's clear from the above discussion that this would be unnecessary. -- Tavix ( talk ) 14:29, 12 March 2017 (UTC)


 * I disagree. I would prefer to clarify that these redirects are covered by either G6, or G8 (as a dependent). This would update the criteria to bring in line with WP:SIANOTDAB, and current wording in G6 about not creating them. Proposal as worded conflates redirects and dab pages. but as I'm the original editor who G6&G8ed them:
 * 1) dab pages: G6 Db-disambig: The two RfDs link to a declined G6&G8 that was not a G6 Db-disambig of dab pages. Nobody is claiming it applies. There's nothing to be fixed. However, G6 does state "If it links to only one article and does not end in (disambiguation), simply change it to a redirect." It explicitly excludes creating redirects of the type in this proposal
 * 2) redirects: This is currently being discussed at RfD. I'm not in favour of conflating lists and dabs. Isn't this the wrong venue for discussing whether to treat lists and dabs as equal in some regard when we have WP:SIANOTDAB?  Widefox ; talk 02:55, 13 March 2017 (UTC)
 * In my opinion the criterion fails to acknowledge that red linked titles can properly appear on a disambiguation page per WP:ONLYONE. I think pages ending in "(disambiguation)" should be measured by the number of listed titles opposed to the number of linked pages.--John Cline (talk) 05:29, 13 March 2017 (UTC)
 * I don't think this change is needed, because it clearly applies to DABs and not to the redirects to SIAs/Lists in question. People were just deleting them as uncontroversial housekeeping, not this specific clause. Since controversy has arisen, these should go to RfD. Patar knight - chat/contributions 14:25, 13 March 2017 (UTC)
 * Worth noting that the controversy is based on extending a search hack from dabs to SIAs. Widefox ; talk 11:43, 15 March 2017 (UTC)
 * From Hack: Hack (computer science), an inelegant but effective solution to a computing problem. Not all "hacks" are bad, and in this case it's helpful since most SIAs are just DABs by another name. Patar knight - chat/contributions 14:00, 16 March 2017 (UTC)
 * My point being that I've proven it isn't "effective" on dabs. So yes, it is a bad hack. One can't recommend or rely on it with dabs. If it was important surely getting it working on dabs would be a priority? What's the point in attempting to hold on to the hack by extending it to a minority of SIAs when it doesn't work on many dabs already, and doesn't work on the vast majority of SIAs? Saying that, I'm no fan of SIAs, so would welcome a revisit of the fundamentals. Widefox ; talk 01:21, 20 March 2017 (UTC)
 * Support proposal, given Widefox's claim that G6 explicitly allows these deletions. Patar knight - chat/contributions 19:29, 16 March 2017 (UTC)
 * Patar knight That's a straw man, I said "...G6 excludes creating them, ...", which we all agree it does, don't we? (I'd appreciate if you strike that as a misquote). We all agree above that "G6 Db-disambig" does not apply to a redirect, nobody has ever claimed it does. Widefox ; talk 01:00, 20 March 2017 (UTC)
 * That was said in the context of you applying G6 to delete those redirects in the past, and arguing that such redirects should be deleted. "G6 excludes creating them" is equivalent to "G6 bars their creation", and since G6 is a CSD, it's reasonable to interpret that as saying that G6 is a valid deletion criterion to be used on these redirects. Not sure there's another way to interpret what you said in that context. Maybe your word choice was poor and you meant to say something like "G6 does not have a clause regarding the deletion of these redirects"? Would be happy to strike if that's what you meant. Patar knight - chat/contributions 15:28, 20 March 2017 (UTC)
 * So we agree I didn't say G6 explicitly allows these deletions. It's a straw man.
 * My word choice was exactly what G6 says. We shouldn't base policy on an unreliable hack (maybe if a bot did create them all, this would be a plausible expectation, but we still shouldn't base policy on maintaining a broken hack), but I agree there's some clarity needed about SIAs and dabs, which I welcome and may solve most of these anyhow. Widefox ; talk 20:53, 21 March 2017 (UTC)
 * There's no functional difference between saying that "these pages should not be created per G6" and "G6 allows the deletion of these pages", just like there's no difference between saying "biographies which don't make a credible claim of significance should not be crated by A7" and "A7 allows the deletion of biographies without a credible claim of significance." Not these redirects pointing to SIA all SIA pages is not more a reason for deleting them then an argument that our DAB pages are imperfect, so we should delete all DAB pages because DABs are "broken". There's no reason why a bot like User:RussBot, which created a lot of the (disambiguation) redirects that are now being deleted, could not create similar redirects for SIAs with a bit of tweaking. Patar knight - chat/contributions 19:08, 22 March 2017 (UTC)
 * Patar knight Look at the section title, nobody is claiming G6 Db-disambig applies to redirects. It's a conflation/straw man several of us have explained. Nobody has or is claiming G6 "explicitly" allows these deletions. It's a straw man. As G6 is not explicit about deleting, just implicit (per my and your interpretation) we agree, but it isn't fair to say my position is, or has ever been, that it is explicit. Further, as the proposal is a conflation, how can it be supported? Throwing SIAs into the mix just muddies it. The hack will remain a hack that goes against the navigation flow we assume of WP:PRIMARYTOPIC. That should be taken up at disambiguation. I support having a bot create all the dab redirects. Having redirects targeting SIAs is controvercial, and should be taken up separately - there's discussion here Wikipedia talk:Set index articles about fixing the definition of SIAs which is the underlying issue here. Widefox ; talk 10:36, 28 March 2017 (UTC)
 * The criteria for speedy deletion (CSD) specify the only cases in which administrators have broad consensus to bypass deletion discussion, at their discretion, and immediately delete Wikipedia pages or media. They cover only the cases specified in the rules here. There's no such thing as "implicitly" allowed CSD deletions. It's either in as an uncontroversial, enumerated CSD criterion, or it's out and should go to a PROD/XFD process. By applying G6 to these redirects for years and then saying that "G6 excludes creating them", you either don't/didn't know what is allowed under G6 or you don't/didn't understand how CSD works. Arguing that G6 is "implicit" about allowing these redirects makes no sense, is demonstrably untrue given the backlash that that position is facing, and demonstrates the need for this proposal. Adding one line to the G6 criteria should be okay; most of the CSD criteria explicitly list out exceptions.
 * I'm also not sure how this goes against WP:PRIMARYTOPIC. The primary topic for "X (disambiguation)" is obviously the page which disambiguates between different articles named/related to X, which in some cases will be SIAs. This isn't about disambiguation, it's about the use of redirects for navigation. Even if the discussion leads to SIAs which are functionally DABs being converted to DABs, it still leaves out borderline cases (e.g. lists, broad concepts, SIAs with more content). Also, until the issue is resolved though, the use of "X (disambiguation)" redirects would both help readers and help tag intentional links in article text.--- Patar knight - chat/contributions 18:54, 29 March 2017 (UTC)
 * As nobody is claiming "explicitly" (or Db-disambig applies to redirects), isn't it time to strike it? It's obviously a straw man/misquote. (building a false dichotomy on a straw man is now bordering on personalising this). When using the word "you" here, do you mean all the editors/admins who've been doing this for years as standard practice until this hack objection? There's no such thing as a primary topic for "X (disambiguation)", it's "X". There's no topic called "X (disambiguation)" (dab pages aren't articles). The problem with relying on hacks (or trying to justify extending it as in this case), is that they aren't reliable by definition (but if it works sometimes it's useful). "backlash" built on sand, is still built on sand and needs calling out as a red-herring. The wider discussion about redirecting to SIAs is exactly the opposite direction to the talk at WP:SIA so SIAs clearly need some broader consensus. Widefox ; talk 00:12, 1 April 2017 (UTC)
 * I've said it before, and I'll say it again: G6 is applied far too often as a "none of the others fit" criterion. This is not its purpose. If the specific situation is not explicitly covered by one of the existing CSD criteria, it is not eligible for speedy deletion. -- Red rose64 &#x1f339; (talk) 22:15, 29 March 2017 (UTC)
 * I reluctantly support the initial proposal. I'm reluctant because I think the net effect will be to create a lot of busy work at RfD, but deletion of these types of redirects is plainly no longer uncontroversial. See also my discussion questioning the point of SIAs. --BDD (talk) 14:41, 16 March 2017 (UTC)
 * I would welcome looking at the wider picture. Questioning SIAs as you've done there, or subjecting the keep reasoning to wider scrutiny given that it clearly goes against the "creation" in G6, and the old consensus of direction (SIAs and dabs diverging) we've been going until now. That a couple have been contested is a fact, the reasons given are based on treating SIAs and dabs in some way the same, which I believe should have more wider consensus, especially as the reasoning given go against WP:PRIMARYTOPIC, WP:D ("..reasonably likely topic name..") and is a hack that is provably broken generally for dabs (as they don't all have such redirects today), so little utility in considering it useful to preserve (not delete) them to SIAs. The reasoning is an argument for more than not deleting, to make the hack work, it would need them creating both for all dabs and all SIAs, which G6 says not to create. I don't think we should base policy on a hack. Widefox ; talk 01:14, 20 March 2017 (UTC)
 * BDD The wording of the initial proposal is about G6 Db-disambig which nobody claims applies to redirects. Widefox ; talk 08:44, 20 March 2017 (UTC)

A9 and New/developing Pages
I question whether the A9 criteria for speedy deletion is an appropriate criteria to have at all, but at the very least the page should be allowed to exist for some period time to allow creators to establish the significance of the figure before they become subject to the rule. Pages that are incomplete and/or poorly sourced are flagged for improvement. Editors are not omnipotent and I see no reason that anyone should believe that they can consistently tell whether the subject of a still-developing page is important.

I logged in to help out with a page that someone new to wiki was creating for a figure that I know is of note, at least within relevant domains, but checking in within a week of its creation, I found that the page had been subject to speedy deletion. There are a great many wikipedia contributors who do not spend their lives logged into WP and thus will not respond to notices that require immediate action. And telling people to go through the process of tracking down the person who deleted it to get their content back is, to put it mildly, obnoxious. I wonder how much content that would be legitimately useful to fill in various niches within wikipedia has been deleted for the bizarre reason that the editor was unfamiliar with the subject (which I think many people would consider a sign that the editor might be the wrong person to alter the page at all rather than that the editor should permanently remove the material). MikeNM (talk) 00:42, 28 March 2017 (UTC) MikeNM (talk) 00:42, 28 March 2017 (UTC)
 * Well if that "figure" was a person, then the article should not be deleted using the A9 criterion. A9 is for a musical recording or list of musical recordings. There are other ways in which an article about a person can be deleted though. You can also ask at WP:REFUND if you know the name of the page, but not who deleted it. Some people also ask me directly on my talk page. But it does not garantee the page will be back. Another option is to get the page up as a draft, then there is more time to get it into shape before it gets tagged for deletion. For tagging for A9 deletions, I ask that the patroller waits 30 minutes before applying the tag, to give the writer a chance to include a claim of importance. Graeme Bartlett (talk) 14:37, 28 March 2017 (UTC)
 * To add to this, the policy already says Contributors sometimes create pages over several edits, so administrators should avoid deleting a page that appears incomplete too soon after its creation. That some admins are too careless when applying policy is a known fact but not one that can be changed by changing the policy itself. Regards  So Why  14:55, 28 March 2017 (UTC)
 * Agree with that, but would also add that A9 is a remarkably easy criterion to avoid. The entire article could be " is a song by ", or " is a popular song in " and it would be out of the woods. Since all we've got here is a vague example that was deleted "within a week of it's creation" which doesn't seem particularly hasty, I'm not sure a real issue has been identified here. Beeblebrox (talk) 00:19, 1 April 2017 (UTC)

Reviewing criteria for files
Now that the proposal at Wikipedia talk:Proposed deletion to apply PROD to files is passing, the criteria for files needs a review. Such change would affect the criteria. I welcome comments about this. --George Ho (talk) 06:08, 12 March 2017 (UTC)

Update: the File PROD proposal has passed. The criteria on files should be reviewed, including F5 (orphaned image) and F7 (invalid fair-use claim). --George Ho (talk) 17:55, 23 March 2017 (UTC)

Another update: The File PROD-ding is implemented into the WP:PROD policy. --George Ho (talk) 19:28, 4 April 2017 (UTC)

CSD A7 to include software
I would like to add software to be covered by the CSD A7 criteria, so it would read as such: "This applies to any article about a real person, individual animal(s), organization, web content, computer software, or organized event that does not indicate why its subject is important or significant, with the exception of educational institutions. This is distinct from verifiability and reliability of sources, and is a lower standard than notability. This criterion applies only to articles about web content and to articles about people, organizations, and individual animals themselves, not to articles about their books, albums (these may be covered by CSD A9), or other creative works. This criterion does not apply to species of animals, only to individual animal(s). The criterion does not apply to any article that makes any credible claim of significance or importance even if the claim is not supported by a reliable source or does not qualify on Wikipedia's notability guidelines. The criterion does apply if the claim of significance or importance given is not credible. If the claim's credibility is unclear, you can improve the article yourself, propose deletion, or list the article at articles for deletion."

The only change here is adding the phrase about software being covered. I would like to see this, as when patrolling and looking at new pages, software is increasingly likely to come up as a topic which makes no credible claim of significance - an example is Underwater (course). This would mean that these articles can be more easily deleted, bringing them in line with organisations and web content; I can see no reason that makes software special, an article has to provide a credible claim.

It is important to note that credible claim is a fairly high bar to deletion, so any questionable topics are still sent down the usual channels, this just means that the clear-cut cases can be deleted. I would like to gather thoughts and improvements here before I take this to a full blown RfC. TheMagikCow (T) (C) 15:39, 5 April 2017 (UTC)
 * I think the most recent discussion of this (or a subset) was in 2014, with substantial opposition, archived at Wikipedia_talk:Criteria_for_speedy_deletion/Archive_54. AllyD (talk) 16:17, 5 April 2017 (UTC)
 * I think my comments in 2014 are the same now - the best counter-argument would be lots of recent AfDs for software where the consensus was basically "what a waste of time - snow delete already" <b style="color:#7F007F">Ritchie333</b> <sup style="color:#7F007F">(talk) <sup style="color:#7F007F">(cont)  16:25, 5 April 2017 (UTC)
 * I think I should point out that much software these days (especially downloadable software) are already A7d as web content. They shouldn't be, but nevertheless, they are. Adam9007 (talk) 17:08, 5 April 2017 (UTC)
 * Exactly - and I think its time to clarify the policy. It is interesting to note that most of the support !votes from 2014 came with the condition that the proposal be expanded to all software. TheMagikCow (T) (C) 17:16, 5 April 2017 (UTC)
 * What do you mean by "A7d"? If you mean nominated for A7 deletion then you are certainly right, and over the years I have declined quite a few such nominations. If, however, you mean deleted with A7 cited as the reason, then I have very rarely seen that. If that is what you mean, can you give a few examples? The editor who uses the pseudonym "JamesBWatson" (talk) 19:45, 5 April 2017 (UTC)
 * Both. I saw an article about a Sonic The Hedgehog game deleted A7 even after my decline (see here). I was also warned for declining A7 on an article about, if memory serves, a mobile app. There are probably other examples, but these are the ones I remember at this time. The thing is, until recently, such subjects did indeed come under web content: WP:WEB said that anything distributed primarily or solely on the web is web content (that would include mobile apps and probably most other downloadable software). However, that was changed after an RfC. Adam9007 (talk) 21:49, 5 April 2017 (UTC)
 * I have looked at the speedy deletion example you give, and I agree that it seems to have been invalid. I have posted to the deleting administrator's talk page about it. Please note, though, that I did not deny that there are times when administrators wrongly use A7 for software, just that it does not, in my experience, happen very often. I see that I actually said "very rarely" which I now think was an overstatement: perhaps "not very often" would have been better. You say that "until recently, such subjects did indeed come under web content", but what you link to regards guidelines for notability, which is a completely different matter from the policy on speedy deletion. The relevant quote is "Any content which is distributed solely on the Internet is considered web content for the purposes of this guideline" (my emphasis), and it would be a complete misunderstanding of how Wikipedia works to cite that as justification for making the same interpretation of the speedy deletion policy.
 * For what it's worth, my impression is that on those occasions when administrators do delete software articles under criterion A7, it quite often, perhaps usually, relates to cases the article does not make it clear exactly what is being referred to, and anyone with little knowledge of software related matters could think it relates to content which runs on the web, rather than on a computer or other hardware. The editor who uses the pseudonym "JamesBWatson" (talk) 17:28, 6 April 2017 (UTC)
 * I see your point, but my point was that the old definition as given by WP:WEB supported the notion that downloadable software is web content. Also, I recently saw an article about a Nintendo Switch game (If I'm remembering right) tagged db-web. I declined, and the author cited the current WP:WEB definition on the talk page contested deletion as why it is not web content. Unfortunately, I can't remember the title. As for misunderstandings, significance is often confused with notability (I've even been accused of "making up my own notability criteria" regarding A7 removals), many editors think that WP:NOTINHERITED (an essay about deletion discussions), WP:INHERITORG (a notability guideline), and Notability_(web) (anther notability guideline) apply to significance and A7 too, so misunderstandings are not exactly uncommon. For what it's worth, I have written an essay addressing them, including the misconception that downloadable software is web content. Adam9007 (talk) 21:31, 6 April 2017 (UTC)

Some Quick Examples: — Preceding unsigned comment added by TheMagikCow (talk • contribs) 17:25, 5 April 2017 (UTC)
 * Articles for deletion/Underwater (course)
 * Articles for deletion/PACE Suite
 * Articles for deletion/World 8-4
 * Articles for deletion/3DimViewer
 * Articles for deletion/EXMACT


 * Oppose. I'm always skeptical of expanding A7 and including software is imho a bad idea for two reasons: 1) It will open a Pandora's box, leading to proposals to include all manner of products, not just software. And 2), for the same reasons supplied in the last discussion linked to by AllyD, which are still true today as they were back then. Unlike with the current subjects eligible for deletion, there is no clear way a software article can contain clear claims of significance or importance. It's not in the project's best interests to include subjects in A7 whose importance or significance no article creator, new page patroller or reviewing admin can reasonably, easily and clearly assess, especially since there is not even a notability guideline for software that could serve as a reference point. Also, I see no evidence that this problem has really increased in the last few years in a way that AFD or PROD(!) cannot handle it. Of the five examples mentioned above, two are not even about software but parts of software, both of which can and should be redirected to the article about the software per WP:ATD-R instead of listing it at AFD. As for the other three, PACE Suite can be merged into the article about the company per WP:ATD-M and WP:NPRODUCT, so 60% of the examples mentioned could be easily handled by existing processes; not really convincing. On a side note: If anything, software should be added to A9, not A7, since there is (again per WP:ATD-M) no policy-based reason to delete an article about a software that is made by a notable entity. Regards  So  Why  18:46, 5 April 2017 (UTC)
 * I am not aware of any specific significance guidelines for the topics included in A7 - please do correct me if I am wrong. I think that whilst being slightly subjective for all of the topics covered by A7, software is little different to the others already covered by A7. An article of no significance tends to just describe what exists or simply state the product exists. Claiming significance includes awards and recognition of the existence of the product. I also don't feel that a lack of a significant notability guideline for software is a major issue. All articles follow the WP:GNG - sources must be non-promotional, secondary and independent. These can usually be assessed by a new page reviewer - now we have the user group with certain requirements to join we can assume a degree of competence. However, I think that if we are talking about sourcing issues in an article, it is likely a significant claim has been made, even a company's website tends to give awards if applicable. Furthermore, sources != significance. I feel that a new page review can easily tell whether a claim would cause an article to be notable, rather than purely descriptive. I can't see any difference between the software inclusion and the web page inclusion, Best TheMagikCow (T) (C) 19:48, 5 April 2017 (UTC)
 * There are no significance guidelines; what does and does not constitute a credible claim of significance or importance has been the topic of many many many discussions on this talk page and elsewhere. I tried to collect some consensus at WP:CCSI but it's still mainly a collection of how many admins handle things. But, as I said above and others have said much more eloquently in the past, there are many articles about the subjects covered by A7 created every day, far too many for AFD or PROD to handle. On the other hand, there is no evidence that there is a widespread problem of such articles being created about software. On the contrary, as I pointed out above, oftentimes such articles can be handled differently by existing processes. Your proposal imho fails all requirements for new or expanded criteria:
 * It's not objective, as this discussion proves there is no agreement which software articles should be covered.
 * Many pages covered by the proposed expanded A7 should not be deleted per WP:ATD or WP:NPRODUCT
 * There is no evidence this is a problem that PROD and AFD can't handle it
 * WP:ATD covers many non-spammy articles and G11 covers the spammy ones, reducing the need per #3 as well.
 * So I understand where you are coming from but the risks clearly outweigh the benefits. Regards  So Why  20:29, 5 April 2017 (UTC)


 * Oppose As I said earlier,  software articles   often cause problems at AfD, because they can be very difficult to judge except wen in one's own specific field.  Let me ask--what exactly would be a statement of importance or significance  for software? as contrasted to an article that did not assert any? We're rushing ahead to do something to remove what we can't define -- that's the opposite of the intent of speedy.  If it seems really clear, Prod can be used, because if someone later notices it, the article can be restored easily.  If downloadable software is being deleted as A7, it shouldn't be, and admins may need to be reminded--or if necessary, the matter taken to Deletion Review.  (For many other types of products, G11 is a usable speedy criterion, but software articles   are generally not blatantly promotional, just descriptive. )   The only type of product that is really safe to speedy for lack of importance in A9, musical recordings, when the criterion is very straightforward.  DGG ( talk ) 19:45, 5 April 2017 (UTC)
 * It is content based, on a claim that would cause source to be written about the article and therefore the article would be notable if the fact/claim is shown to be true. EG:
 * "XXY is a software product developed by YXX studios. It was released in 2012. It features 3D CAD and other product modelling tools."


 * Would not be significant - it is purley desciptive.
 * "XXY is a software product developed by YXX studios. It was released in 2012. It features 3D CAD and other product modelling tools, and has won ZZZ award."


 * Could be significant due to the award being given. TheMagikCow (T) (C) 19:52, 5 April 2017 (UTC)


 * Also,
 * "...Is the one of the largest and most widely used CAD programs"
 * Is a claim of signficance, as is this were true, sources are likley to exist. I can't see how judging this is any different to judging that of a website or company. TheMagikCow (T) (C) 19:56, 5 April 2017 (UTC)
 * Certainly it is often possible to show very easily that a software product has a caim to significance; what is much harder is showing that it does not--there is too much of a fuzzy area. The problem is that if someone write a very brief software article it may or may not be a notable produce. We do not want to speedy delete articles that do not on the face of it have a claim of significance if they are actually notable--this is supposed to be a much less demanding criterion. With a company article of even one sentence long it is often possible to show there is no possible reason for an article in an encyclopedia.. e.g. "Smith's is a corner grocery." Yes, it might conceivably be notable, but the odds are infinitesimal.  Similarly with "John is president of the senior class at Uptown High School".  DGG ( talk ) 23:40, 6 April 2017 (UTC)


 * Oppose At one time I used to think that A7 should be extended to software, and certainly it is occasionally frustrating that an article on software which is blatantly obviously not notable or significant can't be speedily deleted. However, I have gradually come to realise that the frequency with which that happens is tiny compared to the frequency with which A7 is justifiably used on other types of articles, and speedy deletion should be reserved for those situation where requiring every case to go to a discussion would cause significant disruption, which is not so here. Add to that SoWhy's and DGG's very valid comments, and I think there is a very strong case against the proposal. The editor who uses the pseudonym "JamesBWatson" (talk) 19:54, 5 April 2017 (UTC)

F4 two day rule removed?
I recall there used to be a a subrule to F4 which stated that non-free files with no source could be deleted after being tagged for two days. The documentation of di-no source states this functionality. When was this removed? – Train2104 (t • c) 11:13, 1 April 2017 (UTC)
 * It was never in F4. This is what WP:CSD looked like when the two-day parameter was added to Template:di-no source, so it's clearly referring to the first sentence of F7.  That went through a series of narrowings and poor "clarifications" in 2008 until its last vestiges were removed in this edit, without (so far as I can find) any discussion either before or after. —Cryptic 14:19, 1 April 2017 (UTC)
 * Thanks for digging it up. It seems like a good idea to start a discussion as to which is preferable, as having the policy not match the template is not a good idea. In addition, the pre-dating hack doesn't really work well with the daily maintenance category system, I had to recreate an old category today. – Train2104 (t • c) 20:58, 1 April 2017 (UTC)
 * I have updated Wikipedia files with unknown source subcategory starter to include a note as to not to delete emptycats until 5 days have passed so we hopefully have fewer "lost" DI's. Pinging admins who normally do these deletions. – Train2104 (t • c) 14:50, 6 April 2017 (UTC)
 * @Train2104 : I'm not sure that's 100% necessary. I have a script that finds and fixes 'lost' DI's (resulting from MediaWiki cache issues or malformed tags).  Would you consider undoing that change?  I will be filing a BRFA to do this automatically.  Regards,   F ASTILY   20:47, 6 April 2017 (UTC)
 * I've reverted that edit. That said, though a script is a good idea for such rescue, I'm not sure if we should be deliberately leaving a properly made nomination to be picked up by the cleanup script. – Train2104 (t • c) 01:45, 7 April 2017 (UTC)

Listing multiple pages for CSD G4 in the meta template
Please take a moment to comment at Template talk:Db-meta. --Izno (talk) 11:43, 7 April 2017 (UTC)

Pages that have survived deletion discussions
It seems strange that U1 isn't on the list. What if a personal user page was kept at MfD, but the user later decides he no longer wants it? Must he MfD it again? Adam9007 (talk) 17:35, 8 April 2017 (UTC)


 * I have boldly added U1 to that list. I don't see why a user should not retain that latitude within his userspace just because a pre-existing discussion decided to keep it.  Anyone should feel unusually free to revert that addition if it is controversial.  Tazerdadog (talk) 03:21, 9 April 2017 (UTC)
 * Agree, if a U1 were brought to MfD, even if it has been nominated by others for MfD in the past, it would generally be then speedy deleted. — xaosflux  Talk 12:52, 9 April 2017 (UTC)

T2. Misrepresentation of policy being misused
Several times I have declined a speedy deletion request because somebody has used on a template, but where (to me) WP:CSD (Misrepresentation of policy) is clearly not the case, since the template that is being tagged is not an unambiguous misrepresentation of established policy. I'm not the only one finding this; a recent example was by  of a  that was placed by  using WP:TW.

I think that I've worked out how this is happening. The description at WP:CSD includes the text "... and speedy deletion templates for issues other than speedy deletion criteria" - I think that this is being read as if it were "... and is also for the speedy deletion of templates for issues other than speedy deletion criteria", that is, they are using it as a kind of blanket "none of the others fit, but since it's a template, I can use this one" criterion. I feel that the wording should be clarified, but I'm not sure what would be best. Twinkle will need amending too, since at twinklespeedy.js there is the code  here we have 'includes "speedy deletion" templates for issues that are not speedy deletion criteria', which could be misread as 'includes the "speedy deletion" of templates for issues that are not speedy deletion criteria', again, a kind of "none of the others fit, but since it's a template, I can use this one" criterion. -- Red rose64 &#x1f339; (talk) 07:28, 16 April 2017 (UTC)


 * I don't think the text is really unclear but it never hurts to make things clearer. How about just changing the text in db-policy to match the one in WP:CSD which reads e.g. disclaimer templates intended to be used in articles and speedy deletion templates for issues other than speedy deletion criteria? That way it's clear that these are just examples of templates that can be deleted under T2. Regards  So Why  09:15, 16 April 2017 (UTC)
 * I've seen T2 used for any and every kind template (except actual misrepresentations of policy), and if this bit of wording is likely to be the root cause of such practices, then it ought to be changed. It shouldn't be difficult to simply list a different example? I now recall there was one instance when an (otherwise sensible) editor thought that an article created in error in the template namespace was eligible for T2 because there wasn't a policy it was a representation of I attributed this funny reasoning to the fact that this user might have been annoyed, but could this be an easy misunderstanding to make? –  Uanfala (talk) 10:08, 16 April 2017 (UTC)
 * Adding that there was a brief relevant discussion back in December, where a third possible cause for the misuse of T2 was indicated. – Uanfala (talk) 10:18, 16 April 2017 (UTC)
 * Unlike Uanfala's experience, in my work with templates, TFD, and CSD, I hardly ever see T2 abuse, or at least the deleting administrator isn't using it in the deletion summary. That was perhaps the first or second such decline I've made. I only noticed that it was an issue when I saw that the description was removed from the uw template. I have seen a few instances of proper use of T2, and made a few myself, so the criteron shouldn't be removed. I don't think the wording is why it's happening. JamesBWatson's comment in the above linked discussion (the problem is that templates are commonly created which ought to be speedily-deletable but aren't, so good-faith editors try to stretch speedy deletion criteria) is perhaps the best way to put it. Personally I don't think such a new blanket criterion is necessary - I use G2 for one-sentence articles, single links/images, or pages consisting solely of a template loop, G12 for unattributed copies of an entire article, and move to articlespace and deal with it there for anything else that looks like an article. That takes care of almost all the cases. Rewording it to eliminate the speedy deletion mention doesn't seem like it'll harm anything, so let's try it, though. – Train2104 (t • c) 13:12, 16 April 2017 (UTC)


 * Is there any evidence that the suggested misreading of the deletion criterion is the cause of this problem, or is it just a speculation? I can see that the wording could be read that way, but it seems to me an unlikely reading, and I find it difficult to believe that enough people will misread it that way to make this a common happening. I think it is much more likely to be a simple application of the principle "if you think a page should be deleted but you can't find a criterion that fits, then just use any criterion, in the hope an administrator will accept it. You have nothing to lose by trying, and sometimes it works." Essentially the same reason is behind a large proportion of reports to AIV for things that are not vandalism, such as edit-warring, POV editing. That is not speculation: more than once I have known an editor explicitly say that he or she knew full well that their report was not about vandalism, but quite often administrators act on such reports, and if they do it's a good deal less trouble than taking it to AN/EW or AN/I or whatever might be the correct forum. I have likewise occasionally known editors explicitly say that they have used a speedy deletion criterion that they knew was not strictly valid, in the hope that an admin will delete anyway. I don't specifically remember whether in such cases it has ever been T2 that has been involved or not. The editor who uses the pseudonym "JamesBWatson" (talk) 19:59, 16 April 2017 (UTC)

Add a general criteria for duplicates to existing pages (G14)
Although this is already covered by A10, T3, and F1, with partial coverage by F8, I don't see why this can't apply to drafts or categories as well. Any thoughts on this? ToThAc (talk) 18:47, 5 April 2017 (UTC)
 * It should not apply to drafts because some users may wish to develop a draft independent of work that someone else is doing (or, more likely, has already done some years ago and abandoned). Deleting a draft because someone else started one on the same subject years ago is nonsensical. A2soup (talk) 18:54, 5 April 2017 (UTC)
 * Good point, though a grace period might be sufficient for drafts (maybe two days to a week)? ToThAc (talk) 19:27, 5 April 2017 (UTC)
 * You will have a hard time trying to get that accepted. Currently, abandoned drafts can be deleted after not being edited for six months, and even then only if they have the "articles for creation" template. If they receive one edit every six months they can stay indefinitely (and many do: it is not just a theoretical possibility). Even getting policy changed to allow that very limited amount of deletability for old drafts was a compromise as the result of discussion in which there was considerable opposition to any speedy deletion criterion for drafts. I therefore very much doubt that you would stand any chance at all of getting consensus for deletion after a week, let alone two days. Besides, why on earth would you want to? Don't you think that there are many editors who have only a limited amount of time to devote to Wikipedia, and are likely to take far more than a week to develop a good draft for an article? There are numerous examples of editors taking very much longer than that to develop a new article, especially when several editors have cooperated on an article. The editor who uses the pseudonym "JamesBWatson" (talk) 19:38, 5 April 2017 (UTC)
 * A grace period to do what? Submit to editing a prior draft by someone else instead of your own? Why not just let people draft in peace? A2soup (talk) 20:50, 5 April 2017 (UTC)
 * I'm opposed to this. As above, drafts can take time to develop and when they duplicate the title of a live article, it's usually because someone has a major improvement in mind. The CSD categories that exist at the moment are perfectly adequate. Exemplo347 (talk) 20:53, 5 April 2017 (UTC)


 * I really don't see any reason for this. The only situation in which someone is likely to create a page like this is for a draft article, and there's really no harm in letting them sit around for a while. Are there any other situations in which this is likely to be useful and wouldn't be covered under other CSD criteria?  Hut 8.5  21:17, 5 April 2017 (UTC)
 * Redirects, which would be covered by a G criterion, are another issue - duplicates (in the sense of multiple redirects from similar titles to the same target) are usually something we want to keep not delete. Thryduulf (talk) 11:09, 6 April 2017 (UTC)
 * The criteria mentioned were created for specific reasons that do not apply to all pages. I believe that your proposed G14 not only fails for the reasons mentioned above but also fails the requirement #3 at the top of the page since such pages are not really created frequent enough to require speedy deletion to handle them. Regards  So Why  12:04, 6 April 2017 (UTC)
 * Duplicates, including drafts, probably not categories, are best solved by redirecting. No fanfare, no overheads, and no damage for cases where you make a misjudgment such as where someone is using something as a template for a similar but different topic. Whether it is mainspace, userspace or DraftSpace, the redirect is likely to assist someone, and to be otherwise harmless. --SmokeyJoe (talk) 07:36, 19 April 2017 (UTC)

Modules speedy deletion
Hello, as the only author of Module:Sister project links, I would like to ask for its speedy deletion. However the wiki template Db doesn't work in Lua, so I propose to precise this exception in this manual, for example by asking to post a special request on Requests for deletion. JackPotte (talk) 11:08, 19 April 2017 (UTC)
 * I would suggest adding the line  which by analogy with JavaScript pages, should put the page into  - but it doesn't. As an aside, you should never use  directly, instead use a template specific to the criterion that applies, in this case . -- Red rose64 &#x1f339; (talk) 11:21, 19 April 2017 (UTC)
 * Check out what I did on Module:Sister project links/doc and what this did to Module:Sister project links. Used db as a test, you can use db-author yourself. Jo-Jo Eumerus (talk, contributions) 12:13, 19 April 2017 (UTC)
 * Thank you that's another solution which forces the admins to think about deleting the uncategorized module doc after. JackPotte (talk) 12:17, 19 April 2017 (UTC)

Add G14: copyvio temp no longer needed
I recently marked Talk:Koinonia/Temp as speedy G7, but G7 is not the real reason.

The real reason is: "Delete a temp page which is no longer needed, which was originally created per instructions at Template talk:Copyviocore/Temp as a temporary stand-in for an article being investigated for possible WP:COPYVIO. If the investigation doesn't result in the deletion of the article, then the temp file is no longer needed and should be deleted." Mathglot (talk) 06:47, 19 April 2017 (UTC)


 * In that case deleting the temp file is under G6 - Housekeeping, we don't need another separate criterion for this. Roger (Dodger67) (talk) 06:55, 19 April 2017 (UTC)


 * Oh okay, I'll change the code on the file, thanks. Mathglot (talk) 17:46, 19 April 2017 (UTC)

"RfC: Remove speedy deletion criteria A7 and A9" at WP:VPP
Notice: There is currently a RfC at WP:VPP entitled RfC: Remove speedy deletion criteria A7 and A9. Since this affects this policy, you are invited to participate. Regards  So Why  15:09, 26 April 2017 (UTC)

Re-reviewing F7 criterion - Invalid fair use claim (April 2017)
Now that WP:PROD applies to "File:" pages and that Twinkle is updated to allow PROD-ding on files, we can review WP:F7 (invalid fair-use claim). The following passage looks subjective, and the duration is the same as PROD: "Invalid fair-use claims tagged with may be deleted seven days after they are tagged, if a full and valid fair-use use rationale is not added."

Also, I'm concerned about the following: Non-free images or media with a clearly invalid fair-use tag (such as a tag on a photograph of a mascot) may be deleted immediately. An invalid licensing can be resolved by changing the licensing, right?

Also, the following passage is challenged: "Non-free images or media from a commercial source (e.g., Associated Press, Getty), where the file itself is not the subject of sourced commentary, are considered an invalid claim of fair use and fail the strict requirements of Wikipedia:Non-free content criteria; and may be deleted immediately." I tried db-f7 on File:Emma Morano (2016).jpg because the pic was created by Reuters, but the tag was replaced with Di-replaceable fair use.

Considering whether any image fits the "invalid fair use" criterion, I wonder whether "invalid fair use" claim is resolvable by improving the image description, e.g. fair use rationale. --George Ho (talk) 12:43, 18 April 2017 (UTC)
 * With respect to the Reuters image of Emma Morano, did you ask the decliner why it was declined? Using Twinkle for F7 on commercial images provides space for an optional explanation.  I've always used that space to identify the press agency. -- Whpq (talk) 13:28, 18 April 2017 (UTC)
 * Somehow, the swapping was reverted by someone else. --George Ho (talk) 18:38, 18 April 2017 (UTC)
 * And the image is speedily deleted. George Ho (talk) 21:48, 18 April 2017 (UTC)

@Whpq: What about files tagged with Di-disputed fair use rationale and the clause related to that template? George Ho (talk) 01:34, 25 April 2017 (UTC)
 * I don't understand what you are asking. Can you clarify? -- Whpq (talk) 01:50, 25 April 2017 (UTC)
 * I'll rephrase, Whpq: The clause, "Invalid fair-use claims tagged with may be deleted seven days after they are tagged, if a full and valid fair-use use rationale is not added." Is that clause necessary anymore, now that PROD recently applies to files? PROD-ded files can be deleted seven days after; same for those tagged with "di-disputed fair use rationale". George Ho (talk) 01:53, 25 April 2017 (UTC)
 * I'd just treat this as two different deletion reasons that happen to have the same waiting period. -- Whpq (talk) 16:41, 26 April 2017 (UTC)
 * @Whpq: I still don't see a difference between two templates indicating the same waiting period. However, I guess you and I would agree to disagree about the clause. Template:Di-disputed fair use rationale is transcluded in 25 pages], while Template:Proposed deletion/dated files is transcluded in 159 pages (was 300+ several days ago). Huge number, eh? Also, File:Take-That-Love-Love-X-Men-First-Class-music-video.jpg is tagged with the former template instead of the latter, but the concern is too complicated for the former. Same for File:QuantumLeap10Cover.JPG. Response? George Ho (talk) 17:49, 26 April 2017 (UTC)
 * I found the di-disputed fair use rationale to be somewhat misused, so I shifted some to FFD: ,,. I wonder whether the template is misused in other pages. George Ho (talk) 18:47, 26 April 2017 (UTC)
 * The fact that you've feel the template being misused is, at least at this point, only your opinion, and not (in my opinion) a sufficient reason to go around mass converting files tagged with "di-disputed fair use rationale" to prod templates. If you feel further discussion is warranted, then moving the discussion to FFD seems fine; however, if the "di-dfu" template is to be deprecated, then that's something the community should decide to do, not you. I suggest you stop the conversions to file prod for the time being until this can be clarified. -- Marchjuly (talk) 01:13, 27 April 2017 (UTC)
 * All right, Marchjuly. I'll refrain from converting the template to PROD, okay? I'll convert only some to FFD if I want to. --George Ho (talk) 01:20, 27 April 2017 (UTC)