Jump to content

Wikipedia:Village pump (policy)

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Bagumba (talk | contribs) at 22:44, 8 February 2016 (→‎Requirement to cite a list item inline?: WP:CIRCULAR). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

"WP:VPP" redirects here. For proposals, see Wikipedia:Village pump (proposals).
 Policy Technical Proposals Idea lab WMF Miscellaneous 
Shortcuts
The policy section of the village pump is used to discuss proposed policies and guidelines and changes to existing policies and guidelines.
If you want to propose something new that is not a policy or guideline, use the proposals section.
If you have a question about how to apply an existing policy or guideline, try one of the many Wikipedia:Noticeboards.
This is not the place to resolve disputes over how a policy should be implemented. Please see Wikipedia:Dispute resolution for how to proceed in such cases.

Please see this FAQ page for a list of frequently rejected or ignored proposals.



AfD culture

I have been participating in AfD for a few months now. The culture of deletion is becoming rather aggressive. Is anyone else experiencing this? Is there any way that we can look at policies to help slow down the process?

My suggestions would include:

  1. requiring AfD nominators to do WP:BEFORE. I've found quite a few articles nominated with so-called "no room for improvement found" as the reason for AfD and I and a few other users are able to find reliable sources within hours (or minutes on Google nonetheless!)
  2. give articles breathing space. Several new articles have been up for AfD. This is especially problematic when we have a new user who doesn't know about putting up a template to indicate the article is still under construction.
  3. create additional criteria surrounding topics that are more difficult to research, such as areas where there is a language barrier or where history has ignored the achievements of various groups based on race, culture, religion/lack of religion, gender or non-conformity.

I know this has been discussed in the past, but I think it needs to be discussed again. I just witnessed a new user give up over an AfD. (See Malissa A. O'Dubhtaigh: which I'm not saying necessarily meets GNG, but it wasn't given time and the user was handled brusquely.) Wikipedia is about amassing all human knowledge, as I see it, and all voices should be welcome and feel welcome. The aggressive culture of deletion is frustrating even to most hardened editors.

Any suggestions out there? Thanks! Megalibrarygirl (talk) 14:10, 9 October 2015 (UTC)[reply]

There has been this culture in some quarters for a long time, for example look at the very early history and discussion of Oscar Werner Tiegs. Also have a look at WP:ODNT.
Perhaps no one is allowed nominate an article for deletion unless they have actually created somewhere in their history at least a few new articles themselves, which did not get deleted . . ? 152.91.10.22 (talk) 00:09, 6 January 2016 (UTC)[reply]
Megalibrarygirl I would be loathe to work on this article because the lawsuit involved, which stretched out ten+ years, appears to be the only source. There was a name change during the process and since there are no sources to guide us, how can we be sensitive to the preferred name of the party. Further, in reading the suit, the party has felt her medical privacy was not protected. While I encourage diversity and would wish that Wikipedia did as well, this particular article seems like an invasion of privacy. SusunW (talk) 15:02, 9 October 2015 (UTC)[reply]
But that being said, the culture of deletion on here is ver frustrating. If one must check boxes and give rationale to even post a picture, it baffles me that anyone and everyone can nominate an article for deletion without the skill to weigh notability or do any sort of research beforehand. I cannot understand why improvement rather than deletion is not the key. SusunW (talk) 15:05, 9 October 2015 (UTC)[reply]
While you can see my postings on deletionism above, I'm not even sure it's a culture. What I've seen is the positive practice of a few people "patrolling" for vandalism and other negative stuff turn into "I'll delete every new page and let the admins/other editors sort it out." Given the effort involved in getting something into Wikipedia these days, such intellectually dishonest activity discourages nearly anyone making a new article. With some of the articles I commented on in AfD, the creator would ask simple questions about the rationale for the deletion and get absolutely nothing, except the odd "per nom." Once the drive-by deletion happens, the editor in question almost never returns. My favorite had to be an article that was discussed in AfC for ages. Someone took responsibility, wrote the page, and had it marked for deletion essentially as soon as it was submitted. This is how Wikipedia actively drives away contributors.--69.204.153.39 (talk) 15:51, 9 October 2015 (UTC)[reply]
@Megalibrarygirl: I would like to echo the above suggestions and well as emphasize Wikipedia:CSD: unless the article created meets said criteria, don't nominate it for speedy deletion; if it is up for deletion, calmly let creators know tips and give them time to improve the article and send words of encouragement, maybe an encouraging emoticon along with the words. Sam.gov (talk) 20:54, 9 October 2015 (UTC)[reply]
@Sam.gov:, I like that idea. I really think we need to nurture editors more often. I was on Wiki for a long time before I felt confident enough to edit, let along create my own articles. It is intimidating. Megalibrarygirl (talk) 21:32, 9 October 2015 (UTC)[reply]
Thank you. Yes, It can get intimidating during the time before editors become more confident. Sam.gov (talk) 22:09, 9 October 2015 (UTC)[reply]

The culture of "bigger and more is better" has been proven troubling to reputations again and and again. -- TRPoD aka The Red Pen of Doom 21:01, 9 October 2015 (UTC)[reply]

Agree entirely with TRPOD. Wikipedia is not and has never been "about amassing all human knowledge"; it has a very specific remit to only cover material which is demonstrably covered in multiple independent non-trivial reliable sources, and admins deleting material which doesn't fit that remit are acting entirely correctly. As this is an absolute core policy of Wikipedia, there is no realistic prospect of any discussion ever changing it as long as Wikipedia remains in its current form. ‑ iridescent 21:06, 9 October 2015 (UTC)[reply]
There is no absolute requirement for multiple sources even today. GNG does not say that: "generally", where it appears in GNG, means "most", not "all". Also, it is the sum total of coverage in all sources which must be non trivial. James500 (talk) 10:05, 23 November 2015 (UTC)[reply]
I'm not saying bigger is better. You're right, all human knowledge is impossible, I was being hyperbolic in my attempt to describe why I think it's important to have diversity in Wiki. Thanks for calling that out--I should write more concisely sometimes. However, what I am worried about, and why I brought up the topic is that I think that there really is a deletionist culture. I've observed a pattern over time, and so have a few others on WikiPedia:WikiProject Women/Women in Red. For example, I have run into plenty of AfD pages where the nominators often say they've done WP:BEFORE, when they clearly haven't. Sometimes, the nominator will even say they have additional information, but because it's "not in the article," the article should be deleted. I understand that editors want others to follow through and add information when they say they will, but just because someone else didn't add that info, why can't you add it? I only tag articles when I don't have time to add the info myself. If I see an article with a tag, I fix it. It doesn't take long. Why aren't we doing that more often? Megalibrarygirl (talk) 21:32, 9 October 2015 (UTC)[reply]
The obvious answer; because you have 3458 active editors (with "active" defined loosely as 100 edits in the last month), of whom 580 are admins, dealing with 5 million articles, and it's not reasonable to expect us to do everyone else's work for them when they can't be bothered to do it themselves. If you haven't already, it's a salutary exercise to look at the new pages backlog; those highlighted in yellow are the ones that nobody has looked at. "If you see an article with a problem, fix it" is a laudable aim, but completely impractical unless Wikipedia can drastically grow its editor base or throttle the article creation rate; the former has resisted every effort to address it, and every attempt to address the latter has been vetoed by the WMF. ‑ iridescent 22:08, 9 October 2015 (UTC)[reply]
That is nonsense. No meaningful attempt whatsoever has been made to increase the number of editors, active or otherwise. Quite the opposite has happened. The editor retention problem is caused by excessive deletion. The only way to increase the number of editors, active or otherwise, is to reduce deletions by performing corrective surgery on the (unsatisfactory) deletion processes and (vague and questionable) deletion criteria. James500 (talk) 10:05, 23 November 2015 (UTC)[reply]
@James500: No meaningful attempt whatsoever has been made to increase the number of editors See Wikipedia_talk:WikiProject_Editor_Retention -- this wikiproject appears to be dead?
The only way to increase the number of editors, active or otherwise, is to reduce deletions I would not go as far as to say that reducing deletions is the ONLY way to increase the number of editors, but I agree it is a very important step. Here is a small example I just bumped into:
The article I started about Jenny Doan has been sitting as a lonely stub since I started it in February 2014. Then in April 2015 a new editor, User:Drbillnye added some info to it, but when I checked the editor’s history I saw he had only one edit. A check of the editor's talk page revealed that he tried to add more in the form of an article, but the article was deleted by user:NawlinWiki and remains as a red link on Jenny Doan. I assume User:Drbillnye will become one of the many missed opportunities we have had to add new editors? Ottawahitech (talk) 15:38, 28 November 2015 (UTC)please ping me[reply]
Template:PingJames500@Ottawahitech: I think it's a stretch to say that the number of editors has gone down primarily or only because of article deletion. I also think it's a mistake to allow poorly-sourced articles to be left on this page in perpetua. As for the claim that we lost Drbillnye because his article was deleted, 1) the article was deleted because it was promotional/an advertisement, likely because it was sourced solely from the quilt company and maybe even copy-pasted from the quilt company's website, and 2) how do we know that he would've contributed on anything non-quilt company related anyway? pbp 16:04, 28 November 2015 (UTC)[reply]
@Purplebackpack89: We don't know if the editor would have contributed anything to other topics, but if they only added some info to any of the articles in Category:Quilting that would be awsome. Just my $.02 & thanks for pinging me. Ottawahitech (talk) 16:19, 28 November 2015 (UTC)please ping me[reply]
Off-topic @Ottawahitech: Unless there has been a recent change in the code that runs Wikipedia, pings can't be corrected by merely fixing typos. You have to add a new ~~~~ at the same time you fix the typo, then if you want, go back and remove the signature (or remove the "original" signature if you prefer). And no, merely replacing your existing signature with a new one won't work. Since your ping didn't work, I'm going to mention Purplebackpack89 here so that he will get the notification and look up the screen and see your message. davidwr/(talk)/(contribs) 17:08, 28 November 2015 (UTC)[reply]
@James500:@Ottawahitech:I'm a great example, I had never tried to contribute to a wikipedia article before, took me about an hour to try and figure out the interface and tribal lore that goes around proper formatting and the like, then the articles I was trying to link to, if I recall correctly, were articles from the WSJ, NBC Nightly News, MSNBC and I was probably using the a history of the company that I'd written and used elsewhere (either on the site or on other articles) - if that was taboo, I didn't know. I had one article get deleted because it was promotion (the one about the quilt company I believe) and then my edits to Mom's page were nixed for some other reason, my takeaway was that the wiki editor circle were a bunch of pretentious pricks who would rather hack me down and the time and effort that went into my attempts to help build a good article rather than help teach me how to drive value and I didn't bother to come back. — Preceding unsigned comment added by Drbillnye (talk • contribs) 18:12, 28 November 2015‎ @James500:@Ottawahitech: I think this is for you, it was unsigned so the pings never went out. davidwr/(talk)/(contribs) 19:35, 28 November 2015 (UTC)[reply]
I believe this is exactly the typical experience of most new editors. And it's happening multiple X's a day on Wikipedia. Frankly, I'd say Wikipedia would have a better chance of trying to get out a red wine stain by using yellow mustard, then it does of keeping new editors. Especially those editors who write! --MurderByDeadcopy"bang!" 20:14, 29 November 2015 (UTC)[reply]
I totally get what you are saying Megalibrarygirl. I don’t see anyone asking the admins to do everything. I do agree that there is a “get rid of articles” culture on here and have pointed out on more Another example than one occasion to those who say “I would vote to keep if someone would edit the article” that good prose is not a requirement. Then there is the ever popular “editor doesn’t appear to be active” (isn’t that own?, who cares if the creator is active?), and “I see no better improvement” (because if the article is complete and notability is not debatable why would anyone need to improve it?) Seems like a lot of whining and little action on the part of some. Usually I just fix what I see that is problematic. I have rarely asked an admin for anything. What I see is a small group of people, who don't appear to be admins, who nominate every file they can for deletion. I also see a trend of an unwillingness to make Wikipedia an inclusive or welcoming platform, which will result in poor retention. Nothing is written in simple, straightforward or friendly language. (Admittedly, after a year, I still don't know what 1/2 the acronyms that are bandied about mean, and I don't think I want to). Group A and Group B are forever opposing each other as well as any ideas for improving the overall performance. I try to avoid all the drama and save what articles I can. When it gets too stressful, I walk away or just go silent. — Preceding unsigned comment added by SusunW (talk • contribs) 00:29, 10 October 2015
Absolutely! I started this discussion because I believe we can change things. The place to create change is through discussion. I have spent time in the backlogs working to source tagged articles. With the amount of female bios at a measly 15%, I try to source as many as I can in order to at least satisfy GNG. I understand the frustration with many created biographies, but many are actually notable...just because the nominator knows nothing about the topic, doesn't mean no notability. Case in point: looking at new articles, hardly any are women, and the ones who are, are often sports figures or models. Interestingly, a female sports figure with 1 reference often gets an AfD pass, but not other women. Something's off with that. I want to see things change. Let's see what we are able to do. For example, how can we get hard data to support what I and others are observing? I might think there is a problem, but I'd prefer numbers to "it seems." Megalibrarygirl (talk) 01:08, 10 October 2015 (UTC)[reply]
I was active last year for a few months in AfD discussions, and it bothered me deeply that most of them were about notable subjects, but nobody involved in the AfD discussions looked for RS to establish that. That is grounds for a stub tag. That is grounds for doing the work yourself before nominating. I found myself working long hours every day to save articles from deletion, regardless of the topic (I don't care about role-playing games or "onomastics", but I worked to save those articles anyway), and in the end there was only one I couldn't save. This onus has to be placed on the person nominating the article for deletion. So many of them talk about "your" article instead of seeing all articles as "our" articles. Megalibrarygirl, I agree with you completely on requiring WP:BEFORE in order to nominate an article for deletion. iridescent, "it's not reasonable to expect us to do everyone else's work for them when they can't be bothered to do it themselves." This is not "everyone else's work." This is our work. Right there is the problem. We are a community with a common purpose, not factions of "us" who do the work and "them" who don't. And we can never say why someone stopped working on an article (or "can't be bothered"). I think we would have more people participating if this was not such an adversarial environment. We don't have enough admins and people working clean-up, but we certainly do not have enough people doing the work to save good articles from the excessive AfDs for notable subjects that just need a quick Google search.
We are not supposed to "own" articles as editors, but I think we all know that people do. They will revert everything that did not originate with them. Try editing an article for a popular progressive rock album. Or worse, try starting a new article on any music album. It's often an exercise in futility to contribute and make meaningful changes. I got worn down. In AfD discussions I felt beaten down. Nobody tries to help articles before nomination, and discussions are full of competing acronyms, as if they were etched in stone, and everybody (myself included) is convinced they are right. But again, I rescued several articles from deletion, all but one. Had I not taken the time to provide the RS for notability, no one else would, and they would be gone. Then when someone decides to start a new article and sees that a previous version was deleted already, how likely are they to continue? A stub tag (or other tag) is enough to tell readers the article might be a little iffy. If editors have time to patrol and nominate AfDs, they could instead use that time to improve things. More editors might stick with it without all that unnecessary struggle. WP is always a work in progress, and that means a certain percentage of our articles are always going to be stubs under development. "It's been a stub for years," I heard. "What have you done to change that?" is my question. The answer is always the same: nominate it for deletion. Sorry about the tirade. If things were more cooperative, WP would be a lot more rewarding, and a lot more diverse. Right now we have a selection bias - editors who are willing to put up with the struggles are the ones contributing. Dcs002 (talk) 03:16, 10 October 2015 (UTC)[reply]
👍 Like Dcs002 I think you about covered the problem. It is exhausting. Mostly I work on women because as a member of several Wikiprojects on women, those are the alerts I see. But I recently saved a multiple award winning French male architect, and a couple of movies which I have never even seen or heard of because they came into my viewing range. I don't go to the Afd page, it is too overwhelming to think of all the files that have been nominated. Maybe there are indeed a lot that aren't notable, but in my experience most that I have worked on just needed sourcing and a little TLC. SusunW (talk) 03:53, 10 October 2015 (UTC)[reply]
I also agree with Dcs002 and SusunW. I want to see the culture change. The same people are nominating articles for deletion without doing WP:BEFORE. Also, I love the way that you emphasize that it's not about us vs. them... it's about all of us creating a better resource. I think that deletion is especially problematic because others took time to create something and other editors are trashing the creations. Please note, I'm not saying that EVERY article needs to be kept! But let's exercise more care. Let's see what we can do to create a better environment for newbies and let's work on the AfD area. It shouldn't be exhausting or frustrating. How can we do that? Who do we need to get on board with looking at this? Megalibrarygirl (talk) 17:54, 10 October 2015 (UTC)[reply]

While I would agree that there are many self-proclaimed deletionists active in Wikipedia and some good material gets discarded, not all all deletion-related discussions are groundless. Just a look at recent nominations reveals some obvious problems. An article about a video game which is entirely unsourced and contains very little information. A film-related trope pointed by Roger Ebert that may be notable but has otherwise received very little coverage. An article about a local police department in Alaska with not much material to cover. Articles about music performers and bands with no particular level of success (two album releases at best). A minor organization which was briefly in the news in 2007 but has not had any coverage since. A Star Wars-related podcast that got some positive comments a few years ago, with no evidence of lasting influence.

Unsourced articles might have potential for growth, but some are only of interest to their creators and others are potential hoaxes. For example, Wikipedia:List of hoaxes on Wikipedia lists examples of hoax articles that went unnoticed for years. An article on "Jack Robichaux", supposedly a 19th-century serial rapist, existed for 10 years before someone questioned his existence. "Pikes on Cliffs" was an article on a 16th century house with both historical significance and a related legend. It took 9 years before some people realized this article was fabricated. More embarrassing for Wikipedia is that some hoaxes are pointed out by newspapers critical of our accuracy.

Meanwhile, images that get deleted often are tagged for copyright issues. This includes book covers, album covers, screenshots, etch. All to avoid potential legal troubles for Wikipedia. That something is available does not make it free for use. This can get very frustrating when searching for some image that can be found everywhere except Wikipedia.

While habitual deletionists may get annoying, indiscriminately accepting any contribution may be the wrong idea. Dimadick (talk) 23:06, 10 October 2015 (UTC)[reply]

Absolutely no one on this thread has advocated for "indiscriminately accepting any contribution". I believe that each person has agreed that GNG with RS should remain the norm. The issue is the "rush to delete". If it harms no one (i.e. is not a biography of a living person) there is time to review the article and fix any problematic areas. There is certainly time to communicate with the creator and try to mentor them through the process, as well. If one does not have the skill to search for sources to improve an article, then they also do not have the skill to evaluate whether it is notable and should not be allowed to propose it for deletion. (And we can tit for tat all day about deletions - I fixed Pakistan's trade secretary today who was prodded. Clearly notable, government bio, took about 10 minutes to add sources, at most). SusunW (talk) 23:35, 10 October 2015 (UTC)[reply]
Dimadick, I agree with your entire post. I also saw many articles that were blatant advertising for investors and bios for clearly non-notable people (including one by a kid that broke my heart to !vote down, along with everyone else - I hope he eventually understood). While I was participating in AfD discussions, I don't recall seeing a discussion for any recorded work that I would not consider notable under WP:ALBUM, though there was the occasional local band with their own page, and I think they were usually written by fans. I could be wrong with my memory, but I recall about half of the articles on the AfD list being clearly articles that should be deleted, and half being either blatantly notable with inadequate sourcing or questionably notable. My belief is that it hurts us to delete articles because notability is questionable, so I guess I'm an inclusionist.
But the biggest problem, IMO, is the attitude of absolutism in AfD discussions. There is no discussion. Too often there is an acronym cited and an entrenched opinion. When I have fixed articles, or even tried to fix them, I have perceived an attitude of resentment and on many occasions warnings that "we" were just going to delete the article anyway because somehow they knew, without looking for sources or viewing my changes, that there was no way an article or subject could be "made" notable (made, as opposed to being notable). Sorry, another tirade. I guess my experience was more frustrating than I remembered, and maybe I've been carrying some emotional baggage for a while. Dcs002 (talk) 00:37, 11 October 2015 (UTC)[reply]
@Dcs002: I think you're spot on. It's a big encyclopedia, and there are a couple of great folks in AfD, but I would say that that there is this notion among many AfD editors that things like notability are these platonic sorts of things -- abstract ideals which a topic either does or does not embody. Also, if an article creator dares stand up for their work (few do), that's a paddling deleting. So, while we must assume good faith, people should try to acknowledge non-extremist views about notability and such.--69.204.153.39 (talk) 01:28, 11 October 2015 (UTC)[reply]
Thanks for the wake-up call. I need to say that not everyone in AfD discussions was as obstinate as I described. (They were just the ones that made it such a miserable experience.) There were many thoughtful editors as well, and the closers were always very thoughtful and considerate. Dcs002 (talk) 07:49, 11 October 2015 (UTC)[reply]

FYI, the same culture exists throughout the XfD spectrum. Sometimes it seems that certain editors are more interesting in amassing stats for how many of X they successfully nominate for deletion. I have participated in a few of those discussions, and sometimes agreed that deletion was needed, but only after doing my own research on the nominee. I don't see how anyone can possibly research all of the nominees for deletion, and vote on every one of them, within the span of just a few minutes, but that's what some people seem to manage. Etamni | ✉ | ✓  04:35, 12 October 2015 (UTC)[reply]

Ok, several of us here agree that we have a problem. What is the next step after we're done preaching to the choir? What action can we take? What remedies are available? And more importantly, who wants to stick their neck out and take charge of that action? Dcs002 (talk) 06:52, 12 October 2015 (UTC)[reply]
I'd suggest starting with Megalibrarygirl's initial proposal to require more work be done before a nomination can go through, echoing SusunW's points about adding files. There is also something to be said for enacting and enforcing a temporary freeze (perhaps a week) on nomination of new articles except where they need to be speedied. —⁠烏⁠Γ (kaw), 07:58, 12 October 2015 (UTC)[reply]
I just saw this. The entire aggressive attitude of deletionists has been baffling to me for years. They do not seem to be motivated by logic, even when the debate points are overwhelming them. I understand there is a lot of junk out there that needs to be cleaned up, but once the substance of an article is established, a reasonable person would back off. You can see the wave of reasonable people switch their "votes" (I know they aren't really votes, but they are). These deletionists do not back off. They fight to their last breath trying to get legitimate content deleted. I have publicly suspected there is some accrual of brownie points for the most scalps. Worse yet, sometimes they find a corrupt administrator to back them up and they win, forever dooming a valid subject to the perceived WP:SALT, even if not specifically administered. What shocks me the most is how uninformed these people are. They dabble in subjects they do not understand, dismiss sources that are the top of their field, and do not do the required research WP:BEFORE posting their attack. Frustrated as I am about the cases I've seen lost, I have a pretty good record of successful defense when I get involved. I see some names over and over, pushing repeatedly against . . . facts. There should be a penalty for bringing too many unsuccessful (the only way to categorize unfounded) attacks on articles. Once they reach a quota, they should be prohibited from making another proposal for a period of time. If they continue to lose, add to that length of time. You'd think they would learn, but some just won't get it. At some point, ban the serious, serial abusers from ever making another proposal for deletion. Trackinfo (talk) 09:05, 12 October 2015 (UTC)[reply]
Given that a large cadre of editors on Wikipedia could be categorized as deletionists, I think any steps taken would have to be modest and incremental. If we can get away from the culture of deleting most every new page straightaway for others to deal with, that would be a serious start. Some of my thoughts are: 1) require Prod'ing first, and only allow a second user to AfD, not the initial prodder 2) Make filing an AfD at least as hard as uploading an image. Lots of questions about "have you really done WP:BEFORE? and have you tried improving this page." 3) Prevent articles that have had a favorable AfC outcome from getting immediately AfD'd 4) Require each nomination to, if at all possible, bring up specific actionable items that could make the page suitable. I'm sure there are lots of better ideas out there, but beginning to talk concretely is a good start.--69.204.153.39 (talk) 01:02, 13 October 2015 (UTC)[reply]
@Etamni: you said certain editors are more interested in amassing stats for how many of X they successfully nominate for deletion.
I also made the same observation, noting that it only takes seconds for nominators to initiate a deletion discussion which requires at least three complicated edits:
  • Creating a new page for the deletion discussion
  • Notifying the creator of the page of the deletion discussion
  • Putting a banner on the page nominated for deletion
optional:
Ottawahitech,
You missed transcluding the AFD page into the list, but it actually doesn't require any complicated edits at all. Instead, it requires three quick and simple steps:
  1. Go to Special:Preferences#mw-prefsection-gadgets and turn on Twinkle (this only has to be done the first time).
  2. Go back to the page and choose "XFD" from the new WP:TW menu.
  3. Fill in the form and click the 'Submit query' button.
Twinkle will do all the other steps for you. WhatamIdoing (talk) 23:17, 20 November 2015 (UTC)[reply]

Thanks user:whatamIdoing — this is really useful. I wonder though, why it is not mandatory to notify page creators that the page they created has been nominated for deletion if it is that easy and takes only seconds? why do some nominators, and in particular wiki-admins, resist notifying page creators? (See for example user:Good Olfactory here and User:TexasAndroid here) Ottawahitech (talk) 14:34, 23 November 2015 (UTC)please ping me[reply]
There is little point in notifying an inactive editor, and little need to notify a highly active one. Also, the question of whether the subject is suitable for its own article isn't really a question that requires the participation of the first name in the editing history (which, in the case of pages that began as redirects, isn't necessarily the person who wrote the article). WhatamIdoing (talk) 20:54, 23 November 2015 (UTC)[reply]
Ottawahitech, because notifying the first editor is an unnecessary hand-holding duplication of work. If a user is truly interested in whether or not their creations are nominated for deletion, all they have to do is use their watchlist, because it already is mandatory to tag the nominated content with a template. Good Ol’factory (talk) 21:02, 23 November 2015 (UTC)[reply]
@Good Olfactory: Believe it or not, there is a (speculation) large number of editors who do not use their watchlist. I am one of them. I figure if I did watch, I would never have the time to add content. Instead I would be be chasing discussions. I suppose this is because the items that get the most action on my watchlist are talk pages which I find suck up way too much energy. Ottawahitech (talk) 14:19, 6 December 2015 (UTC)please ping me[reply]
I strongly contest that claim: watchlists are nearly universally used, and its clear to that when a new banner announcement appears on the watchlist or a change in the mediawiki happens and editors race it put in complaints of various degree to that change. Further, the watchlist while not required greatly increases the efficiency of any established editor; not using the watchlist would be like not using a TV guide to find when a program comes on but instead flipping through all available channels at random times to do so. (And speaking as one with getting drawn into talk pages, the solution is to not watchlist all those talk pages, or otherwise commit to using the watchlist more effectively). --MASEM (t) 15:39, 6 December 2015 (UTC)[reply]
  • I agree with Masem: most users put pages they create on their watchlist. Furthermore, since many AfDs are done by Twinkle, many people get a talk-page notification anyway. Also, @Ottawahitech: there's a function on your watchlist that allows you to limit what you view to article-space, and, as Masem noted, you need not watch talk pages. pbp 16:17, 6 December 2015 (UTC)[reply]
  • If it's true that users are not using their watchlist (I acknowledge that some may choose not to), then I have absolutely no sympathy for the complaint that they aren't finding out about content they created being nominated. If it's something you care about, use the tools and processes that are provided to find out about them and don't rely on other editors to somehow flag your attention. Good Ol’factory (talk) 23:22, 6 December 2015 (UTC)[reply]
  • There's a couple issues with this:
1) If someone is sufficiently active, they will have a large number of items on their watchlist and it will become easy to miss things. (Although I admit this wouldn't likely apply to newcomers.)
2) Do newcomers even know there is such a thing as a watchlist or how to use it?
3) If someone hasn't specifically checked "Expand watchlist to show all changes, not just the most recent" in the Advanced preferences, there's an unfortunate chance that even if the article creator does check their watchlist for changes to that article that the AfD nomination won't show up because there's been a more recent change to the page. If the latest change is somebody fixing a typo they might reasonably not look at the article.
4) The watchlist defaults to the last 7 days. If somebody creates the article on Friday, and it's nominated for deletion on Saturday, and they don't come back to Wikipedia until Sunday a week later - Wikipedia is not compulsory (WP:CHOICE) - then they won't see the notification because it will have scrolled off the Watchlist.
5) Actually, that's my biggest objection to leaving the onus on the article creator to discover that the article they created is subject to an RfD by requiring them to visit Wikipedia to view their watchlist. It violates the policy that Wikipedia is not compulsory. By doing something positive to ping them, it keeps Wikipedia voluntary for them.
Thisisnotatest (talk) 07:11, 7 December 2015 (UTC)[reply]
Given that the Watchlist link sits at the top of the page, the argument "how many people know it is there" is not really a factor. I do agree that if there is an AFD nom, and then someone edits regularly, the AFD nom will not show up on the page, and that can be a problem, but also at the end of the day, for that and the rest of these WP:OWN applies: when you hit submit on any edit page, you no longer own that content (though you attributed for it). The community can decide if it is appropriate or not without the submitting editor's consent. Granted, there are a raft of problems that generally plague AFD overall, but a lot of the arguments here just boil down to what has already been covered at WP:ATA. --MASEM (t) 16:59, 7 December 2015 (UTC)[reply]

I have also noticed a tendency among many editors to nominate articles for deletion (or even tag them for speedy deletion) when that was clearly inappropriate. This means that either other editors must spend time they could have used to create or edit articles contesting the nomination, or the nominator gets their way and the article is deleted. I would strongly support an additional dialog being required in order to nominate articles (or other kinds of pages) for deletion. A grace period of perhaps 12 to 48 hours before a newly-created article could be nominated for deletion might also be good, in which case articles with serious problems such as copyvio could still be dealt with ASAP via speedy deletion. I haven't yet decided how I feel about the proposal below. (Incidentally, for those wondering about the motivations of over-enthusiastic deletion nominators, I have seen it suggested that they might view AfD as akin to a video game where their goal is to rack up as many "kills" — that is, deletions — as possible. I don't know how accurate that idea might be, but it seems it might be plausible for at least some nominators.) —GrammarFascist contribstalk 07:48, 24 October 2015 (UTC)[reply]

I disagree with some of the confrontational language in this discussion (not from the OP) and the simplistic labelling of fellow editors as "inclusionist" or "deletionist". That's an unfortunate trend in most of the recent AfD-related debates, and such an approach isn't really helpful to solve eventual flaws in a collaborative manner (I am certainly not claiming, that everything is perfectly OK with AfD processes and notability guidelines). WP:AGF includes editors with differing opinions too - just saying. Aside from that general observation: the suggested grace period of n days for new articles sounds like a good suggestion to move forward (and should be relatively easy to implement), assuming we would exclude clear issues like blatant promotion, serious BLP concerns and large unfixable copyvios from that handling. The proposal below should be declined. Such (relatively few) instances of persistent nominations, that are not based on policy, should be handled case by case: either by talking with the nominator of such problematic cases (instead of talking about them), or by improving unclear notability guidelines. GermanJoe (talk) 14:19, 8 November 2015 (UTC)[reply]

I don’t believe the use of such terms is confrontational. I am an wp:inclusionist and I feel slighted onWikipedia because of it. Ottawahitech (talk) 16:49, 12 November 2015 (UTC)please ping me[reply]
  • Maybe we are being too harsh on creators of new articles. But I don't think it's right to force BEFORE down people's throat. It doesn't seem wholly fair to me that editors have to try and fix really bad articles; many of which are clearly unfixable. Until relatively recently, I was a deletionist. I nominated dozens of articles for deletion...most of which hadn't been created by new editors, but rather editors who created a whole lotta of articles in big bunches. pbp 17:07, 12 November 2015 (UTC)[reply]
@Purplebackpack89/C: Is there something wrong with creating a whole lotta of articles in big bunches? From my inclusionist vantage point I see tons of editors who add very little to wikipedia:mainspace, but effortlessly rack up an impressive edit-count which gets them the desirable mop/Admin status through the wp:Request for Adminship process.Ottawahitech (talk) 17:45, 16 November 2015 (UTC)please ping me[reply]
@Ottawahitech:: Oftentimes, articles created in big bunches are poorly sourced or poorly written. Also, TBH, I see people AfDing a lot of articles in hopes of gaining adminship to be a relatively minor issue: not only are the people who do that relatively few in number, but most of the people who nominate a lot of articles for deletion have rubbed enough people the wrong way to preclude them ever having a mop. Oh, FYI, my name's Purplebackpack89, not Purplebackpack89/C. User:Purplebackpack89/C is a redirect to my contributions because there wasn't enough room in my sig to include Special:Contributions/Purplebackpack89. pbp 18:40, 16 November 2015 (UTC)[reply]
@Purplebackpack89: you said: articles created in big bunches are poorly sourced or poorly written but isn’t this how wikipedia became the great resource that it is today? When I looked at the page history of articles that were started in the early 2000s they invariably provided little detail and had no references but given time they now form the backbone of wikipedia which draws the world’s attention. No? Ottawahitech (talk) 15:05, 17 November 2015 (UTC)[reply]
@Ottawahitech: Setting aside the issue that Wikipedia 10-15 years ago doesn't have the rules it does today, do you believe that Wikipedia's initial article mass came primarily from editors creating new articles very quickly, like maybe 10-15-20 in a period of a few hours? Or do you believe that the creation of thousands and thousands of stubs was the result of a myriad of editors each creating a few articles, often over long periods of time? I cannot condone "drive-by creation" where people create many articles in a short amount of time; I really have to say it takes a minimum of an hour to write an article of any kind of quality (of course, that time includes finding and reading the references put in the article). Remember that in between the editors creating all those articles and today, Wikipedia was thought of as the scourge of the internet, not because the articles were short, but because they were unsourced and inaccurate. Even today, I still think it would be beneficial if the project was forbidden from creating new entries for a time, and forced instead to improve quality of articles. pbp 16:11, 17 November 2015 (UTC)[reply]
@Purplebackpack89: I Have to research to see how many editors there were in the early years, but if I remember correctly it was a fairly small number compared with the number of articles they produced, meaning they each created a large number of articles, on average.
As far as [creating] 10-15-20 [articles] in a period of a few hours? I have heard that more recently many articles were actually started by a BOT, not a human. Ottawahitech (talk) 20:32, 17 November 2015 (UTC)[reply]
@Purplebackpack89: Here is the official statistics table I found at Wikipedia:WikiProject Editor Retention:
Interesting to note that the average daily number of new articles has declined from a high of 2,132 in Jul 2007 to a low of 734 in Sep 2015, while the number of editors roughly doubled. BTW there are now 848 articles nominated for deletion through AfD outstanding discussions, many if not most, of which have been re-listed for lack of participation. I bet once other XfD deletions are counted we could be talking about thousands of nominations for deletion. Ottawahitech (talk) 03:11, 21 November 2015 (UTC)please ping me[reply]
Did you consider that there is a ceiling of articles? Yes there are always new notable subjects however a vast majority of subjects have articles about them already. The key is ensuring quality over quantity now. Mrfrobinson (talk) 00:57, 22 November 2015 (UTC)[reply]
That is not even close to being true. The vast majority of notable topics have no article. We can't even match the coverage of old 'premier' general encyclopedias like the 1911 Britannica or the 1885 Dictionary of National Biography, let alone the vast number of works with a narrower focus. James500 (talk) 01:24, 24 November 2015 (UTC)[reply]
I agree with Mr. Robinson, @James500:. Most of the articles that should be created have. And whereas we may not have as in-depth coverage as Britannica 1911 or Biography 1885, I think, if you looked, you'd find that nearly all the entries in those tomes have entries here. pbp 15:50, 26 November 2015 (UTC)[reply]
I did check. We are missing a huge chunk of the 1885 DNB. See the missing articles wikiproject. James500 (talk) 16:56, 26 November 2015 (UTC)[reply]
We are? Because when I thumbed through Epitome 1, I got maybe 450 bluelinks and less than a dozen redlinks, most of which were for articles that appear at slightly different names. Wikipedia:1911 Encyclopedia topics also notes that every single 1911 encyclopedia topic has an article. pbp 17:13, 26 November 2015 (UTC)[reply]
If you look at Wikipedia:WikiProject Dictionary of National Biography/Tracking, you will find to your horror that there are more than six thousand articles missing from the 1885 to 1912 DNB. The situation for later supplements, and for the ODNB is likely to be much worse. The epitome is misleading because some volumes are far more complete than others, due to 'drives' to finish certain volumes in a few cases. James500 (talk) 22:03, 3 December 2015 (UTC)[reply]
@Purplebackpack89: you said I see people AfDing a lot of articles in hopes of gaining adminship to be a relatively minor issue, but I would like to convince you that you are mistaken. Here is some data to substantiate what I am saying:
Of the most recent candidates in wp:Requests for adminship five out of the seven had kept at least one log of articles they had nominated/proposed for deletion. To illustrate the type of logs:
Ottawahitech (talk) 04:31, 3 December 2015 (UTC)please ping me[reply]
@Ottawahitech: You're looking at it in the wrong manner. The reason I see it as a relatively minor issue is because most AfD nominations and votes come from people who aren't seeking adminship. However, I will say this: it makes perfectly good sense to expect a person to know a little about deletion before giving them the power to delete articles. pbp 13:41, 3 December 2015 (UTC)[reply]
@Purplebackpack89: You said most AfD nominations and votes come from people who aren't seeking adminship, so I wonder how you know this to be a fact? BTW the reason I started speculating that many/most deletion notices are generated by wannabe wp:Admins was because of notices I have received on my own talk page over the years. Ottawahitech (talk) 15:46, 4 December 2015 (UTC)please ping me[reply]

I oppose all attempts to make WP:BEFORE mandatory. Experience has shown that it is primarily used as a weapon to attack deletion nominators. It is commonplace for keepmongers to claim a nominator hasn't looked for sources, when it is in fact just a disagreement over the suitability of what trivial and marginal sources there are. Most of BEFORE's checkbox style hurdles are not relevant to the majority of AfDs anyway. Really, all that is expected of nominators is that they produce a coherent argument for why an article should be deleted. Reyk YO! 12:28, 23 November 2015 (UTC)[reply]

@Reyk: you said Most of BEFORE's checkbox style hurdles are not relevant to the majority of AfDs anyway so I wonder if you would elaborate:

Some version of BEFORE should have been made a (behavioural) guideline long ago, for the sake of clarification at least, but many of the steps it requires are compulsory under other policies and guidelines anyway. I think I should point out that some deletionists are in the habit of falsely accusing those !voting "keep" of not looking for sources, when it is in fact just a disagreement over the suitability of what non-trivial non-marginal sources there are. I cannot actually recall any instance of a 'keepmonger' doing the same though, although some deletionists may be in the habit of deliberately pretending to be blind, claiming that no sources whatsoever exist, when they obviously do, and demanding direct links (urls) to sources that come up immediately with obvious search terms in GBooks, GNews, GScholar, JSTOR, Highbeam, etc, or are even cited in the article, that they must be able to see (unless they really are blind), in order to waste time and be obstructive. James500 (talk) 01:24, 24 November 2015 (UTC)[reply]

I agree James500 and Ottawahitech that WP:Before is very important. I have personally been involved in several AfD's where once a good search was done, turned up that the article was indeed very notable. Anyone who can't be bothered to do WP:Before is doing Wikipedia wrong since we're supposed to be building an encyclopedia with verifiable information. If you can't verify that the article is non-notable, how can you even nominate it for deletion in good faith? Megalibrarygirl (talk) 00:40, 26 November 2015 (UTC)[reply]

Wikihounding (WP:HOUND) of inclusionist editors is a fact. There are deletionists who will identify an editor whom they consider inclusionist and then follow that editor around the project, typically in small groups, though they have a talent for getting opportunists to help them now and again, systematically opposing and obstructing everything that they do. The wikihounding does not stop at XfD, as the deletionists will rack their brains to come up with other complaints, frequently absurd, which serve as a proxy for inclusionism, and as an excuse to keep following. The wikihounding is typically accompanied by other misdeeds, such as personal attacks and other off topic comments, canvassing and meatpuppetry. They target one editor at a time in an effort to isolate that editor from other inclusionists. They certainly intend to make editing impossible for that editor, and they probably hope to make editing so unpleasant that he will simply retire. Only a person with superhuman eternal patience could continue editing in the face of this kind of campaign. I know for a fact this happens. It is a fact. James500 (talk) 05:29, 26 November 2015 (UTC)[reply]

@James500:, re: your Wikihounding claims: 1) There are often editors who have made dozens of poorly-sourced articles, in which case it makes sense to take a close look and their contributions, and to admonish them for creating poorly-sourced stuff, and 2) To say that inclusionists have never done anything wrong is not entirely accurate. There are inclusionists who flood AfDs with "keep" votes. There are inclusionists who try to have deletionists blocked. pbp 15:50, 26 November 2015 (UTC)[reply]
That isn't the sort of scenario that I am talking about. I'm talking about people being hounded, for example, for expressing perfectly reasonable policy based opinions that the deletionists simply did not want to hear. And some deletions should be blocked. James500 (talk) 16:56, 26 November 2015 (UTC)[reply]
And there are people who do that to deletionists... pbp 17:13, 26 November 2015 (UTC)[reply]
In practice, that never happens. Deletionists who view Wikipedia as a computer game are far more likely to misbehave. Because they are WP:NOTHERE. James500 (talk) 22:03, 3 December 2015 (UTC)[reply]

Wikipedia doesn't want you! How Deletionists are making sure Wikipedia Isn’t awesome. When articles such as this are being written... Wikipedia we have a problem!!! --MurderByDeadcopy"bang!" 17:29, 26 November 2015 (UTC)[reply]

  • The only part about that essay that is really part of the situation is noting that en.wiki's definition of "notability" is not 100% consistent with the standard English definition, but there's been perennial attempts to find a better name without any success. We have come to be short to say "So and so's not notable" without actually saying "So and so's not notable, as defined by WP:N", which can be confusing to new users (though here, this writer was not a new user by their admission, so I've got a hard time understanding how they never had to encounter WP:N before). That's something to work to improve for all involved. But past that, they are mistaken about the purpose of WP, as we're not here to document important people, we're not a who's who, but a tertiary source that summarizes other sources; we're here to document what reliable sources say about people (in the case of BLP), and if no reliable source covers that person, regardless of their importance in their field, then we can't either. --MASEM (t) 21:10, 26 November 2015 (UTC)[reply]
  • Nothing on en.wiki is consistent, WP:IAR! What I see here is three gigantic problems
  1. Wikipedia is actively making writers mad. Writers write... so I foresee more bloggers writing about their experiences on Wikipedia... oops!
  2. Eventually, the only writers willing to stay in this atmosphere are paid editors.
  3. It's an excellent way to run off new editors fast. So Wikipedia needs to decide, "How few editors does it need to survive?" Or, "Is all that donation money eventually going to go to paid editors after most of the volunteer editors are gone?" Because that's what expect will happen along with paid ads. It's only a matter of time. --MurderByDeadcopy"bang!" 21:41, 26 November 2015 (UTC)[reply]
Deleting articles may cost us editors. Keeping bad articles certainly costs us readers. For every blogpost like the one you've cited (and I admit that one does trouble me a little; mostly because I think 2-3 unimpeachably reliable, independent sources should be sufficient), I could easily find ten from the era when there were no rules and Wikipedia was a haven for misinformation. And article deletion is hardly the only thing that has sent editors away, @MurderByDeadcopy: Many editors just leave because real life gets in the way. pbp 21:57, 26 November 2015 (UTC)[reply]
@MurderByDeadcopy: Thank you so much for providing the link to Wikipedia Doesn’t Want You, as well as alerting me and others to this thread a few days ago. If anyone is interested here are the links to both AfD discussions mentioned in the article:
Ottawahitech (talk) 04:52, 27 November 2015 (UTC)please ping me[reply]

Nobody has given anything except their impression of the sense of "culture of AfD", so it is hard to comment. Firstly, "no consensus" at AfD results in keep, unlike WP:ONUS inside an article, which results in removal of content, which is already a bias against the "deletionists" (totally misleading label). Secondly, it is by no means clear that having a separate article is the best way to work towards the goal of "sum of all knowledge". Knowledge must also be presented in context. Articles can often be merged (or even better, not created in the first place, because they are needless or POV forks) to give context and relate it to other articles. Thirdly, many BLPs are barely disguised attack articles. See this for an example. They are better off deleted than existing. Fourthly, if something is deleted "too soon" it can always be created later. Fifthly, there is no evidence that deleting articles is a major cause of editor attrition. I would bet that many more edits of newbies are reverted than articles deleted, because article creation is a rather high barrier to surmount. Kingsindian ♝♚ 21:36, 26 November 2015 (UTC)[reply]

Thank you for your comments, @Kingsindian:. I agree with them. pbp 21:57, 26 November 2015 (UTC)[reply]
  • Since we're discussing concerns about AfD, I'll toss in a few concerns I have. Perhaps it would be helpful to clarify a couple things in advance: I fall into the inclusionist camp (although I would consider myself an anti-deletionist), and I edit mainly professional wrestling articles. If you feel the need to dismiss my concerns because the latter makes you view me as a teenage fanboy, I can't stop you, but I can tell you that I'm neither a teenager, nor do I watch professional wrestling. Anyhow my main concerns are (1) People nominating articles for deletion because of a perceived lack of importance rather than notability, (2) Closing administrators (or non-administrators) giving a verdict based on votes from the beginning of the discussion, without taking any notice that the current version of the article has received substantial attention and bears little resemblance to the article at the beginning of the discussion. The closing rationale is often a single word—"Delete" with no indication that the administrator has done more than count votes, many of which are no longer relevant. Concerns voiced to that effect are then met with a dismissive "Take it to a deletion review", (3) The lack of sources in some articles isn't because of a lack of effort on the part of editors but rather that they have joined a project with thousands of articles and can only work on a limited number at a time; when someone comes along and starts an AfD, it creates a deadline that forces people to drop what they're doing and come like a trained monkey, and (4) Banned users are allowed to initiate deletion discussions; yeah, sure, banned users aren't allowed to edit at all in theory, but I have pointed out obvious sockpuppets of banned users that have initiated discussions and the response has always been "Yeah, well, they really shouldn't be editing, but let's see how the discussion plays out anyway". To allow banned users to have any say on what is discussed or edited within any time frame is an obvious failure on the part of Wikipedia administrators. When a banned user is found to have created an AfD, the discussion should be closed immediately. We are not here to do the bidding of people who have violated the community's trust to the extent that a ban has been given. GaryColemanFan (talk) 17:00, 29 November 2015 (UTC)[reply]
👍 Like Ottawahitech (talk) 18:28, 29 November 2015 (UTC)please ping me[reply]
I like most of this. Not the first, because there are other reasons to delete in addition to lack of notability. Articles that maybe perceivedas unimportant usually do fall under one or another of the provision of NOT. And for that matter, so do many that clearly meet the GNG. A gooddeal depends on just how you interpret the reliability of the sources and the requirement for significant coverage. But for point 2, yes, it is necessary to close looking at the actual discussion and article, and closes that do not are frequently overturned if brought to Deletion Review. As for 3, Yes, the lack of sources on older articles is about 3/4 those that could be sourced easily enough if someone went to the trouble, and 1/4 those that could not. Our standards were much lower in the beginning about both sourcing and notability. Especially in the beginning, and still continuing, article writers wanted to start new articles, not necessarily finish the job. As for 4, yes, this is a misinterpretation of Banned means Banned, but there is of course nothing to prevent any editor seeing this to then renom the article themselves. DGG ( talk ) 20:28, 30 November 2015 (UTC)[reply]
Based on that paragraph, it appears articles get nominated solely on perception. And I agree. There is way too much I don't like it going on at AfD, therefore it must be deleted! (There's also some, I don't know anything about it too!) As for article writers wanting to start new articles but not finish them, well, that is the whole point of Wikipedia. Wikipedia was created for everyone to work on the same article, not one person. The original point of Wikipedia was quantity, not quality. Nupedia was created for quality, however, quality takes time along with consulting experts and those are two things that Wikipedia vehemently abhors! --MurderByDeletionism"bang!" 17:39, 1 December 2015 (UTC)[reply]
There is a problem of noms that seem to be "I don't like it" (A major arbcom case of this nature involved the editor TTN; off the top of my head the arbcom case was "Characters and episodes 2" which is good bg reading on this), and when there is a clear pattern of an editor nominating a lot of articles without care, it creates fait accompli that we discourage, and this is behavior we should aim to stop. But as outlined in this discussion, that's only something that can be judged by reviewing patterns, not by hard numbers. Also, while Wikipedia may have been formed based on quantity, we clearly are more focused on quality now, as the rate of new article generation (ignoring any subsequent deletions) has slowed down, despite estimates that millions of potential topics of academic interest could still be made. We know AFD is harsh which is why editors are encouraged to sandbox articles or use AFC to get articles that won't be quick AFD targets from the start, getting the quality there before its put into mainspace. --MASEM (t) 17:49, 1 December 2015 (UTC)[reply]
There's an interesting statistic rough guess, derived from counts I make from time to time from log samples, and confirmed by several people at the foundation: for the last 8 years at least, about half the articles submitted end up being kept in WP, and half end up deleted by one process or another.[citation needed]Ottawahitech (talk) 23:33, 1 December 2015 (UTC) DGG ( talk ) 20:28, 30 November 2015 (UTC)[reply]
Statistics like this are worthless! One doesn't even know the time frame for said statistics. Or what is being included by the term articles submitted. Is AfC included? Speedy deletes? Etcetera, etcetera... --MurderByDeletionism"bang!" 17:39, 1 December 2015 (UTC)[reply]
@MurderByDeadcopy: It's very difficult to have a rational conversation with you when you refuse to believe any of the statistics other editors bring up. @DGG: When did it become 50-50? Last I heard it was 70-30 delete. pbp 18:30, 1 December 2015 (UTC)[reply]
My count is made from looking at the rate of submissions to New Page feed per hour at various times of day, and comparing it with 1) the overall growth of articles. and 2) the rate of deletions in the log. I really shouldn't call it a statistic--it's a rough estimate. Trying to verify it, I realize the matter is more complicated, because of AfC; a new count would have to specify whether we ignore Draft space, or include pages started there and submitted, or include all pages started there. I think the 30% might be the proportion speedy-deleted--my estimate included only articles not deleted by prod and AfD as well. urplebackpack89, doyou know of any other count? DGG ( talk ) 20:43, 1 December 2015 (UTC)[reply]

Proposal

The following discussion is closed. Please do not modify it. Subsequent comments should be made in a new section. A summary of the conclusions reached follows.
Per WP:SNOW - 60 days is long enough. Community clearly opposes this proposal. (non-admin closure) Ivanvector 🍁 (talk) 16:51, 15 December 2015 (UTC)[reply]
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

To solve the issue with disingenuous *fD nominations, done without proper research. After an editor has had made ten unsuccessful *fD nominations they are blocked from making any new *fD nominations for a week. After an additional five unsuccessful *fD nominations, they are blocked from making *fD nominations for two weeks. After an additional five unsuccessful *fD nominations, they are blocked from making *fD nominations for a month. After an additional five unsuccessful *fD nominations, they are blocked from making *fD nominations for 2 months. After an additional five unsuccessful *fD nominations, they are blocked from making *fD nominations for 6 months. After an additional five unsuccessful *fD nominations, they are blocked from making *fD nominations for a year. After an additional five unsuccessful *fD nominations (that would be 40 unsuccessful AfD nominations, an obvious, disruptive pattern, over almost a 2 year period of time), they are permanently blocked from making *fD nominations.. Trackinfo (talk) 21:53, 16 October 2015 (UTC)[reply]

@Trackinfo: That's an intriguing proposal that I happen to think is a good idea, but I think it may be a stretch since it's an after-the-fact sort of thing and since it may be seen as new policy. From my short stint in AfD, it seems to me it may be wiser to address the problem before it happens and more editors are railroaded out of Wikipedia. Only a handful of folks in AfD even make a pretense of following WP:BEFORE, marking pages within moments of their creation. They should have to go through a multi-step questionnaire of the type used for image uploads or new-user page creation to ensure they're complying with the policy that already exists. Few people could argue with enforcing existing policy. --69.204.153.39 (talk) 23:12, 17 October 2015 (UTC)[reply]
What I am proposing is a system to enforce policy. With a penalty awaiting, it might make some people think twice about an un-researched nomination. It might also make them learn better Google search technique. I am constantly confounded by low quality editors who make strong statements in an AfD argument * this is all I could find. When I add a dozen sources, that not only demonstrates the error (malicious or otherwise) in their statement, but should also advertise their incompetence in doing research. On many articles we are starting equally with our feet flat on the ground, they don't know the subject they are attacking, I don't know much about the subject I am defending. It shouldn't be about heroism to rescue the article. If they actually cared about the content on wikipedia, it shouldn't be an adversarial process. It should be plainly that anyone can see the subject meets wikipedia standards and deserves to be here. Trackinfo (talk) 09:17, 26 October 2015 (UTC)[reply]
I hate to even mention this, but those who object to wholesale deletion might want to consider checking RfA nominations for deletion history, and voting accordingly. I'm fine with the deletion of material that violates WP:COPYVIO and WP:BLP (assuming the problems cannot be fixed with a scalpel -- or chainsaw), and also material that is overly spammy or otherwise clearly meets the speedy deletion criteria, but most other issues with articles can be fixed by editing the article, rather than by deletion. RfA is already a confused mess, but denying the mop to those who prefer deletion over correction of issues might make a difference. Someday. Etamni | ✉ | ✓  03:23, 5 November 2015 (UTC)[reply]
  • @Trackinfo: This seems to penalize a) people who nominate a lot of pages for deletion, and b) people who just get unlucky. Also, it makes it seem like the only reason deletion nominations fail is because BEFORE isn't followed (and IMO, that's OK; BEFORE is onerous and need not be mandatory). As such, I'm going to have to oppose this. pbp 17:26, 12 November 2015 (UTC)[reply]
It certainly is aimed at people who make frivolous nominations. That IS a problem. There is a crowd who do it for sport, which apparently prompted this discussion long before I got involved. I hate to suggest a remedy, but if there is legitimate cause for a failed AfD not to be counted against the nom, perhaps the closing admin can make such a notation to the record at that time. As with any penalty, it needs to be applied with reason. Elsewhere I do criticize other editors for their ineptitude in performing a Google search. Perhaps I have to high an expectation of intelligence from wikipedia editors. But WP:BEFORE at least demands that they lift a finger. I've had the statement on my page for a long time. I am upset with those who attack articles they do not understand. So spend a moment reading before you attack. If you completely miss the first time, perhaps a more refined search is necessary. And hey, if you find sourcing that the posting editor didn't mention, add in a proper source. Help the wikipedia project. Do something good with your time. There are a lot of other people inconvenienced by a single person initiating the AfD or *fD process. Do so with purpose. Uninformed, incompetence is not a good purpose. Trackinfo (talk) 06:57, 13 November 2015 (UTC)[reply]
No comment on this proposal, but I strongly agree with this particular statement. —⁠烏⁠Γ (kaw) │ 08:17, 13 November 2015 (UTC)[reply]
"But if there is legitimate cause for a failed AfD not to be counted against the nom, perhaps the closing admin can make such a notation to the record at that time." I hope you realize how insanely bureaucratic you're making everything. I also think your most recent statement is far too harsh on nominators of AfDs. I think it's wrong to tell people they have to spend their time sourcing articles, and this proposal comes too close to doing so. pbp 13:49, 13 November 2015 (UTC)[reply]
Furthermore @Trackinfo:, I still say that you're ignoring the myriad of reasons an AfD can be closed as keep. It can be closed as keep because of a disagreement of what's a source and what isn't. pbp 13:58, 13 November 2015 (UTC)[reply]
So in your statement, you are saying you do not believe in WP:BEFORE. You expect that you (or any other nominator) has all the knowledge they need in their own brain and do not need to use any assistance to determine if an article is legitimately valid or not. That's not the way wikipedia works. We depend on WP:V. That certainly should expect that someone who posts an article should do so with sources, but we all realize that is not the case. Particularly novice editors don't know how to add sources. It doesn't mean their content is not valid. it means they have not adapted to the format of wikipedia contributions. So when you see an article on a subject you don't recognize, what would you do? I know everything, so nominate it for an AfD, right? WP:BEFORE says you should lift a finger, do a little research, find out if this is legitimate. So after learning that a subject is legitimate, then you go on to nominate it for AfD, right? Preposterous. You now know it is legit. Fix the d#$! article. Sure there are borderline cases of notability, which will generate arguments. Even then, if you are consistently on the losing end of the argument, you need to adjust your criteria before you inconvenience all the other editors who have to do research and comment. The point being, if you are a consistent Loser, then there is a problem with your standards for nomination. You have a decision making problem. You can't recognize good from bad. We have disputes all the time on what content is valid. Ultimately somebody has to step in and make the final decision, that the consensus results are . . . And that person is ultimately the best judge also to answer the question; Was that nomination well-founded, in good faith, a marginal argument? Did hidden new evidence come in to sway the case? Or if not, that the *fD was made without BEFORE research, in bad faith and was a waste of time for all involved. Trackinfo (talk) 23:36, 13 November 2015 (UTC)[reply]
People often post things that aren't in line with policy: gossip, non-reliable sources, random stuff based on speculation, BLP violations. The end result is that we fix the problem and tell the editor they need to do what policy requires, we don't say we should require that someone who see something based off facebook should conduct their own WP:BEFORE examination and see if a reliable source also says the same thing before we remove that content. -- Ricky81682 (talk) 11:07, 14 November 2015 (UTC)[reply]
@Trackinfo: You're looking at BEFORE in the wrong way. What you're basically saying is that if somebody wrote a poorly-sourced article, I (or any other article patroller) have to spend my time trying to fix it, above and beyond not just nominating it for deletion, even if it's clearly beyond hope. You're being really cavalier with the time of me and other deletionists. You can't, and shouldn't, force people to spend their time a certain way. Furthermore, you assume that anybody who gets up to the thresholds you mention is a "consistent Loser". If you nominate 100200 articles for deletion, and fiveten of them are kept, you have a 95% correct rate...and you still face punishment in your proposal. pbp 13:51, 14 November 2015 (UTC) I fixed your math, PBP. Cheers. Dirtlawyer1 (talk) 16:17, 14 November 2015 (UTC)[reply]
First off, who is making 200 nomination at a time? What kind of quality editing are they accomplishing in that rush? If an editor is making that volume of *D's how could they possibly consider the validity of each article? What they are doing is throwing their few seconds of consideration, into a pile that now become a headache for a whole bunch of editors to spend time to consider. Maybe they found a treasure trove of bulk bad articles by the same editor. Is that something that requires individual AfDs or can that be taken to a bulk discussion about the group. And yes, there have been editors who have deliberately overwhelmed the process by doing exactly that. Essentially I don't like an entire category, so they nominate every article in the category. So in general, I think it is inconsiderate to the wikipedia community to submit that many nominations or even to have that many in play. You can't possibly give each nom its due attention. Trackinfo (talk) 21:47, 14 November 2015 (UTC)[reply]
Who said anything about "at a time"? The way your proposal is worded, @Trackinfo:, you could be sanctioned for ten failed RfDs ever. Let me ask you a question: Do you have a conception of what percent of AfDs are closed as delete and what percentage are closed as keep? And therefore, how many RfDs a particular editor would, on average, have to amass before he had ten that failed and hit your first sanction? At an absolute minimum, you need to link the number of failed RfDs to either a) a particular time period, or b) a number of total RfDs started, though I'm not even sure your proposal is salvageable even when you do that. You also scoff at starting many distinct RfDs all at once, but there are situations where that is appropriate. pbp 22:47, 14 November 2015 (UTC)[reply]
  • Oppose Disruptive AFD nominations can be determined and it's not based on a count. For example, there's a massive number of deletion regarding biographies of the world's oldest people. Are they disruptive? If you look at the current ones, they are coming up keep. If you look at the archives, you'll see that they were all deletes, then redirects and now keeps, but the votes are exploding in volumes from editors who haven't edited here in years (and based off messageboards and the like on the subject). Been a decade of ARBCOM sanctions and the like for that fun. Ultimately, someone who nominated five articles a week ago will look like they're in the right, today they are disruptive. That's not a way to settle things. -- Ricky81682 (talk) 11:07, 14 November 2015 (UTC)[reply]
  • Oppose - It is the article creator's responsibility to include reliable sources to verify the article's content. It is the article creator's responsibility to ascertain whether the article subject is notable with significant coverage in multiple, independent reliable sources. It is the AfD nominator's responsibility to perform the WP:BEFORE homework to see if there are obvious online references that support the article subject's notability. It is the burden of AfD "keep" !voters to demonstrate the subject satisfies the notability and other suitability guidelines for a stand-alone article. This proposal turns those responsibilities upside down, and reverses the burdens of responsibility. And I am happy to compare my AfD record -- as a participant, nominator, and occasional article rescuer -- with anyone. I am neither an inclusionist nor a deletionist; I am an editor who believes strongly in enforcing the notability and other suitability guidelines as they were written and as they were intended, so that Wikipedia may continue to grow as a serious online reference and encyclopedic resource. Dirtlawyer1 (talk) 16:34, 14 November 2015 (UTC)[reply]
  • Whatever those who are Opposing here is just laughable. It's a deletionists market on Wikipedia so ten unsuccessful *fD nominations will never happen. What I'd be interested discussing is just how all those pro-deletionists expect to keep writers on Wikipedia since everyone here already knows exactly how to get rid of them! Also, AfD nominators are not doing the before work and no one on Wikipedia has a clue to what is and what isn't notable. What AfD has become is a haven to harass editors. --MurderByDeadcopy"bang!" 20:09, 16 November 2015 (UTC)[reply]
    • @MurderByDeadcopy: I ask the same question I asked of Trackinfo above: are you aware of the ballpark percentage at which AfDs pass? Your comments would suggest it's in the 90s, and it isn't. I also think you've over-estimate the amount of improper and bad-faith AfDs. pbp 20:24, 16 November 2015 (UTC)[reply]
      • I didn't actually put any % amount to the number of AfD's that pass, but you did which frankly suggests that that number could be 89%. My point is the ease with which an article gets deleted. In order to attempt saving an article one must explain their reason in full, then get cross examined multiple times along with being belittled, plus personal attacks, and followed all over Wikipedia while a vote to delete needs no more than a per nom explanation and viewed as heroic. --MurderByDeadcopy"bang!" 21:15, 16 November 2015 (UTC)[reply]
        • @MurderByDeadcopy:@Trackinfo: The % of AfDs that are closed as kept is actually closer to 30%, which puts the delete rate at about 70%. That means, on average, you'd only need to AfD 33 articles before you have 10 deletions that fail. (BTW, since you two are making such broad generalizations, you should be familiar with this stat). Also, not only do you exaggerate the behavior of deletionists, you make it seem like anybody who votes "Keep" is a saint. I've seen legions of bad "keep" rationales at Wikipedia. pbp 22:13, 16 November 2015 (UTC)[reply]
          • Putting up two numbers without more facts is meaningless. Are these numbers based on all AfD's since the beginning of Wikipedia? Because I'm more interested in the past year since I believe AfD has changed greatly over time. I also consider anyone who votes a "Keep" vote a gutsy move on Wikipedia since it's quite apparent that anyone who does so gets to be openly and unrelentingly harassed by all who vote delete. But I don't believe that is something you can possibly understand since you've only voted "Keep" once two years ago in 2013[2] which puts your delete stats at 98.6%! --MurderByDeadcopy"bang!" 23:57, 16 November 2015 (UTC)[reply]
            • I think your tool is off; I count 1, 2, 3, 4, 5, 6, 7, 8 times just since 2013. Also, it's not as gutsy as you seem to think...why don't you count in the last week how many AfDs were kept, since you only care about the here and now? Get some real figures instead of just going with your instinct. pbp 05:01, 17 November 2015 (UTC)[reply]
              • Seems like your statistics are suggesting an arbitrary randomness to Keeps. Maybe that would be the case with thoughtless *fDs, which is exactly what we are trying to prevent. Perhaps I can't relate. I've been editing for over 8 years and in that time I have accumulated zero failed *fDs. Of course, I've spent a lot of time on the other side, fighting off bad *fDs, into the thousands. That's a lot of effort, for a lot of bad nominations, each one of them that could have been solved the same way I saved them, by googling the subject of the article, finding sources usually in the first page (some have too much non-reliable social media at the top so I have to go deeper) and posting them. I've lost a few, mainly on notability grounds because even though you can post a lot of sources, it devolves into opinion. The key issue is, a lot of these articles were originally poor posts by the original editor. Many were novice editors, others were inconsiderate bulk editors who just didn't spend the time to back up the content they were posting. Sure the original editor could have done better, but we can't expect that of novices. Certainly I'd like to retrain the bulk unsourced stub posters. But do their failures mean wikipedia content, the subject of the article, needs to suffer? Isn't a valid stub superior to a red link (we know nothing about this subject), non-existent link, or worse yet, a subject with perceived salt from its one time deletion due to a poor original poster? Those are the ramifications of deleted *fDs. We are building a knowledge base. But that concept does not succeed if legitimate content is deleted thoughtlessly. We are supposed to be editors. The meaning suggests there is thought behind what we do. Trackinfo (talk) 21:49, 17 November 2015 (UTC)[reply]
                • The problem, @Trackinfo:, is that you're arguing that novices (and bulk editors) need to do less work at the same time you're saying noms need to fix articles instead of nominating them for deletion. You're unfairly shifting work from one (or two) group to another group. As for "isn't a valid stub superior", that depends. Remember that if it isn't sourced, you don't know if anything in it is true/legitimate. We shouldn't leave unsourced stubs up for eternity on the off chance somebody is going to source them. pbp 15:50, 18 November 2015 (UTC)[reply]
I am not pinning extra work on a "group" of people, that is what an improper *fD does. I'll separate the two categories of problem editors. The novice, yes, they should be given a pass, They don't know better. You as the lone, experienced editor arriving on their poorly written or poorly sourced article have a choice to make. 1) Do nothing, as your predecessors have done. I assume you are too activist to let that go. 2) Directly nominate it for *fD; in one lazy step turning your casual observation of a poor article into a problem for the handful of people who notice it in the *fD listings over a few weeks of the process. Finally some admin needs to sort through the mess of comments and improvements to the article and decide what to do with the article. 3) Or you can do a google (or search engine of your choice) search and find out about this subject. You will then know if it is BS (and if its BS, find a way to speedy it and save everyone the problem). If it is legitimate, then you, with your new knowledge and experience as an editor can fix the article. Now it doesn't need to bother other people and the problem is solved. Your little bit of effort saved everybody else their time and trouble. The only time something needs to go through the process is if it truly is a marginal subject. I would go further to suggest, you ought to know the broader subject surrounding the subject in question, to know how it relates. Is this a necessary definition. Is there more to hang onto this subject? If you don't know what you are talking about, butt out. Go back to step 1. The other problem editor is the bulk editor leaving lots of stubs. I believe in cross-referencing. So someone leaving a string of stubs is still helping the greater good. If they are unsourced, that person needs a good talking to. We do have talk pages for that purpose. But because they created a poor article about a valuable subject does not mean it needs to be deleted. I've found a bunch of editors who create stub articles about names in lists of similarly related prose. Each of that cast of characters has a claim to notability based on their participation in something that puts them on that list. A few seconds of google answers this question. In that process, what do you have in your hands? A source. Copy, paste and now the article is sourced. Better yet, now you know something that is not posted on wikipedia. Write some prose, fill in the blanks. You made a handful of edits, improved wikipedia and saved everybody else down the line, the extra work doing the same steps you should have done. And seriously, the amount of time it takes to do that is probably less than all the proper steps to submit an *fD. WP:BEFORE solves everything. Needlessly submitting something to *fD shows your laziness, ineptitude and/or your feckless attitude towards both wikipedia and your fellow editor. Trackinfo (talk) 22:23, 18 November 2015 (UTC)[reply]
@Trackinfo: Setting aside the fact you essentially want to completely dismantle the *fD process and fill Wikipedia with loads of unsourced and potentially inaccurate information, you consistently overestimate the amount of time spent by people because an *fD is created, while at the same time consistently underestimating the amount of time it takes to fix articles. Fixing articles take a lot of time, and deletionists should not be required to do it. One of the principles of Wikipedia is that editors get a choice of what they are allowed to edit, but you want to take that choice away from deletionists. pbp 13:45, 19 November 2015 (UTC)[reply]
That is a complete misrepresentation of what I am saying. Where have I EVER encouraged unsourced articles? I am saying exactly the opposite. When you find an unsourced or poorly sourced article, WP:BEFORE says to do the simple step of researching the subject before you blindly cause other people the trouble of dropping it into *fD. I can state from having done so thousands of times myself, its not that hard to do. Yes, you can choose what you choose to edit. What you should not do is choose to make an uninformed nomination for a *fD. So after googling the subject, having learned something about the subject and evaluating its worth, now it is your choice, to do nothing (which doesn't help wikipedia), to be stupid and nominate legitimate content for *fD, or to copy/paste the source into the problem article. If you choose to be stupid, stupid by ignoring facts that are now on your screen, your laziness is causing trouble for all the editors who follow you. By this proposal, yes, I want to penalize editors for deliberately choosing to be stupid. *fD should be used to get rid of the garbage that is too well done to speedy. None of this discussion is about keeping garbage. Unless you are already an expert, most nominators are NOT, you don't know what you are doing until you have done WP:BEFORE. Trackinfo (talk) 17:36, 19 November 2015 (UTC)[reply]
              • First off, these stat's and numbers issue is what you interjected into this conversation, not me. The above paragraphs only proves my point which is that numbers can be thrown around indiscriminately in a hugely meaningless way. But what I do interpret about all these numbers is a clear-cut way to dodge the issues I have with AfD's.
              • Second, my main points are the ease with which AfD's get deleted... and the enormous difficultly it is to save an article once it gets nominated. The environment one faces in just attempting to save an article from deletion. The harassment, personal attacks, hounding, vengeance, and the issue that the more actual facts one finds that an article should be saved, the more the deletionists double-down into some sort of backfire effect. Deletionists win by badgering and threatening editors who attempt saving an article until they are completely exhaustioned knowing that they can (and will) re-nominate the article at a later date. --MurderByDeadcopy"bang!" 22:05, 17 November 2015 (UTC)[reply]
                • Keep in mind what you are stating above are all arguments generally refuted as arguments to avoid at AFD. There are some editors that nominate articles at AFD willy-nilly which might be questionable, but there are also editors that rapidly create articles with no effort to justify why we should have articles on those topics. The process is self-correcting. Also, I strongly caution against calling people nominating articles at AFD as "harassment". Yes, there have been cases of an editor being petty or going after another editor and nominating articles in bad faith, which is edging on harassment no doubt. But editors that are nominating articles at AFD in good faith, that's far from harassment. --MASEM (t) 03:06, 18 November 2015 (UTC)[reply]
                  • Of course, it's not all AfD noms! Nor do I see rapidly created articles - that sounds like a relic from the past (unless it's a bot). What I'm referring to is the generally accepted environment within AfD along with my own personal experience of being hounded and tag teamed until I was run off even attempting to rewrite an article to save it. Odd thing is, I was finding actual facts for that article, but I've since learned that the more evasive and elusive my reasons to "keep" an article are, the better the odds become that that article gets kept (well, until its next nom anyway). --MurderByDeadcopy"bang!" 04:35, 18 November 2015 (UTC)[reply]
                    • Without having diffs or links to AFDs to know what you are considering hounding and tag teaming (which I have seen before but it is a rarity and usually obvious enough when it happens). More often, it is a newer editor that feels that editors are ruining their work by nominating it for AFD and fight tooth and nail and consider any opposition (read: deletion) as an afront and bitterly complain, when those opposing/!voting "delete" are well within policy to point out such problems. --MASEM (t) 04:41, 18 November 2015 (UTC)[reply]
                      • Now that I've been tried and condemned (but I'm not surprised) I see zero reason to continue this conversation so, Have a nice day! --MurderByDeadcopy"bang!" 05:09, 18 November 2015 (UTC)[reply]
                      • @Masem: you said More often, it is a newer editor that feels that editors are ruining their work by nominating it for AFD and fight tooth and nail and consider any opposition (read: deletion) as an afront and bitterly complain, when those opposing… are well within policy to point out such problems.
                      • What in your opinion should be done in such a situation when a new editor is fighting tooth and nail to save "their" article which does not conform with wiki-standards? Ottawahitech (talk) 14:35, 18 November 2015 (UTC)please ping me[reply]
                        • Encourage them to use draft or user space to develop the article first, or use WP:AFC to help see if the article proposed is appropriate, instead of jumping in feet first and getting burned when they haven't spent time understanding our processes. --MASEM (t) 15:20, 18 November 2015 (UTC)[reply]
                          • @Masem: you said Encourage them… but this is easier said than done: here is an example of what happened to new editor User:WhitetTara
                            • The article she(he?) wrote about Filiz Cicek was deleted 3 times through a wp:speedy: twice as “No explanation of significance” and a third time as a ‘’Unambiguous copyright infringement: no evidence of notability’’
                            • Between Feb 1, 2014, 5:28 - Feb 5, 2014 s/he expended enormous effort to try in good faith to figure out what the problem was, but apparently gave up and left wikipedia after her last edit.
                            • Here is what users like me who do not possess wiki-admin-eyesight can see about User:WhitetTara:
                              • Live edits: 32
                              • Deleted edits: 120
                              • Total edits: 152.
                            • all in the span of 3-4 days. Ottawahitech (talk) 16:59, 18 November 2015 (UTC)please ping me[reply]
                              • Looking at the article and user talk page, this is probably a bad example: WhitetTara appeared to have a connection with Filiz Cicek (based on the user's talk page), and had basically created the article with a copyrighted resume, and while the user claimed to have gotten permission from Cicek to use it. The last deleting admin did try to work to help provide information, so it wasn't an unanswered cry for help; the page was userfied, the user informed and then... it was never acted on. I don't see that as being chased off, just more.. frustration? even though everything was teed up to help. Mind you statements like this do not inspire me that WhitetTara's purpose was wholly to build an encyclopedia, and that often happens at AFD that people thinking they are coming to WP to right great wrongs have to justify keeping articles at AFD that fail to meet standards. Again, not a failure of the system, but the nature of editors wanting instant gratification instead of learning the ropes. --MASEM (t) 17:15, 18 November 2015 (UTC)[reply]

@Masem: you said I strongly caution against calling people nominating articles at AFD as "harassment"...But editors that are nominating articles at AFD in good faith, that's far from harassment
It may be in good faith and still feel like harassment to the party on the other side. Since you ask for a concrete example let me offer up one of mine. I have been doing work in an area of Wikipedia that, in my opinion, is in a mess, namely Patient Protection and Affordable Care in the United States. When talking about this area, understanding terminology like Platinum/Gold/Silver/Bronze plans is crucial. But in 2014 two of the redirects that I created for these terms were nominated for deletion. The other two also disappeared even though I did not receive a notification(IIRC) for the nomination.
I tried to participate in the deletion discussion in good faith, but felt I was mocked by the participants, or at least this is what it felt like since I could not follow what the other participants were talking about. Ottawahitech (talk) 14:49, 18 November 2015 (UTC)please ping me[reply]
                    • Looking at the AFDs, both the articles you created and the AFDs are all being done in good faith : you felt the terms needed separate articles, other editors disagreed, and when it was clear two of the four were set for deletion, a closing admin hit the other two. Nothing in the discussion looks like anything close to harassment, but simply what was a different between what you thought might have been notable and what community standards are, and that's not always a straight forward thing. I disagree in how the terms were deleted rather than redirected to a section on the PP article as they seem like reasonable search terms, but that's far from anything that any editor should take to be harassment or the like. There is a reason we encourage new editors to make their articles in draft/user space first so that they can learn the ropes of how we expect articles to be constructed, but a lot of editors want instant gratification, jump right in and get into a mess that they might take personally. --MASEM (t) 15:20, 18 November 2015 (UTC)[reply]
                      • @Masem: So you believe it is not insulting to use these words: Delete per WP:SOAPBOX. A Gold Card or Gold Plan is not worth the plastic it is embossed on. Ottawahitech (talk) 05:11, 19 November 2015 (UTC)please ping me[reply]
                        • It's not insulting to the editor, which is what I would expect if we're talking harassment. It's dismissive of the importance of the gold plan concept, but there is no attack to the editor in question. If that was a prolonged attitude over a long discussion there might be something to act one, but not one comment in one AFD. --MASEM (t) 05:26, 19 November 2015 (UTC)[reply]
                          • @Masem: So when one accuses you of using Wikipedia as a soapbox or means of promotion — that is not insulting???!!! Ottawahitech (talk) 05:56, 19 November 2015 (UTC){{Bigplease ping me}}[reply]
                            • In the context, no it's not. It's commenting on the contribution and not the contributor. It might be a bit harsh but that's far from violating any civility lines. If it was clear it was a new editor with good faith intentions, one might suggest expanding on SOAPBOX, but that's far from required. --MASEM (t) 06:00, 19 November 2015 (UTC)[reply]
                              • I think that the SOAPBOX claim may have been a little harsh; frankly it sounds like that editor is himself standing on a SOAPBOX. But that one contribution is hardly indicative of all comments at AfDs. pbp 13:45, 19 November 2015 (UTC)[reply]
                                • Certainly, WP has a whole can do a bit better at AFD discussions to avoid it being alphabet soup that newcomers may not understand (also taking a soapbox position on a talk page like AFD is not anywhere close to an issue as if it was written into a mainspace article; there's little actionable about it) But then when people cry that those that nominate AFD should engage in BEFORE, I can point that we should have new editors engaging in reading all relevant policies before creating their first article so they can prevent it going to AFD. And that won't happen; WP is geared towards having no such requirements. At the end of the day, all we can do is encourage more courtesy at AFD, but that's difficult if impossible to enforce. --MASEM (t) 15:28, 19 November 2015 (UTC)[reply]
Actually, then rather than a redirect, it sounds like a disambiguation page is the answer. I've created one for Gold plan, and an editor could create one for the other colors as well. (That said, as someone who has had a couple articles deleted rather than improved, I'm loathe to create them until I see whether this one survives. Thisisnotatest (talk) 13:12, 27 November 2015 (UTC)[reply]
I agree with Masem. The redirects you created are not analogous to the average article that ends up being deleted. Redirects are not articles: they operate on a completely different set of rules. The reason your redirects were deleted wasn't people believed "bronze plan" didn't mean a health care plan; it was because people believed "bronze plan" didn't only mean a health care plan. pbp 15:50, 18 November 2015 (UTC)[reply]
  • I'm with Masem and pbp on this as well. When a redirect gets nominated in a deletion discussion, it's necessary to give an opinion on the redirect's utility, and it's human nature to take offense when someone suggests deleting your work but that's what happens here sometimes. Those comments are not directed at you, they're commenting on the page. SimonTrew's might have been easy to misinterpret but believe me, his comment was not directed at you: pages can be soapboxes too. Also, sometimes RfD is a silly place, don't take it too seriously. Ivanvector 🍁 (talk) 16:44, 19 November 2015 (UTC)[reply]
@SimonTrew: Your name was mentioned here because you alluded to my edits as promotional. As I told user:Masem (see above) I felt you were mocking me during the deletion discussions here and here. BTW thanks for pinging me. Ottawahitech (talk) 11:08, 20 November 2015 (UTC)[reply]
I believe this is a problem present in many XfDs where a small group of editors are doing all the nominations, forming the discussion, and closing it as well. It appears there is little effort to locate subject matter experts to opine. Instead these XfD-insiders form a social clique with their own private rules where many nominations do not even state which guideline had been contravened by the page creator. This is certainly true in wp:CfD which unfortunately I am more familiar with than I care to, but appears to also be common in other forums such as wp:RfD. No wonder that the target editors of these XfDs feel outnumbered. Ottawahitech (talk)please ping me
Ottawahitech, I want to take your criticism seriously, because I've observed such behavior at CfD as well. There seem to be many unwritten standards that live only in the minds of active editors there. Now, mind you, in a consensus-driven project, that's not too far off from the way it should be. Write the standards down so they can be discussed and amended as necessary; it stars with patterns that may be interpreseted as "cliquish".
That said, your implication of some sort of conspiracy at RfD is worrying. Yes, we're among the most active editors at RfD, so it's not unreasonable that we communicate amongst ourselves and hold a lot of the institutional memory around there. But we've also all worked to write down the standards of RfD, especially at WP:RFDO. I explicitly started that page to describe how RfDs usually go, not to prescribe how they should go (compare to WP:AFDP).
You are welcome to become an RfD regular too. We'd be happy to have you. You'll get a better grasp on these issues, and you'll have more opportunities to make arguments for change where you think it's needed. But please don't spend your time trawling talk pages like that. You'll do better for the encyclopedia doing almost anything else. (And for what it's worth, I've had occasional off-wiki contact with some of those editors on other issues, but RfD is discussed in venues that are open to everyone. Transparency is very important to me.) --BDD (talk) 15:34, 23 November 2015 (UTC)[reply]
@BDD: In regards to But please don't spend your time…You’ll do better for the encyclopedia doing almost anything else — this is exactly what I am trying to do, add content, but the actions of many other editors who are flooding my user-talk-page with notices of nominations for deletion, have given me pause about the effectiveness of my contributions. Ottawahitech (talk) 21:52, 23 November 2015 (UTC)please ping me[reply]
@BDD: to this day I have no clue why four useful (to readers) redirects hit the bit-bucket and since you said we’ve also all worked to write down the standards of RfD, especially at WP:RFDO I went ahead and looked at WP:RFDO to see why my redirects were deleted, but I still don’t get it. Can you please help me out? BTW thanks for pinging me. Ottawahitech (talk) 06:35, 25 November 2015 (UTC)[reply]
Ottawahitech, is this really all about one RfD that didn't go your way? If so, I strongly encourage you to simply walk away. I will answer your question, though.
WP:RFDO is not a one-stop shop, and I hope I haven't represented it that way. The "official" word on redirects is at WP:RFD itself, above current listings, in the Guiding principles of RfD and When should we delete a redirect? sections. Please note also that because I was a closer of that discussion and not a participant, I'm not the best person to ask about the rationale behind the delete arguments. But I think the idea was that those redirects could confuse readers looking for something else. There are several "gold plans" mentioned on Wikipedia, and since none of them have standalone articles, it's not clear what would be the most notable of those. There's very little discussion of the plan types at the ACA article—which is probably appropriate—so we're talking about balancing a chance of being slightly helpful versus a chance of obscuring other topics readers could be seeking. I suspect that redirects such as Gold plan (Obamacare) or Gold plan (Affordable Care Act) would not be considered problematic.
I will not be watching this page further; the formatting is topsy-turvy, and the discussion is simply too large. You're welcome to discuss RfD at WT:RFD, and I again encourage you to be a regular participant there. You're also free to contact me on my talk page. I hope this helps. --BDD (talk) 16:02, 25 November 2015 (UTC)[reply]
Honestly, it can be good to have a healthy skepticism about one's own contributions. I can think of one editor in particular, not to pile on, who would've saved a lot of us a lot of work. Be bold, yeah, but if a bunch of your contributions are ending up deleted, best to be a bit conservative and responsive to the implicit criticism. --BDD (talk) 22:04, 23 November 2015 (UTC)[reply]

(edit conflict) I'm sorry, Ottawahitech, you're astonished that a group of editors who frequent a common area sometimes talk to each other? What the hell? Yeah, sometimes we talk about things. So what? Grow up, and drop the stick. You had your opportunity to provide input as did everyone else; that's how discussions work, and it is none of our fault that you didn't speak up about your concerns with the process at the time, or we would have done a better job of explaining our rationales to you. Don't ping me to this discussion again. Ivanvector 🍁 (talk) 15:40, 23 November 2015 (UTC)[reply]

  • @Purplebackpack89: You said it was [deleted] because people believed "bronze plan" didn't only mean a health care plan So are you saying that it is OK to delete any page that may have an ambiguous title, because if this is what you mean there will be very little left in Wikipedia whose audience is global. No? Ottawahitech (talk) 01:35, 20 November 2015 (UTC)please ping me[reply]
  • @Ottawahitech: Please read WP:PRIMARYTOPIC. If there are multiple articles with the same or similar titles or topics that are both relatively well-known, a redirect to just one of them is inappropriate. Instead, there should either be a disambiguation page, or nothing at all. But we're on a tangent ATM. pbp 01:56, 20 November 2015 (UTC)[reply]
@Ottawahitech: I really don't know why you feel mocked by that Rfd given it's probably one the least dramatic and more light hearted Xfd's. If I'm going to use your civility standards, I can argue that you're the one mocking me and my research skills. Personally, I just see it like we're just searching from different parts of the globe. --Lenticel (talk) 02:14, 20 November 2015 (UTC)[reply]
  • @Ottawahitech: My thoughts on your remarks sort of mirror both BDD's and Ivanvector's; I offer you to become more active in RFD to become more familiar with its process, but at the same time, recommend you drop the stick in trying to form some sort of bad faith accusation based on the fact that some of a noticeboard's regulars discuss subjects amongst each other. If the latter did not happen, given that such editors have the most knowledge of a noticeboard, no improvements to improve the functionality and processes of a noticeboard would probably never happen. In fact, regarding RFD, thanks to RFD regulars brainstorming and discussing amongst each other, WP:RFDCO now exists. Wikipedia is a WP:CONSENSUS-based project, and what your accusations are akin to trying to claim otherwise. (That, and if you are trying to reach all recent RFD participants, you probably should have mentioned Tavix and Rubbish computer; Godsy too, but they are already aware of this discussion.) (Also, I'm a bit surprised I was mentioned as a RFD regular, especially given my recent transition from participation in RFD and becoming quite more active in WP:FFD. I'm waiting until the flood of nominations of redirects from Neelix dies down a bit before I go back to being active on RFD.) Steel1943 (talk) 17:04, 23 November 2015 (UTC)[reply]
  • Oppose - "Disingenuous [X]fD nominations, done without proper research" ≠ "Unsuccessful [X]fD nominations", the latter being very vague. Assuming "unsuccessful" to mean resulting in keep (more applicable to XfDeletions than XfDisucssions because the nominator generally suggests deletion in the former): some XfDs are close calls that result in keep and users shouldn't be afraid to make nominations of that nature. Also the proposal as written is very punitive in the sense that it would never reset (10 "unsuccessful" [X]fD nominations over 10 years would result in being blocked from making any new *fD nominations for a week by this wording, which I doubt is the intention). I've thought it over and whether it was a pure automated process or one requiring user input, it would be quite unreasonable, which I can elaborate on if needed.—Godsy(TALKCONT) 17:02, 19 November 2015 (UTC)[reply]
  • Oppose as well. The deletion forums are an important function of the project. Editors shouldn't be afraid to list in them. Editors who make obviously frivolous nominations can already be admonished or blocked for it - for egregious cases, go to WP:ANI. I think making this kind of bright-line rule regarding "failed" deletion discussions is an especially bad thing. Also, deletion discussions don't ever really "fail", that's an unfortunate viewpoint of the process - deletion discussions test community consensus, they don't ever really fail. Ivanvector 🍁 (talk) 17:52, 19 November 2015 (UTC)[reply]
  • Oppose I wouldn't want to sanction anyone for doing what they think is right. I have to assume good faith and hope that those who are doing AfD are generally doing it because they think it's best for Wiki, not to get scalp points. That said, I do disagree with a number of AfD's and I spend a lot of time trying to fix the articles I think are worth saving. I don't think anyone should be "forced" to do anything, but it is very important to do WP:BEFORE. Notability does not depend on the sources actually being in the article--only that they exist somewhere, so all the editor has to do is take a look... hopefully also using a database and see if the person is notable. If the article needs sources, tag it if they are too busy to fix the article. I don't see why so many articles are up for AfD when a quick WP:Before shows the person is notable. Another problem is that many people nominating AfD's obviously don't have access to databases and perhaps they are unable to tell if something is notable because the information is behind a paywall. Perhaps an answer to WP:BEFORE is to require that editors have access to databases before they are allowed to nominate for AfD. Megalibrarygirl (talk) 17:43, 20 November 2015 (UTC)[reply]
I just wanted to add that Megalibrarygirl is over at AfD often enough to know what's actually happening in that arena. AfD does oftentimes come across as some video game where one tries to rack up the most kills! The three most inappropriate reasons, to me, that AfD's end up there is first, because of don't like whether it's either the subject or the editor. Second, is a lack of knowledge about the subject itself. The third one is not interested in fixing the problems within the article. That last problem is going to continue to grow rapidly. At one time, (from what I can deduce) articles on Wikipedia could be started with a simple paragraph which then other writers would add to that article. However, today, an article must be fully fleshed out, like turning in an essay for a final exam. Why would anyone want to put that kind of effort into an article only to not only not receive credit for such an article, but have others add erroneous information? Certainly, not me. I'd rather create my own website and stick it there. Heck, there's even plenty of free spots to put it. What I see is Wikipedia losing its most valuable resource here - its writers! --MurderByDeadcopy"bang!" 18:58, 20 November 2015 (UTC)[reply]
@MurderByDeadcopy: I don't think people expect articles to be complete or face deletion. But I do think they expect them to be sourced or faced deletion. As for the "other people adding erroneous information" argument, a) other people editing "your" article is something you've just gotta live with in a Wiki, and b) the odds of erroneous information being added are much greater if an article stays around. I know you consider people not fixing articles to be a problem, but I'd counter that forcing people to do a particular activity is also a problem. People should always have a choice between fixing or not. pbp 23:12, 20 November 2015 (UTC)[reply]
I don't think people expect articles to be complete or face deletion.
A. I disagree. Seeing article drafts like this[3] getting rejected is baffling to me. That isn't some beginning paragraph or two to an article, that article is pretty complete which should be signed and owned by the writer so that they can be acknowledged for their hard work. Putting that kind of work into getting an article on Wikipedia is exactly why writers aren't staying here. As you've stated, you have to accept that anyone can edit "your" article on Wikipedia and I have zero issue with that premise as long as that exertion isn't surpassed by unreasonable expectations - at which point, I believe, the writer should/will take their creations elsewhere to get the full credit.
B. It's odd that you suggest that believe in forcing people to do a particular activity since I've never recommended anyone be "forced" to do anything and was basically agreeing with Megalibrarygirl who also had said the same thing. However, by nominating articles for AfD that shouldn't be there, but instead should be fixed, it is "forcing" people to do a particular activity or allow said article to be deleted for no other reason except that the nominator wasn't willing to do the work themselves. Either tag the article or fix the article or ignore it, but don't send it to AfD which then "forces" somebody else to fix the mess! --MurderByDeadcopy"bang!" 19:51, 21 November 2015 (UTC)[reply]
@MurderByDeadcopy: The AfC you cite a) was rejected for being unsourced, not incomplete, b) probably wouldn't have been rejected had a different reviewer reviewed it, and c) wasn't an AfD. Also, nobody is forced to fix an article at AfD. You can just let the article be deleted, after all. pbp 20:31, 21 November 2015 (UTC)[reply]
Never said that draft was in AfD nor did I say anyone "had" to fix anything, however, suggesting that an article be allowed to be deleted that shouldn't have been nominated to AfD in the first place doesn't sound accurate either. I have also decided that this conversation is going nowhere, at the moment, so you can have the last word here. Have a nice day! --MurderByDeadcopy"bang!" 20:48, 21 November 2015 (UTC)[reply]
  • Oppose since learning how to participate on XFD noticeboards can sometimes be trial and error, and banning an editor from participating due to such criteria wholesale is akin to assuming that all editors who do so are bad-faith editors trying to cause disruption, and that could not be further from the truth. Steel1943 (talk) 17:04, 23 November 2015 (UTC)[reply]
  • oppose BEFORE may have had its place when wikipedia was starting out. Wikipedia now has more than 5 million articles. Given that most of of them are shit and many downright harmful, BEFORE has outlived its usefulness and certainly entrenching it in this manner is unhelpful to the project. -- TRPoD aka The Red Pen of Doom 01:38, 24 November 2015 (UTC)[reply]
  • Support in principle, though I'm not sure about the numbers. Editors should not only be prevented from making plainly wrong nominations. They should also be discouraged from making controversial ones (the sort that end in no consensus or a close call), as those are the biggest time sink and nuisance ever devised. They are much worse than the nominations that get snowballed. Editors should be made very afraid to make those kind of borderline nominations. The more afraid they are, the better. I do not like borderline nominations. I don't think it matters whether they are doing it in bad faith or not. I am inclined to think that the ability to make AfD nominations should be earned, so I have little problem with this. James500 (talk) 02:04, 24 November 2015 (UTC)[reply]
  • Strong oppose: Much as the proposed policy is well intentioned, there appear to be several issues with it.
  • It does not deter new editors whose articles are nominated for deletion from leaving, instead deterring all editors involved with XfDs.
  • It fails to take proportion into account: if somebody is 99% accurate and they nominate 1000 articles for deletion, thy would be blocked. A user who created 1000 articles would likely be praised, and so to should users who contribute substantially to other areas, provided they use WP:BEFORE and don't nominate articles immediately after their creation.
  • It is too bureaucratic, with too many blocks, quantitative regulations and different stages. It is either serious misconduct, or it isn't.
  • It leans towards the idea that voting Delete, No, or Oppose to anything on Wikipedia is intrinsically negative, when the decision either way should be what is ultimately best for the encyclopedia.
I can imagine that some AfD nominators are working towards a "high score" that in reality does not correspond to actual improvement of the encyclopedia, but this is a wider problem in Wikipedia: for example, I've heard it being said that some editors are unnecessarily reporting users to AIV and UAA.
It is extremely unfortunate that what is no doubt a large proportion of new editors are leaving Wikipedia, and will continue to leave, as the articles they create are nominated for deletion, but I do not believe that this policy will help.
Are new editors creating their first article offered a link to "My first article" when they start creating it? Hopefully this could help, along with more weight being placed on "My first article" when users are welcomed. Having said that, sources should always be searched for before an article is nominated for deletion, and a reasonable amount of time should be given for new articles to be created: if the creating user writes something like "A start" in their edit summary I add the "Work in progress" tag for them.
Rubbish computer (HALP!: I dropped the bass?) 03:18, 24 November 2015 (UTC)[reply]

Prior to nominating article(s) for deletion, please be sure to: ;B. Carry out these checks:

  1. Confirm that the article does not meet the criteria for speedy deletion, proposed deletion or speedy keep.
  2. If there are verifiability, notability or other sourcing concerns, take reasonable steps to search for reliable sources. (See step D.)

;D. Search for additional sources, if the main concern is notability:

  1. The minimum search expected is a Google Books search and a Google News archive search; Google Scholar is suggested for academic subjects. Such searches should in most cases take only a minute or two to perform.
  2. If you find a lack of sources, you've completed basic due diligence before nominating. However, if a quick search does find sources, this does not always mean an AfD on a sourcing basis is unwarranted. If you spend more time examining the sources, and determine that they are insufficient, e.g., because they only contain passing mention of the topic, then an AfD nomination may still be appropriate.
  3. If you find that adequate sources do appear to exist, the fact that they are not yet present in the article is not a proper basis for a nomination. Instead, you should consider citing the sources, using the advice in Wikipedia:How to cite sources, or at minimum apply an appropriate template to the page that flags the sourcing concern. Common templates include {{unreferenced}}, {{refimprove}}, {{third-party}}, {{primary sources}} and {{one source}}. For a more complete list see WP:CTT.

This is what we are talking about. You might not like it (obviously some people don't), It doesn't say optional. Frankly I disagree with it too. I've never used the sources specified to search. For every article I have ever discussed, I have always been able to find sources directly from a conventional Google source and possibly by Deep Googling past the first pages of social media garbage. It literally takes seconds to get on the path to become educated in the subject. If the results are a blank page, are you spelling it right? If yes, that is the clear indication of no sources. If its garbage, get rid of it. If you don't know that answer, you have no business wasting everybody else's time. Trackinfo (talk) 22:45, 27 November 2015 (UTC)[reply]

Support Trackinfo's suggestion. It's important to do WP:BEFORE and anyone who can't be bothered to do so shouldn't be nominating for AfD. Megalibrarygirl (talk) 06:56, 29 November 2015 (UTC)[reply]
  • Oppose: I spend a large portion of my time on Wikipedia working with AfD, and making new policies as per Trackinfo would scare quite a few people monitoring the new pages feed away, and often times there is a backlog of new unreviewed articles that will not get reviewed if that occurs. I believe that extreme deletionism needs to be curbed on Wikipedia, but extreme inclusionism is not going to solve the problem either. I respect Trackinfo's efforts to give new articles a chance, but I disagree with their solution. smileguy91talk - contribs 15:54, 29 November 2015 (UTC)[reply]
Welcome to this elaborate wiki-thread. user:smileguy91. You say you are an experienced wp:AfD worker, an area I try to stay as far away from as I possibly can. Can you please explain why enforcing more strict rules on nominating editors work for deletion will scare away those who monitoring the new pages feed? Ottawahitech (talk) 18:15, 29 November 2015 (UTC)please ping me[reply]
"Experienced" may be an overstatement in this situation, because most of what I handle are articles that need WP:CSD or WP:PROD, although AFD has become of interest to me. As for my explanation, deletion tags are by no means condemnation of the article that they are placed on, nor a sign of imminent deletion since CSD is subject to the review of at least one administrator, XFD/AFD by the community, and PROD by at least one administrator. In my honest opinion, enforcing harsh rules such as those suggested here scares away NPP patrollers because although the punishments suggested are not bans or blocks, they still 1) tie up the user's hands that could have been used to help clear up NPP backlogs, 2) make the editor feel unwanted by the Wikipedia community or otherwise feel that they are making a negative impact, and 3) make the editor feel that Wikipedia is a bureaucracy, which it is not. NPP patrollers do mess up sometimes and place deletion tags on articles that should not be deleted, but everyone's human and make mistakes. People who tag articles for deletion make a net positive impact to the community, and as long as they maintain that net positive, they are beneficial to Wikipedia and thus make sure that content that does not belong on Wikipedia does not remain on Wikipedia. Mathematically, assuming that people who new page patrol maintain the same rate of error, the proposed rebukes listed above would disproportionately punish more frequent and more hardworking NPP patrollers compared to those who check in once in a while. If such a policy were to be implemented by the community to combat radical deletionism, it would have to be based on percentage of deletion requests denied rather than quantity, and the percentage error would have to be high at that, at least 20% IMO. smileguy91talk - contribs 23:48, 29 November 2015 (UTC)[reply]
  • Oppose It depends on the articles, and on the percent of ones deleted, not just the number. We already have on occasion removed people making frivolous nominations based on their being disruptive. I should mention that I deliberately nominate articles I think are on the borderline, with the purpose of letting the community better define the standards, and thus improve consistency. What new users need is not more inclusive rules, but the better ability to tell whether an article is likely to be improved. DGG ( talk ) 20:35, 30 November 2015 (UTC)[reply]
  • Oppose re:"The culture of deletion is becoming rather aggressive," the way I see it, the culture of piggybacking Wikipedia for SEO purposes has become rather aggressive. Semitransgenic talk. 18:22, 1 December 2015 (UTC)[reply]
  • Oppose- completely preposterous. Reyk YO! 20:46, 3 December 2015 (UTC)[reply]
  • Oppose: Careful deletionism/mergism does not harm the project; it makes the encyclopedia easier to navigate, read, and maintain. This proposal punishes new page patrollers and encourages erroneous use of CSD/PROD. Esquivalience t 14:12, 5 December 2015 (UTC)[reply]
Where is there an issue with deleting? The issue is uninformed nominations for deletion. If you blindly delete, then you potentially damage wikipedia's content. If you use WP:BEFORE and research what your are questioning, then you are making a nomination based on information. This proposal enforces placing the responsibility on a nominator to know what they are talking about by using a search for information before they talk. Trackinfo (talk) 23:47, 9 December 2015 (UTC)[reply]
The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

close as unfinished (draft)

The following discussion is closed. Please do not modify it. Subsequent comments should be made in a new section. A summary of the conclusions reached follows.
There is generally support here for the proposal, however as pointed out by DGG, it's already part of the deletion policy. There doesn't seem to be anything to do here. Ivanvector 🍁 (talk) 16:56, 15 December 2015 (UTC)[reply]

I would keep it simple, just allow reviewing administrators to block editors indefinitely for AFD nominations that are absurd. But this doesn't address the real problem: AFD is some how in an incredible hurry (which is pointless) but more importantly it forces the closing administrator to reason in absolutes (within this time). The solution: Encourage/allow administrators to close as "unfinished" which moves the articles to draft space. (As closing them is now easy we can Leave AFD's open indefinitely.)

By having the option to close as draft the admin can chose quickly knowing there wont be any negative implications. If he doubts between delete or draft it is safe to move it to draft or delete it, if he doubts between keep or draft it is safe to move it to draft or keep it. The doubtful cases then sit far away from the current line between keep and delete.

note: I've looked at the pending reviews one time and it was incredibly hard to judge if a topic is worthy of an article or not. You get things like: Professional sports person. No one can be expected to divide those into keep/delete in a remotely consistent way. But even if one could. After one great accomplishment it is nice to have the draft article. Much nicer than having garbage in mainspace or deleting worthy topics. 84.106.11.117 (talk) 15:58, 12 November 2015 (UTC)[reply]

Before we had draft space, it was somewhat common for discussions to close as "userfy" - pages would be moved into a user's space to continue working on them if they weren't quite ready for mainspace. I called for that result in discussions where consensus was that the topic met inclusion standards but the article quality was poor. Poor quality of course is not a valid deletion rationale but sometimes consensus is imperfect. I don't follow AfD much any more so I don't know if pages often get moved to draft space or not, but it is available as an option. Ivanvector 🍁 (talk) 17:09, 12 November 2015 (UTC)[reply]
And those userified articles don't get touched, sit around in draftspace until someone finds them years and years later. I'm sure it may exist but I have yet to see a single userified article bounce back and become a live article again. It's still an option though and with draftspace, that's another option. There's still DRV which often gets calls to restore article that have been deleted based on new information. For those reasons, I understand why AFD would be more deletionist as nothing is ever really dying. If there is actual a red link that was proposed as an article but listed with nothing, went through AFD and deleted, it can always be restored though a number of mechanism provided that someone with the interest to create it provides the sources. However, as someone who works with a lot of userdrafts and new drafts, the general view is "if you created it and put up some statement, you must have gotten it from somewhere and there's 100% chance it'll be easier for you to recall where you got it from than demand that other people do it for you." That's why drafts that don't get edited for six months and aren't worthy of becoming articles get deleted (although almost a third probably get extended at least once or twice which is basically a year without any actual work on it). -- Ricky81682 (talk) 10:55, 14 November 2015 (UTC)[reply]
  • Support, and--as mentioned-- we already do it, but it might be a good idea to explicitly add the options of moving to draft & moving to userspace. We have always closed many discussions with the option: userify. (and a decent proportion do get improved and return) And we now often do close by moving articles into draft space (and there are a few people who work on improving these, including myself--we need more people to do this, there are very few of us.) DGG ( talk ) 20:40, 30 November 2015 (UTC)[reply]
After digging a bit I do see a few move to draft votes. wp:afd argues an article may be kept and improved, merged, redirected, incubated (draft), transwikied (copied to another Wikimedia project), renamed/moved to another title, transcluded into another article (or other page), userfied to a user subpage, or deleted per the deletion policy.
Perhaps we could also come up with a guideline for linking to the draft articles from mainspace. We could make purple in stead of red links. I can usually be bothered to drop a link to a usable source on a talk page but writing a whole article that will/must probably be deleted is not very appetizing. Being able to find the page in a place where it appears to be useful would help a lot. 84.106.11.117 (talk) 12:15, 14 November 2015 (UTC)[reply]
I would have no objection to adding an additional outcome to those presently available, i.e., a new "move to draftspace" version of "userfy". I would object strongly to having open-ended AfDs; if, after a week or three of being listed at AfD, there is no consensus to keep an article, the AfD needs to be closed. Open-ended AfDs would be a bureaucratic nightmare, effectively permitting a flawed article to remain in article space indefinitely. Dirtlawyer1 (talk) 16:42, 14 November 2015 (UTC)[reply]
Moving to draftspace is the new "incubate" option. The incubation pages aren't around anymore. -- Ricky81682 (talk) 01:54, 15 November 2015 (UTC)[reply]
It doesn't matter if it takes a long time to work up the article after moving to draft: it will help build good-faith with newer editors. Keeping editors is very important and it's really scary to new editors when their articles are AfD'd after the editor put a lot of time and effort to write them. I think we need to be respectful of others' work and feelings. Megalibrarygirl (talk) 17:48, 20 November 2015 (UTC)[reply]
I agree with the sentiment but I have found few editors who start off by creating articles that stay on for more than just watching their own articles. The new editors that I think will actually stay probably started off like me, by doing little things like grammatical errors and fixing small problems. Those who's first (and sometimes only) edit is to post a new article I rarely see stay here to work on other articles. Either way, I've been more inclined with taking A7 articles and moving them to draftspace so that there's at least a chance for the editor to work on it. My biggest goal right now is to get WP:ALERTS to figure out some way to get WikiProject onboard with drafts that are G13 tagged or more importantly, that get moved into Category:AfC G13 eligible soon submissions where they are sitting for a month prior to G13 eligibility. That's really the best time to save the newest articles, plenty of time and every little edit resets it for a length. Those are the ones that a decade ago would be the one-line stubs (which seems to be falling out of favor and too aggressively sent to AFD for my view). -- Ricky81682 (talk) 03:25, 24 November 2015 (UTC)[reply]
I have seen WP:BEFORE being misused many times as an excuse to shoot down AfDs of American subject. Mainly due to the point that often is claimed that one reliable source is enough to prove notability in case of American subjects while non-American subjects nee several reliable sources. The Banner talk 16:12, 15 November 2015 (UTC)[reply]
WP:BEFORE can't be used as an excuse to shoot down an article. It can only be used to show that there is relevant information that leads to notability being established. Megalibrarygirl (talk) 00:40, 26 November 2015 (UTC)[reply]
Megalibrarygirl, Alternatives to Deletion and WP:BEFORE are Deletion Policies. They are NOT optional and anybody nominating an article for deletion is required to follow these POLICIES which the nominating editors rarely, in my experience, do. I agree with many Afd's but I see a lot that don't deserve it. Cheers! {{u|Checkingfax}} {Talk} 00:55, 26 November 2015 (UTC)[reply]
WP:BEFORE is not used to shoot down articles, it is used to shoot down AfDs by ignoring/dismissing the research done by the nominator. The Banner talk 21:23, 26 November 2015 (UTC)[reply]
Nor is it policy, Checkingfax is wrong. Wikipedia:Articles for deletion doesn't even claim to be a guideline. Doug Weller (talk) 15:21, 27 November 2015 (UTC)[reply]
I think it is indeed a restatement of policy. Deletion policy reads at WP-ATD "if editing can improve the page, this should be done rather than deleting the page." If the problem is notability , the only way to see if a page can be improved is to look for additional references., which is the essence of WP:BEFORE,
  • Support and It's been done before: On occasion I and others recommended brand-new-in-mainspace articles be moved to WP:Articles for creation back in the day before the Draft: namespace was created. I don't have diffs at hand but if memory serves, more than one AFD closed that way. Formalizing this for brand new pages seems like a good idea. For non-brand-new pages there are other options: Delete the clearly non-notable, soft-delete the "notability unclear" unless someone is promising to fix them in the next few days (in which case, "relist"), and soft-delete or stub the clearly notable topics if the current revision and all past revisions are worse than having no article at all. The reason brand-new pages should be moved to draft instead of deleted and that non-new pages don't "deserve" this privilege is to avoid unnecessarily discouraging editors - especially new editors with little or no article-creation experience. It's far better for editor retention to allow new editors a few weeks or months (WP:CSD#G13 is 6 months) to try and fail to find references that demonstrate that a non-notable topic is notable than to tell them they only have 7 days to find something or the page dies. I recommend that if this proposal to allow AFD discussions to close as "Move to Draft:" passes in any form, it include wording that says any page forcibly moved to Draft: as a result of an AFC close will be be tagged as an WP:Articles for creation draft and that it will be considered "G13-eligible" after the usual time period even if the AFC template is later removed. davidwr/(talk)/(contribs) 23:49, 27 November 2015 (UTC)[reply]
we don;t have to pass anything. it's already an explicit part of Deletion policy, at WP:ATD-I (section 2.5 of the policy page). All we have to do is use it more. DGG ( talk ) 20:53, 1 December 2015 (UTC)[reply]
The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

close as failed

Because we should delete what the policies already say we should. This goes on forever, but it's just an anti-deltionist rant, like hundreds before. DreamGuy (talk) 23:58, 1 December 2015 (UTC)[reply]

Where anywhere does this say to violate policy? The problem is bad, uninformed nominations. Repeat offenders should be penalized. Or do you support uninformed nominations? Trackinfo (talk) 03:37, 8 December 2015 (UTC)[reply]

fork discussion to WP:BEFORE problem

I didn't start the original discussion in order to have an "anti-deltionist rant. Instead, I wanted to talk about the fact that I don't see editors doing WP:BEFORE. I know this because I have improved numbers of articles that other editors have passed off as "no room for improvement." I don't mind articles being deleted if there is a reason for it, but if an editor can't be bothered to check or see if someone is actually notable then this is an actual problem for 2 reasons:

1) It hurts newbie editors: they feel threatened by the process. We should respect people's work and help them improve their articles by doing a WP:BEFORE and passing along the information to the newbie with some tips. It really doesn't take long to do.

2) It makes the process of keeping an article more difficult. Where it would have been easy to slap the article with a "Needs more sources" and bring it to the attention of a relevant WikiProject, instead the article goes through an intimidating process of discussing the alphabet soup of WP:GNG, TOOSOON, etc...

Now I'm not saying these things can't be learned. I've learned to step up into AfD and I will not let myself be intimidated by the process. However, it was intimidating at first.

So, to sum up, this isn't an anti-deletionist rant as DreamGuy characterizes the discussion... it's instead a plea to find a way to get editors to understand the importance of WP:BEFORE. Also, I think more AfD nominators should have database access, but that's another can of worms altogether... Megalibrarygirl (talk) 00:32, 2 December 2015 (UTC)[reply]

  • Comment - This thread seems to be predicated on the assumption that having an article nominated at AfD is an awful thing. Perhaps I am simply an optimist, and prefer to focus on the up-side of AfD nominations, but to my mind AfD nominations often have a positive result - The mere fact that an article is being considered for deletion means that it will be reviewed... and any problems with the article will be highlighted (and hopefully fixed). The mere threat of deletion often results in needed improvements actually being made to a problematic article. This is a good thing. Blueboar (talk) 16:28, 4 December 2015 (UTC)[reply]
  • The mere threat of deletion involves about a 60% chance of deletion. If the editor of that article is new to Wikipedia, there is a 95% chance in running that editor off Wikipedia. But, then, I'm beginning to discover that what Wikipedia wants is fewer editors so maybe that second part is a desirable outcome! --MurderByDeletionism"bang!" 19:37, 11 December 2015 (UTC)[reply]
  • Okay. What I did was rather informal based somewhat like what DGG did above. I would count up the total deletes in an AfD day (so this is only concerning AfD's, not speedy deletes which is much higher) and subtract that from the total. Deletes for every day was always higher between 55-62%, with the rest being no consensus, userfy, merge, and keep. AfD editors who are new, whose articles went to AfD almost always left Wikipedia and never returned... even if the article wasn't deleted. In fact, I specifically began looking into those articles that were saved. I only found two editors of 25 saved articles so that would be about 95%. Of course, these are just approximates. And It was difficult even finding a saved article written by a new editor. Lot's of articles are more often saved based on who initially wrote them or who's backing to keep them than any other reason! --MurderByDeletionism"bang!" 05:10, 15 December 2015 (UTC)[reply]
I agree with Blueboar. We all know that AfD is not meant to be cleanup, but that is what it is in practice. I know one person who never cleans up their (vastly inadequate) articles unless they are AfD'ed, and often they get deleted afterwards anyway. Also, see before and after for this, which I found by clicking on the big red button on Volunteer Marek's userpage. Btw, I think people should do the latter more often, though I don't follow my own advice. (I don't mean deleting it, I mean clicking it). Kingsindian ♝♚ 16:36, 4 December 2015 (UTC)[reply]
@Blueboar: You said The mere fact that an article is being considered for deletion means that it will be reviewed: That may have been true at some point but today the AfD battleground is growing weeds mostly. See for example:
https://en.wikipedia.org/wiki/Wikipedia:WikiProject_Business#Article_alerts
https://en.wikipedia.org/wiki/Wikipedia:WikiProject_Canada/Article_alerts
https://en.wikipedia.org/wiki/Wikipedia:WikiProject_Companies/Article_alerts#AfD
https://en.wikipedia.org/wiki/Wikipedia:WikiProject_Law/Article_alerts
https://en.wikipedia.org/wiki/Wikipedia:WikiProject_Technology/Article_alerts
https://en.wikipedia.org/wiki/Wikipedia:WikiProject_Women/Article_alerts
Ottawahitech (talk) 03:33, 5 December 2015 (UTC)please ping me[reply]
Not sure what those links are supposed to show, or how they refute what I said. Could you elaborate? Blueboar (talk) 14:55, 5 December 2015 (UTC)[reply]
I was trying to illustrate that listing an article at AfD (or any XfD for that matter) does not mean that it gets a proper review. Consensus nowadays is the agreement of a couple of editors on average.
More specifically, WikiProjects that have alerts, list AfDs of articles that have been tagged with the wproj’s banner.On the right hand side you can see the number of participants in each discussion. So, if you click, say, on the link for the alerts for WikiProject Business you will see that out of the 10 deletion discussions only one has 10 paricipants and one has seven. On the other hand four discussions have zero participants, two have one participant and the rest have three. Many of the discussions are relisted over and over.
Don’t forget that many wikiprojects do not have alerts, and many articles are not tagged, so those articles probably have much lower participation. Am I making any sense? Ottawahitech (talk) 06:03, 6 December 2015 (UTC)please ping me[reply]
  • @Blueboar: I wish someone would generate some statistics: You believe that AfD nominations often have a positive result while all I see are many XfD discussions with no participants (other than a nominator). BTW I just discovered that in this situation the alerts show one participant (software bug?), instead of zero. Ottawahitech (talk) 01:12, 13 December 2015 (UTC)please ping me[reply]
The two (having no participants at XfD, and ending with a positive result at an article) are not mutually exclusive. The mere fact that an editor nominates a poor article for deletion can spark improvements to the article - without any discussion on the XfD page. The "reply" to the nomination may be made by fixing the article, without discussion on the XfD page. Indeed, because there is a record of the nomination on the article talk page... even a nomination that is "closed (as no-consensus) due to lack of participation" can result in the desired improvement, years after the nomination. Blueboar (talk) 13:12, 13 December 2015 (UTC)[reply]
@Blueboar: You said The mere fact that an editor nominates a poor article for deletion can spark improvements to the article but again, in my experience this is hardly ever the case. What’s more, even well attended AfDs can generate a lot of talk, but no improvements to the article. See for example: 2015 Los Angeles Unified School District closure an article actively debated at AfD which received almost 1500 views in the last couple of days, but has been pretty much dead in terms of content building since the AfD started. In my experience this is typical — an AfD, successful or otherwise, usually kills the article. Just my $.02 Ottawahitech (talk)please ping me

, *WP:BEFORE is excellent as advice on best practice, but it does not work if you think of it as a mandatory required rule that must be followed. It is unenforceable. Just try to chastise someone you think isn't following it. All they need to do is claim that they did search for sources before nomination, but didn't find anything they thought was good enough. There is no way to "prove" that they didn't do this. Blueboar (talk) 14:26, 13 December 2015 (UTC)[reply]

  • I would support mandatory BEFORE. And if someone says "I checked for refs to support notability and didn't find any," but lots of good sources show up at Google Books and other obvious online sources, then the nominator has lied or is of questionable competence, and it could hurt him if he seeks to become an adminintrator. I do object to any notion that I have to spend a lot of time finding and adding refs to an article someone didn't bother to reference, when that person instead moved on to create a number of other unreferenced articles, to run up his "articles created" count, such as some editors do via semiautomated techniques from online lists of things or persons. Also, many new articles are "vanispamcruftisements" by a single purpose account about their band, employer, or fixation, and if all they are going to contribute are more vanispamcruftisements, the loss may not be a critical one of he goes off in a huff. Edison (talk) 22:43, 15 December 2015 (UTC)[reply]
  • Comment I like Edison's idea. It's true we can't know for sure if someone tried their best to do WP:BEFORE, but if an editor consistently shows a "bad track record" of checking for sources, we can at least weed out editors who shouldn't be involved in admin or higher. If you're working on an encyclopedia as an admin, you really ought to have database access and/or excellent searching skills. Megalibrarygirl (talk) 23:21, 28 December 2015 (UTC)[reply]
  • Comment regarding AfD nomination quality  I think we can agree that there are AfD nominators who take lightly their responsibility to the community in their preparation.  When one part of the community slacks, someone else either picks up the slack, or the encyclopedia suffers.  WP:BEFORE is only one part of the quality problem of AfD nominations.  This is not a simple problem, as we get editors who don't know how to make quality AfD noms, editors who think it is accepted practice to make drive-by noms, and VIPs who won't be bothered with preparing a community discussion.  We also must work with people biased to obstruct AfD consensus-building; joined by the legacy of thought from the ARS, which used poor-quality AfD nominations to up their "rescue" counts.  Another side of this is, where are the examples of quality AfD noms to present as a standard for comparison?  The first step in solving a problem is identifying a problem.  Unscintillating (talk) 20:21, 31 January 2016 (UTC)[reply]
I do not really get the problem with topic banning editors who regularly do not do a good BEFORE although I would probably define a bad BEFORE as regularly missing good material available through {{find sources}}. This is because good faith editors 1) may not have access to other databases or 2) may not know about any of the hundreds of free specialty databases. I would probably expand this to editors who regularly nominate in a particular topic area and do not check specialty databases, for that topic, which are pointed out to them and which they can access. What I find disruptive is when a nominator refuses to acknowledge they messed up and withdraw the nomination when it becomes obvious they messed up. JbhTalk 21:03, 31 January 2016 (UTC)[reply]

Deletions: mandatory notification of page creator?

I really don’t know if it is mandatory to notify a page creator that their article has been nominated for wp:AfD, however in my experience many nominators for the CfD/TfD/RfD/MfD/CSD/PROD/BLP-Prod/Deletion Review (did I miss any?) regularly omit notifying the editor who created the page.

Some editors here have expressed their opinion that such notifications should not be mandatory because they believe all editors should be using their wp:watch list. Since there is already discussion about this here I thought I would add this as a new section and see how others feel about it. Ottawahitech (talk) 16:54, 7 December 2015 (UTC)please ping me[reply]

Watching an article you create is automated. You would have to deliberately unwatch an article to not get notification. That is something that appeared a few years ago, so if you have an old article you created, you should go back to watch it. Same applies to Templates. However Categories get deleted in secrecy because there is no notification process to the articles affected by the removal of a category. Most categories are deleted with no opposition or discussion. Since categories are an aid to navigation, there is no telling the amount of damage some thoughtless, unopposed deletions have caused. I've caught a few after they were deleted, but once it is done it is a difficult process to reverse.Trackinfo (talk) 02:02, 8 December 2015 (UTC)[reply]
It is not automatic to show all changes to a page on the watchlist, only the most recent change. If someone adds AfD, then someone else edits the page, even a minor edit like correcting a typo, the default is that only the second edit shows in the watchlist. Additionally, requiring someone to check their watchlist violates Wikipedia policy that Wikipedia is voluntary. Thisisnotatest (talk) 04:03, 14 December 2015 (UTC)[reply]
Users should not have to rely on watchlists for this. So there should be a talk page advice for the creator, and also for major contributors. For those that are not logged on, notification will likely happen by email. And if they are logged in they will see it at the top of the screen. However I do not think it has to mandatory, just every strongly advised. I would expect any regular AFD CSD or prod nominator to hand out notifications. But for people new at this, I think they can be excused. However if the article gets deleted without these contributors ever knowing, there is a stronger case for allowing WP:REFUNDs or deletion review undeletes. Graeme Bartlett (talk) 04:48, 14 December 2015 (UTC)[reply]
All of this requires a lot of effort on the part of the nominator. Besides being simply laze, some disingenuous nominators might "forget" to properly notify contributors to an article in order to achieve the result. It seems there is a class of nominator who is more concerned about the won/loss record than actually having a reasonable argument about content. I have proposed in the past that this process be automated by a bot notifying all past editors on the article in question. The idea fell flat. Trackinfo (talk) 06:41, 14 December 2015 (UTC)[reply]
@Graeme Bartlett: In regard to your comment I do not think it has to be mandatory: I have been documenting all my deleted edits/pages on my user page for sometime now, and I know for sure that I lost quite a few pages that I had not received notification for on my talk-page. My most recent statistics indicate that this is mostly (but not exclusively) attributable to categories (with associated cat-talk-pages) that I created which disappear with no notice on a regular basis. I also know of at least two ADMINs who openly refuse to notify page creators of nominations. Ottawahitech (talk) 09:01, 30 December 2015 (UTC)please ping me[reply]
@Thisisnotatest: in regards to your comment It is not automatic to show all changes to a page on the watchlist, only the most recent change I think this is also a settable preference? Ottawahitech (talk) 08:36, 30 December 2015 (UTC)please ping me[reply]
@Ottawahitech: As I have said elsewhere on this page, it is a settable preference, at the cost of making your Watchlist content much longer per day. Thisisnotatest (talk) 06:36, 31 December 2015 (UTC)[reply]
@Trackinfo: in regards to your comment Watching an article you create is automated. You would have to deliberately unwatch an article to not get notification it appears to be a settable preference see:
Preferences -> Watchlist -> 
  • Add pages and files I edit to my watchlist
  • Add pages and files I move to my watchlist
  • Add pages I create and files I upload to my watchlist
…and as I said before, some editors (including me) prefer not to spend their wiki-time watching pages. If I could view only XfD notices on pages on my watchlist I may consider it, but otherwise I find watching pages way too distracting. Ottawahitech (talk) 08:28, 30 December 2015 (UTC)please ping me[reply]
@Ottawahitech: I watch almost 8,000 articles. I disappear for days to weeks at a time. During such disappearances, my wikipedia attention is minimal. The single edit posting the *fD is both time sensitive and hard to detect out of all that noise. Once an AfD is posted, some articles get a lot of edits, masking the one edit that revealed that there is now a ticking time bomb on that article. When an article I watch is up for such a nomination, that information is far more important than all the other monitoring am doing. Just as you are questing a ping when a response is written, I want a notification that action is required. Trackinfo (talk) 08:05, 31 December 2015 (UTC)[reply]
  • I support mandatory notification of the page creator and all contributors of significant portions of new text. Watchlists are useless for this. James500 (talk) 11:46, 14 December 2015 (UTC)[reply]
  • Support mandatory notification of the article creator of a pending AfD by the AfD nominator at the same time as the subject article is tagged with the AfD notice template. Much of this discussion and virtually all of the ranting about "deletionist" this-and-that is misguided and horribly exaggerated, but I have always believed that it is a matter of basic fairness to notify the creator of an article subject to a pending AfD. I find it quite odd that this is not already mandatory and I have uniformly demanded notification of creators and AfD re-listings when nominators have failed to provide notice. That said, I oppose mandatory notification of "major contributors" because of the burden it places on the nominator to discern what constitutes "major" and because of the arguments that inevitably ensue over same. The notice given the creator and the tagging of the article with the AfD notice template should be sufficient; no one should be trying to hide pending AfDs, but likewise there is also a burden on concerned editors to keep articles of interest on their watch lists. There are several subject categories of AfDs which I check daily, I have watch-listed over 4,000 articles of concern to me. From time to time, I have also notified WikiProjects (in a neutral manner per WP:CANVASS) of particular AfDs within their subject areas of interest. Any responsible editor should be prepared to do these things as well. Dirtlawyer1 (talk) 12:35, 14 December 2015 (UTC)[reply]
  • Opposed - There is nothing special about being the article creator. Once you upload an article into mainspace, it is no longer "your" article. You have given it to the community to do with as they will. You have no special "rights" in regards to what happens to the article. Which means... you have no "right" to be notified if someone significantly edits it, nor if someone nominates it for deletion. If you care what happens to an article (whether you created it or not), the onus is on you to follow what happens to it. Blueboar (talk) 13:04, 14 December 2015 (UTC)[reply]
This isn't about ownership, it is about transparency and not using sneaky tactics. James500 (talk) 15:54, 14 December 2015 (UTC)[reply]
  • Support for all contributors to the article being nominated This remove the question of ownership. If you took the time to edit the article, you should have an important opinion to be heard on its value to wikipedia, whether you removed content from the article or added to it. Stated above, because this is a lot of work, we should request a BOT automatically make this notification as part of the nomination process (along with creating the discussion article and the header with the link). Trackinfo (talk) 22:03, 14 December 2015 (UTC)[reply]
  • Support when practical - it is sometimes quite impractical to identify an article creator and especially to identify anyone who would be considered a "major contributor", and indeed disagreement about how "major" should be defined. I fear this requirement becoming a "gotcha" loophole to keep content which should otherwise be deleted. But I do support the idea. Also, this constitutes a major change to how we've always operated, and should be better advertised than this sub-thread. Ivanvector 🍁 (talk) 16:01, 14 December 2015 (UTC)[reply]
  • Oppose Being the initial or subsequent editor is just that, they don't own the article. I think it is good form to notify certain contributors - but would in no way want to invalidate these community discussions just because a certain editor wasn't explicitly asked to participate. — xaosflux Talk 16:08, 14 December 2015 (UTC)[reply]
  • Support Preference is that this would be via bot that would notify all contributors except those marking a contribution as minor, but if not, then needs to be required of the nominator. Minimum would be notifying the page creator. It is not that the creator owns the page, it is that the creator is the best person to know why they believed the topic to be notable. It also brings the creator into the education process, increasing the likelihood that their future page creations improve as a result of the discussion. While deletions of my first two article creations were upheld (and discouraged me for year or two from creating any other new articles), my subsequent creations have survived and one of them is regularly edited. Involving me in the deletion process of those two pages, for which the nominator had notified me, was an important part of my education in how and when to create an article. Thisisnotatest (talk) 00:13, 15 December 2015 (UTC)[reply]
Logically it also should not notify back to BOTs as well. Trackinfo (talk) 21:13, 15 December 2015 (UTC)[reply]
  • Weak oppose- usually notifying the page creator is the courteous thing to do. But there are times when that would be useless, such as when the creator has been permabanned, or has stated that they don't want to be bothered with such notifications. Strongly oppose making it mandatory to notify every page contributor. This, obviously, would be equivalent to canvassing for keep votes. AfDs should ideally be judged by neutral, uninvolved editors. Reyk YO! 12:24, 15 December 2015 (UTC)[reply]
  • Comment This is a simple courtesy which should normally be done. But there may be exceptions and so this shouldn't be done blindly. For example, if there's a big group of deletions such as in the recent case of Neelix's redirects, we wouldn't want to spam hundreds of templates onto their talk page. So, this should use guideline language and, so far as I know, that's what we have currently. Is there some specific text that the OP has in mind? Andrew D. (talk) 13:32, 15 December 2015 (UTC)[reply]
Actually that's pretty much exactly what happened with Neelix's talk page, since Twinkle doesn't let every notification be turned off. Another user took it upon themselves to archive the automatic notices onto a subpage, until they got in hot water for it for no good reason. Ivanvector 🍁 (talk) 14:42, 15 December 2015 (UTC)[reply]
  • Oppose any additional forced manual actions for AfD nominators. Neutral on any automated solution using bots.--Staberinde (talk) 18:46, 15 December 2015 (UTC)[reply]
  • Support as simply courtesy. If you have time to manually nom an article for deletion, then also take the time to notify the article creator. If she is no longer active, then there this no harm. If he is banned, then again no harm is done. Many use Twinkle to nominate, so notifying the article creator is effortless. Articles get added to my watchlist all the time when i edit them or add templates, so that here may be thousands of articles on the watchlist, and because of the large number of watchlist listings each day i might not see an afd for some article I created, and thus miss the opportunity to participate in the afd. Edison (talk) 22:30, 15 December 2015 (UTC)[reply]
  • Oppose per WP:OWN. Once you hit the submit button, the content is up to the WP community to do what they want with it. Yes, it should be strongly recommended, but it can't be forced. This applies particularly to pages with complex history, for instance say a page was original created, it was made into a redirect for several years, and then recreated in a completely new form. Who is the "creator"? The first editor, or the editor that recreated from the redirect? And finding that in the last case can prove extremely difficult if there's been more than a few hundred edits to the article. --MASEM (t) 22:51, 15 December 2015 (UTC)[reply]
  • Oppose per WP:OWN the content belongs to the community; we should encourage a culture where creating editors divest themselves of ownership and feel free to just let go and trust their peers. W.r.t those holding the view, the discussion of requiring editors to use watchlists does not resonate; editors are not required to particpate at AfD. NB: I would support requiring some evidence of WP:BEFORE - Ryk72 'c.s.n.s.' 07:19, 16 December 2015 (UTC)[reply]
  • Oppose The page creator is not a special person in regards to an article. There is no reason to even think they are the main contributor. This add needless red tape to handling routine deletion debates and we already have a tool for people to keep track of pages they have an interest in. HighInBC 22:15, 28 December 2015 (UTC)[reply]
  • Oppose this is red tape contrary to WP:OWN. Nominations done through Twinkle already notify the creator. If you care about an article for another reason, use your watchlist. If stuff gets buried in your watchlist, install User:Anomie/linkclassifier, which will highlight links to pages nominated for deletion in pink. Then it will be difficult to miss deletion nominations on your watchlist. BethNaught (talk) 08:20, 31 December 2015 (UTC)[reply]
  • Support mandatory notification of the article creator of a pending AfD, whether by the nom or a bot. Not because the creator owns the article or is any more responsible for the article than the rest of us, but because the creator likely knows the subject better than most of us, and they might have a justification for creating the article that we haven't yet considered, or even plans to expand it that they haven't gotten around to yet. Dcs002 (talk) 22:58, 31 December 2015 (UTC)[reply]
  • Oppose per OWN and CANVASS, and yet another structural mandate - we don't need more rules, we need better articles. Why not require notification, but strike any comment by that editor because their input was canvassed? Why not require anyone expressing "keep" on an article to actually improve the article or we strike their comment? Just as bullshitty but would probably contribute more to the encyclopedia than keeping crap because someone has been notified. Carlossuarez46 (talk) 23:00, 7 January 2016 (UTC)[reply]

Seeing the BOT suggestion getting more traction above, I'll make the proposal formal.

BOT Notification

As a part of the *fD creation process, a BOT shall automatically notify all contributing editors who have added or subtracted 10% or more of the content to the article. Edits marked with an m or b will be excepted from this process. Trackinfo (talk) 21:21, 15 December 2015 (UTC)[reply]

@Masem:New fine tuning in green is a point I conceded early on. But Masem continues to argue against this point. It is now in the text. I invite Masem to tweak it further if necessary, then you can reverse your "vote." Trackinfo (talk) 02:07, 22 December 2015 (UTC)[reply]
  • Support as proponent. Automation takes human effort and subjectivity out of the equation. Any editor who has taken the time to make an edit in the item in question has read some of the content and has enough of an interest in it to have made an improvement to it. Trackinfo (talk) 21:59, 15 December 2015 (UTC)[reply]
  • Oppose . That is going to spam editors that may be doing wikignoming aspects or the like on articles (which don't always mark minor changes). I would support a bot that would notify any editors that has contributed to more than 10% of the total edits on a page (eg at most 10 editors per article), since they are likely going to have the most vested interest. --MASEM (t) 22:51, 15 December 2015 (UTC)[reply]
I would accept the 10% figure as a friendly amendment. Trackinfo (talk) 00:13, 16 December 2015 (UTC)[reply]
  • Oppose- this would have the effect of canvassing for keep votes. Reyk YO! 06:20, 16 December 2015 (UTC)[reply]
  • Oppose - I gnome, and would not like to be canvassed for all of the articles to which I have contributed. More importantly, I would not consider it appropriate that all (or even all significant) contributors be notified; per the WP:CANVASSing issues above. If AfD were less vote-y and more WP:NOTVOTE-y, these concerns might be allayed. NB: I would support requiring some evidence of WP:BEFORE at AfD. - Ryk72 'c.s.n.s.' 07:25, 16 December 2015 (UTC)[reply]
  • I support some form of automated notification of all major contributors. Notifying major contributors is no more canvassing for keep !votes than putting the AfD on a deletion sorting list and the AfD log (instead of some list that is only related to the subject matter of the article, like a list on the WikiProject page, that is presumably less likely to be frequented by people who do nothing but vote for deletion) is canvassing for delete !votes. Major contributors will not necessarily be in favour of keeping the article. And even if they are, trying to conceal the AfD from them looks like deception and gamesmanship. Anyway, neutrally worded notifications are not canvassing. It might be desirable to notify major article talk page contributors as well. James500 (talk) 23:28, 16 December 2015 (UTC)[reply]
  • Comment Do many people nominate things to AfD without using Twinkle? Twinkle automatically notifies the creator. I remember what a sod of a job it was setting up an AfD in my 12,000 unautomated edit days before getting my mop and subsequently twinkling. Notify every contributor? No way. Major contributors? Define 'major' so that a bot or a Twinkle will know who is and who isn't. A vandal adding a page of drivel might get a notification where the adder of a short paragraph of good info mightn't. By percentage of text added, or by number of edits? Some people save after every five words, or so it looks when a one paragraph article has taken thirty edits. How about text removed? I'm not saying it's impossible - I am saying it's going to make one of the early Christian Church's council meetings look like making a decision between lemonade and orangeade. Peridon (talk) 12:56, 17 December 2015 (UTC)[reply]
    • Removals can be 'major'. Also note that you shouldn't make any difference between users who are likely to vote 'keep' and users who are likely to vote 'delete'. A user who removes text might statistically be more likely to vote 'delete' than a user who adds text. --Stefan2 (talk) 15:18, 17 December 2015 (UTC)[reply]
Not if they've removed half a page of vandalism - you've no idea which way they'll vote, or even if they will. Does adding half a page of junk count as a major contribution? To a bot, I would say that it did (unless the bot could detect that it had been removed as vandalism by a human). Referring to your post below - do many Commons files get multiple editing to any great degree? Notifying uploaders by bot is easy (for a bot person). Deciding the value of contribs isn't. It's not always easy for humans. Peridon (talk) 20:31, 17 December 2015 (UTC)[reply]
Those people removing content from the article could likely be delete votes. Including people who delete content should be important to avoid canvasing just one side. The point being, we are notifying people who have shown they are informed and interested parties to the content in question. Trackinfo (talk) 22:53, 17 December 2015 (UTC)[reply]
  • Can't Twinkle just be set up to notify everyone with major contributions? On Commons, it is possible to use c:MediaWiki:VisualFileChange.js to nominate all files in a given category for deletion with a few simple clicks, and the script automatically notifies all uploaders (except reversions and uploads by certain bots). Generally, I support notifying all editors with major contributions (i.e. anything which is not marked as 'bot' or 'minor'), but I think that there should be an exception for certain IP edits. A few days ago, I found text which had been contributed by an IP several years ago, and I thought that it was not useful to notify the IP that the content seems to violate copyright as the original user probably has changed IP addresses since that time. --Stefan2 (talk) 15:18, 17 December 2015 (UTC)[reply]
    • Going to my point above, I have seen articles (primarily dealing with contemporary, popular works) where by the above definition, would include 100s of "major contributors" simply because they did one or two non-minor editors, and the idea of notifying all of them by a bot screams of canvassing. I would think the balance of having the bot figure out the top 5 to 10 (at most) contributors and notifying them would be reasonable that doesn't feel like canvassing but at least proper notification. --MASEM (t) 19:06, 17 December 2015 (UTC)[reply]
  • Oppose AfD needs disinterested parties as much as invested parties. This proposal would bias deletion debates and damage neutrality. HighInBC 22:16, 28 December 2015 (UTC)[reply]
  • Support I don't think AfD is a very neutral place. I think a lot of articles that should never have been up at AfD (the kind I'm concerned about) are there because editors don't do WP:BEFORE and assume a topic/person is not notable. (For example, Agnes Jones Adams, Kelly DiPucchio) Having an interested party would be a useful balance. Megalibrarygirl (talk) 23:13, 28 December 2015 (UTC)[reply]
  • Qualified Support - If the technology is there and someone is willing to be responsible for creating the bot (I know NOTHING about such things), then I support this, but someone must commit to creating the bot and making the bot available to all users. I think 10% is as good a number as any, and we need to draw the line somewhere, but I'd support another number too, as long as it captures what we consider major contributors, or even recent contributors in general (maybe past 2 years?). (Edit) WP is not mandatory, so we cannot require someone to create the bot. Maybe we should have the bot first and then !vote? Dcs002 (talk) 23:06, 31 December 2015 (UTC)[reply]
  • Support this should be the standard. We are losing enough editors to this process as it is, there is no reason not to at least make the process more transparent. I think WP:OWN is a silly argument as what we want are people to provide sources and the creator is likely a good person for that. As far as a canvasing problem goes, I just don't see it. AfDs aren't a vote. One extra "keep" !vote, with no solid reasoning, will have no effect. Hobit (talk) 23:47, 2 January 2016 (UTC)[reply]
Comment. The biggest problem with the "canvassing" rule is it only stops the honest. Canvassing occurs constantly. Wikipedia cannot stop so it should not be a policy. (Unfortunately, AfD's are closed by adding up the "keep's" vs the "delete's"!) --MurderByDeletionism"bang!" 20:38, 7 January 2016 (UTC)[reply]
  • Support not everyone uses Twinkle.
Also, in 2011 not notifying article creators was used as a possible reason to "oppose" someone becoming an admin. See 28bytes. --MurderByDeletionism"bang!" 20:38, 7 January 2016 (UTC)[reply]
  • No strong position, but presumably this amounts to CANVASSing, which ought to be disclosed by each person who was CANVASSed and a closing administrator may give added weight to consensus based on non-CANVASSed opinions. Carlossuarez46 (talk) 23:03, 7 January 2016 (UTC)[reply]
Actually the point of using the BOT would be to remove the POV vote stacking of canvassing aspect from the process. This would bring in people who have demonstrated an interest and are presumably informed about the subject in question. The opposing viewpoint would be to only seek the opinions of the random few who venture through the *fD pages, who will have a high likelihood of not being well informed about the subject in question. Wikipedia is about providing accurate information; being the world's source. Should we depend on uninformed people to decide what is valid content? Trackinfo (talk) 23:57, 7 January 2016 (UTC)[reply]
  • Comment  Since when are our content contributors irresponsible editors who are biased to throw Afd "elections"?  Afd volunteers don't have the same skills as content contributors in access to sources and content comprehension, so are a valuable resource to an AfD discussion.  We need to support our content contributors.  Unscintillating (talk) 20:22, 24 January 2016 (UTC)[reply]
  • Comment  Not everyone keeps everything on their watch list.  I've never known why, but they don't.  Unscintillating (talk) 20:22, 24 January 2016 (UTC)[reply]
  • Support or neutral  The first thing to do is to use a bot to replace the current system of manual notification of page creators by nominators.  The fact that the proposal changed after it was first posted means that the proposal is not yet stable.  Unscintillating (talk) 20:38, 24 January 2016 (UTC)[reply]
Just as a note, as the proponent I respond to the initial objection by Masem within 3 hours of his objection to the original proposal. Not getting a response after seven days, I put it into green text to make it an obvious inclusion addressing his objection in the proposal, with a ping. I thought he would want to discuss, but has instead he has just moved on to comment in other sections. That is the only instability issue to the proposal. Trackinfo (talk) 02:55, 25 January 2016 (UTC)[reply]

XfD culture: Is wp:OWN relevant to this discussion?

I am trying hard to understand how the concept of wp:Own is relevant to this discussion. Yes the article belongs to the community, but the community(singular) does not have an interest in ALL articles. When an article is nominated for deletion only a tiny subset of the community shows up to the wp:XfD discussion and only those who participate determine whether the article is kept or deleted. Of those who participate in deletion discussion the majority are XfD-insiders (those who frequent XfD-discussions and are intimate with the all wiki-deletion-details, but not necessarily with the article's topic). A minority of participants are those who are interested in the topic of the nominated article, but not necessarily in the wiki-deletion-rules, one of which is presumably the article creator. So why preclude this type of participant by not notifying them?

(I am pinging all who have mentioned wp:own here:@Megalibrarygirl:/@Dcs002:/@Sam.gov:/@SusunW:/@MurderByDeadcopy:/ @Ricky81682:/@Masem:@Kingsindian:/@James500:/@Trackinfo:/@Xaosflux:/@Thisisnotatest:/@Ryk72: ) Ottawahitech (talk) 21:44, 28 December 2015 (UTC)please ping me Also @Blueboar: Ottawahitech (talk) 01:59, 30 December 2015 (UTC)please ping me[reply]

Ottawahitech I grow weary of discussions that go on and on and on and never resolve anything. My contention is that own has nothing whatsoever to do with deletion. The only reference I made to the subject at all was to express frustration with nominators who state that the original editor is inactive, which IMO is irrelevant. It doesn't matter who the original editor is of a file. Each and every one of us is capable of improving it and whether any editor is active or not has nothing to do with whether an article is or is not notable. SusunW (talk) 21:59, 28 December 2015 (UTC)[reply]

I agree with SusunW. IMO, we all "own" Wikipedia and that's pretty cool. If someone didn't source something, and you can, source it. If someone made a copyedit error, fix it. Too easy. Megalibrarygirl (talk) 23:26, 28 December 2015 (UTC)[reply]
  • Two issues. First, does the person have to knowledgeable about the topic to be able to intelligently participate? My view is that AFD discussions are largely independent of the topic itself and mostly focused on the available of sources. How else should it be decided what should stay and what shouldn't? There are rare disputes (I think computer science techniques is something I've seen) where it's not clear that there are going to be traditional reliable sources no matter the topic and that results in new WP:TECH-related criteria and fights over whether there's actual support and the like. The reason being, the discussion should be on whether the encyclopedia needs the topic, not on whether the topic "should" be an article. You get that kind of argument all the time, be it "Wikipedia is not paper and should include all cartoon characters" to "it's a significant corporation even if no one can really find evidence of it" to "it's a current event" to emotional sympathy to claims of systemic bias (an issue with an English language focus here) to outright just calling everyone racist or sexist or whatever, none of which I find particularly productive in terms of deciding whether an article in its current state should remain in mainspace. Everyone has opinions on what or shouldn't be here, so why should the views of those who support the topic be put above all others? Second, what more can be done to get people with knowledge of the topic involved? There are wikiprojects tagging onto articles (one reason I focused on getting them tagging for AFC and userspace drafts so that if they are immediately moved and listed for deletion, people know) and separate AFD lists created on various topics. Otherwise, I have no idea when creator activity is an issue. Can you point out an example AFD? -- Ricky81682 (talk) 23:32, 28 December 2015 (UTC)[reply]

Even the text of WP:OWN disclaims that someone can be an expert in the field, as opposed to taking ownership of an article. This concept is lost completely by know-nothings who blindly nominate an article for deletion and their thoughtless "dittohead" supporters. I take serious exception to those who nominate for deletion in a field that is not their expertise or without research into the contents of the article. That is what WP:BEFORE is all about. You can learn about a subject without owning an article. I usually add sources before I get involved--I show my work. Because I do my due diligence before I nominate anything for deletion or before I respond to such a nomination, I expect that of others. I don't see it happening. When someone has enough knowledge in a subject to be posting information to the article, that is simply being informed, that is interest in the subject and an interest in furthering the worlds knowledge about it through wikipedia, not ownership. Trackinfo (talk) 23:55, 28 December 2015 (UTC)[reply]

  • Since I got pinged, I think that notifying some people about xfd's are a fine idea, but I think it is a waste of time to send out notifications based on the criteria (even the amended criteria) above - one where are these metrics going to come from, just article size? If so you want to REQUIRE notification anyone who vandalized by section blanking? This is not sustainable and won't scale. Do you really think we need "Speedy Keep - bad form, editor X from 3000 revisions ago was not notified"? — xaosflux Talk 00:04, 29 December 2015 (UTC)[reply]

I will speak for myself. WP:OWN is highly relevant. Individuals do not own articles, but if there is a problem with an article, we treat them as if they do. We can't have it both ways. If it's up to me to fix or maintain an article I create, then it should also be up to me to decide what goes into that article. Neither is true. We say things like "they just create more work for the rest of us" or "it's up to them to fix their article." No it's not! They do not own the article just because they created it. Maybe a kid started an article on something that is wildly popular among kids, but that kid didn't understand how to cite RS. Those of us who are not kids might not realize how popular or widespread the subject is. The article is ours to fix, improve, develop, or at least tag. Tagging takes seconds! That's hardly imposing an undue workload on anybody, and it tells the reader clearly that there are issues of reliability and the article could use their help. No one is misled. Why do we even have Stub and Starter tags? I have never gotten a satisfactory answer to that from someone with deletionist leanings. If we follow our current trend of only keeping articles as notable that cover subjects known to the most ignorant nominator (who will be the one nominating it) and are covered in depth in 3-5 or more RS (which are already properly cited in the article), we will wind up with nothing but pop culture in WP. Worse yet, we will make ourselves irrelevant. ANYONE can do a Google search, and that is what we are reducing WP to - a glorified Google search. If some editors in AFDs can't find numerous RS on the first page of their Google search, that's it. Well guess what - the public can do that same Google search without coming here.

Back to WP:OWN. Once an article is nominated, there are always editors who think it's up to someone else, the creator/"owner", to persuade them to change their default !vote from delete to keep, that nominated articles should be deleted unless proven otherwise, which to the standards of some is impossible. (I will stand up for the admin closers though. They have always been thoughtful in my experience, even when I don't like the outcome. Also, it's been a while since I participated meaningfully in AfD's, and what's happening now might be different from when I was active there.) And FWIW, I have only created two articles in my 6 years (on and off) of editing, and this is why. People who have no idea what they are talking about and no interest in the subject are judging important topics for notability. I have lost the will to fight that fight. I know how immovable some people can be in the face of contrary evidence, especially when they have no familiarity with the subject. I have other things in my life that are more rewarding to spend time with. Dcs002 (talk) 04:37, 29 December 2015 (UTC)[reply]

@Dcs002: I completely agree with your statement Individuals do not own articles, but if there is a problem with an article, we treat them as if they do — See here for a very recent example: Wikipedia:Articles for deletion/List of founders of companies of the United States where the commentor is saying: this list should be deleted … unless its creator actually puts some work into making it more focused, informative, and useful. Ottawahitech (talk) 01:54, 30 December 2015 (UTC)please ping me[reply]
It's just a counter-example - an inconsistency between WP policy and our own attitudes toward deletion. If we don't own, we should therefore not be treated like we are responsible as individuals for any given article. Dcs002 (talk) 03:25, 30 December 2015 (UTC) (I just moved this because it was intended as a reply to James500.[reply]
As far as I am aware, the creator of an article is personally responsible for it. If an editor creates plainly unacceptable articles with a sufficient degree of persistence, he could, in theory, be given a topic ban. Accordingly he must be notified of any AfD nomination to allow him to defend himself from what might potentially be false accusations of misconduct. James500 (talk) 12:03, 30 December 2015 (UTC)[reply]
These are separate issues, James500. We are each responsible for what we post, but not for the state of any individual article. What you are describing is disruptive editing. If an editor persistently creates unacceptable articles to the extent that they need to be topic banned, that is disruptive editing. If an editor with good intentions creates one or a few articles that don't pass muster in their current form, it is not that user's responsibility to fix the article. They might not understand what's wrong with it, or how policy is relevant to the issue, and therefore cannot fix it. They might be on vacation in Ibiza. But these are likely to be newcomers who need help making better articles, or even editors who have been around a while but have not ventured into article creation until recently. I strongly believe we need to help newcomers more than we do, and to be more tolerant of their attempts to expand the encyclopedia. That is one of the things we risk by assuming the creator "owns" or is solely responsible for improving the articles s/he creates - alienating newcomers and other potentially productive editors (like me). Regardless of intentions, of course we must take action against disruptive editing, but we need to tolerate a certain level of roughness in an encyclopedia that will forever be a work in progress, and we need to reject the idea that "I don't own this new/unsatisfactory article, so it's someone else's responsibility to fix it" as vehemently as we reject the idea that "I own this article, so I control it."
Accusations of misconduct are not part of the AfD process. They have their own process of mandatory notification and defense. "Editor X has started too many bad articles" is not an acceptable reason to delete an article through AfD. AfD closings are determined based on the discussion and consensus concerning the merits of the article, not the conduct of the article creator. Dcs002 (talk) 01:29, 31 December 2015 (UTC)[reply]
In general we should be responsible and held accountable for our actions on wikipedia. That was why I proposed a system to progressively ban editors who make a habit of *fDs without doing WP:BEFORE. That should and effectively already does work for editors who exhibit a pattern to create useless articles or useless edits--essentially that is vandalism. I think the needless *fDs are a form of vandalism but that has not received sufficient support. However, we are not responsible for the subsequent edits of others to an article we have participated in. We can try to be by watching the article and participating, but that is not a requirement. I've created many stub articles as deliberate low hanging fruit. I establish the notability of the subject, place its wikilinks in the chain of events and report what I know about it. Sometimes that is all that has been reported and it remains the stub. Stubs are favorite targets of *fDs, too often in the first few minutes of the article's life before it can develop. But the joy of our public edit policy is that others contribute and some of that has resulted in marvelous blooms of informative articles. I can pat myself on the back for starting the wave, but its is the work of other editors that brought it to fruition. I certainly don't own that. Trackinfo (talk) 01:55, 31 December 2015 (UTC)[reply]
Trackinfo, I'm not sure how banning editors who habitually nominate pages for deletion will prevent creation of useless articles or edits, and I wouldn't go so far as to agree that excessive xFD nomination is a form of vandalism (intentional destructiveness) vs disruptive editing (which might be well intentioned), but your attitude about shared responsibility (and shared opportunity) to edit articles is a bulls-eye! As you said, we can pat ourselves on the back for creating articles, and (worse, IMO) we can take credit for bringing articles to GA or FA status, but this is selfishness, and it disregards the community spirit of WP. We all own all articles together, and if one editor has done most of the work to improve an article to GA or FA (usually the case, I think), I consider that a failure of our community process, and it is yet another factor that contributes to an attitude of ownership. We do our work here anonymously and give it away for free, knowing it might be shredded by someone else, and NO ONE is exempt from that. Taking sole credit for GA or FA is not consistent with that spirit of giving and sharing. Our goal should be a community-created encyclopedia with broad, excellent content, not a well polished, narrow collection of articles. Readers know that anyone can edit WP, so they expect to have to verify things from time to time, especially if we use our tags properly. I don't think they expect proper scientific reviews or Britannica-quality presentation, but they do expect well sourced information. We can do that by having more articles, using stub and starter tags, than we can by deleting them all, and we can also do that by focusing on contributing to articles and sourcing our contributions, and letting the consensus on the talk page of that article, based on WP policy and guidelines, determine its layout and writing style, and not one person's attempt at GA and FA glory. Dcs002 (talk) 23:49, 31 December 2015 (UTC)[reply]

@Ottawahitech: To answer this, AfD may involve notifying the creator, who may think he/she "owns" the article because he/she created it. Although nobody owns any one article, editors are encouraged to start new ones because it is one of the best way to expand Wikipedia, adding new knowledge/expertise, all without acting like they own the article. Notifying the article creator of why the article is up for deletion is a great way in my opinion to let the creator know how to improve the article and should participate in that discussion in a professional manner (i.e. without acting like they own the article). An editor acting like he/she "owns" content is how edit wars may occur. Sam.gov (talk) 07:05, 29 December 2015 (UTC)[reply]

The only time where informing the creator matters is when it's an article with a lot of unsourced (or no source) information, then the creator who presumably added the content would at least be the first person to contact about finding examples of sources. It's just logical to me that the person who added the content would at least have an idea where they got it from, if they don't fine but they would at the very least be the person most likely to suggest sources. -- Ricky81682 (talk) 06:34, 30 December 2015 (UTC)[reply]
Can I get an AMEN! The creator (and major contributors) are a great and logical place to start looking (just like WP itself), but they are not the last place to look, nor is the onus on them for anything. We own WP articles, we control them, the onus is on us always. I know if I add careless content to an article it will surely be deleted, whether I did it intentionally or not. In the end WE decide whether to fix it or flush it, but it is practical to consider carefully what we would flush, and whether is can be fixed. Again, Ricky81682 nailed it, and he did so with far fewer words than I ever could. Dcs002 (talk) 10:17, 30 December 2015 (UTC)[reply]
And that's why a new article sometimes goes to AFD almost immediately with a statement along the lines of asking the creator for some information, especially if the sources isn't complete or entirely accurate or whatever. If they don't, that's fine but then it's up to volunteers around here and unfortunately the bystander effect is human nature. -- Ricky81682 (talk) 11:12, 30 December 2015 (UTC)[reply]

I want to go back to the idea that "the creator of an article is personally responsible for it". OK... in which case, the creator should be responsible enough to follow what happens to the article he/she created. I would extend this to major post-creation contributors (they are responsible for their contributions)... which means there should be no need to alert the creators (or other major contributors) that the article is being nominated for deletion... since article creators (and other major contributors) will be responsible enough to have it on their watchlists. Blueboar (talk) 15:28, 1 January 2016 (UTC)[reply]

or for the rare case of an editor that refuses to use a watchlist, to visit the page regularly to make sure it is all up to date or uses something like WP:RSS. If they walk away after creation and do not bother to keep an eye on it, it's very hard to argue they must be notified if they are refusing to take steps that show awareness and oversight of the article. --MASEM (t) 15:44, 1 January 2016 (UTC)[reply]
  • the creator should be responsible enough to follow what happens to the article he/she create I am trying to reconcile this advice with my own experience at Wikipedia and wondering at what point my "responsibility" ends. For example, back in 2010 I created the article Criticism of Nortel which was nominated for deletion 6 months later. The result of the discussion was a redirect/merge (not clear to me which)
In your opinion am I still "responsible" for:
  • the redirect
  • the contents on the mergee article
  • if I stop editing wikipedia does that make me an irresponsible person
(risking sounding like the old man who tells stories no one is interesting in) Ottawahitech (talk) 15:22, 2 January 2016 (UTC)please ping me[reply]
If you still care about the material, then yes, you still have a responsibility to monitor it. If you no longer care, then you can end that responsibility. Wikipedia is an organization of volunteers. In a voluntary organization, responsibility isn't something that is assigned ... it is something that is willingly taken. We can always stop taking responsibility... we can always hand responsibility off to others... but if we stop taking responsibility for material we add, we no longer have a right to complain about what happens to it. Blueboar (talk) 17:52, 2 January 2016 (UTC)[reply]
Blueboar, all of my arguments so far agree with your position here except one, and that is my agreement with Ricky81682's idea that the creator and the major contributors are the logical people to consult if an article needs better sourcing or other fixes. It makes sense to me that they would be more likely to have, or know where to find, whatever content or sources the article needs. They have also demonstrated a willingness to put some effort into the article already, so they might be more likely than most to be willing to fix the article. That is why I think creators and major contributors should be notified. Doing so would at least demonstrate an awareness that it might be possible to fix the article rather than delete it.
You say if we stop taking responsibility for material we add, we no longer have a right to complain about what happens to it. I would take that one step further and say whatever work we contribute to WP belongs to the world once it leaves our computers, and the world will do whatever it wants with it. (We never have "the right to complain" about it.) We all have to accept that before we start contributing. The only question we should be considering in such cases is whether the material makes WP a better encyclopedia. It's hard to trust that XfD discussions will be decided on that criterion (or its derivative policies and guidelines), and I think we all know cases when they were not. That is where I see the problem. I think we should make sure the nom has several built-in opportunities to pause and consider what is really best for the encyclopedia, and whether an article can be improved. Notifying the creator and major contributors are good opportunities. There are many other steps we could be taking, but those notifications are a very good idea, IMO. Dcs002 (talk) 00:39, 6 January 2016 (UTC)[reply]
Re: "They have also demonstrated a willingness to put some effort into the article already, so they might be more likely than most to be willing to fix the article"... I disagree with this premise. If the article creator actually had put some effort into the article, he/she would have found sources to established notability, and the article would not have been nominated for deletion in the first place.
There is a balance between inclusionists and deletionists... but we intentionally put the "burden of proof" on inclusionists. WP:BURDEN makes this clear... The onus is on those who add information to supply sources, not on those who wish to remove information to show that sources don't exist... this holds true for supplying sources that establish notability. We don't require that deletionists "prove" that the topic isn't notable... we require that inclusionists "prove" that it is notable (by supplying sources).
This is something that is missing from WP:BEFORE... the burden of the article creator to properly establish notability before they submit the article to mainspace. we need to explain that article creators need do a minimal amount of work before they submit an article. If they do this, their articles are much less likely to be nominated for deletion. Blueboar (talk) 14:46, 6 January 2016 (UTC)[reply]
The creator is easy to notify and I think generally is. "Major contributors" are more difficult is define and find though. -- Ricky81682 (talk) 05:22, 6 January 2016 (UTC)[reply]
Very true. I think a best effort, or a good faith effort is the most we can expect on that point, especially on articles with thousands of edits, and half are vandalism or edit warring. Unless someone can define who they are and somehow make a sortable list with each page, I think we'll have to extend some trust to noms that they notified the people who they thought were major contributors. Or maybe ask them to list the editors they notified? Dcs002 (talk) 06:07, 6 January 2016 (UTC)[reply]

COMMENT - if an article has a lot of "Major Contributors", I find it unlikely that it will be nominated for deletion in the first place (surely one of those contributors will have provided sources that establish notability)... On the other hand, if there are a lot of contributors - and none of them have been able to properly establish notability, then that says a lot in itself... it shows that the topic probably isn't actually notable (and thus should be deleted). Blueboar (talk) 14:46, 6 January 2016 (UTC)[reply]

@Blueboar: good point, if there isn't notability established, it should be deleted; there should be a AfD template placed at the top of the article so that major contributors and the creator is aware. Sam.gov (talk) 17:32, 7 January 2016 (UTC)[reply]
If they have the article on their watch lists (and they should, if they actually give a damn about the article), then there is no reason to notify them... they will already know that the article has been nominated.Blueboar (talk) 20:45, 7 January 2016 (UTC)[reply]
Yep, That's what watch lists are for, and contributors are encouraged to use them often; of course editors can have a lot on their watch list, so if it is something really important, then a notification can be beneficial as well. Sam.gov (talk) 19:23, 8 January 2016 (UTC)[reply]
My point above is the AfD template only shows in the watch list once. All it takes is for someone to correct a typo (or anything else) in a subsequent edit and that notification is gone from your watch list. You actually have to visit the article again to see the template. You have to go to another location, not yet in your watch list because you don't know about it, to participate or monitor the discussion. Maybe I am an extreme case but I currently "watch" 8,000 articles. Important stuff can slip through the cracks. Trackinfo (talk) 20:32, 11 January 2016 (UTC)[reply]
I think you're right about that. I tend to check my watch list often and have quite a few articles on it. Sam.gov (talk) 18:38, 12 January 2016 (UTC)[reply]

Lack of participation and vocal minorities

There is a severe lack of participation, relative to their overall numbers, by inclusionists and other non-deletionists on the talk pages of many of those policies and guidelines that relate to deletion. The number of deletionists at these venues is out of proportion to their actual numbers (in no small part because the deletionists are not creating content, and because inclusionists and other non-deletionists rarely become aware of the 'deletion machine' until they are personally on the receiving end of it). I suggest that inclusionists/non-deletionists should be given more encouragement to show up at these venues. We should, for example, actually tell people whose contributions are deleted (for reasons other than things that are non negotiable because, for example, they are beyond our power to change, such as copyright, or because they are manifestly incompatible with the aims of the project, such as vandalism and hoaxes) that consensus can change, and supply them with details of the mechanism (ie RfC and other talk page discussion) for effecting changes to policies and guidelines. I think AfD notification templates should be changed to include this kind of information. It is obvious that most of the victims of deletionism haven't a clue how to complain, because we very often, at best, sneakily do not tell them, and, at worst, talk about policies and guidelines as if they were set in stone. James500 (talk) 15:54, 14 December 2015 (UTC)[reply]

  • The {{Afd-notice}} template gives a link to the deletion discussion, and explains that all users are welcome to contribute to it. Editors making XfD nominations should be encouraged to make clear nomination statements expressing specific reasons why an article should be deleted. Perhaps with Twinkle the nomination statement could be copied to the user's talk page along with the afd-notice. There is already a space to add custom text when posting some speedy notices - something like that. Ivanvector 🍁 (talk) 16:08, 14 December 2015 (UTC)[reply]
That isn't the sort of notification that I have in mind. The sort of notice I have in mind is something like: "Your article was deleted because it failed WP:ORG. If you don't like WP:ORG, you are entitled to go to the talk page of that guideline (WT:ORG) and ask for changes to that guideline." followed by some description of the RfC process. The AfD notice template is a good example of the problem. It tells editors to go to the AfD and discuss Wikipedia's policies and guidelines there, in a way that gives no clear indication whatsoever that those policies and guidelines can be changed or that the correct forum for seeking such changes is the talk page of the policy or guideline in question. An editor who has an article deleted is very likely to be placed under the impression that he has no recourse if the problem is with the content of a policy or guideline. They will assume the policy or guideline is immutable. This is one reason why editing Wikipedia has become a secret art and mystery. James500 (talk) 19:58, 14 December 2015 (UTC)[reply]
Oh I think that's an exceptionally bad idea, as you framed it. It probably wouldn't be terrible to send users to a page explaining the concept of policies and guidelines and how we develop them, and encouraging them to become more familiar and get more involved in the process, because everyone really can participate here despite there sometimes being a steep learning curve. Those of us who are XfD regulars and are familiar with the shorthand jargon we use could certainly do a better job of explaining things to newcomers in plain language; I try to do that myself when I have my wits about me. But I think suggesting to a new user that if they don't like guidelines that they should just go change them is a very, very bad idea. XfD forums are much friendlier places for newcomers than guideline talk pages, in my experience, especially when someone shows up demanding changes. Ivanvector 🍁 (talk) 20:19, 14 December 2015 (UTC)[reply]
I don't think that someone would show up demanding changes, I think that there would be a massive snowball pile-on, possibly of hundreds of people, because I think there is overwhelming hostility towards deletionism from the vast majority of people in the world, apart from a very small but very vocal and determined minority who have just about 'commandeered' some policies and guidelines, it is just that most people have no idea how to seek changes. That said, XfD is one of the most toxic environments on the project. For the creator of the page it is much like being put on trial for weeks. Guideline talk pages are nothing compared to that. The problem with guideline talk pages isn't that they are unfriendly, but simply lack of participation from certain groups. James500 (talk) 14:43, 15 December 2015 (UTC)[reply]
  • OK, I have to challenge the premise of this thread and the assertion that our policy and guideline pages are in any way dominated by "deletionists" who "are not creating content". On the contrary, I suspect that if you actually look into the editorial history of most participants on policy and guideline page discussions (and at XfD discussions), you will find editors who are quite active in creating content (by either starting new articles, or improving existing ones). Blueboar (talk) 13:39, 15 December 2015 (UTC)[reply]
@Blueboar: I remember you favorably as a participant in some early categorization policy forming discussions, but have you looked at policy forming lately? I would go even further than user:James500 and say that some policies were formed by only a handful of participants. For example Wikipedia:Defining the guideline ubiquitously used in current wp:CfD so-called discussions and tell us how many were involved in forming this ‘consensus?

@James500: in addition to what Ivanvector said, I'd like to add that it's a bad idea to encourage people to seek to change an encyclopedia-wide consensus because of their grievances about a single article. Consensus isn't achieved by insisting the mountain come to you, but by you climbing the mountain. Finnusertop (talk | guestbook | contribs) 13:50, 15 December 2015 (UTC)[reply]

It seems a baseless slur to claim that people who != vote "delete" at AFD do not "create content." Skip the ad hominem attacks. Edison (talk) 22:46, 15 December 2015 (UTC)[reply]
I agree. Many people who I see regularly voting delete on bad articles at AfD are strong contributors of good content. Reyk YO! 06:33, 16 December 2015 (UTC)[reply]
Who? Because when I've checked all I found was deleting. First, they go to the article to tag it like crazy, then they delete whole paragraphs, finally they send it to AfD. That's not writing. --MurderByDeletionism"bang!" 16:15, 17 December 2015 (UTC)[reply]
You need to check harder then. Or at least, not just look for stuff that confirms your preconceptions. Consider myself, for instance. Most people would regard me as an evil scary kitten-eating deletionist. But I have two featured articles and three GAs to my credit, and have started around 30 articles. And I am by not unusually productive. Writing an encyclopedia is not just throwing words at a page. There has to be some thought given to accuracy and quality. We are presenting an online encyclopedia and that means taking care to present information that is as accurate as we can make it, that is neutral, that is not buried under a mountain of trivia or diluted across too many articles. This means aggressive removal in some cases. Deletionists understand this but inclusionists for the most part do not. To put it another way, I want an encyclopedia that is both very big and very good, but you only care about big. Reyk YO! 16:31, 17 December 2015 (UTC)[reply]
Writing an encyclopedia is not just throwing words at a page. Do you mean like this?[4] Because an article start like this wouldn't last two seconds on Wikipedia. (FYI - It does look rather like words thrown at a page, but in 2008 Wikipedia was more forgiving!) Also, Wikipedia is not about TRUTH, just verifiability. Deletionists only understand how to delete. It's is a whole lot easier than writing! What deletionists don't understand is how to write. They're negative, pessimistic, and close minded. They're only interested in creating an exact replica of Britannica Encyclopædia. (Why? When there's already one does the world need two! ¯\_(ツ)_/¯) Deletionist are trying to achieve their goals with fewer and fewer editors because they are driving off writers from Wikipedia (and they themselves are not writers!) There are a number times in AfD that the argument is that it is just poorly written. I've even argued that an article ought to be deleted because other sites can do a better job of writing the article than Wikipedia can, and since Google now defaults to Wikipedia, it should be deleted. Of course, if deletionist were really worried about quality, this argument could be applied to many subjects. This lack of editors means that deletionists believe that in order to safe face on quality, they must delete more and more articles since there are fewer editors are around to keep an eye on articles. If deletionists were truly interested in quality, they would be encouraging to new editors, they would welcome new articles, they would work on fixing articles, but instead they just send them to AfD. Because that is the only way they know how to fix articles!
Happy retirement, Reyk! --MurderByDeletionism"bang!" 17:37, 17 December 2015 (UTC)[reply]
Well, that's desperate, having to dig up a ten year old edit to try to make me look inconsistent or hypocritical. Then you follow it up with a long, agitated, inaccurate hate-rant against your perceived enemies, and finish with a mocking comment about how I'm not as active here as I used to be. Very unfortunate debating tactic. I do not have time to waste on this kind of fuckwittery so go rant at someone else. Reyk YO! 18:05, 17 December 2015 (UTC)[reply]
But at least you're not biased. DonIago (talk) 17:40, 17 December 2015 (UTC)[reply]
I've said nothing about participants at XfD or !voting at XfD. "Deletionist" is not an ad hominem in the context of discussing overall participation in deletion-related discussions as it is directly relevant. When I look at the participants on the talk pages of policies and guidelines that are related to deletion, it appears to me that editors that I would expect to be normally regarded as deletionists (a term that does not include everyone who regularly !votes for deletion at AfD let alone everyone who so !votes once), and especially those people who do not create any content, or who create little or significantly less (which is what I mean by "not creating content" ie "not creating enough to keep them occupied"), and want to delete significantly more content, are disproportionately over represented. James500 (talk) 19:34, 16 December 2015 (UTC)[reply]
If you want to call people "deletionists" and then tell them it's not meant to be an insult or a criticism, go ahead but don't be surprised if people disagree. You wouldn't be using it if it didn't mean something. Point out a specific AFD and stop calling people any sort of label. And MurderByDeadCopy-type discussions are not atypical from what I have seen which is why this tends to go in circles with little resolution. Are you concerned about editors with little to no activity outside of AFD discussions? Do you think we should put an SPA notice about that akin to editors who only edit in a particular topic area? It's a suggestion but I don't think it'll be particularly popular. I'm regularly questioned by individuals over a "lack" of content creation since I've gotten focused on finding other people's old content in draftspace and seeing if it's ready for mainspace. One individual points out how much content creation they do which consists of going on partisan article and trying to balance it (or add more of the opposite type depending on your view), which largely gets fought and revised and removed for what it is. That's something but not what I'm interested in. I simply don't get the mass "AFD is a terrible place because articles get deleted" comments here: deleted articles regularly get restored and userified if the editor asks to do so. There's a bigger issue with old attack pages and the like that haven't really been deleted. From looking over old stale drafts, you'll find hundreds of old articles that were going to be deleted and yet still remain around here in some hidden little nick and cranny that's been overlooked. The problem is then separating the wheat from the chaff. -- Ricky81682 (talk) 22:36, 26 December 2015 (UTC)[reply]
Please don't put words into my mouth or pretend to be deaf. That has nothing to do with anything that I said. What I said is that the apparent consensus on the talk pages of some of our policies and guidelines is probably a so called 'local consensus' (WP:LOCALCONSENSUS) that is not really any consensus at all. Meaning that they are not valid policies or guidelines. James500 (talk) 04:49, 29 December 2015 (UTC)[reply]
Can you point out one example? I've found that the policies and guidelines do tend to change to reflect discussions. It's when people bring up unique situations where there's an argument that generally leads to "create a new policy". For example, I've been part of a rampant series of discussions about longevity biographies and while there's been arguments that there's a consensus of something, the discussions show that there isn't one at all anywhere (or at least a settled one). One could argue that the policies don't reflect the consensus while I'd argue that there isn't one and writing one down as if it exists ends all discussions in the wrong place to me. -- Ricky81682 (talk) 06:41, 30 December 2015 (UTC)[reply]

There is a severe lack of participation, period. There is lack of participation on talkpages, lack of participation in most XfDs, lack of participation in guidelines development, lack of participation in RFCs, lack of participation here. How can anyone characterize the result of discussions between a handful of editors , some of whom show up only for one vote then disappear for good, as consensus? Ottawahitech (talk) 05:24, 7 January 2016 (UTC)please ping me[reply]

XfD culture: Wikipedia:Other stuff exists

Many participants in XfD discussions who advocate for deletion frequently point to Other stuff exists as an argument that should be avoided in XfD debates. However this results in inconstency and creates a process where older pages survive while newer (possibly more notable) pages are deleted on a regular basis. Ottawahitech (talk) 23:01, 31 December 2015 (UTC)please ping me[reply]

While I agree that this probably exerts some pressure for inconsistency in favor of old articles, it this the place for this discussion? Does this pressure actually result in the outcome you describe? Dcs002 (talk) 00:06, 1 January 2016 (UTC)[reply]
AND then you have all those quoting OSE but never following its advice: it is important to realize that countering the keep or delete arguments of other people, or dismissing them outright, by simply referring them to this essay by name, and nothing else, is not encouraged. Ottawahitech (talk) 17:34, 1 January 2016 (UTC)please ping me[reply]
Keeping in mind that one AFD that closes "delete" does not create a de facto standard that all similar articles of the same topic should be deleted, it is reasonable to start a discussion at an appropriate page to go "Okay, so this article got deleted, and we have X more that are like it that have the same issues that were addressed in the AFD. What should we do about them?" This might cause a voluntary purge of such articles, an effort to improve the ones that have the best chance to stand out, or the like. It is fait accompli to nominate the entire batch of other articles at once without any discussion based on the single AFD. --MASEM (t) 15:32, 2 January 2016 (UTC)[reply]

Templates and Categories

New discussion on notifications. When a Template goes to TfD, when a Category goes to CfD, these moves should be notified on the articles affected. Templates guide the look of the content of many articles, Categories by definition help uses in cross navigating articles on the same subject. So their removal plays a part in the content of the article. But most TfD and CfD discussions happen in a VERY low traffic area of the back reaches of wikipedia. I don't take the time to search through those lists very often, there is usually no value to that time. But then I am shocked at the craziness of some removals. When I trace them back it was a discussion of at best one other participant. "Lets delete this" "Looks good to me" Poof its gone from hundreds of articles. And the first notification on the articles affected is the removal, after it is essentially a done deal. Trackinfo (talk) 21:32, 18 January 2016 (UTC)[reply]

Seems reasonable. However, in many cases, a category upmerge would be of very little interest to those interested in the article itself, and a category rename would often be of less interest. Navigation templates are often of interest only to those who use the links, which is almost always a small subset of article readers and editors. As an even more absurd example, a change of the category structure generated by templates such as {{cn}} should be of very little interest to anyone other than editors who use the categories. — Arthur Rubin (talk) 23:03, 18 January 2016 (UTC)[reply]
  • Templates already appear on the article including a link to the discussion. Do you want more done? Now, categories? I'm all for that. Is there a technical way to make any part of the category page content show up? I don't think there is. One other problem is that the WikiProjects about the subject are only noticed if the template/category is in those projects which I find is quite rare. -- Ricky81682 (talk) 21:50, 26 January 2016 (UTC)[reply]

Two edit filter RfCs: Modifying existing filters and enabling the block function

Please share your thoughts on two RfCs regarding updates to the edit filter guideline and enabling the extension's blocking ability. Sam Walton (talk) 18:13, 9 January 2016 (UTC)[reply]

RfC: Modifying existing edit filters

The edit filter guideline's recommended uses section currently states that edit filter managers should "generally be tested without any actions specified (simply enabled) until a good number of edits have been logged and checked before being implemented in "warn" or "disallow" modes." One concern that has been raised since the guideline was written is that filters which are set to the stronger settings can still be changed while in these modes; this can be just as damaging as mistakes are easy to make with regex, resulting in the possibility of blocking huge numbers of edits because of something as simple as missing a closing bracket.

Should the Edit filter guideline be changed to include the following text?:

Edit filters with the "disallow" or "throttle" settings enabled should not be modified without first disabling those settings temporarily. The filter should then be monitored for an amount of time deemed appropriate by the edit filter manager before the settings are re-enabled.

I'd like to add that this needn't be a long period of time; for most filters a few minutes to make sure that hundreds of edits aren't suddenly being disabled or something similarly drastic would be sufficient.

This would also apply to the block ability if the below proposal also passes.

Support edit filter guideline modification

  1. Support as proposer. I don't think this is a drastic change but it should help reduce filter accidents. Sam Walton (talk) 18:15, 9 January 2016 (UTC)[reply]
    I support a slight change in wording however, given the comments below, that edits should be tested rather than tested specifically via disabling of the filter. We could add a note for the testing methods (temporary disabling, batch testing, second test filter) or something later. Sam Walton (talk) 11:49, 20 January 2016 (UTC)[reply]
  2. Support I've seen more mistakes with modifying filters than creating new ones. For me this is one of the more strict clauses of the guideline. Just a side note that the batch testing tool can be a very close friend when it comes to modifying filters :) — MusikAnimal talk 18:54, 9 January 2016 (UTC)[reply]
  3. Support Makes perfect sense and, frankly, I'm surprised similar wording isn't already in use. Etamni | ✉ | ✓  18:59, 9 January 2016 (UTC)[reply]
  4. Support. I can't think of one good reason why the new language isn't a good idea. --IJBall (contribs • talk) 19:26, 9 January 2016 (UTC)[reply]
  5. Support — Ched :  ?  19:39, 9 January 2016 (UTC)[reply]
  6. Support reasonable. Keegan (talk) 19:59, 9 January 2016 (UTC)[reply]
  7. Support Makes sense. Armbrust The Homunculus 23:55, 9 January 2016 (UTC)[reply]
  8. Support, although I grant the strength of the oppose argument: when it's apparently an emergency situation, we should let this thing slide; we ought to add a statement to the end, "Filters may be enabled with these settings untested in an emergency, although editors need to be available immediately, watching for false positives and resolving them." Otherwise, it's a perfect WP:IAR situation (so what's the point of creating a rule when we can envision a good situation for ignoring it?), because when we need a newly created filter on an emergency basis, improving Wikipedia absolutely demands that we throw it in without testing it. But yes, when it's not an emergency creation, we shouldn't permit filters to do anything beyond tagging until they've demonstrated through tagging what they're going to do. Nyttend (talk) 14:27, 10 January 2016 (UTC)[reply]
  9. Support No software engineer worth a crap deploys anything without testing it first. NE Ent 22:37, 10 January 2016 (UTC)[reply]
  10. Support No software engineer who isn't worth a crap is a real software engineer. Robert McClenon (talk) 03:27, 11 January 2016 (UTC)[reply]
  11. Support, for the above obvious reasons. --Carnildo (talk) 02:33, 12 January 2016 (UTC)[reply]
  12. Support per above. Kharkiv07 (T) 03:54, 14 January 2016 (UTC)[reply]
  13. Support per the proposer. Thryduulf (talk) 23:00, 18 January 2016 (UTC)[reply]
  14. Support. Sounds like a great idea. APerson (talk!) 01:08, 20 January 2016 (UTC)[reply]

Oppose edit filter guideline modification

  1. Oppose - I think this should not be stronger than making it a consideration when changing the filter, but having a highly abusive editor getting free reign for some time to see whether there are no false positives after the change can be highly disruptive to Wikipedia, possibly resulting in hundreds of edits to be reverted if edit filter manager and culprit are active during different times. I would expect that edit filter managers that do 'break' a filter in a bad way will and should be admonished strongly (including possibly losing the right for some time), and I, for one of the edit filter managers, do expect that to happen to me if I would ever break a filter in such a bad way. --Dirk Beetstra T C 12:12, 10 January 2016 (UTC)[reply]
  2. Oppose. The proposed wording feels too strong to me. In the last two months, disallow filters as a group have been edited more than 120 times (on average about 2 times per day). Mostly such edits tweak narrowly focused filters to combat specific persistent vandals. During that time, I'm not aware of any screw-ups causing large scale problems. Such screw-ups do occur occasionally, but as a practical matter they are rare. If an EFM is properly using batch testing prior to saving any changes (and they absolutely should be) then major problems can be avoided. Adding the extra step to disable and reenable the filter before every edit seems unnecessary. Perhaps for some complex edits the extra effort is appropriate, but as a general rule it seems more like a solution seeking a problem. Dragons flight (talk) 20:47, 9 January 2016 (UTC)[reply]
    There was one incident in the past two months that I found to be rather bad... and it could have been noticed with batch testing, I believe. So perhaps that should be written as our bare minimum requirement. The other thing is we sometimes have "emergency" filters, for large-scale disruption, where we don't want the filter disabled for any period of time. Batch testing would be most appropriate here as well, and as Xaosflux said, a test filter could be used in parallel if need be.
    There was one other incident that happened in the past 6 months, where anonymous users were inadvertently disallowed from editing talk pages (as ~~~~ was disallowed). That was quite bad, but it didn't show up immediately. It got maybe 10-15 hits over the course of several hours, so batch testing may not have been as telling.
    So I guess overall, it's just a matter of checking your work via the logs. That needs to be obligatory, as the issue I think I'm seeing is not incompetence but overconfidence with edit filter management — MusikAnimal talk 23:34, 10 January 2016 (UTC)[reply]
  3. Oppose. I'm all for prudent safeguards but, I don't believe this'd add much. We already point out in the lead and user right sections to exercise care when making adjustments as small mistakes can have a large impact. The interface also already has the syntax check tool to run on an inputted or existing filter's regex. This requirement would mean bloating the change logs/EFM activity levels to at least three entries for every change to these filters. (Incidentally, I wondered if the word "warn" was intended for the proposal rather than "throttle".) –87.115.76.251 (talk) 00:43, 28 January 2016 (UTC)[reply]
  4. Oppose this is the wrong way to do it. A better way is to make a test filter (sandbox) and use that for testing the modification.
    All the best: Rich Farmbrough, 18:21, 1 February 2016 (UTC).[reply]

Discussion of edit filter guideline modification

Not sure about requiring it to be "disabled" first, for example a parallel filter could be set to log only with the new change as a means of testing. — xaosflux Talk 19:43, 9 January 2016 (UTC)[reply]
Good point. I'd expect that most filter changes will be done without creating a test filter though, and this guideline change only says this 'should' be the case; it doesn't prohibit doing what you suggest, and no one's going to chase anyone down for doing it. Sam Walton (talk) 19:48, 9 January 2016 (UTC)[reply]
We don't need that bit about disabling, all we need to say is that the change is tested first. Graeme Bartlett (talk) 21:28, 9 January 2016 (UTC)[reply]
That's fair, I think I would still support the wording being that changes should normally be tested in some fashion, whether through a parallel filter, disabling first, or batch testing. Sam Walton (talk) 17:44, 11 January 2016 (UTC)[reply]
To the closer: It looks like there is/will be a stronger consensus here for this but with a slight change in the wording; namely that changes should be tested rather than explicitly tested via disabling the filter. Sam Walton (talk) 11:47, 20 January 2016 (UTC)[reply]

RfC: Enabling the edit filter's block function

When the edit filter was enabled on the English Wikipedia, the ability for it to block an editor who trips a filter was left disabled (see $wgAbuseFilterAvailableActions here); there were some discussions about the option around then, and there were two discussions (1, 2) prior to this RfC.

Currently the strongest setting for an edit filter on the English Wikipedia is to disallow the edit, where a user is restricted from making an edit if it trips a filter set to disallow. For some LTA users - to give an example - this can then become a game of attempting to navigate around the filter's settings by making a stream of slightly tweaked edits. When the user works out what they have to do to avoid the filter, they'll likely soon be blocked, the filter will be amended to fix the loophole, and they'll move to a new IP and start the process again. It could be extremely beneficial in this example to have the filter set to block the user upon their first attempt at making an edit, such that they have to switch IP before making just their second edit attempt, slowing them down and adding an extra layer of difficulty to the process. This is just one example of where the block option could be useful; there are many filters (for examples see 666, 673, and 674) which successfully (with 100% accuracy) target users who are always eventually blocked by patrolling admins, where this would save administrator time.

For this to be enabled, it seems the following changes should be made to the abuse filter configuration for the English Wikipedia:

  • $wgAbuseFilterAvailableActions[] = 'block' - Enables the block function
  • $wgGroupPermissions['sysop']['abusefilter-modify-restricted'] = true; - Restricts enabling the block function or editing filters where the block action is enabled to administrator edit filter managers
  • $wgAbuseFilterBlockDuration = 'indefinite' - Sets the block length for registered users to indefinite
  • $wgAbuseFilterAnonBlockDuration = '31 hours' - Sets the block length for unregistered users to 31 hours
  • $wgAbuseFilterAvailableActions = array_diff( $wgAbuseFilterAvailableActions, array( 'blockautopromote' ) ); - Disables the 'remove autoconfirmed' option, which is currently a restricted action

Blocks would be made by User:Edit filter (as specified by MediaWiki:Abusefilter-blocker; the account should be created prior to the first block automatically) and, as can be seen on meta, a customisable block description can be set (MediaWiki:Abusefilter-blockreason, which can take a second parameter showing the filter number). Blocked users, in addition to any warnings that are set in the filter, see MediaWiki:Abusefilter-blocked-display upon being blocked, which is again customisable.

The guideline would also need a section on the use of the block function, for which I would propose the following:

"The blocking function is extremely powerful and so may only be enabled for a filter which has received no false positives for the past 30 days or last 100 hits, and should only be used on filters where editors tripping the filter are always currently blocked manually. At least 3 administrators must agree that these requirements have been met, in a public venue such as the edit filter noticeboard prior to the enabling of this option. As with disallowing edits, a public post that a filter is to have the block function enabled is required, and the administrators who enable the setting or alter a filter with the setting enabled are considered responsible for its actions."

Should the edit filter's block function be enabled with the changes above, and should the guideline be expanded as described?

Support enabling block function

  1. Support as proposer. I've long felt that this would be a very helpful feature to have, and am confident it will only affect users we want to block. Sam Walton (talk) 18:15, 9 January 2016 (UTC)[reply]
  2. Support. There are certain things that should never be added and which are reliable indicators of users or IPs to block. I doubt we would want to use it much but there will be times when it comes in handy. I am thinking of my own proposal here where it is possible to define strings that have no legitimate use and are reliable indicators of the abuse we wish to stop. Coupled with review by a human to weed out any false positives then I think this is safe and desirable. --DanielRigal (talk) 18:24, 9 January 2016 (UTC)[reply]
  3. Support enabling with settings proposed, no opinion on the guideline The "use case" is laid out well and I trust the current EFMs with handling such a tool. I do have a caveat with the guideline which I'll note below.Jo-Jo Eumerus (talk, contributions) 18:30, 9 January 2016 (UTC)[reply]
  4. Support As I said in the discussions leading up to this RfC, I think adding blocking functionality to the toolset will work wonders toward combating long-term abuse. This will be a major deterrent for persistent sockpuppetry. With it I think we'll see many abusers give up, which means we can disable those filters, and just overall stop wasting our time chasing them down over and over again. The proposed precautions I think will eliminate major concerns. Our regular edit filter managers are quite good and I trust blocks will only be used where appropriate — MusikAnimal talk 18:48, 9 January 2016 (UTC)[reply]
  5. Support. I have some concerns (raised below) but in general I feel that this is a good idea. Etamni | ✉ | ✓  19:13, 9 January 2016 (UTC)[reply]
  6. Support. In practice, blocking filters should be rare and focused on persistent vandals, but I do think having the option would be useful. Dragons flight (talk) 20:53, 9 January 2016 (UTC)[reply]
  7. Support This will help control some kinds of trouble. Graeme Bartlett (talk) 21:21, 9 January 2016 (UTC)[reply]
  8. Support May be useful, but should be used with extreme care. --Dirk Beetstra T C 12:15, 10 January 2016 (UTC)[reply]
  9. Support as above. Sounds like a great idea - will save lots of time as well. SQLQuery me! 00:33, 15 January 2016 (UTC)[reply]

Oppose enabling block function

  1. Oppose - I can not support the use of non-human blocking. There are far too many exceptions to rules that "code" can not account for. — Ched :  ?  19:41, 9 January 2016 (UTC)[reply]
    Are you aware we have bot blocking already on enwiki? — xaosflux Talk 19:44, 9 January 2016 (UTC)[reply]
    No I was not - but I'm not surprised. The fact that it exists does not however, change my view on whether it's proper or not. But thanks for the info. — Ched :  ?  19:47, 9 January 2016 (UTC)[reply]
  2. Oppose for the same reason as Ched. I'm aware of the blocking bots, and aside from blocking open proxies, I'd still prefer block to be one of the few features in human hands. Blocks need to be able to be explained or defended by the person that made them if needed. Keegan (talk) 19:58, 9 January 2016 (UTC)[reply]
    Per the proposal, admins contributing to the filter are fully responsible for any resulting blocks. A "mistake" with the filter is not an excuse for an inappropriate block, and if the guideline is followed, mistakes should not happen — MusikAnimal talk 20:58, 9 January 2016 (UTC)[reply]
    Of course they shouldn't happen, but they can happen. With a project this large and storied, our track record has shown that pretty well :) I'd rather a person make that mistake, 'tis all. Keegan (talk) 06:38, 10 January 2016 (UTC)[reply]
  3. Oppose per Ched and Keegan. I also have great doubts that our automated processes are faux-intelligent enough to distinguish between an editor "attempting to navigate around the filter's settings by making a stream of slightly tweaked edits" and a klutzy new editor making a good faith effort to make an edit they believe could be legitimate. The Big Bad Wolfowitz (aka Hullaballoo) (talk) 18:25, 10 January 2016 (UTC)[reply]
  4. Oppose Wikipedia explains nothing to new editors now. There is zero reason to create new and improved ways to run them off! (Unless, of course, that is the goal here?!) --MurderByDeletionism"bang!" 18:49, 10 January 2016 (UTC)[reply]
    @MurderByDeadcopy: Per the proposed filter guideline text, this would only be used on filters where there is a minute chance of false positives; the examples I gave have all been disallowing edits for over 6 months with exactly zero false positives. Sam Walton (talk) 11:56, 20 January 2016 (UTC)[reply]
    But . . . is 6 months enough time to comprehend Wikipedia's bureaucratic bloat? --MurderByDeletionism"bang!" 00:55, 21 January 2016 (UTC)[reply]
    @MurderByDeadcopy: What do you mean? Sam Walton (talk) 00:10, 23 January 2016 (UTC)[reply]
    New editors are not given any instruction here at all. New editors learn something only after they do something wrong. Half of all new editors never receive a "Welcome." New editors are never told that essays are not rules. So it is possible to edit on Wikipedia for years and not know about or even heard of certain rules. This is why I empathize so much for new editors since they, not only are oftentimes the only ones on Wikipedia who actually do assume good faith, but also get block for innocently going against some obtuse rule that nobody ever told them about! --MurderByDeletionism"bang!" 18:09, 23 January 2016 (UTC)[reply]
  5. Oppose. I believe humans need to be blocking accounts, because a specific individual needs to be accountable for doing so. I agree with HW, Keegan and Ched. There's a world of difference between automated blocks of known proxy IP addresses (for which we already get plenty of complaints, and because of which we needed to develop an account creation team), and blocking actual accounts. Risker (talk) 20:16, 10 January 2016 (UTC)[reply]
  6. Oppose per Risker (and transitively HW, Keegan and Ched). And especially MurderByDeletionsim. NE Ent 22:36, 10 January 2016 (UTC)[reply]
  7. Strong oppose - In a universe with perfect software writers, this might be worth enabling, but I haven't see perfect software writers around here, even on the payroll of the WMF. (Even with perfect software, I would prefer t human review. I certainly don't trust WMF developers, and don't know when I should trust volunteers to write perfect softare.) I won't trust a script to block people, and to require that they request unblock. That's just wrong. Robert McClenon (talk) 03:25, 11 January 2016 (UTC)[reply]
  8. Oppose The first example given is 666. For me this says "You may not view details of this filter because it is hidden from public view." The consequence would be people being blocked without the details being clear. The Kww case also indicated that there is inadequate oversight of edit filters and so their power should not be increased. Andrew D. (talk) 12:27, 11 January 2016 (UTC)[reply]
    If the exact rules were public, then it would be extremely easy for abusive users to sidestep them. This is part of the problem now - that they can work out what the rules are easily. SQLQuery me! 00:37, 15 January 2016 (UTC)[reply]
    @Andrew Davidson: Are you aware that since the Kww case we have introduced an entire new guideline, new noticeboard, and new mailing list to improve the oversight and use of the edit filter? Sam Walton (talk) 11:56, 20 January 2016 (UTC)[reply]
  9. Oppose: I've seen too many screwed-up automated processes (see: the endless problems with title blacklist false-positives) to trust this. --Carnildo (talk) 02:32, 12 January 2016 (UTC)[reply]
  10. Oppose mistakes happen all too frequently. We need an actual human being behind the block button. I know the proposal makes the filter creators responsible for all blocks, but what if they leave? What if they are on Wikibreak? Particularly for edit filters with some hidden behaviour, unblocks for very innocent false positives may become very tricky. Happy Squirrel (talk) 19:04, 12 January 2016 (UTC)[reply]
  11. Oppose I can not support the blocking of any account by an automated process. We need to have a human looking at the edits to see if they warrant blocking. -- GB fan 12:18, 13 January 2016 (UTC)[reply]
  12. Oppose I'm not ready for this yet, before a step this large is taken more oversight of the edit filter system is necessary. Kharkiv07 (T) 03:54, 14 January 2016 (UTC)[reply]
    @Kharkiv07: What aspects of the edit filter do you think need more oversight, and how could we achieve that? Sam Walton (talk) 00:13, 15 January 2016 (UTC)[reply]
  13. Oppose. I'm assuming that User:Edit filter is going to be set up as a bot. Bots malfunction sometimes. Can anyone else see the problem with this? Steel1943 (talk) 00:28, 15 January 2016 (UTC)[reply]
    No such user exists at this time. If I understand correctly, it would be a function of MediaWiki - the same function that already disallows the very same edits to the same users. SQLQuery me! 00:39, 15 January 2016 (UTC)[reply]
    From what I understand, User:Edit filter would be controlled by the extension and created upon the option being enabled here, not as a normal bot. Sam Walton (talk) 14:39, 15 January 2016 (UTC)[reply]
  14. I can see too many failure cases for this, even if it's a legitimate user reporting an edit in violation of such a filter, and getting slapped with an automatic block. Blocks should be imposed by a human admin willing to take responsibility for doing so, not an automated process. Seraphimblade Talk to me 18:36, 23 January 2016 (UTC)[reply]

Discussion of enabling block function

As an addendum to the proposal, there has been discussion here about automatic pinging of administrators involved in an edit filter with the block function enabled that makes a block, though those discussions are ongoing and not vital to the above proposals. Sam Walton (talk) 18:13, 9 January 2016 (UTC)[reply]

  • Putting my caveat about the proposed guideline here: One needs to consider the damage from not enabling a block function, including users being driven away by the troublemaker that is the filter's target. The guideline is a bit too focused on "false positive" blocks, which are the most important consideration/limitation in any blocking filter but not the only one.Jo-Jo Eumerus (talk, contributions) 18:30, 9 January 2016 (UTC)[reply]
    • @Jo-Jo Eumerus: I'm not sure I follow what you mean, could you elaborate? Sam Walton (talk) 19:17, 9 January 2016 (UTC)[reply]
      • The issue I have is that the guideline does not seem to consider the possibility at all that sometimes, blocking based on a filter with some false positives is necessary to avert bigger damage. I don't know if such things have ever happened here on Wikipedia but I have some offsite experience with aggressive vandals that engaged in wikistalking and attacking other editors to such a degree that some "collateral damage" was considered to be necessary to get rid of these vandals.Jo-Jo Eumerus (talk, contributions) 19:25, 9 January 2016 (UTC)[reply]
  • (edit conflict) While I support the concept, I have a concern about auto-confirmed users possibly being blocked for an indefinite term for triggering one of the selected filters. Just because everyone who has previously triggered a particular filter is eventually blocked, doesn't mean that everyone who ever triggers it will be. Take, for instance, a LTA case where a user continuously attempts to insert his/her own (uncommon) name into articles. The filter is created and the edits get blocked. Now we start blocking those accounts. And someone with that identical name becomes an international news figure. Dozens or perhaps hundreds (or more?) editors see a news story, type the name into Wikipedia and see there is no article (or they see a previously deleted article). They then create an article and try to save it, only to become blocked for their effort. This needs to be considered -- I'd rather just block the edit than have legitimate editors indef-blocked by accident, even where there are procedures for appealing. Etamni | ✉ | ✓  19:30, 9 January 2016 (UTC)[reply]
    My recommendation would be (in this specific case) not to filter-block - it doesn't look like a serious case of disruption anyway. Beyond that, I already recommended that admins and editors regularly check the Abuse Filter block log to catch any false positives; perhaps this could mitigate/alleviate the issue.Jo-Jo Eumerus (talk, contributions) 19:37, 9 January 2016 (UTC)[reply]
Filter 673 was one of the filters used above as an example, and was in mind as I wrote the above comment. There is no way to know, at the time a filter is created, how common usage of the filtered term might change in the future. To indef-block auto-confirmed users for accidentally hitting such a filter is problematic to me. Other than that possibility, I'm fine with turning on the blocking options. Etamni | ✉ | ✓  20:13, 9 January 2016 (UTC)[reply]
We do need monitoring of the filters to see what happens. Unblocks should be able to happen in under 31 hours, which could be the time otherwise selected for IPs. Graeme Bartlett (talk) 23:57, 9 January 2016 (UTC)[reply]
Generally speaking, if you block a user too early int heir career, they're probably gone by the time the unblock happens. Adam Cuerden (talk) 19:07, 10 January 2016 (UTC)[reply]

RfC on Wikipedia:Authority Control

The Template:Authority control is currently used on more than 450,000 articles. As described on Help:Authority control, "Authority control enables researchers to search more easily for pertinent information on the subject of an article". Which external sources are acceptable in the template? Fram (talk) 16:47, 25 January 2016 (UTC)[reply]

Background

The Template:Authority control was created here in June 2009 (it existed already in the German Wikipedia) and moved to its current name in September 2010. Over the years, it got added to more and more articles, more and more sources got added to it, and it got integrated with Wikidata. Discussion over what sources to add was, as far as I can see, mostly limited to the talk page of the template, not to Help:Authority control or Wikipedia:Authority control, and no policy or guideline governing the template seems to exist.

Considering that the template gives the impression of being a list of special, approved sources, and that while the original idea was simply to have unique identifiers for each subject, it has morphed into a kind of reference pointer as well (to use a snippet from the lead of Help:Authority control: "[...]so that the information in the article can be easily cross-referenced[...]"), I think it is time to write down which sources are acceptable in it and which aren't. Fram (talk) 17:04, 25 January 2016 (UTC)[reply]

Wikidata approved sources

We can't simply rely on Wikidata to only provide pointers to reliable sources. While not included in Authority Control yet, Wikidata offers standard a FindAGrave link for every biography of a no-longer-living person. FindAGrave is considered to be avoided at nearly all costs on enwiki, as it is in general not a reliable source.

However, a similar (though perhaps somewhat better) source from Wikidata is already approved in the template and used on enwiki, even though it is also a wiki: MusicBrainz (which is specifically discussed and approved in the second paragraph of the lead of Help:Authority control). It was this link that caused me to discuss this at Wikipedia:Reliable sources/Noticeboard#MusicBrainz and from there to start this RfC.

I don't think it is a good idea to link such specialized wikis (MusicBrainz now, IMDB and others next?) in a quasi-official template like authority control, and I think it should be restricted to some more centrally controlled, truly authoritative sources like national libraries and similar things, for which it was originally conceived. Fram (talk) 17:04, 25 January 2016 (UTC)[reply]

Discussion

  • I don't understand what you are proposing. To my knowledge, authority control (like persondata) is being removed from biographical articles as that function has been superseded by Wikidata. You propose to reverse this? You seem to complain that Wikidata is recording relationships that the en-wiki consensus opposes. You think this forum should reverse that? I agree, Wikidata's links to Find a Grave and the like are problematic. I think Wikidata is the better solution to both the authority control and persondata templates. I don't know to what degree en-wiki can block inputs by Wikidata that this consensus opposes. Perhaps the better solution is to force a change on Wikidata disallowing those links. Chris Troutman (talk) 17:47, 25 January 2016 (UTC)[reply]
    • It can well be that the template is being removed from biographical articles, but as far as I can tell neither of the pages about the template and the authority control mentions this. In fact, Template:Authority control says "this template should be added to all biographies, whether or not there are authority control identifiers in Wikidata already."

      For the sake of this discussion, I don't really care what Wikidata does, apart from the fact that the Findagrave example is quite telling in the difference in standards. What I want to discuss here is which parameters we (enwiki) want to display in our articles, whether fed by Wikidata or added locally is not important. If the solution to what we want is a change at Wikidata, then we will need to discuss our wishes there. But e.g. for MusicBrainz: there are thousands of pages (I think, hard to be sure) where the only authority control displayed through the template is the MusicBrainz ID. We can create a guideline that allows the removal of the template on such pages. We can also look for technical solutions to disable such links on enwiki. And we can discuss it witk wikidata to see what is possible (since they don't only cater to us obviously). Fram (talk) 18:38, 25 January 2016 (UTC)[reply]

      • What's being removed are the template parameters on enwiki, not the template itself, because the values that could be managed are better managed at Wikidata. --Izno (talk) 18:48, 25 January 2016 (UTC)[reply]
      • The MusicBrainz ID links should not be used as references (and any claims of such should be made in the references sections of articles where methinks few if any do appear). They are valuable as authority control but the content at the links is not necessarily notable nor reliable. The only reason there is any content at the link at all is to help people understand what the term means enough to be able to assign it to content (like our articles and those of others which might be useful as references). 50.126.125.240 (talk) 17:51, 1 February 2016 (UTC)[reply]
  • Wikidata and its community don't particularly care which values are displayed here or whether authority control as a template is being used on pages for which it's ill-fit. There may be users in that community who have an opinion, but not the wiki as a whole. --Izno (talk) 18:51, 25 January 2016 (UTC)[reply]
  • Template:Authority Control should be restricted to links which actually do Authority Control; i.e. GLAM institutions and related parties with trained professionals making these judgements. Further, national authorities participating in VIAF should be hidden by default if VIAF is present, because the national authorities very, very, rarely provide anything that VIAF doesn't. Stuartyeates (talk) 20:07, 25 January 2016 (UTC)[reply]
  • Fail to understand proposal "Authority control" is technical jargon that refers to certain library cataloging systems. On Wikipedia it means that and is coming to mean "connecting any Wikipedia article with an external resource by means of an arbitrary identifier taken from a collection of identifiers provided by an established third party". For both medical conditions and drugs there has been discussion about developing the authority control model. See talk pages at {{Infobox medical condition}} and {{Infobox drug}}. See Gout for a live demonstration of an infobox connected live to Wikidata, which is a related concept, and the creation of a "medical authority control" box at the bottom.
    If anyone wants to advance the concept, then I think medicine might be the place where one would find the most interest and feedback. Blue Rasberry (talk) 13:50, 31 January 2016 (UTC)[reply]
  • I agree with some of the other commenters that authority control is not designed for and should not be confused/conflated with reference sources (and as such need not be particularly notable even). The template is traditionally placed at the end of the article, usually within an "External links" section and not a "References" section, for a reason: they are not references. As another commenter pointed out, authority control is more like disambiguation (in fact many such authority controls are called subjects, terms and/or thesauruses, etc.). Like a dictionary term or index key, it is there to group material and could help you find related material on a subject (perhaps even reliable and notable content that could be used as a reference to substantiate an article's content) but it is linked in an article as much to find related material as to claim itself a part of that subject/group and be found too, e.g., the LCCN "sh85135917" authority control item is on the ketchup article as much to help find other information on ketchup as it is to claim the article is also about that topic. Little of what is at the LCCN will help many understand the history of ketchup (unless one is already are familiar with such under a different name perhaps), however, there are works that do talk about the history of ketchup that are linked to that term (try clicking on "LC Online Catalog" from there where you can eventually find things like Pure ketchup : a history of America's national condiment by Andrew F. Smith). Adding the right description (with good use of English words and terms) to an article, can also help an article be more easily cross-referenced but do we really need a policy on what type of words we use in such a description? Well we do have one. English Wikipedia should use English (which is a living language, changes quickly and is hard to define but we usually can differentiate it from other languages). Think of authority controls as subject-based indexing languages, not references. They are ways to group and connect content but not the content themselves. Linking to multiple such languages is useful in much the same way as our interwiki links are. 50.126.125.240 (talk) 17:42, 1 February 2016 (UTC)[reply]
  • This IP understands the situation quite well. The purpose of {{authority control}} is to link an article to the entry for the same subject in various authority files, whether it's the concept of authority control itself, Hilbert spaces, or the Beatles — it provides immediate access to various professionally created databases of information related to the topic (without risk of getting confused with similarly named topics) as well as providing a portal into that topic's place in each database's thesaurus, giving a quick glance at broader, narrower, and related concepts as well as alternate names for the same concept. I don't particularly understand how Wikidata works, so I'm not clear how it fits in, but unless its actions are outright replacing the functionality of {{authority control}} and deprecating it, there's absolutely no reason to get rid of, or seriously restrict the current uses of, this template and the bibliographic integration that it enables. Nyttend (talk) 01:57, 6 February 2016 (UTC)[reply]

Is there any actual reason why userspace drafts must be deleted?

I see all lengthy bureaucratic arguing when we can do this or do that but no one has every given a single good reason why a userspace draft that isn't an attack page should be deleted. Can someone simply and concisely give me a reason why anyone would ever need to delete someone's userspace draft?

Wikipedia is not for the storage of stuff which is not relevant to its purpose. If editors want to keep stuff which is not relevant they should keep it elsewhere. Dmcq (talk) 09:39, 26 January 2016 (UTC)[reply]
  • A good-faith draft of an encyclopedia article, no matter how incomplete, is obviously relevant to Wikipedia's purpose. At no point does a draft article become irrelevant, and at no point does it become harmful simply by nature of being stale. We should not make policy to avoid people's psychological dislike of messiness ("I can't stand the thought of all those unfinished drafts sitting in userspace with no one ever editing them!"). We should make policy to avoid harm, or promote good. What actual pragmatic harm is prevented, or good promoted, by deleting stale userspace drafts? In the case of an editor who has clearly been inactive for many years, such a policy would probably end up being neutral in effect (but still not a net positive compared to just leaving the drafts alone). In the case of an active editor it is inevitable that drama, hurt feelings, administrator involvement, visits to WP:ANI, and inevitably active editors becoming in-active editors would occur in a non-zero number of cases, making the policy a net negative. Thparkth (talk) 11:39, 26 January 2016 (UTC)[reply]
  • There are reasons given at MFD, such as old copies of mainspace, that are too out of date to update; point of view variations that are outside consensus (and abandoned); material not related to an encyclopedia, such as a CV, fantasy sports; hoax like material about non-existent films. I don't think merely being unedited for a long time is a good reason to delete. By deleting we actually clutter up the database more. Graeme Bartlett (talk) 11:51, 26 January 2016 (UTC)[reply]
None of those are **good** reasons. That's why o listed stale drafts cat for deletion.
  • It's also an excellent method of subterfuge to bully individual editors! This is a slippery slope since once this becomes acceptable practice, more, and more, will be included as acceptable deletion. Wikipedia has enough bloated bureaucracy. If editors really want to delete things on this site, a good first step would be less rules not more! --MurderByDeletionism"bang!" 16:33, 26 January 2016 (UTC)[reply]
  • If it's a good faith draft, I see no reason to delete it so long as there's no corresponding article in mainspace. As said above, we don't even save space by deleting articles, since it's a "soft delete" and they remain there. (I doubt we clutter up the database more, it should just be a single bit flag in a "deleted" column, and a 1 takes no more space than a 0.) If, on the other hand, it's an ad, a POV fork, a CV, etc., and the author shows no sign of addressing those issues (or it's blatantly and irreparably inappropriate), we ought to delete it. And of course, we must delete copyvios and attacks on living people immediately upon detection no matter where they may be placed. And I can see the argument that we should at least consider deleting drafts once their subject is already in mainspace; better to improve the live article at that point. But for genuine working drafts not in mainspace? Leave 'em alone. Seraphimblade Talk to me 16:55, 26 January 2016 (UTC)[reply]
  • I think anything that is so poor or devoid of content that it is pointless to have around can be deleted. Stifle (talk) 16:59, 26 January 2016 (UTC)[reply]
  • No, nobody can. Except for the usual reasons why an article might be a candidate for deletion, there are no good reasons to delete a draft just because it's stale. We never know when an idle editor will return, or some other editor will pick up a draft and make a good article out of it. A while back I started to write User:Ivanvector/Drafts are cheap but it needs work. Like Seraphimblade says, there are some reasons why we might delete drafts if they're irredeemable or blatantly violate policies, or if they're redundant to other articles, but those reasons apply equally to articles and are not based on how old the draft is. Ivanvector 🍁 (talk) 17:52, 26 January 2016 (UTC)[reply]
  • On the other hand, wouldn't it make sense to allow editors to delete their own pages in their own userspace? I have built up a few articles in my user space before moving them to main space, and I hate bugging the busy admins to delete the article from my userspace. They have done it for me fairly quickly, but those who work the CSD requests should be paying attention to more urgent needs. There should be a simpler way for me to do this myself. Dcs002 (talk) 18:02, 26 January 2016 (UTC)[reply]
  • I don't think that's technically feasible but author deletions aren't that bad. There's a lot of old drafts that are basically blanked and while one could technically delete them as db-author, that would just be pointless and a waste of time. -- Ricky81682 (talk) 18:16, 26 January 2016 (UTC)[reply]
(edit conflict) I think you know, but you can use {{db-self}} to get them deleted fairly quickly. This works for drafts too if you're the sole contributor. Ivanvector 🍁 (talk) 18:17, 26 January 2016 (UTC)[reply]
I thought it was a technical issue. Dcs002 isn't the first editor to bring that up. -- Ricky81682 (talk) 18:21, 26 January 2016 (UTC)[reply]
Yup, I was talking about the ability to actually delete it myself. I have tagged my userspace articles with that template, but that still makes it someone else's job to go down the CSD list and do the actual deletion. What I have since done is create userspace pages called "sandbox01" through -04 in addition to my regular sandbox. Then I can just blank them and reuse them with the generic name. Dcs002 (talk) 23:50, 26 January 2016 (UTC)[reply]
I don't think that's technically feasible. Besides (WP:BEANS here) it would open up a huge can of worms in that you could then literally move any page into your userspace and delete it. Our page move protections would be immense there which I don't think would be a better system. -- Ricky81682 (talk) 10:38, 27 January 2016 (UTC)[reply]
That makes sense Ricky. That would be a nightmare situation with individuals thinking they are right and don't need to wait for consensus, and the sad fact that there really are a number of people with grudges. It would of course be a type of vandalism, but I think there would be a lot of it in that scenario, with difficult reverts. (Doesn't the page history move with the page in that scenario, leaving the redirect page with an empty history and the user-deleted page taking the history with it?) I've found my own solution by creating multiple sandboxes, so this is a non-problem for me now. Dcs002 (talk) 18:31, 27 January 2016 (UTC)[reply]
  • See Wikipedia:Miscellany for deletion/Draft:Conrad Hughes Hilton III for an example. The content was considered unworthy of articlespace in 2009 and set for deletion. Should it be kept around in userspace anyways? If so, what's to prevent movement again to mainspace, forcing another deletion discussion or the like. There is certain content that is considered never likely to become an article. Saying it should stay in userspace forever (assuming it does) as a potential draft when it would be deleted if it was mainspace creates a lot more work in terms of keeping watching than simply deleting it would. -- Ricky81682 (talk) 18:14, 26 January 2016 (UTC)[reply]
Well sure, but the rationale there is not that it's old, it's that it's content that will never be encyclopedia-worthy. I wish that ThaddeusB had linked to the request to undelete, I'd like to see what the rationale was. I would consider this eligible for WP:G4 deletion. Ivanvector 🍁 (talk) 18:20, 26 January 2016 (UTC)[reply]
Ok, so content that will never be encyclopedia-worthy should be deleted but then how much leeway do we give to possible drafts then? Is it really any different to list drafts for deletion at MFD believing it will never be encyclopedia worthy (see the discussions, that's actually the main issue every time, no one is just idiotically going "well it's been a year, delete")? Age has been a criteria for old drafts for a very, very long time at MFD. -- Ricky81682 (talk) 18:25, 26 January 2016 (UTC)[reply]

Meanwhile Wikipedia:Miscellany for deletion/User:Aakheperure/Khaled Abol Naga draft is another example of an editor's drafts being deleted just because they got "old". 107.72.98.187 (talk) 19:09, 26 January 2016 (UTC)[reply]

elimination of WP:STALE

Since no one can give any reason why a draft should be deleted, I've proposed the entire elimination of WP:STALEDRAFT at WT:UP. 166.171.121.147 (talk) 19:09, 27 January 2016 (UTC)[reply]

Where have you proposed it? All the best: Rich Farmbrough, 13:42, 2 February 2016 (UTC).[reply]
At WT:UP, specifically at WT:User pages#Remove STALEDRAFT where the proposal was quickly rejected. Johnuniq (talk) 01:22, 3 February 2016 (UTC)[reply]

Conflict of Interest

The existing policy is: Wikipedia:Conflict_of_interest

It seems that you have a Conflict of Interest system that does not work. In any organisation with integrity, a Conflict of Interest has a mechanism to be investigated and resolved. I am discovering that Wikipedia has no practical way of doing this. I am being told (perhaps incorrectly) that provided you do not disclose your Conflict of Interest within Wikipedia, then you can do what you want. If you establish yourself with other users and understand the rules, then you are effectively above suspicion. So a person could be using a range of social media, perhaps even promoting themselves as Wikipedia PR specialists, and there is nothing that can be done to stop them (or their team) to full-time edit content, promote clients or their organisations. I have seen some indication that the people who are running the Conflict of Interest page, may be full-time PR professionals. Your Conflict of Interest system should not be defeatable by allying with other conflicted editors other means.

Here are the recommendations:

  1. There should be a clear reporting procedure for Conflict of Interest
  2. The people with authority and training to discuss Conflict of Interest cases should be identifiable by editors.
  3. Conflict of Interest policy must align with best practices, and cannot be watered down by PR companies.
  4. Evidence for a conflict of Interest from outside wikipedia should be allowable, provided it is not public. Surely there is a way of blocking a page from all users except for the parties involved.
  5. Conflict of Interest and other serious violations claims are not, in themselves, personal attacks. It should be expected that the suspicion of a Conflict of Interest is going to be connected with reasonable complaints about editing.
  6. Conflict of Interest applies to the past and the present. An editor under contract to do work, their edits exist and they are not free because the contractual relationship ended. So the sanction must be to remove the edits generated by the contract and not allow them to be restored. Otherwise, they will return after a few months.
  7. Conflict of Interest must extend to clearly to political attacks and commercial attacks.
  8. There should be different severity levels for Conflict of Interest. A president of a small community group should not face the same level of scrutiny as the PR team of a presidential Super-Pac.
  9. The sanctions for Conflict of Interest must be to ban users from editing all pages. The person cannot go ahead with other contracts.
  10. The benefit of declaring a Conflict of Interest must be obvious advantageous and provide protection.

Travelmite (talk) 08:24, 29 January 2016 (UTC) (changed by Travelmite in this dif, fixed by Jytdog in this dif))[reply]

The first problem is to identify conflict of interest edits. This is not easy, unless the cases are very blatant. This is the more tricky since we allow anonymous editors on Wikipedia and allow (and even encourage) editors to use pseudonyms we cannot take action before the behaviour gives prove of conflict of interest.
Persistent Conflict of Interest editing can be, and are considered as disruptive editing and can (and has led) to blocking the involved editor (and evidence from outside Wikipedia is often used to make the case); and the included material is usually removed, regardless whether stuff was written under contract, under personal interest or otherwise. Wikipedia just does not allow sentences to be removed permanently and changing that would touch the fabric of the encyclopedia.
These procedures are not perfect, but the statements above give little practical advice how to get to better procedures.
E.g. how can we find authorities and training? Whose best practices (and where do we find those)?
Your other suggesitons tend to be followed already (e.g. while a declared CoI may lead to removal of material, blocking editors entirely is rare - because the editor was open; while this happens frequently for hidden CoI's.).
So before we continue this. Could you provide a practical way in which a community that prides itself with the slogan that everyone can edit; and which is based on anonymous volunteers; to make your suggestions work, without changing these core values? Arnoutf (talk) 16:43, 29 January 2016 (UTC)[reply]
  • The first problem is to identify conflict of interest edits. Actually this is really easy because no one is free of COI. So every editor here has a COI. Not one individual editor here is bias free including myself. Which is why I find all this stone throwing pointless bullying a complete waste of time.
Or . . . more accurately, it has become a Wikipedia sanctioned witch hunt! --MurderByDeletionism"bang!" 20:48, 29 January 2016 (UTC)[reply]
      • So far I've seen just about every editor who gets stuck with that COI tag on them banned. It really is a death sentence here on Wikipedia.
So . . . can someone show me a COI editor that hasn't been harassed or bullied? One will do, however, more would be preferred, especially if they can speak for themselves. Or . . . do they in fact not exist??? Because, if so, then this is a huge, problem. --MurderByDeletionism"bang!" 06:15, 30 January 2016 (UTC)[reply]
People being paid to ruin Wikipedia articles for the financial gain of other entities have more resources to continue to do so against the purely volunteer editors who do so solely for the benefit of having a quality, neutrally written source for the world to use. That is, as long as people are being paid to push a particular, and decidedly non-neutral, point of view in support of the entities paying them will always win against people who are just here for the love of it, unless we have specific policies in place empowering the unpaid volunteers to refuse to admit the paid liars to the club merely for being paid liars. Unless we do so, the paid liars have the resources to simply overtake Wikipedia by brute force, so long as we take the false notion that anything anyone cares to write is equally valuable, without regard for principles such as adherence to neutrality and verifiability. --Jayron32 07:02, 30 January 2016 (UTC)[reply]
  • People being paid to ruin Wikipedia Wait? What? First off, I do not believe any COI editor comes to Wikipedia hoping to ruin it. That would also effectively ruin their source of income. Second, I believe most paid Wikipedia editors are only doing it to put food on the table. I have a huge luxury here, I can walk away from all this and still maintain a roof over my head. I would never call the level of harassment I see inflicted upon COI editors as winning. In fact, what I do ascertain from your description is a power hungry, narcissistic, sense of entitlement. My point is that any editor, paid or not, are of equal value to Wikipedia as long as they both ascribe to the terms of neutrality and verifiability. But Wikipedia seems determined to put some proverbial star on certain editors.
fyi - The issue most of Wikipedia appears to ignore is the COI with Google and Jimbo. They're ballin' due to Wikipedia! --MurderByDeletionism"bang!" 00:00, 31 January 2016 (UTC)[reply]
  • "I have seen some indication that the people who are running the Conflict of Interest page, may be full-time PR professionals." That's quite an accusation. Please provide evidence or take it back as soon as your current block is expired. Fail to do so and I will block you again. For the information of the other editors here, the above post seems to be fall-out from this post to the COIN noticeboard, where this user accused another editor of having a COI without ever providing any evidence. --Randykitty (talk) 09:57, 30 January 2016 (UTC)[reply]
Perhaps, slow down? The COIN board is by its nature a place with those with COI (and others) are going to post, it seems that is the context of the 'running the board' comment. But what that comment does not take into account is basically no one runs anything around here, and that seems to be the realization of the other comments, ie., we only have limited ability to deal with COI, as we have limited ability to deal with most things, and our only fall back is the good faith of those involved. I have noticed, over and over again, that this situation of uncertainty is often quite stressful to new users, and even experienced users. If there is any solace to be had, here, philosophically, I might recommend reading one of the first things I read on Wikipedia, negative capability. Alanscottwalker (talk) 14:33, 30 January 2016 (UTC)[reply]
No accusation was intended. As requested, the wording has been removed with my full-agreement. I should have made clear that I only intended to mean it was theoretical possibility. I apologise and can explain. In my opinion, this serious risk comes first from several news articles -- well resourced PR firms were identified being paid to edit Wikipedia articles. There are weaknesses with the COI pages. I agree, most crucial to this view was the severe reaction to my complaint, despite following (or trying to follow) the guidelines. This includes (and I mention it to help understand the connection to this policy proposal):
  1. being told I must publish "evidence" before I had finished collecting it or assessing it
  2. having unknown ordinary editors contact me, explaining some points, but also issuing what I felt were inexplicable directions
  3. being directed to steer away from COI to just NPOV
  4. no answers to questions about process or how to protect the other user's privacy
  5. being directed to policies that were, at best, obscurely connected to the matter at hand
  6. being rushed, and at the same time being told to prepare carefully
  7. having the thread summarily closed
Again, may I make clear that various possibilities crossed my mind. Reasonable risks, some of which are relevant to designing systems.
I hope the admin understands that not presenting the "evidence" immediately was the right decision. I am wary of public publication, even if I am only linking Wikipedia pages. Every person deserves fairness and protection from overreaction. Without making an accusation, voluntarily COI disclosures are better than punitive action. What happens after evidence is presented? That is so unclear. At the moment, it's just unconnected words on system. Let's be aware there is a real world out there too - jobs and reputations. We should be seeking positive outcomes. Travelmite (talk) 15:59, 30 January 2016 (UTC)[reply]
I am not going to engage with you here Travelmite except to say two things. First, you say that your now-struck statement was not an accusation; that is not credible - the statement was a direct claim of corruption and plainly stated, and was clearly directed at me. Second - You don't understand how we think about COI in Wikipedia, you don't understand WP:HARASSMENT, and you don't understand how the community navigates the tension between the value, very deeply held by the community, on privacy, and the not-as-deeply-held value of protecting the integrity of WP. Yet you are full of judgments and accusations. As you have been advised by others many times, I suggest you stop making accusations and trying to change things, and instead try to learn. I would be willing to re-engage with you on your Talk page, whenever you like. Jytdog (talk) 16:39, 30 January 2016 (UTC)[reply]
I wrote a full apology on my talk page, regarding the struck out section. I hope that it's accepted. Irrespective of my faults, I absolutely assure you that nothing you have done was suspicious of anything resembling corruption. Whatever our disagreements or misunderstandings, it seems to me you are genuinely interested in doing the right thing in a less than workable system, which maybe you were warning me to stay away from. If you see my point 3, it says "PR companies" plural. I do make a number of criticisms of the whole COI system, it occurred to me that maybe (some level of possible) a PR company had an idea to somehow make their activities easier by making COI complaints harder. I want to make clear that this is only a theoretical possibility. Travelmite (talk) 19:07, 30 January 2016 (UTC)[reply]
You wrote an empty apology on your Talk page, denying what you have actually done. But I don't care about that - I don't need an apology from you. What is most important is that you get properly oriented to how Wikipedia works. You do not understand Wikipedia nor its COI management approach well enough to criticize it. There are so many things wrong with what you have done, including trying to create drama here at the Village Pump, and the things you are still writing are incorrect or are based on incorrect assumptions. Like I said, I would be happy to try to teach you, on your Talk page. Jytdog (talk) 19:33, 30 January 2016 (UTC)[reply]
Please try to discuss the content. I am not intending you to see these as personal criticisms, but system criticisms. This is what I experienced as a first-time trying to report something. Why couldn't it happen to the next person too? Have a look at what is have written in the recommendations? Travelmite (talk) 16:03, 1 February 2016 (UTC)[reply]
I see no way to police conflicts of interest, and in some cases it may not be a good idea, since sometimes only those directly involved in a topic are motivated to update Wikipedia. As someone who hangs out at AfC, the main COI problem that I see is that it pays off. If it didn't, then we wouldn't have a problem. In particular, the use of WP to gain SEO for companies and certain individuals makes COI inevitable and the results highly rewarding. I think we need to tighten up some of our policies regarding CORP and BLP so that it's less easy to exploit WP for gain. LaMona (talk) 21:49, 30 January 2016 (UTC)[reply]
The obvious cases are policed now, and these obvious cases come up because the users just naively think it's a reasonable thing to put their company or organisation online here. Part of the solution above is to make it less of a big deal to have a COI. Then editors can declare their COI, and be mostly treated the same as everyone else. They would be doing the right thing voluntarily. If that happened then, any tricker editors trying to beat the system would be easier to spot. Travelmite (talk) 16:03, 1 February 2016 (UTC)[reply]
  • I find it highly amusing that Wikipedia has determined that being paid must mean that those editors are "bought and paid" for. Yet, at the same time, Wikipedia will only use RS that someone was paid to write. Wikipedia refuses to use individual blogs, blogs that were written by unpaid editors. Wikipedia admires and strives to be just like Britannica Encyclopedia, an encyclopedia written by paid editors. That's some ironic set-up right there!
But here's the best part, all of Wikipedia got played by Jimbo, and now it's Google's turn. Well, done! --MurderByDeletionism"bang!" 19:10, 31 January 2016 (UTC)[reply]
Sources with a reputation for reliability and editorial control, as opposed to randos who claim to know The Truth. You can have one or the other. Not both. --Jayron32 23:58, 2 February 2016 (UTC)[reply]
  • All of the sources that Wikipedia believes are reliable are created by individuals who are paid. Wikipedia won't use a single source that was written by an unpaid editor. That's what's called an oxymoron. Also, Wikipedia has nothing to do with "The Truth," only about verifiability! --MurderByDeletionism"bang!" 06:56, 3 February 2016 (UTC)[reply]
  • Wikipedia doesn't delve into the employment status of the people who write reliable sources. Wikipedia does not want people to edit whereby they have a financial motivation to violate Wikipedia policies in order to use Wikipedia's popularity to promote untrue or inaccurate, but flattering, writing about the people or organizations paying them. I'm not sure why you refuse to acknowledge that people have motivations other than "to build Wikipedia", and that we don't want those people using the established popularity of Wikipedia has a means of promoting themselves through writing that is in direct contravention of the very principles that made Wikipedia itself popular as a source of information, like NPOV. That's the issue. --Jayron32 11:48, 3 February 2016 (UTC)[reply]
  • Wikipedia instead delves into the employment status of their own editors. See how this isn't any better?!
Editors are motivated by all kinds of things, having a financial motivation does not mean that an editor will violate Wikipedia's policies. Or, are you implying that all financial motivations are suspect? That editors should mistrust everything, ever done, that anyone got any financial reimbursement? Because then Wikipedia should distrust the sources it uses.
Also, why isn't Wikipedia more suspect about Google? They have the biggest financial motivation here. Or, is it because Google is the only reason Wikipedia remains a top web site? I've got to wonder, "Would Wikipedia be as popular as it is now without the of Google?" --MurderByDeletionism"bang!" 00:56, 4 February 2016 (UTC)[reply]
There is not going to be one solution that fits everything. It seems you're both making interesting philosophical points that are not in major disagreement. Thanks for your points of view, but if you could be a bit specific and maybe have a comment or two on what was recommended. Travelmite (talk) 18:20, 3 February 2016 (UTC)[reply]

Should raster graphic be maintained when a vector graphic exists?

Is there a policy regarding what should be done with a raster graphic when it is no longer used on any page because a vector graphic had been made to replace it? Is the raster graphic saved for posterity and for future use even when the vector graphic is the superior option? Evan.oltmanns (talk) 13:33, 2 February 2016 (UTC)[reply]

Is the file housed here at Wikipedia or is it over at Wikimedia Commons? Because each site has it's own policies for image hosting, though images in use at Wikipedia may be housed at either location. WP:CSD#F1 indicates that lower-quality redundant images at Wikipedia may be deleted through the speedy deletion process. There is also the Wikipedia:Files for discussion process where deletion of such images can be discussed. I have no idea what Commons policy on this is; it may be different. --Jayron32 16:34, 2 February 2016 (UTC)[reply]
It also depends on the licensing (a policy concern). Regarding deletion outcomes on en.wp and commons, high quality rasters are sometimes kept because they might be useful/used internally for creating other derivatives, or because they've been around a long time and are popular at off-wiki sites (we're not just here for ourselves:), or because the layout/color/etc choices are slightly different that make it fit a different context. That is, if it's useful but not currently used, that might suffice to keep it. If you have a specific example in mind, let us know and maybe someone can give some informal feedback rather than firing up a formal deletion-discussion process. DMacks (talk) 13:57, 3 February 2016 (UTC)[reply]
@DMacks: The graphics in question are File:Navy Cross ribbon.svg and File:NavCrossRib.gif (I nominated for deletion). I am starting a project to improve such graphics and it seems that there will be many cases of this as I work my way through the list. Evan.oltmanns (talk) 14:38, 3 February 2016 (UTC)[reply]
For those playing along at home, at least this example is on commons, so I'll answer wearing my "commons" hat... A small gif that has been replaced by a public-domain svg is a pretty clear-cut "delete" on commons (fails commons:COM:SCOPE, the reasons I mentioned above). From a process perspective, might be easier to replace a bunch of them and then do a bulk DR rather than separate DR for each one. That's a pretty common approach for some other sets of icon/logo-like files, leading to deletion without much ado, lately. DMacks (talk) 21:43, 3 February 2016 (UTC)[reply]
Forgot to mention: "thanks for doing this push for upgraded quality!" DMacks (talk) 21:44, 3 February 2016 (UTC)[reply]
WP:CSD#F1 indicates that lower-quality redundant images at Wikipedia may be deleted through the speedy deletion process.
That criterion "applies to unused duplicates or lower-quality/resolution copies of another Wikipedia file having the same file format" (emphasis added). It never applies to the type of situation cited (involving two different file formats).
CSD F5 applies when a non-free vector graphic replaces all transclusions of a non-free raster graphic, leaving the latter orphaned for more than seven days. In that case, however, the vector/raster distinction isn't directly relevant. —David Levy 23:01, 3 February 2016 (UTC)[reply]
If the raster image is at Commons and has one of the usual licenses, it doesn't make sense to delete it because a vector version is also there. Each of the two has its own strengths and appropriate uses beyond Wikipedia.—Anne Delong (talk) 00:22, 4 February 2016 (UTC)[reply]
Feel free to indicate your use-case or other "keep" rationale at the discussion on commons for the file mentioned (here we are only having a metadiscussion that has no impact on the actual COM:DR process). DMacks (talk) 02:17, 4 February 2016 (UTC)[reply]
What can be said about the fact that selecting a resolution for a SVG actually renders it as a PNG? For those who might not know what I'm saying, if you look at the SVG page on commons and select one of the resolutions, you are presented with a PNG version instead of just a "magnified" vector graphic. Evan.oltmanns (talk) 03:41, 4 February 2016 (UTC)[reply]

Page view statistics not working

One of the most popular features for me on Wikipedia is the tab called "page view statistics" in which one can, quickly and easily, view the number of page views for an article during its history. This feature disappeared about 2 weeks ago and I see some discussion of a new system. Hey, keep it simple for those of us who are computer illiterates, keep it accessible -- but keep it! It's important. And we like it. The way it is. Or was. Smallchief (talk 23:50, 2 February 2016 (UTC)[reply]

This has already been talked about in many other places. But I guess here is also good. The feature was maintained by Henrik who (seemingly) left Wikipedia. As part of the m:2015 Community Wishlist Survey the WMF is going to take over page view statistics. They already have a demo set up, it is working, and up-to-date. It can also be used to compare different article views with each other. See https://analytics.wmflabs.org/demo/pageview-api/ for the demo. --Majora (talk) 23:55, 2 February 2016 (UTC)[reply]
I looked at the demo. It's very slow and cumbersome -- and only accessible with research and effort. Smallchief (talk 00:07, 3 February 2016 (UTC)[reply]
Also, WP:VPT may be a better place for this discussion. This is a technical, rather than policy, issue. --Jayron32 23:56, 2 February 2016 (UTC)[reply]
What I know about policy and technical subjects can be put in a thimble, but I liked the page view feature where it could easily be found and required a single click. I'll check out WP:VPT. Thanks. Smallchief (talk 00:07, 3 February 2016 (UTC)[reply]

How to cite or credit a German Wikipedia article

I have run into a problem regarding the Bing Cave

In writing a short article on the Bing Cave i used ref sources from the cave's official site. These were written in German, which i translated and rewrote in my own wording in English.

I then found that there is a very long German Wikipedia (.de) page on the Binghöhle (Bing Cave) which is, to put it frankly, tediously long. It is of more interest to Germans than to Americans, let us just say. So, i translated only a few portions from a number of different paragraphs on the German Wikipedia page and stitched them together to make three new, concise, snappy American-English paragraphs.

I cited the German Wikipedia page as a reference for what i added.

I did NOT use a standard translation template because i did not actually translate the meters and meters of text on the German page. The article is great for Germans, but i do not have time -- nor do i think the notability factor is there -- for such an extensive article to appear in English.

As soon as i uploaded my additions, the refs were removed by an editor named Gilliam, who said that one cannot cite a Wikipedia page as a reference for another Wikipedia page.

I understand that.

Neither Gilliam nor i, however, know how to properly credit the translation. I reinserted the refs, with Gilliam's cooperative agreement, so that a more senior editor would know how to easily find the three paragraphs in question.

In short: i cannot use a "translated page" template because i did not (nor do i think we should) translate the entire page.

So how do i cite the fact that it is a translation of part of the page?

Please help. It is 3:00 AM here and i do not have time to do much more on the page. I am going to bed now and hope to receive a reply -- or better yet, a fix -- tomorrow.

Thank you.

cat yronwode, not logged in 75.101.104.17 (talk) 11:03, 3 February 2016 (UTC)[reply]

This is more-or-less a case of copying within Wikipedia; attribution to the original translation should be given in the page history of the article. However, you still need to provide verifiable information, relying on reliable sources, inline to the text which you are showing is verifiable. Most German pages do not provide inline citations. --Izno (talk) 12:22, 3 February 2016 (UTC)[reply]
As a side note, reliable sources are not required to be in English. If multiple substantially equivalent sources exist in multiple languages, at least one of which is in English, we prefer that you cite the English one, but if there are only sources available in other languages, it is quite OK to cite those non-English sources. In other words, if only German sources exist, then just cite the German sources (so long as they are reliable, per WP:RS. Another user edited source, such as another Wikipedia, of course, wouldn't qualify...) --Jayron32 13:46, 3 February 2016 (UTC)[reply]
I have done some miscellaneous tidying; the content seems good but I haven't checked the references. --Izno (talk) 15:12, 3 February 2016 (UTC)[reply]
Thank you, Jayron and Izno. I have left the page as-is except that, to be more clear, i did bring over the German refrence section which is not in our current in-line ref format. I used the German "Literature" material because the only English-language source available to me is the autobiographical memoir written by Ignaz Bing, who discovered the cave and wrote extensively about it. The memoir was only translated into English in 2013, and may be the longest piece of writing about the cave in English. I have cited it, of course, by its English title, "Tales From My Life: Memoirs of a Merchant and Cave Explorer in Germany 1840-1918" ISBN 978-0956337016. Thank you for your help. 75.101.104.17 (talk) 19:05, 4 February 2016 (UTC)[reply]

Should we move full-length movies from article space to Commons?

See also: User talk:Jimbo Wales § Debbie Does Dallas

Something that's occurred to me during discussions at Talk:Debbie Does Dallas (because of an ANI report): Why are we hosting full-length public domain movies in some articles when we have Wikimedia Commons for that and when WP:NOTREPOSITORY is a policy? It is, in effect, akin to hosting a whole book. I can start to see the argument "but the book takes up more article space than a windowed movie," but I'm pretty sure we have the capacity to do a windowed streaming book (akin to archive.org or plenty of other sites, if perhaps after a update). It's really not a technical issue (the code is out there), but a matter of focus. You don't need the whole movie to identify the movie, just a description, and if possible select stills or hopefully the trailer.

I'm not so much proposing that any new policy, but seeing what the consensus is on whether WP:NOTREPOSITORY means that we should replace full-length films from articles with a link to their location on Wikimedia Commons, and if not why. Such an arrangement could be useful for users with precarious bandwidth situations, like touch screen phones with limited data plans (no accidentally tapping the movie while scrolling and losing your internet for the rest of the month). Ian.thomson (talk) 16:02, 4 February 2016 (UTC)[reply]

Yes, I meant "showing the videos in the article," without regards to where the file is actually stored. Ian.thomson (talk) 16:41, 4 February 2016 (UTC)[reply]
  • In the general case (regardless of the content of the film as long as it has fallen into the PD or available under proper license terms), this is arguably what should be at Wikisource, as we would do for PD text information. en.wiki would use snippets and can interlink to Wikisource for the film in full. Now, Wikisource would probably have Commons be the one to host the full file, but I don't know if that's appropriate or not; this is almost where we'd want a resource like Archive.org , which prides itself on the dissemination of full, public-domain material, for that. I would say that en.wiki should avoid including full movies (anything more than a few minutes) in articles and instead provide links for full material, though proper use of short clips would be appropriately in scope to support the text. --MASEM (t) 16:14, 4 February 2016 (UTC)[reply]
  • The files are not in article space. The files are on Commons (whether they are embedded in the artciles or not). If a user inadvertently starts the movie playing, they can easily stop it or leave the page. Right Hand Drive (talk) 16:34, 4 February 2016 (UTC)[reply]
Why would movies be exempt from WP:NOTREPOSITORY? Ian.thomson (talk) 16:39, 4 February 2016 (UTC)[reply]
Because there is nothing in that applies here? Perhaps you can explain which part of WP:NOTREPOSITORY is dircetly relevant. Bear in mind that the files are not in article space. Right Hand Drive (talk) 16:46, 4 February 2016 (UTC)[reply]
Wow, you're really good at focusing on stuff you've read into what I said instead of what I actually said. We do not include source documents in other articles, and you've provided no explanation for why movies should be treated any differently than any other source document. Ian.thomson (talk) 16:49, 4 February 2016 (UTC)[reply]
If you could elborate on what part of that policy section applies to the situation at hand, I will consider your points. Right Hand Drive (talk) 16:55, 4 February 2016 (UTC)[reply]
What Ian.thomson is getting at is that, if we took the case of a number of free-license/PD images that are all at Commons all relating to the same topic, it would be a violation of NOTREPOSITORY to stick them all in a gallery on a WP article page. A handful, yes, plus a link to the Commons category to help the reader find more, but we'd not want to be the photo album. In the same manner, judicious use of one or two snippets or frames from a full film would be better than directly inserting the full film clip, though we'd still link the full clip somewhere. --MASEM (t) 16:56, 4 February 2016 (UTC)[reply]
As I have repeatedly explained to Ian.thompson is that there is no difference between embedding a "snippet" and embedding the entire movie. Unless and until the reader chooses to play the movie, all they see is a single frame. And in this case, no one is suggesting that there is a gallery of anything, just a single embedded movie. Right Hand Drive (talk) 17:03, 4 February 2016 (UTC)[reply]
Technically you are correct, there is no difference practically between embedding a snippet and embedding the feature. But we're talking from more presentation and relevance context. Just because one can include the entire movie doesn't mean that helps the reader if our article is discussing a specific scene. Instead, we should embed the clip of that scene so that the reader doesn't have to spend time searching for that scene. We can still provide the link to the full movie in the article's endnotes, but there's little practical use for our readers to embedded an entire movie. Its the same logic with the gallery example. --MASEM (t) 17:16, 4 February 2016 (UTC)[reply]
Yes, if we were talking about a specific case of an article discussing a single scene, it would be helpful to have a clip of that scene rather than the whole film. That is not what we are talking about. In this case, we are talking about an overview article on a movie. It might be useful to clarify whether thsi discussion would also apply to clips or just full movies. Right Hand Drive (talk) 17:24, 4 February 2016 (UTC)[reply]
Including the full movie is still distracting if you aren't speaking to any specific part of it but just including it. We don't for example include all of the text of PD novels on articles about those novels, but do include relative snippets and the link to either Wikisource or Project Guntenburg. Same with audio recordings in the PD. That should be the same here as we are an encyclopedia, not a content repository, but noting other Wikimedia sister sites are meant as content repositories. --MASEM (t) 17:32, 4 February 2016 (UTC)[reply]
Audio: We do include PD audio recordings, and I greatly enjoyed listening to Goldberg Variations and The Well-Tempered Clavier whilst reading about them. I don't think audio is a good comparison.
Distraction: I understand the nuance you're intending (that of an abundance of material, which ends up sidetracking or diverting the attention of the reader), but the ambiguity of the word makes it problematic (a thumbnail for a video could also be considered less distracting than an animated gif, if the thumbnail doesn't contain shocking material).
Repository: A good example is a PDF. It is stored at the Commons repository, but it might be embedded in a Wikipedia article, e.g. United Airlines Flight 175#Calls. We embed material when relevant, with a boundary somewhat based on quantity (which I think is generally related to extensive image galleries, which are a problem for page-layout and section-over-emphasis reasons).
Non-controversial video: For The General (1926 film), and One Week (1920 film), and hundreds of other great articles with Public Domain (long and short) video content, we need a solution that is better than a plain {{Commons}} box. Most readers won't realize that a full film is available behind that link, and will find Wikipedia less useful and less enticing as a result.
Controversial video: I don't have a good suggestion for how to handle these, beyond following Wikipedia:Offensive material and linked policies/guidelines, and improving those as necessary. I fear that the specific article/content used at the start in this thread, is colouring the input, and could end up damaging how we handle non-controversial content. HTH. Quiddity (talk) 20:40, 4 February 2016 (UTC)[reply]
As a note, the UA175 report is not embedded; you have to click to get to the full readable version, with only the front image embedded in the article. Further, that file is stored at Commons. Further, that report is still a link in the EL. So really, there's no issue with repository there. --MASEM (t) 23:10, 4 February 2016 (UTC)[reply]
  • In the same way that still images are helpful to the reader, movies are helpful to the reader. If we have an article on a movie which is in the public domain and available on Commons, it is desireable to embed the movie right in the article. The reader may or may not wish to play the movie, but that choice is left to them. Making the reader go to a different site (Commons) to see the movie is both an unecessary step for the reader but also takes them away from Wikipedia. This is not a god thing. Right Hand Drive (talk) 17:01, 4 February 2016 (UTC)[reply]
Embeded films are a distraction; why would we want to encourage our readers to deviate away from the very pages which we spend so much of our time on? I suggest we stick to encyclopedia stuff and let YouTube deal with the videos. CassiantoTalk 18:14, 4 February 2016 (UTC)[reply]
Being helpful to the reader is not the same as providing encyclopedic coverage. The goal on Wikipedia is to provide encyclopedic coverage via secondary sources. Primary sources—which the film is—are only generally relied on up to the point that encyclopedic coverage depends on them. Obviously if we have an article about a particular work and are in a position to provide free direct access to the work then it is helpful to link to it, and that is precisely what the "external links" section is for. Wikipedia's own guidelines instructs that we should provide the link in the external links section, stating "An article about a book, a musical score, or some other media should link to a site hosting a legally distributed copy of the work". Betty Logan (talk) 20:41, 4 February 2016 (UTC)[reply]
If we have an article about a work of visual art, we almost always include an image in the article, don't we? Are you suggesting that we should abandon this practice, remove the images, and provide links instead? Right Hand Drive (talk) 22:59, 4 February 2016 (UTC)[reply]
It's about how much information you are giving the reader. An entirety of a single work of art is very easy to take in as an embedded image; it's easy to reference in the text to highlight specific areas to the reader to help their understanding. With larger works, like books or films, it's far too much information to throw at the level of the article, though as an EL for those interested, they can view it as needed. We want them to focus on the sections that have received attention by secondary sources and that's best done not by giving them the entire work but the appropriate snippets. --MASEM (t) 23:07, 4 February 2016 (UTC)[reply]
  • I don't see how WP:NOTREPOSITORY compels us to remove useful and directly relevant video files. They are hosted on Commons, they can be added to articles unobtrusively, and they compliment our mission of the distribution of free knowledge. Per Quiddity, we can't hide them behind a Commons link and expect people to know they are there, or expect that merely offering a link is fulfilling our mission. Gamaliel (talk) 21:30, 4 February 2016 (UTC)[reply]
Have you actually seen the link at Debbie_Does_Dallas#External_links? "Full film available at Wikimedia Commons" isn't exactly hiding the link and nobody has suggested we remove that. This is what people are objecting to. Betty Logan (talk) 21:57, 4 February 2016 (UTC)[reply]
I know what people are objecting to, but I don't think we should strip all movies out of the encyclopedia on dubious grounds on the basis of objections in a single article. Develop a consensus for a rule based on WP:ASTONISH for cases like these if you want. Gamaliel (talk) 22:31, 4 February 2016 (UTC)[reply]
A consensus was developed for this particular case at Talk:Debbie_Does_Dallas#Censorship_of_article. Maybe those who wish to challenge the existing consensus should file an RFC or something rather than simply edit-warring? Betty Logan (talk) 23:05, 4 February 2016 (UTC)[reply]
  • I think both the video and link should be posted for the DDD page. The video is fitting not only as source but also how and why it fell into public domain. The link goes to a page that offers more options to view or download for example. This should also apply at similar pages where the video has more than one reason to be posted such as court action and history, again like the DDD story/video. ContentEditman (talk) 22:03, 4 February 2016 (UTC)[reply]
VCX may own the copyright in countries where it is still under copyright and are perfectly within their rights to sue anybody illegally distributing film in those cases, but there is no doubt about its public domain status in the United States since a judge ruled that it was in the public domain. To assert their copyright claim in the US they would surely have to appeal that decision. Betty Logan (talk) 23:05, 4 February 2016 (UTC)[reply]
VCX were certainly still suing people in the US for copyright infringement well over two decades over the 1987 "thrust the film irretrievably into the public domain" ruling. IANAL but this is patently not a clear-cut case. ‑ Iridescent 23:37, 4 February 2016 (UTC)[reply]
In what way is it not clear cut? There is a court ruling that the film is in the US public domain. For the film to not be in the US public domain would require a fresh ruling. That is law 101. If you read VCX's court filing that is linked in the article they are suing people who are torrenting the film precisely because it is a worldwide distribution mechanism i.e. the illegal distribution of the film in territories where the film is under copyright is an integral part of the distribution network. Where it is not clrea-cut is Deep Throat: that film is more than likely in the US public domain too, but as yet there has been no courting ruling to establish it. Betty Logan (talk) 23:53, 4 February 2016 (UTC)[reply]
It's a lower court ruling; in fact, a ruling of the lowest level of courts that could hear the case. It's not actually binding outside of the court district in which it's applied; in this case, Eastern Michigan, or pushing harder, the Sixth Circuit. Sixth Circuit decisions are notorious for being overturned by the US Supreme Court. The Detroit decision isn't binding on the entire US, let alone anywhere else. Risker (talk) 04:43, 5 February 2016 (UTC)[reply]
This is a pretty straightforward case: both Deep Throat and Debbie Does Dallas were released without copyright notices, and both failed to address the problem within five years as required by copyright law. This would usually be enough for us to host the files on Commons. In addition to that though, the 1987 case was brought against VCX by a producer of DDD because they refused to pay him royalties: VCX's defence was that it was in the public domain in the US, and the judge ruled in their favor. This isn't a controversial ruling and I doubt you will find any legal opinion that will come to the conclusion that the film is not in the US public domain. The fact that VCX talks a lot about suing is neither here nor there. Betty Logan (talk) 06:20, 5 February 2016 (UTC)[reply]
  • To take a cleaner example, A Trip to the Moon is in the PD due to age, no question on that. The article uses 2 video clips of versions of that film, primarily to point out differences, and does have plenty of screencaps (all at commons) to help enunciate the encyclopedic nature of the text, and finally it includes a link to the movie at the Internet Archive (though it does look like there's full versions too at Commons). As such, there is no need to include an embedded version of the full film as it does not directly aid in the encyclopedic understanding of the importance of the film and its legacy. (eg I have never read War and Peace but I can read our article on it to have an understanding of why it is such a critical classical work) The link to the full video is a convenience link to help those who want to see it in full find a way to do so. This is an example that we should be following for any type of article about a work that is in the PD/CC-BY, regardless of it being text, audio, or visual. This is the importance of NOTREPOSITORY here. --MASEM (t) 22:58, 4 February 2016 (UTC)[reply]
I think you will find that there are not one but three complete versions of the movie embedded in that article (black and white, colorized, and a remake). If we follow this article as the example, we would embed the full movie in Debbie Does Dallas. Right Hand Drive (talk) 23:17, 4 February 2016 (UTC)[reply]
I was not considering the remake clip, but you are right they are otherwise full versions of the film; the captions suggested they were clips. And knowing that, I would argue that the full versions aren't helping there. The still images as given of the original and recolored (at the same scene otherwise) show the difference that is encyclopedic, and the full movies are more distraction and diffusing the information. --MASEM (t) 23:39, 4 February 2016 (UTC)[reply]
  • NOTREPOSITORY is a truly ridiculous argument for one to make to try and remove a single file. Sorry Ian, but your interpretation would offer carte blanche for someone to remove ANY file they dislike - be it an image, an animated gif, a short audio clip or a full-length movie. All should be treated equally simply as a file, and their merit judged exclusively on encyclopedic value. Even though I think you are well meaning in this case, I must categorically oppose your interpretation of this subsection of the WP:NOT policy. I also take issue with a separate argument made by others stating there is a (local) consensus to use only a link. My read of that debate is that the consensus was to use at least a link. From my POV, embedding the full file would be just as much in compliance as using an EL would be. Now, that being said, the fact that we can embed the entire video is not itself an argument that we should. Given we have the entire source available to us, we can freely use screenshots to convey important aspects of the film that are relevant to the article prose. That is something I would encourage an editor to consider, as the current offering of no images from the film is jarring, given how decidedly unusual that is when we have PD source material to work with. In that vein, if our options are the full video or nothing, I will favour the full video. Resolute 00:19, 5 February 2016 (UTC)[reply]
    • I think this actually is more along my lines of thinking, though I would still justify it under NOTREPOSITORY. With inline media in prose, we don't want just to drop pretty pictures or more information than what helps the reader connect to the topic, even if it is freely usable in the PD. A screenshot may be much more poignant than entire movie in context of the text it is presented with. We should still provide a link, somewhere to the full PD work, but we should be careful of what's put into running prose. --MASEM (t) 00:46, 5 February 2016 (UTC)[reply]
  • Porn films should not be hosted on Wikipedia article space. Wikipedia is not a porn site and should not be hosting porn films. They can stay on Commons if they need to stay somewhere. By the way, this discussion regarding Debbie Does Dallas obviously needs a site-wide RfC, not a non-binding discussion with a misleading thread title hidden away on the Village pump. Please notify me on my talk page when such an RfC is begun. Softlavender (talk) 00:42, 5 February 2016 (UTC)[reply]
  • "Per the Foundation, controversial images should follow the principle of 'least astonishment' " WP:GRATUITOUS. I don't see any reason to limit films or videos or any other media beyond this. Is text really always preferred for an encyclopedia?
I'll note that WP:GRATUITOUS has gone against me in a couple of cases. On postcards, I've inserted a French postcard in the article and people objected. Also at Batting (baseball), the following classic was removed File:Animation of top row of Plate 279, Baseball; batting (4057432207) faster.gif. If those can be removed, I'd think DDD would likely also be removed. Smallbones(smalltalk) 01:19, 5 February 2016 (UTC)[reply]
I hope you can see why people objected in the cases you mention. I also hope that you can see why an article about a pornographic movie is different from an article about batting. Readers looking at an article about a pornographic movie should not be astonished to see pornography. Right Hand Drive (talk) 04:28, 5 February 2016 (UTC)[reply]
In the interests of transparency, Right Hand Drive (talk · contribs) was created on 14 September 2015 and has a total of 31 edits, all concerned with adding the film to the article. ContentEditman (talk · contribs) was created on 4 February 2016 and has a total of 5 edits, all supporting adding the film. Johnuniq (talk) 04:41, 5 February 2016 (UTC)[reply]
Yes and from September 14 until yesterday, there was no issue with the movie being embedded in the article. Incidentally, I'm told that this discussion is not about Debbie Does Dallas, but about a general issue with embedding movies in articles. This discussion has nothing to do with any concerns about the content of that specific movie. Apparently. Right Hand Drive (talk) 05:00, 5 February 2016 (UTC)[reply]
Well, then if we discount the recent SPAs, we don't have much a consensus to host the film or any porn film on WP, even in the non-binding non-public non-RfC threads with misleading titles. Softlavender (talk) 05:20, 5 February 2016 (UTC)[reply]
  • I'm sure a lot of things got mixed up here in an unhealthy way:
    1. First the DDD movie is hosted at Commons no matter how, thus "moving" the full-length movie from article space to Commons (as the title of this discussion section suggests) is utter nonsense. It's only what kind of clickable link is used: one that takes you from the mainspace page to a page on a sister project in order to view the movie, or one that displays a thumbnail (and would take you to another page depending on browser functionality). Basicly it is about whether or not a thumbnail is displayed in mainspace.
    2. Second "without shoving porn in readers' faces" (an argument used in the discussion at Talk:Debbie Does Dallas#Link to full film on Commons) is not helped by the WP:NOTREPOSITORY reasonings that recommend to only show snippets of key scenes, so for instance (from the 7th paragraph of Debbie Does Dallas#Plot) "Lisa offers Tony "anything" and she begins to fellate him, then Tammy joins in, and he ejaculates on Tammy's breasts." would reasonably be such snippet illustrating a key scene. No, WP:NOTREPOSITORY is not the way to go for the "without shoving porn in readers' faces" argument.
    3. In fact the WP:NOTREPOSITORY policy and guidance is quite unrelated to this discussion: in both options the file is hosted at Commons; in both options there is a single link to the file.
In general I'd rather support to have a "thumbnail" link in this instance, like for instance we do the {{listen}} link at the start of the Toccata and Fugue in D minor, BWV 565#Structure section, or the multi-page PDF (containing the entire primary source) as second media file in The Well-Tempered Clavier#Reception.
That being said, I think the Debbie Does Dallas article (the text content of the article) needs some work: for instance, one of the most remarkable "reception" topics of the film is about how it got in the public domain somewhat over a decade after its release: the info on that is rather sparse. --Francis Schonken (talk) 06:54, 5 February 2016 (UTC)[reply]
Bear in mind that this discussion is thoeretically about removing all full length movies from
  • Comment have to agree with Francis Schonken that this whole discussion is very confusing. I already pointed out in the ANI thread before this discussion started that AFAIK no one is suggesting we host it here on en.wikipedia. Amongst other things, there is no reason to when it's on commons. I guess it's possible there may be a porn movie which can't be hosted on commons due to not being public domain in the country of origin but which can be hosted here due to being public domain in the US and then we will have to debate whether to host such movies, but I don't think this is what people are talking about here. And has been pointed out by multiple people even if we do host one here, it's literally impossible with the current software to host a porn movie in article space, it will be hosted in file space. What seems to be most disputed is whether to embed the movie which is hosted at commons in article space. If that's what people care about, it would be good if they are clear that;s what they are opposed to. If people are opposed to even a link to the porn movie on commons then this is another thing and again people should be clear on that. If people feel that way but are fine with linking to it on somewhere besides commons (or conversely don't want any links), they should be clear on that as well. Nil Einne (talk) 07:17, 5 February 2016 (UTC)[reply]
I think some of the terminology is getting mixed up. Certainly the debate at DDD is strictly about whether the film is embedded in the article or just linked to. Either way the film is still hosted at Commons, and people are confusing embedding with hosting. Since nobody is suggesting we physically host the file over here I think we can assume that people mean "embed" when they write "host". Betty Logan (talk) 10:22, 5 February 2016 (UTC)[reply]
Yes, it should be pretty obvious that it doesn't make a damn bit of difference where the actual file is located, just where it displays. Ian.thomson (talk) 10:32, 5 February 2016 (UTC)[reply]
  • This discussion is a hopeless jumble of misunderstandings of policy and technical details. It has predictably become a proxy war over the Debbe Does Dallas movie. Can I suggest that it be closed and the question reformulated sensibly (and without regard to pornographic movies)? Right Hand Drive (talk) 15:26, 5 February 2016 (UTC)[reply]
  • I agree this is nonsense. Having a picture display in an article doesn't mean the picture has been copied to Wikipedia! I agree we should close this -- and suggest that readers make their opinions about censorship heard at the Talk:Debbie Does Dallas. Wnt (talk) 19:24, 5 February 2016 (UTC)[reply]
    • I have no comment specifically on the censorship here (though I have my own ideas on how that should be handled in the specific case) but there is a separate idea that for any PD work of appreciable length (more than a minute or so) that is hosted on either en.wiki or commons, do we embed the work fully in the article, or do we embed relevant clips/sections and provide links to the full work as ELs? There are both technical and content reasons to consider here, separate from what the actual nature of the work is. That's a policy level discussion that should be had. --MASEM (t) 20:17, 5 February 2016 (UTC)[reply]
@Masem: I don't see why or how to split such works into featured clips. I mean, to present one part as more important than the rest is in spirit a sort of original research; the dubious advantage it gives of flipping the reader directly to the good part is more than counteracted by the inconvenience of getting the rest. In this case, of course, featuring a clip of just "the good parts" would be, IMHO, abusing the censorship lobby a bit more than they properly deserve. Even if we want to direct readers to the good parts, it would better be done by text in the caption saying where they are in hours/minutes. If there is one single image (or a few) that has attracted sourced commentary, then that image of course can be included as a separate file in the article, independent of the video. Wnt (talk) 02:19, 6 February 2016 (UTC)[reply]
It's not OR to use clips or screenshots that are directly the subject of discussion in the article itself. For example, I gave the example of "A Voyager to the Moon" , and here, it would make sense to use a representative shot of the infamous "face on the moon", and shots comparing the original black-and-white to the colorized version, all the subject of discussion, but you dont need the entire film. If there is no specific discussion of any scene or the like, that's a good sign that we actually don't need to show any clips from the movie in the article, though screenshots (free) to help make the article look visually interesting is useful. It's free media so we absolutely don't have to be as careful as NFCC would require, but the same thought and considerations should be made before adding video/audio if it is really helping. We have to remember that the reader does not always have access to video or audio players, but image viewers are near-enough universal to be reliable. --MASEM (t) 02:30, 6 February 2016 (UTC)[reply]
@Masem: I looked up this example, and believe this edit to be beneficial. Readers of an article about an old movie probably want to know, early and definitively, that they can watch it - it makes their reading of the commentary more immediate, more likely for them to engage with it. However, there is a technical problem I would like to see an answer to: is there a way to set the display for the embedding I just did, so that when you look at it on the page before pressing Play Media, you are looking at the title page that was up before I made this edit? That way there would really be nothing at all lost by making this edit. Wnt (talk) 11:58, 6 February 2016 (UTC)[reply]
I don't know with how the MediaWiki software works if this is possible (I know other programs can set the key frame to display in lieu of video). This would help; I would also think it should help to include the time length of the prose-embedded movie file as that would also alert a reader if this is a short clip or a long feature. --MASEM (t) 14:59, 6 February 2016 (UTC)[reply]
  • Comment I'm glad to see so much discussion of this difficult issue—I've added full-length videos to articles in the past, but have never felt sure such additions were really relevant to what Wikipedia is trying to do. In the case of old silent films like A Trip to the Moon, I think there are a couple other issues to consider as well:
  • Almost every silent film ever made was intended to be experienced with a musical score. Versions of such films on Wikipedia Commons are necessarily silent (for lack of a public-domain recording of a score for the film), so to call any of them "the complete film" is a bit deceptive: it's not the full experience which the filmmaker intended, and which you can get from any reputable home-video release of the film.
  • Preparing films, especially old films, for home-video releases is a complicated process that often involves all of the following steps: working with numerous public and private collections to determine what fragments/versions of the film survive; combining incomplete prints to reconstruct a complete version, often simply "as close to complete as possible"; restoring tints, tones, and/or hand-coloring missing from the prints in question; removing scratches and other film damage, using chemicals or digital tools or both; recreating title cards missing from the film; researching how fast the film was meant to be projected (i.e. how many frames per second); and compiling all this work into a DVD- or Blu-Ray-ready format. Much of this might be written off as sweat of the brow work, but can we really just rip a painstaking restoration from a DVD and write it off as public-domain? I honestly don't know. I wish there were a clearer policy at Commons about this.
Here's hoping the community can come to a good policy-based consensus about handling these kinds of video files.--Lemuellio (talk) 12:48, 6 February 2016 (UTC)[reply]
  • I guess so, yeah. Just answering the question in the section title ("Should we move full-length movies from article space to Commons?"). Here're my reasoning. (First of all, I'm assuming that moving a movie from the article to Commons also entails moving its position in the article from somewhere within the body of the article to the External Links section; that matters, to me, more than where the actual bits of the actual file are hosted).
  1. Doesn't WP:ARTICLESIZE come into play here? Anything that's in the middle of the article is part of the article. We don't really have a tag for "Here's a section of this article that's actually optional, you don't need go through it to fully understand the subject to the level appropriate for an encyclopedia article." We don't hide galleries of images or text using the {{hidden begin}} template and so forth, I don't think. So if it's in the body of the artgicle the assumption is "It's part of the article, you need to read/view/listen to it unless you'r OK with a partial article", whereas External Links implies "Here's some extra stuff, if you want to read/view/listen it for extra enrichment, go ahead". But making an encyclopedia article that takes 2 hours or whatever to get through -- that's a bit much, n'est-ce pas? I don't think WP:ARTICLESIZE exactly addressed this, but I think WP:ARTICLESIZE would start puking frogs if we told it we were making articles that took two hours to get through.
  2. But my real reason for opposing it is because I don't want us to host pornographic movies. Sorry, but porno trolls is why we can't have nice things. Maybe it would be OK have movies in articles, I dunno. But if we have movies in articles, we're going to have to have pornographic movies -- and I'm sure it can get way way way worse than Debbie Does Dallas -- and I don't think that's really a good idea. In an ideal world, editors of maturity and intelligence would be able to discriminate between appropriate and inappropriate media for a general-purpose encyclopedia used by the general public to host. But, as I'm sure everyone knows, trolls out for LULZ (or to embarrass and damage the encyclopedia) and their useful idiot friends hold the whip hand on that matter. So, no movies please, and if that means you can't include a useful and appropriate movie in your article, take it up with the trolls and their enablers, not me. Herostratus (talk) 16:50, 6 February 2016 (UTC)[reply]
Only commenting on your ARTICLESIZE point: embedded media (audio or video clips) do not contribute or count towards page size beyond the single image used to indicate that it is an embedded work (only until you click it does the actual media "load" and contribute to the number of bytes the reader uses). And to that end, the only advice starts to become to avoid using too many images or embedded media to overwhelm the bandwidth to the reader. As to the time to take to view the work if one is understand the article, that's a very valid point though not something ARTICLESIZE really gets into much; it supports the notion to use the most relevant clips rather than full length films to augment the text, with links to the full works if the reader needs to see it in full. It is the same concept why articles on classic works of literature don't require the reader to read the full work to understand the article. --MASEM (t) 17:25, 6 February 2016 (UTC)[reply]
Readers are not required to play embedded movies or video clips. Nor are they required to watch or listen to the entire thing. They can stop the file playing just by clicking on it again. The suggestion that all readers are obligated to play media files is ridiculous. Readers can decide for themselves whether or not to play media files. I suspect that most readers do not even read all of the text in any given article. Right Hand Drive (talk) 22:40, 6 February 2016 (UTC)[reply]
That second point might be the worst argument in favour of censorship that I have ever seen made on this project. Resolute 22:49, 6 February 2016 (UTC)[reply]
I think we're hearing a lot from people who think that really, providing information is a bad thing most of the time. Giving people access to public domain movies, whatever their provenance, abuses the sweat of the brow put in by commercial movie-makers, because the public needs to have firmly in their mind that video is inherently something they have to pay for... no matter what. Court decisions are inherently made for the benefit of owners, not the public. And better to defeat a thousand attempts to access content than to allow one that might cause someone to criticize, because after all, providing access to something someone thinks is bad is infinitely bad, but providing information people merely want is inherently worthless. A person, in general, needs to be redefined away from some religious woo-woo conception of free will and such, and considered rather as a substandard predecessor to AI that really only needs specific training for its particular job designation, so long as it has it, then be recycled because of course it can never be repaired or renovated. I am just tired, so tired, of people who only see in content the opportunity for control. Wnt (talk) 23:58, 6 February 2016 (UTC)[reply]

How many articles would be affected by a change in practice?

I think this discussion is a confused mess and a waste of everyone's time, but can anyone tell me how many articles have embedded movies? It would be good to have some idea of how many articles would be affected by a change to the normal practice of embedding public domain movies. Right Hand Drive (talk) 22:50, 6 February 2016 (UTC)[reply]

Let's move this to an RfC

See Wikipedia talk:What Wikipedia is not#RfC: amendment to WP:NOTREPOSITORY. Make your !vote there and a (hopefully fairly succinct and cogent) edit in the Discussion section. That way at least where we stand with WP:NOTREPOSITORY, which we've been arguing of the interpretation of and which is important to this issue, can be decided one way or the other.Herostratus (talk) 15:01, 7 February 2016 (UTC)[reply]

Other idea, let's promote Wikipedia:Wikipedia is a tertiary source to guideline

When we're tired of hearing what Wikipedia "is not", here's a stable formulation of what Wikipedia "is". I'd not tamper with the WP:NOT policy to insert things in it that are in fact covered better by the WP:NOR policy ("Do not base an entire article on primary sources, and be cautious about basing large passages on them") — but what might be beneficial is a guideline explaining the connection between WP:NOTREPOSITORY and WP:NOR's WP:PRIMARY. --Francis Schonken (talk) 08:13, 8 February 2016 (UTC)[reply]

Guideline duplication (the potential for conflict)

See ongoing discussion at Wikipedia talk:Article titles#Question about various "naming conventions" pages.

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

I would like to raise the following guideline pages for discussion and community consensus:

What really concerns me is that these two guidelines cover essentially the same ground. Having two guidelines address the same issues is never a good idea... the potential for conflict is high. So... what should we do? Merge the NC page with its MOS counterpart? Depreciate one in favor of the other (if so, which one)? Something else? Please discuss. Blueboar (talk) 18:35, 7 February 2016 (UTC)[reply]

The MoS page does not deal with article titles, whereas the NCCAPS page deals only with article titles. This division of content has always existed, which is why we have a WP:MOS and the WP:AT policy. Regardless, this discussion is a duplicate of one already occurring, so I will close it and provide a link to that one. RGloucester — ☎ 19:09, 7 February 2016 (UTC)[reply]
The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
No problem discussing this at WT:AT... those who would have responded here are encouraged to go there and respond. Blueboar (talk) 20:19, 7 February 2016 (UTC)[reply]

Requirement to cite a list item inline?

I've been looking for a guideline on this (I'm quite sure it exists) but can't seem to find it. When maintaining a list article, I've long believed that verifiability is satisfied by the existence of reliable sources in the target article, so it is not necessary to provide an inline citation in the list, other than for the types of material required to be cited where it appears listed at WP:MINREF. For example, in the list at 1650, it is stated that the Harvard Corporation was established on June 9, 1650. In order to verify this, a reader goes to the link and can see in the target article where there is an explanation of the association's founding in 1650, with an inline reference which verifies the date. I believe it is therefore not necessary to repeat the reference in the list, as the information there is already verifiable and repeating the reference does not add anything. Am I wrong? Ivanvector 🍁 (talk) 20:49, 8 February 2016 (UTC)[reply]

Forget what policies or guidelines might say. Citing in the list maintains the integrity of the list from a verifiability point of view. What if, for example, the linked article is changed and the citation no longer appears or is misrepresented. Do your own research to verify the cite in the article then copy it to the list. Try a few caste-related lists to understand why this is the best approach. - Sitush (talk) 21:10, 8 February 2016 (UTC)[reply]
@Ivanvector: I think it depends on the list. I agree with you that items in lists like 1650 should be adequately sourced in their parent articles. However, other types of lists, like List of allegedly haunted places or List of electric bicycle manufacturers or List of wealthiest historical figures should be sourced right in the list. That said, even in articles like 1650, it's a convenience for the reader to cite in the list. ~ ONUnicorn(Talk|Contribs)problem solving 21:59, 8 February 2016 (UTC)[reply]
There are list types where citation is required, this would include anything that involves possibly contentious claims and definitely BLP-related. For example, a list of LGBT people would absolutely need entries sourced, while a list of people from a certain city is far less contentious and likely doesn't. However, citations should be strongly suggested even for non-contentious claim-based lists. --MASEM (t) 22:09, 8 February 2016 (UTC)[reply]
The WP:CIRCULAR policy says: "Do not use articles from Wikipedia as sources ... Content from a Wikipedia article is not considered reliable unless it is backed up by citing reliable sources. Confirm that these sources support the content, then use them directly." Given that, if someone challenges an uncited statement, I think it's best to simply take the relevant citation from the related WP article and apply it to the list. AFAIK, citations in the list itself would be expected for an WP:FL.—Bagumba (talk) 22:44, 8 February 2016 (UTC)[reply]

Is it simply Wild West?

I'm looking at serious ongoing behavioral issues, and don't know where to turn. WP:ANI doesn't seem to work. WP:NPOVN doesn't seem to work (although i would encourage everyone to watch that page and check it often to help others who are asking for help!) I have found admins who act abusively, instead of helping. I'm seeing bad editing practices all over the place. I'm seeing people unilaterally, archiving talk page sections that they don't like, re-reverting that when it's restored, refusing to acknowledge that it's a problem, insisting that there is consensus when there is not, hatting talk page sections that they don't like (to shut down the dialogue), people calling other editors names all the time, people using bad dialogue (like strawman/misrepresentation and rhetoric in place of substance) and the like. I'm seeing gang-like editing behaviors, where several editors seem to work together to maintain a page in a certain point of view. I'm seeing serious takeover of Wikipedia without a genuine regard to the policies. I'm seeing so much absurd stuff going on that it seems Wikipedia (at least in some topics) is broken. There is so much edit warring instead of discussion. There is unilateral action with complete impunity. There is very little actual enforcement of policies. There is WP:POV RAILROADing. I'm sorry i can't be more specific, but i have been observing these things in general for too long now, and the arbitrtion and enforcement structures simply do not work. It's broken. There is too much pushing and bullying. Where is the respect for each other and for "the sum of all human knowledge"? Rant over. Had to get that off my chest, and hope to hear your experiences, similar or different. SageRad (talk) 21:48, 8 February 2016 (UTC)[reply]

I agree with this wholeheartedly. To be added to Sage's list, I am also perceiving an increased tolerance of editors inappropriately editing others comments - to my mind this should be a clear line with swift and strong action taken if that line is crossed. Relatedly, I am also perceiving an increase in AN/I cases being closed by non-admins. Non-admins can not take action in such closures, therefore all these closures end with no action being taken when they perhaps should. Perhaps the policy of non-admins being allowed to close AN/I discussions needs to be reviewed. I feel this would help in avoiding the Wild West scenario.DrChrissy (talk) 22:12, 8 February 2016 (UTC)[reply]

Retrieved from "https://en.wikipedia.org/w/index.php?title=Wikipedia:Village_pump_(policy)&oldid=704000801"