Jump to content

Wikipedia talk:Criteria for speedy deletion

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by 141.212.111.116 (talk) at 19:53, 2 April 2009 (Add a time delay for G8: very good idea, how about we expand it.). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Userpage exception for G1 and G3

The policy gives a userpage exception for CSD G2 (test page). It should also give an exception for G1 and G3, in agreement with practice. —Preceding unsigned comment added by 129.49.7.125 (talk) 23:02, 16 March 2009 (UTC)[reply]

not G3 and dubiously G1. A p. devoted to what amounts to vandalism can and has been done in user space. DGG (talk) 07:11, 17 March 2009 (UTC)[reply]
Agree with DGG on G3 but it might be a consideration for G1. After all, userspace is a place for testing and sandboxing amongst other things and what is not making sense now might make sense if the user has some time to work on it. Deleting stuff under G1 in userspace seems like a stupid idea to me. G3 implies bad faith by the user and if they are using userspace nonsense as vandalism, we can still G3 it. But if they are acting in good faith, it would be silly to delete such pages and risk alienating a good-faith contributor. As with certain "secret page" deletions, the harm that using G1 in userspace can cause is much higher than the benefits of deleting a page noone cares about anyway. Regards SoWhy 07:27, 17 March 2009 (UTC)[reply]
I don't think there's much of a need for this. Vandalism is vandalism anywhere (and in the case that there's a really good reason, I'm sure no admin would refuse a reasonable undeletion request when appropriate), and I suspect most admins would give more latitude about userspace pages than those elsewhere. Stifle (talk) 13:28, 17 March 2009 (UTC)[reply]
  • If a user wants to create a userpage full of patent nonsense or faux vandalism, that's their prerogative. If ANOTHER user creates someone elses userpage as vandalism or nonsense, then that is G3. Common sense prevails... –xeno (talk) 13:35, 17 March 2009 (UTC)[reply]
I wish that was true but recent experience with MZMcBride's deletions tells us that not all admins have that view about userspace and some like to use G1 as a carte blanche; so I don't think adding an exception to G1 would hurt but might be useful. As you point out, it's still G3 if someone else posts nonsense in your userspace so it would not really change anything but make a clear statement that you are allowed to post nonsense in your own userspace. SoWhy 13:54, 17 March 2009 (UTC)[reply]
Added to G1. –xeno (talk) 19:57, 20 March 2009 (UTC)[reply]

This thread is patent nonsense. We're not a test wiki or a pastebin. It's as simple as that. --MZMcBride (talk) 21:22, 20 March 2009 (UTC)[reply]

Unfortunately, not everyone sees things in black and white like you do, MZMcBride. Is it okay if some consensus is formed?--Fabrictramp | talk to me 21:37, 20 March 2009 (UTC)[reply]
As difficult as it is to register an account and create a user page with "poop" and then leave forever, I see no reason to memorialize such nonsense. Sure, look for the elusive beast known as consensus all you'd like to, but throwing common sense out the window in favor of 'zomg policy' is unacceptable. --MZMcBride (talk) 05:23, 21 March 2009 (UTC)[reply]

Non-constructive IP comment [1] removed. --SmokeyJoe (talk) 09:11, 1 April 2009 (UTC)[reply]

Ah, the simple pleasures. –xeno (talk) 20:31, 27 March 2009 (UTC)[reply]

User pages exception for G1 (patent nonsense)

Recap:

March 20, User:Xeno added user pages as an exception to G1 [2]. Previously, G1 contain no reference including or excluding user pages.
Nine days later, User:MZMcBride took it out, I, User:SmokeyJoe, put it back, and User:CalendarWatcher put it back again, calling for wider discussion.

I believe that the userpage exception should be put back in (ie nonsense userspace pages should not be speediable) for the following reasons:

  • Judging patent nonsense is not uncontestable. There may be meaning in it that isn’t obvious.
  • Such pages are often kept at MfD, with the user educated in our expectations of userspace usage.
  • Patent nonsense is better dealt with by blanking, as a non-administrative action. If it was a mistake, the user can revert. If the user needs to learn, it is easier if the removed nonsense remains accessible for reference. If a user repeatedly posts nonsense, calling it CSD#G3 is readily justifiable. If correcting patent nonsense posting is routinely dealt with non-administratively, then general users will be better encouraged to clean up nonsense themselves. The simple task of cleaning up nonsense, following the non-simple task of identifying it, should not be delineated as an administrator task.
  • MfDs and blankings by another editor are more effective educationally. They involve inter-editor interaction, and do not involve administrator-newcomer power imbalance.
  • CSD criteria authorize mass deletions, and there is more danger of impersonal deletions intimidating new users than there is advantage in deleting nonsense pages in userspace (WP:PERFORMANCE)

--SmokeyJoe (talk) 09:46, 1 April 2009 (UTC)[reply]

G12 situation

I tag an article for G12, but I cannot put in the URL in the {{db-copyvio}} template because the URL is on the spam blacklist. What do I do from here? MuZemike 16:58, 25 March 2009 (UTC)[reply]

Just leave out the http or something, and it should be let through. And mention it in the edit summary that you did this deliberately. :) --Amalthea 17:10, 25 March 2009 (UTC)[reply]
Or put spaces in the URL. Stifle (talk) 22:10, 25 March 2009 (UTC)[reply]

G4 use problem

Hi. A question about the use of the G4 speedy - the description states it's Recreation of deleted material. A copy, by any title, of a page deleted via a deletion discussion, provided the copy is substantially identical to the deleted version ... (my highlighting) - but for those of us who aren't admins and can't therefore see the previous deleted version(s) of the article, how do we know if there has been any substantial change ? Do we therefore assume it's unchanged, and leave the admin reviewing the erquest to make the decision on any changes made ? CultureDrone (talk) 11:33, 27 March 2009 (UTC)[reply]

Ask an admin to have a look? I'm usually happy to do these comparisons if there's any doubt. Lankiveil (speak to me) 00:45, 28 March 2009 (UTC).[reply]
  • If you have any reason to think that it would be similar to the deleted version, I'm sure tagging it for G4 would hurt anything. If it ends up being different, then it would be declined and then you would know that it is different. —Preceding unsigned comment added by Tavix (talkcontribs)
That's why admins review speedy deletions. You tag it G4 if you have suspicion that it might be a recreation, the reviewing admin has to check if the tagging was correct. SoWhy 20:11, 29 March 2009 (UTC)[reply]

Moved

I've been bold and moved and updated the page based on the discussion from a few weeks ago, which seemed to form a rough consensus for "Criteria for summary deletion", thus preserving the CSD acronym. If anyone is having an allergic reaction to it, please do speak up... :D Happymelon 11:52, 27 March 2009 (UTC)[reply]

Did you also plan to go through other policy and guideline page text, and change the word "speedy" to "summary"? Did you also plan to let everyone know that rough consensus to change a policy page means three people almost 4 weeks ago kinda said it was an OK idea? I'm not saying this was the worst thing ever done, but seriously, policy pages should be more carefully considered than this when a major change is under foot! --Jayron32.talk.contribs 12:09, 27 March 2009 (UTC)[reply]
Actually, yes, but I thought it would be prudent to make sure the sky wasn't going to fall down before chasing down the title in other pages :D. And I count five, with one oppose and several "meh"s. Given that I just waved a huge flag on a thousand watchlists, if there is more discussion to be had, it should certainly start now :D Happymelon 12:18, 27 March 2009 (UTC)[reply]
I would say that five people supporting the change was nowhere near enough to actually make the change. I suspect the majority of people weren't even aware of the proposal. Changing the name of something that everyone's familiar with needs a bigger degree of community input in my opinion. Ryan PostlethwaiteSee the mess I've created or let's have banter 12:26, 27 March 2009 (UTC)[reply]
One of the drawbacks of a project this size trying to make decisions via "consensus" is that it's hard to get wide community input for anything. However, I would say this move was just a tad bit too bold for something just being "knocked around" on a talk page. I would recommend switching back and initiating an RFC on this. --Ron Ritzman (talk) 12:45, 27 March 2009 (UTC)[reply]
But what would you say in such an RfC? Rather, what would you say in an RfC that you can't just say now and be done with it? This is just as good a venue for discussing the move whether or not I stick an {{rfc}} template on top :D Happymelon 13:36, 27 March 2009 (UTC)[reply]
I also think the discussion was too small, should have been wider advertised, and should have had more consensus for such a wide ranging change. As far as I can tell it wasn't even mentioned on Wikipedia:Criteria for speedy deletion, Wikipedia:Requested moves, or anywhere other than Wikipedia talk:Criteria for speedy deletion (in a section called "Name of policy" with no move template at the top). I would have opposed if I had seen it. Search currently finds 24 categories [3] and 54 Wikipedia space pages [4] with "speedy deletion" in the name, and 13722 Wikipedia space pages [5] containing "speedy deletion". PrimeHunter (talk) 12:44, 27 March 2009 (UTC)[reply]
Why would you oppose it? That's the only genuinely important thing. I run a bot that has 55,000 edits; the technical details of implementation don't scare me in the slightest, and I'm more than happy to take the time to complete them, including any notifications that will be required (renaming CAT:CSD, for instance, is sure to break a lot of bots if done unilaterally, although it is a trivial thing to avoid if done carefully). As Ron says, it's hard to get sufficiently wide community support for anything without waving big flags like this. Happymelon 13:36, 27 March 2009 (UTC)[reply]
It looks moot now but here are some reasons. Risk of confusion with edit summary, plot summary, summary section, summary article. "Speedy deletion" is an old well-established and widely used term with no other meaning in Wikipedia. Insufficient reason to change it to anything at this point. "Summary deletion" has negative connotations to many. Searches show the term is usually written by people objecting to what they consider inappropriate deletion of pages or parts of pages. PrimeHunter (talk) 19:08, 27 March 2009 (UTC)[reply]

I have to agree with Ryan and Co. above. It's not whether the move was a good idea (which it wasn't) but whether it was supported by consensus. I don't think there was enough discussion to reach a consensus needed to rename a policy that existed for years with this name. A "rough consensus" is worse than that, because all it says is "of those who were aware of that 3 weeks old discussion, the majority possibly did not object to a name change". Before you go ahead and change all pages mentioning CSD, we should have a discussion whether that is wanted. I for one prefer the old name and I think "summary deletion" is confusing to newcomers and an incorrect, too legal term for such a policy. I don't see why there was a need for a change...and I certainly see no consensus for it in a short discussion 3 weeks ago. I don't think boldness is a godo idea when it comes to such decisions. Regards SoWhy 13:55, 27 March 2009 (UTC)[reply]

Summary deletion also may make it seem that it was deleted on the admin's summary judgment alone, when it is the admin acting within the boundaries of years of past precedent. However the literal definition seems to be spot on: Performed speedily and without formal ceremony. FYI, I've left notes at WP:AN and WP:VPP pointing here. –xeno (talk) 14:00, 27 March 2009 (UTC)[reply]
But that's exactly what's happening: a real summary judgment is a court making a decision on the normal basis of applicable law, precedent, etc, without as little fuss as possible. Summary judgments aren't where a court goes maverick and makes whatever decision they personally like; they're still just as observant of principles as ever, it's only the process that gets curtailed. Happymelon 14:24, 27 March 2009 (UTC)[reply]
Yes, I know that in the strict legal and literal sense "summary deletion" actually makes perfect sense but most laypersons think "summary judgment" is A Bad Thing™. –xeno (talk) 15:03, 27 March 2009 (UTC)[reply]
Just want to note my preference again for "straightforward deletion". Doesn't really matter to me though. --Ali'i 14:16, 27 March 2009 (UTC)[reply]

I'm perfectly happy to move the pages back, but only if someone can explain why the further discussion that we all agree is needed can only occur if that happens. Will me adding an extra 130 move log entries (and potentially another 130 if we then conclude that "summary" is better) somehow make it easier to come to the proper consensus? The wiki isn't going to explode if some people temporarily go "eh?" and then are drawn to the discussion to find out what's going on. In the meantime, I'll go spam some noticeboards... :D Happymelon 14:24, 27 March 2009 (UTC)[reply]

I'm a big supporter of Happy Melon's work, but this was a !fail. There was no consensus for the move, and renaming one of the most common and important processes on Wikipedia without consensus is a really bad idea. I prefer the name "speedy" because: name changes create confusion, "summary" already has a meaning on Wikipedia (edit summaries), most editors won't know this meaning of the word "summary", and the name "speedy" deletion helps deflect criticism from creators who in fact had their articles deleted quickly.
Unless someone can give me a reason not to, I'm going to revert the name change until there's consensus to change it. 5 people is not consensus on something this central to Wikipedia. - Dan Dank55 (push to talk) 14:26, 27 March 2009 (UTC)[reply]
I won?!? :D As I said above, my only reason to object to a revert is that it gives the impression of "case closed": tried it, it was reverted, end-of-story-clearly-nothing-more-to-see-here. Which is not very conducive to future discussion. That and the fact that it bloats watchlists and logs and just makes more work if we then decide to move. But as I said, I'm not going to shout at anyone that does move them back, and I'll move them myself iff someone explains why it is 'necessary' or even 'beneficial' to do so. Happymelon 14:36, 27 March 2009 (UTC)[reply]

See my comments in the next sub-section. I strongly dislike this move, on two grounds. Procedurally, I think this was groundless: no defined problem and no consensus for the solution. And in the implementation, it's very problematic: "Summary" means several different things, and the meaning you're implying has unpleasant connotations, including lack of justice (not to mention death). Please revert this as soon as possible.

Is there really a dreadful problem with "speedy deletion"? Is there consensus we should change it? If so, let's find a solution that also has consensus and one that works well. --Dweller (talk) 14:31, 27 March 2009 (UTC)[reply]

Perhaps a !vote is wanted? –Drilnoth (TC) 14:52, 27 March 2009 (UTC)[reply]
Perhaps some constructive discussion first, rather than a polarising poll. Happymelon 14:57, 27 March 2009 (UTC)[reply]
I oppose the move. 'Summary' does not convey the reason behind a speedy deletion, if fact, it has a negative connotation. If anything, the only possible replacement for the word would be 'Immediate deletion'. But that doesn't fit the S... EdokterTalk 14:58, 27 March 2009 (UTC)[reply]
How does it "not convey the reason"? Neither does "speedy", which has similar "negative connotations". If anything, "immediate" is even worse, as many CSD deletions aren't immediate, an many others shouldn't be. Happymelon 15:01, 27 March 2009 (UTC)[reply]
Not everyone sees the words the same way you do. For me, summary deletion brings up an image of a posse in the old west, hanging a suspect without any evidence of guilt. While that may be the practice of some editors and admins at CSD, it's not an image I want to encourage. Speedy has no such connotations for me, but it obviously has some bad ones for you. Could you explain what the problem with the word speedy is that we're trying to fix? That way we may get a better solution. --Fabrictramp | talk to me 15:31, 27 March 2009 (UTC)[reply]
That's certainly not an image we want to encourage, I grant you! The problem I see with "speedy" is that it brings to mind an image of an admin in a race or on an arcade game, trying to delete as many articles as possible before the time runs out, with minimal thought to whether the articles actually warrant deletion. All admins will confirm that the article superficially meets the criterion, but not as many as we would like will do a more thorough check to ensure that we're not throwing the baby out with the bathwater. Fewer still will think to consider whether there is a better outcome for the encyclopedia than to delete the page; the encyclopedia is often better served by a redirect, a rewrite, or a merge, but this is often, indeed usually, not done. This is the attitude to CSD we need to be cultivating: a methodical and thorough evaluation by a 'learned' editor; in exactly the same fashion as a summary judgment. If that results in greater backlogs at CSD, then we need more admins to patrol it, not to compromise our standards. Right now we are throwing out page after page of potentially useful content in a rush for efficiency, to "speedily" get through the category as quickly as possible. That seems to me the greater evil. Happymelon 15:40, 27 March 2009 (UTC)[reply]
I'm not convinced that summary will solve that, especially since the initials will be the same -- the problem admins will still think "CSD" in their heads (not gonna address where else they'd be thinking! LOL), delete as fast as they can, and be done with it. :(
I think we're on the same page as far as the problem to be fixed. I've left a lot of notes to both editors who mistag and to admins who delete articles that shouldn't have been speedied. (Sometimes to educate them, sometimes to educate me). I don't think anything as simple as a name change will solve the problem completely. Mind you, I'm not saying that a name change might not help a little bit, but more fundamental changes need to happen. (Which might need a new section to discuss, so it doesn't get lost in this one.)--Fabrictramp | talk to me 16:09, 27 March 2009 (UTC)[reply]
I prefer "speedy". Wikipedia is full of jargon, and one might think this means it's desirable to use clearer terms for things. But in this case, I think I prefer the jargon. As others have pointed out, "summary" has many other natural meanings including another technical meaning on WP. Its use here has confusion potential. On the other hand "speedy"--especially when used as a noun ("This page is ripe for a speedy") or a verb ("I am going to speedy that page")--is obviously a term of art. The first time I saw "speedy" used that way on a message board, because of its peculiarity, it knew that it had to have a special meaning and I went off to figure out what it meant and what the rules might be for its use. I don't think that "summary" would have delivered the same message. By the way, for what it's worth, this is the first I've heard of this discussion (saw it mentioned at WP:VPP this morning).--Arxiloxos (talk) 15:24, 27 March 2009 (UTC)[reply]
The lawyer side of me cannot resist making this follow-up note on the analogies to "summary judgment". I'd suggest that the AfD process is actually closer to summary judgment (under U.S. law, anyway) rather than CSD. In summary judgment, the parties put forth their arguments, and present a limited amount of evidence in writing, in an expedited but still somewhat deliberate fashion. CSD is more like the "motion to dismiss"--such as a Rule 12(b)(6) motion to dismiss for failure to state a claim under the Federal Rules of Civil Procedure, or what we still call a demurrer in California--in which the court is empowered to throw out a case based on weaknesses that are apparent on the face of the complaint, based only on specific legal arguments and without (in most cases) needing to look closely at the underlying evidence. For those of us unlucky enough to have had our brains polluted by law school or legal proceedings, this might be another argument against using "summary" in this context--Arxiloxos (talk) 15:47, 27 March 2009 (UTC)[reply]
I strongly oppose such move, while it was a bold move, much more discussion should have taken place. Jenuk1985 | Talk 15:08, 27 March 2009 (UTC)[reply]
Why do you oppose the rename? Happymelon 15:11, 27 March 2009 (UTC)[reply]
Please don't nag people who have given an opinion as I have here, and you have done above, its inappropriate. I gave my reason. Jenuk1985 | Talk 15:14, 27 March 2009 (UTC)[reply]
I don't understand where the confusion comes from. If 5 people decided that "Home Page" sounded better than "Main Page" and someone moved it, don't you think that might cause a problem or two? Ryan has moved it back; now we can discuss. I'm against it; I gave 4 reasons above, and I have another reason: the only people who can delete pages are admins, so if there's a problem with how fast admins are deleting, we can solve that problem by discussion with admins. Changing the name and avoiding the discussion sounds like trying to win with good marketing rather than by discussion. The word "speedy" is very important at deflecting the accusation by the attack-page-creator or spammer: "You deleted my article too fast, why didn't you give me a chance to fix it? - Dan Dank55 (push to talk) 15:22, 27 March 2009 (UTC)[reply]
I meant "do you have reasons for preferring 'speedy' over 'summary'", not about the moves back and forth that have just been completed; sorry if that was misinterpreted. I understand fully (and somewhat agree with) the reasons some are unhappy with the way I moved it. As you say, "now we can discuss"; drawing in editors to such a discussion was a large part of my rationale for moving, as I explained below. Saying "I strongly oppose the move" without any further reason contributes nothing to that discussion. Happymelon 15:27, 27 March 2009 (UTC)[reply]
Okay, much better, and we're on the same page (with the same name :) I promise to support a full discussion; I remember back when I was doing more work with style guidelines that I often felt tempted to do exactly the same kind of thing to generate discussion. But really, there aren't a huge number of admins doing speedy deletions; getting us all in a room to pay attention and talk about it should be doable. - Dan Dank55 (push to talk) 15:51, 27 March 2009 (UTC)[reply]

Random sales pitch: I've proposed a WP:WikiProject Policy at Wikipedia:WikiProject Council/Proposals#WikiProject Policy. Such a project might help get a more thorough appraisal of these kinds of issues (one of the problems at the moment is policy ideas don't get enough eyes on them). Comments welcome. Rd232 talk 16:30, 27 March 2009 (UTC)[reply]

It may be better to rename it to administrative deletions. Ruslik (talk) 16:38, 27 March 2009 (UTC)[reply]

Meh, all actual deletions are carried out by Admins, so that name would probably be even more confusing, especially to new users. The Seeker 4 Talk 17:09, 27 March 2009 (UTC)[reply]
OTOH, many newbies think the person who tagged the article is the person who actually deleted it. Administrative Deletions might reinforce that it was done by an admin, and might convey that the article didn't meet some guideline.--Fabrictramp | talk to me 17:31, 27 March 2009 (UTC)[reply]
  • I agree with the rename, since speedy does sound a bit weird and informal and summary probably is better since it implies that the deletion is carried out without discussion (eg, summarily executed) LetsdrinkTea 02:42, 28 March 2009 (UTC)[reply]
  • I'm not keen on either "summary" or "speedy": To me, "summary" implies an official ruling that can't be overturned, when in fact it is or should be easy to recreate an article if there's been only a speedy deletion and no AfD discussion. I agree with FabricTramp about the connotations. "Speedy" might give admins the idea of deleting too soon after article creation etc. How about "simple deletion" or "gentle deletion"? "Simple deletion" preserves the acronym, but people may not like having their article "simply deleted". "One-person deletion"? Coppertwig (talk) 21:18, 28 March 2009 (UTC)[reply]
  • When "Votes for deletion" was renamed "Articles for deletion" the vote mentality didn't change, so I doubt any perceived advantaged of this move would work either. Also, it might confuse people who are actually trying to get an edit summary oversighted. - Mgm|(talk) 10:25, 29 March 2009 (UTC)[reply]

Dislike new name, "summary"

Resolved
 – Moved into section above

As I seem to have missed any discussion that may have taken place about this rename, I'll log my deep dislike of it here. "Summary" means several different things, and the meaning you're implying has unpleasant connotations, including lack of justice (not to mention death).

I'm curious as to what the problem was that prompted this "cure", where the consensus was sought and gained and how many users were involved in that process. --Dweller (talk) 14:21, 27 March 2009 (UTC)[reply]

There was a discussion here. It went for 3 days with ca. 10 people involved and ca. 3 people explicitly in favor. Imho that's not nearly enough consensus to rename a policy on. Also, see section above. Regards SoWhy 14:27, 27 March 2009 (UTC)[reply]
Just to nitpick, I see support from Black Falcon, Dcoetzee, Phil Bridger, Aervanath and myself. I hope I can still count... Happymelon 14:39, 27 March 2009 (UTC)[reply]
I said "explicitly". They way I rad it Black Falcon and Aervanath were not explicitly in favor of changing the name, just that "summary" would be okay if there was consensus to change it. SoWhy 14:47, 27 March 2009 (UTC)[reply]
Thanks. I'll move up there, then. --Dweller (talk) 14:28, 27 March 2009 (UTC)[reply]
Speedy is a bad descriptor and summary is a good one? WilyD 14:29, 27 March 2009 (UTC)[reply]
Let's leave this section now and keep the discussion in one place. --Dweller (talk) 14:33, 27 March 2009 (UTC)[reply]

Moved back

Summary justice is that with which, in their disdain, they have, in some few instances, prevailed upon themselves to indulge the vulgar herd.

Jeremy Bentham, Bentham's Draught for the Organization of Judicial Establishments

Given the comments so far about this move, I think it's clear to say that many disagree with the move. I've moved the page back to its original title for now and we can restart discussion. Ryan PostlethwaiteSee the mess I've created or let's have banter 14:52, 27 March 2009 (UTC)[reply]

I've no problem with that as long as we don't now get "it's been moved twice already" as a reason to oppose a move, which would be a little pathetic. Don't forget to 'unfix' the two double redirects (WP:CSD and WP:SPEEDY) that I updated; I left the other 70 (!) until we came to a conclusion. Happymelon 14:55, 27 March 2009 (UTC)[reply]

That summary justice is really the genuine, and regular the counterfeit, is what any one, who has read the observations of Article 21 of the preceding Title has, I trust, found some cause to suspect.

Jeremy Bentham, Bentham's Draught for the Organization of Judicial Establishments

At this point it would be sensible to summarise from the previous discussion. As noted by MZMcBride as the OP, we regularly encounter the misunderstanding that "speedy" implies either "delete as quickly as possible", or "delete without thought or evaluation". Neither of these are true, but we have a minor but recurring problem of admins who work CAT:CSD believing that they are. There is also the issue that a number of the CSD criteria have time limits which make a total mockery of the "speedy" concept; with some tags needing to be left in place for a week before "speedy" deletion is allowed. Black Falcon proposed "summary" as a replacement to preserve the CSD acronym, with connection to summary judgment; "summary" has the very appropriate meaning of "Performed speedily and without formal ceremony". Happymelon 14:55, 27 March 2009 (UTC)[reply]

  • "Summary justice" also means an absence of proper justice, it means vigilantism, not listening and a host of unhappy connotations for those who understand the term. For those who don't understand the term, there's the confusion of thinking it's something to do with precis. And I'm not sure I agree with the perceived problems with "speedy deletion" being really problematic. Can we do this a stage at a time, rather than rushing? I applaud your zeal, but for a useful process, start by discussing the problem. You may find there's no consensus that there is one, which would render everything else moot. --Dweller (talk) 15:01, 27 March 2009 (UTC)[reply]
    • If you define 'justice' for article deletion as a full AfD, then yes, CSD is summary justice. If you factor in WP:IAR, then yes, there is an element of vigilanteism. In the rather bizzarre quasi-legal structure that exists here, I think the phrase actually summarises the situation perfectly.

      I guess I should have explained what I was doing better, but a big reason for being bold was to encourage further discussion; see for instance the rather better explanation I gave here on a similarly bold update of {{mfd}}. You can't deny that the move has encouraged that discussion! Happymelon 15:10, 27 March 2009 (UTC)[reply]

    • But on the other hand, summary judgement is a judicial proceeding, albeit without a full trial on the merits. – ukexpat (talk) 15:17, 27 March 2009 (UTC)[reply]
  • Yes, the move did encourage further discussion! :) I reread the archive just now, and I didn't see a lot of consensus -- I did see a lot of people not taking the suggestion too seriously. However, since we're having a serious discussion now, I'll chime in. I'm not a fan of "summary", because of the association with vigilantism. Yes, speedy has its problems, but summary is not an improvement.--Fabrictramp | talk to me 15:15, 27 March 2009 (UTC)[reply]

I don't really have a strong opinion either way. "Summary" is a bit ambiguous, but "speedy" also has its flaws. Kudos to Happy-melon for boldly making an attempt to get the ball rolling. –Juliancolton Talk · Review 15:25, 27 March 2009 (UTC)[reply]

  • I think "speedy" conveys it quite correctly actually, except in those cases where the tags need to be in place for a week. But the point is that it's not "as fast as possible" but fast if compared to PROD or AFD. If an article is deleted after 12 hours, it's still 10 times faster than at AFD or with a PROD. So it's comparatively speedy. The only other word for it might be "criteria for uncontroversial deletion" because the only thing all criteria have in common is that they should not be applied when it's a controversial deletion. But speedy deletion has been established for years now and I do not think any change would be solving the underlying problem that some admins are too careless when speedy deleting. That won't be solved by a name change, if anything, "summary deletion" would encourage them to think that they are the "judges" of the deletion rather than just the janitors who clean up the mess. Regards SoWhy 15:59, 27 March 2009 (UTC)[reply]
    • I think speedy is the wrong word--the point of the process is not the time, it takes, but of clearing out the garbage without the need to discuss it, which more closely its "summary". I am not completely sure it's the best word possible, but it has an advantage in starting with the same letter. And it is the standard term for a roughly analogous legal process. DGG (talk) 16:06, 27 March 2009 (UTC)[reply]
And for executions without trial. I doubt people know the legal process, but they probably know "summary execution". And as pointed out above, summary deletion would rather be a correct name for AFD because allows involvement by both parties, not only one like speedy deletion usually does. I think speedy needs to be read as compared to normal deletion because it still is faster than going through deletion discussions. A replacement word would have to show that it only applies when there is no need for discussion, so the correct name in that case would be "criteria for deletion without discussion". Regards SoWhy 16:14, 27 March 2009 (UTC)[reply]

Not thinking of it in legalistic terms at all is a better approach. As noted, the legalisms are prone to misunderstanding and creative misinterpretation, always at risk of metamorphosing into arguments over actual law, and also subject to simple ignorance of specialist meanings of words in favour of general meanings. After all, Wikipedia isn't a court of law or a social experiment. Start renaming things to legalisms, and soon people will be quoting Jeremy Bentham at you to tell you why Wikipedia's "summary deletion" isn't the same as summary justice. ☺ Uncle G (talk) 16:11, 27 March 2009 (UTC)[reply]

  • I oppose renaming to "summary deletion" - it has few identifiable benefits, and the new name smacks of quick legal proceedings, treating the subject with disdain. Basically, I agree with Uncle G above. We may not mean it in that way, but it gives that impression nonetheless. The current name is fine IMO. ╟─TreasuryTagcontribs─╢ 16:17, 27 March 2009 (UTC)[reply]
  • I don't think summary is a good word here. While it seems correct in juridical sense, most of people are probably unfamiliar with it and first thing a wiki editor would make a connection to is the edit summary. And this does not make much sense. My personal opinion is that the expression speedy is just fine - how fast does a bad article get deleted after being tagged? Speedy. Not to mention copyvios and BLP violations that actually should be deleted as fast as possible. By the way, a great deal of people would also think that Jeremy Bentham is in fact John Locke. :-) --Tone 16:18, 27 March 2009 (UTC)[reply]
  • Yeah, I hadn't thought of the edit-summary confusion. I'll just offer up swift deletion since it fits the initials and I just thought of it, but it's no real improvement. Just leave it as it is, I reckon! ╟─TreasuryTagcontribs─╢ 16:27, 27 March 2009 (UTC)[reply]

Oppose - this renaming is a needless waste of everyone's time. Even if it would have been better to call it "summary deletion" originally (which I doubt, for reasons given by others above), changing it now can't possibly be worth the hassle. And even if it were, it's extremely unlikely to achieve a wide enough consensus to do it. So I'd urge those who wanted the move to reconsider and find something more constructive to do. Rd232 talk 16:26, 27 March 2009 (UTC)[reply]

How is it a waste of everyone's time? Nobody is forcing anybody to participate in this discussion. –Juliancolton Talk · Review 16:29, 27 March 2009 (UTC)[reply]
Actually, if you move this page, you break the entire Internet. True story. --MZMcBride (talk) 17:26, 27 March 2009 (UTC)[reply]

Oppose. Whether the name of a well-known Wikipedia page needs to be changed depends on the intended audience. Who are we trying to convince that speedy deletions shouldn't be thought of as speedy? If admins, then we don't need to change a page name to do that, we can simply discuss it with the admins and tell us/them the decision. Taggers? No, I actually want them to think of the deletion as speedy; I want someone who's considering a WP:CSD G7 of their own creation to think "I better do this only if I'm certain, because if I do it, the page is likely to be deleted speedily." I want someone tagging for db-spam to think "I should only tag this page if the tone is so obviously promotional that it should be deleted speedily, without discussion." And as I said above, I don't want to be arguing with attack-page-creators and self-promoters about why I deleted their page so fast; "speedy" says it for me. - Dan Dank55 (push to talk) 17:09, 27 March 2009 (UTC)[reply]
Oppose name change This is a solution looking for a problem. The name of Speedy Deletion is not an issue, and any minor confusion/ambiguity would be compounded by naming it "summary deletion". We already talk about "edit summaries" and such, so using the word for an entire category of deletion would simply confuse new users. At least with "speedy deletion" the word "speedy" means the same thing every time (at least close enough to avoid major confusion) it is used. I do not see a need to change it; no compelling problem exists. The Seeker 4 Talk 17:21, 27 March 2009 (UTC)[reply]

Bold commments don't really help form consensus. --MZMcBride (talk) 17:26, 27 March 2009 (UTC)[reply]

This problem taxed the minds first of the cloning engineers, then of the priests, then of the letters page of the Sidereal Record Straightener, and finally of the lawyers who experimented vainly with ways of redefining murder, re-evaluating it and in the end even respelling it in the hope that no one would notice.

The Hitchhiker's Guide to the Galaxy, Fit the Eleventh

I have to flip my opinion - I think the current name is misleading, but that "summary" has its own misleading aspects - most importantly, many people are simply not familiar with the use of the word in that sense. I would support "Deletion without discussion" but that would change the acronym. Dcoetzee 20:02, 27 March 2009 (UTC)[reply]

  • If you must have an 'S'-word to replace Speedy, I would suggest Simple. I think the important connotation here is that the deletion decision is a simple one: does the article meet the predefined criteria for what should be deleted? If yes, then it can be SD'd (sorry, no snappy verb). If no, then a more complex procedure should be followed. SHEFFIELDSTEELTALK 20:39, 27 March 2009 (UTC)[reply]
    • "Simplified" doesn't quite hit the mark, does it? That's actually an interesting suggestion. It at least has the dual advantages of (a) not being a legalism, and (b) not having the connotations of the other words immediately below. ☺ Uncle G (talk) 20:11, 28 March 2009 (UTC)[reply]
  • Other S words suggested from before: "scheming, secret, sharp, shifty, shrewd, slick, sly, smart, smooth, sneaking, sneaky, stealthy, subtle, supervisory, surreptitious"... Instead of Criteria for Speedy Deletion, we can have Cabal Scheming for Deletion. ;-)--Fabrictramp | talk to me 22:58, 27 March 2009 (UTC)[reply]

I disagree with changing to "summary deletion". "Speedy deletion" indicates exactly what the process is; "summary deletion" simply does not. No need to change this so only WP policy fans get it intuitively. Townlake (talk) 22:51, 27 March 2009 (UTC)[reply]

  • My two cents is that I also dislike the "summary deletion" name, and much prefer "speedy deletion". Lankiveil (speak to me) 00:43, 28 March 2009 (UTC).[reply]
  • I also oppose the name change. While there could be a better name than "speedy", "summary" is not the way to go. What about "procedural deletion"? That embodies the hard-line attitude that's taken towards it, as a juxtaposition to the "discussion" style that AfD is supposed to be. ThemFromSpace 03:17, 28 March 2009 (UTC)[reply]
  • This is another of many recent proposals based on the odd idea that re-naming something actually changes the way it will work. Playing a shell game with the name is not going to change anything, so I am also opposed to this idea. If you want to change the actual process that is a different matter. Beeblebrox (talk) 19:25, 28 March 2009 (UTC)[reply]
  • Oppose, unnecessary busywork. Stifle (talk) 22:40, 28 March 2009 (UTC)[reply]
  • No problem with the bold move of renaming the page - that's how Wikipedia has progressed. A shake of the head and a loud tut at all those who winged and moaned like old nanny goats when an experienced editor in good standing simply cut through process and made a bold edit. However, I see no gain from renaming the page, and much to be lost. It is a well used name, and conveys the sense of the job just as well as the proposed new name. If there are problems with the speedy deletion process, then those problems need to tackled directly. Renaming speedy to summary to prevent inappropriate tagging, is like wallpapering over the cracks of a house with subsidence. SilkTork *YES! 23:05, 28 March 2009 (UTC)[reply]
  • I agree with the suggestion that "deletion without discussion" is the best name for this process, and that's the one I'd vote for if we were creating this process from scratch. But "speedy deletion" does a good enough job of describing the process and it has a lot of history and general knowledge among our contributors. Changing it really is unnecessary busy-work; it makes little or no difference to the ultimate goal of actually creating an encyclopedia: how we execute this process is far, far more important than what it's called. ~ mazca t|c 00:16, 29 March 2009 (UTC)[reply]
  • Oppose I never saw the problem with speedy, and honestlty after reading most of the discussions still don't see a problem with it. I will note that I had to fix a broken redirect to this page (encountered when clicking a link in a CSD template). I thought we had a bot for that? §hepTalk 01:32, 29 March 2009 (UTC)[reply]
  • Oppose the use of "summary" as an attempt to solve a nonexistent problem by making things worse. DreamGuy (talk) 18:40, 30 March 2009 (UTC)[reply]
  • Oppose this is of very low importance, the status quo is acceptable, and there is no obviously objectively better alternative. honestly, find something better to work on. --Cybercobra (talk) 01:04, 1 April 2009 (UTC)[reply]

Yet another What's Wrong with CSD section

The section header says it all. :)

In the discussion above about renaming CSD, it seems that several of us are on the same page (no pun intended) about the problems with CSD. Namely:

  • Too many pages are getting deleted when editing, redirecting, or merging would be more appropriate, more helpful to the reader, and less bitey
  • There's too much of a "race" mentality, both with NPP tagging for deletion and working through the category, although this mentality may just be among a highly visible minority of editors and admins
  • Whatever changes are made need to encourage more thought going into each deletion.

Suggestions I recall from the past involve renaming CSD, adding a mandatory wait period between tagging and deletion (similar to PROD), and a mass campaign of educating editors and admins (which I can tell you from personal experience feels like trying to empty the Pacific Ocean with a teaspoon).

Closely tied into this is the issue of admin accountability. While I personally think the recall process (or lack thereof) is a complete fail, I'm also uncomfortable with the fact that unless an admin really goes off the deep end, there's not much real accountability for things like bad speedy deletions. (And similarly, not a whole lot of incentive for editors to improve their tagging.) Sure, I can remove tags, rewrite, or restore articles myself, but for those of us who take the time to do that, there's a high frustration level (and probably a high burnout rate). Not to mention the high probability that potentially good new editors are scared off by getting a speedy notice 2 minutes after their article is created.

So, any brain storms on how to improve this process?--Fabrictramp | talk to me 16:29, 27 March 2009 (UTC)[reply]

  • How about taking each and every incorrect speedy deletion to DRV and overturn them? Noone likes to be wrong and if an admin gets a dozen speedies overturned each week, they might be more careful. ;-) SoWhy 16:41, 27 March 2009 (UTC)[reply]
    • My impression is there's broad support for all of these ideas. I started off always leaving a message on the tagger's talk page and keeping the diffs at the (unlinked) page User:Dank55/csd whenever I declined a speedy tagged by a registered account; these days, I always put the reason for declining the speedy on my own talk page, and leave a talkback on the tagger's page that links directly to the right section on my talk page, because some taggers were annoyed by the perceived wrist-slapping on their own talk pages. The goal is to provide anyone easy access to all my speedy decisions (you can see all the actually deleted pages in my logs and all the non-deleted pages on my talk page), and open up communication with the taggers, and (sneakily, I suppose) provide admins a quick way to see if taggers are really not getting it ... a lot of talkback notices to my talk page is a bad sign. - Dan Dank55 (push to talk) 16:47, 27 March 2009 (UTC)[reply]
      • So how do you handle taggers who don't get it? I don't get many taggers who are truly annoyed by my messages (I can only think of one, probably because I always explicitly say it's a friendly message), but I don't have a good strategy for the ones who ignore the messages and continue with bad tags.--Fabrictramp | talk to me 17:28, 27 March 2009 (UTC)[reply]
These days, it's a different tagger virtually every time there's a mistake. The one tagger that both you and I were concerned about earlier has stopped tagging, it appears. If I run into another tagger who seems to be a problem, I'll discuss it with them privately first, and if that doesn't work, with other admins who work at CSD. - Dan Dank55 (push to talk) 04:11, 28 March 2009 (UTC)[reply]
Yes, it does seem like the ones who don't get it eventually get bored with tagging and move on to something else. Which might be part of what leads to the emptying the ocean with a teaspoon feeling -- a new tagger comes along to replace them, and the education starts all over. :) --Fabrictramp | talk to me 16:44, 28 March 2009 (UTC)[reply]
  • Fewer pages would be deleted if more care went into creating worthwhile new articles and more filtering to prevent new junk. That would set the practical standard higher for speedy deletion, maybe lead to cleanup/fixing more often; speedy deletion would be a bigger decision (hopefully) more carefully made; maybe even made redundant. The only way to do that (that I can think of) is to make it harder to create new articles. One could turn Articles for Deletion into Articles for Creation, and speedy deletion into speedy creation (both ideas would need a lot of elaboration and might be unworkable...) - it would be less bitey to newbies to have a suggestion rejected than work they've done deleted, and maybe frame debate in a more positive way. But I suspect such a radical change is virtually impossible to develop consensus for now, regardless of the merits of concrete versions of it that might be developed (probably have been somewhere...). Rd232 talk 17:02, 27 March 2009 (UTC)[reply]
I would want to argue that there is not really that much "true junk", just admins who delete terrible-but-ultimately-worthwhile pages as such. For example I got a track record of 25-30% declined speedy deletions. If people had instead tried to fix those articles instead of tagging, we would have a lot less work. Regards SoWhy 18:00, 27 March 2009 (UTC)[reply]
Maybe. But in borderline cases it takes a bit of work to judge whether something is worthwhile, never mind improve it. So if article creation were more consistently a collaborative process, instead of New Editor X starting something on their own (having at best a passing acquaintance with how to do it), there'd be a whole lot less articles being proposed for CSD, which would allow more attention on each one. And there'd be a whole lot less pissed-off New Editor Xs. Rd232 talk 18:08, 27 March 2009 (UTC)[reply]
Just for grins, I popped over to CSD and worked on three articles. One was a true piece of crap that unfortunately didn't meet any CSD criteria. One has about a 50% chance of surviving AfD and made a clear claim of importance, but needs help. The third has about a 95% chance of surviving AfD, made a claim of importance (but I could see how someone could miss the claim), and was well written.
The idea of more collaboration on new articles is intriguing, but I don't think it should be mandatory. If I can write a well-written, well-referenced stub on a 19th century baseball player, should I be forced to wait until someone else is interested enough to collaborate on the article? Yeah, someone may come along and mistag it for deletion, but personally I'd rather take that chance. However, it might be a great place to point newbies who are having trouble writing that first article.--Fabrictramp | talk to me 18:33, 27 March 2009 (UTC)[reply]
I can't see how to make it effective without making it mandatory. For example - off the top of my head, so don't stake me for it - through a flagged revisions sort of thing just for new articles - anyone can create an article, but it only goes public when someone reviews it and OKs it. Combine that with prominent links to AFC for more organised collaboration/discussion particularly for newbies. Optionally could apply the mandatoriness only to new editors (however defined) since it's primarily aimed at forcing them into a minimum of collaboration/discussion. Or X zillion other ways to do it I'm sure, but without mandatoriness of some kind there's not much effect, as the existence of AfC since 2005 shows. (I'm not saying it's useless, it's just if it really worked CSD would be unnecessary.) Rd232 talk 18:45, 27 March 2009 (UTC)[reply]
Yeah, it's that "really works" part that gets you every time. :) One possible improvement would be to make it mandatory only for editors with fewer than X edits, or the opt-out is only available upon request to experienced editors (along the lines of rollback). But then the problem comes in of who reviews? Can't be another new editor, or else the sock/meat puppets will figure out that trick in a flash. What happens when the reviewer isn't thorough, but instantly decides something's crap (along the lines of the current CSD problem)? Probably a dozen other issues, but it's almost lunch in my time zone, so my brain isn't cooperating with thought requests. :)--Fabrictramp | talk to me 19:31, 27 March 2009 (UTC)[reply]
Also, patrolling has a huge backlog already and that way we'd get articles that take days or weeks to be approved, effectively taking what peopel like about Wikipedia, i.e. that what you change appears immediately. SoWhy 20:04, 27 March 2009 (UTC)[reply]
True, but by limiting the population of editors subject to new article review you limit the backlog; also such a system should reduce workload elsewhere (eg AFD, CSD). A disputed rejection can be taken to AfC for further debate. As to putting people off because their changes don't appear immediately (a) it only applies to new articles, they can make changes to existing ones; (b) people shouldn't be creating articles in order to get a kick out of Its Online Now! - WP:NOT a blog. Constructive additions can wait a few days for it to go fully public, and can see and edit the draft in the mean-time, and even tell friends to go look at the draft, etc. Well anyway these are the sort of ideas that would need hashing out if it seemed at all plausible that the community might agree to a sufficiently well-thought proposal (which this isn't!), which I'm not convinced of. Rd232 talk 15:35, 28 March 2009 (UTC)[reply]

(outdent) I've recently starting reviewing articles at AFC, and it is a pretty good "filtering" system. It not only catches articles that would be CSD'ed but also allows reviewers to place an article "on hold" and ask the newbie to try and find better sources, clean up the tone, or whatever else. In this way it not only filters new articles but educates new users, allowing a chance to show them how good new articles are created. I think it would be a good idea if all pages created by very new users went through such a process, but I also think we'd be in for a long, difficult struggle to make that happen, a lot of people will see it as "more bureaucracy" even though the idea would actually be to reduce the number of speedy deletions and educate new users. Some CSD'ed articles are made with deliberate bad intentions, but I think the majority of speedyable articles are made by new users who haven't taken the time to familiarize themselves with our most basic policies, and this would more or less make them aware of those policies in advance instead of after their article is already deleted. Of course, it's also all dependent on there being enough people willing to reveiw new articles, but there would be a lot less "newpage patrolling" going on, that should free up a few hundred users... Beeblebrox (talk) 19:42, 28 March 2009 (UTC)[reply]

"Broken" redirects

redirects to invalid targets, such as nonexistent targets

are considered fair game for speedy deletion. We should recall from time to time how this criterion got there. It was by bullying, not be consensus. It happened in the spring of 2005. Formerly there had been exceptions. There are some really obvious reasons for exceptions. But those who wanted to delete indicscriminately ALL redirects to non-existent targets (1) dishonestly denied that any exceptions had ever appeared in the policy; and (2) denied that they had ever heard of any reasons for exceptions, after those reasons had been repeatedly and patiently explained to them. Michael Hardy (talk) 02:11, 28 March 2009 (UTC)[reply]

{{context}}. —David Eppstein (talk) 02:30, 28 March 2009 (UTC)[reply]

An excerpt from the discussion of four years ago, in March, 2005:

For example, I know enough to know that Eastern Sudanic should redirect to Eastern Sudanic languages, but I could not posisbly write even a stub article about that. A Wikipedian could easily know, from having read a variety of instances, that coupled harmonic oscillator is not one of those phrases that are always plural, so the plural should redirect to the singular, but may not know whether the topic is physics or music or New-Age philosophy. Such a person could not possibly write a stub on that topic, but could easily write a valuable pre-emptive redirect.

I wouldn't think something like that would be hard to understand, but I found people denying that I had written it after I did. Michael Hardy (talk) 02:35, 28 March 2009 (UTC)[reply]

  • Could you perhaps tell us exactly what you'd like to happen? --Fabrictramp | talk to me 16:40, 28 March 2009 (UTC)[reply]
    • Xe would like a more nuanced criterion. Ever since it was first added in 2004 the criterion has been a simple mechanical rule that redirects to non-existent pages are deletable on sight, if they cannot be fixed to point to an existing page. But the most common use of the criterion would appear to be the cleaning up of redirects pointing to pages that have themselves been deleted. If you are asking for an exact wording suggestion, please observe that Michael Hardy has had a proposal containing exact wording on the table since 2005. You can find it in the archives of this very talk page. ☺ You can also find the counterarguments, relating to the value of redlinks, the difficulties incurred by making simple mechanical speedy deletion criteria into subtle rules, and suchlike, there and at the discussions that it in turn links to. Uncle G (talk) 19:12, 28 March 2009 (UTC)[reply]
  • And the problem with this is... Stifle (talk) 22:38, 28 March 2009 (UTC)[reply]

Stop the wholesale Deletion of the Usepages of Indefinitely Blocked Users

The deletion of “usepages of indefinitely blocked users’, especially the talk pages, should stop until such deletions are properly described here at WP:CSD. The policy problem is that these deletions are not covered by WP:CSD or any XfD. The actual problem is that the category is too broad and includes pages that should not be deleted.

For example. User_talk:posturewriter contains in its history a lot of material relevant to the development (and misdevelopment) of mainspace articles. To start to understand the history of the mainspace articles, this user_talk page is important.

It also contains records relevant to the development of WP:MEDRES. This guideline is important but causes problems with some new contributors, and deleting the talk pages of those who have the troubles is not a method for revealing shortcomings in the guideline, and improving on them.

This talk page contains material useful for the development of wikipedia mediation issues. Mediation, or education of the stubornly wayward, or how to cope with the pain and disruption of kooks, however you choose to look at these kind of problems, is definitely an area where we would like to do better. It is not helpful to delete the userpages of every constructive editor who had trouble with our rules, became belligerent, got indefinitely blocked, and didn’t proceed to appeal within one month.

I’m not wholesale against the deletion of userpages of indefinitely blocked users, such as vandalism only, or personal attack only, but the talk pages of users who made good faith contributions to mainspace should not be deleted out-of-process. The example page was even kept at MfD, before being deleted following a series of knee-jerk administrative decisions. --SmokeyJoe (talk) 22:30, 28 March 2009 (UTC)[reply]

I agree with this, but the discussion should be taken up at WP:AN I think. Stifle (talk) 22:37, 28 March 2009 (UTC)[reply]
I agree with Stifle. This is not the place for this discussion. Administrator's Noticeboard and the Village Pump are the place for this kind of discussion. --Ryan Delaney talk 22:45, 28 March 2009 (UTC)[reply]

I hate it when important policy matters are discussed and lost at WP:AN. This is clearly a matter of deletion policy. Deletion policy should be described, for the benefit of those doing it, or subject to it. Non-XfD deletions should be codified here. Cross-post at WP:AN and pumps by all means. --SmokeyJoe (talk) 22:52, 28 March 2009 (UTC)[reply]

This is how we have handled these pages for years. I think the harm associated with it is greatly exaggerated. Policy has yet to describe this long existing practice, it needs to catch up and our practices should not have to wait for that. Chillum 22:59, 28 March 2009 (UTC)[reply]
Unfortunately, it only takes just one admin to do it this way for years. Unless someone questions it, as in the recent spate of deletions of "secret pages", we won't even know what the concensus is because many users (especially ones who can't see the deleted pages) won't ever see what was deleted. Just yesterday I was scratching my head over a "new" user talk page that appeared on my watchlist. After a bit of poking, I realized that I had watchlisted it before the user got indef'd, then someone deleted the user and talk pages, and now someone else had posted a sockblock template on the talk page, making it show up on my watchlist. Later, someone will come along and delete it, still later someone will template it -- how is this in any way productive? If you need to get rid of something on the user/talk page, delete it once and immediately put up some kind of template that says "indef'd and deleted", and then leave it the heck alone.--Fabrictramp | talk to me 23:39, 28 March 2009 (UTC)[reply]
You might dislike the convention, but I can almost guarantee that you won't get the result you want if you try to confine the discussion to the CSD talk page. I understand that it seems strange that you would have to take a discussion about a CSD policy elsewhere (and, contrary to Chillum, I don't think that "We've done it that way for years" is a justification for anything at all). However, the reason this is CSD policy is (if I recall the history correctly) because it was being done so widely that someone thought it should be put in the policy somewhere. Policy pages on Wikipedia are not laws; they are summaries of "best practices" as they are figured out in the field, and thus are kept up to date with what is generally done, not the other way around. Reverting long-standing consensus requires many eyes; this page is not heavily trafficked enough for that. Therefore, forming consensus on this talk page will have the appearance of attempting to push through policy changes using procedural loopholes (forming "consensus" with only a few people who pay attention to this talk page, where others might have very strong dissenting opinions). As it happens, I tend to agree with your attitude about this, but you won't get any support from me (or most others, I would wager) unless you bring it to a wider audience. --Ryan Delaney talk 23:03, 28 March 2009 (UTC)[reply]
There is a basic misunderstanding of wiki process here. It starts with discussion in the smallest group, not the largest. If no consensus is found here, then discussion, per WP:DR expands. The noticeboards are often used, but they are actually a bad idea; they are hot environments, with lots of editors making snap judgments, and the questions get easily diverted. (But there is no harm to a mention of ongoing discussion on AN, or the Village Pump, for that matter, but RfC is better. With a good RfC and if consensus isn't obvious at the conclusion, there are issues here that would be appropriate for ArbComm, and a good RfC helps to delineate the issues.
I dislike that anyone would withhold local consensus based on a wider group not having been consulted, it violates basic principles of deliberative process, i.e., objecting based on what you think some other imaginary editor might think. If any editor here thinks that any specific editor would have something to contribute to this, or would object to some new consensus here, the editor is totally free to inform that person, it isn't WP:CANVASS violation unless such a notification is widespread or designed to support the alleged canvassing editor's POV, and my objection is obviously only to what Ryan expressed: "I tend to agree," but "you won't get any support ... unless you bring it to a wider audience." Someone who thinks a wider audience is needed should take it to the wider audience, not reject a good idea in order to force someone else to do that. --Abd (talk) 18:41, 29 March 2009 (UTC)[reply]
Having done it for years without any apparent problem is a pretty good indication it is not a problem. Some vandals have nothing better to do than stir up a bunch of shit on their talk page before during and after their indefinite block just to have this trophy page. We deny them that trophy. It has nothing to do with building an encyclopedia so we don't host it. This is simply a matter of housekeeping, crap piles up, we remove it. Chillum 23:17, 28 March 2009 (UTC)[reply]
The thing is, it's getting done as a kneejerk reaction. If the crap needs to be flushed, then flush it, but think first. (And if it's just juvenile stuff, blank it). Unfortunately, a small number of admins think every indef'd talk page needs to be deleted.--Fabrictramp | talk to me 23:41, 28 March 2009 (UTC)[reply]
[citation needed]. There's been tons of discussion on this subject and the pages deleted are generally checked against several criteria, in addition waiting at least a month after the last edit to delete it. Mr.Z-man 05:29, 29 March 2009 (UTC)[reply]
In my example below, the talk page was deleted after slightly less than a month (but only 4 days, so I don't think that is a big deal). But what were the criteria for deleting it? There was absolutely nothing that needed to go, and there definitely was useful information for people keeping an eye on that sock.--Fabrictramp | talk to me 15:48, 30 March 2009 (UTC)[reply]
It's not the vandalism accounts which are the problem - these have been happily deleted for years, but the talk pages of contributors with a 'meaningful history' in their talk page which is useful to the encyclopaedia. These were never part of CAT:TEMP when it started, for the same reasons that sockpuppets were pulled out of the category. Numerous discussions, for example at WT:UP have pointed out that these pages can be useful without being considered trophies. As the deletions are mainly done by bots looking through CAT:TEMP, the problem mainly lies in the blocking templates which puts them there, in particular {{uw-block3}}. -- zzuuzz (talk) 23:45, 28 March 2009 (UTC)[reply]
I'm confused then. (No big surprise). User talk:Angels Live is the page I refered to above. This edit, which put an indef block and sock template onto the page, also added Category:Temporary Wikipedian userpages. If you look through the edit history after that, having a working indef block template means they are in Category:Temporary Wikipedian userpages. Is there some other template people should use to keep those pages out of the temporary category? If so, apparently not everyone knows about it.--Fabrictramp | talk to me 01:42, 29 March 2009 (UTC)[reply]
{{do not delete}}. Its already contained in all the sock templates and I believe all the spam-warning templates. Or just don't put {{indef}} on the page, or use {{indef|historical}}. Mr.Z-man 05:24, 29 March 2009 (UTC)[reply]
Chillum. No apparent problem? Did you look for problems? Was the editor effectively silenced with easy to find evidence of appeal? Was a potentially valuable contributor put off due to being treated harshly, with the ultimate door slam of DELETION of his talk history and ability to edit under his chosen username. What about our reputation for dealing with people? We are not talking about vandals and trolls. Vandals and trolls have little hesitation in creating new accounts. I am talking about the contributors of some good and lots of “good faith” contributions. These people are blocked. Why delete the talk history? Just because you can’t see a purpose, it doesn’t mean that there can be no purpose. Unless you already know everything that is useful to know? Have we nothing to learn (think communication effectiveness of guidelines, wikipedia mediation processes)? The costs of failing to learn can be incalculable. --SmokeyJoe (talk) 23:46, 28 March 2009 (UTC)[reply]
Valuable contributor? These are people that are indef blocked, by definition no longer welcome here. If there is a good reason to not delete a page, remove it from the category. If someone needs it for future defense they can ask for the contents. This seems like a tempest in a teapot here.
I see this is a passionate subject for you. For me it is a simple matter of housekeeping, I have no strong feelings on the matter. I do have a position though and I have explained it. Chillum 23:57, 28 March 2009 (UTC)[reply]
This is about clarification of policy. Should every indef block lead blindly to userpsace deletions after one month? When looking into the history of things (controversial mainspace pages, policy effectiveness, guideline interpretation issues, development of how we do things, I don’t want to not find a whole section of our history because it was automatically deleted for no good reason, and if I do find out about deleted information on talk pages, I don’t want to have to ask for it, each and every time. People are indef blocked sometimes with an expectation that they may see the error of their ways, and apologise in an appeal. People are not always indef blocked because everything they have every done was without value. --SmokeyJoe (talk) 00:08, 29 March 2009 (UTC)[reply]
No, this is not personal for me. It see a need for improvement, and making changes is only getting harder. --SmokeyJoe (talk) 00:08, 29 March 2009 (UTC)[reply]
We're here to build an encyclopedia, not to keep a candle burning in the window for forlorn problem children to see the error of their ways. People must be held accountable for their own actions, and if their actions are so egregious as to warrant an indef, then, IMO, good riddance. Tarc (talk) 00:31, 29 March 2009 (UTC)[reply]
My point was that there sometimes is value in the past contributions of an indef blocked user, and that there can be material of use in the talk page history, and that the history of what happened with a now indef blocked user can be very important in our policy and process development. It is not about candles, or one last hope for rehabilitation. I am asking for the histories to be kept available behind the blanked pages of the blocked user. Is there a serious suggestion WP:DENY asks for talk page revisions to be routinely deleted for every blocked user? --SmokeyJoe (talk) 00:51, 29 March 2009 (UTC)[reply]
Tarc has explained my position fairly well. Chillum 00:35, 29 March 2009 (UTC)[reply]
I agree with Tarc as well. --MZMcBride (talk) 04:25, 29 March 2009 (UTC)[reply]
I love reading the minutiae of Wikipedia operations, so I have several reasons to request that indefinitely blocked users with substantial contribution histories be kept: 1. Reading the history of such events is educational for new editors such as myself; 2. Where user pages have been deleted, the resulting lack of transparency will sometimes result in accusations of conspiracies and cabals; 3. Precendent is important in courts of law, so case details are always preserved; this seems like a fine principle for WP also; 4. A user starting afresh may unwittingly be tainted by the name of a blocked user. cojoco (talk) 04:54, 29 March 2009 (UTC)[reply]
  • I have no particular opinion about userpages, but user talk pages should be left untouched unless it contains libel or slander something else that is illegal in the real-world sense. Deleting such pages makes it harder to compare edits of new vandals to old ones and let's them get away with things that would otherwise be easily handled. The speedy deletion criteria says that pages by a blocked user in violation of their ban should be deleted, but it doesn't say anything about other pages they created before they were banned. Obviously using userpages as a webhost after the block should be stopped, but there is no particular reason to delete talk pages. Admins can thrawl deletion logs. Any other user would be left in the dark if they tried to investigate the blocked user's history. - Mgm|(talk) 10:22, 29 March 2009 (UTC)[reply]
  • I cannot see any actual purpose in deleting most of these pages. It does not reclaim storage. It uses work of both the server and whoever is doing it. Andthere are many inactive users who return after a while. We need all we can get. DGG (talk) 16:18, 29 March 2009 (UTC)[reply]
You cannot return if you've been indef blocked. Pages of retired or inactive users don't get deleted. If there is anything of value on a blocked user's talkpage (not just vandal warnings and CSD notices) then you can add the historical tag to the {{indefblock}} template. Users with sockpuppet templates aren't deleted either. OrangeDog (talkedits) 17:21, 29 March 2009 (UTC)[reply]
Simply not true. I was indef blocked. Lots of users are indef blocked or even banned and return; indeed, we prefer that they return, if they do, with their original account. "Indef" means "blocked until unblocked," which might or might not mean forever. There is an additional problem. Sometimes editors are abusively blocked, but for various reasons the community never ends up looking at it or only looks at it much later. Later on, reviewing the actions of an administrator, it can sometimes be seen that there was inadequate warning, or no warning, the admin was in a conflict with the editor, or was even insulting the editor, I can think of an ArbComm case where bad blocks were dug up much later, and helped to show a pattern. Delete the page, only admins can see it, and admins are overwhelmed already. DGG is right. Deleting these pages is make-work that brings no value to the project; certainly many of these pages also bring no value, but others do. There is no harm in blanking the pages, and truly harmful pages can be deleted anyway because of the harm, not because of the indef block, and it's clear that sometimes Talk page deletions are done by admins in service of their own POV. This is rare, I think, but it can help cover the tracks of an abusive admin, and abusive admins can do a lot of damage before our extraordinarily cumbersome process catches up with them. --Abd (talk) 18:05, 29 March 2009 (UTC)[reply]
The vast majority of the pages that are deleted for this reason are vandal-only accounts and username-blocks. Userpages of sockpuppets, banned users, and spammers are kept for tracking purposes. Even then, deleting the talk page doesn't make it impossible for them to appeal. Mr.Z-man 17:39, 29 March 2009 (UTC)[reply]
Vandal-only accounts, if it's truly vandalism -- that should be quite clear and not merely a matter of POV -- should indeed be grounds for deletion. But I've seen the temp category used to delete talk pages for editors who did make useful contributions, but who ran afoul of this or that administrator. I've seen an account blocked for alleged username violation that wasn't; being able to track the warnings and conversation helped me greatly to understand what happened; eventually, some justice will be done, but it takes one step after another, beginning with establishing that this editor actually made positive contributions, and that work should be done within weeks. (The proof will be that the contributions returned, more than a year later, with consensus.) Delete the pages, only an admin could do this kind of follow-up work, thus increasing workload on admins at the same time as concentrating ever-more power in their hands. Structurally, very bad idea. (However, expand the class of editors who can review deleted pages, make that an easily-granted privilege like rollback, then deleting such pages becomes far more reliably harmless.) --Abd (talk) 18:11, 29 March 2009 (UTC)[reply]
  • Is any purpose served by deleting the pages? I can see several reasons, and some minor value, in keeping them. Among these are the need sometimes to review (often years later) what happened to an article and why certain edits were made, for example to track down a copyright violation or review a new suspicion of sockpuppetry. Deleting inactive accounts strikes me as problematic in the same way that deleting any historical records is - you lose your history. Inasmuch as ther is usually nobody to stand up for an indef blocked account, there is no check and balance on the deletion process. Rather than deleting, I suggest categorization, moving, templating, or some other way to flag a user as being of no value to the encyclopedia and kept only to preserve the record. Wikidemon (talk) 17:54, 29 March 2009 (UTC)[reply]
Absolutely. Further, categorization or the other approaches is easily reversible and can be done by any editor. The wiki system allows individual editors to make decisions subject to review. Deletion makes review possible only for a small class of editors, difficult to join under present conditions. Deleting history is truly dangerous in the long run, there should therefore be broad consensus on the necessity of it. Nobody to stand up for an indef blocked account. Yes, often, and when the blocked editor simply goes away mad and convinced that Wikipedia itself is abusive, rather than merely the blocking admin, long-term, deeply-rooted damage is done. This happens particularly to experts, who are quite vulnerable. I'm working on an RfC right now which involves an expert, and I've seen other prior cases. Experts can easily become uncivil when confronted with tenacious disrespect from non-experts. It's a fault (I point out to them when I can -- it's not professional), but a common one, and we need to deal much more carefully with experts if we want to retain them, as we should. Instead, we insult them as "POV-pushers" (big surprise, experts often have a strong POV!), attack them as COI because they have published in the field, block them quickly for incivility, ignoring incivility directed against them, and generally treat them worse than vandals. This is a huge problem. I would not suggest turning the project over to experts, but we'd better welcome them, particularly in Talk, or we will continue to spread the reputation I have found common among experts that Wikipedia is hopeless. The expert editor I have in mind was recently blocked (February, I think), and the Talk page was rapidly deleted citing the speedy criterion discussed here. Eventually, I'll get this fixed, but it takes a huge amount of work to clean up one of these messes. --Abd (talk) 18:27, 29 March 2009 (UTC)[reply]

Real numbers instead of random guesses

Rather than making random guesses about how many pages are in the category that shouldn't be, I decided to actually do some checking. At the time I started writing this, there were 2,529 User talk pages in the category. Of these, 9 (0.3%) have at least 100 revisions. On the other hand, there's 2,316 pages (91.5%) that have no more than 10 revisions and 479 (18.9%) that only have 1. Looking at the 9 pages with more than 100 revs:

So of the 0.3% of pages that have a significant amount of revisions, 2 would have been kept anyway under the current criteria (sockpuppet tracking) and only 4 (0.16%) of the remaining had useful history. In any case, since the query is fast enough, I'll be changing the bot that maintains the category (i.e. removing sockpuppet pages, and pages of users not actually blocked) to remove pages that have >= 100 revisions. Mr.Z-man 19:25, 29 March 2009 (UTC)[reply]

Thanks for the info. I tend to agree that even a 0.16% redunction in the false positive rate is a good thing given the uncertainty over what the rate really is, and the relatively low improvement to the encyclopedia on an incremental basis for each true positive. What are the numbers for 50, or 20 revisions? I would think that even 20 revisions on an indeffed account's talk page indicates that there may be a substantial history with something useful in it. Wikidemon (talk) 20:23, 29 March 2009 (UTC)[reply]
For sockpuppets, make sure your bot removes the {{indefblock}} and adds the relevant parameter to the sock template, rather than adding the historical parameter. Sockpuppets don't belong in Category:Blocked historical users. OrangeDog (talkedits) 20:32, 29 March 2009 (UTC)[reply]

I don't see why talk pages with less than 100 revisions should be automatically considered devoid of usefulness. --SmokeyJoe (talk) 21:59, 29 March 2009 (UTC)[reply]

In most cases it's just escalating warnings or block notices; nothing useful if the person's gone for good and shows every indication of such. -Jeremy (v^_^v Cardmaker) 06:05, 30 March 2009 (UTC)[reply]
They're not, if they have a sockpuppet tag or a spam warning they'll still be kept, because they have an actual, defined usefulness, rather than some hypothetical mainspace-related concern (why we're storing what's apparently critical details about article development on the talk pages of indef blocked users, I have no idea). As I said, over 90% of the pages have 10 or fewer revisions, suggesting a few warnings and a block notice. Even for the pages with more than 100 revisions, 4/9 are almost entirely useless. The pages are also kept for a month after the last edit before deletion. Mr.Z-man 16:30, 30 March 2009 (UTC)[reply]
Depending on the severity of behavior a new vandal / sock account is probably blocked within 5-20 talk page revisions. It would be interesting to see what the distributino really is. But we can't assume it is uniform over time or across different types of blocks / circumstances. Wikidemon (talk) 07:27, 30 March 2009 (UTC)[reply]
The full distribution:
revisions pages
>=100 7
>=90, <100 1
>=80, <90 1
>=70, <80 1
>=60, <70 1
>=50, <60 3
revisions pages
>=40, <50 11
>=30, <40 14
>=20, <30 38
>=10, <20 179
>0, <10 2,374
Over 90% have less than 10 revisions, and 97% have less than 20. Mr.Z-man 16:30, 30 March 2009 (UTC)[reply]

Please keep them

(I am splitting this section again, becomes quite big)

Can we please stop discussing whether these pages can be speedily deleted, it really does not serve any purpose, and though for most of us the damage done by deletion of user talkpages is minimal (most don't care, don't use and don't see the use of them), for some cases that damage is significant, and creates a lot of extra work (which then relies totally on (local) admins).

  1. As Abd pointed out above, some indef blocked users come back, and then the talkpages have to be undeleted.
  2. With editors who have besides a disruptive past also a productive past, the talkpage may contain in old revids discussions which have influenced policies, guidelines or page content. Deletion of that data hides the information from non-admins, and makes reconstruction of such discussions impossible
  3. The editors were blocked for a reason, deleting the pages also hides the reasons, which may still be of interest somewhere.
  4. In similarity with the earlier discussions about IP user talkpages, sometimes the editors are part of a, as yet unidentified, sockfarm. E.g. 213.59.221.0/24 contains 15 identified cross wiki spammers of cube2007.com (socks of Geri2), which ones were warned for that action here (admins, please log out before trying to find them)? Now do the same (cross-wiki) excercise on 89.216.66.0/24 .. Having a list of the accountnames in the latter quickly shows which are blue-links, and so can be checked if those page-histories contain warnings pertaining the issue we are checking.

On the other hand, editors who have not been indef blocked, but have left don't have their pages deleted? Even if they only have performed vandalism. So pages of editors who may have been useful in the past are deleted, and those of which users have long left and are nothing but useless edits are left there. While just those that are blocked are more relevant (in terms of why they were blocked) then those run-of-the-mill vandalism accounts.

It is easy to find which accounts did something, but if and when they were warned/blocked is a totally different issue. That is no matter of an edit count, a count of revisions of the talkpage, if the editors have been linked to somewhere (which count is for the IPs in the 213.59.221.0/24 range: 0; the case was handled on meta). They were tagged as socks (which did not happen with the IPs used by Geri2; again, the case was handled on meta). Etc. etc.

So, in conclusion, please, don't delete old user talkpages where the editor has been involved in some form of coordinated or larger scale vandalism, POV pushing or spamming. And as there is no real gain in deletion, and the pages may be useful to some people on wikipedia, and it is very difficult to decide or to put into rules which accounts can be deleted under a CSD, please do not delete them at all. These discussions are valuable to some of us, and deleting them a) hides them, and b) makes it completely rely on (local!) admins to do certain investigations. --Dirk Beetstra T C 11:50, 30 March 2009 (UTC)[reply]

I am going to add, I am all for a proper way of archiving them, or 'blanking and replacing with a standard template'. --Dirk Beetstra T C 11:53, 30 March 2009 (UTC)[reply]

I should note (again) that spam-related pages (anything with a spam warning template or in one of the subcategories of Category:User talk pages with spam warnings as of a couple weeks ago) is now kept. As are all the pages with a sock template (or any of these templates on the talk page or the userpage and any talk page with more than 100 edits (though based on the distribution above, this could probably be lowered). Also, indef-blocked IPs are re-categorized for further review. Mr.Z-man 16:50, 30 March 2009 (UTC)[reply]
The problem is, spam related talk pages are not perfectly recognisable by the tags on them .. XLinkBot puts a warning for people adding example.com, which is often more a vandalism edit then spam, while many cases (see the talkpages of the spammers in 89.216.66.0/24, all the edits of this range that the range were warned for are spam-edits, though there is (last time I checked) only one warning using a spam-template!). I am sorry, whatever criteria you apply, all these editors should simply be scrutinised by eye. --Dirk Beetstra T C 08:53, 31 March 2009 (UTC)[reply]
Okay, fine, people want to keep thousands of pages of garbage around every month? Whatever. I don't have time to keep repeating these arguments every time a couple people get a bee in their bonnet. The bot is now disabled. Pages won't be deleted and they won't be removed from the category automatically for any reason. If anyone wants these deleted, its fully manual review from now on. Have fun. Mr.Z-man 11:32, 31 March 2009 (UTC)[reply]

User pages of once good faith mainspace contributors. Consensus?

I suggest that the above reveals a consensus that there is not a consensus to speedily delete the talk pages of once good faith mainspace contributors who were subsequently indef blocked. I think there is even not a consensus to speedily delete even the userpages of the once good faith mainspace contributors who were subsequently indef blocked.

The lack of consensus for speedy deletion means that speedy deletions of such pages should not occur, even if previously such deletions were routine.

There should be no insinuation read that any past such deletions were in any way “wrong”. It was policy, albeit unwritten, at the time, but things change. I suggest that things need to change because these unwritten policies have scalability problems, as wikipedia, its number of editors, and the number of administrators grows.

Existing unwritten deletion policy needs to be recorded, so that can be understood, discussed, and tuned. Obviously, clear CSD criteria will make it easier for the not-to-be-denied, and quite valuable, deletion scripts/bots.

--SmokeyJoe (talk) 10:01, 1 April 2009 (UTC)[reply]

Deprecating GFDL 1.2-only as a valid image license on en.wiki

A discussion at Template talk:GFDL-1.2-en, which was advertised on the Village Pump and in the Signpost, has reached the consensus to deprecate GFDL 1.2-only as a valid image license on the English Wikipedia. (The German Wikipedia also did this back in November.) I wanted to advertise this here as well, to give everyone a chance to raise concerns before it is implemented. Our plan so far is to replace the existing {{GFDL-1.2-en}} and {{GFDL-1.2}} templates with the following:

If you have any thoughts or suggestions, please raise them here. Thanks! Kaldari (talk) 15:27, 31 March 2009 (UTC)[reply]

Just to clarify the relevance of this here - if the proposal goes through as above, then F3 will need rewording to incorporate images which have been tagged as GFDL-1.2-only for more than five days. —  Tivedshambo  (t/c) 17:18, 31 March 2009 (UTC)[reply]

Proposal for an expansion of A7

A7 currently covers articles on people who are blatantly non-notable. It seems this should be expanded to cover lists whose only entries are people who, if articles were created about them, would be subject to A7 deletion. An example of such an article is Burswood guitar users (see also AFD at Wikipedia:Articles for deletion/Burswood guitar users). This article seems to have been created by a non-notable person to list himself and a close relative who both have guitars manufactured by the same obscure manufacturer, hence it comes (as far as I see it) in the same vanity-article class as the other types of article listed in criterion A7. Any comments? JulesH (talk) 21:05, 31 March 2009 (UTC)[reply]

I'm leaning against this proposal. I think of lists as a safe haven for information that doesn't belong in any particular article. For instance, it might be useful to have a list of schools in a particular school district, even if none of the schools was itself notable. Or a list of songs by a notable musician, even if none of the songs was notable enough to have its own article. --Stepheng3 (talk) 21:09, 31 March 2009 (UTC)[reply]
Why should people be different? --Stepheng3 (talk) 21:11, 31 March 2009 (UTC)[reply]
Because the guideline for lists (WP:SAL) requires lists of people to always have articles. JulesH (talk) 08:12, 1 April 2009 (UTC)[reply]
Does this pass criterion 3 at the top of this page? Phil Bridger (talk) 21:50, 31 March 2009 (UTC)[reply]
I too would be against this. There's little harm to the 'pedia if we prod such lists instead of speedying them, and much benefit to having the extra time to really see if the list really has no encyclopedic potential. If the list is a blatantly obvious deletion, it can always be an IAR speedy.--Fabrictramp | talk to me 22:41, 31 March 2009 (UTC)[reply]
We have many perfectly reasonable lists for which most or all entries do not themselves deserve articles. For example, lists of paintings by a famous artist (how many paintings have articles?). Likewise, one could imagine a list of - for example - minor league sports players, where most of them don't deserve articles but the list is just fine. Dcoetzee 00:08, 1 April 2009 (UTC)[reply]
Consensus is that such lists are not fine; see WP:SAL. JulesH (talk) 08:12, 1 April 2009 (UTC)[reply]
I also would oppose this type of expansion of A7. Determining whether a list is populated with "people who, if articles were created about them, would be subject to A7 deletion" requires speculation, since we cannot know whether an article is A7-able until it is created. Let's remember that A7 does not judge the notability of a topic, but rather the presence or absence of an assertion of significance. –Black Falcon (Talk) 02:52, 1 April 2009 (UTC)[reply]
That's an interesting objection, and I'm not sure I see a solution for it. JulesH (talk) 08:12, 1 April 2009 (UTC)[reply]
this does not occur frequently enough to be worth the expansion, given the problems. It's hard enough to be sure one at a time. Anything really abusive can be dealt with by the provision for vandalism or test. DGG (talk) 16:12, 1 April 2009 (UTC)[reply]

New article category

I propose a new criteria for BLPs that have been in Category:Unreferenced_BLPs (current population 12916) for more than 3 months. As these articles fail both the spirit and the letter of the policy on biographies of living people, they should not be kept indefinitely. 3 months is ample time for authors to provide some sourcing. We currently do the exact same thing for images, albeit within a shorter time frame. I believe this criteria is:

  • Objective - any editor can determine whether an article has been unsourced for 3 months or not.
  • Uncontestable - the WP:BLP policy clearly does not intend completely unsourced BLPs to exist indefinitely.
  • Frequent - the category population has risen by 3000 in the 3 weeks I have been watching it.
  • Non-redundant - no other applicable criteria exist.

I think that tagging and deletion would initially need to be phased either by initial title letter, or oldest first so that after a few months we are down to tagging new unsourced articles, and giving that author 3 months to fix the sourcing. Kevin (talk) 01:47, 1 April 2009 (UTC)[reply]

So would that be like "A10. An article on a living person with no reliable citations at all that has been tagged as such for at least a month"? ViperSnake151 02:09, 1 April 2009 (UTC)[reply]
Pretty much. A recent discussion at WP:AN suggested 3 months as the time frame. Personally, I'm in favor of a week, but I also think it is reasonable to allow more time for fixing. Kevin (talk) 02:17, 1 April 2009 (UTC)[reply]
I should note here that Category:Unreferenced BLPs is missing about 30,000 biographies by my estimate. (So a proposed new criterion certainly meets the frequency requirement.) The overall proposal looks good to me. --MZMcBride (talk) 02:50, 1 April 2009 (UTC)[reply]
I agree and think this proposal is a solid one. The status quo just isn't working and we need firmer measures to control the amount of crap building up in biographies. Removing unsourced ones is a good step. - Rjd0060 (talk) 02:54, 1 April 2009 (UTC)[reply]
  • I like this idea. There's a potential conflict with area-specific guidelines for "presumed notability" (WP:ATHLETE comes to mind as the type of thing where arguments would arise), but this is an obstacle that can certainly be overcome. BLP is important; this suggestion should advance. Townlake (talk) 03:01, 1 April 2009 (UTC)[reply]
We should not make any judgement about notability in applying this criteria. A source that meets WP:RS would be the only criteria. Kevin (talk) 03:04, 1 April 2009 (UTC)[reply]
I agree, I'm just trying to think through the practical rollout of this. In cases like this one, the argument will come up that since this gentleman was a player in the National Basketball Association, he's presumptively notable and therefore ought to have an entry even if no RSs are immediately added to the article... because that's the way WP:ATHLETE has worked for X amount of time. All I'm saying it this issue will come up and should be addressed proactively. Townlake (talk) 03:17, 1 April 2009 (UTC)[reply]
I think it is important to emphasise here that notability is a non-issue; we don't keep copyvios of articles on potentially notable people, for instance. So, just because that chap is notable, doesn't mean we keep an unreferenced BLP article around about him. Lankiveil (speak to me) 07:59, 1 April 2009 (UTC).[reply]
This is an excellent suggestion. I should point out that the problem with "presumed notability" for certain kinds of BLP shouldn't be one: if no reliable sources whatsoever can be found on a person, then there should not be an article. If sources are found, then the article is not deleted by that criterion. — Coren (talk) 03:17, 1 April 2009 (UTC)[reply]

(edit conflict)A couple of points launching from Vipersnakes151's proposed language above: Firstly, remember that G10 (attack pages) already exists, so we don't need to cover anything that would already be covered by it. Secondly, people will argue about what constitutes an article on a living person, so a BLP speedy criterion should restrict itself specifically to nomenclative articles like Jimmy Wales or Joseph Schmoe. If someone tries to game this by moving an article to, e.g., Odious sexual perversities of Joseph Schmoe, G10 and AfD will still exist to deal with it. Secondly, speedy deletion should not be used for articles with even one reliable source, and especially shouldn't ever be used to checkmate an edit war over the reliability of sources, so a BLP criterion needs to be fairly liberal about what sourcing is acceptable - remembering that AfD exists for anything remotely controversial. Thirdly, A BLP criterion should not be used as an IAR substitute for A7 (no indication of importance) or G11 (spam) either, so a time delay of some sort (X days without sourcing, where X is large) is vital. Having said all of that, I support the basic kernel of this proposal - the fact is that we do have too many BLPs that are unsourced or practically so, and there is more than one good reason to get rid of them. Gavia immer (talk) 03:29, 1 April 2009 (UTC)[reply]

  • I also support this idea. While this won't completely solve our BLP problem, it will let us prune away some of the more marginal articles so that we can better concentrate our efforts on others. I also agree with interpreting "sources" in the loosest possible context, and having a lengthy (3 months or 90 days) time limit to give editors some time to add sourcing to articles that can potentially be sourced. Lankiveil (speak to me) 08:01, 1 April 2009 (UTC).[reply]
I've suggested this before, but, I never thought it would be acceptable. I still think you might have problems getting it through. So, I'd suggest the following sweeteners, which might help more inclusionist minded people to accept it:
  1. Any deletion under this criteria is also summarily reversible by any administrator if the administrator or another editor is immediately willing to reference the article to a WP:BLP compliant state.--Scott Mac (Doc) 08:14, 1 April 2009 (UTC)[reply]
  2. Before there are any deletions, some bot should crawl through all the BLPs which are marked as totally unreferenced and lack any external links, and then place a warning on the creator's page to say "an BLP you created may be unreferenced, and could be deleted, please ensure the the article has basic references"
  3. We bring this in VERY gently. Actually, I'd advise initially against summary deletion - better that if an article is marked as unreferenced for three months, it is then tagged with Template:Unsourced deletion - which gives as further week for sourcing before deletion. Editors can remove the tag only if they source the article. (not so sure about this one)
  4. I'd echo, indeed I suggested already, that this be trialled with articles beginning A-C.
--Scott Mac (Doc) 08:14, 1 April 2009 (UTC)[reply]
  • I really like your third idea, but I would call it {{prodBLP}} and change it somewhat. ;-) It would be exactly the same as {{prod}}, except that in order to contest the prod notice or deltion via prod, it must provide references for all statements, or be stubified in such a way that all statements are sourced. -Atmoz (talk) 18:27, 2 April 2009 (UTC)[reply]
  • I support this as well, with the remark that there should be a grace period (say three months as well) between the acceptance of this rule (and the widespread communication of it), and the application of it, since we have a serious backlog of unsourced BLPs (going back to August 2006), which would mean that without grace period, we could immediately delete everything tagged before 2009, which is some 5,000 articles (most of them on soccer players). I also believe that once it is clear that the consensus here is in favour of the A10 category, this should be posted at the WP:VPP for more widespread discussion before implementation. Fram (talk) 08:17, 1 April 2009 (UTC)[reply]
  • Reasonable plan, although I share Doc G's caveats. tfeSil (aktl) 08:40, 1 April 2009 (UTC)[reply]
  • This is the only way we can fix the unreferenced BLPs without flooding AfD. I think the current backlog should be fed through a bot that limits the number of taggings and as Doc suggested it could also notify the author. At a rate of 200/day it would take just over 2 months depending o to eliminate the backlog. BJTalk 09:27, 1 April 2009 (UTC)[reply]
  • I don't think this is a good idea. We already have mechanisms in place to deal with them. People see to forget that an article, that exists for 3 months, can easily be deleted via WP:PROD which allows possible rescue. There is no need for a new criterion because there is no problem it can fix, that cannot be fixed by the current deletion policy. Those articles can be separated (broadly speaking) in 3 categories:
    • Negative unsourced BLP => we got G10 for that
    • Neutral unsourced BLP without indication for notability => we got A7
    • Neutral unsourced BLP with indication of notability => PROD
    The proposal here does not explain why the current way cannot be applied to these articles as well, nor why it needs to be a speedy criterion. I'm suggesting we just PROD those articles instead, the effectiveness is the same, but it allows both rescuing and community input without having to go through AFD. Regards Why oh Why? 09:37, 1 April 2009 (UTC)[reply]
The problem with PROD is that the tag can be removed for any reason, and then cannot be replaced. I can imagine that many of the articles would then end up not being deleted and remaining unsourced, or having to be taken to AfD. Kevin (talk) 10:20, 1 April 2009 (UTC)[reply]
I don't see that as a problem, quite the opposite in fact. If someone removes the tag, then they are signaling that they are disagreeing with deletion and that wider community input is needed. But from all experiences, PRODs are left in place in the most of cases and if the creator has not worked on the article for 3 months, it's unlikely they will contest it. I'd say that would leave approximately 2-5% of those articles for AFD, which AFD can handle just fine. If there is need for discussion (which contesting a prod would indicate), then discussion should take place. But the harm of having that discussion is not greater than the harm of losing those potentially valuable articles. And I see no gain in speedy-deleting after 3 months which forces us to create such a criterion because if they really contain negative unsourced BLP, it's already covered anyway and that's the only kind of BLP that needs to be deleted quickly and without discussion. Regards SoWhy 10:39, 1 April 2009 (UTC)[reply]
Prod is no use, since people say "it's seems notable" and unprod, without sourcing. Afd is pointless, since the point is not whether the subject merits an article, but whether the current unsourced article should kept. It isn't that we want deletions here, it is that we want to say "unsourced BLPs are unacceptable - if it isn't sourced within three months, it is removed until someone is willing to source it".--Scott Mac (Doc) 11:27, 1 April 2009 (UTC)[reply]
Prod has no teeth and therefore lacks effectiveness. If the creator of an article removes the prod without actually addressing the issues we still need to resort to an AFD where the potential of an article is usually brought into the mix rather than its current state, which often makes articles linger for months or even years. I'd prefer a speedy deletion criterion that keeps out any unsourced material at all. - Mgm|(talk) 08:30, 2 April 2009 (UTC)[reply]
  • I support the proposal. PROD is not effective since anybody can remove a PROD without giving any reason, or making any fix. Regarding A7, it seems absurd that we permit unsourced articles simply because they make an unsubstantiated claim of notability. This proposal encourages BLP creators to go back and source the articles they already made, before they make more unsourced BLPs. It takes far less time for the person making an article to source it, than it does for somebody unfamiliar to come in, and find sources, with little to go on. --Rob (talk) 10:31, 1 April 2009 (UTC)[reply]
    • Then your point is to change A7 to "delete articles without unsourced claims"? Because else you are supporting creating a new criterion to circumvent an existing one. SoWhy 10:39, 1 April 2009 (UTC)[reply]
  • Support per Doc. Hiding T 11:12, 1 April 2009 (UTC)[reply]
  • Oppose per SoWhy. We have PROD already, which works well, and should just be used in these cases - along with more people classifying and unprodding a new flood of BLP prods. Just because people could remove the prods from tons of BLPs, and not do anything to improve the articles, which then escape AfD does not mean this actually happens or would happen in a significant fraction of cases. Unprodders very frequently do some work on the articles and unsourced articles which survive AfDs are generally improved and sourced during the process. John Z (talk) 11:44, 1 April 2009 (UTC)[reply]
    • So, if I prod 5,000 articles this afternoon, that's OK? Indeed this proposal is much less than prod, since it proposes that users get 3 months to reference an article - if prod was used it would be 5 days.--Scott Mac (Doc) 11:49, 1 April 2009 (UTC)[reply]
      • Why wouldn't it? PROD has no taggings-per-day limit, has it? This proposal is more than prod because while there is a 3 month deadline, users are not notified about the deletion and other users will not see from an article if and when it will be deleted. With PROD, the creator is notified and everyone viewing the article knows they have 5 days to save it. Regards SoWhy 11:54, 1 April 2009 (UTC)[reply]
        • We could have a bot tag all BLPs marked as unreferenced for 2 months as liable to deletion, and the same bot could warn the creator - so that would do the same thing, and give far far more warning to everyone than prod.--Scott Mac (Doc) 12:04, 1 April 2009 (UTC)[reply]
        • The creator does not have to be notified when an article is prodded. It's a common courtesy, but it isn't a necessity, and point of fact, it's a common courtesy that the creator is notified when an article is tagged as a speedy, so I don't really understand your grounds of concern. I think if someone were to prod all of these articles in one go, the accusations of WP:POINT would be tremendous. Hiding T 12:14, 1 April 2009 (UTC)[reply]
        • And let us not forget that article creators are specifically told that "An article without references may quickly be deleted." when they create their article, so let's not act like there is no warning. Hiding T 12:16, 1 April 2009 (UTC)[reply]
          • Because with speedy deletions, by the time the creator reads the message, it might already be deleted. With PROD, this is unlikely. If one wants to create a PROD-like system for BLPs, i.e. tagging them for deletion for 2 months, that's fine with me, but then the discussion is wrong here. It's no speedy deletion if the creator has a fixed amount of time after tagging, it's a proposed deletion then. One of the essential points of speedy deletions is that the creator may not have the time to realize that the article is tagged before it's deleted and that admins can and will delete articles on sight that fit the criteria. Suggest a prod-like system where articles get tagged for deletion for say 3 months with a nice "this article will be deleted after 1 July 2009" on them and I'm all for it. But I'm against a speedy deletion criterion because it does not fit within the policy. Regards SoWhy 12:20, 1 April 2009 (UTC)[reply]
            • We already have a number of di- criteria where things get deleted only after some delay. This would be another, with a clearly defined criterion. --Amalthea :  Chat  12:25, 1 April 2009 (UTC)[reply]
              • Exactly. I'm not sure I understand the objections, or at least I'm thinking they've all been considered and met. Hiding T 12:36, 1 April 2009 (UTC)[reply]
              • But the other's fit well with the policy. Creating a criteria that effectively discards A7 and G11 is problematic. Instead I'd suggest a new PROD-like policy on this to clearly seperate it from the speedy deletions which have completely different objectives. SD is for cleaning up the mess, not for deleting on grounds of missing sources or suchlike, hence A7's wording. How about Wikipedia:BLP deletion instead (could be called BIODEL^^)? SoWhy 12:30, 1 April 2009 (UTC)[reply]
                • It doesn't discard anything and it fits in with what we already do here. SD is not for cleaning up the mess, it is for deleting items which do not need discussion. Unless you are suggested it needs to be discussed as to whether a BLP has references, I can't understand your objections or proposals. I doubt this criteria will throw up many more contentious deletions than current methods. Hiding T 12:39, 1 April 2009 (UTC)[reply]
                • (ec)I'd think it complements A7 & G11. They still "clean up the mess", and do so quickly. The less messy, but still highly problematic unsourced BLPs will get past them. The main difference between PROD and CSD I see is that PROD accepts any rationale that would be grounds for deletion at AfD, as long as the proponent thinks it's uncontroversial. CSD has narrowly defined criteria where, unless an article is changed, it will non-controversially deleted. With the case at hand, we have a very narrow criterion an article has to match. This fits in with CSD more than with PROD, in particular since we already have some delayed criteria.
                  Also, I imagine that this criterion will get a much reduced grace period (like 7 days) once the backlog is cleared in several months, so that it would fit even better with the other "di-" criteria we already have. I'm not sure if that's the plan though. --Amalthea :  Chat  12:43, 1 April 2009 (UTC)[reply]
                  • Funny how the two of you disagree whether SD is to clean up the mess or not. But the point is, all our current article criteria are for pages that cannot be salvaged into something worth keeping (or where it's illogical to assume it in cases of A7 and A9 which are very strict on the possibility of notability or where it's not needed in case of A2). But no criterion currently covers any pages that can be salvaged into pages worth keeping. I think adding such a new criterion does not fit with the others which explicitly targets only non-salvageable pages. On the other hand, PROD specifically is for pages which can be salvaged maybe but where noone is doing it, so the proposed criterion fits there much better than it would here. Hence my suggestion to create a separate process for this to avoid mixing elements that are not fitting together very well. Regards SoWhy 13:05, 1 April 2009 (UTC)[reply]
                    • G5 and G11 cover articles that could be salvaged. Hiding T 13:10, 1 April 2009 (UTC)[reply]
                      • I was talking about article criteria. And G11 does not cover those articles actually, because strictly speaking you can only G11 a page that is nothing but advertising, else you can easily remove the spam and leave a valid stub. Regards SoWhy 13:27, 1 April 2009 (UTC)[reply]
                        • G5 and G11 cover articles, so they are article criteria. And G11, by its own definition applies as I said, containing as it does the caveat "would need to be fundamentally rewritten". But I think we've been around this one enough. I think all your objections are met, you don't. There's not that much more to say. Hiding T 13:35, 1 April 2009 (UTC)[reply]
  • I'd like it if the page were visually tagged for deletion during the time anyway, so I think somethink like {{di-unsourced-blp}} "delete if it's been tagged for 3 months and is an unsourced BLP" would be best. This would categorize them neatly, tag them appropriately, and give all interested parties enough time to turn it into a WP:BLP compliant article or stub. The tagger should notify the author as with other db- and di- criteria. The tag would probably only be appropriate on "pure" biographies: if an article only contains some biographic material it should be dealt with differently.
    PROD and a time-delayed CSD aren't that different, as we've discussed here before. One of the main differences is that a CSD tag is not be removed if it clearly applies. "Sufficient references" would still of course be a judgement call, but it can't be removed from a BLP article with no sources at all.
    I very much agree with Scott that this needs to be brought live gently, to the point that only a certain number of unsourced BLPs from that category should be tagged each day (semi-automatically by some dedicated person or bot). --Amalthea :  Chat  12:22, 1 April 2009 (UTC)[reply]
  • I think (at least) initially, this should be applied only to brand new BLPs, so within a few days of creation it should be tagged as {{di-unsourced-blp}}, with a clear warning given on the article, and on the user's talk page. --Rob (talk) 12:52, 1 April 2009 (UTC)[reply]
      • The problem is with swamping those who would wish to fix rather than delete.--Scott Mac (Doc) 12:59, 1 April 2009 (UTC)[reply]
        • I don't fully follow. What would stop us automating a bot to also tag ten (for arguments sake) articles from the backlog per day? Would that swamp us? Or, to grant a six month exemption to the current backlog? Six months would be more than plenty time. Hiding T 13:06, 1 April 2009 (UTC)[reply]
          • Oh, I'd delete the lot tomorrow. However, you'll not get consensus for it when so many are involved. The first step is to stem the flow, so that the backlog does not increase. Then stage two is to try to work on the backlog. One step at a time, and you take more people with you.--Scott Mac (Doc) 13:43, 1 April 2009 (UTC)[reply]
    • Agreed, grandfathering this in, might be best. A policy that says if an unreferenced BLP is created, after a few hours it can be tagged as such - the tag will invite sourcing and warn that it will be deleted in in x days unless sourced, and the creator will also be invited to source it. The tags will add it to a category, so people can patrol that. Even after deletion, the article can be recreated or summarily undeleted, if someone offers to source it. (We can then, very very gently, deal with the backlog. Perhaps allowing many many months before any of the backlog is deleted - indeed ideally nothing here would be deleted for lack of sourcing.).--Scott Mac (Doc) 12:59, 1 April 2009 (UTC)[reply]
  • I agree with Scott Mac (Doc); having a kind of "it will be deleted in X days unless it is fixed" type of thing would probably be best. Regardless of how it is handled or what the time frame is, the pages should definitely be restored upon request to allow for sourcing. –Drilnoth (TC) 13:32, 1 April 2009 (UTC)[reply]
  • I support this proposed criterion's creation. I was going to stress the importance of including a stipulation that such speedy deletions be reversed upon the request of a user who wishes to add reliable sources, but Scott MacDonald beat me to it. This, of course, should have a time limit attached (e.g. the article will be re-deleted if the sources aren't added within three days). —David Levy 13:55, 1 April 2009 (UTC)[reply]

Concrete proposal

A10:Any biography of a living person, created after 1st April 2009, which has no credible sources whatsoever, and has been tagged with {unreferenced BLP deletion} for at least 5 days. Administrators should check that the creator has been given adequate notice. (Note that any article deleted under this criterion may be summarily undeleted by any administrator if any editor indicates a willingness to source the article).
Template {unreferenced BLP deletion} should read: "This article on a living person lacks any sourcing. Please edit this article to provide sources. If this article is not sourced by [day-month-year] it may be subject to deletion. Do not remove this template unless sources have been provided.".

OK, how about it?

  • The deletion time is the same as prod, and the article is undeleted on request (the same as prod).
  • It is grandfathered in (we can think about the 30,000 backlogged unreferenced later - but let's stem the tide)
  • Creators and other are given well adequate time to provide sourcing
  • We are only asking for the most basic sourcing here.
  • The idea is not to delete things, but to create a new atmosphere where sourcing is required.
  • If any good article does get deleted, any admin can undelete without any process or discussion. He just needs to say "sourcing this"

--Scott Mac (Doc) 14:44, 1 April 2009 (UTC)[reply]

  • Support. It might be worthwhile to have previously-tagged pages also deleted over time, as long as they are restored temporarily on request as you describe here to allow for sourcing but, as you said, this can be discussed after we see how the process works with new pages. –Drilnoth (TC) 14:50, 1 April 2009 (UTC)Neutral: I could actually go either way, seeing Colonel Warden's comment below. Deleting good faith material just because it is unreferenced at the time isn't a good idea; prodding it would make more sense if deletion is warranted. –Drilnoth (TC) 14:54, 1 April 2009 (UTC)[reply]
So source it.--Scott Mac (Doc) 14:56, 1 April 2009 (UTC) Indeed, I just did. Anyway, that article would not have been deleted - it would not be covered by this.--Scott Mac (Doc) 14:59, 1 April 2009 (UTC)[reply]
Did some more sourcing on John MacGregor, Baron MacGregor of Pulham Market, which kind of indicates to me why this proposal is a good thing. Hiding T 15:37, 1 April 2009 (UTC)[reply]
Nobody denies sourcing is a good thing. Butthis was better sourced than deleted,wasn't it? DGG (talk) 16:27, 1 April 2009 (UTC)[reply]
Yup, and it was this proposal that motivated someone to do it. If you've got a more effective way of ensuring we don't keep increasing the number of unsourced biographies, then I'm all ears. But saying that an individual case can be fixed, misses the structural problem.--Scott Mac (Doc) 16:35, 1 April 2009 (UTC)[reply]
  • The way I read it, SoWhy is in agreement that we don't have processes to cover this. The user wants a different solution, using something more like prod. I don't see why we should reject this idea because it has the wrong name. Hiding T 15:39, 1 April 2009 (UTC)[reply]
  • Weak support. This seems mostly redundant with the idea of just systematically PRODding unreferenced BLPs; but such systematic PRODding seems harder to actually get done; a new CSD criterion will be used. So a new CSD criterion, whilst redundant in principle, is thus not redundant in practice. It may not be pretty, but it's (probably) better than doing nothing. Rd232 talk 15:37, 1 April 2009 (UTC)[reply]
  • Support would be a stronger support without the grandfathering, waiting period, and undelete on request. BLPs should be sourced or shot. But this is a step in the right direction. -Atmoz (talk) 15:43, 1 April 2009 (UTC)[reply]
  • Comment - not sure. Like it in principle, but I'm unhappy about the grandfathering, if only because it creates two classes of BLP. Will ponder further Fritzpoll (talk) 15:49, 1 April 2009 (UTC)[reply]
  • Support, though I'm not clear on the difference between this and PROD, given the five-day wait period. I'd much prefer it without that. Agree with Atmoz that BLPs should be reliably sourced or shot. SlimVirgin talk|contribs 15:51, 1 April 2009 (UTC)[reply]
The key difference is the tag can't be removed just because someone wants the article kept - to avoid deletion you have to source the article. Thus we establish the principle that unsourced BLPs must be sourced or deleted - without mass deleting the existing backlog (which, unfortunately, will not get consensus). --Scott Mac (Doc) 16:02, 1 April 2009 (UTC)[reply]
The biggest problem is how much sourcing is enough? Its a completely POV criteria. -Djsasso (talk) 16:10, 1 April 2009 (UTC)[reply]
Any legitimate sourcing is better than nothing at all. The proposal doesn't require a particular level of sourcing, just "more than none." Mr.Z-man 16:55, 1 April 2009 (UTC)[reply]
  • Strong oppose. Most such bios are trivial to source the basic facts. At the very least they should go to prod or AfD where the community can see them and have a chance at them. Many editors come here once and never again, but do manage to add a good article. If we do this we shall be deleting a great deal of sourceable work. Perhaps we should add the criterion. "If the administrator has himself made a thorough effort to source them using appropriate resources for the type of article,and demonstrates that on the article talk page." I do not think that many admins would actually be willing to do that. The provision credible source will be interpreted much too broadly,as there is not really agreement on such things enough for a speedy procedure. A good proposal, if what you want to do is throw out the baby with the bathwater. Colonel Warden has it right. DGG (talk) 16:09, 1 April 2009 (UTC)[reply]
    • That argument is falsified by experience. We have a growing number of utterly unsourced BLPs - and simply saying to those concerned about this "go source them yourselves" is simply not working. It has never worked. Here the onus is reversed. If people want us to retain an ever-growing number of BLPs, then they need to start maintaining them in an acceptable manner.--Scott Mac (Doc) 16:14, 1 April 2009 (UTC)[reply]
I checked some of the older ones, and found some people who might not be notable, but no actually unsourced problematic article. The one possibly dubious one had sources, but the ed. forgot to add a "references" tag, so they were not displayed. We are dealing with an almost nonexistent problem. DGG (talk) 16:33, 1 April 2009 (UTC) I also checked three dozen from the last two months. I found a bumber who may not be notable, but no actual BLP problems otherwise. DGG (talk) 16:48, 1 April 2009 (UTC)[reply]
  • As long as care is taken to notify the creator, they can always ask for the material to be undeleted if necessary. We can't avoid choosing between Type I and Type II errors (deleting too much, keeping too much), but deletion is always temporary anyway, except in AFD cases where the subject itself is rejected for inclusion (even then there's Deletion Review). In BLP cases we should draw a different balance between deleting poor material (unreferenced is poor) and keeping it public for potential improvement, hence this criterion directed at unreferenced BLPs. Rd232 talk 16:20, 1 April 2009 (UTC)[reply]
deletion is not temporary for new editors who do not know our baroque procedure. Keeping is much morereversible than deletion, and thatsolves the problemof choosing between I and II. DGG (talk) 16:33, 1 April 2009 (UTC)[reply]
All it takes an appropriate user warning template for this criterion. There's no need for the procedure it should describe to be baroque at all - eg contacting the CSD nominator or deleting admin or if that fails posting at DRV. Really needn't be a big deal. Rd232 talk 16:39, 1 April 2009 (UTC)[reply]
If I told something like that to someone complaining about their bio on OTRS, I would expect to have my access revoked. Mr.Z-man 16:58, 1 April 2009 (UTC)[reply]
  • Strong support - if sources exist, they can be added to the article. The point is that this proposal suggests a long enough timescale for sources to be found and added. Were this a standard speedy criterion of "tag it, wait for an admin, deleted" like most others, I would have reservations. I think there is also enough time for the standard of credibility to be assessed and debated if there is any doubt. This solves a long-standing problem Fritzpoll (talk) 16:20, 1 April 2009 (UTC)[reply]
I agree with you. Let the admin do so before deleting. DGG (talk) 16:34, 1 April 2009 (UTC)[reply]
I agree with you. Let the admin do so before deleting. We're supposed to at least passable content creators, right? DGG (talk) 16:34, 1 April 2009 (UTC)[reply]
Ridiculous. Admins are supposed to be, well, admins, not Last Line Of Defence Against Ever Deleting Anything. Rd232 talk 16:40, 1 April 2009 (UTC)[reply]
No, we are indeed the last line of defence against deletion. That's exactly what the mop is for. Deleting, after checking. Deleting problem articles is almost all I do with the admin buttons--just like you--check my log DGG (talk) 16:49, 1 April 2009 (UTC)[reply]
Let those who want to keep it, source it. Telling people who are concerned about BLP implications that the only way they get to avoid unreferenced BLPs is to go about sourcing them all, is quite unacceptable. That policy has totally failed to stem the rise in unreferenced BLPs. You are arguing for an idea that has demonstrably been falsified by 8 years of experience. Enough is enough.--Scott Mac (Doc) 16:55, 1 April 2009 (UTC)[reply]
  • Oppose. While I'm a "must be sourced fiend", I'm not comfortable with this solution. Ultimately, I think it punishes the reader by removing information just because a couple of editors (the person who wrote the article, the person who tagged it, and the person who deleted it) were too lazy to source it. If this goes through, I doubt I'll be deleting any of those speedies.--Fabrictramp | talk to me 16:52, 1 April 2009 (UTC)[reply]
  • Support - We can't just say "Well, it doesn't look like an attack, so its probably fine." I've seen several cases where articles that looked fine contained false statements for very long periods of time until someone familiar with the subject noticed, or the subject complained. The current "notability-centric" system is entirely inadequate for this problem, and the amount of unsourced BLPs and other articles is increasing at an alarming rate. Mr.Z-man 16:55, 1 April 2009 (UTC)[reply]
  • Oppose per DGG. Jheald (talk) 16:58, 1 April 2009 (UTC)[reply]
  • Oppose. Unsourced BLPs are not actually a problem if it is all uncontroversial. An article that is 99% sourced and 1% libel is much worse. We do not get perfect articles by forbidding anything less than perfect. --Apoc2400 (talk) 17:00, 1 April 2009 (UTC)[reply]
    • "Uncontroversial" is a matter of opinion. What might be uncontroversial to the recent changes patroller looking over each diff for 5 seconds before moving on might be blatantly untrue and harm-causing to the subject. This proposal wouldn't preclude deletion of BLPs that do have sources or make it harder to delete libel, I don't quite understand your objection. Mr.Z-man 17:19, 1 April 2009 (UTC)[reply]
      • "Uncontentious" would be a better word. What I mean is that an unsourced BLP is not much more likely to hurt anyone than an article that has at least one source. --Apoc2400 (talk) 19:07, 1 April 2009 (UTC)[reply]
  • Support This isn't a solution to the BLP problem, but it is a good and necessary idea. [[Sam Korn]] (smoddy) 17:01, 1 April 2009 (UTC)[reply]
  • Support - as a representative of the inclusionist troll guild. ;) We'll probably need to quibble over the word "credible", but otherwise a template - wait - del format is perfectly reasonable, and if the template adds to a category of "blps that'll be deleted if not sourced", they can be easily fixed by those so inclined. WilyD 17:03, 1 April 2009 (UTC)[reply]
  • Completely unsourced biographies of living people have no place on Wikipedia. If an article (a biography of a living person) goes three months without any sources, it should be deleted. If a legit article gets deleted, why is that the end of the world? Couldn't it just be recreated when someone could be arsed to find a fucking source? People! Our biographies of living people are probably our most "dangerous" articles. We must do something. Speedy deleting these articles does not mean there can never be an article on the subject. When sources are provided, it can have a shot. Until then, what positive benefit is there for having potenially troublesome biographies of living people in the encyclopedia. Delete hard with no prejudice towards recreation with sources in the future. Good first step. Mahalo. --Ali'i 17:06, 1 April 2009 (UTC)[reply]
  • Support It helps convey the message that the project is serious about quality and verifiability. Given enough notice and a cat for concerned editors to find articles to rescue, I see no problem. It will only improve overall quality. -- Mufka (u) (t) (c) 17:08, 1 April 2009 (UTC)[reply]
  • Although Hiding seems to think so, I'm not in support in general and certainly I oppose this suggestion of a new A10 to cover it. My proposal was a completely seperate process to CSD with much longer waiting periods before deletion. I might make a full proposal later today when I come home. My reasons for opposing this proposal are a.) does not fit CSD, b.) 5 days is too short and c.) this proposal aims for deletion of those articles rather than fixing them, which conflicts with WP:PRESERVE and WP:REMOVE. Our editing policy is towards keeping information and removing only what cannot be sourced. But there is no BLP I can think of that could not be cut down to a stub and not still be a valid article. If there are unsourced statements, they can be removed individually but never should a possibly verifiable article be deleted because of that. Because an article like "X is an American painter" can be a perfectly fine stub without having to be deleted for not having sources that specify that X exists.
    Yes, I understand that some articles might need to be deleted but I do not agree that it has to be done at a scale which needs a new criterion to cover it. There are good reasons we have WP:PROD and the proposed criteria is actually more strict than PROD; PROD can only be used when an article fails policy and guidelines, not only if it's unclear. Doc's suggestion would allow deletion for the simple possibility of not meeting those guidelines without any proof that they are in fact not verifiable. There is no reason to create a criteria that effectively is like PROD but without PROD's benefits and reasoning. On a side note, I don't think such a change that would replace PROD in large parts of target articles can be done with simple discussion here, it needs a much larger community input. Regards SoWhy 17:09, 1 April 2009 (UTC)[reply]
  • Support. Good one - David Gerard (talk) 17:18, 1 April 2009 (UTC)[reply]
  • Support Only one verifiable source is needed to prevent this from being applied. Is that too much to ask going forward? -- Avi (talk) 17:30, 1 April 2009 (UTC)[reply]
  • Strong support - totally! - Alison 17:32, 1 April 2009 (UTC)[reply]
  • Comment:I've already mentioned above that I support the basic idea, but this iteration still needs to define what "a biography of a living person" is for the sake (and avoidance) of the WikiLawyers. It shouldn't link to Wikipedia:Biographies of living persons, either, despite that being the obvious fix, because that makes for an external dependency that editors would in have to read (in theory; in practice they'd just go with thier memory or their perception of what's acceptable). I suggested above that this ought to apply only to nomenclative articles (that is, naming a particular person); I still think that's a better standard, even if in excludes a few things. Gavia immer (talk) 17:43, 1 April 2009 (UTC)[reply]
  • Oppose per SoWhy. –Juliancolton | Talk 17:44, 1 April 2009 (UTC)[reply]
  • Weak support I'd rather support an alternative that allows for a broader criteria for deleting BLP articles. This criteria prevent previous (prior April 2009) entries without sources from being speedy deleted if they do not contain sources. Since they have been on site the longest then they should go first. As well, I think that having a stub of a single fact that the person existed is not necessary for a comprehensive encyclopedia since the content can be presented elsewhere. Allowing a vast number of these BLP articles has the potential for harm since we do not have adequate number of volunteers to monitor the articles. My strong preference would be for all BLP entries without sourcing for the majority of the content to be deleted with the possibility to be recreated once adequate sourcing is found. FloNight♥♥♥ 17:46, 1 April 2009 (UTC)[reply]
  • Support with caveats. I would prefer an addition: "created after 1st April 2009, or more than 90 days old,". It would be better to have a grace period than a full exemption for "grandfathered" articles. Additionally, this is probably better placed at WP:PROD than at WP:CSD. It is, in essence, a PROD with a stricter limitation for removing the template. (CSD is generally shoot on sight. PROD has the waiting period.) The first is important to me, but the latter is more a quibble. --Vassyana (talk) 17:58, 1 April 2009 (UTC)[reply]
I agree it isn't enough. But something that "isn't enough" for BLP concerned people, while is perhaps acceptable to some BLP inclusionists might gain consensus. My aim would be to generate an atmosphere of less tolerance for unsourced BLPs - hopefully that would encourage sourcing of articles rather than deletion, but it will certainly begin to focus minds.--Scott Mac (Doc) 18:01, 1 April 2009 (UTC)[reply]
I was planning to propose wording that got rid of existing articles that did not have any sources for most of the content and were tagged for a week. No special warning to the creator is needed to delete since this is well past the time period necessary for them to return to the article and add sources. This would let us clear out the vast number of old articles without out sources for the majority of the content, and stop the addition of new articles without content. The reality is that we do not have the manpower to identify and monitor all BLP articles now. I don't see that changing any time soon. I want to reduce the number of articles we need to watch by only keeping the ones that are referenced articles, not including unreferenced stubs (which add no value to the reader beyond what a redirect would do) or poorly referenced start length articles (which have the large potential to be inaccurate, and some potential to actually cause harm to the person). FloNight♥♥♥ 18:17, 1 April 2009 (UTC)[reply]
  • Agree it could be better framed as a PROD, with removal of tag only if a source is provided. Also agree that complete grandfathering doesn't really make sense. Better to give a longer grace period after creation, but apply it to all BLPs, new and existing. I'd also challenge the inclusionists to come up with an upper limit on how long completely unsourced BLPs should be allowed - bearing in mind that unsourced BLPs existing for a long time are prima facie of low notability, and the unsourced WP article is probably relatively prominent on the internet. Rd232 talk 18:12, 1 April 2009 (UTC)[reply]
  • Prod/speedy who cares what we call it, let's discuss the substance. I'm not at all proposed to dealing with the old BLPs - however I was looking for a starting point that might get consensus. Anything that involves tagging 30,000 articles and deleting a percentage of them will get a string of opposes. If you want to do that, can I ask you to propose a seperate supplemental/complementary idea later, so that you neither cause people to oppose this, nor split the support vote. (I personally will support any such proposal).--Scott Mac (Doc) 18:24, 1 April 2009 (UTC)[reply]
  • Support. +sj + 18:16, 1 April 2009 (UTC)[reply]
    A general caveat, since I don't like the fact that deletion always deletes the catalog record that someone once tried to create an article : I'd really like to see a catalog, open to human organization unlike the deletion log, of pages of all sorts that have been deleted, with relevant categories. Certainly any page that could be described as "may be a good article some day, but isn't yet and we need to clean up"... the original materials is often quite good and useful for anyone coming along to add to it later -- and totally invisible to those future editors. My suggestion below about a delay for applying G8 to newly deleted (and newly created) articles cuts at the same problem. +sj +
  • Oppose. BLPs are not special. -- LondonStatto (talk) 18:18, 1 April 2009 (UTC)[reply]

Random section break

  • Support - We'll finally stop the problem from growing. As long as people are creating verifiable BLPs, this proposal poses no threat, as they merely have to provide just one source for their information. The only good criticism I see far, is the proposal doesn't go far enough. But, that's not ground for rejection, only for a new proposal in the future. --Rob (talk) 18:26, 1 April 2009 (UTC)[reply]
  • oppose1)If you want to effectively prevent more casual editors from creating articles Citizendium is that way. 2)Once you've ajusted for effectively making it impossible for casual editors to create new articles can you show that sourcing actually helps at all? 3)Can you show that BLP issues in free articles is actually significant compared to edits to existing articles (remember you can't drive by create an article). Given the falling rate of new articles do you seriously think we can afford to put up more barriers to creation?Geni 18:30, 1 April 2009 (UTC)[reply]
  • Imaginary problem There is no epidemic of unsourced BLPs. The huge number of ones in the most recent months category is due to the retrospective addition of tags to old articles. I checked a total of 50 from March. 48 of them were from 05 or 06. Almost all of them were either clearly notable athletes (including Olympians) and clearly notable politicians (including prime ministers). They were apparently added in batches and not sourced at the time. I checked about the same number of new bios from April 1 New Pages. 4 or 5 were abusive--and they had been already tagged for Speedy, and I deleted them accordingly. An equal number were unsourced and probably not notable, but routine careers, They should be checked and perhaps prodded, or dealt with as Spam and self-advertisement --but we already have speedy A7 and G11 to deal with that. But it does not seem urgent. There is a real problem, though: the addition of false information and abuse to existing sourced bios. Flagged revisions will do them, if it works. This proposal will have no effect on it whatsoever. I challenge the proposer to find me 5 articles from the last 5 days which are actually harmful and have not been caught. I challenge Flo in particular to find more than 1% of the unsourced articles from the backlist that are harmful (& where the harm was not from later additions) and have not been caught. (sourced but harmful articles that have not been caught , yes, those can be found. Neither this proposal nor her proposal addresses them at all.) DGG (talk) 18:35, 1 April 2009 (UTC)[reply]
To answer User:DGG, I looked at articles created March 9 (back of the NP log), and found 13 unsourced bios - User:Kevin/unsourced, not counting those that were moved or fell off the back of the log. Kevin (talk) 22:14, 1 April 2009 (UTC)[reply]
  • Support. Obvious corrolary of "do no harm"... unsourced == not needed until it's sourceable and sourced, there is no rush... As for Sj's idea of a catalog, that has merit enough to kick around and see if it can be made to work. ++Lar: t/c 18:42, 1 April 2009 (UTC)[reply]

Random break

(note: this is so it is easier to edit)

  • Support as a way of dealing with the BLP problem without the backlog that would ensue from flaggings. It's not a solution to the problem by any means, but its a good start. This extends from our policy on verification, since if an article isn't properly verified it should go. When a BLP isn't properly verified, it can do much more harm than the standard unsourced article. In the perfect Wiki, editors shouldn't be able to create articles without going through AfC (which would screen out the bad BLPs), but since we don't live in the perfect Wiki this is a suitable alternative. ThemFromSpace 18:50, 1 April 2009 (UTC)[reply]
  • Oppose as written - per WP:BITE, and in agreement somewhat with User:DGG's comments, espcially to add in "If the administrator has himself made a thorough effort to source them using appropriate resources for the type of article,and demonstrates that on the article talk page." I could go along with allowing a ProD, and if "credible source" were defined as "reliable source" and "verifiable". More discussion may be needed, but this is a good start. Bearian (talk) 19:15, 1 April 2009 (UTC)[reply]
  • Oppose per DGG and Apoc. Joe 19:34, 1 April 2009 (UTC)[reply]
  • Strong Oppose - This is a non-speedy speedy, which makes no sense; and PROD serves this well enough now. I'm all for sources, but this seems to be burning down the village to save it. It's one thing to delete unsourced controversial material in a BLP article; quite another to delete entire articles, regardless of whether the unsourcedness has any whiff of controversy. TJRC (talk) 19:35, 1 April 2009 (UTC)[reply]
    • Why should our reference work give information that has no sources? It makes it completely unreliable. We need to stop pretending that we are giving our readers good content when we're not. Going back later and looking for sources to reference the content is entirely backwards. FloNight♥♥♥ 22:15, 1 April 2009 (UTC)[reply]
      • Most encyclopedias do not give sources for every article. Sources are great but it is perfectly possible that an unsourced article is great, while hundreds of sources can be sherrypicked and re-interpreted. --Apoc2400 (talk) 18:15, 2 April 2009 (UTC)[reply]
  • Oppose for two reasons.
1) As pointed out above we have a WP:PROD procedure that is designed for this sort of situation, i.e. where non-urgent deletion of articles can happen without discussion. In answer to the point made that anyone can remove a prod tag, is there any evidence that this prod tags get removed without explanation from unsourced BLPs frequently enough to satisfy criterion 3 at the top of this page? I don't see many AfDs created for that reason. If it does become a problem in the future we can deal with it then. Until that time we can give articles another five days if they have already been sitting here for three months.
2) Doing this, by treating all BLPs equally, would be a distraction from the primary purpose of WP:BLP, i.e. to protect people from harm. Today I noticed an article that the proposer of this criterion prodded for being an unsourced BLP for three months. Even if the article content was incorrect would having it on Wikipedia for an extra five days possibly do Mr Abbasov any harm? Would it damage him to say that he plays football and weighs 73kg? A simple Google search confirmed that the article was indeed incorrect, because it was out of date, but I was able to fix it with a source findable within seconds. Would the encyclopedia have been better if the article had been speedily deleted? Let's concentrate our efforts on the BLPs, or content about living people put into other articles, that have a potential to do harm, and can be handled by WP:CSD#G10, editing or oversight. As an example, I found an article few days ago about a 16-year-old that said she had performed in pornographic films, and an adminstrator (yes, an administrator) had put a prod tag on it for non-notability rather than delete it immediately. This proposed procedure will take away attention from such serious cases that need to be dealt with speedily. Phil Bridger (talk) 19:36, 1 April 2009 (UTC)[reply]
I PRODded about 50 articles to try and answer the question of whether PROD could be used to deal with this problem, or if the PROD would just end up being removed without sourced being added. I understand that adding a source is better, but lately the number of unsourced BLPs has been growing by 200 articles per day, more than I can source. These have been tagged for months, with no action whatsoever. Kevin (talk) 20:34, 1 April 2009 (UTC)[reply]
There are thousands of articles about people with false, outdated information. Having false, outdated, unverified information is harmful to both the reader and the person. I will no longer accept the lousy content that we are providing to our reader. Unless we remove it, it will be there giving us the false sense that we are doing a good job comprehensively providing information when we are not. My standards are higher than this and I'm not going to lower them. It is wrong to continue to pretend that we are doing a good job when we aren't.
I personally do not have the time, knowledge of the topic, or foreign language skills to search out content to fix these articles. I see no alternative to fix this problem except to delete them until a well sourced entry can be written. FloNight♥♥♥ 20:39, 1 April 2009 (UTC)[reply]
We got an edit policy that specifically tells us how to deal with those articles: Preserve as much information as possible and remove the parts which are unsourced. Could you please elaborate why this approach is inferior to deleting the article? I made an example edit, see here. It took me just a little bit longer than selecting "delete" but this way there is not all information lost and the article is not a BLP problem anymore. Regards SoWhy 20:51, 1 April 2009 (UTC
Actually it does cause problems to have a huge number of stub or pre-stubs. Because we do not have enough volunteers to review every edit in a timely manner some of these under watched articles are going to have unreverted vandalism, nonsense, and unsourced negative content added. We have no idea which article it will be, but we know that someones article is being changed to make it be unencyclopedic as we speak. If the content can be covered in another entry then there is absolutely no additional value to the reader for a stub over a redirect. FloNight♥♥♥ 20:57, 1 April 2009 (UTC)[reply]
This is not an argument in favor of the proposal so much as it's an argument in favor of not having any articles at all on living people. Just because someone adds a source doesn't mean that there is no vandalism, nonsense, or unsourced negative content in the article.--Fabrictramp | talk to me 21:05, 1 April 2009 (UTC)[reply]
Fabrictramp says it all. Every BLP can be vandalized in that way. After all, a BLP with 20 sources would not be covered by this criterion. We cannot go around deleting articles just because they are not watched by enough people. We would have to delete ~95% of all articles then. Yet the risk of someone just coming by and removing all those sources and adding some libel exists. Should we delete it preemptively? You need to explain why it's better to delete exactly and only those pages in Category:Unreferenced BLPs than to apply the editing policy to them and revert them to problem-free stubs or PROD them. Regards SoWhy 21:15, 1 April 2009 (UTC)[reply]
That articles can be vandalized is irrelevant. If this goes through, admins should obviously take care to check if a better version is in the article history as always. - Mgm|(talk) 08:42, 2 April 2009 (UTC)[reply]
Huh? The point is that this is doing something rather than nothing. What we're currently doing is not working because we aren't really doing anything. This isn't a complete fix and I don't believe anyone is advertising as one, but its at least a visible step in the right direction. Mr.Z-man 21:48, 1 April 2009 (UTC)[reply]
Unfortunately, humans have a common tendency to follow the "Something must be done. This is something. Therefore we must do it." line of reasoning. Unfortunately, if the "something" doesn't solve the problem, no progress is made. FWIW, I've worked on a number of BLPs today. Most were easily sourced. One was not, and prodded for lack of notability. 4 were copyvios and tagged for speedy. Yes, this proposal would have gotten rid of the bad ones, but it would have thrown out the good ones too, probably with more work than it took me to source them. I still wonder how many here took up my "fix five" challenge. I fear not many did.--Fabrictramp | talk to me 00:19, 2 April 2009 (UTC)[reply]
I fail to see how there cannot be a middle ground between "solving the problem" and "totally worthless." If we have 2 or 3 people each fixing 5 unsourced BLPs every day, we can basically break even at the current rate that they're being added, assuming that they're all properly tagged and categorized soon after creation. That still leaves the 30,000 from previous months and years. Mr.Z-man 16:33, 2 April 2009 (UTC)[reply]
Hmm, I initially wanted to dispute your numbers, but I just looked at the 36 articles in Category:Unreferenced BLPs from April 2009 and only 3 of them were created this year (1 2 3). The massive influx of the category in the recent 4 months apparently came from the tagging of the many old articles, which the current proposal wouldn't affect. --Amalthea 16:56, 2 April 2009 (UTC)[reply]
The numbers came from a database query, looking for pages created in the last 30 days (still in the recentchanges table) that were also in Category:All unreferenced BLPs or both Category:Living people and Category:All articles lacking sources. There are 346 pages that meet those criteria in the last 30 days, which averages to about 81 per week, and of course that only counts the unsourced BLPs that were properly categorized and tagged. Mr.Z-man 19:36, 2 April 2009 (UTC)[reply]
Why is it better to delete BLPs which are unreferenced for longer periods? Because unsourced BLPs existing for a long time are prima facie of low notability, and probably have few or no watchers; and the unsourced WP article is probably relatively prominent on the internet. Any harm done either by the creator or a drive-by editor may be (a) visible for a long time (b) unclear that it is harmful, since anybody happening by can't qickly check sources (c) high up in Google searches for that person, so any harm is very visible - unlike the same garbage being spewed on a no-name blog. WP:BLP exists for a reason and the logic behind it applies more strongly to people of low prominence, but sufficient notability for inclusion; and it's precisely these bios which are likely to be unreferenced. WP's desire to cover every living person of note needs to be weighed against the possible harm done to the subjects by giving platforms to people who dislike them. I've come across at least 2 bios, for example, which resulted in the subject being placed on a terrorist watchlist (Category:People placed on a terrorist watchlist as a result of false information on Wikipedia, anyone?). Should we place (a) 100% importance on this i.e. no BLPs at all; (b) 0%, let anybody libel anyone ("let God sort 'em out") or (c) strive to find an appropriate balance? Rd232 talk 22:14, 1 April 2009 (UTC)[reply]
  • Support in principle, but oppose the use of the word "credible" in the phrase "no credible sources whatsoever". CSD is not the place to judge whether a source is "credible" (which I'm assuming means reliable). –Black Falcon (Talk) 19:53, 1 April 2009 (UTC)[reply]
  • Strong support in the spirit of BLP. We need something like this in place. PeterSymonds :  Chat  20:19, 1 April 2009 (UTC)[reply]
  • Support, obviously. I do think that the proposal needs to be able to address the huge backlog, as well as future articles. Kevin (talk) 20:23, 1 April 2009 (UTC)[reply]
    • CommentI'm kind of appalled that backlog is being used to justify wholesale and expedited deletion of entire articles with no controversial material. TJRC (talk) 21:08, 1 April 2009 (UTC)[reply]
  • Oppose. Immedatism may be the watchword for BLPs, but often it takes time to find good sources, and any way you look at it, a stub that says "John Doe is a painter" isn't going to hurt anyone. By all means remove controversial unsourced material, even if it's barely controversial at all, per BLP policy - but everybody has something noncontroversial you can say about them. Besides that, it's easy to circumvent this criterion by merely claiming that the person is dead (without sources, who would know?) I also object strongly to the inherently subjective nature of the term "credible." Dcoetzee 20:41, 1 April 2009 (UTC)[reply]
  • Support. Great idea. Should have been implemented many moons ago. JBsupreme (talk) 20:45, 1 April 2009 (UTC)[reply]
  • Comment: It's worth noting because of the grandfathering, this proposal will help us keep far more verifiable material than the current approach. It will get BLP-creators to fix the article, while it's still fresh in their mind (and they're still active with the project), and will encourage them to include sources in the future. Providing sources is easy if it's done at the time of creation, or shortly afterwards, by the creator, who should know where thy got their info. But, if we let that article sit around for months, or years, with no sources, and then re-visit it, the creator is probably gone, or forgot the article, lost interest, or just forgets where he found the information. At that point, it's often a huge burden for others to find sources. For some areas, it's very hard for somebody to find and evaluate good sources outside of the particular area of interest. So, the article gets PRODed and/or AFD'd, nobody is willing or able to fix it, and it gets deleted, losing all the work that went it to it. The editor who took a few weeks/months off Wikipedia, comes back, and finds their article gone. It seems opponents of this proposal make assume the only thing this proposal does is delete more articles, when in fact, it will fix more articles. --Rob (talk) 21:50, 1 April 2009 (UTC)[reply]
    • I agree that after the fact quick fixes like are done at Afd or when someone removes a PROD can be problematic especially for people with minor notability. We can end up with merged identities in an article. And the most quickly available content, that is added merely to keep the article, often will not give us a well balanced article. Getting it fixed soon after creation is key to improving the quality of content. FloNight♥♥♥ 22:05, 1 April 2009 (UTC)[reply]
  • Comment: I see this proposal not as a way to delete unsourced BLPs (it does that, but for me that's secondary) but rather as a means to challenge the attitude that it is acceptable or appropriate for articles to be written that do not cite their sources. Doing so is poor practice from an encyclopedic perspective (see Wikipedia:Verifiability), a legal perspective (see Wikipedia:Copyrights and Wikipedia:Non-free content, both of which apply to use of copyrighted text), and from a professional perspective (the sources of information and ideas should be attributed). Experience has shown that adding {{unreferenced}} is simply not enough in too many cases. –Black Falcon (Talk) 22:09, 1 April 2009 (UTC)[reply]
  • Strong Support, Wikipedia should not have any unsourced BLPs, whether the person is notable or not, and whether the article is potentially harmful to the subject or not. This proposal will not solve the problem, but it will go a long way towards making it more manageable. Lankiveil (speak to me) 22:14, 1 April 2009 (UTC).[reply]
  • Neutral (leaning Weak Oppose) as written - per DGG and Colonel Warden and WP:BITE. PROD appears to be working, so I see no gain and plenty to lose by the proposal. I'd tend to go with consensus but I am not seeing it here. Casliber (talk · contribs) 22:16, 1 April 2009 (UTC)[reply]
    • How it is biting to ask people who wish to contribute an article to add one source - and to do so within 5 days? We are an encyclopedia - surely it properly conveys to a newcomer that we take our content, and its reliability, seriously --Scott Mac (Doc) 22:23, 1 April 2009 (UTC)[reply]
      • It is. If you can't see that for new users then I am not sure how I can explain it to you. Casliber (talk · contribs) 23:53, 1 April 2009 (UTC)[reply]
        • Then your powers of reasoning and expression are a deal lower than I assumed. "It is." it really quite a pitiful response, when we are dealing with such an important issue.--Scott Mac (Doc) 23:56, 1 April 2009 (UTC)[reply]
          • Let's not descend into personal attacks, please. I'll take a stab at explaining why it's bitey. User:NewEditor gets excited about being able to contribute something to an encyclopedia, and writes something about John Doe, a famous person in his town. He's always heard that John Doe did X, Y, and Z, so he adds it to the 'pedia. Like 99% of everyone out there, NewEditor has no clue that reliable, independent sources are needed for stuff "everyone knows". The next time he signs on, there's a new message, saying in effect "your stuff isn't good enough, you didn't do it right, and if you don't hop to it, we'll delete it, assuming we haven't deleted it already." NewEditor slinks away with his tail between his legs, having been slapped down by the Cabal.--Fabrictramp | talk to me 00:26, 2 April 2009 (UTC)[reply]
    • We have over 30,000 BLPs tagged as being completely unsourced, many for more than 2 years - about 1 in 11 BLPs is entirely without sources (almost twice as bad as the rate for all articles) - if this is what "working" looks like... Mr.Z-man 23:13, 1 April 2009 (UTC)[reply]
  • Oppose - This is another example of trying to substitute editorial judgement with blind rule following. This is easily gamed. A book can be listed as a source. How many admins are going to go to the library and read the book to verify the claims? Source references can be deleted and then the article tagged. There is no substitute for editorial judgement. A key point of our BLP policy is the deletion of unsourced problematic/controversial claims, not all unsourced claims. If you read a completely unsourced BLP and it has no claims that seem problematic, it should not be deleted. The biggest problem with admins editing articles is admins blindly applying rules to articles that they know nothing about. If you are ignorant of the subject of the article,you should not edit it. WAS 4.250 (talk) 22:22, 1 April 2009 (UTC)[reply]
    • An unsourced or poorly sourced article adds no value to the encyclopedia and potentially causes problems. People have the right to a well-written, well-balanced article based on verifiable reliable sources. Experience has taught us that if we accept less then the articles will remain. Taking another approach is needed to raise our standards to where they need to be in order to have a high quality reference work. FloNight♥♥♥ 22:29, 1 April 2009 (UTC)[reply]
    • re "If you are ignorant of the subject of the article,you should not edit it." Most editors follow this advice. If an article is outside their area of expertise, they will simply leave it alone. So, unsourced articles on marginally (but sufficiently) notable people are left alone by Wikipedians who never heard of the bio subject. Unfortunately, we can't rely on experts for most articles, as there just aren't enough. Often, the only Wikipedian familiar with the bio subject, is the one person who wrote the article. We need independent reviewers of articles, who aren't necessarily familiar with the subject, to carefully review all BLPs, not just for obvious libel, but more subtle problems. Such reviewers need to know the sources used in writing the article, otherwise it's impractical to spend hours search blindly for sources, never being able to prove they don't exist. --Rob (talk) 00:24, 2 April 2009 (UTC)[reply]
  • Oppose as drafted (1) CSD is no place to make policy or define terms so talk of "credible sources" is inappropriate. Either refer to "reliable sources" or "sources". Given how WP:BLP is worded I suggest it should be "reliable sources" (2) This seems to me to be more about amending WP:PROD than amending WP:CSD; it doesn't really fit here; if it were listed there I might support it. (3) I've created a summary of existing deletion policy for BLPs at WP:DP-BLP so that I could find my way around the myriad policies. Hope that's useful. As others have pointed out, BLP articles that fail to assert notability qualify for CSD under A7 and negative unsourced BLPs under G10. Neutral BLPs which assert but do not prove notability only qualify under PROD. The issue about prods being removable by any editor seems to be a problem with prod rather than a problem with BLPs or CSD. AndrewRT(Talk) 22:30, 1 April 2009 (UTC)[reply]
  • Support, except for the part about "credible" sources. That will just make it difficult for admins to enforce. A binary analysis of whether there are any sources provided or not is simple to understand and easy to implement. Regular processes can handle the corner cases. Undeletion is a straightforward solution for when sources are later found, or for when an author forgets or does not know to provide sources. --bainer (talk) 22:57, 1 April 2009 (UTC)[reply]
  • Comment Any WikiProject for an article should be notified - they are the people most likely to have the resources and interest to provide reliable and relevant sources. Royalbroil 23:26, 1 April 2009 (UTC)[reply]
  • Oppose The criteria itself is controversial (in other words, there isn't widespread agreement that articles meeting the proposed criteria be deleted). The vast majority of pages which could be deleted by this would be harmless. And who are we kidding, really? Where are the leagues of editors and admins combing cat:BLP looking for credible sources who would be well served by this new deletion criteria? Are we just adding another backlog? This time with a reasonable downside risk to it? Protonk (talk) 23:39, 1 April 2009 (UTC)[reply]
  • Oppose. Why delete good articles at speedy that may not be content violations simply because they lack citations? If the person is notable, then the article should stay. If there are content issues, tag it. If you really think there is a major concern, PROD it or take it to AfD. Vegaswikian (talk) 00:25, 2 April 2009 (UTC)[reply]
  • Oppose I fail to see, as DGG has said, why G10, PROD, and AFD do not cover all of this. More minor points: As AndrewRT has mentioned, the issue of PRODs can be fixed by forcing rejected prods to automatically be sent to AfD. Or maybe even by creating WP:AfD/Uncontroversial, where seeing what is tagged with prod and with what rationale can be more easily identified. Also, as Casilber has mentioned, I fear that this will lead to even more newbie-scaring off, and right now, we need to court newcomers more than we need to delete every single unsourced BLP. 01:40, 2 April 2009 (UTC)
    • Can you explain how tagging per this proposal would scare off a newbie *more* than PROD and/or AFD? --Rob (talk) 03:23, 2 April 2009 (UTC)[reply]
      • Sure thing. PROD rationales and AFD by their very nature are usually only used on non-notable or unverifiable articles. This "A10" rationale would be a bit more indiscriminate, and would end up hitting verifiable and notable people. For someone to create a article on a perfectly fine subject without an explicit source and have it be deleted a week later...well that would be more disheartening to me that if it had happened to me for writing about a non-notable subject. 05:50, 2 April 2009 (UTC) —Preceding unsigned comment added by 24.62.228.22 (talk)
  • Oppose. This is unneeded as we have systems in place that seem to work very well at deleting material. This looks to be a solution in search of a problem. We're here to create articles. Let's find ways to encourage sourcing and better writing instead. -- Banjeboi 02:10, 2 April 2009 (UTC)[reply]
  • Support We can have articles on the subject when they are sourced. This is about academic responsibility. Considering it can be undeleted on request then if anyone really cares enough about the article then this won't effect them. It will just get rid of hundreds of abandoned unsourced articles about living people. Chillum 02:23, 2 April 2009 (UTC)[reply]
the proposal was not for dealing with the abandoned ones,but for new articles coming in. DGG (talk) 03:42, 2 April 2009 (UTC)[reply]
Perhaps when we no longer have to deal with 80 or more new unsourced BLPs a week, we can actually make some progress on the 30,000 abandoned ones. Mr.Z-man 04:29, 2 April 2009 (UTC)[reply]
  • Support. It's not perfect, but on the whole this will do more good than bad. Yilloslime TC 03:03, 2 April 2009 (UTC)[reply]
  • Comment This proposal reminds me of when "Free Use Content" got turned into "Non-free content" and then the deletions became rampant. Obviously, two different cases with different circumstances... but I think this shouldn't turn into a "Tag 30k articles in a week via bot" type of thing (which I'm not saying this will). No other comment except to say I think this is a step in the right direction. --Izno (talk) 04:37, 2 April 2009 (UTC)[reply]
  • Oppose. Any speedy criterion which opens up for the speedy deletion of articles like Lars Peder Brekk (the Norwegian minister for agriculture) is simply not acceptable. Sourced or not sourced, that BLP should never be deleted, let alone speedy deleted, no matter how many days or how long a grace period is given. Sjakkalle (Check!) 07:22, 2 April 2009 (UTC)[reply]
    • Neither is it acceptable to have BLPs without a single source. Kevin (talk) 07:53, 2 April 2009 (UTC)[reply]
    • In theory, that same article could already have been deleted with WP:PROD. In reality such deletion wouldn't occur with PROD or with this proposal, because somebody could easily prevent it, by adding one source (like the one there now). --Rob (talk) 07:56, 2 April 2009 (UTC)[reply]
      • No administrator worthy of the position should delete an article on the Norwegian minister of agriculture. If it is PROD-ed, and for some reason remains PROD-ed at the end of five days, the correct procedure for the admin is to remove the PROD tag. I strongly believe that if an article like Lars Peder Brekk were deleted from Wikipedia, it would bring Wikipedia into serious disrepute in the Norwegian press. Sjakkalle (Check!) 08:53, 2 April 2009 (UTC)[reply]
      • Regarding the reasons behind the proposal, I don't think it would achieve its aim if it were implemented, because the root cause of BLP violations is not that biographies are unsourced, but that our RC/Newpages patrol is not able to catch each and every edit made, and that bad edits sometimes slip through. There are without question too many cases of serious libel being added to BLPs which were caught up by the press before it was caught by our anti-vandalism mechanisms. For example, the bios of prime ministers Jens Stoltenberg and Torbjørn Jagland were both hit. I have at times (thankfully, very rarely) encountered vicious and obvious attack pages which remained online for over two weeks when I pulled the trigger on them. However, while an event like that is very serious (and I strongly favor stiff sanctions levied against people who do that kind of mischief), neither was fundamentally a result of people accepting unsourced articles or edits. It was a result of people not noticing the vandalism. Unsourced BLPs which are negative and disparaging are already being speedy deleted by criterion G10, and unsourced edits which are negative to a BLP subject are speedily reverted when they are noticed, as they should be. A speedy criterion which expands our mechanisms to correctly condemn bad-faith stuff to something which targets good-faith stuff as well is not going to improve the encyclopedia. Sjakkalle (Check!) 09:12, 2 April 2009 (UTC)[reply]

Random break

(note: this is so it is easier to edit)

  • Oppose There is no deadline. Articles should be flagged to encourage edits (with the unref tag, for example) instead of deletion (unless, of course, they simply aren't notable). Deleting these articles will just unfill many hole that have been plugged with their initial creation. Editors who start unref'd articles (BLP or not), should be pointed to ways of adding refs and improving their creations. Lugnuts (talk) 07:44, 2 April 2009 (UTC)[reply]
There are currently about 14000 articles tagged as unsourced BLPs. Waiting for improvement has not worked up to now, so how do suggest we proceed? Kevin (talk) 07:53, 2 April 2009 (UTC)[reply]
In the time you would take to delete them with that new A10, you could easily apply WP:EP to them or WP:PROD them. The dilemma you create is a false one: As those deletions have to be made manually by admins, multiple admins would have to review each of those 14000 articles to avoid deleting articles where the sources exist but which are still tagged or where the sources were removed in acts of vandalism. Now if those admins instead of hitting "delete", just hit "prod" or, much better, just remove the unsourced content and leave a valid stub, would it take them more time? Not really I'd say. It's actually more time consuming because all users can PRESERVE/REMOVE those articles or PROD them but only admins could delete them. Regards SoWhy 09:00, 2 April 2009 (UTC)[reply]
If we remove all the unsourced content there is nothing left. We're not talking about poorly sourced articles, they are completely unsourced. Why are people so resistant to adding sources? Kevin (talk) 09:26, 2 April 2009 (UTC)[reply]
It's not about whether people are resistant to adding sources. It's about why you think admins have the time to delete those articles but they don't have the time to fix them which does not take more time. I pointed out an example above: It took me the same time to just cut it down to a stub as reviewing all revisions whether the sources were in the article before (and that's what admins would have to do!) would have taken me. And don't you think the result I achieved is preferable to deletion? Regards SoWhy 09:32, 2 April 2009 (UTC)[reply]
Yes I do. I also believe that an atmosphere where the creator of an article does the sourcing rather than having someone come behind them and fix things up is better. Look at it from my point of view: I strongly believe that every BLP should be sourced, and that there is no reason why any BLP should no be sourced. I do not have the time or resources myself to fix every unsourced BLP, so I must turn to another method. Tagging them has not worked, the growing backlog proves that. My objection to PROD is that it can be removed without addressing the problem. What is next? Kevin (talk) 09:44, 2 April 2009 (UTC)[reply]
The whole point of the wiki system is that the creator does not have to do everything but that every article is a collaboration of many editors. I understand your point of view, I share it in fact. But if you say that you don't have the time to fix them yourself, you won't have the time to delete them with this new A10. And my point is that if fixing and deleting take the same time, there is no reason I can see to prefer the latter. The main problem with those BLPs is not that we cannot delete them, most prods go uncontested after all. It's that noone is willing to go through that backlog to handle them. But a new criterion will not fix that, will it? Regards SoWhy 09:54, 2 April 2009 (UTC)[reply]
I'm sure I can make an informed decision and delete a whole lot faster than adding a decent source. Kevin (talk) 09:59, 2 April 2009 (UTC)[reply]
I challenge you to prove it. Let's take the random example I picked yesterday (and to which I alluded before): Richard Doherty (military historian). To make your informed decision, you will have to review all 40 revisions of this article to see whether there were sources in it at some point (because they can easily be removed by a vandal). Set a stopwatch and see how long it takes. Then, navigate to Google News and search for "Richard Doherty" "historian". Find a source and write a simple <ref>-tag citing that source. Set a stopwatch and time your progress. Then tell me which of those tasks took longer. Regards SoWhy 10:09, 2 April 2009 (UTC)[reply]
This is a completely bogus example. The warning tag would be placed shortly after a *new* article is made. All but the first edits to the article would be done with the warning about sources plainly visible. The admin would review the article around 5 days after. The example you gave was made in 2006. Using your own example, an admin would only have to review four versions by two editors. Most importantly, the creatore would have been given a warning, and been able to provide the source the used, preventing any admin from having to do anything, and this problem could have been fix in 2006, if we had this proposal earlier. Obviously, you manufactured the best example you could, and it actually disproves your point. --Rob (talk) 17:51, 2 April 2009 (UTC) Added: I should have also noted, the example article you gave actually was sourced from the very first version, and would *never* be deleted under this proposal, as it doesn't require complete and proper sources. --Rob (talk) 18:01, 2 April 2009 (UTC)[reply]
  • I'm not sure every admin would be as thourough as me by searching the history before deleting a page, but I'd like to point out that there is a tool that makes it a lot easier to search an article history than the manual labor methord. - Mgm|(talk) 10:13, 2 April 2009 (UTC)[reply]
  • If they are not, they are not following policy. Speedy deletion policy is that nothing should be deleted where there is a previous version to revert to that would not be speedy-deletable. But which tool is there to automatize that task? Searching for <ref>-tags? Well, most newbies don't know them and thus would not use them. I cannot think of a way to search for all ways someone might have referenced an article. But to speedy-delete a page, that is what admins would have to do. Regards SoWhy 10:32, 2 April 2009 (UTC)[reply]
It took me about 20 seconds to check the first edit, and the one before yours, both of which had a source, therefore the appropriate action is not deletion. I'm well aware of how long deletion takes from going through candidates for speedy deletion. It wasn't the best example perhaps, but my opinion stands. Kevin (talk) 10:20, 2 April 2009 (UTC)[reply]
  • Support. Black Falcon (talk · contribs) and Thivierr (talk · contribs) (Rob) summed up my view best. The proposal needs some fine-tuning but the basics are there. If we protect the existing pages by grandfathering, we can improve Wikipedia by sourcing them, rather than wasting our time tagging incoming articles. Wikipedia is now of the size that we should encourage good editorial judgement over growing at all costs. Deleting articles that don't meet requirements immediately enforces the rules listed at the bottom of the edit window (verifiability is the only one of the rules listed there that is not being effectively enforced). As long as existing articles are left out of the proposal, I fully support it. - Mgm|(talk) 08:57, 2 April 2009 (UTC)[reply]
  • Support. I'd be screaming blue murder if this was retrospective, but for new articles? We need a cultural change in this respect, and there's zero harm done by implementing this as a start. Rebecca (talk) 10:43, 2 April 2009 (UTC)[reply]
  • Oppose. This proposal creates a new deletion mechanism that works parallel to WP:PROD and has no advantages over it. It would create additional administrative workload, and would require those of use who regularly check proposed deletions to attempt to rescue article that should not be deleted to check in two places rather than just one. There is no reason that instead of changing CSD these articles cannot simply be dealt with by placing a {{prod}} tag on them instead of the currently-proposed new tag. I would suggest those who consider deleting these articles necessary should turn their attention to the existing mechanisms for dealing with these issues, rather than trying to create new ones. JulesH (talk) 12:16, 2 April 2009 (UTC)[reply]
  • Oppose - Per DGG. — neuro(talk)(review) 12:36, 2 April 2009 (UTC)[reply]
  • Support - equivalent of preventing users from removing prods without fixing the problem, which should be policy anyway. PhilKnight (talk) 14:14, 2 April 2009 (UTC)[reply]
  • Weak support—while I balk somewhat at the idea of deleting articles using such a crude method, given the seriousness of potential damage through biographies of living persons it is a reasonable measure. That being said, I agree with Protonk that this proposal is greatly weakened by its own controversy; most criteria for speedy deletion are those which the community as a group endorses as good reasons to delete a page without further discussion. {{Nihiltres|talk|log}} 16:24, 2 April 2009 (UTC)[reply]
  • Weak support I already delete unsourced BLPs if any negative thing is said, per G10, and those without claims of notability per A7. Still, I think the trend is to raise the bar for BLPs, and rightly so. Jclemens (talk) 16:44, 2 April 2009 (UTC)[reply]
  • Support. We shouldn't be creating unsourced articles about any topic.   Will Beback  talk  17:05, 2 April 2009 (UTC)[reply]
  • Strong support - Anything to strengthen protection of BLPs is a step in the right direction. Policy dictates that sourcing is the burden of the author. It is not an administrative responsibility to source BLPs. It is our responsibility to protect the subjects and victims of BLPs. In cases where there are no sources, the article should not exist. Those wanting to save such articles will have five days to dig up sources. لennavecia 17:07, 2 April 2009 (UTC)[reply]
  • Support. Verifiability has always been the cornerstone of our articles. This is an enhancement and another step forward to our BLP problem. - Mailer Diablo 17:11, 2 April 2009 (UTC)[reply]
  • Support the principle, with a hope that that deadline will steadily move backwards in time as the backlog moves forward in time, until the problem is dealt with. Disagree, however, with the timeframe. We really should have a "Criteria for Quasi-speedy Deletion" between PROD and SPEEDY for images and A10. Sceptre (talk) 19:21, 2 April 2009 (UTC)[reply]

Proposed proposal modification

Noting bite objections, hesitancy over the harshness of the concrete proposal’s solution, and the seriousness of the issue (unsourced articles detracting from Wikipedia’s reliablilty).

Instead of deleting after 5 days, move the article to some project space location (but never automatically to userspace), where if it remains without credible sources, after 90 days it may be deleted.

By moving the article out of mainspace, and breaking any incoming links, this somewhat mitigates the potential damage to a LP, considerably reduces the risk of the casual reader unwittingly reading misinformation, and gives the newcomer-author ample time to consider our sourcing requirements. --SmokeyJoe (talk) 05:06, 2 April 2009 (UTC)[reply]

That proposal does not address most of the opposing reasons, especially not why deletion is to be preferable to cutting articles down to stub size by removing the unsourced content as per editing policy. The main problem is not that those articles exist but that noone feels obligated to do the simple work needed to preserve the information. And it does not explain why admins would be willing to go through thousands of articles to move them but not to prod them or remove the unsourced information - after all, there is no difference in the time it takes to do it. Regards SoWhy 09:06, 2 April 2009 (UTC)[reply]
I don’t think that wikipedia should host unsourced BLP stubs.
I don’t think I support WP:PRESERVE when it comes to unsourced information on living people.
I expect that, in practice, the admin will move, leaving no redirect and tag the unsourced BLP. If no one removes the tag, or moves the article to main space or userspace, then after 90 days it will be deleted by an automated process. I think the difference with PROD is that articles are prodded if it is believed that the article should be deleted. BLPs would be moved to the 90 day limbo zone out of a hope that the authors will provide sources. Yes, it sounds a lot like PROD, but much gentler for the newocomer author in that it has a long limbo time, and different in that the article is immediately moved out of mainspace. --SmokeyJoe (talk) 09:38, 2 April 2009 (UTC)[reply]
Aside from the fact that WP:PRESERVE is policy that cannot be overruled by creating a new criterion here, you fail to explain why admins would have the time to move those article and tag them and leave the author a note and delete the article after 90 days but won't have the time to WP:REMOVE the unsourced information or spend 2 minutes on a simple Google News search instead. If they have enough time to do the former, the surely have enough time to do the latter. If they don't have the time to do the former, then the problem is the unwillingness to do any work on those articles, not their existence and then it won't be solved with such a criterion. Regards SoWhy 09:48, 2 April 2009 (UTC)[reply]
I understood this was about BLPs completely lacking in credible sources. Removing the unsourced information means removing everything. Arguably, such articles are deletable due to WP:BLP, notwithstanding WP:EP. The admin actions are straightforward, even automatable. Improving articles is not straightforward. Google news reports are not a good basis for wikipedia articles. It is definitely not the role of admins to go around sourcing newcomers substandard BLPs. The question that seems to be dividing us is: “Should unsourced BLPs be allowed to stay?” --SmokeyJoe (talk) 10:30, 2 April 2009 (UTC)[reply]
No, it's not automatable. As sources can be removed by vandals, each article has to be checked for this before deletion. It's a time-consuming procedure anyway. Google News can be basis for WP articles because it allow finding reliable sources, which is what matter here. The question is not, whether unsourced BLPs should be allowed but whether deleting them is really the best way to deal with them given the alternatives (which already exist). Regards SoWhy 11:07, 2 April 2009 (UTC)[reply]
WP:CSD, WP:PROD, and WP:BLP are policy also. If there is a consensus to change the editing policy, it can be changed. With the exception of law-based policies like WP:COPYRIGHT, no policy is immutable. The "alternatives" consist of the few people who actually care about bringing BLPs up to standards within a decade sourcing every single BLP of every marginally notable person that gets created by themself. That's what we've been doing, that's what's led to the 30,000 page backlog we have now. If you have other alternatives that don't involve deletion of a large amount, or a few people doing massive amounts of work, please propose them. Mr.Z-man 17:10, 2 April 2009 (UTC)[reply]

Alternative solution

If there are 14,000 unsourced BLP articles out there, why doesn't some just go through and tag them all with PROD? Or more realistically, tag the first 500 for now so that the PROD backlog doesn't get too much and you give content adders the opportunity to save as many as they can within a reasonable length of time. Set up a Wikipedia:Wikiproject Unsourced BLPs to manage teh workflow. In six months the problem will be over. This can already be done within existing policy and achieves the same - this debate becomes redundent. AndrewRT(Talk) 16:55, 2 April 2009 (UTC)[reply]

Addressing unsourced articles, not just unsourced BLPs

The problem is not limited to BLP articles. Every day the category of unreferenced articles grows in size and despite my best efforts, it's like carrying water to the sea -- so I gave up. (I manage to reference 5 articles while 50 come in).

Unfortunately, the editing community can't agree. At the one side there are people who say there is no deadline and that existing deletion processes address these issues, on the other hand there are people who want to take immediate action. The ever increasing amount of unreferenced articles clearly mean something should be done, so we need to reach a middle ground that keeps both parties happy and does something about the problem. - Mgm|(talk) 09:39, 2 April 2009 (UTC)[reply]

Option 1: Speedy deletion

This option might be disagreed on by many, but it addresses something that is already codified as a policy. Articles must be verifiable.

At the bottom of the edit window there is a line that says: "Content that violates any copyright will be deleted. Encyclopedic content must be verifiable. You irrevocably agree to release your contributions under the GFDL*." Copyrighted material is regularly deleted by the speedy deletion criterion G12 and the rules about GFDL are applied whenever needed. Verifiability has no such efforts to enforce it. To encourage good encyclopedic practices and lift weight of AFD, we should discourage the writing of unreferenced material altogether. It's time to focus on quality rather than quanitity. To avoid serious loss of information this would only apply to newly created entries.

A10 speedy deletion applies to: "Any article that lists no sources or external links whatsoever and has been created after April 30, 2009." -- Mgm|(talk) 09:39, 2 April 2009 (UTC)[reply]

Option 2: Projectification

To make recreation of potentially interesting articles easier for WikiProjects, I also suggest a change to WikiProject pages. Each project would get an additional page called a "draft board" or something similar where they can ask to have have pages "projectified" (project type userfication) for referencing. If this method is used, we can use an alternative prod format which has the criterion: "Any article that lists no sources or external links whatsoever, has been created after April 30, 2009 and has been tagged for at least 5 days." (removing the prod without addressing the issues raised would obviously be forbidden.) - Mgm|(talk) 09:39, 2 April 2009 (UTC)[reply]

Option 3: Filtering

The new AbuseFilter can be set to disallow any article that lacks references altogether and give the user making the edit a friendly warning without the requirement for a bot.

This will clearly put more strain on AFD and other deletion processes because it will become less clear whether sources are reliable sometimes, but it does address the issue of articles being completely unreferenced by giving editors something to check for accuracy rather than wondering where the information came from. - Mgm|(talk) 09:39, 2 April 2009 (UTC)[reply]

Can it work if the creator writes "Soorces: Some Book by a Guy" (sic)? I think it important to allow plenty of leeway in what constitutes a source. Kevin (talk) 09:56, 2 April 2009 (UTC)[reply]
I don't think WT:CSD is the right venue for such discussions... SoWhy 11:12, 2 April 2009 (UTC)[reply]
I posted it here because it is an expansion on the BLP thread above. I'd be happy to move it if we can agree on a location and leave a link behind. - Mgm|(talk) 11:51, 2 April 2009 (UTC)[reply]

I would strongly oppose any such proposal, as it increases the barrier for new users creating topics. Most of us didn't learn how to format references properly for quite a while after we began editing wikipedia, and the fact that somebody can come here and start a new article with very little commitment (i.e., just by signing up for an account and waiting a couple of days) is one of our strengths. Adding new barriers to this should only be done when absolutely necessary, and I see this proposal as a solution without a problem. JulesH (talk) 12:19, 2 April 2009 (UTC)[reply]

Preternaturally Strong Oppose. This is, in my considered opinion, a terrible idea. I'm sorry to be so blunt, MacGyverMagic, but I just do not think this should be implemented. Ever. From the proposal's pushing personal preference of one referencing method over another, its disregarding factor many wikiprojects are moribund, plus apparent reluctance of proposer to continue help adding references (fine) and instead wipe swathes of new articles on sight (not fine); the idea a reward for a job well done is three new jobs, is not uncommon; even if one specific rewarded person decides to pull back for a while, that doesn't warrant measures like this. –Whitehorse1 12:22, 2 April 2009 (UTC)[reply]

This is a terrible idea and seems counter to the entire concept of Wikipedia. -Chunky Rice (talk) 17:13, 2 April 2009 (UTC)[reply]

Question

Do these options also cover things like the one-sentence stub articles about "this town in a country you've never even heard of" and "that one book that isn't even sold in bookstores"? I think that an important part of Wikipedia's expansion is coming from the people who quickly create large numbers of short articles, encouraging others to expand them... saying that these articles with 1-2 sentences, maybe an infobox, a stub template, and a couple of cats should be deleted or "projectified" just doesn't seem right to me. Certainly all articles should be references—these short articles are tagged with {{Unreferenced}} as is—but when an article is that short not having references is, in my mind, acceptable. Once an article gets longer and isn't stating the obvious (obvious being "[Town name] is a town in [the United States/Argentina/India/whatever], located at [Coordinates]", then it certainly needs to be referenced, but are you proposing articles like that sample be deleted or projectified due to a lack of references? If so and this gets passed, I can see a number of users severely cutting back on their editing time because what they focused on can't really be done anymore. –Drilnoth (TC) 13:47, 2 April 2009 (UTC)[reply]

There is no added value to a reader to have stubs or pre-stubs that are unreferenced. The reliability of our content is entirely based on good sourcing since our content is largely created by non-experts. We regularly find hoax or nonsense articles when deep reviews of references are done.
In my opinion, an existing inferior article will stop someone from starting a better article because they will not as urgently see the need to fill the gap if there is not a red link. So, there is a definite downside to a massive number of extremely brief entries. FloNight♥♥♥ 18:46, 2 April 2009 (UTC)[reply]
And hopefully these editors can be directed toward other ways to contribute if they are not using any references. FloNight♥♥♥ 18:49, 2 April 2009 (UTC)[reply]

Add a time delay for G8

I propose adding a time delay for G8 - I see it being abused unintentionally in the middle of discussions with slow editors. Article is being edited by 1 or 2 newbie editors; it gets a csd tag slapped on it within hours (often for notability, lack of sources, &c), sometimes it's deleted before the author even understands what has happened. OK, we're not so friendly to newbies, no problem -- at least there's a talk page to have a steady discussion about whether or how to create the article properly, right?

But no, the talk page gets speedied also, almost immediately. This can be very confusing.

Proposed alternative : a talk page for a deleted article can only be deleted after the article has been deleted for [a week]. Admin-aware scripts can still find these pages automatically; and it's friendlier to new editors. If the talk page is spam or vandalism, as people seem to have suggested in past versions of this discussion, it can still be speedied under the appropriate criterion. +sj + 18:11, 1 April 2009 (UTC)[reply]

I support this, for talk pages of deleted pages only (things like redirects to deleted pages can be speedied right away). –Drilnoth (TC) 18:18, 1 April 2009 (UTC)[reply]
For what it's worth, my rule for orphaned talk pages is orphaned + no talk page activity in the past seven days. (I also generate a report currently set to update twice weekly here: Wikipedia:Database reports/Orphaned talk pages.) The colored rows are the ones I used to bot delete. --MZMcBride (talk) 06:48, 2 April 2009 (UTC)[reply]
I support retaining Talk pages for a while, but I'd say 4 weeks, to allow for illness, holidays, real life, etc. I also suggest a banner should be placed on a deleted article's Talk page to: link to the deletion discussion or other explanation of the deletion; tell the editors what they can do if they think the deletion was unjustified or they have found sources to show notability, etc. --Philcha (talk) 10:30, 2 April 2009 (UTC)[reply]
Not a bad idea, but if it would help get this through, why not use something like PROD instead of speedy deletion? Gives the editor a chance to get their act together if the material's legit, and still gets it off the project if they can't be bothered getting it referenced, or if the references don't exist. Rebecca (talk) 10:45, 2 April 2009 (UTC)[reply]

So when I close a TfD as delete, I can delete the template itself under the TfD, and the /doc subpage under G8, but I have to wait a week to delete the talk page under the same criterion? Happymelon 17:09, 2 April 2009 (UTC)[reply]

Is [8] an approved change to the wording of {{duplicate}} ? 76.66.193.69 (talk) 05:58, 2 April 2009 (UTC)[reply]

Seems fine to me. Do you disapprove? --Amalthea 09:53, 2 April 2009 (UTC)[reply]
The comments below the template state "Only use for images that are exact duplicates!" Hence the wording of the template now better reflects usage so I sould support keeping this change. AndrewRT(Talk) 17:00, 2 April 2009 (UTC)[reply]

What is a "sourced article"?

Several articles which are not explicitly sourced, but still contain enough information to make the location of the source obvious. Take as an example:

John Cox is a chess player who has written several chess books including: The Berlin Wall: The Variation That Brought Down Kasparov, Starting Out: 1.d4, Dealing with d4 Deviations and Starting Out: Alekhine Defence. He holds the title of International Master and has a FIDE rating of 2367.

If something like this were submitted, the article is not explicitly sourced, except that if someone took a look at any of the books mentioned in the paragraph, they would see "John Cox" prominently written on the front cover, the back cover , the spine, and the inside of the book. A claim that someone has a FIDE rating is obviously sourcable to the FIDE rating list. Is an article like this "unsourced" for purposes of the speedy criterion people are discussing above?

Obviously, an editor ought to make a reference section, he ought to provide a link to the chess federations website to show that the person really has the rating the article says he has, but not doing so is precisely the kind of mistake novice editors often make. Sjakkalle (Check!) 15:10, 2 April 2009 (UTC)[reply]

WP:DELETE says improvement is always preferable to deletion. However I've seen deletion debates that have ignored such pointers to good sources and where there have been delete votes. I confess I'm in 2 minds about this situation. Such behaviour is a violation of the WP:DELETE policy, and some of the attitudes I've seen behind "delete" votes have not been pleasant. OTOH I have not intention of doing another editor's chores, and I've seen editors who create unsourced stubs by the lorry-load. --Philcha (talk) 15:37, 2 April 2009 (UTC)[reply]
I think the simple answer to your question is yes, that would be unsourced. Sources need to be explicit. AndrewRT(Talk) 17:03, 2 April 2009 (UTC)[reply]
Here's a source for Cox's books: http://www.amazon.com/s/ref=nb_ss_b?url=search-alias%3Dstripbooks&field-keywords=john+cox+chess&x=12&y=18 .There are other sources, too, including the Library of Congress. Yours, GeorgeLouis (talk) 18:16, 2 April 2009 (UTC)[reply]
I agree. The publishing world is full of ghostwriters, pen names, collective pen names, "as told to"s, royalty-only credits, posthumous works finished by others, and all sorts of various strageness. To cite an example, Don Pendleton only wrote the first batch of Mack Bolan books, but his name still appears on all the subsequent volumes anyway, for what I can only guess is contractual reasons. I'm not saying any of this is good or bad or right or wrong, or whatever, but the bottom line is pretty clear that just because someone's name appears on the cover doesn't mean they wrote the text in side or even necessarily approve of the text inside. For this reason, a book cover alone cannot be considered a reliable source. Andrew Lenahan - Starblind 18:21, 2 April 2009 (UTC)[reply]