Wikipedia talk:Criteria for speedy deletion

change the way we deal with G12

There is a problem here which has been bugging me for a while, and I think the fix is probably pretty simple, but it's always a good idea to run thess things up the flagpole before just doing them. The problem is that in the majority of cases, a copyright violation is the bigger problem, but not the only problem. Most of the time stuff that gets deleted as G12 would be deleted as G11 if we hadn't detected the copyvio. I try to always add a note to that effect to the creator's talk page, but I don't seem to be in the majority in taking this extra step. So they come back to look at their page, and find it's been deleted as a copyright violation. They go through the whole procedure outlined at WP:DCP and repost it, confident that it's problems have been overcome, and it's speedy deleted again as advertising. Everyone on both sides has just had a chunk of their time wasted. An easy way to prevent this would be to simply create a combined copyvio/advertising CSD template and enable it with Twinkle and Huggle, retaining the current tag for the rare cases where it's not just some company trying to post their latest press release or other PR material as an encyclopedia article. I can't think of a downside to this, but maybe I've missed something. Comments? Beeblebrox (talk) 20:23, 20 December 2009 (UTC)

• Here's a mock up of what it might look like:

• Beeblebrox (talk) 20:29, 20 December 2009 (UTC)

I agree that this can be a problem. I have tweaked your proposed wording a bit for the current wording of G11 ("unambiguously" instead of "blatant") but it's a good idea. Did you have a name for the template in mind? Regards SoWhy 20:39, 20 December 2009 (UTC)

I think it's a great idea, and would even consider including a link to WP:COI. :) --Moonriddengirl ^(talk) 20:46, 20 December 2009 (UTC)

I agree. It would be very useful at WP:Suspected copyright violations. Theleftorium 20:54, 20 December 2009 (UTC)

I keep the following words set up in in a text file and very often add them to the G12 warning:

Please note that even if the copyright issue were resolved, the promotional tone of a company or personal website is likely be unsuitable for an encyclopedia article, which requires a neutral point of view.

I did suggest some time ago that they should be incorporated in the G12 warning template, but there was no response. They are aimed at the same problem - users painfully going through a copyright release to find their entry rejected on other grounds - but are rather more general than Beeblebrox' suggestion. JohnCD (talk) 21:02, 20 December 2009 (UTC)

A more generic solution - add an additional parameter "note=" to all db- templates, which would show up as explainatory comments and/or additional reasons to speedy, and work up Huggle and other tools to make it easy use some common canned note= text, like note=May also qualify for G11, advertising or note=May also qualify for A7 - No indication of importance (individuals, animals, organisations, web content). davidwr/(talk)/(contribs)/(e-mail) 21:23, 20 December 2009 (UTC)

Quite often the subject may actually be notable, and the problem is that the text of the press-release/company website/Myspace profile submitted is unacceptably promotional and POV. In those cases we want not to frighten them off but to break it to them that they are going to have to do some work to make an acceptable article. davidwr's "note" parameter could still be used to provide a message for that case, of course. JohnCD (talk) 21:32, 20 December 2009 (UTC)

Maybe we should make a special db-multiple template which you can supply with multiple criteria and it shows all of those in the message, e.g. {{db-multiple|G11|G12}}. Regards SoWhy 21:37, 20 December 2009 (UTC)

• Endorse db-multiple. davidwr/(talk)/(contribs)/(e-mail) 21:41, 20 December 2009 (UTC)

What I envisioned is that "canned" note= parameters would be added to Huggle etc. to cover 90% of the most common cases. There are still plenty of cases where a customized note is needed, and plenty of cases where no note is needed at all. By the way, the experimental template User:Davidwr/db-2 (analogous to {{prod2}}) has an optional comment parameter. For example: {{User:Davidwr/db-2|Confirmed copyvio. Additionally, this material is unambiguously promotional and should not be added to Wikipedia, regardless of it's copyright status (CSD G11). ~~~~}} davidwr/(talk)/(contribs)/(e-mail) 21:41, 20 December 2009 (UTC)

Proposal: db-multiple

I proposed above that we create a sort of {{db-multiple}} to do what Beeblebrox has suggested and more. Here is my idea of how it could look like (using {{db-multiple|G11|A7|G12}}):

Someone would just have to dress it up in fancy template coding to make it do what I just created statically but one done it could be a good thing to have, just like {{article issues}}. What do you all think? (and who would be willing to code it?) Regards SoWhy 14:38, 21 December 2009 (UTC)

Love it; will not code for the good of the project. :) --Moonriddengirl ^(talk) 15:09, 21 December 2009 (UTC)

Yes, good. (I should like the existing copyvio-only version to still be available as an option.) For what it's worth recently I have dealt with the problem by not tagging for copyvio if I can see a reasonable alternative tag (usually promotion). JamesBWatson (talk) 15:29, 21 December 2009 (UTC)

It's probably a good idea to note the copyvio also, just in case the article ever winds up at WP:DRV or the admin reviewing disagrees about the alternate rationale. --Moonriddengirl ^(talk) 15:38, 21 December 2009 (UTC)

Tim Song's template

Here it is:

{{User:Tim Song/Sandbox|G1=|G2=|G3=|hoax=|G4=|G10=|Attackorg=|G11=|G12=http://example.com|A1=|A2=s:Main Page|A3=|A7=|bio=|web=|corp=|animal=|club=|band=|A9=|A10=|category=|demo=yes}} produces: User:Tim Song/Sandbox Tim Song (talk) 16:53, 21 December 2009 (UTC)

In hopes of keeping this even conceivably usable by the non-huggle-endowed, could the G12-url and A2-source parameters be combined into non-empty values for G12 and A12, that is, {{db-multiple|G1=|...|G11=|G12=http://example.com|A1=|A2=s:Main Page|A3=|...}}? —Korath (Talk) 17:06, 21 December 2009 (UTC)

 Fixed though you shouldn't be using more than three or four parameters at the same time anyway... Tim Song (talk) 17:17, 21 December 2009 (UTC)

Endorse - let's do it. I'm sure there will be glitches to work out later. davidwr/(talk)/(contribs)/(e-mail) 17:24, 21 December 2009 (UTC)

Looks like a great way to note several strong issues (giving reviewing users multiple options) and relay the most information to creating editors whilst avoiding the bite-y problems we've discussed before associated with multiple db tags. ~ Amory (u • t • c) 19:03, 21 December 2009 (UTC)

Works for me; I've come across things that were multiple SD worthy. Of course one reason is all you need, but still... HalfShadow 19:55, 21 December 2009 (UTC)

Could it be coded to allow using{{db-multiple|G1|G3}} instead of {{db-multiple|G1=|G3=}}? Regards SoWhy 20:58, 21 December 2009 (UTC)

Unlikely and way harder. That would require using a #switch on each parameter, I think; perhaps someone a bit more template-savvy can think of another method. Named parameters is what {{article issues}} uses, anyway. (If you want easy memorization, |A3=yes has the same effect; as long as the parameter is supplied its value does not matter). Tim Song (talk) 21:05, 21 December 2009 (UTC)

Yes, but {{article issues}} has them for the month and year, it makes sense there. I'll drop happy-melon (talk · contribs) a line, he is template-savvy, maybe he can think of something. I think people will keep on forgetting to add the "=" if it has no use. I mean it makes sense for A2, G12 or G4 for example but not for the others. Regards SoWhy 21:19, 21 December 2009 (UTC)

Opposed unless Moonriddengirl girl codes.--Fuhghettaboutit (talk) 23:12, 21 December 2009 (UTC) (support in spades actually)

Looks like a good idea to me; it'd be helpful not just at WP:SCV but with new-page patrolling in general. Just make sure it can be used by us non-Hugglers, please... A Stop at Willoughby (talk) 06:00, 22 December 2009 (UTC)

Happy-melon's template

Did someone ask for a stupidly complicated template? Your wish is my command :D
{{db-multiple|G1|g3|g2}}

Currently only works for G1-3, purely because I'm too lazy to update the other templates necessary. If someone could duplicate this edit to the rest of the templates that they want represented in this stack, and add them to {{db-multiple/item}} - the syntax should be fairly clear. Apologies for the slightly dodgy grammar and punctuation resulting from taking the raw criterion statements out of context, but it means there's one fewer place to update the texts if we want to change them. Please have a play and let me know what you think. Happy‑melon 14:59, 23 December 2009 (UTC)

That's exactly what I thought it should look like. Two things though: 1.) Can it be modified to show a warning if it is used without parameters? 2.) Can your coding handle criteria that need extra information, i.e. {{db-multiple|G12=http://www.copyvio.url/}}? Regards SoWhy 15:21, 23 December 2009 (UTC)

1) yes, easily. 2) not at the moment. Which parameters would need a value? Happy‑melon 16:08, 23 December 2009 (UTC)

I'd say G4 (for the XFD), G12 (for the source of the copyvio) and A2 (for the foreign wiki with the copy, optional though since A2 probably is never used in this template). Regards SoWhy 16:18, 23 December 2009 (UTC)

Happy-melon, can you please do something to prevent this talk page from being listed on CAT:CSD, which it is now because your template includes a category link? --R'n'B (call me Russ) 18:48, 23 December 2009 (UTC)

Second. I'd noinclude the cats in the test template, but I don't want to go mucking around with someone else's proposal. Looks like a good proposal, too. UltraExactZZ ^Said ~ Did 19:18, 23 December 2009 (UTC)

Muck around as much as you want, it's just a test after all. I can't find where it's included from though. Regards SoWhy 20:04, 23 December 2009 (UTC)

Fixed, rather inelegantly. It's included from {{db-multiple/item}} which in turn included it from the speedy templates. Tim Song (talk) 20:48, 23 December 2009 (UTC)

I tentatively support this, but I'm not quite sure how it would be functional with Twinkle's Radio button selection style, which concerns me seeing as all of my new page patrol is done using TW. Once I know how this would work, it would have my full and complete support. Ks0stm ^(T•C•G) 19:41, 23 December 2009 (UTC)

Well, I'm sure it can be re-coded to use multiple choice buttons instead. I'll drop Amalthea a note to be sure though. Regards SoWhy 20:04, 23 December 2009 (UTC)

• Yes, the TW change is definitely doable. Tim Song (talk) 20:48, 23 December 2009 (UTC)
• Never let the tools stand in the way of improvements. With this case in particular, the worst that could happen is that Twinkle won't support multi-SDs for a while. But as Tim said, it's certainly doable. I won't be able to work on it till next year, and I'm not quite sure yet about the best way to present that option without sacrificing the current simplicity, but there are a number of options, so no worries. And by the by, abusing radio buttons as buttons, like Twinkle likes to do, is a usability nightmare anyhow and can use a change.
  However: I notice the user notification code has been conveniently dropped from all multi-SD template variants above. Happy Melon, while you're at it, could you be so nice and create a sister template {{db-multiple-notice}} that takes the same parameters and outputs a nice user notification à la {{db-g1-notice}} and friends? :D
  Amalthea 00:05, 24 December 2009 (UTC)

Y I have now added all criteria to {{db-multiple}}, edited all db-xxx templates to allow raw=yes and rephrased those that started with a "." to sound better when used this way. The template is ready to use, although Amalthea is correct that a sister template for notifying users is probably needed. Also, it currently (see above) does not support parameters for those templates that require them (e.g. G12 and A2). My idea would be to use the same parameter names that the templates use themselves (e.g. url= and source=) and db-multiple simply passes them to the relevant templates, e.g. using {{db-multiple|G12|url=http://www.example.org}} invokes {{db-g12|raw=yes|url=http://www.example.org/}} in {{db-multiple/item}}. Should be possible and easier than trying to make G12= to work in those cases. Regards SoWhy 12:24, 24 December 2009 (UTC)

I think that would be the simpler solution. The notification templates aren't based on a meta-template, so no fancy tricks will work there; and building a template that substitutes without leaving a huge mess of parser functions will be tricky if you try and be too clever. Could be tricky. Happy‑melon 13:10, 24 December 2009 (UTC)

Then you (or someone with template skills) just needs to implement it

As for the notification template, we could use something like {{nn-warn-reason}}. I created an example at {{nn-warn-multiple}}. Regards SoWhy 13:50, 24 December 2009 (UTC)

Anyone still interested in this? Regards SoWhy 13:46, 4 January 2010 (UTC)

• Nice idea. That's a keep. Debresser (talk) 14:28, 10 January 2010 (UTC)

I have now added support for url= on G12 and F9; for rationale= on g6, G7, G8, and T3; and for source= on A2. I have not provided for the 2nd positional parameters which some of the specific templates (such as {{db-a7}} support, but that could be added easily enough if wanted. DES ^(talk) 20:23, 19 January 2010 (UTC)

Incubated articles and R2

I just closed Wikipedia:Articles for deletion/A Marine Story as "incubate" and moved the article to Wikipedia:Article Incubator/A Marine Story. The instructions at WP:INCUBATE say to tag the mainspace redirect R2 as we do with userfication but the current R2 criteria excludes the "Wikipedia" namespace. I tagged it R2 anyway but perhaps an exception needs to be written into the R2 criteria for incubated articles. --Ron Ritzman (talk) 02:56, 11 January 2010 (UTC)

Agreed. WP:CSD#R2 covers redirects from the mainspace to the userspace, which of course allows admins to userfy without leaving a redirect behind. Incubation is essentially another form of userfying, so I think this exception is a common-sense addition to the criterion in question. (Of course, I would prefer speedily deleting all redirects from mainspace to project-space, but that's another question entirely....) A Stop at Willoughby (talk) 05:20, 11 January 2010 (UTC)

Moreover, I suspect this is common practice already among admins closing AfDs as "incubate." A Stop at Willoughby (talk) 05:21, 11 January 2010 (UTC)

I think it's arguable that G6 applies, though that's typically used for content that will return (such as cleanup before a page move), because it is uncontroversial, technical maintenance. However, I think WP:IAR applies here in that everyone agrees it should be deleted, and we've been doing it under R2 for a while, despite its lack of qualifying, and instruction creep is bad. I don't really agree with altering R2 nor do I agree with creating a new criterion for this trivial case. I think just replacing the instructions at WP:INCUBATE with G6 instead of R2 would be reasonable, and perhaps even make a specific template for G6 as applied to incubation (just like {{db-copypaste}} and {{db-histmerge}} exist. --Shirik (Questions or Comments?) 18:02, 12 January 2010 (UTC)

Fork

Would someone please explain to this bear of very little brain the difference between a content fork and an article that qualifies for deletion under A10? — [[::User:RHaworth|RHaworth]] (talk · contribs) 07:18, 12 January 2010 (UTC)

most of the time, I think a content fork will "expand upon, detail or improve information" - that is, it will rewrite the article from the unique POV of the forker. The value of the addition can be debatable, but I think A10 is aimed at the people who haven't figured out "redirect" and copy/paste an existing article at a new name instead. (at least, that's my interpretation). --Alvestrand (talk) 08:28, 12 January 2010 (UTC)

Another example of an A10 would be if someone created an article at airoplane saying "An airoplane is a flying machine with wings" and going on in similar vein about fixed-wing aircraft for a paragraph or two. This doesn't contain mergeable material, is not a plausible redirect, and doesn't expand upon, detail, or improve information on the subject. Stifle (talk) 16:42, 13 January 2010 (UTC)

Length of Time Speedy Delete Should Be Left on Article

It strikes me there should be a minimum requirement on the length of time between when a speedy tag is placed and when the article is actually deleted. I had a speedy applied to one of my articles at 12:05 AM Eastern. In looking at the nominators edit history, there were numerous instances where a speedy was applied and then the article was deleted an hour or two later. This is particularly onerous since many of the speedys were placed in the early morning hours. There should be an "assume good faith period" where the author is allowed time to correct a problem or at least give other editors a chance to look at the article. This should be a minimum of 24 hours or even 48 hours or perhaps even more. Americasroof (talk) 18:45, 15 January 2010 (UTC)

I'd be happy with some sort of pause for speedies of good faith articles. But {{G10}}, {{G3}}, and {{G11}} should still be done ASAP, also {{G7}} and {{U1}} are relatively low priority speedies, but there is no reason to delay them. PS have you tried Wikipedia:Deletion review? ϢereSpielChequers 19:16, 15 January 2010 (UTC)

when it comes to speedy, most sensible admins will usually give a7's and similar a grace period, even if they don't, most of us will usually restore one to your userspace if you ask. Setting any kind of formal time limit is just excessive bureaucracy--Jac16888^Talk 19:45, 15 January 2010 (UTC)

WereSpielChequers, deletion review is not necessary because the article, Zimmer Real Estate Services, was not deleted. Of course, that's not to say that the speedy tagging was appropriate (my opinion is that a {{prod}} or a comment on the article's talk page would have been better in this case). –Black Falcon ^(talk) 19:50, 15 January 2010 (UTC)

Thanks for your comments. The A7 speedy was applied ONE MINUTE after the article was first posted and before other edits could occur. Hence, my concern that if an editor is quick on the gun there, then should at least be a safety valve. Americasroof (talk) 20:02, 15 January 2010 (UTC)

I would not support this, at least not as a blanket requirement for all speedy criteria. A delay is not necessary (or not appropriate) for many of the speedy criteria: G1, G2, G3, G5, G6, G7, G8, G9, G10, G12, and virtually all of the other non-article speedy criteria. I would also like to echo the sentiments expressed by other editors in this related discussion: imposing a time delay is a "quick-fix" only that, as is often the case with such fixes, brings with it as many problems as it fixes. Such a measure does not address and cannot change the mentality of speedy deletion tagging, which unfortunately (and partly by necessity) places too much emphasis on speed and too little on case-by-case evaluation and engagement of creators of problem articles. –Black Falcon ^(talk) 19:48, 15 January 2010 (UTC)

Thank you for your quick replies. I do agree with the quick deletion of most of the items. It's the A7 (which hit my article), A9 and G11 where are subject to interpretation and which can be corrected which need to be throttled down on speedys. Those incidentally are the articles most likely to hit newbies. Thanks again. Americasroof (talk) 19:56, 15 January 2010 (UTC)

I'd be reluctant to introduce "real speedies" and "24-hour speedies". I think we can leave this to the admins involved. Debresser (talk) 18:13, 16 January 2010 (UTC)

If there was a required time period involved, then it would not be a speedy deletion. Speedy deletion exists to ensure that the most obvious cases are quickly dealt with and not placed into a time-delay queue like PROD or AFD when the result would likely be the same either way. Articles should be "ready-to-go" by the time they hit mainspace. That doesn't mean they should be done when you hit "Save" the first time, but rather that the majority of the information that you have in front of you should be written up. (Then further edits reflect additional research, etc.) At the very minimum they need to pass the speedy criteria before being in mainspace; if you're still working on an article-in-progress that hasn't reached the point it passes CSD yet, work it up in your userspace and call a few other editors' attention to it by way of talk-page messages. (Sadly just being in mainspace doesn't attract editors—there's 6,830,873 after all; I've had several that have been in mainspace for years and have only had myself and bots edit them.) If you have other concerns with an article that was speedied, try contacting the deleting admin. —Scott5114↗ [EXACT CHANGE ONLY] 19:18, 16 January 2010 (UTC)

There are at least 500-1000 articles deleted every day using CSD, a significant portion of which are A7 deletions (probably ~50%). If we mandate a 24 hour waiting period, we'll end up with CAT:CSD constantly clogged with hundreds of articles, only a small fraction of which would be eligible for deletion. In most cases A7 cannot be "corrected," as the subject is truly not notable at all. At best a spurious assertion of notability can be added to force an AFD. Mr.Z-man 19:59, 16 January 2010 (UTC)

I'm not sure the problem with the A7 tag on Zimmer Real Estate Services is the timing anyway; this [1] is what it looked like when it was tagged (not that different to now). I wouldn't have said that was an A7; I think the scale of the projects listed was enough claim of significance to avoid speedy deletion. Cassandra 73 (talk) 23:07, 16 January 2010 (UTC)

Leave it to the admins. Even on a difficult criterion like A7, some articles can plainly be deleted within seconds of tagging ("Johnny X is a soccer player for his local high school and plays the tuba"); others will be more difficult. The speed with which an article is deleted is a matter for admin discretion. If an admin pulls the trigger too quickly and gets it wrong, its likely they'll hear about it. --Mkativerata (talk) 06:26, 19 January 2010 (UTC)

I agree entirely. Whatever unofficial and unwritten guideline each admin uses seems fine 95%+ of the time seem to work just fine. Watching a list and/or going to the CSD page and looking at tagged articles in categories, if I'm around a few hours I can see the whole process for a lot of articles run start to finish. A7s are kind of the default setting... the neighbor noise complaint 911 call of CSDs, as it were. Those in apparent good faith do get noticed often, contrary to popular belief, at some point in the process. The people who work on the admin end of it seem to have it down cold and I'm always impressed at the priority category enforcement used, so why fix what already works and would be a gigantic effort to overhaul for arguably no benefit?

Blah, no, I can't support any set time delay policy for any reason. If a patrol saw something and knows it has a grace they could start an AfD with a SNOW close in mind. Sometimes it'd work, others no. What if this is in the wait period? Is the article immune? This is why CSD exists; an admin is acting in place of a short-length AfD that would have a SNOW close. If I can easily jury-rig AfD into something that is 1) faster, 2) more transparent, and 3) consensus-based instead of a normal CSD on a delay to delete, why bother? Community discussion to admin delete versus more waiting and only the admin delete? I'll take the first method, please. We have counter-CSD patrols to improve or "stub-ify" articles, userification, {{holdon}} {{newpage}} {{construction}}, CSD removal to PROD, PROD to AfD, deletion review, etc etc. All of that exists so that this can just run along on its own. ...Oh, and as always, it's not our responsibility if someone throws out an article for publishing before it meets basic standards... but even so I'd userify plenty if it were permissive for non-admins. At least, it wasn't a month ago and I haven't heard of a change. ♪ daTheisen(talk) 15:02, 19 January 2010 (UTC)

The tag was left on the article for about 47 minutes. Then it was removed because A7 didn't apply. If that user hadn't removed it someone else would have, perhaps an admin. Just because something has been tagged for speedy deletion doesn't mean it will be deleted under the speedy deletion criteria. If people just let them sit because an arbitrary time limit hasn't expired yet, it would just hold up the process, making it a pain to find valid speedy deletion deletion candidates and and to remove the tag from invalid speedy deletion candidates. In that situation the tag may have stayed on the article for much longer before being removed. If something's not a speedy deletion candidate it shouldn't be tagged for speedy deletion. An arbitrary waiting period before deletion wouldn't change that. Such pages should either be kept or go through PROD or AFD instead. Reach Out to the Truth 15:51, 19 January 2010 (UTC)

Criterion for dangerous images?

Could we expand criterion F2 to include images that contain potentially malicious code? I admit that I don't know how the software determines whether an image is dangerous, but apparently at least Commons is set up to do this — Commons image File:Great Moravia not cropped, eng labels.svg contains an automated message reading "Warning: This file may contain malicious code, by executing it your system may be compromised." If I'm missing something on the technical side, please tell me that and accept my apology for taking your time. Nyttend (talk) 03:49, 20 January 2010 (UTC)

Add new criteria to CSD

Copied over from discussion at AN/I

How does everyone feel about a new CSD# for BLPs that are totally unsourced for more than a year? <>Multi‑Xfer<> (talk) 07:20, 20 January 2010 (UTC)

I'd go for 2 months, myself. If someone's making an article, they should (hopefully) have - or know where to acquire - sources already. A year just seems to long to me. - Tainted Conformity ^SCREAM 07:26, 20 January 2010 (UTC)

• This discussion should be at WT:CSD, but yes, I would entirely support a CSD for all BLPs that are tagged as unsourced for a time on the order of months.  Sandstein  07:28, 20 January 2010 (UTC)
• I think this would work after we largely clean up the current mess. We obviously can't just dump tens of thousands of articles into the current CSD queue, so we'd have to proceed slowly in cleaning up the 51,000 unreferenced we have now. I think using the PROD solution above would work better for that and would not put a bunch of extra weight on CSD which is already always backlogged but important for other reasons (copyvios, attack pages, etc.). Once we've cleaned out most of the existing unreferenced BLPs I'd fully support creating a CSD category for BLPs unreferenced for X months. However I could be missing something in my thinking here, and if others prefer this to the above solution I'd certainly be fine with that. --Bigtimepeace | talk | contribs 07:37, 20 January 2010 (UTC)
• If this achieves consensus at WT:BLP (as it should) then it will allow us to fast-track removal of these articles, so yes it's a good idea and will help with what Bigtimepeace calls "the current mess". Guy (Help!) 07:46, 20 January 2010 (UTC)
• This is a double-edged sword. It's productive in theory, so I want to support it in that way. We could delete stuff, but it would have the possibility of alienating editors who are newbies or don't edit much. Ah, a tough decision at almost three in the morning. Kevin Rutherford (talk) 07:51, 20 January 2010 (UTC)
• I'm a bit against this. I think the proposal at WT:PROD is better, and if that's what's agreed-upon, this CSD would be mostly irrelevant. If it's been unreferenced for an entire year, what's one more week of waiting, really? This borders on instruction creep if the PROD change is implemented. --Shirik (Questions or Comments?) 08:37, 20 January 2010 (UTC)
• Support, but only if the PROD suggestion doesn't come to fruition. - Tbsdy (formerly Ta bu shi da yu) ^talk 08:49, 20 January 2010 (UTC)
• Second choice. A prod with some teeth (no easy reversal without improvements) is a much better and friendlier option. Only if that compromise cannot be achieved should this drastic action be considered. Fram (talk) 08:53, 20 January 2010 (UTC)
• Strongly oppose There is far too much chance that this will lead to deletion of many perfectly valid articles that could be referenced if anyone tried. Looking at a few of the articels deleted out-of-process in the incident that sstarted this, I had no trouble addign sources to 3 out of 4, and i'm confident that print sources exist for the 4th. Remember that unsourced contentious BLPs are alredy deletable, so we are talking exclusively about uncontentious content here. DES ^(talk) 09:20, 20 January 2010 (UTC)
• Oppose - too many babies would be chucked out along with the bathwater. The PROD proposal is much more reasonable, and allows for transparency and for the articles to be sourced before being deleted. Many, many of the articles in question can be easily sourced with a cursory Google search. The Wordsmith^Communicate 09:55, 20 January 2010 (UTC)
• I have a number of objections to this. The mere fact that an article is unsourced does not mean it should be deleted, particularly if it can be easily demonstrated that sources exist. Deletion is a last resort and only occurs for articles that have fundamental, severe problems that would either prevent a compliant article from being written or would require the article to be completely rewritten from scratch. Lack of citations is not one of these problems.
• There are plenty of unsourced BLPs that are perfectly encyclopedic. Take a look at Hazel Byford, Baroness Byford. The subject is a peer and a current member of the House of Lords, and if I took the article to AfD I would be laughed at since there are clearly plenty of references available. Yet it was totally unsourced for a lot longer than a year. Hut 8.5 09:56, 20 January 2010 (UTC)