Cannabis Ruderalis

Content deleted Content added
Legobot (talk | contribs)
Adding RFC ID.
(One intermediate revision by the same user not shown)
Line 846: Line 846:


== RFC: Allow stewards and global admins to help with countervandalism ==
== RFC: Allow stewards and global admins to help with countervandalism ==
{{rfc top|User withdrew RFC. --[[User:Izno|Izno]] ([[User talk:Izno|talk]]) 18:25, 18 December 2015 (UTC)}}
{{rfc top|User withdrew RFC. --[[User:Izno|Izno]] ([[User talk:Izno|talk]]) 18:25, 18 December 2015 (UTC)|rfcid=3EECBDB}}
:'''Withdrawn''' - I think it is clear which direction the discussion is going. I withdraw the proposal. -- [[User:Taketa|Taketa]] ([[User talk:Taketa|talk]]) 18:19, 18 December 2015 (UTC)
:'''Withdrawn''' - I think it is clear which direction the discussion is going. I withdraw the proposal. -- [[User:Taketa|Taketa]] ([[User talk:Taketa|talk]]) 18:19, 18 December 2015 (UTC)
Topic: ''Allow stewards and global admins to help with countervandalism''
Topic: ''Allow stewards and global admins to help with countervandalism''
Line 886: Line 886:
*'''Oppose''' The purpose of the global admin is to provide a service on small Wikipedias where the admin numbers are so low as to be heading for disaster. Enwiki hasn't reached that point yet. As to the global name changing that's already in, there are problems with that on occasions when outside people don't understand our naming policy. It's quicker, but people with unsuitable names have been renamed to equally unsuitable names. Removing a bureaucrat is rather a different matter than dealing with vandalism, just as closing an RfA is different from closing an AfD. Any global admin or steward who wants to do admin work here can apply in the usual way. [[User:Peridon|Peridon]] ([[User talk:Peridon|talk]]) 11:32, 17 December 2015 (UTC)
*'''Oppose''' The purpose of the global admin is to provide a service on small Wikipedias where the admin numbers are so low as to be heading for disaster. Enwiki hasn't reached that point yet. As to the global name changing that's already in, there are problems with that on occasions when outside people don't understand our naming policy. It's quicker, but people with unsuitable names have been renamed to equally unsuitable names. Removing a bureaucrat is rather a different matter than dealing with vandalism, just as closing an RfA is different from closing an AfD. Any global admin or steward who wants to do admin work here can apply in the usual way. [[User:Peridon|Peridon]] ([[User talk:Peridon|talk]]) 11:32, 17 December 2015 (UTC)
:'''Withdrawn''' - I think it is clear which direction the discussion is going. I withdraw the proposal. -- [[User:Taketa|Taketa]] ([[User talk:Taketa|talk]]) 18:19, 18 December 2015 (UTC)
:'''Withdrawn''' - I think it is clear which direction the discussion is going. I withdraw the proposal. -- [[User:Taketa|Taketa]] ([[User talk:Taketa|talk]]) 18:19, 18 December 2015 (UTC)
{{rfc bottom}}
{{rfc bottom|rfcid=B6873A7}}


== Are names a style issue or a content issue (or both)? ==
== Are names a style issue or a content issue (or both)? ==

Revision as of 19:00, 18 December 2015

 Policy Technical Proposals Idea lab WMF Miscellaneous 
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]

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]

  • @GrammarFascist: I agree. Also, many wp:XfDs attract very little attention, leaving the page creator, if they are still around, to be the only editor to cast a Keep vote. Sometimes the nominator very conveniently forgets to inform the page creator. It’s rare but I have seen wp:Admins deleting pages that had no "votes" (other than the nominator's implied vote). Ottawahitech (talk) 10:18, 14 November 2015 (UTC)please ping me[reply]
    There are not votes at XfD! They are comments, sometimes the rationale speaks for itself and the admin deletes the article. Mrfrobinson (talk) 02:40, 24 November 2015 (UTC)[reply]
  • Thank you for providing ONE example and claiming it as a fact. Mrfrobinson (talk) 16:10, 8 December 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:
  • What checkbox are you talking about?
  • Why do you say that they are not relevant to the majority of AfDs? Ottawahitech (talk) 17:17, 25 November 2015 (UTC)please ping me[reply]

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]

  • Some blogger can't write vanity articles about himself and friends, and has a long multi-page hissy fit about it. Meh. Reyk YO! 20:50, 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 thru 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]
  • @Ivanvector: You said user:SimonTrew’s [comment] might have been easy to misinterpret but believe me… Since you are vouching for him it sounds like you personally know Si Trew? Ottawahitech (talk) 01:45, 20 November 2015 (UTC)please ping me[reply]
  • @Ivanvector and Ottawahitech: I have no idea why my name is being brought into this. Anyway, Ivanvector and I know each other only through the RfD pages. However it would probably be fair to say Ivanvector has a good measure of my editing and reasoning style. Si Trew (talk) 02:47, 20 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]

  • @Ottawahitech: This is a rather worrying accusation especially since editors at RfD do explain their reasons if they are politely asked for it. We also have differing opinions (here's a live RfD demonstrating that) so I can't see how you view RfD as a monolithic clique. I'm sorry but I think we are no longer having a civilized discussion with all these accusations and unfair generalizations. --Lenticel (talk) 01:02, 24 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]
  • Every one of my user boxes was because of experiences I faced at AfD so it can't be Wikipedia's least dramatic spot. So, yes, deletion has become an evil place! --MurderByDeadcopy"bang!" 17:17, 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]
  • How about the source of this, you can't provide stats without the source. Mrfrobinson (talk) 02:23, 13 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]

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]
  • 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]
  • Ah, I see all the deletionist are out to win this simple, courtesy proposal too! The last thing Wikipedians want apparently is transparency. C'est la vie! --MurderByDeletionism"bang!" 16:22, 17 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]


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 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]

  • 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]
    • This can be solved by creating a page where editors can add their user names if they want to opt out from notifications. --Stefan2 (talk) 15:18, 17 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]

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]

@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]
  • Feel free to proclaim victory in a game nobody else is playing. Per WP:DENY I am withdrawing from further communication with you. Reyk YO! 18:55, 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]

Clarifying MOS:IDENTITY in articles in which transgender individuals are mentioned in passing

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.


This discusses a clarification to MOS:IDENTITY as recommended in this recent proposal. Which names and pronouns should be used for transgender individuals in articles of which they are not the principal subjects and that discuss events that took place before they publicly announced their transition? In the following examples, the first article is about the men's Olympics and the second article is about a film.

  • PREVIOUS ONLY: Generally it is unnecessary to go in detail over changes in name or gender presentation unless these are relevant to the passage in which the person is mentioned. Refer to transgender individuals using the name and pronouns that they were using at the time of the event in question.
    Example: Bruce Jenner competed in the men's Olympics in 1976; he won a gold medal. Larry Wachowski wrote the script for his film in 1994.
  • CURRENT ONLY: Generally it is unnecessary to go in detail over changes in name or gender presentation unless these are relevant to the passage in which the person is mentioned. Refer to transgender individuals using the name and pronouns that correspond with their most recent publicly announced self-identification.
    Example: Caitlyn Jenner competed in the men's Olympics in 1976; she won a gold medal. Lana Wachowski wrote the script for her film in 1994.
  • ALWAYS BOTH: Generally it is unnecessary to go in detail over changes in name or gender presentation unless these are relevant to the passage in which the person is mentioned. Refer to transgender individuals by both names, concisely; use either name first, as needed.
    Example: Bruce Jenner (later Caitlyn Jenner) competed in the men's Olympics in 1976; he won a gold medal. Lana Wachowski (credited as Larry Wachowski) wrote the script for her film in 1994. (Use the pronouns which correspond to the name which is used first.)
  • BOTH IF RELEVANT: Generally it is unnecessary to go in detail over changes in name or gender presentation unless these are relevant to the passage in which the person is mentioned. Refer to a transgender individual by both names, concisely, if the previous name is relevant in the context of the article where the reference is made; otherwise, use only the current name.
    Example: Bruce Jenner (later Caitlyn Jenner) competed in the men's Olympics in 1976; he won a gold medal. (Readers may wonder why a woman participated in a men-only event, and including Jenner's previous name resolves this.) Lana Wachowski wrote the script for her film in 1994. (Readers will not wonder why a woman wrote a script.) (Use the pronouns which correspond to the name which is used first.)
  • ONLY THE MORE RELEVANT: Generally it is unnecessary to go in detail over changes in name or gender presentation unless these are relevant to the passage in which the person is mentioned. Use the name and gender identity most relevant to the context of the passage in which the reference is made. When it is unclear which one is more suitable, default to the identity that would be used in the main biography.
    Example: Bruce Jenner competed in the men's Olympics in 1976; he won a gold medal. Lana Wachowski wrote the script for her film in 1994.
  • OTHER (1) = DEPENDS ON CONTEXT: Use the name and gender identity that fits best in the context of the article where the reference is made (principle of least surprise for the reader). When it is unclear which one suits better, default to the identity as defined for the main biography. Generally it is unnecessary to go in detail over name and/or gender identity changes, unless these are relevant to the article where the name of the person is inserted.
    Examples: see Wikipedia talk:Manual of Style#Ninth draft (proposal 2)
  • OTHER (2) = PREVIOUS STRICTLY APPLIED, BOTH WHERE USEFUL: For historical events, refer to transgender individuals using the name and pronouns that they were using at the time of the event in question. However, when the scope of a word, even within a sentence, is not clearly limited to the past, use the present name and pronouns. Consistency is not particularly important. Both may be used at editors' discretion if it makes the article better to do so.
    Example: Bruce Jenner competed in the men's Olympics in 1976; he won a gold medal. His world record was broken in 1980, but her innovation of carrying a spectator's American flag on a victory lap continues to this day. Larry Wachowski wrote the script for her film in 1994. (The innovation is still her innovation; the film is still her film, hence it is her film, her innovation. Had her world record survived until 2015, then it would be her world record!)
  • OTHER (3): (please explain)

This does not apply to biographical articles about transgender individuals; that is covered here. 18:10, 11 October 2015 (UTC)

Support ALWAYS PREVIOUS ONLY

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.


  1. Support This would be consistent with the way any normal name change is treated. A newly married woman can choose whatever naming convention she wishes to use. We accept that from the point in time that she makes such a declaration. We don't go back and rewrite her name into childhood. Transgender people should not have a special exception to go back and rewrite history, particularly when it goes against the core wikipedia policy WP:V. If public records at the time present a particular name, that is the name embedded in history for that event. If our married woman gets divorced and wants to erase her ex-husband's name, there are means to cross reference to the appropriate person but the historical name on the documents remains. Wikipedia provides that cross reference in directing the proper name to the current article which can clearly discuss the reason for the change, whatever it is. Trackinfo (talk) 18:40, 11 October 2015 (UTC)[reply]
    Except this is not consistent with the way any other name change is treated. We don't always keep the "previous" name... instead, we look and see how the majority of sources (written after the name change took place) handle the name change, and follow source usage. So... if the sources decide to "re-write" history, and use the "new" name in historical contexts, then we follow along and do so ourselves. If not, we don't either. Blueboar (talk) 21:13, 11 October 2015 (UTC)[reply]
    Take this as an example: List of Wimbledon ladies' singles champions#Open era where names evolve over time. Look at Evonne Goolagong in 1971 and 1972, Evonne Goolagong Cawley in 1976 and beyond. Chris Evert in 1978, Chris Evert-Lloyd in 1979. Those were their names of choice at the time they entered the tournament. Trackinfo (talk) 21:26, 11 October 2015 (UTC)[reply]
    Both of these examples are cases where the person didn't drop any of their old name, they just added a new name. We definitely need, IMO, to allow us to explicitly link the old name to the new name when the person is better known by the new name. עוד מישהו Od Mishehu 05:22, 12 October 2015 (UTC)[reply]
  2. Support per Trackinfo. I could write out an opinion myself, but I'd pointlessly reiterate a lot of what they've already stated.Godsy(TALKCONT) 22:20, 11 October 2015 (UTC)[reply]
  3. Support - Though I could certainly see adding a footnote stating current status on first mention in an article. Fyunck(click) (talk) 02:22, 12 October 2015 (UTC)[reply]
  4. Support. When we are discussing an event, a person named Bruce competed. Nobody named "Caitlyn" competed in the event. Caitlyn won a Women of the Year award. Not "Bruce". Grognard Extraordinaire Chess (talk) Ping when replying 02:15, 13 October 2015 (UTC)[reply]
  5. Support - Julius Caesar did not die in Rome, Italy, he died in Rome, Roman Empire. Historical events must not be rewritten with modern names. — Preceding unsigned comment added by Bobby Martnen (talk • contribs) 22:31, 23 October 2015 (UTC)[reply]
    Then we would be writing about the death of GAIVS IVLIVS CAESAR. Being clear on the name in use at the time to avoid anachronism is good, but so is including another name the reader might know of the subject by.--Trystan (talk) 23:44, 23 October 2015 (UTC)[reply]
    That is a different thing. "Julius Caesar" is the English Translation of "GAIVS IVLIVS CAESAR". We don't have an article called "History of Deutschland. Bruce Jenner is a completely different case, as someone English-speaking who changed their name. Another analogy is the Warsaw Pact. Warsaw is called "Warszawa" in Polish. If Poland decided to rename Warsaw "Miasto Walesa", we wouldn't rename the Warsaw Pact article "Miasto Walesa Pact", but the fact that Warsaw is called "Warszawa" in Polish wouldn't influence that decision. Bobby Martnen (talk) 18:31, 29 October 2015 (UTC)[reply]
  6. Strong support - Historical events must not succumb to emotional pity and the emotional weakness of human beings. Let's not ruin Wikipedia with our own emotions, let's make it a viable source, not a biased source. We can't lean towards transgenders, but we can't lean towards transphobes either.--AlHadeed (talk) 11:03, 1 November 2015 (UTC)[reply]

Oppose ALWAYS PREVIOUS ONLY

  1. Unacceptable Could almost live with it except that sometimes the context makes unavoidable to mention both, e.g. the lede of List of charges in United States v. Manning. For a tennis player comparison see the second paragraph of the lede of 2005 French Open, containing both Justine Henin-Hardenne and Justine Henin. --Francis Schonken (talk) 21:37, 11 October 2015 (UTC)[reply]
    An excellent example. Henin is referred to without the hyphenated name in the portion referring to the longer term (including after she divorced Hardenne). A historical time reference. Trackinfo (talk) 21:55, 11 October 2015 (UTC)[reply]
  2. strong oppose as completely contrary to BLP and multiple recent previous discussions. -- TRPoD aka The Red Pen of Doom 22:39, 11 October 2015 (UTC)[reply]
    With the constant insertion of female pronouns and names we have Transgender women marrying women and fathering children. Those have to be clear, repeat WP:BLP violations for all those other affected people due to wikipedia mis-reporting the identity of who they married or who their "father" was. The current identity is not the person who represented at that time.Trackinfo (talk) 01:00, 12 October 2015 (UTC)[reply]
    We have transgender women marrying and having children with other women? It's almost like gender identity and biology are two entirely different things. We do not have a duty to falsely represent the subjects of our articles because representing those subjects accurately might require a bluelink. That is, in fact, the precise opposite of our expectations for how content treats human beings. Ironholds (talk) 03:26, 12 October 2015 (UTC)[reply]
  3. Totally unacceptable essentially per TRPoD. The idea that this is "just how we handle people" simply falls apart when you look at how content does, practically, handle name-changes - around noble titles, particularly - where we tend to consistently use either the title'd name or the non-title'd name and not switch halfway through. Ironholds (talk) 03:28, 12 October 2015 (UTC)[reply]
  4. Comment Per the "treat transgender individuals like everyone else" argument, both Wikipedia editors and the wider world treat transgender name changes like a special case, and there's nothing wrong with the MOS reflecting that reality. If that ever changes, we can update the MoS then. Darkfrog24 (talk) 03:33, 12 October 2015 (UTC)[reply]
  5. Strong oppose per TRPoD. To "treat transgender individuals like everyone else" means to call them by their preferred names and pronouns. Nobody I'm aware of goes around calling Michelle Obama "Michael" or referring to her as "he". (And if somebody has done that, kindly don't link me.) Besides, many transgender people are better-known by their post-transition names; with regard to Laverne Cox, for example, it would make no sense to refer to her by whatever her name at birth had been. —GrammarFascist contribstalk 05:37, 24 October 2015 (UTC)[reply]
  6. Oppose: Offends too many people, is insensitive, and leads to never-ending conflict.  — SMcCandlish ¢ ≽ʌⱷ҅ʌ≼  14:52, 12 November 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.

Support ALWAYS CURRENT ONLY

  1. Support I see this option as the best for getting in line with the GLAAD Media Reference Guide. It is also the best option for dealing with the issue of deadnaming. - MellowMurmur (talk | contributions) 12:57, 13 October 2015 (UTC)[reply]
@MellowMurmur: Letting an advocacy organization influence how certain groups are described is highly inappropriate and against core policies.Godsy(TALKCONT) 18:08, 13 October 2015 (UTC)[reply]
@Godsy: Can you be more specific? I do not see advocacy organizations mentioned in the article you linked. - MellowMurmur (talk | contributions) 11:05, 14 October 2015 (UTC)[reply]
@MellowMurmur: WP:NPOV for example. All encyclopedic content on Wikipedia must be written from a neutral point of view. GLAAD's own website states "Shaping the media narrative. Changing the culture." WP:RIGHTGREATWRONGS: We can only report that which is verifiable from reliable and secondary sources, giving appropriate weight to the balance of informed opinion. WP:ADVOCACY: Advocacy is the use of Wikipedia to promote personal beliefs or agendas at the expense of Wikipedia's goals and core content policies, including verifiability and neutral point of view. Despite the popularity of Wikipedia, it is not a soapbox to use for editors' activism, recruitment, promotion, advertising, announcements, or other forms of advocacy.Godsy(TALKCONT) 14:18, 14 October 2015 (UTC)[reply]
Aspiring to a NPOV involves representing disparate views, not excluding them. MOS:IDENTITY explicitly says that, when usage in reliable sources is mixed, use the terms that a group uses for itself. How could we do that without considering the recommendations of organizations like GLAAD on LGBT-related issues?--Trystan (talk) 14:36, 14 October 2015 (UTC)[reply]
@Trystan: Hopefully that wording will change with the two concurrent RfCs about MOS:IDENTITY (i.e. this one and Wikipedia:Village pump (policy)/Archive 123#Revisiting MOS:IDENTITY in articles about transgender individuals). This issue shouldn't be treated differently from anything else, or made to be a drastic exception. However, you're correct, the current wording paints us in a corner regarding your last sentence.Godsy(TALKCONT) 15:51, 14 October 2015 (UTC)[reply]
To briefly clarify: "I see this option as the best for getting in line with the GLAAD Media Reference Guide." I'm objecting to getting "in line" (or in other words conforming) to an advocacy groups guidelines, as opposed to following reliable sources, as we do for everything else.Godsy(TALKCONT) 16:15, 14 October 2015 (UTC)[reply]
I am not a native english speaker and feeling a bit under fire here. Allow me to elaborate that I choose to mention the GLAAD Media Reference Guide here because it comes from people who have been spending a lot of time and energy on something very similar to what Wikipedians seem to be trying to do here. Namely figuring out best practices for writing about transgender individuals. What Trystan wrote sums up the intention of my contribution. The WP links you are offering seem to be dealing with how to write articles more than setting guidelines for what to say or not say at the village pump. - MellowMurmur (talk | contributions) 17:37, 14 October 2015 (UTC)[reply]
The links I offered (because you requested that I be more specific) do indeed deal with how to write articles, as does your suggestion. I've offered above how I feel we should alternatively handle it. We simply disagree, there is no need "feel... under fire", because we hold different opinions. Regards,Godsy(TALKCONT) 18:38, 14 October 2015 (UTC)[reply]
@Godsy: I believe these two proposals are only intended to deal with the gender identity subsection of MOS:IDENTITY. The text I am referring to, "if it isn't clear which is most used, use the term that the person or group uses", is in the general part of the guideline, and applies to all groups. (It used to be followed by an example of choosing between Jew and Jewish person.)--Trystan (talk) 01:27, 15 October 2015 (UTC)[reply]
@Trystan: In those cases, that may be a reasonable place to turn, as long as preceding text of the guideline (i.e. "When there is a discrepancy between the term most commonly used by reliable sources for a person or group and the term that person or group uses for themselves, use the term that is most commonly used by reliable sources") has been followed. I was confused by your characterization of the guideline above "when usage in reliable sources is mixed" which isn't the same as what it actually states.Godsy(TALKCONT) 01:50, 15 October 2015 (UTC)[reply]

Support ALWAYS BOTH

  1. Support This seems like it would work reasonably well. It's not at all rare for an actor to have "John Smith (credited as John A. Smith)" after their names. Darkfrog24 (talk) 18:11, 11 October 2015 (UTC)[reply]
    Poor example. We only do that when a name is credited differently from the commonly accepted stage name. When Marion Morrison started his career, he was credited as Duke Morrison. Once established, nobody every questioned him being credited as John Wayne. Trackinfo (talk) 21:14, 11 October 2015 (UTC)[reply]
    I mean that if we cite one of Wayne's earliest movies, we'd say "John Wayne (credited as Duke Morrison)." You know, I think the ALWAYS BOTH option should be a plan B. We should go with BOTH IF RELEVANT and then only switch to ALWAYS BOTH if there are too many fights over when it's relevant. Darkfrog24 (talk) 01:42, 12 October 2015 (UTC)[reply]
  2. Support I would support this for any case were someone has become widely known by more than one name, in the interests of clear writing. It is much clearer to let readers know they may know of Lew Alcindor as Kareem Abdul-Jabbar or that Leningrad is the same city as modern day St. Petersburg. While I don't think it is an egregious anachronism to say that Cary Grant was born in Bristol or that Michelle Obama attended Princeton, we should write in a way that both clarifies the name in use at the time and informs the reader they may know of the individual by another name.--Trystan (talk) 21:59, 11 October 2015 (UTC)[reply]
  3. Support Not just for transgendered people but for any proper name changes, where entity A is now know as entity B but at the time of point of coverage they were known as A. This option helps the reader in two ways: if they need to search for more sources beyond WP they will know what term to search for as at the time of the point of coverage, and when we are linking to the article on this entity, this will prepare the reader to recognize that they will be landing on a page with a different name but it is the same entity they clicked on. --MASEM (t) 22:10, 11 October 2015 (UTC)[reply]
    To be clear, I would think this only is when the sources or event is before the name change. For events/coverage well after the name change, the current name is sufficient by itself. --MASEM (t) 23:03, 11 October 2015 (UTC)[reply]
  4. acceptable (second choice) -- TRPoD aka The Red Pen of Doom 22:42, 11 October 2015 (UTC)[reply]
  5. Weak support; acceptable as an alternative, but I feel that under some circumstances (especially if they're more famous under their new name or their change is well-publicized) it isn't necessary to include the old name. --Aquillion (talk) 04:43, 12 October 2015 (UTC)[reply]
  6. Support (second choice). Sometimes the former name isn't relevant (this is true in both trans and non-trans cases, e.g. Princeton University lists "Michelle Obama" as a graduate, it doesn't use her previous name because it isn't notable/ relevant), so my first choice is "both if relevant (otherwise, only current)". Listing both names strikes a balance, a compromise, between listing only one name or only the other: it provides the benefits of the current name (crediting accomplishments to people under their most up-to-date names rather than fixating on old strings of letters; being recognizable to people who know only the new name; acknowledging the name change and thus avoiding misgendering the person and rejecting their identity; etc), and the benefits of the old name (reproducing whatever sources at the time said about a given event; being recognizable to anyone who knows only the old name). And as Masem notes, it avoids easter-egg links as would result if we used only former names in text (since in almost all cases the articles themselves are at current names). -sche (talk) 04:47, 12 October 2015 (UTC)[reply]
  7. Support as a compromise Not my first choice, but acceptable. This option avoids confusion, and doesn't assume that a reader knows facts which in fact some readers may not know. DES (talk) 11:58, 12 October 2015 (UTC)[reply]
  8. Support in all cases of name change (not just transgendered people) except where the change is merely adding a new part to the old name (e.g Evonne Goolagong/Evonne Goolagong Cawley) and/or removal of previously added parts (Justine Henin-Hardenne/Justine Henin). This shouldn't apply, however, in a list of then-unnotable people who come from a specific place or graduated from a specific educational institution, etc., such as the Michelle Obama example above. עוד מישהו Od Mishehu 12:27, 12 October 2015 (UTC)[reply]
  9. this is acceptable, though not my first choice. I don't like the MOS pushing us to add clutter to articles, and there are plenty of places where including both may not be the most reasonable option. However, there are many scenarios where this would work fine and not contribute to misunderstandings + it's better than many of the other options. Protonk (talk) 18:05, 12 October 2015 (UTC)[reply]
  10. Support (as my first choice).  For articles where the person is not the primary subject of the article, I believe both names should be used.  This would give the reader the maximum amount of information, and without attempting to rewrite history.  (My second choice would be "PREVIOUS ONLY.")
    Richard27182 (talk) 12:16, 13 October 2015 (UTC)[reply]
  11. Support (as first choice), but avoid pronouns: The examples given for this option are severely faulty in using "he". Rewrite to avoid the necessity to insert a pronoun that may be insensitive to subject, and which will cause never-ending strife from language-change activists. Usually one can either merge two short sentences in a way that obviates a need for a pronoun, switch to a neutral pronoun with a non-human referent ("this record", not "his record"), or repeat the surname (if it has not changed). Generally, and certainly in both of these examples, the names before and after the public change are both relevant, if for no other reason than to prevent any reader confusion or ignorance about who is being written about. And crediting persona B with the works of persona A is philosophically problematic, confusing to readers, and violates the norms of crediting.  — SMcCandlish ¢ ≽ʌⱷ҅ʌ≼  14:56, 12 November 2015 (UTC)[reply]

Support BOTH IF RELEVANT

  1. Support This seems to be the best option to me. EDIT: We should use this rule on a provisional basis. If there are too many fights over what's relevant and what's not, then we auto-switch to ALWAYS BOTH. Darkfrog24 (talk) 18:11, 11 October 2015 (UTC)[reply]
  2. support under the proviso, ALWAYS includes the current with previous if relevant/necessary-- TRPoD aka The Red Pen of Doom 22:41, 11 October 2015 (UTC)[reply]
  3. Support, with caveat I would put the current name first, as in "Caitlyn Jenner (then Bruce Jenner)", and use the person's currently-preferred pronouns. Funcrunch (talk) 22:48, 11 October 2015 (UTC)[reply]
    Support, with different caveat - it will rarely be relevant, so care should be taken to avoid presuming relevancy where there was none as seen by reliable sources at the time. For example, in an article about the 1976 Olympic Games, there is no obvious relevance to referring to the decathlon winner as any name other than Bruce Jenner or as any gender other than male. Had the events happened 30 years later, there might have been some relevance since, by then, the international sporting community was actively dealing with the issue of transgender athletes who were born male and wanted to compete as female. davidwr/(talk)/(contribs) 00:53, 12 October 2015 (UTC)[reply]
    You do understand that this option means "always use the current name and only use both if the previous name is relevant," right? Darkfrog24 (talk) 01:40, 12 October 2015 (UTC)[reply]
    Thanks, somehow I missed that. davidwr/(talk)/(contribs) 01:55, 12 October 2015 (UTC)[reply]
    That actually is what should be done. The current name should be the default, with clarification using the previous name only if there is a public reason for it (like, everyone pretty much knows what Jenner's name was when she won her gold, anyway, and the media and olympic records reflect it, etc.). TMagen (talk) 10:32, 12 October 2015 (UTC)[reply]
    There are transgender people that have done notable things prior to their transition and abandoned that life and name. Connecting them by this policy would be problematic. "John Smith invents widget, quietly leaves that life and transitions to Jane Doe. Wikipedia updates the widget article to reflect inventors new name/transition even though inventor left that life and name behind." Wikipedia should not be in the business of blindly connecting pre and post transition identities. Suicides have been attributed to such carelessness. --DHeyward (talk) 21:07, 12 October 2015 (UTC)[reply]
    That is an edge case I worry about. However, every option on this RFC is problematic with regard to that edge case: if the pre- and post-transition names aren't connected in visible text, there'll still be an (easter-eggy) wikilink (if the person is notable enough to have their own article). The question, for me at least, is thus: what's better as the general rule? And I think the answer is: acknowledging the current name visibly. The top of the MOS notes that there may be occasional exceptions to any of its rules. And on the talk page of an article of a widget company where someone was notable enough to be mentioned, but not notable enough to have their own article, you could make a compelling argument that the current name should be handled as one of those exceptions and excluded as WP:UNDUE. -sche (talk) 21:27, 12 October 2015 (UTC)[reply]
    @-sche: Context matters which is why I chose it. My concern is that there are dogmatic crusaders that care less about the individuals wishes than they do about their agenda. There will be persons that care less about what the individual wants and choose their own dogmatic view. Some of those will argue for pre-transition name only. Others will argue post-transition name always. The truth is that individual choices matter far more than ideology. If Caitlyn Jenner wants her children to call her "dad," we are in no position to oppose this. If she is aware of the infobox picture and chooses not to update it based on her business and personal goals, we shouldn't listen to ideologues that are furious when she is not. If she wants all present day references to use "Caitlyn" we shouldn't say "Bruce" where "Caitlyn" is preferred. We must be sensitive to context over ideologues because there is no universal response that is always correct. --DHeyward (talk) 07:15, 15 October 2015 (UTC)[reply]
  4. Support (first choice), preferably with Funcrunch's caveat. (1) This attributes things to people who did them using the most up-to-date names, rather than fixating on what strings of letters period sources used. Editors seem to find this intuitive in non-trans cases, e.g. Princeton University says "Michelle Obama" graduated from there in 1985 even though her surname wasn't "Obama" until 1992. (2) It avoids unnecessarily misgendering people, which jars many readers/ editors and is incorrect because scientific understanding from brain studies etc. is that e.g. a trans man was never a woman and one cannot accurately say "she did X" or "he was a woman until he came out at 23" any more than "John was attracted to women until he came out as gay at 24" or "diseases were caused by miasma until about the 1880s, when germs began to cause them". (3) Where a previous name is relevant/notable, this allows for it, so as to inform people who expect the previous name either based on their knowledge or the context (as in the Olpymic example, where the inclusion of the previous name clarifies why Jenner was participating in the men's competition), while also having the current name for the reasons above and because (especially younger) readers who know only a new name (especially of someone who transitioned further in the past than Jenner) will not recognize the old name and may not think to click a wikilink, if the person is even notable enough that one is possible (such links are easter eggs, anyway). Reasons 1 and 2 are why I prefer this to "always both". -sche (talk) 01:27, 12 October 2015 (UTC)[reply]
  5. Support This places things into historical context but respects the person's current status. - Knowledgekid87 (talk) 02:11, 12 October 2015 (UTC)[reply]
  6. Support per Funcrunch, although in the given example and related situations, I would retain "(credited as Larry Wachowski)" since the name a credit appears under is generally going to be relevant. —烏Γ (kaw), 02:23, 12 October 2015 (UTC)[reply]
  7. Support, although I would say that in the second case, the former name (but not the former gender) is relevant because readers might be surprised to see that Lana wrote the movie when the credits say Larry. --Ahecht (TALK
    PAGE
    ) 02:28, 12 October 2015 (UTC)[reply]
  8. Support Seems the best option, though I agree with Funcrunch's caveat. While I have this page on my watchlist and saw it that way, I was also pointed to this discussion by a post to my talk page. PaleAqua (talk) 02:59, 12 October 2015 (UTC)[reply]
  9. Support. They're all problematic in some way, but this seems like the least problematic. Some kind of note is probably required to explain non-intuitive situations, such as sportspeople. NinjaRobotPirate (talk) 03:37, 12 October 2015 (UTC)[reply]
  10. Support, although with several caveats. I would always give their current name precedence, so it would be eg. "Caitlyn Jenner (then Bruce Jenner)" or something similar rather than the reverse. On the other hand, I would want to define "relevant" somewhat broadly -- generally, if people are likely to be reading this section of an article or parsing a list looking for a specific name, then we should have the name there somewhere to avoid confusion. The main questions to me are "are there likely to be significant numbers of people who will read this looking for a specific name, and only know that name, even if it's out of date?" And, more generally, "are there significant numbers of people likely to be confused by this, whether because they're only familiar with the old name or whatever?" If so, we should generally have both names. --Aquillion (talk) 04:41, 12 October 2015 (UTC)[reply]
  11. Weak support, without pronouns - I would suggest the name in use at the time is usually relevant - including how a writing credit for Lana Wachowski would have appeared in the work. I suppose there are a few cases where it wouldn't be, along the lines of "Lana Wachowski attended Oxbridge", where you don't really need to know the name in use at the time. I would remove the pronouns from the examples; it is trivially easy to avoid them when mentioning someone in passing. While it is an historical fact that Jenner was named Bruce at the time, the issue of whether she was always a trans woman or only became one when she transitioned will be highly contested.--Trystan (talk) 05:48, 12 October 2015 (UTC)[reply]
  12. Weak Support I believe this option and "only the more relevant" are the most reasonable, but I'm more inclined to support the latter, since this one produces potentially unnecessary clutter, and redirect links would make the disambiguation clear in the latter. --Waldir talk 09:23, 12 October 2015 (UTC)[reply]
  13. Support. The current name should be the default, and the previous name should be used for clarification, context, or any other reason that is important to understanding the content (for example, if all the sources are from the time, and refer to the person by the previous name). TMagen (talk) 10:35, 12 October 2015 (UTC)[reply]
  14. Support, provided "current only" is the preferred option & 'relevance' is a higher standard than 'this is the name sources used at the time'. Protonk (talk) 18:07, 12 October 2015 (UTC)[reply]
  15. Support, in that I think my cavaets on the previous option (the USE BOTH ALWAYS) amount to this at the basic level, or at least my opinion sits somewhere between these at a high level. I do stress that relevancy should be based on sources at the time if we are talking a date event, as to make sure the reader has a good awareness of search terms to do their own research as well, and common sense does come into play (ala the Michelle Obama example). --MASEM (t) 18:13, 12 October 2015 (UTC)[reply]
  16. Support As others have pointed out, it will not always be necessary to use both names. When it is, the current name should be put first. I would write it thus: "Caitlyn Jenner (then known as Bruce Jenner). I include the "known as" because it's not that she was a different person then; she was just known by a different name. Neljack (talk) 22:32, 12 October 2015 (UTC)[reply]
  17. Support parenthetical dual-naming as an appropriate style when readers' might otherwise be confused or draw false inference. Vannie227 (talk) 00:26, 16 October 2015 (UTC)[reply]
  18. Support with the specification (as Funcrunch and others suggested above) that the current name should come first, and the previous name be given as a parenthetical. Wording such as "Caitlyn Jenner (competing as Bruce Jenner) won that gold medal", to clarify why the previous name is mentioned at all, seems a good idea. —GrammarFascist contribstalk 05:26, 24 October 2015 (UTC)[reply]
  19. Support (as second choice), but avoid pronouns: The examples given for this option are severely faulty in using "he". Rewrite to avoid the necessity to insert a pronoun that may be insensitive to subject, and which will cause never-ending strife from language-change activists. Usually one can either merge two short sentences in a way that obviates a need for a pronoun, switch to a neutral pronoun with a non-human referent ("this record", not "his record"), or repeat the surname (if it has not changed). Generally, and certainly in both of these examples, the names before and after the public change are both relevant, if for no other reason than to prevent any reader confusion or ignorance about who is being written about. And crediting persona B with the works of persona A is philosophically problematic, confusing to readers, and violates the norms of crediting. I allow that in some cases (e.g. long lists of credits) it may not be necessary to include the second name, but in running prose we should usually do so. If you like, think of my position as being a clarified stand between the option I'm !voting on here, and the oen above this: "USUALLY BOTH".  — SMcCandlish ¢ ≽ʌⱷ҅ʌ≼  14:56, 12 November 2015 (UTC)[reply]
  20. Support Seems like the option that would offend the least people. Also reduces discrepancies when referring to sources. Swordman97 talk to me 03:43, 13 November 2015 (UTC)[reply]
  21. Support: This generally seems to be the most sensible approach. Midnightblueowl (talk) 21:02, 16 November 2015 (UTC)[reply]

Support ONLY THE MORE RELEVANT

  1. This option seems more in line with WP:Trans?, already in use. Megalibrarygirl (talk) 21:35, 11 October 2015 (UTC)[reply]
  2. Support as long as the name is wiki-linked, this seems to be the most useful for readers, since it avoids cluttering the text while providing proper disambiguation to the current gender (either by using a redirect or a piped link). --Waldir talk 09:25, 12 October 2015 (UTC) moving my support to "DEPENDS ON CONTEXT" --Waldir talk 18:26, 17 October 2015 (UTC)[reply]

Support OTHER (1) = DEPENDS ON CONTEXT

  1. Support, for reasons explained at Wikipedia talk:Manual of Style. --Francis Schonken (talk) 20:39, 11 October 2015 (UTC)[reply]
  2. I support using the most relevant names depending on the context. This is how we deal with choosing historical vs modern names in other articles... I see no reason why we should handle name changes that are due to gender identity any differently. Sometimes (mostly in list articles) we only mention one name (because only one name is relevant in that context)... but at other times (mostly in more sentence based articles) we give multiple names (because both names may be relevant in that context). In other words... this simply isn't an issue that can be resolved by one-size-fits-all ALWAYS THIS or ONLY THAT "rules" - It's a SOMETIMES THIS BUT SOMETIMES THAT issue, that can only be resolved by giving editors flexibility to reach a consensus. Which names to use (whether the "former" name, the "new" name, or both) should be determined on a case by case basis. I Oppose framing this as a one-size-fits-all "rule" with ALWAYS and ONLY "rules", because different solutions will be appropriate in different contexts. Context and source usage drive which names are used, not our own biases. Blueboar (talk) 21:07, 11 October 2015 (UTC)[reply]
    Tx! I knew this proposal wasn't too difficult to grasp. Tx again. --Francis Schonken (talk) 23:56, 11 October 2015 (UTC)[reply]
  3. Support a variant: Use #1:PREVIOUS ONLY unless context dictates otherwise "Refer to transgender individuals using the name and pronouns that they were using at the time of the event in question" unless context demands using both names or conceivably, in rare cases, the other name. In an article about the 1976 Olympics, the winner of the decathlon is Bruce Jenner, and the pronoun-gender is male. In an article or about famous transgender people, it could go either "Bruce Jenner (now Caitlyn) won the decathlon" or "Caitlyn (then Bruce) Jenner won the male decathlon" with a pronoun gender of male or female respectively. davidwr/(talk)/(contribs) 02:05, 12 October 2015 (UTC)[reply]
  4. Support essentially for the same reasons as Blueboar plus the additional caveat that always- and only-types of rules sometimes result in absurdities. An article about the 1976 Olympics needn't go beyond mentioning the name (then) of the winner of a particular event. This is the name that will be in contemporary sources, and this is the name that someone familiar with the subject would expect to see. An article about transgender athletes would be an appropriate place to mention both names. An article about some recent event (post-change) where the same individual made an appearance or was presented an award needn't mention any but the current name of the individual who attended and, if relevant, the individual's gender (one place it is usually relevant is when an appropriate pronoun is used, at which point the gender is implied rather than stated). It might be a good idea to have a default option when it isn't completely clear from the context which option to use. Etamni | ✉ | ✓  03:00, 12 October 2015 (UTC)[reply]
  5. Support as a matter of historical accuracy balanced with common sense. Dirtlawyer1 (talk) 03:37, 12 October 2015 (UTC)[reply]
  6. Support for historical accuracy. The historical achievement was made using a certain name, and that name should always be connected with the achievement. Binksternet (talk) 05:06, 12 October 2015 (UTC)[reply]
  7. Support as sources are likely to identify contextual relevance. There are no hard and fast rules and the individual will have different levels of difference to dead names. We should not presume hat someone wishes to be linked to the accomplishments of their dead name so context matters. If a person was previously a male athlete record holder and transitions, we should not presume that they wish to be known as a male athlete record holder. PC police are not the BLP police. --DHeyward (talk) 05:10, 12 October 2015 (UTC)[reply]
  8. Support Just as usage in reliable sources (which we should follow without good reasons not to) will vary from case to case, so our usage should vary. In sports articles (excepting special ones like LGBT Olympians) it's enough to call Jenner simply "Bruce Jenner"; Jenner being transgender or her later name Caitlyn are not in any way relevant (indeed, repeatedly noting them would give them undue weight) and only serve to confuse things. (When she publicly announced her new name Caitlyn and identity as a woman, there were very unfortunate attempts by at least one editor to credit Jenner with records in women's athletics, sources not required.) In other articles it may be appropriate to use Bruce, Bruce (later Caitlyn), Caitlyn (then Bruce) or simply Caitlyn, depending on how relevant each name is. Sideways713 (talk) 10:12, 12 October 2015 (UTC)[reply]
  9. Support Similar to option 5 above, we should generally follow the reliable sources. If there is any plausible confusion, we should give both names, putting the one favored by reliable sources in the context involved first. I mostly agree with Sideways713 above. DES (talk) 12:02, 12 October 2015 (UTC)[reply]
  10. Support. Context is always more important than maintaining a single dogma. It would be ludicrous to say that Caitlyn Jenner won a medal in an article about the event in which the medal was won. Caitlyn Jenner didn't; Bruce Jenner did. This is making no comment on Jenner's gender identity at the time. It is simply stating a fact. The same with Lana Wachowski. Lana Wachowski did not make films before 2012; Larry Wachowski did. Again, that is making no comment on Wachowski's gender identity at the time. It is simply stating a fact. We do not practise revisionism on Wikipedia. -- Necrothesp (talk) 15:12, 12 October 2015 (UTC)[reply]
  11. Support This does not happen enough to justify making hard rules. Check context and build precedents for more time. Blue Rasberry (talk) 19:55, 12 October 2015 (UTC)[reply]
  12. Support There are obviously times when a new name is not relevant, such as in an article about a television series that ended 30 years ago. What has happened to anyone since then has little relevance to the series so there is no need to include the new name. What is important in such a case is what happened at the time. On the other hand, there may be cases where inluding both the old name and new name may be necessary. What to do in any case should be determined based on context. --AussieLegend () 01:52, 13 October 2015 (UTC)[reply]
  13. Context matters. In the case of the historical record of Olympic results, "Bruce Jenner" is relevant and making note of the decades later change to her current identity/name as Caitlyn is not. I view this in similar vein to athletes who compete under one name and later got married. The record is rarely changed retroactively. But this is only one example, and it is foolish to tie ourselves down to an all or none situation. There will undoubtedly be cases where such individuals are mentioned in passing, but for which the use of both names, a later name or a footnote will be important. But as a general rule, articles or lists that document the historical record should be left as-is. Anachronisms are unencyclopedic. Resolute 16:10, 13 October 2015 (UTC)[reply]
  14. Support From a historian's standpoint, all names are relevant to building the profile of a person; however, that being said, privacy issues must be taken into consideration, especially on BLP. We don't re-write history nor push POV. Name changes happen often with women in certain cultures and knowing all of the links becomes essential for building their timeline. On the other hand, there are times when people have chosen to disassociate with a prior life and those choices must be respected. There is no rule for all contingencies. Common sense, when the notability in life occurred, whether a prior identity is relevant or disclosure might cause harm must all be weighed. If one doesn't have the ability to analyze, mayhaps they need to leave that article for someone else to write, rather than creating a hard and fast rule. SusunW (talk) 16:56, 14 October 2015 (UTC)[reply]
  15. Support – bottom line, we need to go on what the sources at the time state. To take an example I just stumbled across, the credit for the CHiPs episode is for "Bruce Jenner", not "Caitlin Jenner", so in a situation like that, the credited name must be used. Etc. --IJBall (contribs • talk) 05:39, 17 October 2015 (UTC)[reply]
  16. Support per the Principle of least astonishment, as long as the final recommendation is phrased as clearly as in the option description above, and not hinging too much in the "depends on context" part. --Waldir talk 18:28, 17 October 2015 (UTC)[reply]
  17. Support (second choice) per above.Godsy(TALKCONT) 19:05, 22 October 2015 (UTC)[reply]
  18. Support (second choice) I advocate for inflexibility above because this option calls for people being reasonable. In most cases, wikipedia editors can reach a consensus and reason outweighs WP:POV. And yes I have had some crazy arguments that haven't always gotten there, but the majority of the time, reason works. As the editor who wrote probably the majority of the content about Bruce Jenner over the last 5 years, starting from my own track career competing with Bruce. I have been dealing with this evolving situation around this article and its web of wikilnks for more than six months. The crew of POV pushing advocates have so driven opinion regarding this case, including the rewrite of the MOS we are dealing with here, that reason has gone out the window. Their opinion is that Bruce never existed and their desire is to wipe out the history of this person that is familiar to millions of people. If they succeed, it will lend more credence to the internet mantra, you can't trust wikipedia, more often repeated in full sarcastic tone "You can trust wikipedia." Give them an inch and they will take a mile. This less restrictive alternative will give them that inch. Trackinfo (talk) 22:07, 29 October 2015 (UTC)[reply]
  19. Support also judicious phrasing will generally obviate most problems. Having said that it will often be contextually necessary to mention the later name. All the best: Rich Farmbrough, 17:36, 9 November 2015 (UTC).[reply]

Neutral on OTHER (1) = DEPENDS ON CONTEXT

  1. This would be preferable to "always the former" or "always the current", which are basically PoV-pushing WP:ADVOCACY of two opposing types. However it's basically a wishywashy pseudo-option that in actual practice will resolve to "usually both", the compromise between "always both" and "both when relevant", since both usually will be relevant. That is to say, everything on WP depends on context, so having an explicitly "depends on context" option here is like saying "I will breathe, but only if I'm alive". It's tautological hedging for no reason.  — SMcCandlish ¢ ≽ʌⱷ҅ʌ≼  15:06, 12 November 2015 (UTC)[reply]

Support OTHER (2)

  1. Just to be cussed I put up what makes the most sense to me, but only by a hair, I must admit. There is no especially appealing way to handle this bug in our language, but I think we should dissect even individual sentences to choose one or the other. Wnt (talk) 15:19, 30 October 2015 (UTC)[reply]

Oppose OTHER (2)

  1. Strongest opposed to this option. Any result like "His world record was broken in 1980, but her innovation of ...", or "Larry Wachowski wrote the script for her film" is unacceptable. Any reader not already intimately familiar with the subject (and remember that is about mentions in passing at other articles) will have no idea what this means. Each construction appears to refer to some other, unnamed, female person, and will be taken for an editing error, implying that something was accidentally deleted.  — SMcCandlish ¢ ≽ʌⱷ҅ʌ≼  15:12, 12 November 2015 (UTC)[reply]

Discussion (trans individuals in other articles)

Please give a better description to the option described as "Other 1". Georgia guy (talk) 21:08, 11 October 2015 (UTC)[reply]

Please feel free to do so yourself; add it as "OTHER (2)" – I might like it and change my !vote. Francis Schonken (talk) 21:18, 11 October 2015 (UTC)[reply]

Pursuant to discussion on WT:MOS, I have notified the two WikiProjects which are directly concerned with this topic: Wikipedia talk:WikiProject LGBT studies (diff) and Wikipedia talk:WikiProject Manual of Style (diff). -sche (talk) 21:51, 11 October 2015 (UTC)[reply]

The issue of using appropriate historical names impacts a lot of projects... so please alert more than just those two. For example, as can be seen from our using the choice of Bruce vs Caitlyn Jenner as an example, I think you should have alerted Wikipedia talk:WikiProject Sports (I have corrected the omission). We should give this as wide an audience as possible, so if anyone thinks a project should be notified, please do so. Blueboar (talk) 00:16, 12 October 2015 (UTC)[reply]
Excellent idea, BB. I also plan to hit up the bio noticeboard, and if anyone wants to get started on notifying the participants in the previous discussion, that'd be great. Just do it on their personal talk pages so we don't get any double-alerts. Darkfrog24 (talk) 00:47, 12 October 2015 (UTC)[reply]
I have just notified Wikipedia:WikiProject Television, since it affects that project as well. --AussieLegend () 02:28, 17 October 2015 (UTC)[reply]

The more comments I see on this the more I come to believe that BOTH IF RELEVANT would be the best choice, but ALWAYS BOTH is less likely to cause fights. I think we should adopt BOTH IF RELEVANT on a six-month provisional basis and then auto-switch to ALWAYS BOTH if there are too many fights or too much trouble. Darkfrog24 (talk) 01:43, 12 October 2015 (UTC)[reply]

  1. Question, suppose the person does not want to have explained about his or her transgender, has this been discussed before? Lotje (talk) 13:46, 13 October 2015 (UTC)[reply]
Oooh, I don't know. But MOS:IDENTITY has included the words "unless the subject has indicated a preference otherwise" for a long time. I don't see that it would be a big problem to add those words to this part of the rule too. Darkfrog24 (talk) 14:30, 13 October 2015 (UTC)[reply]
Wikipedia is not censored... if reliable sources discuss someone's transgender, so can we. While we try to respect the desires of the subject of an article, we are not limited by them. Blueboar (talk) 15:58, 13 October 2015 (UTC)[reply]
Blueboar has it exactly, though I'd add that it's fine to use the person's preferences where they do not contradict this. On transgender issues, the fact that it is polite to refer to someone by his or her preferred gender pronoun ordinarily wouldn't hold much weight, but because the jury is so far from being in on things like reliable sources, the biological realities underlying transgenderism, and whether this is a correction or a change, then it serves as a pretty good tiebreaker. Darkfrog24 (talk) 16:03, 13 October 2015 (UTC)[reply]


Hi Darkfrog24.  I agree with you when you write that "ALWAYS BOTH is less likely [than BOTH IF RELEVANT] to cause fights."  But I'm not so sure about your proposed solution of "adopt[ing] BOTH IF RELEVANT on a six-month provisional basis and then auto-switch to ALWAYS BOTH if there are too many fights or too much trouble."  After six months, who or what criterion would be making that decision?
Richard27182 (talk) 08:43, 14 October 2015 (UTC)[reply]

We look around and observe whether anyone's been fighting over it. I guess we could also ask the participants here to keep their eyes open. The good thing about hosting MOS:IDENTITY at the MoS is that a lot of the time, people post notices of disputes at WT:MOS. Darkfrog24 (talk) 13:58, 14 October 2015 (UTC)[reply]

I don't understand the purpose of the "Oppose ALWAYS PREVIOUS ONLY" category.  All the other categories are "support" categories; why does "ALWAYS PREVIOUS ONLY" have its own "oppose" category?
Richard27182 (talk) 08:46, 14 October 2015 (UTC)[reply]

Initially, no option had an 'oppose' section. However, enough people posted explicit objections / comments on the problems of that option that someone thought it would improve the readability of the thread to put those objections in a subsection. -sche (talk) 09:04, 14 October 2015 (UTC)[reply]


I know I'm not the first person to bring this up, but it's important and I think it deserves more attention than it's getting.  One of the problems with using the current identity only is potential conflicts with WP:BLP.  Suppose a female trans (while still biologically male and still publicly identifying as a man) had married a woman (let's say the fictitious Mary Smith).  If we must always use the current name only, then we would have to write "[trans current name] married Mary Smith."  Mary Smith may feel this implies that she is a lesbian, and if so, may feel insulted, maybe even libeled.  Our only real option would be to make no mention of the marriage at all!  How would the proponents of CURRENT ONLY propose to handle this kind of situation?
Richard27182 (talk) 09:11, 15 October 2015 (UTC)[reply]

I'm not a current-only supporter, but I do feel we should make a presumption in favour of current pronouns, so issue does come up. I'd say: "Prior to coming out as a trans woman, she married Mary Smith."--Trystan (talk) 13:37, 15 October 2015 (UTC)[reply]
A LOT depends on which article we are talking about... and who the subject of the sentence is. Is the "she" referring to the trans-gender person, or to the non-transgender spouse? In an article about the non-transgender spouse (Let's call her "Susan"), it is both inaccurate, and potentially harmful to say "In 1993, she married Mary Smith". Saying that implies that Susan is lesbian. I think we should say "In 1993, she married Joe Smith".
Now... if Mary is notable in her own right (and also has an article)... I think it appropriate to link the name "Joe Smith" to the Mary Smith article (where the transition from "Joe" to "Mary" should be explained). If Joe/Mary isn't notable (and thus does not have an article to link to)... then we have another question to ask... is the issue of Mary's current trans-gender identity relevant to Susan's life. It may not be... and if not, then there is no reason to mention it in the article on Susan. Blueboar (talk) 14:47, 15 October 2015 (UTC)[reply]
I think Trystan has it right. While generally it is not necessary to go into detail that a person is trans, briefly referring to it to prevent confusion is fine. Darkfrog24 (talk) 16:33, 15 October 2015 (UTC)[reply]
@Trystan: @Darkfrog24:
I think Trystan's  "Prior to coming out [emphasis added] as a trans woman, she married Mary Smith."  is a major improvement over my (deliberately constructed) worst case. However it still has a problem. It fails to rule out the possibility that, even though the person Mary married had not yet publicly come out as a trans woman, Mary may still have been totally aware of the situation. If she was not aware of the situation at the time, she might still find the statement offensive and libelous.
Richard27182 (talk) 00:35, 16 October 2015 (UTC)[reply]
I can see why someone might find the information "You married someone who later came out as a trans woman (so it is possible to construe that you were in a same-sex marriage depending on one's definition of the term)" offensive, but if it's true then it's not libelous. If these are living people, then we'd have to be careful (only say it when relevant, don't say "they were in a same-sex marriage" because that's interpretation and not fact, etc.), but it would fall under WP:NOTCENSORED. Darkfrog24 (talk) 01:05, 16 October 2015 (UTC)[reply]
[inserted  05:52, 16 October 2015 (UTC)]  Ping:@Darkfrog24:
This is a complicated subject and I probably wasn't clear enough in my posting.  What I meant was that if Wikipedia stated that "Prior to coming out [publicly] as a trans woman, she married Mary Smith," some readers might assume that Mary Smith likely knew the true gender identification of her own spouse even though the world as a whole did not.  But if Mary did not know of the "trans" gender identification of her spouse at the time of the marriage, then for those readers the article would be misrepresenting something about Mary. And she might see it as defamatory or libelous.  (I'm not sure if I just clarified my point or further obfuscated it.)
Richard27182 (talk) 05:52, 16 October 2015 (UTC)[reply]
We shouldn't imply she knew, but it is not our job to rule it out either. Not being a tabloid that delves without cause into the most private details of the relationship between spouses, there are very few situations in which we either would or could comment at all about what Mary knew and when. If we are presenting verifiable facts in a clear and fair way, it isn't defamation.--Trystan (talk) 12:41, 16 October 2015 (UTC)[reply]
I don't think telepathy is RS. I would say that the words as you've given them, Richard, don't imply whether Mary knew one way or the other. I also think you're overestimating how scandalous it is to be married to someone who later comes out as trans. Darkfrog24 (talk) 12:58, 16 October 2015 (UTC)[reply]
[inserted - 11:33, 17 October 2015 (UTC)] Ping: @Darkfrog24:  @Trystan:
The point I'm trying to make (not very well, I'm afraid) is that there are scenarios where it would be problematic if we have the MOS prohibit any mention of a trans's past name, or gender identification, or previously applicable pronouns.  For example we know that WP:BLP sets extremely strict standards for writing about  "any [emphasis added] living person mentioned in a BLP, whether or not that person is the subject of the article, and to material about living persons in other articles and on other pages, including talk pages."  Considering the previously discussed case of the fictional "Mary Smith," if Mary belongs to a very conservative religion that condemns transsexualism, and if the Wikipedia article could be seen by some as even suggesting the possibility that Mary had knowingly been married to a trans, I believe that that, in and of itself, would trigger WP:BLP issues.  I agree with Trystan that  "[T]here are very few situations in which we either would or could comment at all about what Mary knew and when."  But I believe that this is one of those very few situations where we do have to be extremely careful about what we write and avoid any possibility of giving the wrong impression, because of the sensitive nature of the issue involved.  For this reason (as well as other reasons), I feel that having the MOS require that all references to trans's must use only their current identification is not just impractical, but totally infeasible.
Richard27182 (talk) 11:33, 17 October 2015 (UTC)[reply]
No, you've managed to get that across. Given the response rate so far, I don't think you need to worry about ALWAYS CURRENT ONLY. It looks like some version of "use both" is going up there. Darkfrog24 (talk) 12:51, 17 October 2015 (UTC)[reply]
For what it's worth... here is my prediction: This round will end with the compromise of "ALWAYS BOTH" - which will resolve the debate at most articles. However, it will NOT resolve the debate at all articles. The debate will continue at articles where it simply does not make sense to use both (where simple common sense would be to use just one or the other) and where we discover that using both is problematic (such as where using both will create a potential BLP issue)... and in a year or two we will have to re-re-visit the discussion with a narrower focus on these few problematic situations. At which point, we will eventually end up with some form of "IT DEPENDS - USUALLY WE SHOULD USE BOTH - BUT NOT ALWAYS". Blueboar (talk) 14:19, 17 October 2015 (UTC) [reply]
Hi Darkfrog24 and Blueboar
I more or less agree with both of you; both concerning a likely outcome of this VPP/RfC, and also the fact that there will be times when "USE BOTH" would actually be inappropriate.  But please keep in mind that the Manual of Style begins with the words:  "This guideline is a part of the English Wikipedia's Manual of Style. Use common sense in applying it; it will have occasional exceptions."  I really believe that that should cover most if not all of the exceptions that might occur if we end up with "ALWAYS BOTH."
Richard27182 (talk) 09:19, 18 October 2015 (UTC)[reply]
You can tell people "It's just a guideline" from noon to night but in my experience they still treat everything in it as a hard and fast rule. That's why we have to be so careful about what goes into it. Darkfrog24 (talk) 14:43, 18 October 2015 (UTC)[reply]
Ping:@Darkfrog24:
Understood.
Richard27182 (talk) 09:13, 19 October 2015 (UTC)[reply]
We actually did raise the issue of contacting transgender organizations (or at least transgender Wikipedians) when working out the wording of these two threads, but it was determined that the possible votestacking effect would outweigh the benefits of the insight that they could provide. At least one transgender Wikipedian has volunteered an opinion here anyway. Darkfrog24 (talk) 21:11, 15 October 2015 (UTC)[reply]

Was this not a formal RfC? Who/How/When is it going to be closed? -- TRPoD aka The Red Pen of Doom 03:35, 24 November 2015 (UTC)[reply]

It is a regular RfC, but thirty days have passed and the tag has timed out. Formal closure has been requested. Darkfrog24 (talk) 17:15, 24 November 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.

AfDs on newsworthy events

Of course, notability of horrific events can be shaky, especially when news may be primary proof of notability. However, AfD on 2015 Colorado Springs shootings will fail as did other AfDs. I don't know why people tend to nominate events that became notable when press has emphasized them. Can we limit number of these deletion nominations to reduce failures? --George Ho (talk) 06:36, 28 November 2015 (UTC)[reply]

Sadly, with the frequency that such shootings are occurring, it's becoming increasingly difficult to say that each one is notable. Risker (talk) 06:52, 28 November 2015 (UTC)[reply]
The news sources continue to give extensive coverage of each of them. That what notable means, the way we use it. Using Risker's formulation, I could equally say. that the way that such shootings are occurring, they are each of them becoming increasingly notable. They may not be unusual, but unusual is not the same aa notable. DGG ( talk ) 08:16, 28 November 2015 (UTC)[reply]
It is all too common for people to confuse "unusual" with "notable". In fact, things that are unusual may receive a lot of attention because they seldom happen, but things that often happen can also receive a lot of attention, and they too are notable. If mass shootings became so horrifically common that they no longer received much attention, then they might not need articles, but as long as they are getting extensive coverage, they certainly should have articles. Everyking (talk) 23:54, 28 November 2015 (UTC)[reply]
If only more people would read the guidance in WP:EVENT, especially Wikipedia:Notability (events)#Don't rush to delete articles. Fences&Windows 23:24, 28 November 2015 (UTC)[reply]
Wikipedia is not a newspaper. People that are interested in current events that have unclear notability should be writing these articles at Wikinews, and if it turns out to be an encyclopedically notable event (more than just a few days of coverage) then it can be transcluded into en.wiki. --MASEM (t) 23:57, 28 November 2015 (UTC)[reply]
This is about writing encyclopedia articles, not newspaper articles. Nobody is saying Wikipedia should be a newspaper. Everyking (talk) 00:42, 29 November 2015 (UTC)[reply]
People rush to create articles on any type of event like a shooting or a disaster (manmade or natural). Some are definitely of encyclopedic value, but many are not, but the rush to create this is treating WP as a newspaper. Wikinews is set up for those that want to write on current events; once they prove notable, they can be moved over. --MASEM (t) 00:47, 29 November 2015 (UTC)[reply]
Normally it's just people trying to improve the encyclopedia by writing about notable, encyclopedic subjects. Seldom do I see current event articles that are genuinely non-notable. Everyking (talk) 01:38, 29 November 2015 (UTC)[reply]
I see plenty, random crimes, random traffic accidents, random storms, random bombings/attacks in larger conflicts, etc. I'd guess that for every notable event, there's two non-notable event articles, based on what I've seen. Wikinews was set up for people that wanted to write about current events to work at, not Wikipedia. --MASEM (t) 20:24, 29 November 2015 (UTC)[reply]
I agree and think if we were really trying to treat Wikpedia as a newspaper we would get more articles about local sports teams and other local events such a traffic accidents etc. I also find that a large number of the aricles up for deletion on thee grounds usually do not last for the full seven days meaning that the majority does not appear to share this view.--65.94.253.102 (talk) 06:46, 29 November 2015 (UTC)[reply]
  • WP:NOTNEWS spends most of its text explaining the sort of content and style of Wikipedia articles, not the subjects of the articles themselves. That is, Wikipedia articles should have the content, tone, and style of an encyclopedia article. --Jayron32 17:45, 1 December 2015 (UTC)[reply]
I do not see random crimes , etc. I do see an attempt to include all bombings/attacks in larger conflicts and a great many murders. Whether this is appropriate content of not depends upon your view of the encycopedia. DGG ( talk ) 20:45, 1 December 2015 (UTC)[reply]
This is an example (please do not put it up for deletion) of what I'd call a random crime 2012 Seattle cafe shooting spree. Yes, people were killed, it was covered in national news, but that's it. It's a news story, with very little long tail or impact on the rest of the world, in contrast to 2013 Los Angeles International Airport shooting (also in which there was a death) which caused new legislation/regulations to be developed in following it. The latter has encyclopedic value because it impacted the world at large, the former does not, and should have been started at Wikinews first. Similarly 2013 Mahabubnagar bus accident should have been made at Wikinews first as this is not an encyclopedic topic without any larger impact on the world at large. People race to create these nowadays before a full understanding of the situation is at hand. --MASEM (t) 20:58, 1 December 2015 (UTC)[reply]
Exactly. We are turning into a news website, and not a very good one at that. We're stretching the bounds of notability much too far, and especially so in situations where articles are little more than quotefarms. - Sitush (talk) 06:13, 3 December 2015 (UTC)[reply]
I don't really frequent AfD, but my own viewpoint is similar: the bounds of notability have been stretched too far. There are other points peculiar to specific areas. I work often in WP:ARBPIA, and one major problem I see is that every terrorist incident is given its own article, divorced from context, almost wholly sourced to newspapers, or in passing mentions in books. They are basically WP:POVFORKs intended to demonstrate "X are terrorists". Some level of forking is healthy, I think, because it can emphasize some particular aspect of the topic. However, a lot of forking is essentially a way to get around stuff which should not be kept. Discussion in this area is polarized, so often leads to "no consensus", which defaults to "keep". This makes creating articles a favourite tactic of POV pushers. A separate but similar problem is that a lot of WP:BLPs in this area are basically attack articles. Kingsindian ♚ 06:37, 3 December 2015 (UTC)[reply]
That "no consensus" at AfD defaults to "keep" has long been a bugbear of mine but generally is a wider issue. You do, however, raise a very good point in terms of gaming the system in this specific context. - Sitush (talk) 06:49, 3 December 2015 (UTC)[reply]
  • To prove my point: The New York Times reports that there have been a minimum of 354 mass shootings so far this year in the United States.[5] We do not have articles on all of them; in fact, we have articles on relatively few of them. They're no longer automatically notable, and haven't been for some time. Just because something's been reported in (multiple) news media doesn't make it notable; we don't report on big traffic pile-ups routinely either, despite many people dying in them and their being reported in multiple MSM sources. Mass shootings are, in fact, daily occurrences not just in the United States but in many other countries; it is only our systemic bias that results in a number of American shootings being reported in Wikipedia, instead of the ones in Mexico, Venezuela, or most of Africa. Risker (talk) 05:16, 3 December 2015 (UTC)[reply]
    The solution to systemic bias is to create new articles on topics that deserve them rather than to delete otherwise quality articles. If reliable source material exists on an event in Mexico, it would be a Good Thing for Wikipedia to create such an article. We don't make Wikipedia better by arbitrarily deleting a worthwhile article on an event in the U.S. merely because "We've got enough American articles, thanks". --Jayron32 20:24, 3 December 2015 (UTC)[reply]
    The question is begged if these are "quality" articles. They can be well sourced because of MSM coverage, but one must keep in mind that most news reporting of this nature is primary sourcing, failing WP:NOT#NEWS, WP:N and WP:NEVENT. Some shootings do create significant debate - there's no question the encyclopedic-ness of the Sandy Hook shooting as it related to gun control discussion and the like. Most don't - they happen, there's a short tail and burst of news, and then events quiet down, with the long-tail impact only affecting the local area. Wikinews should be used by such interested editors to populate these events, and there's no reason on WP that we can't maintain lists of these notable shootings with links to Wikinews (the most recent case from yesterday proves there's an interest in how many shootings in the US occurred in the year, so a page to document that makes plenty of sense). But we definitely should not be having articles on every single one. --MASEM (t) 22:40, 3 December 2015 (UTC)[reply]
This point about the short tail and long tail is very important. People use the short tail to claim WP:DIVERSE, ignoring the fact that the long tail is only local. A related point is that WP:LASTING is rarely applied, and when used, is done inconsistently. There is an inherent tension between being up-to-date on recent events and applying WP:LASTING. Consider the following two AfDs, one delete/redirect, and one "no consensus" (both by the same closer, who, incidentally, I consider a fair and very good closer). Kingsindian ♚ 12:58, 4 December 2015 (UTC)[reply]
How "long" does the "long tail" need to be? The problem with WP:LASTING is that while it is a very good criteria for determining whether an event is notable... it does not always work the other way around... it is a very poor criteria for determining whether an event is non-notable. There are lots of events that are considered notable and yet don't pass WP:LASTING.
As an example... consider the University of Florida Taser incident of 2007. There is no question that this was a notable (or at least note-worthy) news event back when it occurred. It engendered all sorts of discussions about free speech and the appropriate (vs inappropriate) use of tasers. But... the event was not "the catalyst for anything of lasting significance". Today the event is all but forgotten. It had no lasting impact on society. No laws were passed due to the event. Nothing changed because of the event. Even the pop-culture fad for quoting "Don't tase me, Bro!" has faded. In other words, I don't think passes WP:LASTING). Yet, I would hesitate to say that the event was completely non-notable. I think it is worth a stand-alone article. (That article may need to be rewritten... but I think an article should exist). Blueboar (talk) 14:38, 4 December 2015 (UTC)[reply]
The taser incident has a reasonably long enough tail that it's clearly an encyclopedic topic; note that there were issues raised on the campus's security, and free speech aspects. Stuff has change, even if it really is only the fact "don't tase me bro" is a meme the only linger effect of that. The long tail doesn't need to be a permanent impact, but it needs to be more than just affecting the people directly involved with the incident and close friends and family, and others local to it, and more than just the first few days of news coverage. --MASEM (t) 14:50, 4 December 2015 (UTC)[reply]
There are lots of events that are considered notable and yet don't pass WP:LASTING. Leaving aside the fact that perhaps this article did pass WP:LASTING, there is no contradiction between this statement and mine. WP:LASTING is only one of the criteria for notability, it is neither necessary nor sufficient. And you haven't really given an argument about why you think the article is notable, other than your opinion. Maybe it is, maybe it isn't, but as they say: "show your work". Secondly "how long does a long tail need to be" cannot be answered. Such questions are inherently subjective and dependent on context. Again, one needs to "show their work". My point is that this is rarely, if ever done. Kingsindian ♚ 15:45, 4 December 2015 (UTC)[reply]
I think what Blueboar was getting at is that if one took LASTING to the letter, then if news sources die out about an event after much time as past, such as the assassination of JFK (for an example), then one could argue that that event is no longer notable, which of course is silly to think of for this or any example; by nature, coverage of an event will diminish over time. But as you do state, LASTING is but one piece. More importantly, to me, is taking in how that tail is relative to the timeframe's news cycle (in the 21st century, this would be 1 to 2 days, but if we talk about the early 20th century that could easily be a week or more); if the story reported today dies out in a day or two, its notability is begged by LASTING, but if that dies down after a week, it's probably notable. This is why we need to encourage more people to use Wikinews. Stories that fail LASTING here would have zero difficulty existing at Wikinews from the start, and if it does turn out the story lasts longer than a few days (an example for myself was the mess over the shooting of Cecil the lion which I thought was more a run-of-the-mill human interest story), then we can transcribe into en.wiki. --MASEM (t) 16:37, 4 December 2015 (UTC)[reply]
I am confused by the reference to the JFK assassination. Of course WP:LASTING does not state that the coverage has to be in newspapers. There have been books written about the JFK assassination, studying it in depth, and of course there are a thousand conspiracy theories, and then there are books studying the conspiracy theories. It would definitely pass WP:LASTING however you read it. Regarding the latter point, I am pretty cynical that the people that I'm talking about (no names) will be satisfied by Wikinews. They want their article on Wikipedia, because whenever anyone Googles the term, it would come up. And I know their motives for doing this. I don't think Wikinews has that sort of search engine ranking (correct me if I'm wrong). Kingsindian ♚ 16:53, 4 December 2015 (UTC)[reply]
What I am saying is that if one took an extremely narrow view of LASTING, then the fact that today, right this moment, there are no sources that were published today discussing the JFK assassination means that LASTING is failed and we should delete it. Which of course is not going to happen for reasons you state. Now taking that same logic to the Taser example, again there are no sources right this instant, published today, that are discussing it, and the same logic applies if one was being narrow on what LASTING meant. My point is that a news story disappearing off the radar, alone, is not sufficient for determining if LASTING applies. It's how long that tail was relative to the time of the event, not whether there's continued coverage indefinitely. Further, just because there may be sources published today talking about an event does not necessarily meant the long tail of a story is sufficient to meet LASTING; I give examples of local crimes that end up in the death of innocent victims, where local news will often cover the family's grief year after years as part of a human interest angle. If the story came and went in the news, and this type of coverage is the only long tail, that's not meeting LASTING. --MASEM (t) 17:01, 4 December 2015 (UTC)[reply]

[unindent] The problem is that most people have no clue what primary sources are, and they throw a fit when their votes are ignored by an admin who follows the note-a-vote standards and ignores AFD votes that rely on primary sources, such as news reports about an incident, in determining whether a topic is notable. I tried enforcing WP:PRIMARY one time when closing an AFD (either it was a recent incident that had just happened, or it was a person who hadn't been getting any coverage except for news reports that were published at the time of an incident in which the person was involved), but a pile of Randies filed a deletion review because it was a "new and idiosyncratic idea" (or something synonymous) to consider news reports from the time of an event to be primary sources. Policy is clear that we should ignore AFD votes that have no basis in reality and that primary sources don't count toward notability, and in the context of history (the context in which event and biographical articles exist), news reports and other documents from the time of an event are unambiguously primary sources, so policy already says that we should ignore these votes, but if you don't know that and you reject it when it's explained to you, you're going to throw a fit if current policy is followed. It's past time to add a clarification to policy, something saying basically "Because news reports from the time of an event are primary sources for that event, they cannot count toward notability; notability depends on the existence of secondary sources, those that examine primary sources and were published after the context in which the primary sources were produced. Articles about events, individuals, and other subjects may only be retained if secondary sources are furnished to support the article, unless consensus specifically holds that an individual article should be considered exceptional". For three prominent situations (the Colorado Springs murders, to the San Bernardino shootings, and to the Paris attacks), news reports are still appearing: unless someone can provide convincing WP:IAR arguments, we have no business having articles on any of them at this moment. Nyttend (talk) 20:13, 9 December 2015 (UTC)[reply]

If you think the article on the Paris attacks deserves deletion, an article which has been praised by mainstream journalists, then you are very far out of step with the consensus on event articles. News articles are not usually considered to be primary sources, and wikilawyering as such when closing deserved to be overturned. Fences&Windows 02:17, 11 December 2015 (UTC)[reply]
Out of step, yes, because most of the people who vote on these things don't know what they're talking about. The concept of a news article about a just-happened event is a perfect example of what's given in the first sentence of WP:FRINGE, an idea that departs significantly from the prevailing views or mainstream views in its particular field. History universally employs the term to refer to documents created at the time of an event and documents representing the memories and perspectives of people who experienced those events; see [6], the history section of [7], and [8]. There is scholarly consensus that documents created at the time of an event are primary sources, so don't push an alternate POV. Nyttend (talk) 03:07, 11 December 2015 (UTC)[reply]
I definitely agree that news articles are primary sources for the most part. However, there is no requirement that an article only rely on secondary sources. I already mentioned above that there is an inherent tension between covering up-to-date events and lasting encyclopedic significance. That is not going away anytime soon. That said, there is no doubt at all that the Paris attacks will have lasting significance (arguably they already have). There is no automatic way to determine such things for general events; it is inherently subjective. However, subjective does not mean arbitrary: one must argue one's case. Kingsindian  ♚ 03:52, 11 December 2015 (UTC)[reply]
  • The problem with GNG is not that editors do not understand what a primary source is, but that GNG fails to consider them. You can write a perfectly good article with primary sources (provided you know how to handle them, though that isn't much of an argument as many editors don't know how to handle secondary sources either). To complain about the proverbial "Randy from Boise" misunderstanding GNG is sheer nonsense, because GNG was created by ... the proverbial "Randy from Boise"! It has the problems it does because it was self invented by a bunch of nonentities on the internet who did not really know how to write an encyclopedia. Its purported definition of "notability" is pure unadulterated unreliable 'original research' that is probably wrong. James500 (talk) 06:58, 11 December 2015 (UTC)[reply]

I started the discussion as hopes to limit the number of failing AfD nominations. With all the discussion, apparently we can't limit number of deletion nominations. In fact, interpretation of news articles vary, but they are considered primary sources usually. In other words, there's nothing we can do? Right, James, Nyttend, Kingsindian, and Masem? Are we gonna sit by and let failing AfD nominations on newsworthy events increase? George Ho (talk) 05:39, 15 December 2015 (UTC)[reply]

There's nothing to do. We don't preemptively protect new pages so we can't really know which new page on which news event should be protected against being listed for deletion. Once it's listed, speedy keeps are relatively common (although sometimes it's not that easy right away) and once that's done, we can shut off the AFD listing and move on. For pretty much every new article, there's at least one person out there who thinks it should be deleted for the most part and we won't change the whole project to stop them. -- Ricky81682 (talk) 05:47, 15 December 2015 (UTC)[reply]
What needs to be done is to uphold WP:NOT#NEWS better at AFD and have better clarity on how most things that happen in the news are not encyclopedic and fail GNG/NEVENT (starting on the fact that the bulk of newspaper reports on breaking events are primary and thus not sufficient for notability), and encourage editors that want to write on current events to use Wikinews, which gives us the possibility of moving a story that may not immediately seem notable into Wikipedia mainspace when it turns out to be notable. --MASEM (t) 22:45, 15 December 2015 (UTC)[reply]
Are journalistic skills required for Wikinews? George Ho (talk) 03:59, 16 December 2015 (UTC)[reply]

Deaths in month, Deaths in year: (enforced non)compliance with Wikipedia citation standards

If this is not the correct place for this discussion, please suggest where it should be.

Articles on "Deaths in (year)" and "Deaths in (month) (year)" have substantial noncompliance with WP:CITEHOW, which says

Citations for World Wide Web pages typically include:
  • URL of the webpage – that is the URL of the webpage where the referenced content can be found, not, e.g., the main page of a website when the content is on a subpage of that website (see Wikipedia:Shallow references)
  • name of the author(s)
  • title of the article within quotation marks
  • title or domain name of the website
  • publisher, if known
  • date of publication
  • page number(s) (if applicable)
  • the date you retrieved (or accessed) the webpage (required if the publication date is unknown)

Recommendations for news citations are similar. This section of Wikipedia:Citing sources does not offer any category, group, or type of article where these typical components of citations should not be used.

The current article, Deaths in 2015, which has entries for deaths only for the current month of December 2015, instructs editors in the top comment section:

References should be in<ref>[url & title]</ref> format, as full citations make the page too slow to load, and too big to edit.

If this instruction, or any similar instruction elsewhere in Wikipedia, is allowed to remain, I believe that WP:CITEHOW should specifically note any and all such exceptions.

I believe this instruction should be removed (pursuant to a proper decision-making process in the appropriate forum). I believe that the author name, publication name, and publication date, among other items, are useful for a number of purposes, including tracking URL changes, finding archive URLs, and assessing the reliability of sources. I believe that "full citations make the page too slow to load, and too big to edit" is utterly without merit. For example, I recently edited Deaths in March 2012 to include full reference info for most incomplete references, and this increased the article size by 5,463 bytes, to 153,940 bytes. It is ludicrous to argue that a 153,940-byte article is too big to edit, but a 148,477-byte article is not to big to edit. Of course, the article already had a significant number of full references, but still.

For the past, there are articles by year starting with Deaths in 1995 and ending with Deaths in 2003. After that, there are articles by month starting with Deaths in January 2004. Only the current article includes the instruction for providing stripped references. On the 7th day of each month, the article for the preceding month is launched by extracting that month's info from the current article. (At year-end, it's slightly different but similar.) Thus, each "Deaths in (month) (year)" article is initially loaded up with only stripped references, and most editors follow the existing pattern of stripped references. Over time, some editors insert non-stripped reference information that should have been there all along, and would be much easier to create if the comment were removed and editors followed the instructions of WP:CITEHOW in the first place.

(For Deaths in October 2011 and older, instead of using footnote references, most or all of the references are inline external links. These should be converted to normal footnote references. Before mid-2005, most entries don't have even inline external links. These articles should be brought into compliance over time with a full reference for every entry, but that is beyond the scope of this discussion.) —Anomalocaris (talk) 08:37, 13 December 2015 (UTC)[reply]

Just a bit of background: the current state of affairs is a compromise arrived at following a 2012 RfC about the use of inline external links vs. full references. I do think the time is ripe for another discussion on the subject. Personally, I agree with the OP; no-one should be enforcing the use of incomplete references in any area of the 'Pedia, and the size argument is pretty silly. DoctorKubla (talk) 12:07, 13 December 2015 (UTC)[reply]
  • WP is a collaborative project. If you think the citations in these articles need to be fixed... don't just sit back and complain, (expecting someone else to take care of it)... step up, and WP:FIXTHEPROBLEM yourself. Blueboar (talk) 14:32, 13 December 2015 (UTC)[reply]
Blueboar: I have already worked on Deaths in March 2012, Deaths in February 2012, ‎Deaths in September 2012, and Deaths in December 2011, but the full project of repairing all such articles is quite large, and this is all beside the point. The main point is that the unlawful compromise needs to be replaced, the instruction in the current article needs to be removed, and editors should be expected to follow WP:CITEHOW. —Anomalocaris (talk) 17:17, 13 December 2015 (UTC)[reply]
Please note that the concept of an "unlawful compromise" does NOT exist at Wikipedia, because two of the most important bedrock rules governing Wikipedia are WP:CONSENSUS and WP:IAR. That doesn't mean that the we shouldn't decide to change the process and make the links proper references, but the reason we should do that has nothing to do with the process that came up with the current system. The process that put in the current system for the "Deaths in..." articles was perfectly valid, and the same process will be used to change it to something else. --Jayron32 16:25, 14 December 2015 (UTC)[reply]
@Anomalocaris: Rather than removing the current instructions, I would opt for the additional instructions being included along with them, perhaps as optional: for example, being included on all references on articles where this seemed more appropriate, and not being included on articles where the page length is already a cause for concern, but only if there is substantial evidence that the page is taking too long to load. I'm not an expert on this, though. Rubbish computer (Merry Christmas!: ...And a Happy New Year!) 00:38, 14 December 2015 (UTC)[reply]

RfC: SVG as appropriate format for non-free files?

Neutral

Does SVG file format qualify as "fair use" and meet the non-free content criteria? Why or why not? If not, how will this affect all non-free files in SVG format? --George Ho (talk) 00:04, 14 December 2015 (UTC)[reply]

Non-neutral

WP:IUP says not to use "px" as "px" will force a fixed size on all users who prefer to view images at any size. With SVG, an image becomes big at 400px, prompting other users to use the "px". Even with good faith, this violates the policy and a user's freewill to choose any size that he or she wants. File:2015 Climate Conference.svg is used as an infobox image for 2015 United Nations Climate Change Conference. The image was very big at SVG format, so someone else shrank the image to 240px, forcing readers preferring 220px to view it bigger than 220px. I tried FFD, but David Levy found the forum inappropriate. The SVG format has been discussed in the past elsewhere, but there has been not a consensus to disqualify it as fair use. I am trying my best to let anybody pick any size, but "px" is still used. The same goes for File:Icarly logo.svg, which replaced File:Icarly-logo-2.png. I eliminated the px from iCarly, resulting in a bigger size. Even reducing the size of the SVG file is proven ineffective as PNG is still used to provide whatever size a user prefers, including 400px. --George Ho (talk) 00:04, 14 December 2015 (UTC)[reply]

  • The only acceptable use of a non-free SVG file is for logos and other similar identifications, iff the SVG is something publicly available by the entity the logo represents (either as the SVG directly or a format like PDF that the SVG can be pulled from). Any other use of SVG (particularly user-made ones) violates NFCC#3 as well as potentially NFCC#4 (not previously published). We discourage users from trying to recreate copyrighted logos as SVG to avoid the complexities of copyright law as applied to both the graphic image and the underlying SVG (XML) code. --MASEM (t) 00:18, 14 December 2015 (UTC)[reply]
  • Sigh, why does it seem like this comes up over and over and over? Pixel size doesn't make any sense for vector images, the relevant thing is level of detail: eliminate detail that is not necessary to render at an appropriately-limited size. No other stupid limitations. Anomie 00:21, 14 December 2015 (UTC)[reply]
What do you mean, Anomie? What are "Details", and how do they matter? Pixels are all I can think about, and nothing more. George Ho (talk) 00:24, 14 December 2015 (UTC)[reply]
I looked for past discussion, and I found this one near the top of my search. And to my surprise, George Ho, I see you commented there. So why exactly are you bringing this up again? Anomie 00:33, 14 December 2015 (UTC)[reply]
Shall I answer? I won't do that without you answering my question. George Ho (talk) 00:37, 14 December 2015 (UTC)[reply]
Feel free to re-read the points in the old discussion. I'm not feeling like dealing with feigned ignorance tonight. Anomie 00:44, 14 December 2015 (UTC)[reply]
  • Ok, so why not just use |upright = [x] where [x] = a proportional value of the screen size? Seriously, they made a work around for this type of problem ages ago. Cheers, Drcrazy102 (talk) 00:51, 14 December 2015 (UTC)[reply]
Template:Infobox event already does that, Drcrazy102. 100% (upright=1) = 400px at preference. Or "thumb" or "frameless" already does the job. We must consider also the layout of the article content. --George Ho (talk) 00:55, 14 December 2015 (UTC)[reply]
Almost forgot, if I reduce the scale to .5 (50%), the image will become too small for those preferring default or smaller size. If I increase to 1.35, the image will become too big for those preferring the maximum size. George Ho (talk) 01:03, 14 December 2015 (UTC)[reply]
  • Aside from the NFCC#4 issue I do think that NFCC#3 is really a limit to how much material we use. It's fairly clear here that mere pixelsize is not a good measure (also as has been noted, using a modified SVG file creates other issues with NFCC#4, NFCC#8 since you may be misrepresenting the logo - which is what nonfree SVGs frequently are - and NFCC#1/FREER because of complicated copyright status), so coming up with another standard seems like the right call, for me. Jo-Jo Eumerus (talk, contributions) 06:45, 14 December 2015 (UTC)[reply]
    • Right. An SVG file is not just a logo but a logo combined with some computer code, and the computer code may be separately copyrighted, requiring a licence from the author of the computer code per WP:FREER. --Stefan2 (talk) 18:41, 14 December 2015 (UTC)[reply]
  • Anomie is right in assessing that the level of detail (number of elements defined in the SVG file) is more relevant than rendered pixel size. WP:NFCC#3b talks about numerous standards for measuring minimal use ("Low- rather than high-resolution/fidelity/bit rate") and we should not assume that pixel size is the one that corresponds best with SVGs.
I also disagree with admin David Levy's interpretation that FFD is not forum for non-free SVG files because "the concern expressed ... applies to every non-free SVG file". The concern expressed in my opinion was compliance with WP:NFCC#3b, and given the complicated nature of this in SVG files (as demonstrated) it's definitely something that should be discussed in FFD rather than dismissing it as something self-evident. Finnusertop (talk | guestbook | contribs) 07:02, 14 December 2015 (UTC)[reply]
I wasn't suggesting that FfD is never the appropriate forum in which to discuss non-free SVG files. George's rationale was that use of the SVG format was the problem. ("I believe that the format is too superior to make the use 'fair'. Shall we use the PNG format instead?")
Regarding Anomie's comment, I agree as well (assuming that non-free SVGs remain in use at Wikipedia). I've edited File:2015 Climate Conference.svg to reduce the level of detail. —David Levy 17:26, 14 December 2015 (UTC)[reply]
You also need to consider the rationales given by other participants in the discussion. I was specifically discussing the detail of the vector elements. --Stefan2 (talk) 18:36, 14 December 2015 (UTC)[reply]
My apologies if the closure came across as a dismissal of that concern. It's quite valid, of course, but it doesn't necessitate an FfD listing; users can simply perform detail reductions as needed and transclude the {{orphaned non-free revisions}} tag. George has done so with raster images, in fact. He simply misunderstood the SVG format's nature and didn't realize that something equivalent was possible, leading him to believe that the only solution was to use a PNG file instead. (Had the extent of his confusion been apparent at the time of the closure, I'd have noted this therein.) —David Levy 18:58, 14 December 2015 (UTC)[reply]
What "something equivalent", David? If not PNG, what else then? --George Ho (talk) 04:37, 15 December 2015 (UTC)[reply]
I was referring to the act of modifying an SVG to reduce its level of detail. —David Levy 10:31, 15 December 2015 (UTC)[reply]
Even an "inferior" SVG file might not qualify as fair use and/or meet NFCC. You can still trasclude an image at any size unless you force the size. George Ho (talk) 23:51, 16 December 2015 (UTC)[reply]
Your comprehension of this subject remains inadequate, despite multiple explanations and follow-ups thereto. This seems unlikely to change. —David Levy 01:16, 17 December 2015 (UTC)[reply]
  • I think that George Ho misunderstands the file size requirement. The rule, per WP:NFCC#3b, is that a file shouldn't be too big, and what constitutes 'too big' depends on the file. An image contains a level of detail, which can be reduced. If the file is a bitmap file, then the level of detail will typically be reduced if you remove some pixels. If the file is an SVG file, then the default pixel count is just a number on a line in the source code, and changing this number doesn't remove or add any information. An SVG file contains geometrical elements such as lines, circles and rectangles, and if you remove or replace some geometrical elements, then the size will sometimes change. A rectangle can either be coded as a rectangle or as four lines, and switching from one variant to the other will not change the size of the file, but modifications to the vector elements sometimes changes the file size. Unfortunately, it is currently not trivial to determine if an SVG file fails WP:NFCC#3b or not as most discussions about size requirements have been about bitmap images.
If a non-free file is in violation of WP:NFCC#3b, then the file needs to be deleted or replaced by a different file which is smaller. The smaller can either be in the same file format or in a different file format, i.e. we could reduce PNG→SVG or SVG→PNG if the user reducing the file finds it more convenient to change the file format while reducing the file. --Stefan2 (talk) 18:36, 14 December 2015 (UTC)[reply]
I don't mind details. If the detail is high-quality, I don't mind as long as the format is PNG. Actually, a low-detailed SVG is not as good as high-quality PNG extracted from high-quality SVG. But if pixels is not a significant thing, how can you explain infobox's various transclusion of a file? --George Ho (talk) 00:03, 15 December 2015 (UTC)[reply]
You're failing to distinguish between the pixel size of the image rendered within an infobox and that of the file from which MediaWiki derives it. In the SVG format's case, the latter does not exist. —David Levy 10:31, 15 December 2015 (UTC)[reply]
From what does MediaWiki derive? Also, shrinking the image doesn't make the file format a fair use, does it? George Ho (talk) 23:49, 16 December 2015 (UTC)[reply]
Given the apparent impossibility to write a response to one of your questions that you don't misunderstand fundamentally, I lack the patience to continue trying. —David Levy 01:16, 17 December 2015 (UTC)[reply]
  • question I don't work with images, so this may be a stupid question, but What is there special about this articular file format that makes it more likely to be a violation than other file formats? I would have thought copyright problems are about the nature of the image itself, not the format in which it is captured. DGG ( talk ) 01:13, 15 December 2015 (UTC)[reply]
    • One problem with SVG is that at its nature it is a human readable XML file, effectively programming code. And case law is not strong on where the line is drawn on creativity in code, and creativity in what the code produces. The latter clearly has the potential for copyright protection, but since one generally uses a mechanistic process to take SVG and render it, the question is begged if the SVG itself is different from the image, or a novel work on its own. There is no good answer to this question but it does raise the potential of having two different copyrights involved (the image, and the person that "coded" the image) and that makes it even more a naunse for non-free if these are two different copyright holders. It is assumed that an SVG submitted and self-created by an editor under CC-BY has none of those issues. --MASEM (t) 01:23, 15 December 2015 (UTC)[reply]
    • @DGG: The most important difference between svg and the other file formats uploadable at Wikipedia is that the former is losslessly scalable to any size.Take a png or jpeg uploaded to Wikipedia at a typical resolution of 150x150 pixels and try to print it on a mug or T-shirt or 100-foot-wide banner and you get a pixellated mess. Do the same with a svg and there's no loss of quality. This image from SVG shows the issue nicely, especially if you render it at, say, 3000 pixels wide. —Cryptic 02:10, 18 December 2015 (UTC)[reply]
I think you;re saying that it would make it facilitate making a copy that would not be fair use. But our responsibility is only to accurately give the copyright status. Any non-PD file here or in Commons, whether fair use or CC:3 SA, can be used in violation of copyright by not making attribution. The proper use of our material is the responsibility of the reuser. DGG ( talk ) 05:41, 18 December 2015 (UTC)[reply]
  • According to WP:IUP#Format, "The SVG is dynamically rendered as a PNG at a given size when inserted into an article." How would removing some details make the use still "fair"? Is the image still the same or different at 400px-PNG with reduced detail? I don't want to hear whether it's still the same at 220px or 200px. --George Ho (talk) 06:09, 17 December 2015 (UTC)[reply]
    • A file with pixels does not necessarily contain less copyrighted material than a file with pixels. Bitmap files usually contain more information if the pixel count is higher, but there are exceptions. It all depends on what the files contain. --Stefan2 (talk) 15:25, 17 December 2015 (UTC)[reply]
      • Such as? How would details affect the transclusion of images in infoboxes? --George Ho (talk) 17:45, 17 December 2015 (UTC)[reply]

Password security RfC at meta

There is currently an RfC at meta to increase password length to 8 characters and prevent common passwords being used for accounts which can edit the MediaWiki: namespace and who are covered by the nonpublic information policy (CheckUsers and Oversighters) - meta:Requests for comment/Password policy for users with certain advanced permissions. Callanecc (talk • contribs • logs) 00:24, 14 December 2015 (UTC)[reply]

Tagging draft articles

Policy question. Should WikiProject tags be removed from an draft if it's been rejected by AFC? I've having an argument with MPJ-DK who keeps removing tags from Draft talk:TASW Cruiserweight Championship and others because the submission has been declined. To me, declined isn't the end of the article and it seems odd. The project won't be notified if the draft gets taken to MFD or moved to articlespace or whatever (or it has to be retagged). I started tagging these once it was considered a bug that people didn't automatically inform when the articles didn't have a project tag so it seems there's complaints if you do and complaints if you don't. -- Ricky81682 (talk) 01:35, 15 December 2015 (UTC)[reply]

They don't need to be tagged, but if a project tags them, then they shouldn't be untagged. The talk page can disappear when the draft is deleted. Graeme Bartlett (talk) 02:19, 15 December 2015 (UTC)[reply]
three ofbthe four untagged will never be article as they were 1) an article that already exsts, 2) a cruft list of video game characters and an article on a team that existed for 10 days. None would survive and AFD. Why tag that.stuff? Fourth one is an AFD nom that was rejcted 3 months ago notability and nothing was done. Why tag old junk? If it had potential i could see it be tagged. MPJ-US  05:15, 15 December 2015 (UTC)[reply]
Ok, fine, but if someone makes it into an article, then it'll be re-tagged later. Seems like you're wasting a lot of more time removing the tags (including from the video games project as well) than me tagging them when they start. If you don't think they should be there, just list them for deletion. How does removing the tag and letting them sit around forever help? -- Ricky81682 (talk) 05:24, 15 December 2015 (UTC)[reply]

Userboxes migration

How did the userboxes migration change anything? Users can still add userboxes relating to personal views and beliefs (that do not make Wikipedia unsafe). In other words, what I am asking is how does being in the user namespace rather than the main namespace make any difference? 76.176.28.235 (talk) 07:12, 15 December 2015 (UTC)[reply]

Well they used to be in the template space not main namespace but I don't see much of a difference. There's some userboxes that show up at MFD under WP:POLEMIC for what it's worth. I think User:UBX is being used to host a number of those pages so there's a consistent place for them. -- Ricky81682 (talk) 07:19, 15 December 2015 (UTC)[reply]

RFC: Allow stewards and global admins to help with countervandalism

The following discussion is an archived record of a request for comment. Please do not modify it. No further edits should be made to this discussion. A summary of the conclusions reached follows.
User withdrew RFC. --Izno (talk) 18:25, 18 December 2015 (UTC)[reply]

Withdrawn - I think it is clear which direction the discussion is going. I withdraw the proposal. -- Taketa (talk) 18:19, 18 December 2015 (UTC)[reply]

Topic: Allow stewards and global admins to help with countervandalism

Dear all,

At the talk page of WP:RFA Biblioworm asked for ideas on how to lighten the load on admins. This as a follow up of the Phase I RfC for the RFA2015 reform project, which showed community consensus that we should somehow try to lighten the load on admins. I made a suggestion and a bureaucrat indicated that it was an interesting idea, but it needed to be developed and put forward at a different venue. As such, I would like to ask you for feedback on my proposal below.

I suggest we allow stewards and global admins to help with blocking straight forward vandalism (ip, logged in vandal) and let them delete obvious spam pages. The users are trusted and experienced with this type of work. Letting stewards delete obvious pages is already policy on meta and works fine for the local admins. Among the global-admins are the most active and experienced vandal fighters in the world. Such a change would represent a significant increase in vandal fighting admins and take away a huge load. Moreover it would give en.wiki experience to the global users, who might afterwards become more active here or even apply for adminship here and help the English Wikipedia even more. It is a win-win situation.

I would greatly appricate your input. What do you think. Do we want this. If yes, how can we make this proposal more specific. What checks do we need. Issues to consider. Would the policy on meta be applicable? How to proceed. Thank you very much.

Sincerely, Taketa (talk) 08:12, 15 December 2015 (UTC)[reply]

As a matter of clarification, this is a proposal to change Wikipedia:Global rights policy#Stewards, yes? meta:Stewards policy refers to that page.Jo-Jo Eumerus (talk, contributions) 10:52, 15 December 2015 (UTC)[reply]
Good point. Yes the proposal would result in changing that section and also Wikipedia:Global rights policy#Global sysops. Sincerely, Taketa (talk) 11:28, 15 December 2015 (UTC)[reply]
And removing enwiki from meta:Special:WikiSets/7 if the bit about global sysops passes, I guess.Jo-Jo Eumerus (talk, contributions) 12:28, 15 December 2015 (UTC)[reply]
Yes. If we make the suggested changes to the global rights policy, this would be part of the technical implementation. Taketa (talk) 12:42, 15 December 2015 (UTC)[reply]
  • I think this arrangement could work; we already have stewards and global renamers working at WP:CHUS, so the arrangement is not without precedent. –xenotalk 11:41, 15 December 2015 (UTC)[reply]
      • Support - While I certainly wouldn't want them entering most of our admin areas of work (this should be done by someone who is familiar with the way things work on English Wikipedia), I think that Stewards and Global sysops should be able to recognize obvious vandalism and spam; and our warning system is simple enough to understand what's going on. This would reduce the work load on our admins, leaving them more available to handle tasks where a higher level of understanding our community is required (banned users, XFDs, edit wars etc.) עוד מישהו Od Mishehu 11:55, 15 December 2015 (UTC)[reply]
  • Support – setting such a narrow limit for stewards and global sysops w.r.t. enwiki counter vandalism work should be fairly harmless. sst✈(discuss) 14:06, 15 December 2015 (UTC)[reply]
  • Here's my loaded response:
Oppose/Moot (Please see my comment below on why this is actually "moot". Steel1943 (talk) 18:05, 15 December 2015 (UTC)) allowing global admins access to the basic admin tools on the English Wikipedia (removing this Wikipedia from meta:Special:WikiSets/7) for a couple of reasons. I say this due to lack of usefulness and "lack of local consensus". I fail to see how a group of only 18 editors would be able to help with the load in the least, given their very small number. Also, access to the administrative tools should be provided to an editor via consensus by the local Wikimedia project: this proposal contradicts that precedence, and it's not one that we should start. Lastly, the discussions for global admin "RFAs" do not seem to be advertised globally, so how is this local Wikimedia project supposed to be able to know about the nomination so they can support or oppose the candidacy? And;[reply]
Support allowing stewards access to the admin tools since their appointment process is more rigorous than our local Arbitration committee elections, so thus the worldwide trust is the equivalent of being on ArbCom, so might as well. Also, steward nominations are advertised globally, so all participants on all Wikimedia projects, including this one, are given ample notification about steward elections. (In other words, the members of the English Wikipedia cannot adequately say "I did not know about it" when there are notifications about the elections placed at several locations, including the watchlist.)
Steel1943 (talk) 17:28, 15 December 2015 (UTC)[reply]
Dear Steel1943, the global sysops are a small group indeed. However as described on Wikipedia talk:Requests for adminship#Easing the load on admins, only 3 admins did half of the last 500 deletions on enwiki. If you add 18 highly active people, and let them deal with vandalism, imagine the amount they can do. For example MoiraMoira on her own did over 1000 admin actions in the last month. You point out that stewards are to have consensus and global sysops not. However global sysops are elected by the global community as well. Everyone on enwiki can vote during their election. They work as admin on hundreds of projects. Ofcourse I fully understand the notification explanation, there is a sliding scale, and I accept your views. Do you really need everyone involved, everytime someone is appointed I wonder. We trust the old admins we never voted on. We trust subgroups to make guidelines. We have the oportunity to get involved if we wish. Is this not enough? The people who currently rename account on enwiki, global renamers, which used to be trusted only to bureaucrats (on 1 project where they do it on 800) are appointed the same way. Sincerely, Taketa (talk) 17:52, 15 December 2015 (UTC)[reply]
@Taketa: Actually, your proposal to specifically give "global admins" admin privileges of this Wikipedia is may actually be (text in italics added – Steel1943 (talk) 18:39, 15 December 2015 (UTC)) moot anyways. I'll explain below. Steel1943 (talk) 18:05, 15 December 2015 (UTC)[reply]
  • (edit conflict) As it turns out, giving global admins administrative privileges on the English Wikipedia is may actually be (text in italics added – Steel1943 (talk) 18:39, 15 December 2015 (UTC)) moot. Per Meta:Global sysops#Scope:[reply]

    By default, global sysops may use this global user group's permissions on wikis that meet one or both of the following criteria:

    * fewer than ten administrators exist; or
    * fewer than three administrators have made a logged action within the past two months.

    ...The English Wikipedia has more that 1000 administrators, and a lot more that three perform administrative actions on a daily basis. With that being said, this proposal in regards to global admins is truly "moot" since it contradicts global policy. – Steel1943 (talk) 18:05, 15 December 2015 (UTC)[reply]
    Um, that policy continues with "Projects may opt-in or opt-out at their own discretion if they obtain local consensus." The prior section just enumerates the default stance ("By default...").Jo-Jo Eumerus (talk, contributions) 18:11, 15 December 2015 (UTC)[reply]
  • The way I read it, the purpose of global admins is to help manage a new Wikimedia project until the project establishes its own guidelines and procedures for appointing administrators. I agree with this specifically being the purpose of that group (thus why I read it and established a "moot" stance, but it is also why I oppose letting the group have local admin rights to this project, and would for any project that has surpassed the default criteria.) Steel1943 (talk) 18:15, 15 December 2015 (UTC)[reply]
    Global policy says that "by default" it is implemented on those wikis, and all wikis can "opt-in or opt-out". We can ask them to help if we want to. That is the question, do we want to. The English Wikipedia has 600 active administrators. Consensus is that we should do something to lighten the load for these admins. Adding 18 active people does something. It is more then we had new admins in the past half year. Ofcourse, you are free to your opinion and I will leave it at this. Sincerely, Taketa (talk) 18:21, 15 December 2015 (UTC)[reply]
Allowing this Wikimedia project to be removed from the global admin opt-out list is like saying that the list of administrators local to this project are not able to handle the load of administrative work local to this project, and need outside help. That sends a negative message to our assumptions of our own administrators' capacities. Issues with the abilities of local administrators to do their locally-appointed tasks should be taken by either desysopping the ones we got (usually via WP:ANI) or nominating and appointing aspiring new local admins (via WP:RFA.) Allowing "outside help" to participate here has the potential to deter possible future local administrators from running due to the lack of being able to show proof for their worth due to a lack of a need for such tasks. Thus, this is my opinion. Steel1943 (talk) 18:30, 15 December 2015 (UTC)[reply]
  • Oppose The global admins and stewards have better work to do than bail out the lazy admins here at en-wp. That a handful of admins here have been managing the vandal problem is proof that RfA isn't selecting users that actually intend to wield a mop. Chris Troutman (talk) 18:40, 15 December 2015 (UTC)[reply]
  • Oppose These people have not been chosen to do the proposed job, and would not have volunteered on the basis of doing counter vandalism work on en.wikipedia. If you want to nominate any for an admin here, you can see if they are willing and if people here want them for that job. Graeme Bartlett (talk) 21:02, 15 December 2015 (UTC)[reply]
  • Oppose Good governance tends to require segregation of duties rather than omnipotence. Andrew D. (talk) 00:13, 16 December 2015 (UTC)[reply]
  • Oppose The solution to "lighten the load on admins" is more admins. If stewards or global admins want to do that, they can head over to RFA. Prodego talk 01:51, 16 December 2015 (UTC)[reply]
  • Oppose With respect the the global stewards, who I am sure perform their responsibilities admirably, the solution to insufficient admins working on vandalism at en.Wiki is expand the admin corps; if insufficient editors pass RfA, then the solution may be to unbundle and distribute the tools required to address vandalism. - Ryk72 'c.s.n.s.' 07:02, 16 December 2015 (UTC)[reply]
    • I think the situation is as Od Mishehu describes above. We trust people from outside enwiki with highly advanced rights, like removing our bureaucrats. We surely trust some of them to fight vandalism. However we do not trust them to do other admin chores. Because those don't just require trust, but also advanced knowledge of our community and specific community guidelines. Moreover, we want only people we ourselves appointed to have rights. Unbundling vandal fighting would be a solution. Making it possible to vote someone to do only that. However, it is not something likely to happen. In theory anyone could apply for such a right. And people will not feel comfortable to appoint such a right to just anyone. However, if you could unbundle and make it possible for stewards and global sysops to apply for such rights, or former stewards, and former Wikipedia admins, in a vote, here on Wikipedia, I would support that. And it might work out well. Former admins who had issue with AFD are still trusted with vandal fighting and could return. Sincerely, Taketa (talk) 07:27, 16 December 2015 (UTC)[reply]
  • Oppose The purpose of the global admin is to provide a service on small Wikipedias where the admin numbers are so low as to be heading for disaster. Enwiki hasn't reached that point yet. As to the global name changing that's already in, there are problems with that on occasions when outside people don't understand our naming policy. It's quicker, but people with unsuitable names have been renamed to equally unsuitable names. Removing a bureaucrat is rather a different matter than dealing with vandalism, just as closing an RfA is different from closing an AfD. Any global admin or steward who wants to do admin work here can apply in the usual way. Peridon (talk) 11:32, 17 December 2015 (UTC)[reply]
Withdrawn - I think it is clear which direction the discussion is going. I withdraw the proposal. -- Taketa (talk) 18:19, 18 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.

Are names a style issue or a content issue (or both)?

As a follow on from the (now closed) RFC regarding MOS:IDENTITY (above)... I think part of the reason why we did not reach a completely clear consensus is that there is a fundamental (underlying) question that has not yet been asked: Is the MOS the right venue to deal with the issue?
Should the question of what NAME to use when referring to someone in an article really fall within the scope of our MOS guidance? I suspect that many editors would say "no"... considering the question of what NAME to use when referring to people to be a question of fact (a content issue resolved by examining sources and not a style issue to be resolved by our own internal style guidance). I also suspect that many other editors will disagree with that contention, and say "yes"... that it should be something that is governed by MOS guidance. Whichever view one holds... That is a fairly fundamental difference of opinion. I think we need to reach a consensus (if we can) on this fundamental question before we can properly resolve the issues presented at the RFC. So... I ask the question: Should the issue of what NAMES to use really be subject to MOS guidance in the first place? Blueboar (talk) 16:20, 15 December 2015 (UTC)[reply]

It's not a simple issue with a simple solution. There are two different, but intertwined issues here:
1) What name should we list an article under
2) How should we refer to a person in an article about them
The first issue is more specialized: it is subject to basic conventions we've established here at Wikipedia regarding naming an article, like WP:UCN, but also issues regarding having respect for living people (WP:BLP) that require us to temper our strict adherence to a simple algorithm with care and prudence.
The second issue is absolutely an MOS issue, though (like much of the MOS) is reflective of general conventions displayed through good writing; an issue which isn't subject merely to Wikipedia but to good English usage at large, though some issues are Wikipedia-centric, there are also the standard considerations one has for producing good quality text. In the same piece of writing (anywhere in the world, not just at Wikipedia) it would not be uncommon to refer to a person by a) their official full name b) their common full name c) their common first name or nick name d) their surname at various places in a piece of writing. The MOS should absolutely set conventions for doing so in a consistent manner. It is a style issue.
Part of the issue we have (and this is maybe where some of the overreach of WP:AGF can come in) is that some people try to use naming issues to make political statements unrelated to quality writing. Insisting that a person be called something, or refusing to call them something, can often be done for reasons unconnected to what is best in telling a quality story, and more about controlling and shaping the narrative to present one's own political point of view on any number of matters. Sometimes, I think, we focus too much on the AGF-friendly solution by refusing to confront greater issues. --Jayron32 16:31, 15 December 2015 (UTC)[reply]
WHY do you consider it an MOS issue? Determining what name someone used at a given period of time is no different than (say) determining what the population of a country was at a given period of time. Sources may disagree, but we look to sources to make that determination. Surely you would not say that determining population numbers are an MOS issue (would you)? So why would names be different? Blueboar (talk) 13:33, 16 December 2015 (UTC)[reply]
Here is why it is an MOS issue. There's a man whose official name is James Earl Carter, Junior. He served as President of the United States from 1977-1980. When we write about this man, how we refer to him in our text is entirely a style issue. Do we call him his full name every time? Do we call him Jimmy Carter? Do we call him Jimmy? Do we call him James? Do we call him Carter? Do we call him Mr. Carter? Do we call him President Carter? What pronoun do we use? What titles do we use? Do we use some combination of these, depending on context? Style is all about word choice. That's the point of a "manual of style": to prescribe and proscribe certain linguistic conventions and word choices so as to provide some consistency of style, and reduce inconsequential discussions over these matters. We decide when and where to use certain words, punctuation, grammatical constructions, etc. ahead of time and publish those guidelines in the Manual of Style. Since this is all about word choice, it is certainly an MOS issue. --Jayron32 13:50, 16 December 2015 (UTC)[reply]
1977-1981, actually.  :) Neutron (talk) 22:29, 17 December 2015 (UTC)[reply]
I disagree. Consider the following: A major city in Russia has undergone various name changes over the years... from St. Petersburg to Petrograd to Leningrad and back to St. Petersburg. I want to refer to this city in an article... What name should I use? As I see it, the answer is a factual determination, governed by historical context... it's not question of style. Blueboar (talk) 14:08, 16 December 2015 (UTC)[reply]
Different issue. Jimmy Carter is simultaneously (as in right now) known by different names, factually. Whether I call him "Jimmy Carter" "James Earl Carter, Jr." "Jimmy" or "Carter" is not a factual issue because those are all factually correct names right now, and at all points in his life. Choosing which one to use, in which context, is a style issue. Choosing which name of a city which had different names at different times is a different issue. This is more like choosing which name to use when referring to a place like New York City. Do we use "New York City", "New York", "New York, New York", "New York, NY" etc. and in which contexts. All are factually correct, so choosing which ones to use are style issues. --Jayron32 14:22, 16 December 2015 (UTC)[reply]
I think the city example works; there is still a difference between questions of fact and questions of style. The facts are that the city was called Санкт-Петербу́рг/Sankt-Peterburg/St. Petersburg, then Петрогра́д/Petrograd, then Ленингра́д/Leningrad, then back to St. Petersburg. How we refer to it is a question of style, of which "use only the anglicized form of the common name in use at the time" is only one option. Other plausible styles would be to also give the modern name and/or Russian name on first mention within an article.--Trystan (talk) 00:45, 17 December 2015 (UTC)[reply]
I agree that using the city example shows why it is a MOS issue, particularly in light of naming of transgendered individuals RFC; what name to use is going to depend on context. If that context is historic, then using the name that that city was known by at the time is appropriate; if the context has no real fixed time, then the most convenient way to refer to the city should be used. Understand the context to then make further determination on the right name makes it a style issue. --MASEM (t) 01:09, 17 December 2015 (UTC)[reply]
I am still not sure that I understand this viewpoint, so let me present another example of a name change: There is a building in New York City that used to be named the "Pan Am Building". It is now named the "Met Life Building". I think we would agree that choosing which name to use in an article when referring to this building depends on historical context. But would you say that choice is a style issue? If so, why? What does style have to do with it?Blueboar (talk) 15:06, 17 December 2015 (UTC)[reply]
Is the transgender naming issue still bothering you? Would it be possible to come out and stop dancing around the issue and state, in unequivocal and unambiguous terms, what you want changed about the way we do things? Trying to get people to agree with you by obfuscating what you're going after isn't helpful. Just tell us what you want, if enough agree, we'll fix it. If people don't agree, it'll stay the way it is. How about that instead of all of this "here's an analogy I'll set up to force everyone to agree with me so I can spring that "GOTCHA" moment when I bring out what I don't like about the whole transgender naming issue, and make everyone look foolish for lacking consistency!", you just tell us what is really wrong. --Jayron32 16:23, 17 December 2015 (UTC)[reply]
"Is the transgender naming issue still bothering you?"... not really... I am concerned about a more fundamental question: What information should (and should not) fall within the scope of an MOS? Blueboar (talk) 17:15, 17 December 2015 (UTC)[reply]
I think it can and cannot, depending on to what end. Naming issues, like what to call a person when there are a range of choices (surnames, nicknames, titles, etc.) are absolutely an MOS issue, it is a style, not factual, issue. There are other naming issues, such as those brought out in the transgender naming discussion above, which may not be; though it may be worthwhile to mention such issues in the style guide because people may come looking for them here as well. That is, while there is some crossover between the issues of identity and dignity granted to living persons, which is a policy issue outside of the scope of a style guide, there are also crossover issues that should be addressed here. I see no reason not to include at least an overview or cursory treatment, with links to the policy pages, in the MOS. --Jayron32 20:38, 17 December 2015 (UTC)[reply]

Perhaps I need to ask this another way... can someone give me some examples of the kind of information that is not considered within the scope of an MOS? (they do not necessarily have to be related to the issue of "names", but it would help me if they were). Blueboar (talk) 21:32, 17 December 2015 (UTC)[reply]

I've been watching this conversation with interest and have not replied, but the more I think about it, I think naming conventions are always a manner of style. The factual parts of a name really have nothing to do with the conventions of how someone is called. This becomes extremely apparent when looking at women's names. At certain times in history it was completely unacceptable to refer to women in terms of anything other than a father or a husband. Patronymics, surname changes, and custom have obscured many historical records. There was the period wherein it was considered overly familiar to refer to a woman by anything other than Mrs/Miss (Frau/Fraulein, Señora/Señorita, etc.) X, as using their first name was seen as overly familiar. Then there was a period wherein first names were used and surnames often excluded, resulting in women being given back their identity, but simultaneously being treated differently than men. Currently, the convention tends to refer to all professionals by a surname (unless of course the notability is derived under a singular name). Thus Coretta Scott King would be referred to as Scott prior to marriage and King thereafter. Her husband, in the article about King would be Martin (he is not being spoken of as a professional in her article but a spouse, i.e. personal relationship) or MLK. In any case, it all is style. Her factual content of her name is what it is in an given period but how it is presented is a matter of custom or style. Don't know if any of that helps you. SusunW (talk) 06:45, 18 December 2015 (UTC)[reply]
@SusunW - So WP:Naming conventions (people) is essentially an MOS governing names of people, even though it is not prefaced with the letters "MOS"? Interesting idea. Would you say that WP:COMMONNAME is an MOS?
@ all... This still does not answer my question as to the limits of "style" ... is there any article content that doesn't fall within the scope of "style"? Blueboar (talk) 13:27, 18 December 2015 (UTC)[reply]
I would say no. Content could be described as the presentation of facts. The facts are the facts, and the presentation is the style.--Trystan (talk) 14:30, 18 December 2015 (UTC)[reply]
No. Let's stick with my Presidents of the U.S. naming issues. Look at something like Gerald Ford. There is a person who had two completely different legal names at different phases of his life; for the first 3 years of his life he was "Leslie Lynch King, Jr." From ages 3-21, he was legally "Leslie Lynch King, Jr.", but informally took the name of his adoptive father, and became "Gerald Rudolph Ford, Jr." After age 21, he formally changed his legal name to match the name he use, becoming legally "Gerald Rudolph Ford, Jr.". Noting these facts during the course of the article is not a style issue. The article correctly and accurately notes the dates and particulars of his official name history. The style issue comes in when we decide what referents, and when, to use to refer to this person at various points throughout the article: that is, the use of various conventional forms of his name (including, but not limited to, any of the following options: The full name, partial conventional names (omit middle, use first only, use last only, whether to use postnominal "Jr.", etc.), nicknames, pronouns, and titles (like Mr. or President) would be style issues. Because it deals with how we present information in the narrative of the person's life, not with the basic facts. Whether we call him Gerry, Gerald, Ford, President Ford, etc. None of those is wrong, but decisions of which to use depend on style conventions we select to set a certain tone in the article. --Jayron32 15:22, 18 December 2015 (UTC)[reply]
Blueboar Never is such an all encompassing thing. Life is way more grey than most humans acknowledge, but in general, I doubt that there are many instances in which content is not effected by style. And yes, Jayron32 you get exactly my point. Though your example is how it effects a man, that exact thing happens to well over half of the articles on women. If one cannot search all the variant of their names, important facts about history will more than likely be omitted, thus the content needs to accurately reflect what they were called, but the tone we are aiming for, encyclopedic, definitely is a style dictate. SusunW (talk) 16:08, 18 December 2015 (UTC)[reply]
Well, part of the problem here, is that the issue was a non-issue until the transgender naming issue made it an issue. People change names all the time, and we've had non-controversial means of dealing with it. Starting with Chelsea Manning and continuing with Caitlyn Jenner, there have been several high-profile issues where a person has transitioned between two genders and changed their names as well. When people change names because of adoption, or marriage, or as stage names, or for any of a number of other reasons, Wikipedia has dealt with these uncontroversially. We've always consistently used a person's most recent, common, or preferred name when referring to them at all phases of their lives; the parts of Bill Clinton's biography when his last name was Blythe still call him Clinton, even though he didn't use that name during those times. Sofia Loren is called by the surname "Loren" even for the times of her life before she adopted that stage name. Martin Sheen's biography consistently uses the name Martin Sheen at all phases of his life and career despite it not being his official name for any part of his life, and not even existing as a stage name for himself prior to starting his professional acting career in his early 20s. In almost every case, nearly universally, we don't change how we refer to people in their past: we use their current name for their entire lives. Yet, calling the person who won the Men's Decathlon in 1976 "Caitlyn Jenner" makes people uncomfortable, in ways that calling the child then known only as "Ramón Estévez" by the name "Martin Sheen" doesn't bother anyone. --Jayron32 16:34, 18 December 2015 (UTC)[reply]
"We've always consistently used a person's most recent, common, or preferred name when referring to them at all phases of their lives" ... In that statement I completely disagree. The article title is the name they were notable under, but as I said above when Coretta Scott was unmarried, the portion of her biography dealing with her life as that entity should reflect that entity as that is the name sourcing will be found under. She was not King until she married and reflecting that would be confusing. Likewise, in the case of numerous notable women Evonne Goolagong, Elizabeth Taylor, and many others, referring to them by any name other than the one in which they gained notability would create confusion. Goolagong's career was made before she married Cawley. I would venture most people would not even recognize that surname. Taylor changed husbands so often that it would be totally confusing to refer to her as anything other than Taylor. I think common sense has to dictate naming patterns, as does likelihood of finding sourcing, etc. SusunW (talk) 17:01, 18 December 2015 (UTC)[reply]
Really? We don't refer to Elizabeth Taylor as "Elizabeth Taylor" consistently throughout the article and at all phases of her life, even when she was known by a different name? I can find no uses of another name in her article. Can you please show me how we change what we call her at different phases of her life? Elizabeth Taylor was her preferred name to be used in public, and we consistently use that name. --Jayron32 17:08, 18 December 2015 (UTC)[reply]
I'm pretty sure I specifically said "Taylor changed husbands so often that it would be totally confusing to refer to her as anything other than Taylor." But look at Goolagong's article. She is called almost exclusively Goolagong as that is how she is recognized. Her most recent surname is Cawley, according to your statement, she would be called that, which is not the case. SusunW (talk) 17:14, 18 December 2015 (UTC)[reply]
Re: "the issue was a non-issue until the transgender naming issue made it an issue" I have to disagree... I think the issue of whether (and how) names fell under the scope of "style" guidance has been under the surface in lots of other disputes. For example, the long debate over "Deadmau5" vs "Deadmaus" centered on the question of whether to follow style guidance (MOS:TRADEMARK) or COMMONNAME. (note: MOS:TM has since been amended, but there was a more direct conflict back then). My puzzlement over the scope of MOS guidance (what should and should not be covered in a style guide) when it comes to names has been building for a while... the Transgender RFC was merely the spark that caused me to ask about it. Blueboar (talk) 17:17, 18 December 2015 (UTC)[reply]
We've always consistently used a person's most recent, common, or preferred name when referring to them at all phases of their lives
I just checked the first example that came to mind: Muhammad Ali (like Jenner, an internationally prominent Olympic gold medalist) and found that the article doesn't reflect the above claim.
In almost every case, nearly universally, we don't change how we refer to people in their past: we use their current name for their entire lives.
Surely, your previous description ("most recent, common, or preferred name") is more accurate. The second article that I thought to check was Cat Stevens, wherein we refer to the musician by two different names (depending on the time period), neither of which is his preferred/current/most recent one (which is relegated to the infobox and prose pertaining to the name issue itself).
Perhaps these are rare exceptions. I'm inclined to wonder whether the name changes' occurrence after the individuals achieved fame is a factor. —David Levy 17:31, 18 December 2015 (UTC)[reply]
David Levy therein lies the rub. For the majority of women, it makes no difference whether notability occurred before or after marriage and a name change. They will have multiple names if they choose to take another surname and most do. The reason I entered the debate in the first place was to stress how very common name change actually is. We cannot ignore that it happens or use a single "rule" to apply to all circumstances. SusunW (talk) 17:39, 18 December 2015 (UTC)[reply]
Agreed. In articles about both females and males, context is key. Cassius Clay changed his name to Muhammad Ali as part of a well known religious conversion, which is meaningfully different from an instance in which someone adopts a pseudonym simply because it's considered more appealing or marketable.
Incidentally, I just checked the third example to come to mind: Kareem Abdul-Jabbar. As in the aforementioned articles, Jayron's "all phases of their lives" statement does not apply. —David Levy 18:33, 18 December 2015 (UTC)[reply]

WP:ANIME discussion on studios and films

There's an important discussion at WT:ANIME regarding the use of studios in the infoboxes of anime films. The discussion can be found at Wikipedia_talk:WikiProject_Anime_and_manga#RfC:_Anime_films_and_production_companies. Lord Sjones23 (talk - contributions) 14:14, 17 December 2015 (UTC)[reply]

Comment

This donation banner is getting a little obnoxious. I don't remember it being so bad in previous years. It's enormous; its colouration is extremely aesthetically jarring; it fills up most of the screen every time I try and go to a Wikipedia page (regularly), and then after its closed it sneaks another red banner out at the top sometimes. It might be more effective than before; but a little discretion when asking for money might be a little more distinguished....

142.25.33.103 (talk) 15:14, 17 December 2015 (UTC)[reply]
If you create an account, you will never see the banner again. You don't even need any money. Just create an account, and you can then set the preferences to make the banner never show up. It will take you 2 minutes. --Jayron32 16:19, 17 December 2015 (UTC)[reply]
I do have an account; haven't logged in for a long time. I wasn't griping for my benefit in particular, but was concerned more for the professional image of the encyclopedia when viewed by others. I just think it's starting to go a little too far. But I guess it works....
142.25.33.103 (talk) 16:26, 17 December 2015 (UTC)[reply]
I have to agree that the current banner is over-kill (for those of us who don't want to be permanently logged in, we still have to deal with the banner in order to do so... the banner is so huge that I have to scroll down the page just to find the "log in" button.) Blueboar (talk) 18:17, 17 December 2015 (UTC)[reply]
@#$%&!! I just logged out to check, and I was appalled to see my entire screen blotted out by a donation "banner". The WMF rotates random banners for testing, and that one was absurd. At 1920x1080 screen resolution and 100% browser zoom the only other thing visible was the article title at the bottom edge. At lower resolution or higher zoom it fills the screen completely. Alsee (talk) 10:10, 18 December 2015 (UTC)[reply]

Replacement of 'St.' and 'St' by 'Saint' in titles

Following a series of requested moves, by others and me, I would like to suggest the implementation of a policy to replace the use of disputed abbreviations ('St.', 'St' or 'St-'?) by clear informative full names (incidentally also corresponding to how the names are pronounced orally). For your information, here is a list of such articles: https://en.wikipedia.org/w/index.php?title=Special%3APrefixIndex&prefix=St&namespace=0&hideredirects=1
Peco Wikau (talk) 22:28, 17 December 2015 (UTC).[reply]

Oppose Who's going to decide if an abbreviation is disputed or not? On most pages, there is a clear common name in use, and that's the one each individual page uses. A blanket policy would not serve these pages well. Rockypedia (talk) 23:45, 17 December 2015 (UTC)[reply]
Oppose I dispute the idea that these abbreviations are universally disputed, particularly in place names where there is clear common usage, like St. Helens, Oregon. It would be ludicrously inaccurate to rename that to "Saint Helens" because nobody uses that form. Regards, Orange Suede Sofa (talk) 00:09, 18 December 2015 (UTC)[reply]
Oppose for the same reasons already cited. No one refers to St. Louis, Missouri as Saint Louis. SusunW (talk) 00:24, 18 December 2015 (UTC)[reply]
Oppose. I've never seen the "St." in Mount St. Helens expanded when the name is written. --Carnildo (talk) 01:19, 18 December 2015 (UTC)[reply]
Oppose There are a number of cities I'm aware of with "St." in the name that are never referred to as "Saint". It would be bizarre to see them written that way.  DiscantX 02:03, 18 December 2015 (UTC)[reply]
Oppose because telling editors to use a different spelling for US place names than the spelling used by the USGS is just asking for trouble. Chris the speller yack 02:51, 18 December 2015 (UTC)[reply]
Oppose Per above. Alex2006 (talk) 07:02, 18 December 2015 (UTC)[reply]
Oppose - The use of "Saint" vs "St." is governed by WP:COMMONNAME and Wikipedia:Naming conventions (geographic names). Essentially, our usage is determined by what sources use - if the sources normally refer to the city using the abreviation "St.", then that is what we should use (as it will be more recognizable)... and if they use "Saint" then we should use that instead. Blueboar (talk) 13:14, 18 December 2015 (UTC)[reply]
Conditional support Thanks for your input. The idea wasn't to consequently change this per general principle, but exclusively where properly fit - meaning excluding notable places like mentioned above, which I also do oppose as per WP:COMMONNAME. The idea was thus to distinguish on a case by case method. Chicbyaccident (talk) 16:17, 18 December 2015 (UTC)[reply]
Oppose I am also opposed to the use of 'St.' as the full word ends in t (Similar to 'Dr' not 'Dr.'). 'St-' is used in French but not normally found in English. 'Saint' is not a common form in English based placenames, but other languages differ and this should be respected (if only in redirects, which cost very little). As to Saints themselves, IMO 'St' will do. Any Saint that wants a full spelling has only to notify us via OTRS. Peridon (talk) 18:06, 18 December 2015 (UTC)[reply]
Oppose The suburb of St Kilda (and therefore its footy team) is always written thus. The spelling is official, and it is not named after any saint. Hawkeye7 (talk) 18:31, 18 December 2015 (UTC)[reply]

Leave a Reply