Wikipedia talk:Criteria for speedy deletion/Archive 41

Queston about G7
I happened to notice the deletion discussion Articles_for_deletion/Simon_Williams_(comic_artist). In this case, it is clear that the user who created the page didn't actually want the page deleted, but said to go ahead with deletion out of frustration with the page being nominated for deletion. After the page was deleted, the page creator posted an additional comment which made it clear that he was very upset that the page was deleted. I'm asking about this here because I'm really uncertain if G7 was meant to apply when a page creator doesn't think the page should be deleted, but has nevertheless posted a comment saying that the page should be deleted. Is G7 appropriate in such cases, or is it only appropriate when the page creator actually wants the page to be deleted? Could some clarification on that perhaps be added to the G7 description or to the explanations subpage? Calathan (talk) 22:25, 10 December 2010 (UTC)
 * It's spirit of the rule that's important and not its exact wording. If people thought the article should have been deleted then there's a good chance it did. If someone issued a PROD then we can be sure the creator would be the only one that objected; forcing a week long AfD. By the user consenting to deletion we know he wouldn't contest the PROD, the PROD would stand and the article would be deleted... in a week's time. Using CSD G7 allows us to skip that and remove a non-notable article without it hanging around for a week. I think the user realised that the article needed to go, and his final comments were just a bit of drama: laying a guilt trip, calling us snobs and vowing never to use the site again. — Fly by Night  ( talk )  16:06, 11 December 2010 (UTC)
 * I never saw the article in question, so I have no idea how close or far it was from meeting the notability guidelines. I was just surprised that it got deleted as a G7.  My assumption had been that G7 was only for cases where a person actually wanted the article deleted.  While you say the spirit of the rule is what's important, if different people think the spirit of the rule is something different from reading it, then I think the wording needs clarification.  Also, I don't think the user thought the article needed to go.  I think he still has no idea how the notability guidelines work and didn't understand why the article was being deleted. Calathan (talk) 16:30, 11 December 2010 (UTC)
 * You make a good point about the interpretation. I tagged an article for something a while back and, between tagging and an admin seeing it, the article was improved so that it didn't meet the criteria. But the admin deleted it, per db-blanked, shortly after because the user blanket the article. So in that case, implied consent was enough to delete per CSD G7. — Fly by Night  ( talk )  16:57, 11 December 2010 (UTC)
 * What Fly by Night says often happens, and I will frequently suggest just that to authors of  articles I move from speedy to prod because they do not fit a speedy reason, but are essentially hopeless. My usual wording is:   If you decide that the article cannot meet our standards, you can facilitate matters by placing at the top a line reading :   .    But on the other hand, if I se someone deleting an article of theirs that appears to have considerable promise, I'll query them before deleting.    DGG ( talk ) 01:59, 12 December 2010 (UTC)


 * I just noticed this thread, and figured I might as well comment since I did the deletion. I saw that the user was clearly frustrated, but he was also notified of what the problems with the article were and how best to go about fixing them if possible. He had a whole week available to attempt to fix it up, but his immediate reaction was to throw a fit and say to go ahead and delete it. He claims he was given no guidance, when in fact Drmies explained quite clearly what the problem was. He got advice, but he didn't like what the advice was so he took his ball and went home. We say this is the encyclopedia anyone can edit, but the fact is that some people have too much ego and just can't get down with the way things are done here. Beeblebrox (talk) 20:15, 19 December 2010 (UTC)

Uiolentapneumonoultramicroscopicsilicovolcanoconiosising
I saw this, and I just couldn't let this one go by; "Uiolentapneumonoultramicroscopicsilicovolcanoconiosising. pronounced We-o-lenta-new-mono-ultra-microscopic-silico-volcano-cony-osis-ing. derived from the word pneumonoultramicroscopicsilicovolcanoconiosis. the word was created on the 21st of december 2010 it has 56. The forcible torture of making victim inhale volcanic silicon molecules causing inflammation of the lungs, resulting in scaring of tissue and possibly disease for the purpose of causing harm and pain to the individual/individuals." The Blade of the Northern Lights ( 話して下さい ) 16:57, 21 December 2010 (UTC)


 * Hooray. &mdash; Timneu22 · &#32; talk 17:06, 21 December 2010 (UTC)
 * I hate it when my tissues get scared; I can never find out where they hide. Half  Shadow  18:17, 21 December 2010 (UTC)


 * It seems like forcing somebody to say or spell that word would be an even worse torture (or enhanced interrogation technique). Jehochman Talk 18:35, 21 December 2010 (UTC)

Just when you thought you'd seen everything...
This has to be the most bizarre garage band ad I've ever seen.

HIT-5 is a five-member mainland Chinese boy band that debuted on October 20, 2008 under TH Entertainment. The group consists of Guo Zi Yu, Gao Yu, Dong Yu Feng, Yang Fan, and Duan Huang Wei. HIT-5 stands for Handsome Idol Teenagers. The group has released one full-length album, a mini-album, and various singles.

Members Guo Zi Yu Guo Zi Yu (Chinese: 郭子渝) is HIT-5's leader and main rapper. His English stage name is G-KING. He was born on December 09, 1988 in Henan. He is 179cm tall and weighs 60kg. His favorite artists include the Black Eyed Peas, Jay-Z, Beyonce, Jennifer Lopez, JLS, TVXQ, BIGBANG, Mayday, and Wang Lee Hom. He enjoys playing soccer and swimming. He has type O blood.

Duan Huang Wei Duan Huang Wei (Chinese: 段黄巍) is one of HIT-5's main vocals. His English stage name is David. He was born on December 08, 1989 in Jiangsu. He is 184cm tall and weighs 66kg. His favorite artists include Kim Jaejoong, The Black Eyed Peas, and Lady Gaga. He enjoys sleeping and has type A blood.

Gao Yu Gao Yu (Chinese: 高宇) is HIT-5's main dancer and rapper. His English stage name is kido. He was born on February 06, 1989 in Jiangsu. He is 180cm tall and weighs 65kg. His favorite song is I Believe I Can Fly. He enjoys playing basketball and has type B blood.

Dong Yu Feng Dong Yu Feng (Chinese: 董玉峰) is one of HIT-5's vocals. He was born on December 02, 1989 in Anhui. He is 183cm tall and weighs 60kg. He enjoys spicy food, likes the color green, and has type O blood.

Yang Fan Yang Fan (Chinese: 杨帆) is one of HIT-5's vocals. He was born on January 26, 1990 in Jiangsu. He is 182 cm tall and weight 63kg. His favorite artists include TVXQ, G-Dragon, Taeyang, and Super Junior. He likes sleeping, the colors black and white, and listening to music. He has type A blood.

Discography Full-Length Albums

Mini-Albums

 Singles 

References (1) http://baike.baidu.com/view/1944685.htm (2) http://fuckyeahhit5.tumblr.com/post/2596600230/hey-do-you-know-their-official-website-or-full#notes (3) http://www.yesasia.com/us/nothing-do-not-loves/1022853948-0-0-0-en/info.html

In my 8 1/2 months on NPP, I have never seen a band article advertising the member's blood types. The Blade of the Northern Lights ( 話して下さい ) 22:16, 7 January 2011 (UTC)
 * Perhaps they're members of some Vampire rock genre? Elen of the Roads (talk) 23:59, 7 January 2011 (UTC)
 * There's a common belief in parts of Asia (our article mentions Japan and Taiwan) that blood type determines personality, somewhat like star signs. This has lead to blood type being a standard item in this kind of profile. Algebraist 00:07, 8 January 2011 (UTC)
 * Yes, this actually reads like random but genuine publicity for a generic talent-agency created Asian boy band to me. — Gavia immer (talk) 00:32, 8 January 2011 (UTC)
 * I know about the whole blood type thing (I'm going to grad school in the fall to study Japanese history); never seen it in a band ad anywhere. Many other contexts, yes, but this is a first for me.  Suffice to say that Melt Banana and Chthonic don't advertise such things (although they're also about as far from boy bands as you can get).  The Blade of the Northern Lights  ( 話して下さい ) 01:11, 8 January 2011 (UTC)

A7 criteria
I have come across a few articles that admins have refused speedy deletion on the latest being David Rossiter which has since been speedy deleted. The admin stated that the article made ...a credible assertion of importance or significance, sufficient to pass A7. A cursory glance at what was stated in the article along with the sources would have shown that it was BS. So if I create an article about myself and claim for example that I was a number 1 selling musician or the first in some field making me notable with no sources to back this up, then is this enough to pass this criteria? Mo ainm ~Talk  10:20, 21 December 2010 (UTC)
 * Yes, unless it's blatantly non-credible. First published Inuit hip-hop artist? Credible. First woman to sail around the moon? Not so much. Thparkth (talk) 12:28, 21 December 2010 (UTC)
 * Good examples. :-) And the latter would probably be a G3 rather than an A7. Regards  So Why  13:47, 21 December 2010 (UTC)
 * I was the one who declined this A7, which has subsequently been deleted as a Hoax. Obviously if someone had checked for sources and tagged it as a hoax then my declining the speedy would be troutworthy in the extreme. But in my understanding there is no obligation to search for potential sources when correcting a deletion tag. I gave a cursory glance at the article, it was unsourced and made what to me was a credible assertion of importance. So I replaced the tag with a BLP prod as it was an unsourced new BLP that clearly asserted not just importance but notability. If someone who knew the subject or had tried to source it tags it with G3 that is ideal, but I consider my BLPprod tag was correct and A7 was an incorrect tag. We deliberately set the speedy deletion criteria to err on the side of caution, so that contentious and borderline deletions should be by prod or AFD. This means that many articles which are incorrectly tagged for speedy deletion will subsequently be deleted at AFD or after someone has tried to source them and found them to be puffed up, or in this case a fake. To my mind the best answer for that is to try and get more of our taggers to slow down and try and source articles.  Ϣere  Spiel  Chequers  14:41, 21 December 2010 (UTC)
 * Forgot about this thread, I wasn't getting at you WereSpielChequers I was just looking for clarification. So if it is unsourced but a claim is made what do you do then? Mo ainm  ~Talk  23:05, 23 December 2010 (UTC)
 * I'd say it depends on the claim. For example, someone just created an article about an obvious nobody, with the words "won the nobel prize" in it. This is obviously false, so I just flagged it a7/g3. But if you read a claim like "is the top band in Brazil" and you google it but don't get any results, I often post the A7 tag with text above it (and a comment) that says something like "this google result shows the claims are untrue." &mdash; Timneu22 · &#32; talk 23:09, 23 December 2010 (UTC)

R3
R3 is currently for recently created implausible redirects. Why is it important that they are recently created? The redirect may have been created a few years ago but never deleted. If it has no links, what difference does its age make?  McLerristarr &#124;  Mclay1  13:45, 23 December 2010 (UTC)


 * Because when discussing redirects, WP:ITSUSEFULL is a valid argument. As such, any redirect that survived a long period of time was most likely noticed by some editor and they decided that it's a useful redirect (by not nominating it under R3). But if even one person finds a redirect useful (which we have to assume after all that time), we should not delete it without discussion. Regards  So Why  14:02, 23 December 2010 (UTC)
 * (ec) The whatlinkshere tool is useful for judging how useful a redirect is. If those incoming links are removed, there's no way to determine if it was linked to and considered a worthwhile redirect in the past. That's less of a concern with a newly created redirect of course. Other possibilities are here. –Whitehorse1 14:09, 23 December 2010 (UTC)


 * It depends what namespace it's in however. In the main namespace, I agree, but in other namespaces, people often don't bother cleaning up redirects. The redirect that sparked this question was in the category namespace. Very few people will have ever seen that page but no one bothered to nominate it for deletion. I fail to see how its age, which has nothing to do with its usefulness (in this specific case), makes it any different to other implausible redirects cased by moves (except it wasn't exactly moved since it's a category – all the members were moved). I still think R3 should be for any age redirects, at least for non-mainspace pages. Editors just need to apply common sense before nominating things.  McLerristarr &#124;  Mclay1  15:04, 23 December 2010 (UTC)


 * As explained above, the older the redirect, the far likelier it is that someone found it useful. You can guess that they didn't but uncertainties are nothing that should be handled with speedy deletion. If it was around for years, there is no harm in keeping it for 7 more days at RFD and it's really not that much work to start a RFD, is it? And of course, we don't have to worry about storage space or about numbers, so why (speedy) delete them at all? Unless they present a problem, there really is no point and if they do, you can explain it at RFD. Regards  So Why  15:49, 23 December 2010 (UTC)


 * When we say that a redirect "has no links", we mean that it's not being used as an internal link on the English Wikipedia. The older the redirect is, the more likely it is that someone has bookmarked it or is otherwise using it off-wiki—something we can't easily test for.  WhatamIdoing (talk) 18:46, 31 December 2010 (UTC)

Orphaned-talk-page-deleting bot broken?
I just deleted a significant number of orphaned talk pages from CAT:CSD that apparently had been up for some time. Is there something wrong with the bot that deletes orphaned talk pages? Nyttend (talk) 14:12, 31 December 2010 (UTC)


 * seemed to have stopeed working on 27 December. You might want to ask about it, who runs the bot. Regards  So  Why  15:11, 31 December 2010 (UTC)

This would be which CSD reason?
HOW I TAUGHT MY GRANDMOTHER TO READ AND OTHER STORIES

THIS IS THE FIRST BOOK OF SUDHA NARAYANA FOR CHILDREN.IN IT SHE REFERS TO HER PREVIOUS EXPERIENCES THAT CHANGED HER LIFE.IN THEM WE COME ACROSS MANY INCIDENTS OF HER LIFE LIKE HOW SHE TAUGHT HER ILLITERATE GRANDMOTHER TO READ AND HOW A SMALL COMPANY WITH A MEAGRE CAPITAL OF Rs10,000 GREW UP TO BE INFOSYS.WE ALSO COME ACROSS MERE BEDTIME STORIES WHICH HAVE A LOT OF MORAL IN THEM.SHE ALSO TELLS OF HOW PEOPLE LIKE JRD TATA CHANGED HER LIFE

&mdash; Timneu22 · &#32; talk 14:07, 22 December 2010 (UTC)


 * Not a speedy candidate. It's a poorly written article about a book which is not obviously notable, but none of that's a reason for speedy deletion. Algebraist 14:13, 22 December 2010 (UTC)


 * This is obviously a case for speedy userfication. There are so many things wrong with this article, it does not belong in the main namespace. &mdash; Timneu22 · &#32; talk 14:15, 22 December 2010 (UTC)


 * I'd say this is a borderline G11. Otherwise, if you can't find an article on the author, just prod it as a non-notable book. Prods and AfD's are also for stuff that doesn't belong in Wikipedia. --  Blanchardb -Me•MyEars•MyMouth- timed 14:27, 22 December 2010 (UTC)


 * I know, but as we've had this conversation a bazillion times, PROD often fails (author will just remove it) and AfD, in a case like this, is a waste of people's time. Speedy userfication in a case like this is the best of all worlds. It doesn't BITE the newbie, it would explain to the newbie why the article is in poor condition without eliminating the content, and it removes the obvious nonsense from the main namespace. &mdash; Timneu22 · &#32; talk 14:31, 22 December 2010 (UTC)
 * Userfication is fine where the "article" is really an autobiography and can become a userpage. I've also used it to turn testpages into sandboxes. But I'm uncomfortable using it for potential articles, especially BLPs and ones that should actually be deleted. In my view the place to develop and improve articles is in mainspace where they can be categorised and multiple editors can work on them. That said I've heard of at least one wiki that has "SHOUTING" as a deletion reason, and while I don't think we should implement that here, I can see the temptation. As for the broader question, CSD is for a limited number of clear cases which can short-circuit the normal deletion process, most articles that merit deletion do qualify for one or other speedy deletion tags. But an article can be pretty obviously heading for deletion and yet not qualify for speedy deletion. If someone can identify a frequently occurring, clearly definable group of of obvious deletions then we could introduce a new CSD type.  Ϣere  Spiel  Chequers  14:57, 22 December 2010 (UTC)
 * IF ANYTHING THAT TITLE NEEDS TO BE CHANGED BECAUSE IT DOES SEEM LIKE SHOUTING! Maybe we need speedy inubation, then? That's the area for improving these types of articles, right? &mdash; Timneu22 · &#32; talk 15:03, 22 December 2010 (UTC)
 * I frequently move articles to correct capitalisation issues. Even if you believe something merits deletion there is no harm and much good faith in improving it even if at the same time you are tagging it for deletion. As for incubation, I see that as having similar drawbacks to userfication. The advantage of a wiki is collaborative editing and we only really get that in mainspace.  Ϣere Spiel  Chequers  15:11, 22 December 2010 (UTC)
 * I see. I guess my goal is to keep the main namespace as professional as possible. As for a CSD for this, I don't think it's possible unless you'd want to have a CSD that is an and-or kind of thing... "if an article meets any 6 of these 10 criteria...". I do see plenty of articles that fail just about everything, but don't fall neatly into a CSD. &mdash; Timneu22 · &#32; talk 15:13, 22 December 2010 (UTC)
 * Fram has now redirected it from How I Taught My Grandmother to Read and other Stories) to the article on the author, Sudha Murthy. Just conceivably the individual books are notable, but the obvious first step would be to expand the discussion of them in that article. After all, there are, alternative to deletion, such as this.  I would have done the same: first check if the author has an article, and then make the redirect. I possibly would have merged some of the material as a start on expansion, but anyone can do that as it has not been deleted.    DGG ( talk ) 00:45, 23 December 2010 (UTC)


 * It's one of the things that first irritated me about Wikipedia--not everything that's clearly not appropriate for the encyclopedia is speedyable. It's one of those pesky things like "due process" in criminal proceedings.  It gets in the way a lot of the time, but it's there to prevent people from being railroaded.  There should always be a set of "clearly junk" articles that don't meet the speedy criteria, just to make sure the speedy criteria aren't applied in a manner that trashes good content. Jclemens (talk) 01:13, 23 December 2010 (UTC)
 * Is that a vote in favor of my "6 out of 10 criteria" suggestion? &mdash; Timneu22 · &#32; talk 01:25, 23 December 2010 (UTC)
 * Unless you list your ten criteria it isn't really a proposal, but I'd be surprised if that approach either met the simplicity requirement for speedy deletion or would involve enough articles to be worthwhile.  Ϣere Spiel  Chequers  01:55, 23 December 2010 (UTC)
 * It's not something I've put much thought into. But it's a shame when everyone on here says "yeah, not encyclopedic", yet we're all handcuffed by the guidelines to permit the article's existence. If an article met a number of WP:NOT reasons, for example... &mdash; Timneu22 · &#32; talk 13:55, 23 December 2010 (UTC)
 * Ah but just because there is no applicable Speedy deletion criteria does not mean we are permitting an article's existence. Remember our primary deletion process is AFD not CSD, even if in practice there are more CSD deletions than AFD ones. If you think an article merits deletion but there is no relevant CSD criteria then Prod or AFD it. If you can formulate a clear simple test that would identify another significant group of articles that would always get deleted at AFD, then feel free to propose it here as a potential new CSD code.  Ϣere Spiel  Chequers  17:09, 23 December 2010 (UTC)
 * Exactly. If you can propose a new criterion that meets the requirements at the top of this page, by all means go ahead and do so. Coming here and bitching about every article yo find that can't be speedy deleted isn't going to accomplish anything. I'm quite certain this has been explained to you many times already. Beeblebrox (talk) 20:36, 23 December 2010 (UTC)
 * Beeble, I wasn't bitching about anything. Retract your comment. "About every article I find" is just bullshit. Retract your comment immediately. &mdash; Timneu22 · &#32; talk 21:06, 23 December 2010 (UTC)
 * Nope. How many times have you started a thread here about some article or other yu think you should be speedy deleted but can't be? How many months has this been going on? What has it accomplished? I stand by every word of that remark. Beeblebrox (talk) 22:56, 23 December 2010 (UTC)
 * The fuck you do. I make a few hundred patrols per week, and you said "every article I find." This is a lie, and I expect you to retract it. Further, we were having a pleasant conversation here, and my initial question was to see which speedy should apply to an article. After being told "none", I said, "well this seems like another good indicator for speedy userfication", and the conversation commenced. You just jumped in this thread to make inaccurate claims about my abilities as an editor. It's all false, false, false. You should be ashamed. &mdash; Timneu22 · &#32; talk 23:00, 23 December 2010 (UTC)
 * (ec) It seems like there are a lot more admins deleting tagged pages than there are people actually patrolling and tagging them (see the section started at the bottom). It's easy enough for the admin corps to handle the pages that are already tagged for CSD/PROD/AfD, but someone actually has to tag them; we have to make the decision what to do with it before the admins ever get there. Not to mention that given how few of us are actually out tagging things, it's a much bigger burden on us to monitor PRODs and set up/monitor AfDs. Whereas admins basically have to worry about it at the end of the 7 days, we get the pleasure of having to monitor all of them for the entire 7 days, even though it's a foregone conclusion. Timneu22 and I have both given suggestions before (A11, speedy userfication); in fact, Timneu22 mentioned speedy userfication already. Perhaps we should revive one or both of those discussions; implementing either one would significantly help. Yeah, I have to say it's annoying that we're mostly met with hand-wringing, but Timneu22 and I have now both suggested something. The Blade of the Northern Lights  ( 話して下さい ) 23:11, 23 December 2010 (UTC)


 * Ok Tim, whatever, you don't start a thread on every single article you see, it's just a figure of speech (as I would have thought was obvious) but fine I'll grant you that point. I have not attacked your abilities as an editor, I have questioned the wisdom of repeatedly complaining here about not being able to speedy delete certain things, and i continue to stand by that assertion. Anyway, what is so hard about watchlisting something for a week? I PROD or AFD something pretty much every week in addition to preforming dozens if not hundreds of admin actions, monitoring oversight emails at OTRS, working on the backlog of several thousand uncategorized articles, watching pages at Commons, currently drafting a Wikimania bid for 2012 on Meta, just started editing on Simple, and I have a job in the real world on top of that. If it's too much trouble for you to monitor a deletion nom then I suggest you stop working in deletion related areas. The suggestions you have made in the past did not gain support from the community, so what is up with blaming the admin corps for being unwilling to ignore consensus? That is exactly what we are supposed to do, and we don't get paid any more than you do for our trouble so I don't really appreciate the admin-bashing tone of this conversation. Show me where an article wasn't deleted that does in fact fall within one of the criteria and then you've got a valid complaint. Beeblebrox (talk) 23:27, 23 December 2010 (UTC)
 * I'm not trying to bash anyone, I'm just pointing out that PROD and AfD are two very different tasks for those with and without admin tools. If I didn't like doing this, I wouldn't; the problem is, we have a paucity of people doing what Timneu22 and I specialize in, and it can be frustrating at times.  Shit happens.  I don't have time to dig through and find everything, but one example that comes to mind is Hangry, which was a neologism sourced to a local website and Urbandictionary.com that got dragged through AfD.  What I was trying to say above (although it obviously wasn't clear) wasn't that it's too difficult, it's that we're trying to streamline it.  But again, I've suggested we revive a discussion; if you don't want to, just say as much.  And while I can't speak for Timneu22, what makes it hard for me to watchlist things for a week is that I have PDD-NOS, which among many other things severely hampers my organizational abilities; when I have tried to use it, I get so incredibly frustrated trying to keep it in order that I've decided it's not worth the emotional toll (which sounds funny until you see it for yourself), so I try to operate completely by memory.  It usually works, as my memory is extremely good, but it's not perfect. That's why I'd like to streamline it; it's not monitoring everything that gets me frustrated (see straw man), just this one group of articles that have foregone conclusions. The Blade of the Northern Lights  ( 話して下さい ) 23:42, 23 December 2010 (UTC)
 * OK, here's a gem I just came across; Lipocurean. I know Spanish Wikipedia's A3 is "articles consisting solely of OR"; that's essentially what this is. Does that seem feasible?  The Blade of the Northern Lights  ( 話して下さい ) 00:25, 24 December 2010 (UTC) That got IAR deleted; perhaps we should create said criteria to avoid that, if you're interested in working within consensus.
 * Could one guarantee though that it was only original research. Just thinking - I could write an article that looked exactly like it was only OR, but where there is actually a notable, if obscure, topic and sources that academics (or geeks, or dentists or something) would be aware of. Elen of the Roads (talk) 17:00, 1 January 2011 (UTC)

A10 "Recently created"
Rationale? Whereas 'Old' would show a higher probability that the article might not be improved. Anarchangel (talk) 14:18, 1 January 2011 (UTC)
 * Strictly speaking if an article is completely redundant there's little sense in keeping it around, but my intuition is that more "mature" articles that have been around longer and have more editors and more edits have a higher chance of containing some tidbit of useful information that can be merged into the other article. It may also indicate disagreement over the best name for the article, in which case a redirect and not deletion is called for. For these reason I think it's useful to have a deletion review. Dcoetzee 14:50, 1 January 2011 (UTC)
 * I agree with Dcoetzee. A10 is similar to R3 in that regard. The longer something exists, the higher the chance that deletion will not be uncontroversial. Regards  So Why  14:58, 1 January 2011 (UTC)

Question about speedy and BLPs
Could someone point me to past discussion of whether or not it should be possible to speedy unsourced BLPs if they are older than a certain amount of time? BE——Critical __Talk 05:27, 8 January 2011 (UTC)


 * See Wikipedia talk:Criteria for speedy deletion/blp. A more extensive discussion is at Wikipedia talk:Requests for comment/Biographies of living people, with what you are referring to at Wikipedia talk:Criteria for speedy deletion/Archive 37. As a result of these discussions, Proposed deletion of biographies of living people was created as a policy for those articles (instead of using speedy deletion, imho correctly). Regards  So Why  09:16, 8 January 2011 (UTC)


 * Hey, thanks :D BE——Critical __Talk 20:45, 8 January 2011 (UTC)

Unusual G7
At the moment User:NotAnonymous0 is coming up in Category:Candidates for speedy deletion by user - but I can find no trace of a CSD on that page (and it has not been changed since 9 October 2010 anyway). There are no other pages tagged G7 - so I cannot see that it's due to some transcluded template. It's a mystery...  Ron h jones (Talk) 17:02, 9 January 2011 (UTC)


 * I assume that someone tagged a userbox for deletion without using -tags and it was still cached. I guess the template in question was User:A930913/UVClub. Regards  So Why  17:17, 9 January 2011 (UTC)

Redirects from names of living people to articles where they are not discussed
I would like to get other opinions about whether the following situation falls under criteria R3 and/or G10, and if it doesn't, whether we should add or alter a criteria so it is.

If there is a redirect from the name of a living person, that does not contain any edit history not directly relevant to the redirect, to another article in which this person is not discussed, and where the association of that persons name with what is discussed at the target is a potential BLP issue.

To give a specific example, currently being discussed at Redirects for discussion/Log/2011 January 2 is a redirect to Julian_Assange from the name of one of the women who is making the allegations discussed in that section. There is consensus at the target article not to include the names of the accusers, so she is not discussed there. I believe that were her name mentioned in the article without any accompanying verification that explicitly mentions her that thsi would be a BLP issue; and as her name is not mentioned there there is no such source (as there is no need for one).

User:TeleComNasSprVen suggested that this might fall under criteria R3, but I don't think it does (it is not a typo, and if she were discussed in the article it would be a plausible redirect so it's not a misnomer either). I think G10 is a closer fit, but the purpose of the redirect isn't solely to attack or disparage the subject - as I said it would be a good redirect if she were discussed there (positively, negatively or neutrally), and you can't add sources to a redirect. Thryduulf (talk) 19:39, 9 January 2011 (UTC)

I should also add that where BLP issues are not involved, I do not see the need to speedy delete - WP:RFD works fine for these cases. Thryduulf (talk)


 * Good question. When it's blatant, such as redirecting "John Doe" to Pedophilia, I think we can use G10. In this case, the matter is more complex and even with BLP policy in mind, a discussion at WP:RFD, even when it's longer, should be preferred. The fact that redirects are less exposed to the common reader and that there is some plausibility to have one with that name are good reasons to allow a discussion. The RFD shows that there certainly is controversy over it, so speedy deletion would not be in anyone's best interest. Regards  So Why  19:47, 9 January 2011 (UTC)
 * Sorry, but I was referring to this criteria when I cited R3, not CSD. :| TelCo  NaSp  Ve :|  15:43, 10 January 2011 (UTC)
 * I think that that R3 you stated is intended for areas where G10 may apply, but it's likely that some admins will think otheerwise; or for borderline cases. At any rate, this list of criteria is for listing the redirects at RfD, not for speedy deleting them. עוד מישהו Od Mishehu 20:39, 10 January 2011 (UTC)

Slower G10 deletions?
Negative unsourced BLPs can be speedy deleted at present (G10). Attack bios obviously should immediately be. But sometimes it isn't so clear. For example, I came across this this article yesterday. Now, it was obviously unsourced and negative - and technically I could have deleted it immediately. But, it is also the case that the article was probably substantially factual, notable, and harmless. When I've been patrolling BLPs, I've often found similar cases with bios on old mafia bosses, or disgraced Fijian politicians - dozens in the last few weeks alone.

The difficult for someone patrolling is what to do. Tag it, and it will sit for another 4 years. I could research it myself, but if I don't choose to do that (and I don't usually like doing research), what else? Prodding isn't any use since BLPprod doesn't apply to older articles, and regular prods will get removed with "seems notable" -often with the thing still unsourced. I could send to AFD, but again, I'm not saying there shouldn't be an article here, merely that there can't be an unsourced one - and AFD does sometimes tragically keep something because it can be sourced, without actually sourcing it. (In this case, I raised the matter in IRC and invited interested editors to fix it, rather than me deleting it.)

What I'm wondering is whether admins ought to have another option. The option of saying "this needs sourced soon, or it must die" - and giving a short period of grace before speedy deletion. In that period, if any other admin judges the article harmful they can still kill it, but otherwise those who like to rescue such things get a short window (if they miss the window, it can still be undeleted later if someone wants to fix it.)

Currently, I tend to speedy such articles, and then undelete them if someone asks and offers to source them. However, that does tend to lead to friction, and doesn't allow non-admins to review. Some time ago, I put together Template:G10 delayed (indeed I forgot I created it until now) - just to see what this might look like.

This would NOT represent an expansion of the CSD - because all the applicable articles would already be speedy candidates. It would simply allow an admin to take the decision to slow down his speedy, in the hope of another solution, rather than deletion, being found. It would also not preclude attack articles being instantly nuked.

Thoughts?--Scott Mac 14:53, 11 January 2011 (UTC)


 * You raise a lot of interesting and meaningful concerns, and I am really happy that you are thinking about the substance of such articles instead of simply G10 them (which would be a completely understandable response). I tend to think that the best course of action would be to incubate them somewhere outside mainspace, noindexed, and then notifying them to some interested wikiproject (or even the, admittedly debated, ARS, which could help in rescuing these things and sorting them). Also on a personal note: I know we have our grudges, Scott Mac, but in the interests of the encyclopedia I'd be very happy if you can pop on my talk page and notice me of some of these articles -I'd be happy to source them if I can or put them to deletion if I can't find anything. -- Cycl o  pia  talk  15:05, 11 January 2011 (UTC)
 * This isn't just about me or you. So me putting them on your talkpage won't upscale. What I'm trying to do is to tweak current practice to find a place where negative unsourced BLPs (whose notability is generally not in question) can be fixed by those who want to - but are now allowed to hang about indefinitely in hope. The incubator idea is interesting, but we'll not get consensus for such ideals. We might get consensus for my small tweak. --Scott Mac 15:12, 11 January 2011 (UTC)
 * I know it wouldn't upscale, it was just raising a hand to help you now. It was, so to say, a deflamatory gesture in the name of common interest. But fine. The delayed G10 sounds interesting but I doubt it will be of real help if a mechanism to notify people interested in the potential sourcing (either by notifying wikiprojects or otherwise creating a "hub" where to deal with that) isn't also put. -- Cycl o  pia  talk  15:19, 11 January 2011 (UTC)
 * It could create a hub. It could add the articles to a special category, and a bot could generate a list for sorting. I don't imaging this tag would be applied very often or to very many articles. Even when I'm at the height of my searching, I'm only finding a few utterly unsourced negative bios per day - and some obviously need immediate deletion because they are scurrilous. But if you look through my talk page you'll find a steady stream of people saying "can you undelete this?" I always do if they are willing to source it, but it would be good to have a less heavy way to the same result = "either no article or a sourced one".--Scott Mac 15:27, 11 January 2011 (UTC)

Some recent examples of my G10 deletion (any of which I'm happy to undelete if someone is willing to source): Oreste Scalzone, Mickey Featherstone Virgilio R. Gonzalez.--Scott Mac 15:35, 11 January 2011 (UTC)
 * I'm just thinking out 'loud, but how about a system where the pages are blanked and editors are invited to draft a sourced version on the talkpage or a subpage thereof? After a period of time (2 days, a week, whatever), an admin reviews the new draft.  If it's good, they replace the blanked page with it. If it's no good, they delete the article.  -- Lear's Fool 15:07, 11 January 2011 (UTC)
 * Interesting, but won't get consensus. The current norm is to speedy negative unsourced articles. You'll not get that changed, but we might give admins a little leeway to be more creative.--Scott Mac 15:15, 11 January 2011 (UTC)
 * edit conflict to SlimVirgin, below Okay. I suppose my main concern with your proposal is having negative, unsourced BLPs still being indexed by search engines.   doesn't work in the mainspace, so the only way to prevent indexing would be to accompany your delayed G10 with a courtesy blanking, which means further improvements would have to be drafted elsewhere (the talkpage?).  What do you think about adding a courtesy blanking to your template, and a note inviting people to source the pre-blanked revision?  -- Lear's Fool 15:37, 11 January 2011 (UTC)
 * Yes, blanking is a good idea.--Scott Mac 15:38, 11 January 2011 (UTC)
 * The regular G10 template asks users to blank the page in a warning below the speedy box, we could use an appropriately modified version. Cenarium (talk) 20:03, 11 January 2011 (UTC)
 * I think this is an excellent idea, assuming the period of grace isn't too long. But it's certainly very fair, in that it gives people a reasonable chance to find sources. SlimVirgin  talk| contribs 15:32, 11 January 2011 (UTC)
 * I'd say 7 days MAXIMUM. But a list could be kept of any not sorted in that time, so people can offer to source them beyond the deadline.--Scott Mac 15:37, 11 January 2011 (UTC)
 * Mickey Featherstone had sources listed as "Further reading", and those sources do all refer to him as far as I can see from Google Books: Davis, John H. Mafia Dynasty: The Rise and Fall of the Gambino Crime Family. New York: HarperCollins, 1993, English, T.J. The Westies. St. Martin's Paperbacks, 1991. ISBN 0-312-92429-1, _____. Paddy Whacked: The Untold Story of the Irish American Gangster. New York: HarperCollins Publishers Inc., 2005. ISBN 0-06-059003-3, Mustaine, Gene. Murder Machine. Onyx Books, 1993. Scott, you really shouldn't be speedily deleting such articles. Fences  &amp;  Windows  19:58, 11 January 2011 (UTC)
 * I tend to think that permission to delete without review, a la G10, implies permission for an administrator to take any lesser action which might also solve the problem. Thus, I really don't think blanking should be off the table--it, along belongs alongside research/expansion, incubation/NOINDEXing, and other sub-deletion approaches as a valid way to handle such an article. Jclemens (talk) 15:38, 11 January 2011 (UTC)
 * I tend to agree with Jclemens. In the interests of consensus, I definitely prefer this to simple G10. One can also get a list of articles tagged by seeing what links to the template, which is nice and neat. I am happier again with mass deletions if we have a log somewhere of all the articles so far removed, so that any admin other than Scott or a TPS of Scott can take a look and undelete/userfy/email/whatever. Casliber (talk · contribs) 19:40, 11 January 2011 (UTC)
 * Can we not widen BLP PROD to include such BLPs, so long as they are stubbed? My experience of this kind of thing was Yoshinori Watanabe, about a Japanese yakuza boss - it was nominated for speedily deletion as an attack page, declined, then blanked, then deleted. I came across it because it was debated at ANI, hardly the optimum way to deal with such articles.  Fences  &amp;  Windows  19:49, 11 January 2011 (UTC)
 * Let me be clear. We are not talking about mass deletions - there are hopefully very few negative unsourced articles - or about controversial deletions. We are talking about articles that currently fall within the CSD - but can sometimes be fixed. All I'm saying is that things might be smoother if a reviewing admin has the option of slowing down his speedy deletion. Unless and until someone puts a valid reference on such a negative article, it would still remain eligible for speedy deletion. I'm happy with blanking, as long as it is understood that the blanking is a temporary measure, to allow some grace for fixing the article. I'd only be willing to use such a "delayed speedy" if the time allowed were less than 7 days. (I'm still willing to userfy or undelete for immediate sourcing beyond that time).--Scott Mac 19:57, 11 January 2011 (UTC)


 * I had suggested sometimes ago the option to delay a speedy, see Wikipedia talk:Criteria for speedy deletion/Archive 36, which generated support, but didn't follow up. I proposed it for G11, A1, A3 and A7, but it could certainly be extended to G10, possibly others. Technically, this can be implemented with an option delayed=yes, which changes the template wording and categorization (so no need for new templates). Generally speaking, users could delay a speedy if there is a reasonable possibility for the concerns qualifying the article for speedy deletion to be addressed, and doing so seems worthy (i.e. if it's a certain AFD-kill it's not worth it). Cenarium (talk) 20:03, 11 January 2011 (UTC)


 * I like the delayed-G10 template idea, and would some kind of small info box, perhaps on the BLP noticeboard, to give folks visibility to articles tagged with the template. Something simple, just listing the articles tagged, and perhaps (if it's possible to do with template coding) the date they'll be deleted. --InkSplotch (talk) 20:31, 11 January 2011 (UTC)


 * The specific case that sparked this is indeed an interesting object lesson in checking for sources, but there are varying degrees of attack pages, and this one is more the exception than the rule. The vast majority of attack pages I have deleted are just that, pages clearly written from a specific point of view to defame or insult a specific person. We don't want to open the door to keeping that sort of thing on-wiki for even one second. Blanking is not an acceptable alternative because anyone with even a passing understanding of WP can still see it in the page history. Don't get me wrong, I like this idea, but it needs some tweaking or it could be gamed to keep libel and other garbage on-wiki. What about RevDel? We could use that to remove the most negative information and inform the article creator that it can only be restored if they provide a source. Beeblebrox (talk) 22:38, 11 January 2011 (UTC)


 * Personally, I'd still delete most of the examples given here, but would want a noindexed list of redlinks created somewhere so people can work on recreating the articles if they want to do so. The redlink list would include the birth and death years and 'profession' and 'nationality' of the person in question (i.e. basic biographical metadata). Cases where the basic biographical metadata is not probably not worth spending time on if any sort of priority is applied to such a list. The system would intentionally not give people access to deleted revisions unless they asked, as it should be possible to write a new stub just from the basic biographical metadata (name, dates, country, profession) and available source. In many cases, the redlinks might already exist at name (disambiguation/set index) pages, but a central listing of redlinks would help, split by topic probably. This could be in addition to the slower G10 proposed above, if support can be found for that. Carcharoth (talk) 08:30, 12 January 2011 (UTC)
 * Very often, especially with Mafiosi and Pornstars the profession is itself negative. I'm loathe to keep such things longer than necessary. If the admin who finds them has any hesitation then its perfectly possible to tag rather than delete. I suggest that a better approach would be to come up with a gentler message to the author, I have done some very apologetic ones that have made it clear how to get there article restored if they can provide a reliable source.  Ϣere Spiel  Chequers  13:06, 12 January 2011 (UTC)

Commons image with hidden personal information
I'm attempting to find an admin to delete an image of photo identification that has been edited to blur out the subject, but the underlying layer is still visible in the image preview (.jpg keeps a record of the preview, but for some reason it isn't the same as the censored version). It's some kid's ID and I'd rather not broadcast it all over the place so how can I get in touch with an admin with access to commons? Thanks. 64.180.84.184 (talk) 03:40, 12 January 2011 (UTC)
 * You need to go here:. Actualy in this case emailing oversight-commons@lists.wikimedia.org might be a better idea. There's nothing we can do about it from over here.  Beeblebrox (talk) 04:16, 12 January 2011 (UTC)
 * Thanks I'll do that. 64.180.84.184 (talk) 06:49, 13 January 2011 (UTC)

How can we encourage more NPPers?
There are thousands of unpatrolled pages dating back to November 24. After a month, new pages are automatically marked as patrolled, and this makes it quite likely that articles will slip through the cracks. How can we encourage more people to be NPPers? &mdash; Timneu22 · &#32; talk 16:55, 23 December 2010 (UTC)
 * Don't know how to encourage editors to join in. But posting the link makes it easier for readers of you message to drop in a do a few.  Also, if this is a problem, should the 30 days be changed to 60 days? Vegaswikian (talk) 23:35, 23 December 2010 (UTC)
 * And in addition to those, there are the Article Wizard creations from January 2010 articles that need looking at. Vegaswikian (talk) 23:44, 23 December 2010 (UTC)
 * Maybe it would help to stick Special:NewPages in right above or below Special:RecentChanges on the sidebar. The Blade of the Northern Lights  ( 話して下さい ) 23:56, 23 December 2010 (UTC)
 * As I understand it, these pages aren't marked as patrolled after 30 days, but that they simply fall off Special:Newpages. Kudpung and WereSpielChequers are having a similar conversation at Wikipedia talk:New pages patrol, if anyone is interested.  -- Lear's Fool 22:24, 26 December 2010 (UTC)
 * Currently the flag of patrolled or not is only maintained for articles in their first 30days, and there are techy reasons not to extend that. We could continue it by getting a bot to add a hidden category to any such articles so they can be followed up and dealt with, but we'd need a bot writer..... On the broader issue of handling the flow of new articles better, one of my favourite ways is to identify potential new candidates for WP:Autopatrolled status so their subsequent articles don't go through NPP. I did a big trawl about a year ago and identified dozens of them, its probably time for another such trawl. But of course any newpage patroller can nominate candidates for AutoPatroller status.  Ϣere Spiel  Chequers  22:49, 26 December 2010 (UTC)

If pages are reaching the end of the NPP 'conveyor belt', it is because they are not being removed from the stream as fast as they are being replaced. Extending the length of time that they remain in the system (which equates to extending the duration of RecentChanges since the two are tracked through the same database structures) will merely hide the problem for 30 days, after which you will see exactly the same flow of pages into the ether; it will do nothing to address the fundamental issue which is, as Timneu says, that articles need to be removed from the system at a faster average rate than they are put in. Happy‑melon 23:53, 26 December 2010 (UTC)
 * The backlog has fluctuated in the past, and will doubtless fluctuate in the future. Keeping some sort of tag on the ones that currently fall off the end is one part of the solution, recruiting more patrollers is another. We have plenty of backlogs, I can think of no other where we automatically approve things at the end of the queue.  Ϣere Spiel  Chequers  14:02, 29 December 2010 (UTC)
 * (To WSC) i'm just thinking out loud here, but would it be worth a broader rethink of the autopatrolled userright? Currently it's quite tricky to get (I certainly wouldn't qualify), and I wonder whether reducing the requirements and allowing more autopatrolled editors would work. I'm not sure how far this would go to reducing the backlog, but it may be a good idea to bring the standards for autopatrolled more into line with those for rollbacker and reviewer regardless. Regarding the unpatrolled backlog, it may be worth getting the wikify WikiProject involved, as I imagine there's a lot of overlap. -- Lear's Fool mobile 02:15, 27 December 2010 (UTC)
 * I wouldn't qualify either if I wasn't an admin (or maybe I would - if I wasn't an admin our coverage of Magonids would probably now be rather more complete). Currently you need to have created 75 articles and shown that your new articles don't need to be patrolled by others, or you need to go through RFA and it is then awarded to you as part of the mop. I can't remember the last time we had a successful or even near successful RFA candidate who had any opposes for not yet being ready for autopatroller, so in theory we probably could lower the bar. But I'm convinced there will be loads of candidates out there who are quietly submitting an article a week and finding and appointing a bunch of them as autopatrollers would make a difference. A year ago I trawled for them manually and I suspect the hundred or so who I appointed then have subsequently contributed thousands of articles. But without a bot producing a list of article contributors it is very time consuming to do this. If we were to run such a bot and exhaust our prospect list then I guess we could lower the bar and look at candidates with fewer new articles created, but the gain would also be lower - someone who has created sixty articles in three years might only be contributing one or two articles a month. It takes much longer to check a candidate for Autopatroller status than it does to check one of their articles and mark it as patrolled, so it is only worth doing if someone creates lots of articles.  Ϣere  Spiel  Chequers  14:02, 29 December 2010 (UTC)
 * There is a fundamental problem in that there are plenty of pages which tell an editor "how to edit", and are often added as a welcome to their talk pages. For the more mundane matters, there is no "advert" - there's no "volunteers wanted" on the main page. Unless one is really curious or has made some bad edit, I would suspect there are lots of editors out there totally unaware of how they could possibly help Wikipedia. I drifted into vandal fighting as I was curious to find out what TW and HG stood for in an edit summary. The work of an NPPer is even more harder to observe.  Ron h jones (Talk) 00:09, 30 December 2010 (UTC)
 * I got into NPP because I was on recent changes and came across a new article tagged by CorenSearchBot. It took me a couple of weeks to even find Special:NewPages, so I was watching RecentChanges looking for new articles for a while.  I suspect that we'd get at least a few people by simply making NewPages more prominent.  As to the autopatroller right; we really need to make that easier, although I'll leave numbers up to those who are more experienced. I'll say this, though; the 1-2 articles a month doesn't sound like a lot, but when you multiply that by a few thousand it can make a difference. The Blade of the Northern Lights  ( 話して下さい ) 06:24, 30 December 2010 (UTC)
 * 75 articles!! Needs to be a lot less than that. Hell, I'd give it to people who have 1000 mainspace edits or who have previously created 5 articles without problems. Elen of the Roads (talk) 15:18, 31 December 2010 (UTC)
 * ^Strongly agree with this point. 75 articles is overkill by a longshot. Few users qualify for this, so the benefit is minimal. --Patar knight - chat/contributions 03:19, 1 January 2011 (UTC)
 * Have started discussion at Village_pump_(policy), see if anyone can remember why it was set to such a high number. If that doesn't turn up anything dramatic, someone could start an RfC at Wikipedia talk:Autopatrolled.Elen of the Roads (talk) 17:19, 1 January 2011 (UTC)


 * One thing I've wished for is a way to subdivide the list. If I could get a list that was automagically filtered to display (for example) medicine or military-related articles, then I think a couple of the big WikiProjects would be happy to do some subject-specific patrolling (perhaps leveraging the AlexNewArtBot).  But most of the stuff is pop culture, which I have basically no interest in.  I do trawl through the list on occasion just to see if there's anything that seems relevant, but it's primarily a sea of BLPs, with no way of knowing what might be what I'm looking for.  WhatamIdoing (talk) 19:54, 1 January 2011 (UTC)

Back to this topic briefly. I ran a Special:Newpage query that included 10,000 articles and searched for "band". I was able to nominate quite a number of awful band articles for AfD or CSD. And I was just looking for "band", because it's an easy thing to catch. I'm sure there's much more rubbish in the pile of 10,000 that isn't band-related. I see how this discussion turned into ways to automate the patrolling and such... I really think we just need more humans to go through the backlog. It's horrible how some articles can "make it" just because no one is on patrol. Can we get more humans? &mdash; Timneu22 &middot; &#32; talk 15:43, 13 January 2011 (UTC)
 * I remember doing that with him, and it was rather startling; I think the total I got was 56 CSDed garage bands, and about 10 more that we PRODded. The autopatrolled issue is a part of the problem, but we do need more people as well.  I can only think of a very few of us who regularly do NPP; maybe we can pull a few vandal fighters over, especially now that a certain user is back. We could also make some noise in high-profile areas, like the people handling unsourced BLPs have, and see where that gets us.  A few loud notes at the Village Pump might help. The Blade of the Northern Lights  ( 話して下さい ) 02:49, 14 January 2011 (UTC)

Give more people the ability to actually delete junk, rather than just slapping a template on. Friday (talk) 00:09, 15 January 2011 (UTC)
 * That'd be nice too; you have anyone in particular in mind? The Blade of the Northern Lights ( 話して下さい ) 00:14, 15 January 2011 (UTC)

Is a page filled with code patent nonsense?
I think this is patent nonsense. It's code, which isn't patent nonsense to me, but it's not at all prose, so is this patent nonsense?

function varargout = dsp_project(varargin) %DSP_PROJECT M-file for dsp_project.fig %     DSP_PROJECT, by itself, creates a new DSP_PROJECT or raises the existing %     singleton*. % %     H = DSP_PROJECT returns the handle to a new DSP_PROJECT or the handle to %      the existing singleton*. % %     DSP_PROJECT('Property','Value',...) creates a new DSP_PROJECT using the %     given property value pairs. Unrecognized properties are passed via %     varargin to dsp_project_OpeningFcn. This calling syntax produces a %     warning when there is an existing singleton*. % %     DSP_PROJECT('CALLBACK') and DSP_PROJECT('CALLBACK',hObject,...) call the %     local function named CALLBACK in DSP_PROJECT.M with the given input %     arguments. % %     *See GUI Options on GUIDE's Tools menu. Choose "GUI allows only one %     instance to run (singleton)". % % See also: GUIDE, GUIDATA, GUIHANDLES

% Edit the above text to modify the response to help dsp_project

% Last Modified by GUIDE v2.5 10-Jan-2011 02:23:48

% Begin initialization code - DO NOT EDIT gui_Singleton = 1; gui_State = struct('gui_Name',      mfilename, ...                   'gui_Singleton',  gui_Singleton, ...                   'gui_OpeningFcn', @dsp_project_OpeningFcn, ...                   'gui_OutputFcn',  @dsp_project_OutputFcn, ...                   'gui_LayoutFcn',  [], ...                   'gui_Callback',   []); if nargin && ischar(varargin{1}) gui_State.gui_Callback = str2func(varargin{1}); end

if nargout [varargout{1:nargout}] = gui_mainfcn(gui_State, varargin{:}); else gui_mainfcn(gui_State, varargin{:}); end % End initialization code - DO NOT EDIT

% --- Executes just before dsp_project is made visible. function dsp_project_OpeningFcn(hObject, eventdata, handles, varargin) % This function has no output args, see OutputFcn. % hObject   handle to figure % eventdata reserved - to be defined in a future version of MATLAB % handles   structure with handles and user data (see GUIDATA) % varargin  unrecognized PropertyName/PropertyValue pairs from the %           command line (see VARARGIN)

% Choose default command line output for dsp_project handles.output = hObject;

% Update handles structure guidata(hObject, handles);

% UIWAIT makes dsp_project wait for user response (see UIRESUME) % uiwait(handles.figure1);

% --- Outputs from this function are returned to the command line. function varargout = dsp_project_OutputFcn(hObject, eventdata, handles) % varargout cell array for returning output args (see VARARGOUT); % hObject   handle to figure % eventdata reserved - to be defined in a future version of MATLAB % handles   structure with handles and user data (see GUIDATA)

% Get default command line output from handles structure varargout{1} = handles.output;

function signl1_Callback(hObject, eventdata, handles) % hObject   handle to signl1 (see GCBO) % eventdata reserved - to be defined in a future version of MATLAB % handles   structure with handles and user data (see GUIDATA)

% Hints: get(hObject,'String') returns contents of signl1 as text %       str2double(get(hObject,'String')) returns contents of signl1 as a double

% --- Executes during object creation, after setting all properties. function signl1_CreateFcn(hObject, eventdata, handles) % hObject   handle to signl1 (see GCBO) % eventdata reserved - to be defined in a future version of MATLAB % handles   empty - handles not created until after all CreateFcns called

% Hint: edit controls usually have a white background on Windows. %      See ISPC and COMPUTER. if ispc && isequal(get(hObject,'BackgroundColor'), get(0,'defaultUicontrolBackgroundColor')) set(hObject,'BackgroundColor','white'); end

function lo1_Callback(hObject, eventdata, handles) % hObject   handle to lo1 (see GCBO) % eventdata reserved - to be defined in a future version of MATLAB % handles   structure with handles and user data (see GUIDATA)

% Hints: get(hObject,'String') returns contents of lo1 as text %       str2double(get(hObject,'String')) returns contents of lo1 as a double

% --- Executes during object creation, after setting all properties. function lo1_CreateFcn(hObject, eventdata, handles) % hObject   handle to lo1 (see GCBO) % eventdata reserved - to be defined in a future version of MATLAB % handles   empty - handles not created until after all CreateFcns called

% Hint: edit controls usually have a white background on Windows. %      See ISPC and COMPUTER. if ispc && isequal(get(hObject,'BackgroundColor'), get(0,'defaultUicontrolBackgroundColor')) set(hObject,'BackgroundColor','white'); end

function up1_Callback(hObject, eventdata, handles) % hObject   handle to up1 (see GCBO) % eventdata reserved - to be defined in a future version of MATLAB % handles   structure with handles and user data (see GUIDATA)

% Hints: get(hObject,'String') returns contents of up1 as text %       str2double(get(hObject,'String')) returns contents of up1 as a double

% --- Executes during object creation, after setting all properties. function up1_CreateFcn(hObject, eventdata, handles) % hObject   handle to up1 (see GCBO) % eventdata reserved - to be defined in a future version of MATLAB % handles   empty - handles not created until after all CreateFcns called

% Hint: edit controls usually have a white background on Windows. %      See ISPC and COMPUTER. if ispc && isequal(get(hObject,'BackgroundColor'), get(0,'defaultUicontrolBackgroundColor')) set(hObject,'BackgroundColor','white'); end

function signl2_Callback(hObject, eventdata, handles) % hObject   handle to signl2 (see GCBO) % eventdata reserved - to be defined in a future version of MATLAB % handles   structure with handles and user data (see GUIDATA)

% Hints: get(hObject,'String') returns contents of signl2 as text %       str2double(get(hObject,'String')) returns contents of signl2 as a double

% --- Executes during object creation, after setting all properties. function signl2_CreateFcn(hObject, eventdata, handles) % hObject   handle to signl2 (see GCBO) % eventdata reserved - to be defined in a future version of MATLAB % handles   empty - handles not created until after all CreateFcns called

% Hint: edit controls usually have a white background on Windows. %      See ISPC and COMPUTER. if ispc && isequal(get(hObject,'BackgroundColor'), get(0,'defaultUicontrolBackgroundColor')) set(hObject,'BackgroundColor','white'); end

function up2_Callback(hObject, eventdata, handles) % hObject   handle to up2 (see GCBO) % eventdata reserved - to be defined in a future version of MATLAB % handles   structure with handles and user data (see GUIDATA)

% Hints: get(hObject,'String') returns contents of up2 as text %       str2double(get(hObject,'String')) returns contents of up2 as a double

% --- Executes during object creation, after setting all properties. function up2_CreateFcn(hObject, eventdata, handles) % hObject   handle to up2 (see GCBO) % eventdata reserved - to be defined in a future version of MATLAB % handles   empty - handles not created until after all CreateFcns called

% Hint: edit controls usually have a white background on Windows. %      See ISPC and COMPUTER. if ispc && isequal(get(hObject,'BackgroundColor'), get(0,'defaultUicontrolBackgroundColor')) set(hObject,'BackgroundColor','white'); end

function lo2_Callback(hObject, eventdata, handles) % hObject   handle to lo2 (see GCBO) % eventdata reserved - to be defined in a future version of MATLAB % handles   structure with handles and user data (see GUIDATA)

% Hints: get(hObject,'String') returns contents of lo2 as text %       str2double(get(hObject,'String')) returns contents of lo2 as a double

% --- Executes during object creation, after setting all properties. function lo2_CreateFcn(hObject, eventdata, handles) % hObject   handle to lo2 (see GCBO) % eventdata reserved - to be defined in a future version of MATLAB % handles   empty - handles not created until after all CreateFcns called

% Hint: edit controls usually have a white background on Windows. %      See ISPC and COMPUTER. if ispc && isequal(get(hObject,'BackgroundColor'), get(0,'defaultUicontrolBackgroundColor')) set(hObject,'BackgroundColor','white'); end

function scl_Callback(hObject, eventdata, handles) % hObject   handle to scl (see GCBO) % eventdata reserved - to be defined in a future version of MATLAB % handles   structure with handles and user data (see GUIDATA)

% Hints: get(hObject,'String') returns contents of scl as text %       str2double(get(hObject,'String')) returns contents of scl as a double

% --- Executes during object creation, after setting all properties. function scl_CreateFcn(hObject, eventdata, handles) % hObject   handle to scl (see GCBO) % eventdata reserved - to be defined in a future version of MATLAB % handles   empty - handles not created until after all CreateFcns called

% Hint: edit controls usually have a white background on Windows. %      See ISPC and COMPUTER. if ispc && isequal(get(hObject,'BackgroundColor'), get(0,'defaultUicontrolBackgroundColor')) set(hObject,'BackgroundColor','white'); end

function shft1_Callback(hObject, eventdata, handles) % hObject   handle to shft1 (see GCBO) % eventdata reserved - to be defined in a future version of MATLAB % handles   structure with handles and user data (see GUIDATA)

% Hints: get(hObject,'String') returns contents of shft1 as text %       str2double(get(hObject,'String')) returns contents of shft1 as a double

% --- Executes during object creation, after setting all properties. function shft1_CreateFcn(hObject, eventdata, handles) % hObject   handle to shft1 (see GCBO) % eventdata reserved - to be defined in a future version of MATLAB % handles   empty - handles not created until after all CreateFcns called

% Hint: edit controls usually have a white background on Windows. %      See ISPC and COMPUTER. if ispc && isequal(get(hObject,'BackgroundColor'), get(0,'defaultUicontrolBackgroundColor')) set(hObject,'BackgroundColor','white'); end

% --- Executes on button press in sig1. function sig1_Callback(hObject, eventdata, handles) % hObject   handle to sig1 (see GCBO) % eventdata reserved - to be defined in a future version of MATLAB % handles   structure with handles and user data (see GUIDATA) string1=get(handles.signl1,'string'); %Get input as a String signal1=str2num(string1); %Convert string to num lower1=str2num(get(handles.lo1,'string')); % Get lower limit of first signal upper1=str2num(get(handles.up1,'string')); %Get upper limit of first signal axes(handles.axes1); cla; stem(lower1:upper1,signal1,'fo') title('First Signal') xlabel('n') ylabel('x1[n]') grid on

% --- Executes on button press in sig2. function sig2_Callback(hObject, eventdata, handles) % hObject   handle to sig2 (see GCBO) % eventdata reserved - to be defined in a future version of MATLAB % handles   structure with handles and user data (see GUIDATA) string2=get(handles.signl2,'string'); signal2=str2num(string2); lower2=str2num(get(handles.lo2,'string')); upper2=str2num(get(handles.up2,'string')); axes(handles.axes2); cla; stem(lower2:upper2,signal2,'fo') title('Second Signal') xlabel('n') ylabel('x2[n]') grid on % --- Executes on button press in add. function add_Callback(hObject, eventdata, handles) % hObject   handle to add (see GCBO) % eventdata reserved - to be defined in a future version of MATLAB % handles   structure with handles and user data (see GUIDATA) string1=get(handles.signl1,'string'); signal1=str2num(string1); lower1=str2num(get(handles.lo1,'string')); upper1=str2num(get(handles.up1,'string'));

string2=get(handles.signl2,'string'); signal2=str2num(string2); lower2=str2num(get(handles.lo2,'string')); upper2=str2num(get(handles.up2,'string')); n1=lower1:upper1; n2=lower2:upper2; n=min(min(n1),min(n2)):max(max(n1),max(n2)); y1=zeros(1,length(n)); y2=y1; y1(find((n>=min(n1))&(n<=max(n1))==1))=signal1; y2(find((n>=min(n2))&(n<=max(n2))==1))=signal2; sum=y1+y2; axes(handles.axes1); cla; stem(n,sum,'fo') title('x1[n]+x2[n]') xlabel('n') grid on

% --- Executes on button press in sub. function sub_Callback(hObject, eventdata, handles) % hObject   handle to sub (see GCBO) % eventdata reserved - to be defined in a future version of MATLAB % handles   structure with handles and user data (see GUIDATA) string1=get(handles.signl1,'string'); signal1=str2num(string1); lower1=str2num(get(handles.lo1,'string')); upper1=str2num(get(handles.up1,'string'));

string2=get(handles.signl2,'string'); signal2=str2num(string2); lower2=str2num(get(handles.lo2,'string')); upper2=str2num(get(handles.up2,'string')); n1=lower1:upper1; n2=lower2:upper2; n=min(min(n1),min(n2)):max(max(n1),max(n2)); y1=zeros(1,length(n)); y2=y1; y1(find((n>=min(n1))&(n<=max(n1))==1))=signal1; y2(find((n>=min(n2))&(n<=max(n2))==1))=signal2; diff=y1-y2; axes(handles.axes2); cla; stem(n,diff,'fo') title('x1[n]-x2[n]') xlabel('n') grid on % --- Executes on button press in scal. function scal_Callback(hObject, eventdata, handles) % hObject   handle to scal (see GCBO) % eventdata reserved - to be defined in a future version of MATLAB % handles   structure with handles and user data (see GUIDATA) signal1=str2num(get(handles.signl1,'string')); lower1=str2num(get(handles.lo1,'string')); upper1=str2num(get(handles.up1,'string')); scale=str2num(get(handles.scl,'string')); c1=0; for i=lower1:upper1; if (mod(i,scale)==0); c1=c1+1; d1(c1)=i/scale; y1(c1)=signal1(c1); else c1=c1+1; end end axes(handles.axes1) cla; stem(d1,y1,'fo') title('x1[a*n]') ylabel('n') grid on

% --- Executes on button press in shft. function shft_Callback(hObject, eventdata, handles) % hObject   handle to shft (see GCBO) % eventdata reserved - to be defined in a future version of MATLAB % handles   structure with handles and user data (see GUIDATA) string1=get(handles.signl1,'string'); signal1=str2num(string1); lower1=str2num(get(handles.lo1,'string')); upper1=str2num(get(handles.up1,'string')); shift=str2num(get(handles.shft1,'string')); n0=lower1:upper1; n=n0-shift; axes(handles.axes2); cla; stem(n,signal1,'fo'); title('x1[n-k]') ylabel('n') grid on

% --- Executes on button press in conv. function conv_Callback(hObject, eventdata, handles) % hObject   handle to conv (see GCBO) % eventdata reserved - to be defined in a future version of MATLAB % handles   structure with handles and user data (see GUIDATA)

string1=get(handles.signl1,'string'); signal1=str2num(string1); lower1=str2num(get(handles.lo1,'string')); upper1=str2num(get(handles.up1,'string')); string2=get(handles.signl2,'string'); signal2=str2num(string2); lower2=str2num(get(handles.lo2,'string')); upper2=str2num(get(handles.up2,'string')); lx=length(signal1); lh=length(signal2); l=lx+lh-1; u=l+lower1-1; n=lower1:1:u; y=conv(signal2,signal1); axes(handles.axes1); cla; stem(n,y,'fo') title('Y[n] = X[n]*H[n]') grid on function sampfreq_Callback(hObject, eventdata, handles) % hObject   handle to sampfreq (see GCBO) % eventdata reserved - to be defined in a future version of MATLAB % handles   structure with handles and user data (see GUIDATA)

% Hints: get(hObject,'String') returns contents of sampfreq as text %       str2double(get(hObject,'String')) returns contents of sampfreq as a double

% --- Executes during object creation, after setting all properties. function sampfreq_CreateFcn(hObject, eventdata, handles) % hObject   handle to sampfreq (see GCBO) % eventdata reserved - to be defined in a future version of MATLAB % handles   empty - handles not created until after all CreateFcns called

% Hint: edit controls usually have a white background on Windows. %      See ISPC and COMPUTER. if ispc && isequal(get(hObject,'BackgroundColor'), get(0,'defaultUicontrolBackgroundColor')) set(hObject,'BackgroundColor','white'); end

function noofsampls_Callback(hObject, eventdata, handles) % hObject   handle to noofsampls (see GCBO) % eventdata reserved - to be defined in a future version of MATLAB % handles   structure with handles and user data (see GUIDATA)

% Hints: get(hObject,'String') returns contents of noofsampls as text %       str2double(get(hObject,'String')) returns contents of noofsampls as a double

% --- Executes during object creation, after setting all properties. function noofsampls_CreateFcn(hObject, eventdata, handles) % hObject   handle to noofsampls (see GCBO) % eventdata reserved - to be defined in a future version of MATLAB % handles   empty - handles not created until after all CreateFcns called

% Hint: edit controls usually have a white background on Windows. %      See ISPC and COMPUTER. if ispc && isequal(get(hObject,'BackgroundColor'), get(0,'defaultUicontrolBackgroundColor')) set(hObject,'BackgroundColor','white'); end

function sigfreq_Callback(hObject, eventdata, handles) % hObject   handle to sigfreq (see GCBO) % eventdata reserved - to be defined in a future version of MATLAB % handles   structure with handles and user data (see GUIDATA)

% Hints: get(hObject,'String') returns contents of sigfreq as text %       str2double(get(hObject,'String')) returns contents of sigfreq as a double

% --- Executes during object creation, after setting all properties. function sigfreq_CreateFcn(hObject, eventdata, handles) % hObject   handle to sigfreq (see GCBO) % eventdata reserved - to be defined in a future version of MATLAB % handles   empty - handles not created until after all CreateFcns called

% Hint: edit controls usually have a white background on Windows. %      See ISPC and COMPUTER. if ispc && isequal(get(hObject,'BackgroundColor'), get(0,'defaultUicontrolBackgroundColor')) set(hObject,'BackgroundColor','white'); end

% --- Executes on button press in fftrad. function fftrad_Callback(hObject, eventdata, handles) % hObject   handle to fftrad (see GCBO) % eventdata reserved - to be defined in a future version of MATLAB % handles   structure with handles and user data (see GUIDATA) samp_no=str2num(get(handles.noofsampls,'string')); samp_freq=str2num(get(handles.sampfreq,'string')); sig_freq=str2num(get(handles.sigfreq,'string')); omega=2*pi*sig_freq; Samp_Tm=1/samp_freq; n=(0:samp_no-1)*Samp_Tm; signal1=eval(get(handles.signl1,'string')); %%IN RADIAN/SEC l=length(signal1); fftSize = 2^nextpow2(l); Norm_Fact= 1/fftSize; X = Norm_Fact*fft(signal1,fftSize); X = fftshift(X); magX = abs(X); angX = angle(X); omegaX = linspace(-pi, pi, fftSize);

% Create Mgnitude Spectrum. axes(handles.axes1) stem(omegaX, magX ); title('Spectrum of x[n]'); xlabel('Angular Freq (rad/sec)'); ylabel('Magnitude Spectrum'); grid on %Creates Phase Spectrum axes(handles.axes2) stem(omegaX, angX ); title('Spectrum of x[n]'); xlabel('Angular Freq (rad/sec)'); ylabel('Phase Spectrum'); grid on % --- Executes on button press in ffthz. function ffthz_Callback(hObject, eventdata, handles) % hObject   handle to ffthz (see GCBO) % eventdata reserved - to be defined in a future version of MATLAB % handles   structure with handles and user data (see GUIDATA) samp_no=str2num(get(handles.noofsampls,'string')); samp_freq=str2num(get(handles.sampfreq,'string')); sig_freq=str2num(get(handles.sigfreq,'string')); omega=2*pi*sig_freq; Samp_Tm=1/samp_freq; n=(0:samp_no-1)*Samp_Tm; signal1=eval(get(handles.signl1,'string')); %%IN RADIAN/SEC l=length(signal1); fftSize = 2^nextpow2(l); Norm_Fact= 1/fftSize; X = Norm_Fact*fft(signal1,fftSize); X = fftshift(X); magX = abs(X); angX = angle(X); freqX = linspace(-samp_freq/2, samp_freq/2, fftSize); % Creates Magnitude Spectrum axes(handles.axes1) stem(freqX, magX,'fo'); axis tight xlabel('Frequency (Hz)'); ylabel('Magnitude Spectrum'); title('Spectrum of x[n]'); grid on %Creates Phase Spectrum axes(handles.axes2) stem(freqX, angX,'fo'); axis tight xlabel('Frequency (Hz)'); ylabel('Phase Spectrum'); grid on

% --- Executes on button press in plzro. function plzro_Callback(hObject, eventdata, handles) % hObject   handle to plzro (see GCBO) % eventdata reserved - to be defined in a future version of MATLAB % handles   structure with handles and user data (see GUIDATA) num=str2num(get(handles.signl1,'string')); denum=str2num(get(handles.signl2,'string')); X=tf(num,denum,[],'variable','z^-1'); axes(handles.axes1); cla; Xp=pole(X); Xz=zero(X); zplane(Xz,Xp); grid on

% --- Executes on button press in impz. function impz_Callback(hObject, eventdata, handles) % hObject   handle to impz (see GCBO) % eventdata reserved - to be defined in a future version of MATLAB % handles   structure with handles and user data (see GUIDATA) num=str2num(get(handles.signl1,'string')); denum=str2num(get(handles.signl2,'string')); X=tf(num,denum,[],'variable','z^-1'); axes(handles.axes1); cla; [h1 t1]=impz(num,denum,10); stem(t1,h1,'fo'); grid on title('IMPULSE RESPONSE') xlable('Samples') ylabel('Amplitude') axis tight % --- Executes on button press in stpz. function stpz_Callback(hObject, eventdata, handles) % hObject   handle to stpz (see GCBO) % eventdata reserved - to be defined in a future version of MATLAB % handles   structure with handles and user data (see GUIDATA) num=str2num(get(handles.signl1,'string')); denum=str2num(get(handles.signl2,'string')); X=tf(num,denum,[],'variable','z^-1'); axes(handles.axes2); cla; [h2 t2]=stepz(num,denum,10); stem(t2,h2,'fo'); grid on title('STEP RESPONSE') xlable('Samples') ylabel('Amplitude') axis tight

% --- Executes on button press in zoomon. function zoomon_Callback(hObject, eventdata, handles) % hObject   handle to zoomon (see GCBO) % eventdata reserved - to be defined in a future version of MATLAB % handles   structure with handles and user data (see GUIDATA) zoom on

% --- Executes on button press in zoomof. function zoomof_Callback(hObject, eventdata, handles) % hObject   handle to zoomof (see GCBO) % eventdata reserved - to be defined in a future version of MATLAB % handles   structure with handles and user data (see GUIDATA) zoom off

% function file_Callback(hObject, eventdata, handles) % hObject   handle to file (see GCBO) % eventdata reserved - to be defined in a future version of MATLAB % handles   structure with handles and user data (see GUIDATA)

% function edit_Callback(hObject, eventdata, handles) % hObject   handle to edit (see GCBO) % eventdata reserved - to be defined in a future version of MATLAB % handles   structure with handles and user data (see GUIDATA)

% function help_Callback(hObject, eventdata, handles) % hObject   handle to help (see GCBO) % eventdata reserved - to be defined in a future version of MATLAB % handles   structure with handles and user data (see GUIDATA)

% function uipushtool6_ClickedCallback(hObject, eventdata, handles) % hObject   handle to uipushtool6 (see GCBO) % eventdata reserved - to be defined in a future version of MATLAB % handles   structure with handles and user data (see GUIDATA)

% function open_Callback(hObject, eventdata, handles) % hObject   handle to open (see GCBO) % eventdata reserved - to be defined in a future version of MATLAB % handles   structure with handles and user data (see GUIDATA) [filename, pathname] = uigetfile( ... {'*.m;*.fig;*.mat;*.mdl','MATLAB Files (*.m,*.fig,*.mat,*.mdl)';  '*.m',  'M-files (*.m)'; ...   '*.fig','Figures (*.fig)'; ...   '*.mat','MAT-files (*.mat)'; ...   '*.mdl','Models (*.mdl)'; ...   '*.*',  'All Files (*.*)'}, ...   'Open'); if isequal(filename,0) disp('User selected Cancel') else disp(['User selected', fullfile(pathname, filename)]) end

% function close_Callback(hObject, eventdata, handles) % hObject   handle to close (see GCBO) % eventdata reserved - to be defined in a future version of MATLAB % handles   structure with handles and user data (see GUIDATA)

% function save_Callback(hObject, eventdata, handles) % hObject   handle to save (see GCBO) % eventdata reserved - to be defined in a future version of MATLAB % handles   structure with handles and user data (see GUIDATA)

[filename, pathname, filterindex] = uiputfile( ... {'*.m;*.fig;*.mat;*.mdl','MATLAB Files (*.m,*.fig,*.mat,*.mdl)'; '*.m', 'M-files (*.m)';... '*.fig','Figures (*.fig)';... '*.mat','MAT-files (*.mat)';... '*.mdl','Models (*.mdl)';... '*.*', 'All Files (*.*)'},... 'Save as');

% function cut_Callback(hObject, eventdata, handles) % hObject   handle to cut (see GCBO) % eventdata reserved - to be defined in a future version of MATLAB % handles   structure with handles and user data (see GUIDATA)

% function copy_Callback(hObject, eventdata, handles) % hObject   handle to copy (see GCBO) % eventdata reserved - to be defined in a future version of MATLAB % handles   structure with handles and user data (see GUIDATA)

% function paste_Callback(hObject, eventdata, handles) % hObject   handle to paste (see GCBO) % eventdata reserved - to be defined in a future version of MATLAB % handles   structure with handles and user data (see GUIDATA)

% function selectall_Callback(hObject, eventdata, handles) % hObject   handle to selectall (see GCBO) % eventdata reserved - to be defined in a future version of MATLAB % handles   structure with handles and user data (see GUIDATA)

% function lwrlmt_Callback(hObject, eventdata, handles) % hObject   handle to lwrlmt (see GCBO) % eventdata reserved - to be defined in a future version of MATLAB % handles   structure with handles and user data (see GUIDATA) msgbox(' LOWER LIMIT ')

% function uprlmt_Callback(hObject, eventdata, handles) % hObject   handle to uprlmt (see GCBO) % eventdata reserved - to be defined in a future version of MATLAB % handles   structure with handles and user data (see GUIDATA)

% function x1_Callback(hObject, eventdata, handles) % hObject   handle to x1 (see GCBO) % eventdata reserved - to be defined in a future version of MATLAB % handles   structure with handles and user data (see GUIDATA)

% function num_Callback(hObject, eventdata, handles) % hObject   handle to num (see GCBO) % eventdata reserved - to be defined in a future version of MATLAB % handles   structure with handles and user data (see GUIDATA)

% function ft_Callback(hObject, eventdata, handles) % hObject   handle to ft (see GCBO) % eventdata reserved - to be defined in a future version of MATLAB % handles   structure with handles and user data (see GUIDATA)

% function x2_Callback(hObject, eventdata, handles) % hObject   handle to x2 (see GCBO) % eventdata reserved - to be defined in a future version of MATLAB % handles   structure with handles and user data (see GUIDATA)

% function hn_Callback(hObject, eventdata, handles) % hObject   handle to hn (see GCBO) % eventdata reserved - to be defined in a future version of MATLAB % handles   structure with handles and user data (see GUIDATA)

Discussion
Thoughts? &mdash; Timneu22 &middot; &#32; talk 15:26, 10 January 2011 (UTC)


 * Speedy delete as A1, unable to identify the subject, lack of context. Fram (talk) 15:36, 10 January 2011 (UTC)
 * Nope. Patent nonsense means it's incomprehensible, not non-encyclopedic. If anything, I'd say the speedy deletion criterion which most likely applies to this is G12--code is automagically copyrighted when written, and there's no copyright notice that I see on first glance, so I'd call it a likely copyvio. ec: I'd not call it A1, there's comments in the code. Jclemens (talk) 15:38, 10 January 2011 (UTC)
 * Well G1 worked, but I guess A1 is better. The title was DSP TOOL USING GRAPHICAL USER INTERFACE, so it was clear that the code was for whatever that is... but I guess "whatever that is" was unclear, so yeah, A1. &mdash; Timneu22 &middot; &#32; talk 15:43, 10 January 2011 (UTC)
 * Either of those, or A3. Code is not meaningful, substantive content. Beeblebrox (talk) 00:23, 11 January 2011 (UTC)
 * No, code is not G1, and is not G12 either unless a non-free copyrighted source is identified (many of the source code submissions to Wikipedia are in fact written by contributors). It is rather likely to be either A1 or A3, though, unless it contains explanatory comments. Dcoetzee 01:12, 11 January 2011 (UTC)
 * If if has explanatory comments comprehensible to anyone besides the programmer himself, it's likely to have been written by someone who was forced on pain of termination to write said comments, hence copyrighted. :-) Jclemens (talk) 03:06, 11 January 2011 (UTC)
 * G1 is not applicable. The content is coherent, though not in English.  A3 does not apply, because there is certainly plenty of (admittedly non-encyclopedic) content, and A3 is only for short articles, which that was clearly not.  A1 would demand that someone knowledgeable in the language in question couldn't understand what is going on.  And has been pointed out, G12 should probably be able to specifically identify the source.  So... I'm thinking it should have been PROD'ed.  Not everything that's clearly non-encyclopedic should be speedily deletable. Jclemens (talk) 03:11, 11 January 2011 (UTC)
 * In this case, I'd say it's so clearly non-encyclopedic that G13 (hopeless to the point no one would argue, get the hell rid of it) would apply. There's still no Office of Speedy Deletions to my knowledge. But could be PROD'ded, too. It's not actively harmful content, and one's not worse than the other. (Though one might want to direct the author to a site like Pastebin, as that may be what they're looking for anyway. In that case, removing it quickly would discourage the practice. (Off the topic, Jclemens, how do you get by without commenting? If I look at code I did six months or a year ago, it can take me some time to even figure out the details of what the hell -I- did, let alone to have someone else figure it. And besides that, explaining it in a clear form makes you think about what you're doing anyway. Comments are good!) Seraphimblade Talk to me 04:01, 11 January 2011 (UTC)
 * J, you say the content is coherent, just not in English. Gimme a break. That provision is intended for material in a foreign language, not computer codes. Let's not pretend the intent was to protect an article like this. The criterion was never intended to be wiki-lawyered in such a manner to protect an article that is not in any language spoken by actual human beings. I also don't see where it is specified that A3 is only for short articles. It is for articles with no substantive content. Like a bunch of computer code without any explanation of what it is. And let's not forget that we are allowed to use our own brains once in while to make a decision. I would have accepted IAR as a reason to delete something like this. Dumping code on us without explanation could only confuse our readers. I have been among those who have criticized Tim in the past for trying to stretch what CSD is for, but he's right on in this case. Beeblebrox (talk) 04:13, 11 January 2011 (UTC)
 * Seraphimblade, when I code (which is entirely uncommon--I don't think I've written anything more than a shell script in a decade or so) I write comments to help me remember what I did, not introduce someone else to the topic.
 * Beeblebrox, you've got it 100% backwards: Speedy criteria don't exist to "protect an article", they're a very limited set of things, defined by the community, which can be deleted without debate, fanfare, or even much in the way of notice. Using initiative to expand speedy definitions without consensus is improper, and while computer code may indeed be pointless and non-encyclopedic, it's hardly downright harmful.  PROD works fine in these cases.  It's not like a raft of code hanging around for a week is going to hurt anything. Jclemens (talk) 15:34, 11 January 2011 (UTC)
 * Yes, but the criteria are deliberately narrowly worded to protect articles from being deleted unnecessarily. I think your contention that computer code qualifies as a foreign language is deeply flawed and sets a precedent we don't want to set. If it's a foreign language, then how about you translate it into English for us so we can all understand it? That's what the prohibition against deleting article just because they are not in English is for. Any article that cannot be translated into English because it is not written in a language intended for use by human beings should not qualify for that protection and should qualify for speedy deletion. Wikipedia may be written on computers but it is meant to be consumed by people. Beeblebrox (talk) 22:27, 11 January 2011 (UTC)
 * Go read G1 again... Fanfic isn't G1'able. Bizarre conspiracy theories aren't G1'able.  Why should computer code be different? Jclemens (talk) 04:43, 12 January 2011 (UTC)
 * Because it is impossible to turn a bunch of code into an article. Fanfic can be read and understood in general terms even if a person is unfamiliar with the fictional universe it is based in. Conspiracy theories may be nonsensical from a logical standpoint but if the gist can be comprehended by the average person they do not qualify. Computer code is different in that it has no meaning in any language used by humans to communicate with humans. It's irredeemably incoherent and cannot be translated into something that can by understood in English. As I said, if that's not the case I'd be interested to see a translation of the code into English. Not an explanation of what it does or what it's for, if that had been included we could have just cut the code out and decided if what was left fit a CSD, but rather a translation of the code into comprehensible English. It's my contention that this cannot be done. Prove me wrong and I'll happily concede the point. Beeblebrox (talk) 06:15, 12 January 2011 (UTC)
 * Beeblebrox is largely correct. Computer code is a set of instructions, meant for a compiler or Interpreter (computing), not a description or explanation primarily for a human reader. Even where these code instructions can be translated into English, they would clearly be WP:NOTMANUAL, as well as most probably incomprehensible to anybody not intimately aware of the particular task they were created to perform -- and of no interest to anybody not wanting to perform that task. NotEnglish+InstructionManual+Incomprehensible+ExtremelyNarrowInterest = blatant SPEEDY in my book. It's not so much a matter of whether, but under which rule -- as it would appear to be under the overlapping penumbra of several. HrafnTalkStalk(P) 06:53, 12 January 2011 (UTC)


 * This seems to one of those times when we run the risk of tying ourselves in knots over technicalities of CSD. This to me screams WP:IAR; not encyclopedic, never going to be encyclopedic, shouldn't be here, so delete. Ged  UK  13:48, 14 January 2011 (UTC)
 * That's common sense. You'll find that common sense and IAR are hated by many of the hard-core admins here. Yesterday Life is the name of strive and struggle was written by a guy who said it was his own personal essay and that it was a place for people to add things about positive living (or something). No chance of ever beingencyclopedic, but an admin left me a message saying that it could not be CSD. So people can self-proclaim that I wrote this essay that is nonsense!! but admins would rather we follow procedures than use common sense. You're spot-on, Ged. &mdash; Timneu22 &middot; &#32; talk 15:30, 14 January 2011 (UTC)
 * You're all missing the point. Or rather, you're making points that are invalidated by the presence of other, non-speedy deletion processes.  In real life, I can't go out and find a murderer and bash his head in, but if I catch him in the act and that's the only way to stop him from killing someone right then and there, I can do so and it would be called justifiable homicide.  In much the same way, speedy deletion criteria are the limited, closely defined set of things where a single admin, with no notice or review, is allowed to summarily execute an article.  If any of you think computer code should be G1-able, then by all means start an RfC and seek community consensus to expand the speedy criterion definition; I wouldn't oppose such a proposal. But don't pretend that there's something wrong with IAR being insufficient grounds for a speedy: any remotely controversial speedy, any one that's contested in good faith by a single editor in good standing, goes to AfD instead, where things can be sorted out appropriately. (The exception being articles where real, ongoing harm is an issue) Jclemens (talk) 15:42, 14 January 2011 (UTC)


 * What about something that isn't remotely controversial? Like an essay that someone says is an essay, that isn't encyclopedic. The essay I'm talking about today is different than anything else I've brought up, because the user said he created the essay for people to comment on it! Use IAR here; there's no reason to leave such nonsense around! &mdash; Timneu22 &middot; &#32; talk 17:48, 14 January 2011 (UTC)
 * In the case of essays there are some that are suitable for moving to user space, some that should be in Wikipedia space and some that don't belong anywhere on Wikipedia. People have different opinions on what is suitable for essays in userspace (and sometimes this depends on the contribution history of the user in question) and what is suitable for essays in Wikipedia space. So unless the essay meets an existing speedy deletion criteria then it should go to AfD. IAR is never a suitable reason to delete something. Thryduulf (talk) 17:56, 14 January 2011 (UTC)


 * I would have to agree with Jclemens here. Mixing WP:SPEEDY with WP:IAR is a very bad combination. I would probably argue for its inclusion under G1 -- as (i) it is not meant to make linguistic sense to humans (ii) it is not covered by any of that criteria's exclusions. A bit of a stretch, but sufficiently relevant/analogous to pass muster for a non-controversial deletion. HrafnTalkStalk(P) 18:19, 14 January 2011 (UTC)
 * IAR doesn't say "If a rule prevents you from improving the encyclopedia, unless it has to do with CSD, ignore it", it says, "If a rule prevents you from improving the encyclopedia, ignore it". There are some times where IAR is the right thing to do, and this would seem to be one of these times, as it improves the encyclopedia by not having random computer code floating around.  If we were to let this go, someone might take the opportunity to post malware in code form that would sit around for 7 or more days.  CSD is not here to prevent people from using common sense, as you seem to be suggesting; I actually trust our admins' judgment when it comes to this matter. The Blade of the Northern Lights  ( 話して下さい ) 22:04, 14 January 2011 (UTC)
 * What's not said in IAR, but probably should be, is that given the amount of controversy an IAR decision can prompt, IAR is often an inappropriate choice because shortcutting existing processes can consume more time in drama than simply following the seemingly overly bureaucratic community processes would have consumed in the first place. IAR is more for "marching off the map" into unknown territory where no processes exist than for saying "the community processes take too long to do this". Thus, while I entirely agree that IAR can apply everywhere, there's rarely a good reason to use it instead of established process. Jclemens (talk) 22:18, 14 January 2011 (UTC)
 * And this would seem to fall under that category, unless someone can remember another time where a new article was entirely made up of computer code. If that has happened before (maybe it has, I've only been around since March 2010), that would be a starting point, but I certainly don't know of it. I also know that IAR can excite controversy; that's why this thread is still alive. The Blade of the Northern Lights  ( 話して下さい ) 22:31, 14 January 2011 (UTC)
 * WP:SPEEDY+WP:IAR=arbitrary article deletion at admin discretion -- not a good idea in my book. In fact, I'm not sure if I'd ever be in favour of a WP:IAR utilisation of admin tools. It would set a dangerous precedent. I would consider widening the interpretation of G1 to include information that is encoded (particularly when it is non-encyclopaedic even when decoded) is far less dangerous. HrafnTalkStalk(P) 03:39, 15 January 2011 (UTC)

Photos over 5 years old
I suggest that photos over 5 years old NOT be speedied for the following reasons: I'm not asking that the current rules not be enforced - only that some time be taken so that all the people involved can be properly contacted and participate in a non-speedy deletion discussion.
 * It's very likely that the rules on uploading photos have been changed since that time
 * It's very likely that editors other than the uploader have an interest in keeping the photos, and these editors may be difficult to find and inform
 * It's very likely that the original uploader will be difficult to contact
 * It's very unlikely that anybody is being hurt by copyright infringement - if the copyright holder hasn't contacted us in 5 years, he probably won't ever contact us.

Smallbones (talk) 17:06, 8 January 2011 (UTC)


 * If a photo meets any of the speedy criteria, it should be deleted regardless of how long it has been on Wikipedia. I think the only criterion for which that could be disputed is criterion F10 (useless media files), which is for files, including pictures, which have no foreseeable encyclopedic use. That's regardless of whether it is of any other use to anyone. However, an alternative to outright deletion would be to transfer the file to Commons if any of Wikipedia's sister projects could conceivably make use of the picture.


 * Often, unused pictures that old were uploaded to insert in an article that was itself speedy deleted, and I disagree with the assertion that someone other than the uploader might have some interest in keeping the picture. Should that be the case, it shouldn't be that hard to show that the picture does indeed pass the F10 criterion or is otherwise transferable to Commons. --  Blanchardb -Me•MyEars•MyMouth- timed 18:59, 8 January 2011 (UTC)


 * Again, I'm not saying don't delete them if they don't meet current criteria, I'm saying don't speedily delete them - just take the time to get proper input that may take longer to get in these cases.
 * After 5 years or so there are many people other than the uploader who may be interested in the photo. In my case, I try to make sure that lists of National Register of Historic Places listings are completely illustrated.  There are often over 100 listings in a county (up to about 600).  My specific problem involves "F4. Lack of licensing information. Media files that lack the necessary licensing information may be deleted after being identified as such for seven days if the information is not added. Be aware that editors sometimes specify their source in the upload summary."  Requirements for licensing information are likely to change over a period of 5 years.  I'd hate to think that every 5 years, I'll have to find new pictures for each site, essentially because 5 year old photos are going to be very easily deleted without any discussion effectively allowed.  Just slow down the deletion process, please, for this small subset of our files to allow proper input.  Smallbones (talk) 20:13, 8 January 2011 (UTC)
 * Five years, plus a week to fix the problem should be more than enough time. NRHP content already gets a free pass on WP:N, I don't see any compelling reason to give them a free pass on copyright policy as well. I also think it's unlikely the image use policy is going to radically change every five years. if somebody snaps a photo of a building and uploads it at Commons as a free image it should be fine permanently. Beeblebrox (talk) 22:18, 8 January 2011 (UTC)
 * Please take this request seriously, nobody is asking for a "free pass on copyright policy." All I'm saying is that if a photo has been in use for 5 years without any problem, it's rather extreme to have a procedure where it can be deleted speedily with the only notice going to the uploader. Why is there a rush to delete these without comment or calm consideration?  Example: on Jan. 31 files were listed for deletion and only the uploader was notified.  On Jan. 6 a bot commented out the photo in a NRHP list with a notice that the file could be deleted by Jan. 14.  I noticed it and asked the nominator to give me some time to see what was happening.  On Jan. 7 the photo was deleted.  What possible reason is there for this rush?
 * Most cases handled by speedy are for new articles that don't meet the basic requirements for being on Wikipedia. These photos have been around for 5 years and contributed to the encyclopedia during that time.  All I'm asking for is to have a reasonable chance to find out about the proposed deletion, comment on it, and check whether the problem can be rectified.  Smallbones (talk) 03:40, 9 January 2011 (UTC)
 * I see what you are saying here and completely agree. Where there is a known copyright infringement we are right to get rid of it as soon as we can. Where there is no suspicion that something is a copyright problem, only that there is a chance it isn't free because we don't know enough to be completely certain either way, then there is no harm (and possible benefit) in not being in such a hurry. As to what to do about it, perhaps we should add a requirement that the 7 day period does not start until messages have been left on both the uploader's talk page and the talk page of any page that uses the file. I'm tempted to suggest that any for any uploaded with no edits in the past year that a human is required to see if there are any other contact details (e.g. links to other project's talk pages, email addresses, etc) and attempt to make contact via any method as well. 19:14, 9 January 2011 (UTC)
 * There is a push to get the lack of licensing fixed at the moment, see User:MGA73/No license. The problem is not jsut for over 5 year old pictures, but more recent stuff too.  Even if the photo is speedy deleted, if a license or evidence is forthcoming the picture can come back on line.  I can assist if this is required, or you can use WP:REFUND. Graeme Bartlett (talk) 21:18, 9 January 2011 (UTC)
 * Thanks for the information and for concentrating on the basic issue - speedy vs. non-speedy. Now I know at least where to look for these soon-to-be deleted files, which has sub-cats by dates and appears to be semi-hidden.  I understand that there are a lot of improperly uploaded files - maybe 70 in the January 9 sub-cat - and something needs to be done.  I'd say ones that have been uploaded in the past year almost have to a pretty strict culling process.  But in the January 9 list, I browsed through 8-10 proposed speedy deletions of photo that looked old or interesting, finding only 3 or so that were over 18 months old.  One was uploaded by a user who says he is in the top 400 editors by number of edits.  He forgot to put a copyright notice on the file when he uploaded it, but did put in the information that he took the picture himself.  This tells me that even an experienced editor can have a couple of oversights now and then.  Interestingly, when notified he did add the copyright permission, but forgot to take off the "This file has no copyright information" tag.  So who knows whether it would have been deleted or not?  (I took that tag off).  Another older file File:Raffles Lighthouse.jpg was quite interesting.  The original uploader did everything right, but another editor uploaded a non-free image over it, and changed the copyright permission. (I reverted to the original).  Would this have been caught in a regular speedy process?  Another obviously inexperienced editor just filled in the form sparsly on a fair use image- that looked pretty straightforward to me to fill in a few obvious details. So based on a very small sample - I'd say that there are not that many photos here that are even 2 years old and being careful with them won't hold up the process.  And older photos are affected by quirks that I never would have even imagined.  Why not just say that photos over 2 years old cannot be speedied, or at least add a requirement that timely notifications be put on the article talk pages where the photo appears?  Smallbones (talk) 05:43, 10 January 2011 (UTC)
 * I think the simplest short-term measure would be to simply require that for all photos nominated under this category, the seven-day period does not start until notices have been placed on both the uploader's talk page and the talk page of any page that includes them. This should be easily doable by bot, and if so done, should delay the process by only a few seconds for those images that should really be deleted (thus not affecting the legal issues at all), while providing more time for cases such as those Smallbones identifies in the original message. If after a few months this hasn't fixed the problem, then we can look at more complicated ways of solving the problem, hopefully with more data to work with. Thryduulf (talk) 15:31, 11 January 2011 (UTC)
 * So the new wording should read as follows?

"F4. Lack of licensing information. Media files that lack the necessary licensing information may be deleted after being identified as such for seven days after the uploader and the talk pages where the file appears are notified if the information is not added. Be aware that editors sometimes specify their source in the upload summary."

The text in bold being the new wording; it wouldn't be bold on the CSD page. Does everybody agree? Shorter or simpler variants would almost certainly be acceptable to me. Smallbones (talk) 22:08, 11 January 2011 (UTC)
 * This sort of thing has come up in the past, and the general consensus was that multiple notifications would be nice but could not be mandated. In fact, even notifying an uploader or article creator is not actually required by policy. It's something that everyone should do of course, but it has never gained a consensus as a absolute requirement. I know I have seen it in the past that when an image is tagged for CSD a notification is placed right under it on any page it is used on. If we could automate that process there would be no need to try and require mass notifications. If I recall correctly, the main objection in the past to such requirements was that if an item was that important to you you should have it on your watchlist. That's why we have them after all. Beeblebrox (talk) 22:20, 11 January 2011 (UTC)
 * So a photo that's been around for awhile, where somebody has over-written the properly entered copyright info (see File:Raffles Lighthouse.jpg as explained above) can simply be "disappeared" without telling anybody?  If this is the sense of this provision, then I'd guess 90% of Wikipedians would say you are over-stepping here.  Smallbones (talk) 22:30, 11 January 2011 (UTC)
 * Why can't notifications be mandated? They are for other types of deletion - if we create the relevant templates (which probably already exist) it's only 1 edit for the uploader's talk, and 1 edit per page the file appears on - edits that could easily be done by bot. Thryduulf (talk) 02:19, 12 January 2011 (UTC)
 * 5 days and no responses as to why notifications cannot be mandated. Am I then to presume that there is no reason we can't implement this way to improve the deletion process? Thryduulf (talk) 12:53, 17 January 2011 (UTC)


 * Not saying that automatic notification is bad but have we any evidence that editors dont notify when they add Template:Di-no license as it is part of the instructions. It only really needs to automated if we have evidence that editors are ignoring the instruction. MilborneOne (talk) 13:10, 17 January 2011 (UTC)
 * Instructions are only to notify the uploader, not the talk pages of the articles that use the photo. Smallbones (talk) 14:10, 17 January 2011 (UTC)


 * I don't know, but the problem that this is trying to address is that interested editors aren't getting to find out about images that might be deleted in time to do anything about it. This is why the suggestion is to require notification on the talk pages of pages that use the file as well as the uploader's talk page. Say that file:Example.jpg was being marked for deletion because it wasn't explicitly released under a free license according to current standards. Currently, only the uploader (user:example) would be notified, but if that user has retired then it is not unlikely that the editors at Example, where the image was used, would not have their talk page on their watchlists. As such the first they might know about the file being marked for deletion is a bot removing the image after it has been deleted.
 * Under this proposal, the file would not be deleted until 7 days after notifications had been placed at user talk:Example and Talk:Example. Thryduulf (talk) 13:59, 17 January 2011 (UTC)
 * Still confused Template:Di-no license says that the uploader should be notified and the article use tagged with a deletable caption. So I am confused that you think the editors with the article on the watchlist would not see the deletion caption being added. MilborneOne (talk) 19:29, 17 January 2011 (UTC)
 * If it were reliably used then yes they should, but in practice the addition of "deletable caption" is not consistent and when it is added is frequently done several days after the image was tagged. As it currently stands the deletion period starts with the image tagging, not the notifications (which should be given, but are not required to be given, so deletions can happen even if they aren't). This change would mandate the notifications and the deletion countdown would not begin until they are. So it would give a guaranteed 7-day period after being notified rather than the current somewhere up to 7 days but sometimes none. Thryduulf (talk) 22:09, 17 January 2011 (UTC)
 * Just seems strange that you would tag it days later, normally you add the template and do the uploader notice and add the captions. Not sure why anybody would come back to it days later. Have we any stats that people go back days later to add them, most people would just do the job then move on. Sorry to go on but I am still not convinced we have a problem. MilborneOne (talk) 22:25, 17 January 2011 (UTC)
 * I don't know that anybody collates stats on this sort of thing, but it's sometimes a bot or another user that adds a delayed tag. See the very start of this thread for details of the problem. Thryduulf (talk) 23:45, 17 January 2011 (UTC)
 * OK - I dont agree that it is a problem, if it is a copyright issue it does not matter how long since it has been uploaded. If the image doesnt meet the copyright rules then it will go, giving a longer notice is unlikely to help and the suggestion to wait until the last notification is unlikely to delay the deletion by more than a few days. If a user is really miffed about an image dissapearing then they can take it to a deletion review. But I do agree and would support a case for automating the notification process, but I dont think that would require a change in the text here. I will leave it to others to comment now, thanks. MilborneOne (talk) 00:08, 18 January 2011 (UTC)

Since you asked for stats, I went and checked out a small sample. For the first 10 files on the page "Category:Wikipedia files with unknown copyright status as of 12 January 2011" (date chosen to see how long it takes to notify) that had been included in at least one article
 * 8 files did NOT have notifications in the articles
 * 2 files did have notification in the articles


 * 10 articles with the above photos were NOT notified
 * 2 articles with the above photos were notified - and none were notified late.

Obviously a small sample, but equally obvious that non-notification is much more common that notification. As far as getting the photos reinstated after they have been deleted - that is incredibly hard. But correcting them while the upload info is available, I'd guess about 4 could have been rectified if somebody bothered to inform the uploaders a few basics, rather than biting the newbies. For the very few older files (over 2 years old) that I've seen, I'd guess 80-90% of the problems could be rectified, if the uploaders were still available. Smallbones (talk) 05:11, 18 January 2011 (UTC)


 * Point of order: F10 applies only to non-media files. Stifle (talk) 10:07, 14 January 2011 (UTC)

Mandatory notification for deletion of files
So we have evidence there is a problem (interested editors not finding out about files that may be speedily deleted before they're deleted), and a suggestion for how to solve this problem (require notifications to uploader's user talk, and page talk of pages that use file; start 7 day period only when these notifications have been made). How can we move forward to implement a solution, either this proposal or a better one (not that any have been made)? Thryduulf (talk) 01:02, 22 January 2011 (UTC)

hoaxes and BLPs
I know hoaxes have been discussed, and it's always been decided to not speedy them if they're not blatant. But, wouldn't it make sense to say a BLP that's unsourced, that may be a hoax, should be speedied on sight, since any hoax would expose the subject to ridicule, even if the claims are positive, and even they (the subject) were the author of it. I use this model's bio as an example, which could be embarrassing to the subject, if people thought she was making these claims about herself. Keeping the article around a few days, and having an AFD (which remains visible), just invites people to use Wikipedia to make up plausable false claims about a person, just for kicks. --Rob (talk) 20:20, 21 January 2011 (UTC)


 * I don't see any reason to do so. There is consensus against speedy deleting unsourced BLPs and there is consensus against speedy deleting non-blatant hoaxes. So why should there be consensus for the combination of both? If the claims are not clearly a hoax, then there is no reason to treat them like a hoax. Both AFD and WP:BLPPROD were designed to handle such cases after all. Anything might expose any subject to ridicule by third-parties, even sourced facts. But while a person's life and the effects of a Wikipedia article on it are acceptable reasons for deletion in certain cases, I don't see a reason why it has to be handled by speedy deletion. Potential misuse by other people is not a valid reason for deletion after all. Otherwise we would have to delete quite a lot of material (just think about pornography-related pictures that might seriously offend some people but are still encyclopedic). If material is purely negative and unsourced, we have G10. If it's clearly a hoax, we have G3. If there is no indication of importance or significance, we have A7. But for the rest, we should always give the creator the benefit of doubt and allow some time to decide about them. Regards  So Why  22:27, 21 January 2011 (UTC)

There are gradations between speedy and 10 days on AFD. I'd suggest poping a fairly obvious hoax on the BLPNB, where a few people can review it. If it's obvious, someone may well ignore the rules and speedy it after a bit of discussion.--Scott Mac 22:50, 21 January 2011 (UTC)
 * Generally, SoWhy's position pretty much mirrors my position on Speedies, but here I think we differ... but WP:BLP already covers this, "Contentious material about living persons that is unsourced or poorly sourced—whether the material is negative, positive, neutral, or just questionable—should be removed immediately and without waiting for discussion"--- Balloonman  NO! I'm Spartacus! 22:53, 21 January 2011 (UTC)
 * Balloonman has hit the nail on the head here. If you remove all unsourced or poorly-sourced contentious information from a BLP, and there is no content left, then you can speedy it under A3. Typically though, at least a stub will remain (e.g. "Jane Doe is an actress.") While A3 does not usually apply if there is a more substantive version in the history, I think it should if reverting is not an option. Dcoetzee 01:06, 22 January 2011 (UTC)

"Useless" templates and the G2 criterion
I have been going through a lot of old, orphaned templates lately, and I often find ones that contain no more than a few words, or a single link. Here's an example: Hovet. It contains a piped link only: Hovet No documentation (even in edit summaries), it's totally orphaned (not even any incoming links except from lists of orphaned templates), it's been sitting around for awhile (i.e. it's been given a chance at life, which it hasn't taken), and it has no scope for future use. (In this specific case, the template was used briefly in the article 2009–10 Elitserien season, but then it was removed. The creator,, no doubt created it in good faith, and not as a test.)

I've been nominating these for G2, and admins have been deleting them. But they're not really "test pages". The wording of G2 doesn't say exactly what a "test page" is; it provides no guidance at all. Twinkle's popup tip uses the example "Can I really create a page here?" The kind of template I refer to here is not similar to that stereotypical "test" by any stretch - often, they appear to have been created in good faith, but they aren't serving any purpose and won't serve any purpose in the future.

Here are a couple more examples: Hulk & Joseph 10 (which contained the name of the template, before an IP changed the contents to "Template:Hulk"), and Imbucent succession box (which contains some parameters for something). Same arguments apply to both: no documentation, totally orphaned, both old (2009 and 2007 respectively), and no scope for future use. Again, I would have nominated these for G2.

A third kind: templates that contains only the name of the template, like Important Buildings. They would be an obvious candidate for A1 as articles, but for templates all we are left with is, again, G2. (This is maybe a clearer use of G2 than with the others I mentioned before.)

My concern with G2 is that its name "Test pages" doesn't reflect the contents of these pages. They are not necessarily tests - there may once have been a use for them. But they are long forgotten, and won't be used again. Seeing "test page" in the deletion log does not help a creator or contributor to understand why the deletion took place - the template was not a "test" in their mind, it was a good-faith contribution (albeit a useless one in the long run). Do we need a new criterion? Or do we need to explicitly word G2 (or some other criterion) so this kind of thing falls under it? — This, that, and the other (talk) 09:45, 25 January 2011 (UTC)


 * I'd rather go with G6 or G8. If they are completely unused for a long time, then removing them is just cleanup and as such probably always unproblematic. If they are unused because the page that used them was removed, G8 applies. In the first example you cite, T3 probably applies (not directly but its spirit), since it's a hardcoded instance of a link that can be created dynamically by the software. If those don't apply, I would use WP:TFD though, unless it's obviously created as a test. If they exist for such a long time, then there is no harm in keeping them a little longer. Regards  So Why  10:25, 25 January 2011 (UTC)

What is "speedy"
I noticed an article that had been marked for speedy deletion a month ago, and I spent a few minutes checking. It is very short, cut and paste from a promotional website, contains just 3 references which are blind, states qualifications that I could not verify, and irrelevant name dropping puffery. I list these concerns in the Discussion. Do articles actually get deleted if they are not actionable? Michael P. Barnett (talk) 11:35, 25 January 2011 (UTC)
 * If is totally cut and pasted from a website it would probably qualify for deletion under criterion G12 (copyright infringement).  Them From  Space  11:45, 25 January 2011 (UTC)
 * Are you sure it's correctly marked for speedy deletion? Right now there are no articles older than two days in the speedy queue. Thparkth (talk) 12:10, 25 January 2011 (UTC)
 * The article is Paul Karslake I assumed the article was marked for deletion because, on my PC, I see "Paul Karslake FRSA This file is a candidate for speedy deletion. It may be deleted after Friday, December 17, 2010." in red, below the hat-notes (I think this is the correct term). I put in the four of these that are marked with a ! (exclamation). The fifth, that is marked with a ? on an open book was there already. I should explain this is remote from my interests -- I registered to edit WP articles to provide verified information on technical topics from 50+ years ago, started to practice on articles about places where I have lived, and this led me to Karslake article when searching web for material for Leigh-on-Sea. I have been putting a lot of effort into WP because I think so many articles are good, and the method of working is essential to many situations, but I am alarmed by the amount that is not good that seems irremediable. When I encountered an article that was actually marked for deletion (or appeared to be) I thought it could be salutary to see whether this really occurred. Hope I am not out of order in raising this question. Michael P. Barnett (talk) 13:39, 25 January 2011 (UTC)
 * I see what you're referring to - the message about speedy deletion refers to an image that was previously used in the article. It looks like it was deleted on copyright grounds. I'll remove the now-useless message in the Karslake article itself. Thparkth (talk) 13:52, 25 January 2011 (UTC)
 * Thanks. I am reassured that "marked for speedy deletion" is not ignored. That leaves open the question of whether articles that are as bad (and in violation of WP guidelines) as I think this is can remain. I am particularly bothered by the contrast between tolerance of what I think blatant violation of WP guidelines in an article like this, and the hair splitting wiki legalisms that make writing good faith material that seems to conform to common sense interpretations of guidelines an invitation to wiki-legalistic arguments that preempt time that could be spent on substantive contributions. Are there processes that review the kinds of criticisms I posted?. Michael P. Barnett (talk) 14:16, 25 January 2011 (UTC)
 * Certainly it will remain as-is, unless someone is motivated to improve it, or if it can't be improved, to nominate it for deletion. The article isn't an obvious candidate for speedy deletion though. Thparkth (talk) 14:54, 25 January 2011 (UTC)
 * Thanks. I have a more general question that I think can be posed as a follow up to this exchange. I do not want to nominate any article for deletion, only to warn readers when I think an article is seriously flawed. Of the 80 articles to which I have made changes (several of these minute and / or non-controversial), I think errors in less than 10 merit hatnotes. For some of these, I would need to construct new templates, to display "an Editor thinks that this article departs from mainstream usage of the term ... see Discussion" or "an Editor thinks this article deals with only a few of the topics that are covered by standard monographs with the same title -- see Discussion". Is putting hatnotes on 10% of the articles that a contributor edits wiki-"bad form" or exceptional. The articles are on topics I used for initial self-education and then substantive work, and in a few cases, that my wife and consulted for ephemeral reasons. I am trying to extricate myself from all articles except those of close personal interest to which I think I can make a useful contribution. I have draft information for other articles that I do not have time to research adequately. I am putting these in Discussion pages, for other people to follow up on, if anyone thinks this beneficial. I realize I am straying from the deletion issue, but this question is so close to what is in this paragraph already, I hope it is ok for me to ask for a referral to where I can find if a template stating "more information in Discussion" is permissible and, if so, how to find if it exists already. I have a morass of template material already, and think there may be a lot more. Also, related (I hope not obviously) how to alert appropriate Wikipedians to a possible harmful practice based on a principle I described in an invited talk to a reputable professional meeting some years ago, that has been published conventionally. Michael P. Barnett (talk) 18:19, 25 January 2011 (UTC)
 * Well, for the second template you mention, you could use : "This article is weighted too heavily toward only one aspect of its subject." The first one doesn't seem to exist as you mention it; is as close as I can find. These boxes that are placed at the top of articles are not "hatnotes", they are known as "cleanup templates" or "maintenance templates" (or even sometimes "amboxes"). Placing them on 10% of articles is probably not a concern, particularly if the articles are less developed (shorter) or poorly constructed. Still, this is all off-topic for WT:CSD. Let's end the discussion or carry it on elsewhere. — This, that, and the other (talk)  10:30, 26 January 2011 (UTC)

Link WP:BEFORE
Lead section, 4th paragraph down, 2nd sentence: "Before nominating a page..." <-- Would a link to WP:BEFORE be appropriate/helpful here? Or will that possibly confuse people? -- &oelig; &trade; 22:22, 24 January 2011 (UTC)
 * I'd still like to create a "BEFORE creating an article..." page, myself. I've never much cared for the hideously overused WP:BEFORE. "BEFORE creating an article, ensure that you have found adequate source material in order to ensure that the subject of your article passes the notability requirements, and that the article adheres to all other content policies. If not..." Seraphimblade Talk to me 05:12, 25 January 2011 (UTC)
 * I'd kind of rather you not do that. In addition to being more related to AFD than CSD, BEFORE is being used more and more as a blunt object to accuse users of acting in bad faith. That's something I'm not keen to encourage. Beeblebrox (talk) 04:57, 26 January 2011 (UTC)
 * FWIW, I agree with this. Speedy deletion should be based on what's currently in the article and/or can easily be deduced from what's in the article.  It is intentionally a lightweight process, and should not be overly burdened with the requirements of BEFORE. Jclemens (talk) 22:03, 31 January 2011 (UTC)

A7 claim of significance must be in article text (vs only on cited source)?
Another editor objected to my tagging an article as A7, because (he said ) even though the article text itself gave no claim of signficance (simply said Company X exists, does Y, has N employees ) a claim of signficance exists in one of the sources cited in the article. I say that the text of A7 -- ''An article ... that does not indicate why its subject is important or significant. This is distinct from verifiability and reliability of sources, and is a lower standard than notability. ... 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... (my bolding) -- strongly implies that the claim of significance has to be visible in the text of the article, so one need not rummage around in the sources to find even one reason the topic might'' be notable. In particular, since A7 provides that it "does not apply ... even if the claim is not supported by a reliable source" the implication is that the required claim must exist whether or not any source exists i.e. it needs to be in the article. It seems to me A7 has little value if one has to look through all the sources to see what might be there, when the originator of the article couldn't be bothered to mention even a bare minimum of one qualifying claim of significance. Thoughts? EEng (talk) 21:29, 27 January 2011 (UTC)
 * FWIW I agree with you. – ukexpat (talk) 21:52, 27 January 2011 (UTC)
 * Opinions will vary, and the wording isn't clear on this, but I would consider it inappropriate to speedily delete an article where you know there is a credible claim of significance regarding the topic, even if is not explicitly present in the article text. Thparkth (talk) 22:37, 27 January 2011 (UTC)

Well of course, if I knew such a claim was in one of the sources, I'd just add it to the article and the problem would be resolved. And I agree the wording isn't clear. I'm trying to see if we can decide on what the right interpretation is and and (maybe) get consesus for clarified wording. Take a look at the article I linked and tell me whether you think it's incumbent on an editor to read through the 500 words in the three sources cited just to see if, somewhere in there, there's some claim of significance, before nominating for A7. EEng (talk) 22:52, 27 January 2011 (UTC)
 * If there's a list of potentially reliable independent sources, in my mind that's an assertion of significance that the subject may meet the general notability guideline and should be discussed at AfD, not left to just one or two people to determine the article's fate via speedy. Paul Erik  (talk) (contribs) 22:58, 27 January 2011 (UTC)
 * The key there, of course, is potentially reliable independent sources. So, Facebook, Twitter, Official Site, BandCamp, YouTube, YouGetThePoint... don't apply! &mdash; Timneu22 &middot; &#32; talk 23:01, 27 January 2011 (UTC)
 * I agree with that. Paul Erik  (talk) (contribs) 23:03, 27 January 2011 (UTC)

This seems to be going in the direction of saying that the simple fact that sources (other than of the Facebook variety) are listed, then that counts as an assertion of significance on its own? That means that any article which cites any non-Facebook-type source immediately escapes A7? EEng (talk) 23:15, 27 January 2011 (UTC)
 * We want editors creating articles to be paying attention to WP:N, so in some ways listing sources is the best way to assert significance. It's asserting that independent sources have written about the subject. See also User:SoWhy/Common A7 mistakes. Paul Erik  (talk) (contribs) 23:21, 27 January 2011 (UTC)

Agree that we want to encourage sourcing, but the question still is whether listing some sources, without giving any idea in the article itself what the source of the subject's notability even might be, passes muster. The essay you linked says Yes, setting a very low bar:
 * If the article makes any of these claims, it almost certainly does not meet A7...Has received coverage of any kind in possibly reliable sources...

Now, that essay is just an essay, not policy. The question is whether this is an appropriate interpretation of the A7 policy. I would advocate that it is not, and that the article text itself should have at least something to indicate significance. I'd endorse pretty much the full list of significance-signifying items in the list given in the essay, if at least one of them is given in the article text. I think that last provision is asking very little, and is a useful requirement. An example: The article (about a company called AnaJet ) which started me thinking about this question lists three sources. One is your standard dry company-profile piece (# of employees, revenue, etc); one  is a (surprisingly interesting) discussion of the technical challenges involved in printing on textiles (mentioning several companies) and the third  is about Anajet itself. I read through all of them and I can honestly say that nowhere is there even a single instance of what one might call a claim of significance. The closest I could come is:
 * "The printers are AnaJet founder Chase Roh's answer to the clothing industry's problems with traditional screen printing."
 * "Brother and AnaJet are considered by many to offer the only printers specifically designed for printing on fabrics and textiles."
 * "Notice that Silevitch mentioned the print heads. There is a reason for this. While AnaJet’s machine was designed specifically for printing on fabric, it does utilize Epson print heads."

Really, that's it. There's no claim of even tenuous significance in the article because there's none in the sources which is why, of course, there's none in the article either. Yet despite this (under Paul Erik's interpretation) this article survives A7 and goes to AfD, and everyone has to suffer through all boring this stuff to discover for himself or herself not only that there's no notability, but that there's nothing that even hints at it. They should't have to do that, and under my interpretation of A7, they wouldn't: the article text should be required to give some indicator of significance (wregardless of whether sources are listed and regardless of what those sources might say). If the article can't do that, as this one can't, then it's deleted under A7 and we can all move on to other things.

The above is longer than I intended but there it is. Since I've gone this far I'll propose (in order to keep discussion concrete) that the policy's A7 text be modified thus:
 * An article about a real person, individual animal(s), organization [etc etc] that does not indicate why its subject is important or significant. contain, in its text, at least one credible assertion of fact constituting a suggestion of the subject's importance or significance.  [etc etc]

Thoughts? Don't all yell at me at once, please. EEng (talk) 00:50, 28 January 2011 (UTC)
 * (@Paul Erik e/c with large block of text above ) Agree wholeheartedly. Here's where I stand on this.--Fuhghettaboutit (talk) 01:13, 28 January 2011 (UTC)


 * A7 is for cases where one sees no reason to believe the article could ever develop into something viable. If there is any reason to believe an article has a chance of surviving an AfD because of cleanup/expansion that could take place during the AfD itself, then A7 must not be used. And if a cited source gives a reason to believe the article could be expanded into something viable, then the article is simply not an A7 candidate, even if the claim of importance is not within the text itself. Although in such a situation, criteria A1/A3 may apply, but not A7. --  Blanchardb -Me•MyEars•MyMouth- timed 01:19, 28 January 2011 (UTC)

Assuming that your interpretation of A7's current text is correct, I'm suggesting that we change it, in a very minor way. To repeat, I'm proposing that the article's creator, or just one person who cares about it, be required to trouble himself to take something indicating significance from one of those sources and put it into the article. That's it. Is that asking too much? The point of my long excursion above was to show that, where this isn't done (even now, when it's not required to be done) it's a pretty good indicator that there's nothing at all even suggesting significance that can be added to the article. That's the question on the table. EEng (talk) 01:26, 28 January 2011 (UTC) P.S. to User Fuhg: all of the examples you gave, with the possible exception of poet Penrose, would survive under my proposed version of A7.
 * My post was very specifically responding to another which was talking about the inclusion of reliable sources in the article text. They are an indication of importance and significance by virtue of the fact that we hold up sourcing as the wellspring of notability. The whole nature of notability is that for purposes of an encyclopedia, reliable sources taking note of a topic is what's important and significant for a topic's inclusion. But application of notability requires us to make a determination of whether the reliable, independent, secondary sources significantly treating the topic actually exist. So when we go to the far lower threshold of an indication of importance or significance (A7), putatively reliable sources being included, all by itself, is a fundamental indication. I was not targeting the scenario in your original post which, by contrast, contemplates us taking on the obligation of surveying the content of the sources included, in order to find an assertion in their text. That is totally unworkable. So I would have declined your A7 request—not because of anything in the sources, but because the sources themselves are not Myspace or Facebook but Business Week and others.--Fuhghettaboutit (talk) 02:21, 28 January 2011 (UTC)
 * I agree that there should be at least one credible claim to significance in the article text. Just because an article lists a source like Business Week doesn't mean the source is even relevant, let alone contain any claim of significance. I don't think it's too much to ask that if someone has gone to the trouble of finding sources that they include at least one claim from those sources in the article text. Regarding the specific wording suggested above, I'm happy with most of it but not the ending. I'd suggest instead:
 * An article about a real person, individual animal(s), organization [etc etc] that does not indicate why its subject is important or significant. contain, in its text, at least one credible assertion of fact that indicates why its subject is important or significant.  [etc etc]
 * Although I'm not 100% happy with this I think the slightly simpler language will help more people understand it. I would make it clear and explicit in an explanatory note that the inclusion of sources does not, on its own, constitute an assertion. I'd suggest making the same wording changes to A9 too.
 * To me, A1, A3 and A7/A9 together constitute the absolute minimum standard that are required for an article to be acceptable: There must be actual content that gives enough context to identify the subject of the article and contains a credible assertion that the subject is significant and/or important enough for an encyclopaedia article. Thryduulf (talk) 12:24, 28 January 2011 (UTC)
 * I disagree with your proposed wording. I feel that if an article contains a reference to a relevant reliable source, then that itself is a credible claim of significance, and the article should not be speedily deleted. Thparkth (talk) 15:22, 28 January 2011 (UTC)
 * The point is that it should be possible to determine whether a credible assertion of significance/importance is made by reading only the text of the article. The evaluation of the relevance and reliability of sources is something that is AfD's job. So either every article that includes a source (regardless of relevance or reliability, including myspace and facebook links) but does not state it's importance gets sent to AfD, or the claim of significance must be in the article text. Those are the only two options that meet the objectivity requirement of speedy deletion criteria. Thryduulf (talk) 15:46, 28 January 2011 (UTC)
 * This is a false dichotomy. Myspace and other obviously-self-published material never counts as evidence of notability, so no judgement call is necessary. If a topic has been covered in an independent reliable source, that is prima-facie evidence of a claim to notability, and speedy deletion under A7 is not appropriate even if the article text itself isn't explicit about it. This is the current practice for what it's worth. Thparkth (talk) 20:53, 28 January 2011 (UTC)
 * The concept that sourcing alone is a statement of importance isn't reasonable. There are a lot of sources that convey no importance or notability. Should an article contain a statement that demonstrates notability? Certainly. Should a nominator take a quick peek at sources and fix instead of nominate when the source contains a statement of importance? Generally, yes. Should the admin processing the same article make the same check? Generally, yes. Has either the nominator or the admin made a serious error if they don't notice the statement in the source when the author failed to include it in the article? No. It's unimportant, and the worst that will happen is that a poorly written article gets deleted, and someone with better skills will have to recreate it. An excusable mistake with insignificant consequences. &mdash;Kww(talk) 21:05, 28 January 2011 (UTC)
 * I agree with Thparkth (and disagree with Kww that the consequences are minor): Noting coverage in independent reliable sources is prima-facie evidence of a claim to notability, and this is the current practice generally, if not universally among admins. We practically hit new editors over the head with the message that the best way to demonstrate notability is to show independent coverage—it's in all the introductory material, including the Article Wizard ("If a topic has received significant coverage in reliable sources that are independent of the subject, it is presumed to satisfy the inclusion criteria for a stand-alone article."). It appears in the template: "Please help to establish notability by adding reliable, secondary sources about the topic." The core policy of WP:V notes in a section all its own, "If no reliable third-party sources can be found on a topic, Wikipedia should not have an article on it." The edit notice when anyone creates a new article says, "When creating an article, provide references to reliable published sources. An article without references, especially a biography of a living person, may be deleted." A new editor who pays close attention to that is someone we want to keep around, even if they aren't getting all other aspects quite right. Quickly deleting such articles sends a frustratingly mixed message.  Paul Erik  (talk) (contribs) 22:04, 28 January 2011 (UTC)
 * (@ Thryduulf) You miss the point. "[T]here should be at least one credible claim to significance in the article text" you say, but you are limiting that claim to a prose assertion for unknown reasons. We are talking about indications of importance or significance for encyclopedic purposes. Our underlying goal is to separate wheat from chaff, and the wheat is topics that are likely to merit inclusion. Where would we look to down the road, on the merits, for whether a topic merited inclusion? We would look to whether it was the subject of treatment in reliable sources. That is how we ultimately assess whether a topic is "important or significant" enough to be included. With CSD A7, we are not down the road yet. We are not exploring whether the topic actually meets these standards but looking for a mere indication that it may. At the A7 assessment point, we don't know whether any statements of fact are true. We don't know whether a statement like "is very well know X" actually should continue "...in my high school only." We don't know whether, even if the statement is true, there are sources backing it up. Sourcing is the goal and the touchstone and the standard we will look to and require an article to meet to substantiate its importance. But as a practical matter we can't ask for that to be shown in an article's first version, so we ask for an "indication of importance and significance". That indication does usually take the form of a statement of fact, but because of what we are, and concomitantly, the grounds upon which we decide whether topics merit articles, there can be no better and direct indication of importance than cited reliable sources already present; they indicate that the higher level standard of proof notability calls for, may actually be met.
 * John doe is an artist (born year) haling from X.
 * John doe is an artist (born year) haling from X. He is very well known and has exhibited widely.
 * John doe is an artist (born year) haling from X.<Citation to The New York Times and a book on impressionist art>
 * The first is uncontroversial A7. The second asserts a fact indicating importance, though we don't know if its true. The third indicates that the New York Times and a topic specific book have content on the subject—the very types of material that the second would need to show, if questioned, is already indicated in the third.--Fuhghettaboutit (talk) 00:08, 29 January 2011 (UTC)
 * That's true, and I think both the tagger and the reviewing admin have an obligation to review it. But if the sources were articles in a high-school newspaper, it's still A7 material. I don't think A7 should be written to force retention of an article sourced to questionable sources in an effort to avoid an occasional error with articles sourced to legitimate sources.&mdash;Kww(talk) 13:57, 29 January 2011 (UTC)
 * Re the 3rd example, if both citations are linked to an on-line, or other source the reviewer has access to, and neither seem to indicate any actual notability, it may well still be A7. He may well, for example, have been mentioned in the NYT as the art student son of Jane Doe, the famous artist. However, I agree that if no such access is available one should AGF and decline the speedy (possibly PRODing it) even if the text itself fails to assert notability. Ben   Mac  Dui  16:17, 29 January 2011 (UTC)
 * As the editor who began this thread, I can only say... Oh my goodness! What a firestorm I've set off!  I'll wait until the dust settles a bit before commenting. I do appreciate everyone's efforts to help answer this innocent question posed by lil' ol' me. EEng (talk) 14:22, 29 January 2011 (UTC)
 * That would be equivalent to where the assertion of fact is not true or deceptive or overblown and the tagger or reviewer takes on the task of checking. We get a lot of that in new pages. Based on placing and reviewing a few thousand csd tags, I think there are far more pages (by percentage) where the prose assertion is a lie, deceptive or overblown, than it is the case a citation to a seeming reliable independent source that someone has bothered to include turns out to be bullshit.--Fuhghettaboutit (talk) 18:45, 29 January 2011 (UTC)
 * True enough, but I have seen it. Ben   Mac  Dui  19:41, 29 January 2011 (UTC)
 * Oh sure. Seen it many times.--Fuhghettaboutit (talk) 20:02, 29 January 2011 (UTC)
 * This happens a lot with articles about criminals; without any references, they're usually G10s. But if they have a reference, you have to check and see if it backs up the claim; there was one instance where I came across a screed of text accusing a man of child molestation, and the one "reference" was an article about three guys going to a basketball game.  It was an obvious attempt at bullshitting; on borderline cases with A7 or G10, I always check the prose and the references.  The Blade of the Northern Lights  ( 話して下さい ) 04:16, 1 February 2011 (UTC)

F7 Summary Deletions
Under what circumstances is an F7 deletion appropriate without a dfu tag or similar process? I've just restored three images (File:Complete androgen insensitivity presenting with inguinal hernia.jpg, File:Complete androgen insensitivity syndrome.jpg, File:Complications from infant genitoplasty.jpg--NOT SAFE FOR WORK) which were deleted because the uploader added a Non-free newspaper image tag for the licensing section presumably because we don't have a licensing tag for journal images. The tag notwithstanding, detailed copyright and source information were present in the fair use rationale. Is it appropriate to delete those kinds of images on sight (I'm not looking for answers to whether or not it was appropriate to delete those three per se, that's in the past)? The only discussion I see on it (admittedly without deeply searching WT:CSD) is on the template talk page from 2006. Protonk (talk) 16:33, 31 January 2011 (UTC)


 * I'm unsure why those examples were deleted - a detailed tag and a license tag were present after all. Even if one were to argue that F7 was applied correctly, not even notifying the uploader is not really the correct way to act in this case. In general, F7 specifically mentions that images should only be deleted if there is a clearly invalid fair-use tag present. In cases where the uploader clearly thought about those things, one should never use any of those criteria to immediately delete an image. Regards  So  Why  21:58, 31 January 2011 (UTC)

Proposed rewrite to G4
So I apparently misused this criterion recently, and I'd like to propose a little bit of "corrective and preventive action" to make sure someone else doesn't make the same mistake.

Current version:


 * G4. Recreation of a page that was deleted per a deletion discussion.
 * A sufficiently identical and unimproved copy, having any title, of a page deleted via a deletion discussion. This excludes pages that are not substantially identical to the deleted version, pages to which the reason for the deletion no longer applies, and content moved to user space for explicit improvement (but not simply to circumvent Wikipedia's deletion policy). This criterion also excludes content undeleted via deletion review, or which was deleted via proposed deletion or speedy deletion (although in that case the previous speedy criterion, or other speedy criteria, may apply).
 * db-g4, db-repost

Proposed version:


 * G4. Recreation of a page that was deleted per a deletion discussion.
 * A copy, regardless of title, of a page deleted by a recent deletion discussion. G4 does not apply to pages deleted through a speedy criterion, pages where the reason for the deletion no longer applies, content moved to user space for improvement (but not simply to circumvent Wikipedia's deletion policy), or content undeleted through deletion review.  This criterion should not be used if the copy has additional content, references, or major changes, even if the topic and intent of the article is the same, and a new deletion process should use WP:PROD or a speedy criterion other than G4.  If the content is a clear copy-paste of the deleted content, use G4.
 * db-g4, db-repost

Summary of changes:


 * Indicates that it only applies to recent deletions (i.e. consensus can change).


 * Gets rid of undefined terms like "substantially identical" which are so subject to interpretation that they are meaningless. The same sense is still included ("additional content, references, or major changes").


 * A lot of rewriting, hopefully clearer and a little less legalistic.


 * Attempts to explain some things which are in the current tag which I fell afoul of.

Something to consider. SDY (talk) 19:36, 17 January 2011 (UTC)
 * The last clause seems extraneous. You've actually made the bar much lower and far more subjective and difficult, since "additional content" could mean.. what? An extra sentence is additional content, so is an extra paragraph, or 30,000 fully-referenced words on the matter. Ironholds (talk) 10:45, 18 January 2011 (UTC)


 * I'm certainly no deletionist, but I think "copy" is too strict. If "John Doe is great" is deleted at AFD, a new article called "John Does is a good guy" still qualifies for G4, even if the content is different. The point of G4 was that people should not be able to circumvent a community decision by slightly altering the text while not addressing the problems that were the reason for its deletion at all. I am more in favor of the other proposals, although I'm wary of the "recent". If I recreate a page after two years, I see no reason not to use G4. On the other hand, if it's recreated immediately and then tagged after two years, I interpret the fact that it was allowed to exist for such a long time as a sign that consensus might have changed. Regards  So Why  11:39, 18 January 2011 (UTC)


 * Instead, I think this is trying too hard to prevent "mistakes". I think G4s, and others, such as A7s, defy precise codification, and we should rely on human intuition to make the calls.  There will always be "mistakes", and to account for this, protests or contests against the speedy should be invited, and where the contest is are even close to reasonable, simply undelete and list at XfD for a discussion.  --SmokeyJoe (talk) 15:42, 18 January 2011 (UTC)


 * Taking another stab at the language:


 * G4. Recreation of a page that was deleted per a deletion discussion.
 * A copy, regardless of title, of a page deleted by a deletion discussion where consensus has not changed. G4 does not apply to pages deleted through a speedy criterion, pages where the reason for the deletion no longer applies, content moved to user space for improvement (but not simply to circumvent Wikipedia's deletion policy), or content undeleted through deletion review.  This criterion should be used with caution if the copy has additional content, references, or major changes, even if the topic and intent of the article is the same, and a new deletion process should use WP:PROD or a speedy criterion other than G4.  The intent of G4 is to avoid repeated discussions of the same deletion discussion when the reason for deletion has not changed.
 * db-g4, db-repost


 * Changes include "recent" to "no change in consensus", changed "not used" to "used with caution", and explicitly states the gestalt of the idea that we've been discussing. SDY (talk) 16:46, 18 January 2011 (UTC)


 * The proposal is confusing. A page is not a copy if it "has additional content, references, or major changes", so what's it trying to say? Is it proposing to delete under G4 pages that are not copies ? --Bsherr (talk) 17:09, 18 January 2011 (UTC)


 * A copy need not be exactly the same and it can still be called a copy. See SoWhy's example above.  Semantics aside, yes, G4 could be used to delete things that are not exact copypasta.  The intent, as I understand it, is just to avoid having exactly the same discussion over again, and if the changes don't address the reason it was deleted, it can be re-deleted under G4.  SDY (talk) 17:22, 18 January 2011 (UTC)


 * Indeed, "sufficiently identical and unimproved copy" meant that a copy only need be "sufficiently identical", which, I presume, would include trivial and other changes that do not improve the article. The proposed text does away with that, and instead advances that an article with, for example, "major changes" is still a "copy". I think that's a much more unclear connotation of what a copy is. If the goal is to clarify the language, this seems to aggravate the problem. --Bsherr (talk) 17:28, 18 January 2011 (UTC)


 * FWIW, I think that this is important to clarify. I also think it's a bit silly that as the policy is currently written someone can create a brand new article on an AfDed subject (say, for notability concerns) twenty minutes after the first is deleted and it has to go through AfD again if the content is not "substantially identical". (I'm sure it could be deleted under WP:IAR, but it shouldn't have to be; G4 should help prevent that.) So I applaud this effort, and I hope we can come up with something reasonable. To avoid ambiguity, I too think we should avoid the word "copy" here, though. What about "A recreation" or "A new or recreated version"? Beyond that, I don't understand what this means: "This criterion should be used with caution if the copy has additional content, references, or major changes, even if the topic and intent of the article is the same, and a new deletion process should use WP:PROD or a speedy criterion other than G4." "should be used with caution" suggests that you can G4. The second half of the sentence seems to say you cannot. I would support stopping that sentence with the words "is the same." The rest of the sentence seems unnecessary to me. --Moonriddengirl (talk) 17:29, 18 January 2011 (UTC)


 * G4. Recreation of a page that was deleted per a deletion discussion.
 * A copy, regardless of title, of a page deleted by a deletion discussion where consensus has not changed. G4 does not apply to pages deleted through a speedy criterion, pages where the reason for the deletion no longer applies, content moved to user space for improvement (but not simply to circumvent Wikipedia's deletion policy), or content undeleted through deletion review.  This criterion should be used with caution if the copy article has additional content, references, or major changes, even if the topic and intent of the article is are the same, and a new deletion process should use WP:PROD or a speedy criterion other than G4 .  The intent of G4 is to avoid repeated discussions of the same deletion discussion when the reason for deletion has not changed been addressed.
 * db-g4, db-repost

Another stab, hopefully addressing some of the concerns. SDY (talk) 17:34, 18 January 2011 (UTC)
 * It's better, but it's still not workable as is. The "used with caution" language is still problematic. The criterion needs to provide explicitly when it should and should not be used. Otherwise, it fails criterion 2 of our four criteria for CSDs. --Bsherr (talk) 18:38, 18 January 2011 (UTC)
 * What about "This criterion should be used with caution if the article has additional content, references, or major changes, even if the topic and intent of the article are the same, as it is not for use when alterations could reasonably have changed the outcome of the deletion discussion. The intent of G4 is to avoid repeated discussions of the same deletion when the reason for deletion has not been addressed." --Moonriddengirl (talk) 18:56, 18 January 2011 (UTC)

You know, folks, you're giving me Fledgling Jason Steed flashbacks here. Thank you so much. (In other words, take a look at the related discussions for multiple recreations of substantially-identical content.)--SarekOfVulcan (talk) 18:46, 18 January 2011 (UTC)
 * So if consensus hasn't changed, and any attempt to create a new article is subject to G4.... how is consensus supposed to change? Jclemens (talk) 18:55, 18 January 2011 (UTC)
 * There are a lot of ways to change consensus that are not enacted at article level. For example, if WP:CREATIVE decides to regard authors as notable if they publish a single book, then a single-book author's article is no longer G4able. :) --Moonriddengirl (talk) 19:00, 18 January 2011 (UTC)
 * Not a really clear answer, unfortunately. Walk through this with me: Article is deleted properly. New article is created which solves the issue... at least in the author's good-faith opinion. How, aside from every single admin agreeing that the reason for deletion no longer applies, is the article safe from G4? Jclemens (talk) 19:05, 18 January 2011 (UTC)
 * How does an author who creates an article that he believes clears A7 escape CSD aside from every single admin agreeing that does? or G11? All speedy deletions rely on the good sense of those who apply them. Fortunately, we have WP:DRV where something goes awry. --Moonriddengirl (talk) 19:14, 18 January 2011 (UTC)
 * A7 and G11 aren't subject to the historic level abuse that G4 has been. I entirely empathize with the need to quickly quash bad-faith readditions, but see an enhanced abuse potential with the proposed re-wording.  I'd rather have something like "...created by an editor with less than 50 mainspace edits".  It's an objective criteria, even if irrelevant to the content of the article, which would serve to deter SPAs while ensuring that G4 is not used as a hammer in good-faith disagreements over notability. When one editor in good standing recreates an article in good faith, it should be sent to AfD instead of G4 (although some other CSD could apply, e.g. G10-12). How can we state that without giving the SPAs a field day? Jclemens (talk) 19:22, 18 January 2011 (UTC)
 * "Fledgling Jason Steed" doesn't help. It's an AFD, not a deletion review about a G4 deletion, so it doesn't really determine anything. Jclemens's question is right on, and Moonriddengirl's point is also right on. "Sufficiently identical and unimproved copy" means just that. Just change a few words around, and it's probably sufficiently identical and unimproved. Because it is uncontestably redundant to run the article through AfD, consensus allows admins to delete them speedily. Add a substantial amount of text or references to the article, and it's no longer identical and probably improved. A discussion then needs to occur to arrive at consensus about whether the article overcomes the prior reasons for deletion. Admins don't get to make that decision unilaterally. As always, bad calls about G4 can go to DRV. Speedy deletion is always about erring on the side of giving users a chance to participate in a discussion when they're editing in good faith. --Bsherr (talk) 19:39, 18 January 2011 (UTC)
 * See also Articles for deletion/Fledgling Jason Steed (2nd nomination). We had to fight this one too many times in too many places.--SarekOfVulcan (talk) 18:30, 25 January 2011 (UTC)


 * In my experience, G4 is no more liable to abuse than the other criteria--the same 3/4 or so of the G4 request I see are clearly valid, just as with any of the other reasons. The problem is more precisely that G4 when borderline is often a controversial situation, involving divided or unclear or erratic consensus at the original AfD. The current wording is a little too imprecise,but the proposed one is a good deal too loose. It should be major additional content, and significant key  references--but this is really covered already in the requirement to address the deletion reason.  I'm also a little dubious about the wording "where consensus has not changed" but I cannot immediately think of a better.    DGG ( talk ) 22:38, 18 January 2011 (UTC)


 * Should worse recreations fall under G4? The examples I found indicate that it does not apply: Deletion review/Log/2009 July 5 (keep deleted, G4 not applicable; July 2009), Articles for deletion/Nicholas Beale (4th nomination) (G4 reversed by deleter, sent to AfD, IAR speedy; October 2009). If admins are not allowed to judge that a recreation is worse, then how can they evaluate "sufficiently ... unimproved"? Flatscan (talk) 05:43, 19 January 2011 (UTC)
 * Articles for deletion/Nicholas Beale (4th nomination) seems like a strong indication why they should. If an article is deleted for not have sufficient sources, say, to verify that its subject is notable and a new article is created with entirely different language but with no new sources, is there any reason that we should have to go through AfD again? What if it adds a Myspace link? --Moonriddengirl (talk) 19:06, 19 January 2011 (UTC)
 * That's the situation that would posssibly call for redrafting of the criterion, I think. But we need to remember that speedy deletion is often so efficient that content creators would suffer by never knowing exactly why their recreation wasn't considered improved. Proposed deletion allows such users to understand the issues and choose to improve the page or consent to deletion. If they do legitimately believe their recreation addresses the issues raised in AfD, they should have a chance to make that argument. Using "obviously" or "blatantly" with "unimproved" might be the best way to go. --Bsherr (talk) 19:21, 19 January 2011 (UTC)

Attempting to incorporate proposals, focusing on the intent of G4 (not to repeat the same discussion when nothing has changed):


 * G4. Recreation of a page that was deleted per a deletion discussion.
 * A copy, regardless of title, of a page deleted by a deletion discussion where consensus has not changed. G4 does not apply to pages deleted through a speedy criterion, pages where the reason for the deletion no longer applies, content moved to user space for improvement (but not simply to circumvent Wikipedia's deletion policy), or content undeleted through deletion review.  The intent of G4 is to avoid repeated discussions of the same deletion when the problems that led to deletion have not been addressed.  If the article has changes such as additional content or references that attempt to address the original reason for deletion G4 should not be used.
 * db-g4, db-repost

Tempted to mention Fight Club in the last sentence, frankly, since that's really what G4 is about. My expectation of G4 is that it would quash attempts by users to "test into compliance" deletion arguments and keep forcing the deletion argument until they get the answer they want (diehard fanatics have problems with admitting defeat). Just as my .02 on the "same article but worse" question, multiple authors in good faith attempting to create the same article (i.e. three members and two fans of the same lame garage band that has extremely dubious notability) should not force repetitive discussions, even if all five of the articles share nothing but the name of the band. SDY (talk) 01:55, 20 January 2011 (UTC)


 * Getting close. For starters, it shouldn't self-reference as "G4". That should be replaced with "this" or "this criterion". I'm going to think on the rest of it. --Bsherr (talk) 05:41, 20 January 2011 (UTC)
 * Nope, still not workable. It needs to eliminate a good faith attempt to address the deletion cause. Further, there is no way a speedy deletion--an action by one admin--can test consensus, so "consensus has not changed" is inherently a non-sequitor. Jclemens (talk) 21:32, 21 January 2011 (UTC)
 * A good faith attempt to address the reasons for deletion will never be mistaken for "a copy", so I think that is addressed. A agree about your latter point, but I think SDY's intent can be accomplished by other means.
 * We discussed above that there are other means by which consensus changes other than at the page level. I think the right way of addressing this is by exclusion of situations in which consensus has changed, rather than inclusion only of situations in which consensus has not changed. Furthermore, we're not really concerned with consensus at the XfD; really, it's about whether there has been a change in policies, guidelines, etc., forming the foundation of the consensus at XfD. I too struggle with the wording, but perhaps, "This excludes pages the foundation (e.g., policies, guidelines) of the consensus of the deletion discussion of which has significantly changed such that it is credible to argue that the consensus of the deletion discussion is in doubt." ?
 * --Bsherr (talk) 01:27, 22 January 2011 (UTC)


 * The last sentence: "If the article has changes ... that attempt to address the original reason for deletion..." was my attempt to address the "good faith attempt" that Jclemens is concerned about. This could be made more prominent.  I agree with reversing the first sentence, maybe shift to "copy deleted by discussion where it is clear that consensus has not changed" so the burden of proof is on the deleter rather than on the deleted and disallows the criterion if there is any ambiguity about the consensus.  SDY (talk) 14:47, 22 January 2011 (UTC)

Arbitrary break

 * G4. Recreation of a page that was deleted per a deletion discussion.
 * A copy, regardless of title, of a page deleted by a deletion discussion where no attempt has been made to address the reason for deletion through additional content, references, or changes. This criterion does not apply to pages deleted through a speedy criterion, content moved to user space for improvement (but not simply to circumvent Wikipedia's deletion policy), content undeleted through deletion review or if consensus has changed on the deletion, such as a change in notability guidelines.  The intent of this criterion is to avoid repeated discussions of the same deletion when the problems that led to deletion have not been addressed.
 * db-g4, db-repost

I think it addressses all of the concerns that have been raised. I reorganized it slightly to make the "no attempt" more prominent, and modified the language about consensus changes to make it clearer. Tempted to also add "A user wishing to challenge a previous deletion should use deletion review instead of reposting the same article." but maybe that's more for the tag, which may also have to be rewritten. Frankly, since this is a rewrite more than a real change it might be OK to leave it, though again I'd like to avoid the "substantially identical" language since it is so incredibly vague. SDY (talk) 00:26, 24 January 2011 (UTC)
 * I agree, this version addresses all of my concerns. Jclemens (talk) 00:45, 24 January 2011 (UTC)

I know I'm coming late to the discussion but I just noticed the edit and I have, well, many changes I would propose.
 * Starting with "A copy" is likely to confuse since copy implies an exact duplicate, and while this criterion does cover exact copies, the whole point of all the explanation included is to address pages that are more than duplicates. This was noted by more than a few people above and I would second Moonriddengirl's proposed "recreated version".
 * "No attempt to address..." is the biggest problem I see. Someone may have "attempted" to address the deletion basis, but done so quite insufficiently (in fact this is very common). This sets up an intent standard. Was it the person's intent to address the deletion basis even though failed miserably? Yes? Okay, then article X which had no reliable sources must be kept because a Myspace citation was added and the person intended that to fulfill the deletion discussion basis of lack of reliable sources. Oh, but Myspace here is not a reliable, independent, secondary source—doesn't matter; the person "attempt[ed] to address the reason for deletion." What to replace this with is the biggest hurdle I think. Is it a page that does not sufficiently address the deletion bases? Substantively? Reasonably? The closest I've seen to an objective standard also comes from Moonriddengirl: "when alterations could reasonably have changed the outcome of the deletion discussion". All of these though require some judgment on the part of the tagger and the admin reviewing, and all are better than judging from the perspective of whether the re-creator thought they were attempting to address the deletion bases.
 * I would add prod to the list of things not covered by deletion discussions, after speedy deletion. Some might say that prod is a form of speedy deletion but this needs to be explicit since the vast majority do not understand it this way.
 * "or if consensus has changed on the deletion" is another problem. The intent here is to refer to a change in outside policy or guideline that underlies the deletion basis. It does not read this way. It reads as referring to a change in the consensus at the deletion discussion itself (a non sequitur, since the deletion discussion was the source of the consensus). Let me just propose language that I think addresses all this and more:


 * <tt>A recreated version of any page, regardless of its title, that was deleted through a deletion discussion which is an exact or substantial copy of the prior version or where additional content, references, or changes from the previous version could not reasonably have changed the outcome of the deletion discussion. This criterion does not apply to pages deleted through any speedy criterion (CSD), proposed deletion (prod), content moved to user space for improvement (but not simply to circumvent Wikipedia's deletion policy), content undeleted through deletion review or if consensus has changed on the policy or guidelines underlying the deletion basis, such as a change in notability standards. The intent of this criterion is to avoid repeated deletion discussions of the same topic when the problems that led to deletion have not been addressed.</tt>--Fuhghettaboutit (talk) 04:21, 25 January 2011 (UTC)
 * I just noticed too, and I'd tend to agree. Though I'd shorten it: "An article which was previously deleted as the result of a deletion discussion and which does not remedy the issues which led to deletion." You don't just need to try to fix it, you need to actually fix it. Seraphimblade Talk to me 05:09, 25 January 2011 (UTC)
 * I just inserted a missing "not", but I think this is workable, too. It can still be tightened a bit, but I agree with the emphasis: if an editor has made a good-faith effort to address the deletion discussion, whether from a copy or by creating a new article from scratch, going back to AfD (with the possibility of salting the title if the community's patience has become exhausted with good faith but chronically insufficient efforts) rather than G4 is the right process. Jclemens (talk) 18:21, 25 January 2011 (UTC)
 * We need to keep the "exact or substantial copy" part of the wording. This is what G4 is there for. Too many editors are apt to put their own interpretation on whether or not the previous reasons for deletion have been addressed. I think it was unwise by the way to change this with only a few editors contributing to the discussion here, and it should be changed back until there is clear consensus for a change. --Michig (talk) 20:40, 25 January 2011 (UTC)
 * Silence is sometimes just an indication that no one objects. If you look at the way I posted it (I requested reverts in the comment, after all), I clearly did not expect it to be final, and the edit had the desired effect of generating additional input.  Just for the record, "exact or substantial copy" and "copy" don't have a lot of difference for me, as I expect the criterion will be applied by humans, not lawyers or computers, who understand the nuance that moving a word or two around does not change whether or not it is a copy.  SDY (talk) 01:46, 26 January 2011 (UTC)
 * Legalese is a swear word for what is often an attempt to obfuscate (insurance contract anyone); good legal writing, by contrast, is all about clarity and precision in language. I have trouble imagining anyone feeling talked down to or insulted by this language and I do think it provides clarity for a small imprint of verbiage.--Fuhghettaboutit (talk) 04:08, 26 January 2011 (UTC)

(undent) I use the term "legalese" to mean anything that is stated in sesquipedalian overcomplexities that add lots of words but don't add lots of meaning. We can haggle over the wording later. The main thing that we appear to be disagreeing on now, though, is whether a good faith (but ineffective) attempt requires a full discussion or is G4-able. As Jclemens has pointed out, we have other tools available if an editor decides to abuse a more lenient version. I'd rather see discussions than speedies if there's any doubt, though I think we might be able to wrangle in some of MRG's expectation of a "clueful" good faith attempt. SDY (talk) 04:44, 26 January 2011 (UTC)
 * I really don't see how good faith is relevant. We delete hundreds of things that were created in good faith every day. You can have all the good intentions in the world and still create an inappropriate article. Either they have rectified the issue that led to the initial deletion, or they haven't. If there is a reasonable case to be made that they have, then we let the article stand. If not we delete it. I don't think it is really flawed and needs to be changed. The way it was written was working fine. Beeblebrox (talk) 04:53, 26 January 2011 (UTC)


 * The previous version did not address the issue of what "substantially identical" meant (which this whole "attempt" business is clearly related to), so it appears that there is some uncertainty about what the policy should say. Frankly, the previous version is probably only clear to you because you were familiar with using it, and policy should be clear at first reading, not simply through experience, especially for things like speedy criteria because of the WP:BITE potential.  Reading the old policy, I have no clear idea what "substantially identical" means.  SDY (talk) 14:12, 26 January 2011 (UTC)


 * (e/c) I don't understand why we are going anywhere near an intent standard. It makes no sense to me at all, and talk about an ambiguity-riddled thing to judge. A person's additions/changes to a recreated article either do, or do not, address the deletion bases. What they intended/attempted to do in making the changes seems to me exquisitely irrelevant. I can't imagine where we would begin to make an assessment of whether such changes/additions were in good faith or not. Going back to the example I used before of adding Myspace links (or Facebook; some blogs; maybe some unreliable sources that are not so blatantly invalid on their face) who's to say this wasn't a good faith attempt to address a deletion discussion's basis for deletion of lack of sourcing, albeit, without a good understanding of the relevant policies? It seems to me if we enact this we would need to take every article that contained additional content to AfD because only in the most blatant cases would good faith be able to be judged against the recreator (we do assume good faith after all).--Fuhghettaboutit (talk) 05:03, 26 January 2011 (UTC)


 * My impression of the speedy criteria is that they were intended to be used if and only if no community input is necessary. If there is any doubt, it should be going to a full discussion, not arbitrary deletion.  Note that at no point was there a suggestion that WP:AGF was part of the policy, and adding a few clearly inappropriate references isn't much of an "attempt."  MRG's comments about things that might "change the outcome" I think hit the nail on the head.  SDY (talk) 14:12, 26 January 2011 (UTC)


 * If the issue here is that "substantially identical" is something that people don't understand, then why not simply try to clarify that (not difficult I would have thought) rather than altering the wording in a way that allows people to delete articles simply because they alone have decided that the new article doesn't address the reasons for deletion from the original AFD. --Michig (talk) 18:27, 26 January 2011 (UTC)
 * Trying to unambiguously define this is a mistake. If the article is the same as the previously deleted version, delete it. If the wording is altered but not in a way that addresses the concerns that led to the deletion, delete it. If substantive improvements of any kind have been made, keep it. That is the intent behind this csd. While the criteria are deliberately narrow, they also deliberately contain phrases like "substantially identical" so that the reviewing admin is permitted to ast in the spirit of the criterion. A7, the mst widely used criterion, uses the phrase " credible claim of significance or importance " and we trust admins to be able to evaluate that as well. Mistakes will be made in both directions no matter how carefully we try to word the criteria. Being too specific is as bad or worse than being too vague. Beeblebrox (talk) 21:01, 26 January 2011 (UTC)
 * I agree with your interpretation of 'substantially identical' but I've seen others interpret it as 'same issues as last time', irrespective of the article content. Yes, it's difficult to define it too tightly but it may be useful to specify some specific instances when G4 does not apply, such as an article deleted at AFD 4 years ago, where a new and completely different article has been created by a different editor - I've seen two of these in the past 2 days - one tagged as G4 (and detagged by me) and one deleted as G4 without prior tagging. --Michig (talk) 21:23, 26 January 2011 (UTC)
 * I originally interpreted "substantially identical" to mean "similar content and problems" (spades and shovels) and not "copies or near-copies" (spades and shades). Which is it?  The current policy does not say.  It does not address what the article's author could have or should have done but did not do that led to a speedy deletion, and it sounds rather arbitrary and capricious.  SDY (talk) 01:01, 27 January 2011 (UTC)
 * What the author should or could have done was address the deletion basis announced at the deletion discussion. If an article was deleted at AfD because notability was not shown, the additional content in the reposted article that would invalidate G4 applying would be reliable, independent secondary sources that treated the topic in some detail. Similar for verifiability, except that it would the information content and not the topic that would be the focus of the sufficiency of sources. If the article was deleted at AfD because it was too close paraphrasing, the changes would be a rewrite so that copyright was not violated, and so on for any deletion discussion. There's nothing arbitrary or capricious about it. I am implacably opposed to any standard that asks us not to judge whether the additional content addressed the deletion discussion basis, but instead asks us to gaze into a crystal ball to divine whether we think the person was acting in good faith in an attempt to address the deletion basis, regardless of whether they were successful or failed. It is a non-starter.--Fuhghettaboutit (talk) 05:02, 27 January 2011 (UTC)
 * I agree with Fuhghettaboutit's view of the purpose of this CSD criteria and also that it is not our purpose to assess the intent. But, Michig, it should be used when there are the "same issues as last time", irrespective of the article content, when those issues led to an outcome of deletion at deletion debate. To use the same example I raised above, if an article deleted at AfD for lacking sufficient sources to substantiate notability is recreated 15 minutes later with entirely different text but the same sources, it does not need to go back through AfD. The sources are not improved by the change in language. There are many possible scenarios where articles are deleted at AfD for reasons that have nothing to do with the specific text in use; limiting this criteria to those cases where the same text is used would generate unnecessary waste of community resources. --Moonriddengirl (talk) 11:55, 27 January 2011 (UTC)
 * I think you're missing the point. If someone is reposting a deleted article with no improvement, then yes, G4 applies. What I'm saying is that if someone else (who may never have been aware of the original article) creates a new article with completely different content, then G4 does not apply. The new article may lack sources, but that would not justify a G4 as it isn't a repost but a new article. One example I came across was about a musician who had released two albums since the AFD - it isn't appropriate for an individual to decide unilaterally that he isn't notable now and delete it as a G4 based an outcome from years before relating to a different article. In short we need to distinguish between reposting deleted articles without improvement, and new articles about the same subject created by different editors. G4 should apply to the former but not the latter.--Michig (talk) 17:29, 27 January 2011 (UTC)
 * I think, actually, we may be disagreeing on what the point is. :) I believe that the point of the criteria is to avoid wasting community time on deletion debates where the community has already passed judgment and there is no reason to believe that the judgment would have changed. If User:JohnSmith creates an article on musician AllThatandMore citing only his Myspace and it is deleted because the Myspace does not verify notability, the Myspace still does not verify notability when User:JaneDoe uses it to create an article. I believe the criteria should bridge the gap between ordinary speedy deletion candidates (that is, content which by broad consensus is inappropriate) and content that would not normally meet speedy deletion criteria but which the community has already judged. If a musician has released two albums, that is a material change of circumstance that might result in a new outcome of a deletion debate. That's a different kind of issue. --Moonriddengirl (talk) 18:07, 27 January 2011 (UTC)
 * Many of the criteria here help to avoid wasting time on deletion debates. We agree, it seems, that a material change in circumstance may result in a different outcome, so G4 would not be appropriate. Where we perhaps differ is that I don't think it should be used for completely new articles where the AFD that resulted in deletion is from years ago, with the possibility that new sources exist that did not back then. It's for dealing with reposting against consensus, not for preventing new articles from being created, which are better dealt with via a new discussion. Consensus can also change. --Michig (talk) 18:19, 27 January 2011 (UTC)
 * Actually, I would agree with you that in many cases if it was from years ago G4 is probably not appropriate. But I do disagree if you are saying that User:JaneDoe's article, created 10 minuted after the one deleted by User:JohnSmith, needs to go through AfD again even though it uses the single same source to substantiate notability that was rejected at AfD. I think it is important to recognize the reason that the content was deleted and to exercise good judgment in determining whether a new article has any hope of addressing that reason, so that we avoid process for the sake of process. --Moonriddengirl (talk) 18:33, 27 January 2011 (UTC)

(undent) I had originally been tempted to not include the "attempt" language but Jclemens had objected to a criterion that didn't include it so I left it in. I think the main question is how we address a reasonable attempt that might still ultimately fail but shows that the re-poster made every reasonable attempt to conform to notability policy but still fell short (e.g. article deleted per WP:NOTMEMORIAL, WP:NOTINDISCRIMINATE and WP:NOTBATTLEGROUND and the recreated article addressed the memorial and battleground issues but debatably still failed to demonstrate encyclopedic value). I totally agree that if it's obvious that the changes fail to address the reason for deletion then G4 it is, and that was what the edit I placed attempted to say (this whole discussion of AGF is not even hinted at in the actual text). In these marginal cases, how much discretion do we give the speedying administrator in determining whether community input is needed? It sounds like F_a_i's stance is that the administrator should have broad discretion, and I'm not really comfortable with that. Speedy criteria should have predictable outcomes. SDY (talk) 13:50, 27 January 2011 (UTC)
 * Well, I'm not sure what you mean by my stance being that admins should have broad discretion but, I can tell you that the language tweaks most were suggesting, including mine, which incorporated suggestions by others, were clarifications of the existing standard's language The standard for additional content has had since at least January 2007, a reference to additional content addressing the deletion bases. In 2007 it said ""Substantially identical" means that the new article doesn't attempt to address the reason for which it was deleted." This was more explicit in the last version and I think better than the current, e.g., as of July 2009. That standard is now contained in the language "the reason for the deletion no longer applies", which has the same result. The change to language that asks us to assess whether the attempt was in good faith is a sea change to the standard (and one which I think I've made clear, makes no sense at all to me).--Fuhghettaboutit (talk) 00:03, 2 February 2011 (UTC)

Deletion of foreign redirects
There's a redirect for discussion about foreign redirects: here. I'd really like to see a policy that makes sense on this, and I've stated it repeatedly and in my delete vote on that page. ''If something originated in that language, a redirect is valid, otherwise it is not. Voiture→car is not a valid redirect.'' If anyone wants to weigh in on that discussion, it may help for setting a policy. &mdash; Timneu22 &middot; &#32; talk 21:32, 1 February 2011 (UTC)


 * The situation here is a problem. Currently, R3 states that "Redirects from in other languages [are generally useful]." But no explanation is given, and the word "generally" is very forgiving and subjective. Several arguments are used against these unhelpful foreign redirects: they are very unlikely to ever be used (people wanting content in other languages are probably going to be browsing their language version of Wikipedia); they set a bad precedent (if allowed, it opens up the way for the creation of potentially millions of foreign redirects which are in all probability never going to be used); it is redundant to the interwiki linking system; and it is extremely difficult to maintain foreign redirects on a mainly English-speaking project (case in point: is "Fizbucket boo" -> "Wikipedia" an appropriate redirect? No. What about "Свеча аромат мыла" -> "Wikipedia"? Who knows, without going to the trouble of using an online translator). I believe this discussion has been had to death in the past, but the discussion at this RfD made me realise that there appear to be many people in favour of deleting "random foreign redirects", as well as a few against. So I decided to contribute here.


 * Perhaps we need a new CSD. The situation here is quite hard to pin down in a terse criterion, but here's an attempt (which might still be too general):
 * Redirects in a foreign language and/or writing system, where the subject matter of the target article is clearly not related to the foreign language and/or writing system (or, for redirects in foreign languages, any aspect of any country in which that language is spoken, broadly construed), and where the name of the subject described in the target article does not originate in that language and/or writing system.
 * (Just to be clear, this isn't a proposal with which I (personally) really have the time or patience to follow through; it's just an idea.) — This, that, and the other (talk) 09:46, 3 February 2011 (UTC)


 * There are so many generalities and exceptions to that I have to wonder why you think a speedy deletion criteria is needed? The merits of each individual redirect can be, and are, discussed at RfD. While foreign language redirects to unconnected subjects might not be useful or needed, they almost never going to be harmful such that discussing them for a week will be a problem (or, at least they are no more or less likely to than any other redirect). It has been suggested elsewhere (and this is at least the third concurrent discussion of which I'm aware) that proposes to presume that every redirect that someone has gone to the trouble to create manually is useful, and even if they aren't if they don't conflict with anything they aren't doing any harm so why go to the trouble of deleting them, particularly speedily. Any that do conflict or have other issues that prevent this general state of affairs applying will best be dealt with at RfD. As such I'd have to oppose any speedy deletion criterion for them. That a significant number of people object to their deletion should be a clue that speedy deletion isn't going to be uncontroversial, which precludes speedy deleting them. Thryduulf (talk) 21:12, 3 February 2011 (UTC)
 * Bots/Requests for approval/brest-bot regarding a bot to create redirects to articles from the equivalent titles in Macedonian may also be of interest. Thryduulf (talk) 21:15, 3 February 2011 (UTC)

Articles that meet notability guidelines
There have been a number of articles that don't "assert" or "indicate" importance in the text, but are backed up with citations to (obviously) significant coverage in independent reliable sources. Since such articles will always survive AfD discussions, it seems senseless to permit them to be speedily deleted. There is nothing in the notability guidelines about "assertion" or "indication" of notability, just reference to the actual criteria, which relate to the subject's coverage or other fact patterns&mdash;not text in the article.

I've tweaked the text at A7 to reflect this.

<sup style="color:green;">Bongo  <sub style="margin-left:-4.2ex; color:blue;">matic  07:22, 6 February 2011 (UTC)
 * Makes sense to me. Shame we actually have to say this, though, since the general instructions for CSD clearly support this: speedy deletion is only for things for which everyone (or everyone familiar with and understanding Wikipedia's inclusion policies, at any rate) agrees that no encyclopedia article should exist OR that there is a fatal flaw (G10-12) with what's currently there. Jclemens (talk) 07:53, 6 February 2011 (UTC)
 * I've always thought this to be implicit in both A7 and (per Jclemens) speedy deletion policy in general but there's absolutely nothing wrong with spelling it out explicitly. Also, mentioning notability as one of two ways to cross the A7 bar should draw attention to the distinction between "notability" and "claim to significance or importance", which in my experience is lost on a number of editors. So I agree with the change. --Mkativerata (talk) 07:56, 6 February 2011 (UTC)
 * I've always taken the existence of a source to be an inherent indicator or assertion. No harm in this change. Ged  UK  12:20, 6 February 2011 (UTC)

(In response to all.) I totally agree that this should be obvious, and it's a little pathetic to have to add the clarification. However, I've seen a number of speedy nominations (including a successful one today for Van Dykes&mdash;an admittedly lame stub sourced to a 6,000 word New Yorker dedicated solely to the topic) of articles that have been sourced to overwhelmingly meet the guidelines' hurdle. Moreover, the "assertion" language has crept into prod and AfD nominations, so this should help nip those in the bud. <sup style="color:green;">Bongo  <sub style="margin-left:-4.2ex; color:blue;">matic  14:54, 6 February 2011 (UTC)
 * Needs more discussion. I thought it was pretty obvious that something for which there is demonstrated notability will obviously and necessarily be of some importance or significance. However, I would not change the language in the way suggested, because the moment we accept the word "notability" into the guideline, people will list articles for speedy on the basis of not meeting WP:N, whereas the actual standard is intended to be a lot less. (That's not the real problem with deletions such as the one mentioned: the actual problem is that if there is no indication in the article, how far is the nominator or deleting admin expected to go to find one? I'd say they must at the very least look at any refs the article contains, but what if the refs do not contain any, but a cursory search would easily find them? I admit that I do not always look if there's nothing present and the situation looks borderline and I'm doubtful whether I will find anything,  though I will look if I think I can find something. ) Perhaps we need a rewording, but not this one. I predict that the effect would be the exact opposite of what is intended.   recall proposing a very similar change my first year here, but more experienced people explained this to me.  I have consequently reverted, and I think we need some discussion first about a proper wording. As for a wording, I think the effect would be better gained with almost  the exact opposite. It is not necessary to show the subject would actually meet a notability guideline.  , or perhaps the more elaborate  It is not necessary to show the subject would actually meet a notability guideline; merely an indication or credible assertion that there is some  importance of significance or notability is sufficient.     DGG ( talk ) 00:00, 7 February 2011 (UTC)

I always considered citations to reliable sources to be very literal "assertions of significance". There's no difference to me between saying, "this band was written up in a full page article by The New Yorker", and simply linking to the article, as far as A7 is concerned. I actually prefer it, because it avoids the awkward "X is notable because" phrase you sometimes see in stubs. Someguy1221 (talk) 00:47, 7 February 2011 (UTC)
 * I agree that more discussion is needed and that the language used was worse than what we currently have. To be honest the only way I can think of that an article could demonstrate that it meets the notability guidelines without asserting importance or significance would be if it included an external link that showed it met WP:N without asserting anything in the article text. We had a very recent discussion about this, and it didn't quite reach consensus. Personally I still feel that as soon as you start needing to look at anything external to the article to text to determine whether it asserts significance or not then it clearly doesn't. Thryduulf (talk) 00:53, 7 February 2011 (UTC)
 * Myself, when I look, I find enough about 25% of the time. But since I only look when I think it worthwhile, I estimate thats about 5% of the articles that would otherwise be deleted. That someone write an uncited unclear article on a notable topic is a very frequent occurance, and it doesnt't mean that it should be deleted, but used as a starting point, or at least as an indication to write something.    DGG ( talk ) 02:00, 7 February 2011 (UTC)
 * DGG, I think your point on the wording is well-taken. However, your edit summary (reverting the changes, not here) suggests (whether or not intentionally) that there isn't consensus that articles that fail to assert importance&mdash;but actually demonstrate (WP) notability should not be nominated for speedy deletion. I don't think that's correct.
 * Thryduulf, I considered adding this topic to the discussion above, but I don't think it's relevant. I'm not referring to articles whose subject is claimed to be important by third-party sources, I'm referring to topics that are the subjects of in-depth coverage in independent reliable sources&mdash;whether or not such sources describe the topics as "important". To pass the notability guideline, a topic doesn't need to be asserted to be important at all&either in Wikipedia or in a third-party source. The notability guidelines&mdash;even the subject-specific ones&mdash;all tie back to coverage, not descriptions as "important" (indeed the second sentence of WP:N states "Determining notability does not necessarily depend on things like fame, importance, or popularity.").
 * Here's alternative wording to the original tweak&mdash;welcome everyone's improvements.
 * An article about a real person, individual animal(s), organization (e.g. band, club, company, etc., except schools), or web content that does not indicate why its subject is important or significant. This is distinct from verifiability and reliability of sources, and is a lower standard than notability. 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. In addition, this criterion does not apply to to articles that demonstrate that their subjects meet Wikipedia's notability guidelines, even articles that fail otherwise to indicate why their subjects are important. moved Note: 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, software, or other creative works. This criterion does not apply to species of animals, only to individual animal(s).
 * Thoughts? <sup style="color:green;">Bongo  <sub style="margin-left:-4.2ex; color:blue;">matic  01:05, 7 February 2011 (UTC)
 * Far too many words. KISS.--Scott Mac 01:12, 7 February 2011 (UTC)

As the person who originally suggested "no assertion of notability" I'd resist any change in this. Firstly, guidelines are guidelines, and not policies. Personally, I don't read them - I'd rather take each article on its merits YMMMV. The point of "no assertion of notability" was that it ought (mostly) to be cut and dry - and not intended to do AFDs work for it. If the article doesn't contain any claim, which if true, would assert anything important about the person, then it may be speedied. Of course, the subject of the article might be notable, and it is just that the notability hasn't been mentioned - but that's by and by. If someone writes an artilce and can't tell us why the person is important, the onus isn't on the patroller or the reviewing admin to separate the article from the other 99 about someone's favourite uncle. The criteria has NOTHING whatsoever to do with sources - and I'd strongly resist any attempt to insert any instruction creep here. If we insert a source consideration, then we'll get it cutting both ways - because people will start deleting articles WITH unsourced assertions of notability - and retaining articles with sources but no assertion. The point about a speedy is the face of the article ought to tell you whether it qualifies, without looking at sources or guidelines. That means speedy decisions can be quickly standardised. Sure, articles with assertions of notability will get kept, even when the article fails the guidelines (that's a matter for AFD or prod, not speedy), and occasional articles lacking an assertion will notable despite that (but they can be recreated with the default remedied). No change here please.--Scott Mac 01:11, 7 February 2011 (UTC)
 * I agree completely with this. XfD is the main deletion process for Wikipedia, not speedy deletion. The criteria for speedy deletion must be "objective", "uncontestable", "frequent" and "non-redundant". I'm struggling to see how trying to add complex rules for the infrequent occasions when articles that fail to tell us why we should have an article about that subject but would meet notability guidelines if they did meets these requirements? As soon as you are trying to evaluate a whether a source is reliable or notable in itself then you fail the objectivity clause, complex rules are often struggle to be uncontestable and I've not seen anything that shows this is a frequent occurrence. If it's unclear whether something is making an assertion of importance or significance or not, send it to PROD or AfD. Thryduulf (talk) 02:28, 7 February 2011 (UTC)

We have WP:REFUND and WP:DRV to challenge any deletion don't forget.
 * CSD needs to do two things 1) shovel a lot of shit reasonably quickly. 2) leave things which have a reasonable probability of not being shit. These aims are sometimes in tension. The minute we require shit-shovellers to stop and assess sources on every crappy article "just in case" we're tipped the balance one way. The minute we start allowing people to shit-shovel an article on the grounds the sourcing seems poor, we've tipped it the oher way. No, keep sourcing out of it.--Scott Mac 02:37, 7 February 2011 (UTC)

Because notability is just about existence of sources, the inclusion of sources in an article is an assertion of notability. There is no requirement that the article has to say "This topic is notable because"; just putting in a reference to the topic of the article is a clear statement that there are sources on the topic. When I create articles, I make sure to include a source for exactly this purpose. For example, the inline citation to Kechris in Lusin's separation theorem is an assertion of notability. &mdash; Carl (CBM · talk) 02:55, 7 February 2011 (UTC)
 * This is very logical. Unfortunately, some editors do not adhere to the view that sourcing is an assertion of notability (and nominate articles that are sufficiently sourced to establish notability). The suggestion was to clarify that very point. <sup style="color:green;">Bongo  <sub style="margin-left:-4.2ex; color:blue;">matic  03:03, 7 February 2011 (UTC)
 * In that example I see two assertions of significance - that it has references to academic works (these are not the same (imho) as external links to random websites) and that it was proven by somebody notable enough to have a Wikipedia article. Either one gives it enough to pass the A7 bar without further investigation. Whether the references back up the claims in the article is not a matter for a patroller, if they have doubts they should tag it for AfD/PROD/bring it to the attention of a relevant wikiproject for investigation. Thryduulf (talk) 03:21, 7 February 2011 (UTC)
 * I agree. My point is that if there are even superficially plausible references, that should be enough for page patrol. It's not even necessary to look at the references - just the citation info itself can be a credible claim of importance. &mdash; Carl (CBM · talk) 03:27, 7 February 2011 (UTC)
 * I regard the above discussion can best be seen as a gloss or explanation of the traditional wording, but not a replacement for it.
 * But there is one point above to which i take the strongest exception. There is a difference between WP:V and WP:N. WP:V is necessary, but not sufficient for a Wikipedia article. In the other direction, the absence of immediate verification in a submitted article is not cause for rejection if there is reason to think that WP:V is possible and that there is some prospect of notability. There may be sources, and the sources may not indicate any importance. We may have any number of directory--type sources that refer to something, and establish that what is said about the person is true, but if what they indicate is true is insignificant, the person is not notable. (I can easily find a dozen such reliable sources for   even the author of a self-published book I c, and some will be secondary sources. (they will, of course, be neither discriminate nor substantial).
 * Consider the purpose of A7: the purpose is to remove as soon as possible those articles about whom it is clear that no WP article can ever be written. There are some cases we can tell easily: a band that has yet recorded no songs, a person who is still a junior high school student, a corner grocery. Unless there is something really special, none of these have a chance of having notability, not by the GNG, not by any other guideline, not by common sense--and anyone nominating for speedy and any admin looking at it will surely agree. These are what A7 is for. The current rule works very well for removing them. And for any notable band or business or person it will work very well for keeping them, because it it not possible that they can be notable and yet unimportant.  There are two problems: one is that the article might because of ignorance or carelessness not give an indication, but there may be evidence to be found if one looks; how to handle this will always depend upon how much work we are willing to do. .   The other is that in some cases it may not be at all clear whether what is indicated is possibly important: the model is an article asserting someone won a local amateur championship: the person may think it important, but we know that Wikipedia at present will not consider it important. It's a good faith assertion of notability , and might even be sourced--but the chances of a sustainable article is zero.   Where to draw the line here will always be a matter of judgement.  The guideline at present works very well if usedf properly. No guideline works if used as some use it, to mean "I don't think it's notable."  The present wording is the proper balance. Our job is to get people to follow it. And frankly, I see   few errors made with A7, except when the article is judged to early on. The errors are with G11, which has no firm criteria at all, for it depends how much rewriting one thinks is reasonable.
 * It is never a good idea to base a change in the speedy guidelines on a single isolated case--the multiplies and complicates rules, which are best kept simply. There is only one thing that must be made clear: what is needed to pass A7 is much less than notability, just something to tell us that an article might be possible.   DGG ( talk ) 04:05, 7 February 2011 (UTC)
 * DGG, the proposal is not based on an isolated case&mdash;it has occurred on multiple occasions. Moreover, the language here has insinuate its way into numerous AfD discussions, and (if my recollection is correct) even held some sway. If the confusion were limited only to speedy deletions&mdash;which can generally be undone quickly&mdash;I would concede the point. But it's not. <sup style="color:green;">Bongo  <sub style="margin-left:-4.2ex; color:blue;">matic  04:21, 7 February 2011 (UTC)
 * There is an argument in favour of the status quo (requiring an assertion of notability): it promotes the writing of better stubs. The author presumably has in their mind some idea of why their subject is important or significant: A7 as it stands should encourage them to write at least a sentence or two to share that idea with readers. JohnCD (talk) 18:31, 8 February 2011 (UTC)
 * I generally try to find a reason to keep an article, and I have found the existing wording of A7 sufficient to do so. The borderline cases that this might address are where something of importance to the person is indicated, but it is totally clear that it would not be of encyclopedic  significance.  The goal then is to avoid harm to the encyclopedia, and also avoid embarrassment to the editor or to the subject (actually, most of the times where this is relevant, the editor is  the subject & it is particularly necessary to not hurt his feelings: Do No Harm applies in dealing with living people at every level, and in every process). The editor needs a careful personal explanation, and the deletion accomplished without embarrassment.    I normally use the concept of "encyclopedic importance", by which I mean, is it something that a sensible person who has some idea of the nature of Wikipedia, could reasonably think might be suitable for inclusion?  If it's not, I use speedy. If so, I Prod, and advise the person to withdraw the article--usually they do, once they're told in a sympathetic way that it's outside our scope. People of good will recognize that we do have a limited scope, and that if they inadvertently write an article that does not fall within it, it will not be kept.  If they are stubborn about it and remove the Prod, they'll have to face AfD--there's no help for it.
 * The problem isn't the wording, it's admins who  look for every possible reason to delete an article. No change in wording will deal with that problem.    DGG ( talk ) 01:30, 12 February 2011 (UTC)

Templates, Deletion, and utter laziness
I don't know about other admins, but one of the checks I do when looking at a Candidate for Speedy Deletion is to check the history. If I want the deletion rationale to be pulled from the template, I have to click back to the article. Is there a way for the "Delete" function to pull the rationale from the template even if I'm coming straight from the history - Or from the Edit Page, for that matter? No idea if we've discussed this before, but it seems like a simple solution. UltraExactZZ Said~ Did 14:31, 10 February 2011 (UTC)


 * I usually use the middle mouse button (thumb one at home) in Firefox to open the history in a new tab. That way, you can simply close the history with a shortcut (or, lazy people like me, using a mouse gesture) and end back on the tagged page. And if you use CSDHelper or Twinkle, you don't even have to open the delete page. Just an idea of course. I don't know of any solution that works the way you describe it but maybe it can be integrated into CSDHelper/Twinkle if you ask the developer(s)? Regards  So Why  23:12, 10 February 2011 (UTC)

Deletion of css and js user pages
If this Help Desk post by is correct, can it be added as a note at "U1" on this page, and in the documentation for  itself? It's something that gets asked about from time to time. -- John of Reading (talk) 09:15, 7 February 2011 (UTC)


 * I'd rather recommend we add a note like "To request deletion of subpages where templates cannot be used (like .css and .js pages), add to your talk page with the request instead." It's easier than adding a category to those pages and less confusing, because admins might wonder why such pages appear in the category if there was no template on them. Regards  So  Why  09:48, 7 February 2011 (UTC)


 * Wouldn't simply blanking these pages have the same effect as deleting them? The only reason deletion might be needed is because some users create .css or .js pages because it's the only way a non-admin can create a page that can't be edited by other non-admins. I believe Timotheus Canens did this for kissle permissions before he became an admin. --Ron Ritzman (talk) 14:55, 7 February 2011 (UTC)


 * Someone who changed their mind about the Edit counter tool would need to delete, not blank, their EditCounterOptIn.js. I have added SoWhy's suggestion to the project page. -- John of Reading (talk) 16:19, 7 February 2011 (UTC)


 * Why would you not just put the CSD template on the talk page, like we do for all other deletion templates where the main page cannot be edited for whatever reason? <b style="color:forestgreen">Happy</b>‑<b style="color:darkorange">melon</b> 01:16, 8 February 2011 (UTC)


 * I think that templates do transclude on .js pages, but don't display properly. I remember having some odd behavior in a script that was resolved by escaping the templates' braces. I searched the WP:Village pump (technical) archives, but I didn't find anything. Flatscan (talk) 05:12, 9 February 2011 (UTC)


 * db-u1 will properly categorize a .js or .css page into Category:Candidates for speedy deletion by user. – xeno <sup style="color:black;">talk 14:38, 12 February 2011 (UTC)


 * Thanks for confirming, Xeno. I've revised the note to explain the behavior. Flatscan (talk) 05:25, 13 February 2011 (UTC)

Empty categories for deletion
The following categories have been empty for over a week but have not been deleted as yet: Category:Wikipedia articles in need of updating from August 2007 Category:Wikipedia articles in need of updating from December 2006 Category:Wikipedia articles in need of updating from December 2007 Category:Wikipedia articles in need of updating from January 2007 Category:Wikipedia articles in need of updating from February 2007 Category:Wikipedia articles in need of updating from July 2007 Category:Wikipedia articles in need of updating from June 2007 Category:Wikipedia articles in need of updating from March 2007 Category:Wikipedia articles in need of updating from May 2007 Category:Wikipedia articles in need of updating from November 2007 Category:Wikipedia articles in need of updating from October 2007 Category:Wikipedia articles in need of updating from September 2007 I'm not sure if there's a fault somewhere that has meant they haven't been listed anywhere. Hugahoody (talk) 17:47, 12 February 2011 (UTC)
 * Not sure what's going on there. I'd assume there's some sort of issue with either Monthly clean-up category or somewhere in db-g6, but I can't spot it quickly.  Anyway, I whacked 'em for good measure.  Cheers.  <i style="color:green;">lifebaka</i>++ 14:30, 13 February 2011 (UTC)
 * Thanks, Hugahoody (talk) 14:52, 13 February 2011 (UTC)

I have a few more: Category:Articles with trivia sections from September 2007 Category:Articles with trivia sections from January 2008 Category:Articles slanted towards recent events from February 2009 Category:Articles slanted towards recent events from January 2008 Category:Articles slanted towards recent events from June 2008 Category:Articles slanted towards recent events from May 2008 Category:Articles slanted towards recent events from September 2008 Category:Articles with sections that need to be turned into prose from February 2007 Category:Dead-end pages from December 2010 Category:Dead-end pages from November 2010 Category:Dead-end pages from September 2010 Category:Wikipedia spam cleanup from April 2009

Hugahoody (talk) 22:05, 14 February 2011 (UTC)
 * At a guess, the templates are sticking these in CAT:SD properly, because they were all nuked when I first saw this about twenty minutes after you posted it. Cheers.  <i style="color:green;">lifebaka</i>++ 23:36, 14 February 2011 (UTC)

A small expansion of G8
Last night, I came across List of Rural banks in Ghana, a list article consisting entirely of non-notable banks that don't, and never will have, articles. G6 already provides for deletion of disambiguation pages that are completely redlinked; should we expand G8 to include entirely redlinked lists? My proposed wording (in bold) would be something like; "Such as talk pages with no corresponding subject page; subpages with no parent page; image pages without a corresponding image; redirects to invalid targets, such as nonexistent targets, redirect loops, and bad titles; list articles where none of the articles it lists exist or have ever existed; and categories populated by deleted or retargeted templates." That's just a rough draft, and can absolutely be tweaked. Thoughts? The Blade of the Northern Lights ( 話して下さい ) 18:11, 15 February 2011 (UTC)
 * Works for me. – ukexpat (talk) 18:17, 15 February 2011 (UTC)
 * This proposal could create GFDL problems. It's related to a scenario that comes up on RfD with some regularity.  While I agree that we ought not to have a list of non-notable anything, the fact is that these lists are frequently created and sometimes they become the source material for a few examples which are later copied into a more comprehensive article.  Deleting the page destroys the pagehistory and obscures the attribution of the original content. A better solution in my opinion is to simply be bold and overwrite the list with a redirect.  (In the example above, the target might be Financial Services in Ghana or, since that page does not yet exist, Economy of Ghana.)  The attribution history is preserved, the list is removed from view and, most importantly, the redirect and its history serve as a continuing notice to future editors that we don't want such a list and quietly preempt its re-creation.  Best of all, it's a resolution that does not require admin intervention - it can be executed by any editor.  Rossami (talk) 18:46, 15 February 2011 (UTC)
 * In this instance, the page has no useful history, there's nothing even remotely useful for an article, and it's an unrealistic redirect. I'm not seeing how GFDL comes into play on this, any more than it would on a redlinked disambiguation page.  The Blade of the Northern Lights  ( 話して下さい ) 18:52, 15 February 2011 (UTC)
 * (edit conflict) I do not think that this specific instance is a sufficient example for the general principle. It's too simple a case since, as noted above, Financial Services in Ghana does not yet exist. Mining in Ghana, on the other hand, does exist and includes a number of references to specific companies. The attribution history of that page does not make clear where the content came from but it's plausible that at least some content was first in a parallel "list of" page. (Maybe GSE All-Share Index?) We've seen similar editing patterns in the merger and later redirection of "list of songs by XYZ" pages, "list of supporters of political candidate ABC", "list of glossary terms", etc. Fictional topics seem especially prone to this kind of pattern. It's theoretically possible to have the same problem with a redlinked disambiguation page but I can think of no examples where the editing followed that pattern on a page marked as a disambiguation page. Again, this is not a defense of this specific page above - just a concern that the example does not generalize to a universal rule. Rossami (talk) 19:20, 15 February 2011 (UTC)
 * Unnecessary. AfD and PROD can easily handle the load, there's no need to speedy articles such as this.  Cheers.  <i style="color:green;">lifebaka</i>++ 19:07, 15 February 2011 (UTC)
 * Agree. Also, I do not think a single admin is able to determine whether no articles can be created from those red links. After all, per WP:REDLINK such links should serve to instigate users to create those articles. So speedy deletion is probably neither appropriate nor needed to handle those article. Regards  So Why  00:09, 16 February 2011 (UTC)
 * I appreciate and agree with the intent behind this proposed changes, but this is not a very common occurrence and therefore outside the scope of speedy deletion. Beeblebrox (talk) 00:27, 16 February 2011 (UTC)

T4 proposal
To reduce the load at TfD, I propose a T4 criterion for unused templates. Templates must meet these criteria:


 * Must not be transcluded on any non-userpage.
 * Must not be orphaned via process (TfD). (just like C1)
 * Must not be orphaned through the use of substitution on more than one page.
 * Must be over 1 month old
 * Must not be a template designed for use by substitution.
 * Must not be an administrative template that becomes orphaned by nature.
 * Creator must be notified, anyone can object by using the template and removing the tag.
 * Template must be tagged for a week
 * Any user can request restoration, provided that he/she state what page it is to be used on.

I know this sounds a lot like a template PROD, but unless a complete new process is created, I believe it belongs under CSD. WP:DOT can remain with some changes, as there still needs to be a system to identify which templates shouldn't be used anymore. What do you think? &mdash; Train2104 (talk • contribs • count) 20:23, 15 February 2011 (UTC)
 * I do see a couple of templates this would cover over in TfD at the moment. I'm not 100% convinced it's necessary, but neither do I see how a criterion with this intent could hurt all that much.
 * One little change I would like to make is in the first requirement. Rather than requiring that the template is not transcluded on any non-user page, I would prefer that it not be transcluded on any page.  There are templates which are designed solely for use on user pages, which we want to keep (such as userpage), and I would prefer not to make a criterion like this easy to be misused.  Any templates currently residing in the templatespace with userspace transclusions, which shouldn't be in the templatespace, should be moved rather than deleted.  Cheers.  <i style="color:green;">lifebaka</i>++ 20:37, 15 February 2011 (UTC)


 * This criteria is way too complex for CSD. However the combination of a 7 day process and anyone being able to request restoration makes this a prod not a CSD. So I'd suggest you make this a template prod proposal.  Ϣere Spiel  Chequers  02:24, 16 February 2011 (UTC)

Rewording G10
It seems from and  that we as a community want G10 to be broader than it is. How would people feel about removing the word "entirely" from the phrase "entirely negative in tone and unsourced" ? JoshuaZ (talk) 04:00, 10 February 2011 (UTC)
 * Considering WP:BLP, "entirely" is not necessary.  Corvus cornix  talk  05:04, 10 February 2011 (UTC)


 * Disagree. If there is non-attack content to be preserved, the content can be deleted, and even revdeleted as necessary.  There's no need to remove the word entirely from this because CSD criteria should always be interpretted as narrowly as possible, and broadening this criterion only makes it more ambiguous as to when it should be appropriate.  Leave it as it is; if an article contains a mix of attack text and good text, excise the bad and leave the good.  -- Jayron  32  05:12, 10 February 2011 (UTC)
 * Remember that the long text of G10 is just an amplification of the short criterion ("Pages that disparage or threaten their subject or some other entity, and serve no other purpose"). The examples given are just that - examples, not restrictions on what can be deleted under G10. The real issue here is article content that would be acceptable (assuming notability) in a sourced article, but is an attack when found in a completely unsourced one. I know what my opinion of that is - unsourced biographical articles should go, full stop - but given that the community has a spectrum of opinions on this, the question is whether such articles can exist in a state where they are waiting for sources that may not arrive. I'm not sure this fits squarely under the present G10 criterion, and so I opined in the relevant AfD that it didn't seem to apply, technically. I would like to see such things made deletable under some criterion. — Gavia immer (talk) 05:14, 10 February 2011 (UTC)
 * If we're still talking in the hyperspecific here, about the "porn actor" example, the issue with that specifically is that porn actor isn't an unambiguous attack, in the was that say "murderer" would be. Everyone considers murder a crime.  There are, however, varying opinions on whether performing sexual acts for money is, of itself, something which carries necessarily negative connotations.  I'm not sure that it does.  That someone thinks it is disparaging of the subject is obvious; however I doubt that everyone would think that.  As such, I don't think changing the language of this criterion merely because we can't all agree on whether or not pornography is unambiguously a negative thing to be associated with is really a great course of action.  It's usually a bad idea to make systemic changes based on small, inconsequential ambiguities like this.  -- Jayron  32  05:31, 10 February 2011 (UTC)
 * I agree. Also, I think WP:BLPPROD can handle such articles in most cases for exactly the same reason. If it's really clearly disparaging, G10 covers it. If only parts are, it doesn't, because you can remove those parts instead. No need to change the criterion though. In this case policy was simply not applied correctly and now there is a perceived need to change policy - there isn't. I just read the article in question and most of it was not defamatory or negative in tone. The correct way would have been to remove those parts perceived as such and tag the rest as WP:BLPPROD or A7. Regards  So Why  10:45, 10 February 2011 (UTC)
 * That's really splitting hairs though. If I removed all BLP-violating content from this revision, I have essentially blanked the article. If I then delete it per WP:CSD, isn't that gaming the purpose of A3? And what then is the difference between that and immediate deletion per WP:CSD? <b style="color:navy;">NW</b> ( Talk ) 14:27, 10 February 2011 (UTC)
 * Perhaps I am missing something, but as far as I can see, the revision would still contain a claim to significance and a filmography, enough to make the page pass all the speedy deletion criteria.  (talk) 15:44, 10 February 2011 (UTC)
 * Yes, I don't think that qualifies as an A3 deletion. Paul Erik  (talk) (contribs) 15:53, 10 February 2011 (UTC)

I don't think we need to change G10's wording. There's IAR, there's BLP, and there's common sense. If someone removes a speedy tag from a potentially libelous BLP without bothering to remove the offensive material, then I say restore the tag, remove the content, and trout the removing user. / ƒETCH COMMS  /  16:03, 10 February 2011 (UTC)
 * Or block him if truly egregious or repeated issues arise. Jclemens (talk) 03:09, 11 February 2011 (UTC)

Proposed new criterion A11
Tacking this onto CSD G10 isn't a good idea, since it invites endless disputation concerning whether unsourced claims of participation in the production of adult entertainment constitute "attacks", and similar issues. At the same time, extreme BLP violations clearly merit speedy deletion. As this is a frequently recurring problem, the propriety of such deletions should be codified in the CSD. Recourse to IAR should be limited to uncommon circumstances which policies cannot anticipate, or where the policy violation is trivial, which isn't relevant here, since deletion is a big deal. A possible wording:
 * A11: An article in which every page revision is comprised entirely of unsourced, unreliably sourced, or original research controversial material directly relating to specific living people, or could be speedily deleted under another criterion after removal of the same. Chester Markel (talk) 01:57, 11 February 2011 (UTC)


 * Redundant: If it could be deleted under another criteria then why the new criteria?!? We already have WP:BLPPROD and the other CSD criteria.  Which articles which should unambiguously be deleted speedily would this criterion cause to be deleted which would not under existing criteria?  -- Jayron  32  02:04, 11 February 2011 (UTC)
 * While one could, in principle, remove the BLP violations in an article, then immediately delete it under CSD A7 or a similar criterion, this is likely to be seen as a form of gaming, especially since the CSD are generally only used when every revision of an article meets the criterion. In most cases, an admin blanking an article in its entirety, then immediately deleting it per CSD A3, would have to contend with many disgruntled editors. In any event, the removal of serious BLP violations should not be made contingent upon an admin jumping through procedural hoops of editing an article to render it more deletable. The matter is of sufficient importance that it should be a simple, straightforward application of the CSD. BLPPROD isn't an adequate remedy, since such deletions can only be performed ten days after tagging the article. Unsourced articles making controversial claims about living people should be removed yesterday. The language "could be speedily deleted under another criterion after removal" of the BLP violations is necessary to avoid end runs around the CSD, by inserting trivialities into the article so that it isn't comprised entirely of unsourced controversial material. Chester Markel (talk) 03:03, 11 February 2011 (UTC)
 * Do you have any examples of articles where this deletion criteria would be useful, as I requested above? This looks surprisingly like a solution in search of a problem.  I'd like to see some data, some actual articles which would not have been speedily deleted under another criteria, but could under this one, where such a speedy deletion would be unambiguously needed.  That is, show everyone the actual need for this crtierion.  I am not opposed to new criterions where evidence shows they are needed.  But I am opposed to new criterions just for the sake of dealing with hypothetical problems which may or may not be actual problems... In other words, I would be perfectly willing to support this idea if you can show (rather than tell) where it is needed.   -- Jayron  32  03:16, 11 February 2011 (UTC)
 * The former article on "Tina Mai" clearly required immediate deletion, fits my proposed criterion precisely, and was not effectively handled by the present CSD: the article was tagged for G10 speedy deletion, untagged, and eventually deleted only after an extended discussion over whether and how it could be speedied. Chester Markel (talk) 04:42, 11 February 2011 (UTC)
 * No, it didn't. Simply saying so does not make it true. The problematic material could have been removed (WP:REVDEL anybody?) and the rest tagged with WP:BLPPROD, couldn't it? Once the material deemed problematic is gone, the need to remove the article immediately vanishes as well. Regards  So Why  07:39, 11 February 2011 (UTC)
 * Perhaps in some alternate universe, in which all controversial material which violates WP:BLP because of poor or non-existent sourcing could be revision deleted. However, on this Wikipedia, revision deletion criterion 2 only covers the subset of BLP violations that are also "Grossly insulting, degrading, or offensive material". (Some limitation on the scope of BLP violations that can be revision deleted is fairly obvious, since overzealous administrators might otherwise start blowing away article revisions which they found to give undue weight to sourced negative material, etc.) We'd have the debate linked at AN/I all over again, except this time, instead of debating whether an unsourced claim of participation in the production of adult entertainment constituted an "attack", we have would have an argument over whether the same material was sufficiently "grossly insulting, degrading, or offensive" to be the sort of BLP violation that could be revision deleted. Opinions would vary as a function of the discussion participants' views on adult content itself. Chester Markel (talk) 03:42, 14 February 2011 (UTC)

Alternate proposal: Modify A7
After examining my own arguments and the discussion above, I think the "attack page" nomenclature is a diversion from the real issue. We can crystallize the major point as follows: when a new article contains assertions of importance that are also BLP violations ("contentious unsourced material"), then the BLP violations should be removed. It's clear enough from various discussions that referring to such articles as "attack pages" in the general case tends to be controversial - but material that violates BLP should still be removed. That can lead to a situation where BLP surgery leaves an article that meets the letter of A7 or even A3, but only "artificially" - it can be clear that the creator of the article meant for there to be an assertion of importance, but that assertion of importance was removed for violating other content policies that don't necessarily mandate deletion of the article. The fix would seem to be to cut the Gordian knot and simply declare that BLP-violating "contentious unsourced material" is not acceptable as an A7 "assertion of importance" even while it is contained in the article.

For reference, here's the current text of the second part of A7 (a footnote distinguishing A7 "importance" from "notability" is omitted):

I propose that this be changed as follows (removed text struck through, added text bolded):

This would not prevent the theoretical creation of a new article on, say Jared Loughner, because the claim of importance would be contentious but sourced. Likewise it wouldn't allow A7 deletion of an article like "Joe Blow is an award-winning journalist who personally shot and killed John F. Kennedy", regardless of whether such a new article should be deletable, because if you removed the BLP-violating material you would still have a claim of importance that meets A7. It would allow articles like the one that started this discussion to be deleted, because the only claims of importance were unsourced contentious material, and the only material that didn't violate BLP amounted to "so-and-so is a person", which doesn't meet A7.

It will be noted as an objection to this proposal that it amounts in practice to speedy deleting articles simply for not having sources, since sourced material wouldn't violate BLP, and we have never required sources in new articles in order to avoid immediate deletion. To that objection, I will simply note that we do require sources in new BLP articles; articles that don't have them can be deleted via sticky prod. This proposal would allow a narrow subset of articles eligible for the BLP prod to be deleted sooner rather than later, but it would not suddenly make them more subject to deletion, since they already are.

It will also be noted that this would make A7 dependent on a separate policy page that could change - but WP:BLP is a mature core policy that is unlikely to change dramatically. Everyone knows what is actually meant by that policy; it just happens to be too long to repeat it in its entirety inside the A7 criterion. An attempt to manipulate BLP policy in order to manipulate A7 would be noticed immediately if it actually resulted in a change in how A7 was applied. Moreover, there is broad support for deleting BLP-violating material regardless; all this proposal does is avoid a current collision between two policies related to deletion of material.

Any thoughts? — Gavia immer (talk) 06:10, 11 February 2011 (UTC)


 * I have to re-state what Jayron stated above. This seems like a solution to a non-existing problem and it's a solution that the community (for very good reasons!) rejected multiple times. The last time we had this discussion, WP:BLPPROD was created to address those articles. A solution, that satisfied most people, both supporting and opposing a radical deletion of unsourced BLPs and thus gained consensus. If you propose a change that effectively nullifies this consensus with respect to such articles, then you need to also show why the current mechanisms in place to deal with such articles are insufficient. Moreover, your example proves my point. As I stated above, the article that started this discussion, could have been handled perfectly well with the existing processes: Remove the contentious material (possibly revdelete it) and tag the article with a sticky PROD (since there is sufficient reason to believe that sources possibly exist and thus A7 should not be used). So where exactly is the need for a change? In fact, if one were to change A7, I would suggest to add a simple sentence like "Use BLPPROD instead if the claim of importance has been removed as an unsourced claim that violated WP:BLP". Regards  So Why  07:33, 11 February 2011 (UTC)
 * BLPPROD is nice, but what of articles that are very barely sourced (IMDB, perhaps a sentence or two is sourced) enough so that BLPPROD doesn't apply. And what of the articles created before March 2010, to which BLPPROD isn't allowed to be used on? <b style="color:navy;">NW</b> ( Talk ) 21:27, 11 February 2011 (UTC)
 * For the small number of articles that are that poorly sourced which are neither speedy deletion candidates nor suitable for BLPPROD there is an apparently little valued process by the name of "AfD" that is perfectly set up to handle the cases that fall between the cracks of other processes. Thryduulf (talk) 21:46, 11 February 2011 (UTC)
 * Ah, you mean a process that will unnecssarily take (a) week(s) to handle a straightforward case? I think I'll just be citing BLP in any further deletions I make where G10 doesn't fully apply, and people shall be free to request undeletion if they are willing to immediately improve the article. <b style="color:navy;">NW</b> ( Talk ) 22:31, 11 February 2011 (UTC)
 * You know I like you, NW, but that's simply the wrong way to do it. If G10 does not apply, you should not use it, not as a tagger and certainly not as an admin. A number of users and admins, as this discussion shows, have, in their belief that speedy deletion should handle content problems, started a trend to request changes to perfectly fine working policies for reasons they cannot adequately explain. Take your example for instance: As an article, all content policies and guidelines apply to it. It's sourced to IMDB? Remove the source and the contentious material sourced to it - WP:V allows you to do so and has always done so. Then tag the rest, that now does not contain material harmful to a living person, as BLPPROD. If it's an older article, use regular PROD or AFD, as Thryduulf points out correctly. If an article exists for a year and longer (pre-March 2010), then another week will not change much. But it might allow people to rescue the article when they see it discussed for deletion, thus potentially saving us valuable information. The problem imho is that a low but significant number of users and admins has come to the conclusion that CSD is a regular deletion process - it's not. Community consensus, for as long as Wikipedia exists, was and is that deletion discussions are the regular way to handle deletions. No admin should ignore this consensus (and the policy that describes it) just because they think it's "unnecessary" or because they think it's a "straightforward case". We had plenty of examples where "straightforward cases" turned out to be problematic and in need of discussion. Which is also the reason why we have to criterion that says "Admins can delete stuff if they think discussion is unnecessary". As such (TLDR): Use G10 when it fits but when it doesn't, use the tools in place to handle such articles. There is neither need nor justification to ignore the restrictions of the speedy deletion policy (especially not this policy where any subjective reasoning by admins will reflect badly on the project as a whole) when existing policy covers the problem just fine. Regards  So Why  00:03, 12 February 2011 (UTC)
 * I have yet to come across an article that needs speedy deletion that could not be appropriately deleted under the existing criteria. Whether the statement that a person is notable as a porn actor is disparaging depends on the context. If no  indication is given that the person is in fact in that line of work, the only safe assumption is that it might be intended as disparagement; it is the sort of thing that ill mannered people say of their friends or enemies, and we must always delete it. If there were literally no other context, I'd use A1, as we have no real idea of the person indicated.  It's very easy to see on Google if there is some evidence that the person is involved in porn--and in that case, it's a credible non-disparaging statement.  The BLP policy is sufficient to delete any questionably BLP, and I think we generally do just that already. Those that get by do so because they're not looked at carefully, not the lack of rules to remove them  DGG ( talk ) 01:36, 12 February 2011 (UTC)
 * Surely you jest. In this discussion there was an extended argument over whether a statement that a person is notable as a porn actor, not backed up by reliable sources and with no RS available via a straightforward web search, constituted an "attack". The offending article was eventually deleted as a BLP violation, but only after the deletion tag had been removed, and a debate over whether the page could be speedily deleted, and, if so, under what criterion. Above, editors are still arguing that the article didn't require speedy deletion at all. There clearly is an active dispute over whether articles can be speedily deleted because they violate WP:BLP by including unsourced (and, in the case referenced above, probably unsourceable) controversial material about living people. Chester Markel (talk) 03:55, 14 February 2011 (UTC)
 * If there is an active debate about whether something is eligible for speedy deletion or not then it isn't. Speedy deletion is only for cases where deletion it is non-controversial and everybody agrees that it would be deleted at AfD regardless of the individual details. The existence of a debate about whether it should be deleted or not proves that this is not the case. 09:36, 14 February 2011 (UTC) — Preceding unsigned comment added by Thryduulf (talk • contribs)
 * Exactly. And while you keep on saying that they should be speedy deleted, you have so far failed to show why removing the offending material instead wouldn't work. Regards  So Why  14:41, 14 February 2011 (UTC)
 * I have, and you've ignored it. While speedy deletions are generally uncontroversial, arbcom recognizes that administrators such as yourself seek to include articles founded with BLP-violating inadequately sourced material about living people in Wikipedia, for at least seven days until AFD discussions are concluded. Additionally, WP:BLP itself provides that "If the entire page is substantially of poor quality, primarily containing contentious material that is unsourced or poorly sourced, then it may be necessary to delete the entire page as an initial step, followed by discussion" at deletion review. Codification of the legitimacy of such deletions in the CSD simply encourages more admins to step up to the plate, and avoids the need to continually warn other administrators that they may be desysopped for unilaterally restoring controversial material removed for a violation of BLP source requirements. Chester Markel (talk) 04:10, 15 February 2011 (UTC)
 * Erm, is this not exactly what WP:CSD is for? If removing the offending material would not leave a viable article and there is no version of the article that is suitable for Wikipedia it can be speedily deleted under G10. If there is a previous version of the article that is not a BLP violation or removing the information would leave an article that is viable then the offending material can be removed/reverted (along with revision deletion if necessary) and the article can be discussed at AfD/BLPPRODded without causing any BLP issues. Thryduulf (talk) 11:14, 15 February 2011 (UTC)
 * Exactly. Your argument above (which I meant to reply to, sorry for forgetting) basically was "The community does not allow a single revision with such content to be deleted, that's why we need a way to delete the whole page instead". As this (slightly pointy) summary shows, you made your argument just weaker, not stronger. If there is no consensus to delete a single revision of a page, why should there be consensus to delete the whole page including non-violating revisions? As Thryduulf points out, there is no discrepancy between WP:BLP and speedy deletion criteria. The page can already be deleted if it completely violates WP:BLP and if it doesn't, even WP:BLP says that [p]age deletion is normally a last resort. If a dispute centers around a page's inclusion (e.g., because of questionable notability or where the subject has requested deletion), this is addressed via deletion discussions rather than by summary deletion. Summary deletion is appropriate when the page contains unsourced negative material or is written non-neutrally, and when this cannot readily be rewritten or restored to an earlier version of an acceptable standard. (emphasis added) There simply is no justification in WP:BLP to speedy delete a BLP-article when all the contentious material has been removed and as said above, there is no need for it as well. Regards  So Why  15:21, 15 February 2011 (UTC)
 * The revision deletion criteria are understandably designed for use on articles which should not be immediately deleted in their entirety, and therefore contain an explanation of the subject's notability without any inadequately sourced controversial information concerning living people. In such a context, there is little motivation for readers to go digging through the page histories to determine what the articles are "really" about, and no need to delete every BLP-violating revision. The situation presented by an article which has been rewritten in essentially empty form to remove a BLP violation, because editors can't agree whether the unsourced controversial information is also negative or an attack, is quite different. "John Doe is a person.[citation needed]" is such a ridiculous parody of an acceptable article that any reader with even a minimal level of wiki-sophistication will review the page history, and determine the actual subject. For this reason page blanking as a method of deletion has been unequivocally rejected by the community, and is only an acceptable method of removing articles with fundamental violations of the BLP source requirements for controversial material if BLP itself is deemed to be of little importance. Chester Markel (talk) 14:25, 16 February 2011 (UTC)

A7 and sources
I have a question about the relationship between GNG (and other "multiple reliable sources" notability criteria, such as that in BAND), on the one hand, and A7 on the other. A7 says, in pertinent part:"An article ... that does not indicate why its subject is important or significant. This is distinct from verifiability and reliability of sources, and is a lower standard than notability. ... 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.(Emphasis added.)"My question is about articles which unquestionably make no claim of significance or importance in the text of the article, but which: To turn this into a question: If an article makes no claim of significance or importance in its text but cites a bunch of sources, some of which are (or may be) reliable and relevant, does that save it from A7 tagging and deletion? By saying, "This is distinct from verifiability and reliability of sources, and is a lower standard than notability," A7 may say that it does not.
 * Clearly meet GNG by having multiple reliable sources, or
 * (and this is the main point of my inquiry:) Have one, but only one, reliable source, or
 * Have multiple sources which if they were reliable would be good sources, but which are all clearly unreliable, or
 * Have multiple sources which are of unevaluated or questionable reliability.

My personal feeling is that in light of the "if in doubt, don't delete" nature of CSD: ought to constitute a credible claim of significance or importance that ought to disqualify the article for speedy deletion even if no such claim is made in the text of the article, provided that such sources are on relevant, significant points. (By the latter I mean, for example, that if the article is about XYZ, a company in the widget industry, the sources must be about XYZ, not about widgets or the widget industry, and must say something about XYZ other than its basic information, existence, goals, mission, etc.)
 * a single clearly–reliable third-party cited source, or
 * two or more third-party sources which are of questionable reliability but which are not clearly unreliable, or
 * satisfaction of GNG

I've seen articles from which I'd like to remove the CSD tag with an edit summary saying, but I've been reluctant to do so. Should I be?
 * "Removed A7 speedy tag; having a single reliable source indicates significance or importance" or
 * "Removed A7 speedy tag; multiple potentially-reliable sources indicates significance or importance",

Best regards, and thanks, <font face="Trebuchet MS" size="2" color="blue">T RANSPORTER M AN  (<font face="Trebuchet MS" size="1">TALK ) 17:14, 16 February 2011 (UTC)
 * I've declined A7 on things that have sources, but my gut feel is that things which have clear sourcing aren't tagged for A7 too often at all. Remember, anyone who in good faith doesn't think a speedy deletion criterion applies can remove the tag, so you would have been entirely within your rights to remove those A7s. The reason I don't do that more often is that I don't do speedy deletions as often as I used to. Jclemens (talk) 17:39, 16 February 2011 (UTC)


 * Imho, having one or more possibly reliable sources is an indication of importance/significance. Nowhere in A7 it says that the claim has to be in the text after all. As such, I have often declined such taggings in the past. I agree with you that it would be against the spirit of speedy deletion to delete a page just because the claim was not made in the text itself. Regards  So Why  17:41, 16 February 2011 (UTC)


 * it depends what the source is and what it says. If someone gives a few cites from local papers from G News for a band and it turns out they are one line mentions of performances, it does not show  any plausible possibility of notability. I would speedy such an article without hesitation if it claimed nothing more, but of course after checking myself that there was nothing more. A reference is always a reason to check, rather than react instantaneously.  I think the wording should better be "having a single substantial reliable source" .   It is also correct to remove a speedy with the reason "references suggest it might possibly be significant or important." which is the wording I use when necessary; actually, no reason is necessary, but it always helps to give one and I always do--it will give the nominator some reason to check before going immediately to AfD .  But as Jclemens says, it is rare to find reliable references on articles otherwise speediable for A7.  I think we would do better not to complicate the criterion. When I became an admin here 3 years ago, there seemed to be about 20% incorrect speedy nominations and 10% incorrect actual speedy deletions; I think the number now is more like 10% and 5%, which is still too many, but it may not be practical to reduce the error rate much further in a system like ours.   Most people do recognize that a claim or indication of any reasonable sort is sufficient. The exceptions seem to be often pointy, and no wording will discourage them. At this point, I'm more concerned with what the NPP misses than what it incorrectly tags. We can catch the incorrect tags, but we may never notice the misses.    DGG ( talk ) 17:56, 16 February 2011 (UTC)


 * Just FYI, an example of one that I didn't think made an acceptable indication in the text but which did have one reliable source. Thanks to all of you for your comments, they are very helpful, indeed. Best regards, <font face="Trebuchet MS" size="2" color="blue">T RANSPORTER M AN   (<font face="Trebuchet MS" size="1">TALK ) 18:16, 16 February 2011 (UTC)


 * For totally missing the "Articles that meet notability guidelines" discussion above on this page (!!!) before posting this question and response. I award myself a [[Image:Rainbow trout.png|20px]] self-whack!. [[Image:Blush.png|16px]] Cluelessly, <font face="Trebuchet MS" size="2" color="blue">T RANSPORTER M AN  (<font face="Trebuchet MS" size="1">TALK ) 21:58, 17 February 2011 (UTC)

Propose expansion of A9
Why is CSD#A9 limited only to music? Why not creative works in general?

I frequently see articles (recent example: Canadian Dream) about a film, book, video, etc. that should be candidates for speedy deletion but aren't because A9 is too specific. ~Amatulić (talk) 07:03, 14 February 2011 (UTC)
 * Part of the reason is that the consensus regarding authors/books and musical artists/musical works is different. For example, it is not uncommon for notable books to be written by non-nontable authors, but one of the thresholds for notabability of a musical recording is that the artist has an article. For this reason the criteria for musical recordings are not suitable for books. I suspect that it would not work for films/video either as these are not tied to a single person in the way books/musical records are.
 * This is not to say that speedy deletion criteria could not be written for these subjects (I have no idea either way about the necessity), but it would be one or more new criteria not an expansion of A9. Thryduulf (talk) 09:44, 14 February 2011 (UTC)


 * A9 serves to get rid of articles that were created for A7 bands - an album by a MySpace-band for example. Unlike those subjects, articles about other creative works are not created often enough to justify speedy deletion and as Thryduulf says, there is not the same link between those subjects and their creators and such subjects may well be significant when their creators are not but it's much harder for a single admin to be able to judge this correctly. PROD and AFD can handle those subjects quite well. Regards  So Why  14:39, 14 February 2011 (UTC)


 * Yes, I know PROD and AFD are alternatives. I come across articles that I am 99.9% certain would be deleted anyway in an AfD discussion, but I don't delete them because there isn't an "official" rationale available. AfD is already overloaded; one reason that speedy deletion exists, I thought, was to reduce the burden on AfD.
 * I guess A9 could be expanded to include anything that requires an article to exist on the subject of the creating entity or work. Fictional characters come to mind as one thing that could fit in A9. ~Amatulić (talk) 17:54, 14 February 2011 (UTC)
 * How many such articles go through AfD on any given day, though? <i style="color:green;">lifebaka</i>++ 18:13, 14 February 2011 (UTC)


 * Fictional characters and similar subjects were proposed in the past and rejected every time. With most of those subjects, redirecting or merging are usually preferable anyway. Those where redirecting or merging does not work are the minority and can be handled by AFD just fine. Regards  So Why  20:06, 14 February 2011 (UTC)


 * Yes, fictional characters that have no article to merge into can be handled by prods or AfD just fine. I am wondering why the burden of AfD is acceptable for articles that clearly wouldn't stand a chance. You might answer, "the numbers are so small!" Well yes. But for an AfD, someone has to nominate it, others have to respond, someone has to close the discussion, and by the time the article is deleted, probably a collective hour or two of human life has been expended on something that could have been dealt with right up front. ~Amatulić (talk) 23:08, 14 February 2011 (UTC)


 * You're looking at it the wrong way. AfD is the norm and there has to be a good reason why it is not required for certain narrowly defined scenarios. If you can come up with a narrowly defined criteria that is objective, specific, not redundant and wont generate false positives; and show some evidence that such a criteria is actually needed then by all means propose it. I'd recommend though looking for some of these past discussions and seeing what the arguments against were. They will almost certainly be brought up again, and if you have no answer as to how or why they are not relevant to this proposal, otherwise it will fail and you'll be wasting your time. Thryduulf (talk) 03:36, 15 February 2011 (UTC)

Ultimately, there's always criterion G13. Like any application of this criterion, it should be applied sparingly and when in doubt discussion should be defaulted to. But really, it doesn't take a week to say that a turd is a turd and needs flushing, even when it doesn't meet rule ABC6582959. If you don't want your articles quickly flushed, don't write a turd. Seraphimblade Talk to me 04:53, 15 February 2011 (UTC)
 * WP:IAR should never be used as the reason to speedily delete anything. The reason for this is that WP:CSD (and WP:OFFICE) list every circumstance in which there is consensus that a page may be speedily deleted. Thus when you use WP:IAR to delete something speedily, by definition your actions are not supported by consensus and are thus not eligible for either speedy deletion (where actions must be uncontroverisal) nor IAR (as actions taken with this justification must improve Wikipedia, and deleting something without consensus does not improve, and indeed harms, Wikipedia). If something is harming Wikipedia then it can be speeidly deleted by one of the existing criteria, if something is not harming Wikipedia there is no need to speedily delete it. Using WP:IAR as a reason to speedily delete something allows any admin to delete anything they want deleted at any time (the entire reason we have deletion discussions and speedy deletion criteria is to stop this). Thryduulf (talk) 11:04, 15 February 2011 (UTC)
 * Thryduulf beat me to it but I will say it as well. An appeal to IAR is a sure sign that the speedy-deletion was invalid and that one of the other processes should have been used instead.  Allowing IAR as a speedy-criterion puts far too much power in the hands of one person and, to be blunt, our own history has repeatedly demonstrated that as individuals, we are remarkably bad at identifying "turds".  (That's why, for example, apparent hoaxes are not speedy-deletable.)  As a group, we are much more effective at sorting the wheat from the chaff but that process takes time.  Hence, the VfD process (now XfD). Wikipedia is not a bureaucracy but Process is important.  Consistent application of our own processes and self-imposed controls is an important part of maintaining the credibility of the project and also as a continuing sign that we welcome the donated hours of our volunteer editors.  Rossami (talk) 14:55, 15 February 2011 (UTC)
 * I agree with those statements. Speedy deletion was never meant to replace deletion discussions entirely and admins were never appointed with the power to delete anything they think should be deleted. As Rossami says, many admins have abused IAR to delete what they thought were "turds" when there was never consensus for them to do so. That said, I would not be as definitive as Thryduulf is. While there had been no example where speedy deletion was required but not allowed by WP:CSD yet, we cannot rule this possibility out completely. There might be an example one day which has to be deleted immediately but where none of the criteria fit and in that case, IAR would be valid. Those cases Seraphimblade mentions are no such examples though, in fact, they are the opposite: The community has explicitly considered allowing such speedy deletions and then decided against it. If you use IAR in such cases, you abuse it. Regards  So Why  15:06, 15 February 2011 (UTC)
 * Although I started this thread, I have to agree that invoking IAR is a bit over the top for speedy deletions. I don't recall having to invoke it for any other reason yet, either. ~Amatulić (talk) 00:20, 16 February 2011 (UTC)
 * With what we have currently, such examples are indeed rare (and applications of IAR should be rare, if you're invoking it all the time, it means either the rule is wrong or you are, and that either the rule or what you're doing needs a change). I don't think I've ever actually done an IAR speedy, and I may well never come across an occasion to do so. But I wouldn't go so far as to say they'd never occur. Before we included animals in A7, for example, I'd see some examples of people deleting articles on someone's pet dog and the like. There's no chance of that surviving, and there's no purpose in tying up AfD with such an obvious case. Now, yes, we ultimately realized the underlying rule needed an addition, and made that addition. But I wouldn't say that those who made the obvious call before it was technically codified were somehow "wrong". Seraphimblade Talk to me 05:42, 17 February 2011 (UTC)
 * I would say that those using IAR as a reason to speedily delete anything were wrong, because I stand by my statement that it is never appropriate. In the specific example cited, there was at the time no consensus that articles about pets should be speedy deleted, and no consensus regarding where the line between notable and not-notable lay - the existence of Category:United States Presidential pets suggests some can be notable and even when a criterion exists interpretation of it can vary (I'm reminded about the "biscuit deletions" following the introduction of G11). It would have been far better for the project to have prodded them or nominated them at AfD. Repeated SNOW closures in the same direction would provide clear evidence that is required for a speedy deletion criterion to be added or modified. Something being IAR speedied, no matter how frequently, is not evidence of their being any consensus that it should be speedy deletable. I should perhaps make it clear that I fully support the use of IAR in almost all scenarios that are not speedy deletion. Thryduulf (talk) 15:10, 17 February 2011 (UTC)
 * I don't know, I can think of a couple instances where I'd tag something per IAR. If I came across an article titled "How to hack into Xbox Live accounts", I'd tag that; it doesn't meet any of our CSD requirements, but it's instructions on how to do something that is obviously illegal.  Not that I'm advocating using IAR a lot, but there are a very few situations where it makes sense.  As to the expansion of A9; I'd like to (I trust our admin corps to handle it), but I don't think it will happen because many people are not as optimistic as I am. The Blade of the Northern Lights  ( 話して下さい ) 03:41, 19 February 2011 (UTC)
 * I think any tutorial on how to do something that is considered illegal everywhere is a "deliberate attempt to compromise the integrity of Wikipedia" because there is no way the creator can (in good faith) assume that such material should be included. Thus G3 could handle it. But "illegal" is another problematic term since not everything is illegal everywhere and Wikipedia is a global project. For example, it's illegal in certain countries to depict the prophet Mohammed. Does that mean we have to delete pictures of him? Of course not. Things that are posted that are clearly universally illegal (child pornography, cracking instructions etc.) can be handled by G3 as clear vandalism. But the rest should be handled by XFD. As for your optimism: It might sound bleak but the pessimism many share here is well-founded because some admins have "taken the law in their own hands" far too often to leave any room for interpretation in policies. Regards  So Why  10:35, 19 February 2011 (UTC)
 * I meant illegal as in "illegal in the US state of Florida", I should have made that clearer. I suppose G3 would work just fine for that sort of thing.  As to my optimism; I've only been around here for just under (at the time of writing) a year, so I haven't seen as much.  The Blade of the Northern Lights  ( 話して下さい ) 23:18, 19 February 2011 (UTC)