G11s in Draft Space
I'm not sure if anything has changed or if I'm simply having more Drafts on my watchlist but I've been noticing a lot of Drafts deleted under G11. As a new page patroller I am no stranger to G11s and regularly use that tag myself. However I've now seen at least a couple occasions where there are good faith efforts at creating an article that are wiped away (or proposed to be wiped away) through G11. These articles certainly weren't ready for mainspace, but they weren't in mainspace they were in drafts and were going to have to go through AfC. Maybe they'd have been approved, maybe not, but I think something is off when these drafts are summarily deleted without any real chance to improve them. I am not in favor of saying no G11 for draft space at all but would love to see more editor caution in tagging drafts as such and admin in approving those tags. Best, Barkeep49 (talk) 02:34, 9 October 2018 (UTC)
- I have seen cases (rarely though) where a draft starts out as promotional PR speak because that's the only text the author has just starting out, and then the draft is improved to the point where it becomes acceptable. In general I don't like seeing a G11 tag on an draft unless the draft has been around for a while and isn't improving. But early on in the life of the draft? No, not really. ~Anachronist (talk) 03:09, 9 October 2018 (UTC)
- I have processed a lot of AfC submissions. Many of them are so clearly G11 I tag them immediately for deletion. Why waste volunteer time rereviewing spam? Legacypac (talk) 03:48, 9 October 2018 (UTC)
- You're definitely an experienced AfC reviewer. But I think there's a big difference between a draft that has yet to be submitted or has been submitted once and one that has been declined a couple of times. Draft space should be, in my thinking, a place where articles can be incubated and improved; it's why we don't allow most speedy delete criteria and why we let drafts sit for six months before being deleted (maybe). Summary deletion feels different there than it does in mainspace where it harms the credibility of the encyclopedia. We invite editors of declined drafts to the Teahouse for a reason - the idea that a draft would need to be fundamentally rewritten to be accepted, which is the G11 standard, doesn't strike me as troublesome or a waste of volunteer time. Best, Barkeep49 (talk) 04:00, 9 October 2018 (UTC)
- I have processed a lot of AfC submissions. Many of them are so clearly G11 I tag them immediately for deletion. Why waste volunteer time rereviewing spam? Legacypac (talk) 03:48, 9 October 2018 (UTC)
- I am also for applying a higher G11 standard for drafts. I know some of our AfC reviewers are on an anti-spam jag and are using G11 as part of this. I fear admins are not giving due considerations to WP:ATD for these drafts. No way for me to know though because deleted stuff is in a black hole. ~Kvng (talk) 03:52, 9 October 2018 (UTC)
- A lot of Draft SPAM is created for the SEO benefits created by the links and mirrors. A Wikipedia link from Draft space is almost as good as from mainspace, and well meaning editors who promote keeping SPAM around in Draft are only facilitating the abuse of the site by Spammers. I'm a big advocate of promoting the less than perfect but notable pages for the big world of editors to work on, but the chances of either a disinterested or connected editor rewriting a topic that meets G11 are slim to none. Legacypac (talk) 07:59, 9 October 2018 (UTC)
- How are SEO benefits achieved in these cases? I thought draft space is not indexed by Google and others, so links from there should not turn up? If there are really SEO benefits, maybe we can find a technical solution to prevent that, thus eliminating the incentive to create such drafts. Regards SoWhy 08:11, 9 October 2018 (UTC)
- No index links are an important part of sculpting inbound link profiles for SEO. Been that way for a few years now. Legacypac (talk) 09:59, 9 October 2018 (UTC)
- How are SEO benefits achieved in these cases? I thought draft space is not indexed by Google and others, so links from there should not turn up? If there are really SEO benefits, maybe we can find a technical solution to prevent that, thus eliminating the incentive to create such drafts. Regards SoWhy 08:11, 9 October 2018 (UTC)
- Quite a lot of G11 spam in draftspace is lightly edited press releases, i.e WP:COPYVIOs; many or I'd say most are on non-notable topics anyhow; and for things that meet G11 criteria it is better to start anew. The main thing with spam is that even removing the buzzwords and making it not obviously spammy doesn't really fix the issue; it just hides it. To write a neutral article one must start with the reasonable intention of doing so with multiple independent and indepth sources. Galobtter (pingó mió) 08:04, 9 October 2018 (UTC)
- I strongly disagree. Many articles started and start out without sources and with POV language because they are oftentimes created by enthusiasts and fans that want to tell the world about how great this or that is. In many cases, we wouldn't have strong, well written articles if no one had started a bad article first that someone thought worth to improve or that the creator has later returned to fix when they gained more experience. Regards SoWhy 08:22, 9 October 2018 (UTC)
- Yes, this is broadly true. I would normally only go for G11 in draft where there is either sockpuppetry or COI/UPE. Guy (Help!) 08:44, 9 October 2018 (UTC)
- COI/UPE is the root of nearly all G11 drafts. Random 3rd parties don't tend to create SPAM. Legacypac (talk) 08:54, 9 October 2018 (UTC)
- Certainly, articles without sources and issues of promotional or fan POV can become good, that's not really what I'm talking about. I'm more talking about articles like "Bizco provides the best furniture solutions..contact us at" sort of stuff, where it obvious the goal is to spam wikipedia, and not merely an enthusiast writing in a fan perspective; for those articles there is no value in their content because it is better to start afresh, and the editor is very unlikely to be able to rewrite that into something useful (if there is any utility there - the vast majority of companies spammed are not notable). I haven't really found in my experience, or at-least I can't recall any cases of merely an enthusiast or fan creating an article that meets the G11 bar and I'm not going to tag G11 things created by a fan, but most G11able stuff in draftspace is a obviously a COI or UPE editor spamming non-notable companies or similar Galobtter (pingó mió) 13:08, 9 October 2018 (UTC)
- Yes, this is broadly true. I would normally only go for G11 in draft where there is either sockpuppetry or COI/UPE. Guy (Help!) 08:44, 9 October 2018 (UTC)
- I strongly disagree. Many articles started and start out without sources and with POV language because they are oftentimes created by enthusiasts and fans that want to tell the world about how great this or that is. In many cases, we wouldn't have strong, well written articles if no one had started a bad article first that someone thought worth to improve or that the creator has later returned to fix when they gained more experience. Regards SoWhy 08:22, 9 October 2018 (UTC)
- Wasn’t there a consensus against COI/UPE being speediable demonstrated on this page earlier this year? —SmokeyJoe (talk) 09:27, 9 October 2018 (UTC)
- G11 has and still does require the text to be promotional, not the intent. What Legacypac probably means is that in many cases of COI/UPE, the text screams spam as well, thus making them eligible for G11 in general. Regards SoWhy 09:57, 9 October 2018 (UTC)
- I think all speedy deletion criteria (other than copyvios and G7s) should be applied in draft space with a very light touch. Certainly nothing in draft space should be tagged for G11 speedy deletion until the author has been given a chance to improve it (i.e. it's had a {{advert}} or similar on it for a month and the concerns have been explained on the talk page) unless there is evidence of bad faith (not suspicion, not absence of evidence of good faith) and . It is far, far better that we have a little bit of spam in draft space for a short while than we throw away good faith articles that start out spammy. Thryduulf (talk) 12:08, 9 October 2018 (UTC)
- I've tagged several Drafts G11 just today. There is no point trying to get a spammer to rewrite their spam especially when the topic is unlikely to be notable anyway. I don't think anyone is throwing out good faith articles that start out spammy. I see plenty of G11 material just rejected and not CSD'd (on resubmission) and I personally only CSD the most clear cut cases, often after several rejections for being promotional. Legacypac (talk) 21:06, 9 October 2018 (UTC)
- I have tagged a number of drafts for G11 when they are very obviously never going to be accepted (eg: "Tyler-Courtney Jones is a 16-year old YouTube Instagrammer. He likes Ed Sheerhan and wants to grow up to be a singer like him. His songs are going to revolutionise the singer-songwriter industry, and he is absolutely and supremely confident he will be the next big thing. Tyler-Courtney's next shows are scheduled to be the Royston Vasey Youth Club and St Cuthbert's School for Boys Christmas fair") or a seriously bad idea to exist on Wikipedia full-stop (eg: "Crazy Maisie (b. Chardonnay Aimee Chavwick, 29 September 2001) is a political activist and adult actress who has defended the right of women in the porn industry. She has appeared in [big list of wholly inappropriate and NSFW titles]. She signed an exclusive deal with the Sunday Sport so she could pose nude on her 16th birthday" - with no sources outside two tabloid newspapers) ... anyway, you get the idea. These sort of instances are rare. Ritchie333 (talk) (cont) 13:24, 9 October 2018 (UTC)
I've also noticed on quite a few occasions that spammers/UPEs were using draft space to duck autoconfirmed. They would create the article in ten edits, wait four days, and then promptly either copy and paste or move it to mainspace. Draft space is not for the storage of inappropriate material, including blatant ads. Seraphimblade Talk to me 13:35, 9 October 2018 (UTC)
- Seraphimblade, Can they play the same game in User space? ~Kvng (talk) 19:47, 9 October 2018 (UTC)
- Kvng, yes, and I've seen that done too. Fortunately, at least in the cases I saw, a patroller caught on when it got moved to mainspace and tagged it, but still better that it didn't happen at all. Seraphimblade Talk to me 20:59, 9 October 2018 (UTC)
- There are lots of ways a spammer can go to get auto or extended confirmed. Having a non-deleted record of their edits does help provide context when investigating someone for the non-admin among us. Best, Barkeep49 (talk) 00:58, 10 October 2018 (UTC)
- Incubation of spam does not seem to be a compelling reason to use G11 in Draft space. What Legacypac said earlier about the noindex SEO loophole is the only strong argument I've seen here. Is it possible to work with Google to close that loophole in Draft space? Arguments about keeping Draft space tidy don't hold water for me because of G13. AfC has recently implemented a reject process which can kill zombie drafts. ~Kvng (talk) 17:06, 10 October 2018 (UTC)
- I'm probably one of the more prolific wielders of the G11 stick at AFC, I've tagged thousands of blatant WP:Vanispamcruftisement drafts, very few were turned down by the second opinion admins. Quite frankly this idea can only come from someone who has absolutely no clue at all about the meaning of the "Great Firehose Of Ordure (GFOO)" appellation. Roger (Dodger67) (talk) 16:31, 9 October 2018 (UTC)
- The last handful of drafts I tagged as G11 were Draft:Hannah Sneddon, Draft:Kimberly Minatti, Draft:Connor Murray and Draft:Maggie Claydon - all of which were deleted by other administrators. And as discussed on Wikipedia talk:WikiProject Women in Red, I'm currently doing a review of biographies of women to see if any declined drafts can be improved and expanded to the point of acceptance. Ritchie333 (talk) (cont) 16:38, 9 October 2018 (UTC)
- I do delete drafts under G11 but I try to apply a more lenient standard than I would in mainspace. I'd be happy with amending the policy to say something along those lines. Hut 8.5 21:10, 9 October 2018 (UTC)
- I use this also, and in fact I urge that it be used a little more. But as I understand it , the standard for promotionalism in Draft this has always been more permissive. Permissive as it may be, still some drafts are going to be complete advertisements, & suitable for deletion as G11. DGG ( talk ) 05:16, 14 October 2018 (UTC)
Test case
I just started reviewing draft articles as part of AfC, and here are a couple test cases:
The first one is written by a SPA with two edits total; in the queue for 7 weeks; non-notable company & very promotional. Would you guys tag is for G11/A7? The advantage of tagging vs declining would be to take the draft out of the queue so that another AfC reviewer can move onto something else. The second draft is pretty much the same situation. None would survive AfD if moved to main space. I would appreciate feedback on these two items. K.e.coffman (talk) 01:42, 13 October 2018 (UTC)
- HOLLA Group may well be notable. Look at the range of highly credible media coverage and the scale of the downloads they have had. I might approve it with a little more checking.
- AIPES is an industry association with close ties to the EU and some sort of oversight or advisory role in the EU. Not really a commercial promotion situation, though associations do need to promote themselves to some extent. I'd want to see some independant coverage on them and a trim on the organization details before approving the page. It has promise. I would not tag either G11 - there are tons of better candidates for G11 in Draft. Legacypac (talk) 02:37, 13 October 2018 (UTC)
- I agree with K.e.coffman that HOLLA is not notable given lack of articles about it rather than product and my support of WP:INHERITORG as part of WP:NCORP. I would G11 in mainspace and decline in draft. I would not tag AIPES as G11 in either draft or mainspace and can find indicators of notability without too much trouble. If I found in mainsapce I would take a weed wacker to much of the article as not encyclopedic but depending on what a deeper investigation of notability uncovered either mark it as reviewed (or reviewed with a notability tag if I thought it a close call) or tag it with notability and leave it unreviewed. It's very unlikely I would nominate for AfD. Best, Barkeep49 (talk) 02:49, 13 October 2018 (UTC)
- There are preferred WP:ATDs for both of these. The idea that not deleting these clogs the AfC pipeline assumes that when declined, these will be be promptly resubmitted without substantial improvement. Sometimes that happens. Mostly the author either abandons or makes some improvements and not usually immediately. If resubmitted, it is not too much work for subsequent reviewers to look at the diffs and determine whether to quickly reject again or have a deeper look. This is not clogging, this is what we do at AfC, help authors improve their drafts. ~Kvng (talk) 01:24, 14 October 2018 (UTC)
- Neither are hopeless. HOLLA offers the choice of writing the article about the company or the product. A more knowledgable promotional editor would in fact have done it on the product, because in article space software is not susceptible to A7. It would be fairly easy to turn the present article into an article on the product, and the worst promotionalism could be removed. whether it will ever end up an acceptable article depends upon someone who knows and cares working on it. For now, it should get declined. the article on the organization is like many other similar ones: they are very hard to find sources for that pass NCORP, and they are hard to write non-promotionally without being directory entries. Sometimes they are kept at AfD nonetheless if the organization is sufficiently important. It should be declined, with a request for references and to tone down some of the claims of importance. G11 is for worse than these two--there enough of them to make it worthwhile to look at the new submissions, now that it is so easy to do so, and get the very worst out of the pipeline as soon as possible. In terms of the spammers, it can have a good effect to reject them as early as possible. DGG ( talk ) 05:27, 14 October 2018 (UTC)
- I don't think either of those qualifies for speedy deletion in draft space. While both have promotional wording it's not bad enough to avoid giving the author the benefit of the doubt in draft space. The second one is getting very close to the point where I'd be prepared to delete it in mainspace under G11 though, there isn't much text in it which isn't promotionally worded. This doesn't mean they should be accepted or moved to mainspace though. Hut 8.5 10:14, 14 October 2018 (UTC)
There seems to be consensus here that these are not great G11 candidates. I hear from other AfC reviewers that their G11 proposals rarely get kicked back by administrators. So, I'm interested to hear what our CSD administrators would have done if either of these had been tagged for G11. ~Kvng (talk) 14:52, 15 October 2018 (UTC)
- Thank you all for the feedback; I will go ahead and decline the drafts on advertisement grounds. K.e.coffman (talk) 02:15, 16 October 2018 (UTC)
Weird Question About Questioning G11 Tags on Drafts
While we are on the subject of tagging drafts as G11, which I in general support, I have a question. Occasionally, in reviewing AFC, I see a draft that has been tagged as G11, but is still pending AFC review, and, on my review, I disagree with the G11, but think that the draft is not suitable for article space and may or may not ever be ready for article space. I decline the draft, for notability reasons, and either as 'adv' or as 'npov'. So far, so good. But I disagree with the G11. Sometimes I have contested the G11, but have left the G11 tag on the draft, and it usually then goes away, and without a comment that the challenge was denied. Either the reviewing admin doesn't read the talk page, or the reviewing admin has lower standards of G11 than I do. So, in the future, should I continue to contest the speedy deletion using the button for the purpose (and wonder whether the statement is actually read), or should I actually pull the G11 tag? I am very reluctant to pull a CSD tag that was applied in good faith by another reviewer. I think that if a reviewer thinks that a page should be speedy-reviewed, I should let an admin speedy-review the page. But I now don't know if this means that the admin will actually read the talk page challenge, in which case I should challenge on the talk page, or if the admin only looks at the draft page and the tag itself.
So: Should I continue to question what I think are unduly harsh G11s, or should I pull them?
Robert McClenon (talk) 02:07, 24 October 2018 (UTC)
- I just reviewed language around this today as I had not contested a speedy deletion claim in draft space before. The clearest statement of policy I found came from this very page: "
The creator of a page may not remove a speedy deletion tag from it. Only an editor who is not the creator of a page may do so.
" (formating in the original). As I was not the creator of the page I felt I was in the clear to remove the tag and so I did. Best, Barkeep49 (talk) 02:16, 24 October 2018 (UTC)
The Admin will need to also delete the talkpage, so hopefully they read it. I'm in the habit of G11ing spam without declining the page first. It seems more direct/less encouraging. Legacypac (talk) 02:53, 24 October 2018 (UTC)
- Robert, if you believe the draft does not rise to the level of G11 then you should remove the speedy deletion tag from it. ~ GB fan 10:32, 24 October 2018 (UTC)
- If you believe that any page tagged for any speedy deletion criteria does noes not meet the requirements of that criteria then you should always (unless you are the author of the page) remove the tag. This applies regardless of namespace or criteria. Thryduulf (talk) 10:50, 24 October 2018 (UTC)
- If you do remove a speedy tag but any other speedy tag applies you should retag it. Legacypac (talk) 06:01, 28 October 2018 (UTC)
Speedy deletion for circular redirect (WP:SELFRED)
Should this kind or redirect be given its own criteria (example)? A user created some of them only to make the link blue on 2014 Asian Para Games, main article. Hddty. (talk) 07:54, 15 October 2018 (UTC)
- No. These are not speedy-worthy redirects. The links can be removed from the main article but these kinds of articles ("SPORT at EVENT") follow an established pattern and the creating editor probably just wanted to emulate this. Plus, those are redirects with potential, i.e. someone might want to create those sub-articles later. Regards SoWhy 08:11, 15 October 2018 (UTC)
- I believe these should be deleted in order to make the link red (to encourage article creation), but that is a matter for WP:RFD, not for speedy criteria. —Kusma (t·c) 12:46, 17 October 2018 (UTC)
Semi-protected edit request on 24 October 2018
Ttgg66 (talk) 20:27, 24 October 2018 (UTC)
Extended content
|
---|
Use common sense "WP:COMMON" redirects here. For other uses, see WP:COMMON (disambiguation). Shortcuts WP:UCS WP:COMMON WP:SENSE WP:COMMONSENSE Wikipedia has many policies or what many consider "rules". Instead of following every rule, it is acceptable to use common sense as you go about editing. Being too wrapped up in rules can cause loss of perspective, so there are times when it is better to ignore a rule. Even if a contribution "violates" the precise wording of a rule, it might still be a good contribution. Similarly, just because something is not forbidden in a written document, or is even explicitly permitted, doesn't mean it's a good idea in the given situation. Our goal is to improve Wikipedia so that it better informs readers. Being able to articulate "common sense" reasons why a change helps the encyclopedia is good, and editors should not ignore those reasons because they don't include a bunch of policy shortcuts. The principle of the rules—to make Wikipedia and its sister projects thrive—is more important than the letter. Editors must use their best judgment. Why isn't "use common sense" an official policy? It doesn't need to be; as a fundamental principle, it is above any policy.
— René Descartes[10] When advancing a position or justifying an action, base your argument on existing agreements, community foundation issues, and the interests of the encyclopedia, not your own common sense. Exhorting another editor to "just use common sense" is likely to be taken as insulting, for good reasons. If in a particular case you feel that literally following a rule harms the encyclopedia, or that doing something which the rules technically allow degrades it, then instead of telling someone who disagrees to use common sense, just focus on explaining why ignoring the rules will improve Wikipedia in that instance. Be careful about citing this principle too aggressively. While it's quite acceptable to explain your own actions by saying, "it seemed like common sense to me", you should be careful not to imply that other editors are lacking in common sense, which may be seen as uncivil. Wikipedians come from diverse ethnic, religious, political, cultural and ideological backgrounds and have vastly different perceptions. Other editors are likely to ascribe very different meanings and values to words and concepts than you, so try to state your arguments as fully as possible. Citing concrete policies and guidelines is likely to be more effective than simply citing "common sense" and leaving it at that. |
Not done This isn't an edit request, it's a text dump from WP:COMMON. Hut 8.5 20:33, 24 October 2018 (UTC)
Semi-protected edit request on 27 October 2018
Under the fourth paragraph in the "Introduction to criteria" section, change "You can copy and paste such warnings to the talk pages of the creators and major contributors, choose from others listed at Category:CSD warning templates, or place the unified warning template, {{subst:CSD-warn|csd|Page name}}
, which allows you to tailor your warning under any particular criterion by replacing csd
with the associated criterion abbreviation (e.g. g4, a7)." to "You can copy and paste such warnings to the talk pages of the creators and major contributors or choose from others listed at Category:CSD warning templates."
I think this change is a good idea because I noticed the CSD-warn template has been deleted as an "unused template." Therefore, it should not be mentioned here anymore. 24.5.8.227 (talk) 00:43, 28 October 2018 (UTC)
- This request seems in good faith, but I'm bothered that a substable template was speedy-deleted because it is not in-use. Does anyone watching this page wish to dispute that deletion either with RHaworth or at WP:DRV? --Izno (talk) 00:57, 28 October 2018 (UTC)
- Courtesy Ping: @RHaworth:. Tazerdadog (talk) 05:30, 28 October 2018 (UTC)
Not done: the template has been restored. feminist (talk) 18:27, 1 November 2018 (UTC)
Proposal to merge db-blankdraft into G13
Now that pretty much all drafts are under the purview of AfC, it seems unnecessary to have {{db-blankdraft}} separated out into its own category with different deletion criteria from what we're using on draftspace drafts. I think it would be better if we eliminated {{db-blankdraft}} and then add a new criteria under G13 allowing any draft, userspace or draftspace, containing only default placeholder text to be deleted after six months of no edits. That would bring it in line with how AfC drafts are currently being handled. --Nathan2055talk - contribs 07:21, 2 November 2018 (UTC)
- What would be the benefit? When blank or near blank Draft space pages come up unedited 6 months we G13 them anyway. In userspace we use "blank draft" and in Draft space G2 test edit to delete blank submissions. Perhaps we should extend Blank Draft over Draft space in Twinkle so we can more accurately tag the blank pages. Legacypac (talk) 08:00, 2 November 2018 (UTC)
- @Legacypac: Right now, db-blankdraft requires a full year without any edits from the page creator, while G13 only requires six months without edits to the page. The only policy difference I'm proposing is changing the db-blankdraft requirements to the same "six months without page edits" we're using with G13 and extending it over draftspace as well. Nathan2055talk - contribs 08:05, 2 November 2018 (UTC)
For reference, here's what I'm proposing as a rewritten G13:
This applies to any pages in the draft namespace, any pages in userspace with the {{AFC submission}} template that are not currently pending review, and any drafts in either namespace with no content except the placeholder text generated by the article wizard that have not been edited (excluding bot edits) in over six months. Redirects are excluded from G13 deletion. Drafts deleted in this manner may be restored upon request by following the procedure at Wikipedia:Requests for undeletion/G13.
All it really is is consolidating and slightly generalizing existing deletion policies to make it easier to eliminate pure, unnecessary trash. Nathan2055talk - contribs 08:14, 2 November 2018 (UTC)
- Support totally logical. So we would depreciate the G6 blank draft criteria then. Legacypac (talk) 08:27, 2 November 2018 (UTC)
- Whatever "db-blankdraft" is, it's not G6. (Except for the folks who consider G6 to be "anything I can delete without anyone except maybe some random influenceless newbie raising a fuss" or "any new speedy deletion criterion I can sneak in without gaining consensus for a new speedy deletion criterion".) I also agree that this is better than mistagging such pages as test edits. —Cryptic 12:05, 2 November 2018 (UTC)
- On a bit more reflection, I'm more in favor of generalizing A3 to apply to most non-talk namespaces. We'd have to identify a few classes of pages to exclude - categories, sandboxes, and galleries of (free) images in userspace spring to mind. I still support this proposal, as written, as a second choice. —Cryptic 13:08, 2 November 2018 (UTC)
- Also needing to be excluded would be redirects and soft redirects, files and file description pages (especially for files hosted at Commons), templates (especially ones that don't display anything much/are just a framework + a transcluded documentation page), user and user talk pages. I don't think this would be an improvement. Thryduulf (talk) 15:31, 2 November 2018 (UTC)
- On a bit more reflection, I'm more in favor of generalizing A3 to apply to most non-talk namespaces. We'd have to identify a few classes of pages to exclude - categories, sandboxes, and galleries of (free) images in userspace spring to mind. I still support this proposal, as written, as a second choice. —Cryptic 13:08, 2 November 2018 (UTC)
- Support. G6 is by far the worst CSD criterion we have for misuse per Cryptic and anything that moves us a step closer to actually make it meet the standards required of new criteria is a good thing. Moving one aspect of it to a different criteria where it fits better is an example of such a step. Thryduulf (talk) 12:39, 2 November 2018 (UTC)
- Support - This is a clear improvement over the status quo. Tazerdadog (talk) 17:07, 2 November 2018 (UTC)
- Support per Thryduulf. Word for word. ~ Amory (u • t • c) 00:52, 3 November 2018 (UTC)
- Support Makes sense, less confusing funplussmart (talk) 15:58, 3 November 2018 (UTC)
- Support logical. Cabayi (talk) 16:02, 3 November 2018 (UTC)
- Q Would this mean blank drafts would wait 6 months before being deleted? I assume I'm missing something... ——SerialNumber54129 16:03, 3 November 2018 (UTC)
- Yes. In draftspace and for userspace drafts with AFC templates, that's no different from the status quo. For userspace drafts without AFC templates, this proposal shortens it from sitting for a year (or longer, if the author edits other pages; or shorter, if you can con an admin into deleting it immediately). —Cryptic 16:14, 3 November 2018 (UTC)
(Ec) :I am in favor of reducing the wait from one year after the editor has been active" (a silly long time) to "6 months after the userspace blank draft was created." For Draft space blank submissions to AfC I see no reason to retain these test edits for more than a few minutes. The deleted page can always be easily recreated but almost never are. I CSD hundreds of blank pages submitted to AfC every few months to reduce the G13 burden and they never come back. Legacypac (talk) 16:20, 3 November 2018 (UTC)
Redirects in the File: namespace G6 → R4
Criterion G6 is overloaded with many different things all lumped together as "uncontroversial maintenance" and is the most frequently abused of all criteria. It would never be approved if proposed as is today. The best way to solve this, in my opinion, is to unbundle the various different reasons into separate criteria that are individually objective. I'm not proposing to do this all at once, but to work on it step-by-step so that objections to one aspect don't derail the whole thing.
One aspect of G6 stands out as being a particularly poor fit with the rest: "Deleting redirects in the "File:" namespace with the same name as a file or redirect at Commons, provided the redirect on Wikipedia has no file links (unless the links are obviously intended for the file or redirect at Commons)." Accordingly I propose to move this criterion, without any changes, from G6 to a new R4 for these reasons:
- It deals only with redirects, and is thus where someone will look for it
- The general footer to the R criteria (don't speedy delete redirects with significant history, use RfD for redirects that don't meet the criteria) apply to these redirects equally with others
- It contains requirements that are significantly different to other things deleted using G6
- This isn't really "maintenance" in the same sense as other aspects of G6 (e.g. pages created in error/in the wrong place, etc)
- Deletion summaries will become more useful.
This does not change what can be speedy deleted, just under which criterion is gets speedy deleted. Thryduulf (talk) 12:43, 5 November 2018 (UTC)
- Support - This appears to be a clean improvement. How often are redirects deleted under this particular provision of G6? Tazerdadog (talk) 15:02, 5 November 2018 (UTC)
- I don't know, but we see several that possibly could be come through RfD. Thryduulf (talk) 17:16, 5 November 2018 (UTC)
- Just a bit of history here: Back in 2015, there was (or is) a category that listed all of the pages on Wikipedia in the "File:" namespace that had the same name as a page on Wikimedia Commons; the category contained a few hundred or thousand pages. After consensus was established around that time for creating a WP:CSD criterion for deleting such pages that are redirects, I created {{Db-redircom}}. Afterwards, that category was essentially emptied by a handful of editors using {{Db-redircom}}. However, as of present day, I don’t think pages in the "File:" namespace on Wikipedia with the same name as a page on Wikimedia Commons get created that often ... most likely as a result of the 2015 clearing of the aforementioned backlogged category. Steel1943 (talk) 15:44, 6 November 2018 (UTC)
- Support not an area I work but this appears more logical Legacypac (talk) 20:30, 5 November 2018 (UTC)
- Support. I knew there was a CSD for this, but I was looking in the wrong areas and couldn't find it until it was pointed out that this falls under G6. Hopefully moving it over will be more intuitive to prevent this in the future. -- Tavix (talk) 15:14, 6 November 2018 (UTC)
- @Tavix: would a note in the Files: section footer along the lines of "For redirects in the file namespace with the same name as files on Commons, see criterion R4" be useful do you think? Thryduulf (talk) 02:17, 7 November 2018 (UTC)
- I certainly would not be opposed to such a note. To clarify, do you want to add it to the notes at WP:FCSD? -- Tavix (talk) 14:23, 7 November 2018 (UTC)
- I was thinking of placing it at the end of the list of criteria, but if others prefer the top then I'm perfectly happy with that. Thryduulf (talk) 15:29, 7 November 2018 (UTC)
- I certainly would not be opposed to such a note. To clarify, do you want to add it to the notes at WP:FCSD? -- Tavix (talk) 14:23, 7 November 2018 (UTC)
- @Tavix: would a note in the Files: section footer along the lines of "For redirects in the file namespace with the same name as files on Commons, see criterion R4" be useful do you think? Thryduulf (talk) 02:17, 7 November 2018 (UTC)
- Support. Whatever gets the concept behind {{Db-redircom}} more exposure. (Disclaimer: the diff that Tavix mentioned in the previous comment was an edit I made.) Steel1943 (talk) 15:30, 6 November 2018 (UTC)
Neutral.I don't think unbundling is necessary - this is uncontroversial maintenance, caused by incremental software changes over nearly two decades. However, moving this into the redirects section of CSD does sound like a good idea. Deryck C. 16:25, 7 November 2018 (UTC)- I think that is the point - to be in the Redirects section it has to be split from G6 and given an R designation. I don't know how often this is used. There was mention of a category tracking these cases. Does that still exist? Do we track how many times each CSD is used? Legacypac (talk) 22:24, 7 November 2018 (UTC)
- @Deryck Chan: I'm not disputing it is "uncontroversial maintenance", I'm saying it's a different sort of maintenance to the examples given, applies to a narrower set of pages and very has different requirements to all other aspects of G6. G6 is not a dumping ground for everything that could be considered maintenance of some description - otherwise we might as well fold in G8, A3, F2, F10, C1 and U2. Thryduulf (talk) 18:08, 13 November 2018 (UTC)
- Changing to weak support. I don't mind which section and what serial number we put this type of deletion under, but I'm not massively excited about unbundling either. What I don't want to see (in the foreseeable future?) is that we deprecate away G6 altogether. Deryck C. 19:07, 13 November 2018 (UTC)
- Personally I would like to see G6 completely deprecated as that's the only way I forsee the rampant abuse of it by some administrators will stop. Every aspect of it that is required would be transferred to a new, objective and focused criterion - speedy deletion is not and never has been intended to be a routine method of deletion - it is a narrow set of exceptions to the need to get consensus for every deletion, limited to those situations where consensus will always be in favour, not just what one admin thinks people probably wont object too strongly too. This is all independent of this proposal though. Thryduulf (talk) 23:51, 13 November 2018 (UTC)
- Changing to weak support. I don't mind which section and what serial number we put this type of deletion under, but I'm not massively excited about unbundling either. What I don't want to see (in the foreseeable future?) is that we deprecate away G6 altogether. Deryck C. 19:07, 13 November 2018 (UTC)
- Support. Why not. — pythoncoder (talk | contribs) 01:59, 14 November 2018 (UTC)
- Support per nom. ---- Patar knight - chat/contributions 23:04, 15 November 2018 (UTC)
- Support; this changes nothing about our practice and thus will have no practical effect whatsoever, so the only real question is "what will users find to be simpler". Putting it with redirects is definitely simpler than keeping it at G6. Nyttend (talk) 20:37, 18 November 2018 (UTC)
Proposal/RfC - Extend WP:U5 to the draftspace
I am going to propose that WP:U5 gets extended to the draftspace. This is because the draftspace is being abused in a way that there are so many drafts being found daily which are basically WP:NOTWEBHOST. It is mainly point 5 of WP:NOTWEBHOST which I am seeing in loads of drafts. Rule 5 of WP:NOTWEBHOST is "Content for projects unrelated to Wikipedia. Do not store material unrelated to Wikipedia, including in userspace." and I am seeing that new users are using the draftspace in a way so that WP:U5 can be escaped because WP:U5 does not apply to the draftspace at the moment. If this is implemented, there will be less drafts coming to WP:MfD daily that could actually do with being speedily deleted per WP:U5.
My new proposed wording for WP:U5 is:
Pages in userspace or draftspace consisting of writings, information, discussions, and/or activities not closely related to Wikipedia's goals, where the owner has made few or no edits outside of user pages and drafts, with the exception of plausible drafts and pages adhering to Wikipedia:User pages#What may I have in my user pages?.
Pkbwcgs (talk) 17:21, 12 November 2018 (UTC)
- Support I also find these Drafts at AfC and otherwise regularly. I'm not sure that new accounts are researching our WP:NOTAWEBHOST policies and choosing Draft space over userspace to avoid U5 but we do channel new users toward Draftspace and a certian portion of these users post U5 type material. We need the ability to CSD this junk without wasting time at MFD even more in Draft then userspace because it often is submitted to AfC, and sometimes multiple times. Legacypac (talk) 17:31, 12 November 2018 (UTC)
- Comment U numbers only apply to userspace. I suggest deprecating U5 and replacing it with a G number, perhaps G15, worded to include userspace and draftspace as proposed. Purely to avoid confusion. — Frayæ (Talk/Spjall) 17:55, 12 November 2018 (UTC)
- Need examples - This proposal is based on the idea that MfD is being bogged down by drafts that could be speedied under U5 if it applied to drafts. To support this, we need to see examples a number of recent drafts that would be speedied under the current proposal but cannot be under any existing criteria. @Pkbwcgs: can you give some examples of these "loads of drafts"? A2soup (talk) 17:58, 12 November 2018 (UTC)
- @A2soup: Things like Draft:Take care of your beauty, Draft:How To Pass Nebosh IGC Exam in First Attempt?,
Draft:How ICT has an effect on Societyand Draft:How I do control my thinking would be examples of drafts which would meet U5 if it were to be extended to the draftspace as they are not related to Wikipedia. Pkbwcgs (talk) 18:04, 12 November 2018 (UTC)- Right now we have to use G11 as a catch all to deal with instruction manuals, product specifications, team rosters, and all sorts of assorted non-articles that could fit this criteria. Anything that might be fictional can potentially be db-hoax tagged but could fit this criteria better. Occasionally someone posts something that is not an advert or hoax but certainly isn't ever going to be an article and then it is just left to get swept away by G13 in six months time. This new criteria would make it more transparent and easier to deal with the material we should not be hosting. — Frayæ (Talk/Spjall) 18:07, 12 November 2018 (UTC)
- @A2soup: Things like Draft:Take care of your beauty, Draft:How To Pass Nebosh IGC Exam in First Attempt?,
- Support I have nominated a few of these drafts myself. Deprecate U5 and replace it with G15 as per Frayae. CoolSkittle (talk) 18:15, 12 November 2018 (UTC)
- Commment indeed G15. Most of this U5 stuff can be speedied out of Article space on some other A? Criteria but Wikipedia, Template and other spaces can be used for webhosting too. The main issue is Draft space though because we channel new accts there. Legacypac (talk) 18:19, 12 November 2018 (UTC)
- @Legacypac: It is very rare to see U5-related stuff in the mainspace because a user has to be autoconfirmed to create a page in the mainspace on Wikipedia. Pkbwcgs (talk) 18:34, 12 November 2018 (UTC)
- I am sure G14 doesn't exist yet? Pkbwcgs (talk) 18:32, 12 November 2018 (UTC)
- G14 may not exist as enacted policy, but there are so many proposals for a G14 with various different attributes in the archives that I feel it would be wiser and less confusing to go one number up and match U5 with G15. — Frayæ (Talk/Spjall) 18:39, 12 November 2018 (UTC)
- I am sure G14 doesn't exist yet? Pkbwcgs (talk) 18:32, 12 November 2018 (UTC)
- @Legacypac: It is very rare to see U5-related stuff in the mainspace because a user has to be autoconfirmed to create a page in the mainspace on Wikipedia. Pkbwcgs (talk) 18:34, 12 November 2018 (UTC)
- Oppose I suspect this will be used to delete drafts which are just very bad, instead of just those which are NOTWEBHOST violations. Some of the examples cited above are original essays or violations of WP:NOT#HOWTO. In other words they are attempts to write Wikipedia articles by people who just don't know how Wikipedia works. That doesn't make them WP:NOT#WEBHOST violations, unless they've been hanging around for long enough (in which case G13 would apply). Hut 8.5 18:50, 12 November 2018 (UTC)
- Oppose. Solution in search of a problem. MFD does not seem overrun by such drafts with the examples cited having been created weeks apart. Also, what Hut 8.5 said, the potential for abuse seems far too high because new users might very well write bad drafts that get better later. I also fail to see why G13 can't handle them. Where is the pressing need to remove them asap? Regards SoWhy 18:56, 12 November 2018 (UTC)
- SoWhy have you participated in more than 25 MfDs yet? Why are you commenting on an area you have little experience with?
- Hut - Any CSD can be abused, all we are talking about is location of the unsuitable material. If it is U5 in userspace why should it be ok in Draftspace which is a more collabertive environment. Legacypac (talk) 19:26, 12 November 2018 (UTC)
- Anyone can see that there are not that many MFDs. One does not have to participate in them to do so. SoWhy 19:31, 12 November 2018 (UTC)
- Sure, any CSD can be abused, but if a CSD is particularly prone to abuse than that's a reason not to have it. I'm not a particular fan of U5 in userspace, to be honest, but in draft space I think there's a higher chance that the author was at least trying to write an article. Hut 8.5 20:28, 12 November 2018 (UTC)
- @Hut 8.5: Is a WP:NOTWEBHOST violation okay in the draftspace? Why do we have WP:U5 in the userspace but not in the draftspace? The draftspace is easily abused for WP:NOTWEBHOST. I have a question. If I see a personal profile of a user in the draftspace then what should I do? We can't leave these sorts of stuff in the draftspace. Pkbwcgs (talk) 20:43, 12 November 2018 (UTC)
- You can get inappropriate material in draft space deleted at WP:MFD if it does not qualify for speedy deletion. Speedy deletion criteria are only good for narrow cases where people agree that pages meeting the criterion should be deleted. This suggestion shows a strong likelihood that it will be used to delete content which doesn't actually fall foul of WP:NOTWEBHOST, which makes it a bad idea. NOTWEBHOST doesn't apply to attempts to write encyclopedia articles, at least not unless abandoned, and even in this discussion there are suggestions that this criterion will be used to delete pages of this type. Hut 8.5 21:40, 12 November 2018 (UTC)
- @Hut 8.5: Thanks for your reply. Yes it is clear that NOTWEBHOST doesn't apply for attempts to write an article. That is certain. However, WP:MFD is becoming flooded when taking inappropriate material there and most of it is WP:NOTWEBHOST stuff which can be eliminated by extending WP:U5 to the draftspace. Pkbwcgs (talk) 21:47, 12 November 2018 (UTC)
- I don't think it's being "flooded" with this stuff at all. There are plenty of people trying to get drafts deleted for being essays, how-to guides, dictionary definitions, etc but none of those equate to NOTWEBHOST. So either the criterion will be useless for those pages or it will be used to bring a criterion of "inappropriate draft" in through the back door. The first option makes it useless and the second one would be actively harmful. Bear in mind that drafts will be deleted after six months unless someone is working on them anyway, there's no particular need to bring them to MfD in the first place most of the time. Hut 8.5 21:56, 12 November 2018 (UTC)
- @Hut 8.5: Thanks for your reply. Yes it is clear that NOTWEBHOST doesn't apply for attempts to write an article. That is certain. However, WP:MFD is becoming flooded when taking inappropriate material there and most of it is WP:NOTWEBHOST stuff which can be eliminated by extending WP:U5 to the draftspace. Pkbwcgs (talk) 21:47, 12 November 2018 (UTC)
- You can get inappropriate material in draft space deleted at WP:MFD if it does not qualify for speedy deletion. Speedy deletion criteria are only good for narrow cases where people agree that pages meeting the criterion should be deleted. This suggestion shows a strong likelihood that it will be used to delete content which doesn't actually fall foul of WP:NOTWEBHOST, which makes it a bad idea. NOTWEBHOST doesn't apply to attempts to write encyclopedia articles, at least not unless abandoned, and even in this discussion there are suggestions that this criterion will be used to delete pages of this type. Hut 8.5 21:40, 12 November 2018 (UTC)
- @Hut 8.5: Is a WP:NOTWEBHOST violation okay in the draftspace? Why do we have WP:U5 in the userspace but not in the draftspace? The draftspace is easily abused for WP:NOTWEBHOST. I have a question. If I see a personal profile of a user in the draftspace then what should I do? We can't leave these sorts of stuff in the draftspace. Pkbwcgs (talk) 20:43, 12 November 2018 (UTC)
- @Hut 8.5: If a user writes about personal stuff in the draftspace then what speedy deletion criterion should be used? U5 is only applicable to the userspace. Pkbwcgs (talk) 19:07, 12 November 2018 (UTC)
- WP:UP#NOT says that personal opinions and "Extensive writings and material on topics having virtually no chance whatsoever of being directly useful to the project, its community, or an encyclopedia article" are writings, information, discussions, and activities not closely related to Wikipedia's goals which is what WP:U5 is about and I see those things in the draftspace. Pkbwcgs (talk) 19:11, 12 November 2018 (UTC)
- You're assuming that just because something is inappropriate or deletable then there must be a speedy deletion criterion for it. It doesn't work that way. Hut 8.5 20:28, 12 November 2018 (UTC)
- WP:UP#NOT says that personal opinions and "Extensive writings and material on topics having virtually no chance whatsoever of being directly useful to the project, its community, or an encyclopedia article" are writings, information, discussions, and activities not closely related to Wikipedia's goals which is what WP:U5 is about and I see those things in the draftspace. Pkbwcgs (talk) 19:11, 12 November 2018 (UTC)
- @Hut 8.5: If a user writes about personal stuff in the draftspace then what speedy deletion criterion should be used? U5 is only applicable to the userspace. Pkbwcgs (talk) 19:07, 12 November 2018 (UTC)
- Comment Draft:How ICT has an effect on Society, an example given above, was declined at AFC and the author invited to resubmit. Surely in this circumstance speedy deletion would be out of the question. Thincat (talk) 19:46, 12 November 2018 (UTC)
- Oppose per Hut 8.5. -- Tavix (talk) 21:57, 12 November 2018 (UTC)
- Oppose per Hut 8.5.--Bbb23 (talk) 22:02, 12 November 2018 (UTC)
- This is bound to be unsuccessful like every single proposal I make is. I am pretty useless at making proposals and at everything. Pkbwcgs (talk) 22:03, 12 November 2018 (UTC)
- Oppose. Complete overlap with G13. G13 works, with good pacing of notifications and ease of REFUND. No need to make speculative negative judgements on thin new unsubmitted drafts. If a draft does not meet any G* criterion, the six month G13 process suffices. NB. —SmokeyJoe (talk) 22:26, 12 November 2018 (UTC)
- G13 is for abandoned pages. U5 is for webhost inappropriate pages. You don't need to speculate on the pages this will apply too, they are clearly not appropriate. Legacypac (talk) 22:53, 12 November 2018 (UTC)
- I have not seen any draftspace NOTWEBHOST violations that are so bad that they can't be left to the G13 process. I have seen draftspace NOTWEBHOST nominations at MfD where the nominator is making quick assumptions about the limited content and an psychoanalysis of the author. A mistake in these assumptions is more damaging to the project than leaving a silly NOTWEBHOST draft violation to expire and get deleted per G13. We created G13 with this exact sort of thing in mind. --SmokeyJoe (talk) 06:33, 13 November 2018 (UTC)
- G13 is for abandoned pages. U5 is for webhost inappropriate pages. You don't need to speculate on the pages this will apply too, they are clearly not appropriate. Legacypac (talk) 22:53, 12 November 2018 (UTC)
- Oppose - Unnecessary. Truly problematic examples are covered sufficiently by other deletion criteria (CSD or otherwise). — Rhododendrites talk \\ 04:08, 13 November 2018 (UTC)
- Oppose. I agree with the spirit behind this, but WP:NOTWEBHOST is way too broad of a speedy deletion criteria, especially for a process that receives a lot of poorly formatted drafts from people who haven't yet gotten the hang of editing. As others have said, this will almost certainly just turn into an "eject drafts I don't like" button. I'm always going to be in favor of retaining drafts unless they are either obvious corpspam (G11) or it's abundantly clear they are no longer being improved (G13). Other than those two criteria, I'd rather draft deletions go through MfD. Nathan2055talk - contribs 04:11, 13 November 2018 (UTC)
- Support per Wikipedia:Miscellany for deletion/Draft:When can you claim that you’ve been in a country or state?, and other supporting comments here by the editors who actually work in the draft space. I also support promoting this criterion to a "general" criterion. Ivanvector (Talk/Edits) 13:44, 13 November 2018 (UTC)
- Oppose per Hut 8.5, SmokeyJoe and Nathan2055. Thryduulf (talk) 18:11, 13 November 2018 (UTC)
- Support per nom and Legacypac. PrussianOwl (talk) 21:59, 13 November 2018 (UTC)
- All the people supporting "per Hut" fail to realize we almost never see Hut around AfC or MfD so it's no skin off their back to make those who actually work in these areas do more busy work on NOTAWEBHOST violations. In fact, the regulars at AfC and MfD are mainly supporting based on experience and the Opposes are mostly editors without significant contributions to the AfC and MfD. Legacypac (talk) 22:09, 13 November 2018 (UTC)
- You say this as though the maintenance of draftspace (or interpretations thereof) is all that's at stake; as though it is separate from the value and usefulness of draftspace itself or the people who actually use it. I'd say that the opinions of people who use, want to use, or coach people through using draftspace (regardless of AfC), are at least as valuable. Nobody is obliged to engage in any particular maintenance task. As this is not articlespace and nobody who isn't looking for them will ever see the overwhelming majority of these pages, the benefit to be gained from deletion is considerably less, but the extent to which editors' experience is affected is the same. So having hoops in place that must be jumped through to delete something doesn't strike me as a bad thing, apart from the most obvious instances. A central problem to me is not whether or not the most egregious examples are pages that should be kept, but about a fundamental disagreement about what constitutes NOTWEBHOST. — Rhododendrites talk \\ 23:36, 13 November 2018 (UTC)
- (edit conflict) @Legacypac: the number of NOTWEBHOST (a vague and subjective collection criterion that new editors cannot be expected to know about) violations is not relevant here, the relevant factor is the number of good faith pages that are not violations that will get swept away and the number of newbies who will be BITTEN and never return. Editor retention is already a problem, if the price of not making that worse is more work for some editors then that is a price worth paying ten times over. That you have failed to convince those of us who are not regulars at MfD that this is actually a problem that needs solving (let alone that this is the way to solve it) should tell you something. Thryduulf (talk) 23:42, 13 November 2018 (UTC)
- This is called an ad hominem fallacy--whether we do work there is irrelevant to the question of the work that should be done there. --Izno (talk) 02:01, 14 November 2018 (UTC)
- Oppose: Where the NOTWEBHOST is a critical issue, we have better CSD to apply. Where it is not a critical issue, G13 is sufficient for draft space. --Izno (talk) 02:04, 14 November 2018 (UTC)
- No confidence that taggers - and admins, for that matter - will prove any better at identifying material plausibly intended as drafts in draftspace than they have in userspace. —Cryptic 04:50, 14 November 2018 (UTC)
- @Pkbwcgs and Legacypac: I've just had a look through every current WP:MFD listing. There are 33 pages in draft space, exactly 1 of which could be speedily deleted based on WP:NOTWEBHOST: Draft:Assignment Two(BF). This is evidence that this criterion is not needed. As Hut 8.5 notes above, there are many draft-space being nominated at MfD for other reasons - for example being essays, duplicates, covering non-notable subjects, etc. but these would not fall within the scope of this criterion so it would be either unused or abused. Of those others nominated, only around three quarters (at most) have no opposition to deletion - which is much too low for a speedy criterion which needs to be around 99% or greater, and at least half of those with no opposition are being deleted for subjective reasons that are unsuitable for speedy deletion. Thryduulf (talk) 12:44, 14 November 2018 (UTC)
- @Thryduulf and Hut 8.5: I understand that you are against this proposed G15 being implemented. Your arguments apply equally to the existing U5 criteria, and could be applied equally to deprecating U5 without a replacement. What do you say to this? — Frayæ (Talk/Spjall) 14:35, 14 November 2018 (UTC)
- I'm not ideologically opposed to that, but I'd want to look at how often it is currently being used and what it is being used to delete before offering a firm view. Thryduulf (talk) 14:44, 14 November 2018 (UTC)
- (edit conflict) You didn't ask me, but in general I support deprecating U5 if it is not extended to the draft space. Before we had a draft: namespace it made sense that material completely unrelated to Wikipedia posted in an editor's userspace was CSDable, but now that users are just as likely to post this sort of material as a draft, the CSD restriction to userspace strikes me as ridiculous bureaucracy. If I post a plot guide to my D&D campaign at User:PEIsquirrel/The Mystical Age Of The One Pine Tree In The Yard With The Good Nuts U5 can apply, but if I post the same content to Draft:The Great War Of The Glorious Chipmunks And The Vile Felines it has to go to MfD, and I find that distinction silly. Either NOTWEBHOST violations are speediable everywhere, or they are not speediable anywhere. Ivanvector (Talk/Edits) 14:50, 14 November 2018 (UTC)
- I completely agree with Ivan. There is a general opinion here that G15/U5 should not be used on drafts. Logically this would apply to all drafts or no drafts regardless of namespace as Ivan explains. — Frayæ (Talk/Spjall) 15:24, 14 November 2018 (UTC)
- However, some of the opposition to this proposal was based on the fact that we already have a criterion (G13) that will take care of these drafts and that those in favor have imho not demonstrated why these drafts should go to MFD instead of waiting for them to become eligible for G13. Regards SoWhy 15:44, 14 November 2018 (UTC)
- @SoWhy: Who wants to wait for six months to get rid of loads of drafts that are basically tons of junk? Basically, what G13 is doing is creating more work for admins as they have to delete tons of drafts everyday that meet G13 and the majority of those drafts are nothing but junk. Some of these are NOTWEBHOST violatinos, some of these are how-to guides, some of these are spam and I even saw a homework assignment in the loads of piece of junk in AfC. Yes, there are very interesting and good articles created via AfC which is why it is a very useful process. However, it is so sad to see that loads of junk is in the draftspace as well. If you look at Category:AfC submissions declined as jokes, at least 90% of these can be speedy deleted without waiting six months. Here is a classic example of what junk is. I tagged for speedy deletion as a blatant hoax. I also see Category:AfC submissions declined as a test which is stuff that has zero chance of improvement. Basically, tons of useless rubbish that can be deleted but is G2 valid for the draftspace? One draft which I tagged as G2 has been deleted but I remember it was absolutely blank when I tagged it for deletion. However, does this mean the others can be deleted? If U5 is not going to the draftspace then we need a general criterion for deletion of junk in the draftspace. Look, over 3,000 junk adverts, around 60 dictionary definitions which don't stand a chance because Wikipedia is not a dictionary and around 90 drafts which are blank and hopeless and all of these have to wait six months to be deleted? However, I oppose the deprecation of U5 because I still tag web hosts in the userspace for speedy deletion and new users will use the userspace for personal stuff and web hosts which has no place on Wikipedia. Pkbwcgs (talk) 16:18, 14 November 2018 (UTC)
- I fail to understand your "creating more work for admins" argument. Whether a page is deleted under G13 or under your proposed G15, the work needed to delete the page is the same. Indeed, the workload is probably higher if the admin has to evaluate the draft against a complex set of criteria for "junk" as you call it instead of just checking whether it meets the requirements for G13. However, saying "who wants to wait?" does not really answer the question "why can't we wait?". As has been pointed out above, the problem is not that people are in favor of keeping "junk" but that "junk" or NOTWEBHOST or anything like that is too vague to serve as a useful criterion because we always have to take into account the potential for abuse. Thryduulf has summarized it pretty well above. Regards SoWhy 16:41, 14 November 2018 (UTC)
- I still don't understand this. Why should junk be allowed in the draftspace but not anywhere else? Pkbwcgs (talk) 16:52, 14 November 2018 (UTC)
- There is no "junk" speedy deletion criterion. That's why you want to create one, isn't it? But as pointed out multiple times, "junk" is highly subjective and the whole point of draftspace is to allow new editors to work on stuff that some might see as "junk" to the point that useful articles are created from this "junk". If they lose interest, those drafts will already be cleaned up by G13. But if just 1% of drafts deleted under such a criterion were actually viable articles and these editors leave the project as a consequence, this is far more harmful to the project as a whole. Regards SoWhy 17:18, 14 November 2018 (UTC)
- Never in the time I worked in the draftspace have I seen someone successfully create a mainspace article from junk. If a draft looks proper then it is more likely to go to the mainspace. A piece of junk that will not be ever improved shouldn't have to wait six months and what users tend to is to submit the same draft over and over again without any difference so that it won't get caught on the G13 trap. Pkbwcgs (talk) 18:17, 14 November 2018 (UTC)
- The tendentious resubmission without improvement that you describe usually leads to deletion at MfD. Why shouldn't a piece of junk wait six months? Drafts are not indexed by search engines and are impossible to find unless you're looking for them, deletion doesn't free up any Wikimedia server space (the data is still retained). There is no benefit to the project of deleting drafts, except in the cases where they pose legal issues, which are already covered by other criteria. If even one draft that would have been improved is deleted or even one newbie that would have become a productive editor is driven away, then your proposal will be a net negative to the project. A2soup (talk) 19:02, 14 November 2018 (UTC)
- What you said about new users improving a "junk" draft is extremely unlikely based on what I have seen so far in the draftspace. Pkbwcgs (talk) 19:22, 14 November 2018 (UTC)
- The tendentious resubmission without improvement that you describe usually leads to deletion at MfD. Why shouldn't a piece of junk wait six months? Drafts are not indexed by search engines and are impossible to find unless you're looking for them, deletion doesn't free up any Wikimedia server space (the data is still retained). There is no benefit to the project of deleting drafts, except in the cases where they pose legal issues, which are already covered by other criteria. If even one draft that would have been improved is deleted or even one newbie that would have become a productive editor is driven away, then your proposal will be a net negative to the project. A2soup (talk) 19:02, 14 November 2018 (UTC)
- Never in the time I worked in the draftspace have I seen someone successfully create a mainspace article from junk. If a draft looks proper then it is more likely to go to the mainspace. A piece of junk that will not be ever improved shouldn't have to wait six months and what users tend to is to submit the same draft over and over again without any difference so that it won't get caught on the G13 trap. Pkbwcgs (talk) 18:17, 14 November 2018 (UTC)
- There is no "junk" speedy deletion criterion. That's why you want to create one, isn't it? But as pointed out multiple times, "junk" is highly subjective and the whole point of draftspace is to allow new editors to work on stuff that some might see as "junk" to the point that useful articles are created from this "junk". If they lose interest, those drafts will already be cleaned up by G13. But if just 1% of drafts deleted under such a criterion were actually viable articles and these editors leave the project as a consequence, this is far more harmful to the project as a whole. Regards SoWhy 17:18, 14 November 2018 (UTC)
- I still don't understand this. Why should junk be allowed in the draftspace but not anywhere else? Pkbwcgs (talk) 16:52, 14 November 2018 (UTC)
- I fail to understand your "creating more work for admins" argument. Whether a page is deleted under G13 or under your proposed G15, the work needed to delete the page is the same. Indeed, the workload is probably higher if the admin has to evaluate the draft against a complex set of criteria for "junk" as you call it instead of just checking whether it meets the requirements for G13. However, saying "who wants to wait?" does not really answer the question "why can't we wait?". As has been pointed out above, the problem is not that people are in favor of keeping "junk" but that "junk" or NOTWEBHOST or anything like that is too vague to serve as a useful criterion because we always have to take into account the potential for abuse. Thryduulf has summarized it pretty well above. Regards SoWhy 16:41, 14 November 2018 (UTC)
- @SoWhy: Who wants to wait for six months to get rid of loads of drafts that are basically tons of junk? Basically, what G13 is doing is creating more work for admins as they have to delete tons of drafts everyday that meet G13 and the majority of those drafts are nothing but junk. Some of these are NOTWEBHOST violatinos, some of these are how-to guides, some of these are spam and I even saw a homework assignment in the loads of piece of junk in AfC. Yes, there are very interesting and good articles created via AfC which is why it is a very useful process. However, it is so sad to see that loads of junk is in the draftspace as well. If you look at Category:AfC submissions declined as jokes, at least 90% of these can be speedy deleted without waiting six months. Here is a classic example of what junk is. I tagged for speedy deletion as a blatant hoax. I also see Category:AfC submissions declined as a test which is stuff that has zero chance of improvement. Basically, tons of useless rubbish that can be deleted but is G2 valid for the draftspace? One draft which I tagged as G2 has been deleted but I remember it was absolutely blank when I tagged it for deletion. However, does this mean the others can be deleted? If U5 is not going to the draftspace then we need a general criterion for deletion of junk in the draftspace. Look, over 3,000 junk adverts, around 60 dictionary definitions which don't stand a chance because Wikipedia is not a dictionary and around 90 drafts which are blank and hopeless and all of these have to wait six months to be deleted? However, I oppose the deprecation of U5 because I still tag web hosts in the userspace for speedy deletion and new users will use the userspace for personal stuff and web hosts which has no place on Wikipedia. Pkbwcgs (talk) 16:18, 14 November 2018 (UTC)
- However, some of the opposition to this proposal was based on the fact that we already have a criterion (G13) that will take care of these drafts and that those in favor have imho not demonstrated why these drafts should go to MFD instead of waiting for them to become eligible for G13. Regards SoWhy 15:44, 14 November 2018 (UTC)
- I completely agree with Ivan. There is a general opinion here that G15/U5 should not be used on drafts. Logically this would apply to all drafts or no drafts regardless of namespace as Ivan explains. — Frayæ (Talk/Spjall) 15:24, 14 November 2018 (UTC)
- @Thryduulf and Hut 8.5: I understand that you are against this proposed G15 being implemented. Your arguments apply equally to the existing U5 criteria, and could be applied equally to deprecating U5 without a replacement. What do you say to this? — Frayæ (Talk/Spjall) 14:35, 14 November 2018 (UTC)
- To answer the ping above, I would be quite happy to get rid of U5 entirely as I think it is frequently abused to delete acceptable stuff, but I doubt there's consensus for that here. Genuine NOTWEBHOST violations are going to be more common in userspace than in draftspace, if only because userspace is specifically marked as your personal area and because we do allow some content which isn't related to Wikipedia there. By contrast if you start a draft then you are explicitly setting out to write an article and it's more likely that you will end up with at least an attempt at an encyclopedia article.
My main problem with this expansion though is that it is likely to be interpreted as "junk draft", which is a very bad idea for a speedy deletion criterion. Most of the examples which were cited to motivate this expansion above are not really NOTWEBHOST violations at all, and those are supposed to be the poster children for the criterion. I don't see any need to hurry to delete these drafts before the G13 expiry period. G13 is both more general and easier to assess than U5. The former only requires you to look at the edit history, the latter requires you to read the draft and come to some sort of judgement on it. If a draft is getting repeatedly resubmitted or recreated without any improvement then G13 wouldn't apply, but there aren't many of those cases. Hut 8.5 19:14, 14 November 2018 (UTC) - Random question: Do/did we have a G14 criterion? I cannot find evidence of its existence or former existence anywhere. Steel1943 (talk) 20:23, 14 November 2018 (UTC)
- @Steel1943:
G14 may not exist as enacted policy, but there are so many proposals for a G14 with various different attributes in the archives that I feel it would be wiser and less confusing to go one number up and match U5 with G15. — Frayæ (Talk/Spjall) 18:39, 12 November 2018 (UTC)
If that helps. — Frayæ (Talk/Spjall) 20:26, 14 November 2018 (UTC)- @Frayae: Yep, sure enough. Either way, IMO, if this somehow turns into an enacted “G” criterion, it should be G14 since the only G14 that will matter is the one that becomes policy. Steel1943 (talk) 20:30, 14 November 2018 (UTC)
- Agreed, the only that matters for numbering is what is enacted. I'm sure there were multiple G13 proposals unrelated to our current criteria (and G12s before that) and I know there were several R4 proposals that are completely different to the one that looks likely to gain consensus in the section above. Thryduulf (talk) 21:09, 14 November 2018 (UTC)
- @Frayae: Yep, sure enough. Either way, IMO, if this somehow turns into an enacted “G” criterion, it should be G14 since the only G14 that will matter is the one that becomes policy. Steel1943 (talk) 20:30, 14 November 2018 (UTC)
- @Steel1943:
Hut 8.5 says "By contrast if you start a draft then you are explicitly setting out to write an article and it's more likely that you will end up with at least an attempt at an encyclopedia article." which sounds like someone with a very different experience in Draftspace than me or a very different idea of what an article looks like. User:A2soup your info on Draft is a few years out of date. You are correct Draft is not "indexed" but it is mirrored to sites that are indexed and Google does count links from no indexed pages toward importance. Google actually looks for no index links as part of a well rounded link profile for ranking. Wikipedia links are gold because Wikipedia is a high importance site. Spammers and link builders love your attitude. Legacypac (talk) 21:06, 14 November 2018 (UTC)
- @Legacypac: Spam can already be speedy deleted under criterion G11 so that is completely irrelevant. Thryduulf (talk) 21:10, 14 November 2018 (UTC)
- That's good info that I wasn't aware of, thanks. I agree with Thryduulf that anything problematic in this regard is already covered by G11, but it does change my perception of draftspace a bit. A2soup (talk) 21:17, 14 November 2018 (UTC)
- Note I have seen more WP:NOTWEBHOST stuff in WP:MfD today so I am going to continue with this RfC. Pkbwcgs (talk) 18:33, 15 November 2018 (UTC)
- Seriously, Draft:My Journey To Photography is another example of WP:NOTWEBHOST and still there are so many opposers? Examples have been provided. Pkbwcgs (talk) 18:38, 15 November 2018 (UTC)
- Your examples have not demonstrated the need for this criterion. Per the very top of this page, CSD criteria need to meet 4 tests: Objective (several commenters have stated that they believe WP:NOTWEBHOST is subjective and you have not refuted this), Uncontestable (nobody has even attempted to refute my comments about 75% (at most) of nominations at MFD currently being uncontested; others have also expressed doubts), Frequent (I saw only 1 of ~30 nominations of pages in the draft space at MFD that would fall under this proposed criterion, 1 nomination in ~7 days is far from frequent enough to justify a CSD criterion. Most of the other "junk" you want to speedy delete would not actually fit, further demonstrating that it is not an objective criterion) and Nonredundant (You have completely failed to convince me and many others that this is not redundant to G11 and G13). Using Draft:My Journey To Photography as an example: For starters it was speedily deleted as a copyright violation (so fails "non-redundant"), but if it wasn't a copyvio it could have been moved to become the userpage of the user submitting it (fails "Uncontestable"). Before you say that it would have been excessive as a userpage, that is a judgement call that requires consensus to determine (fails "objective"). Thryduulf (talk) 22:30, 15 November 2018 (UTC)
- Thryduulf's points are exactly what I was trying to get across. WP:NOTWEBHOST is one of the most subjective WP:NOT criteria, and we get a massive number of people unsure of how to properly write wiki articles in AfC. While there are blatant cases like Draft:My Journey To Photography (which still could have been userfied as Thryduulf said), I see absolutely no reason why we should not be encouraging people to write better articles and reformat valid submissions rather than throwing around the CSD hammer immediately. In my opinion, immediate CSD should only be used on drafts for 'blatant' corpspam (G11), copyvios (G12), and BLP violations (G10). There's no reason why we shouldn't wait the customary six months for everything else, bad drafts aren't indexed by Google and aren't causing anyone harm and at best helping someone complete a draft could help someone become a returning wiki editor rather than scaring them off. Nathan2055talk - contribs 23:29, 15 November 2018 (UTC)
- Your examples have not demonstrated the need for this criterion. Per the very top of this page, CSD criteria need to meet 4 tests: Objective (several commenters have stated that they believe WP:NOTWEBHOST is subjective and you have not refuted this), Uncontestable (nobody has even attempted to refute my comments about 75% (at most) of nominations at MFD currently being uncontested; others have also expressed doubts), Frequent (I saw only 1 of ~30 nominations of pages in the draft space at MFD that would fall under this proposed criterion, 1 nomination in ~7 days is far from frequent enough to justify a CSD criterion. Most of the other "junk" you want to speedy delete would not actually fit, further demonstrating that it is not an objective criterion) and Nonredundant (You have completely failed to convince me and many others that this is not redundant to G11 and G13). Using Draft:My Journey To Photography as an example: For starters it was speedily deleted as a copyright violation (so fails "non-redundant"), but if it wasn't a copyvio it could have been moved to become the userpage of the user submitting it (fails "Uncontestable"). Before you say that it would have been excessive as a userpage, that is a judgement call that requires consensus to determine (fails "objective"). Thryduulf (talk) 22:30, 15 November 2018 (UTC)
- Seriously, Draft:My Journey To Photography is another example of WP:NOTWEBHOST and still there are so many opposers? Examples have been provided. Pkbwcgs (talk) 18:38, 15 November 2018 (UTC)
- Perfect - userfy these Drafts. Then we can tag and delete them U5. There are plenty of promosing drafts no one works on improving, keeping hopeless ones around helps no one. Legacypac (talk) 23:37, 15 November 2018 (UTC)
- Moving something to a different namespace for the sole purpose of getting it speedy deleted would be a blatant bad faith misuse of both page moves and speedy deletion. Anyone doing that should expect a very swift trip to ANI. It's also a strong argument in favour of deprecating U5. Thryduulf (talk) 00:19, 16 November 2018 (UTC)
- I wouldn't even be opposed to repealing U5 per the reasons given here. WP:NOTWEBHOST is not an objective criteria, and while I'm unsure of how to search the deletion log to verify this, I can't imagine we use it enough that MfD wouldn't be a substitute for the few cases where it does come up. G11 already covers obvious spam in all namespaces anyway, and outside of stuff G11 already covers, everything else U5 could be used on is subjective violations of WP:UPNOT that should be deleted through consensus anyway. Nathan2055talk - contribs 00:49, 16 November 2018 (UTC)
- U5 is used a lot in userspace cleanup. Lots of random junk left by non contributors. MfD does not need all this worthless junk coming there. Legacypac (talk) 01:02, 16 November 2018 (UTC)
- We need though to have an objective way of determining what is and is not speedily deletable "junk" though (and no, "junk" is not an objective description of anything). The more I read in this discussion the less convinced I am that U5 is fit for purpose. Thryduulf (talk) 01:51, 16 November 2018 (UTC)
- Thryduulf, see this article or this article; "junk" is objective descriptions for both :-) Nyttend (talk) 20:46, 18 November 2018 (UTC)
- Update: Today, I came up with a new proposal at Wikipedia:Village pump (policy)#Proposal/RfC: Should we allow WP:PROD in the draftspace?. Pkbwcgs (talk) 16:25, 16 November 2018 (UTC)
- We need though to have an objective way of determining what is and is not speedily deletable "junk" though (and no, "junk" is not an objective description of anything). The more I read in this discussion the less convinced I am that U5 is fit for purpose. Thryduulf (talk) 01:51, 16 November 2018 (UTC)
- U5 is used a lot in userspace cleanup. Lots of random junk left by non contributors. MfD does not need all this worthless junk coming there. Legacypac (talk) 01:02, 16 November 2018 (UTC)
- I wouldn't even be opposed to repealing U5 per the reasons given here. WP:NOTWEBHOST is not an objective criteria, and while I'm unsure of how to search the deletion log to verify this, I can't imagine we use it enough that MfD wouldn't be a substitute for the few cases where it does come up. G11 already covers obvious spam in all namespaces anyway, and outside of stuff G11 already covers, everything else U5 could be used on is subjective violations of WP:UPNOT that should be deleted through consensus anyway. Nathan2055talk - contribs 00:49, 16 November 2018 (UTC)
- Moving something to a different namespace for the sole purpose of getting it speedy deleted would be a blatant bad faith misuse of both page moves and speedy deletion. Anyone doing that should expect a very swift trip to ANI. It's also a strong argument in favour of deprecating U5. Thryduulf (talk) 00:19, 16 November 2018 (UTC)
- Perfect - userfy these Drafts. Then we can tag and delete them U5. There are plenty of promosing drafts no one works on improving, keeping hopeless ones around helps no one. Legacypac (talk) 23:37, 15 November 2018 (UTC)
- Oppose I don't think there's much of a reason for this - I don't see web hosting issues at all at AfC, and I feel like it will be misused. SportingFlyer talk 11:04, 17 November 2018 (UTC)
U5 timing
Hello, just wanted to come here for a sanity check. I just ran across User:AviatorTJ/SpaceKraft in CAT:CSD; it would definitely qualify for U5 were it newly created, but it's seven years old. Is the criterion meant for pages of any age, or should it be used only for recent creations? The criterion doesn't say anything about dates, but on the other hand I don't remember the last time I saw a page tagged for U5 that wasn't rather newly created. It would help if we expanded the criterion with a date comment, either "should only be used for recent creations" or "may be used regardless of the date when a page was created". Nyttend (talk) 20:40, 18 November 2018 (UTC)