Wikipedia:Village pump (policy): Difference between revisions

Browse history interactively

← Previous edit Next edit →

Content deleted Content added

VisualWikitext

Inline

Revision as of 15:01, 27 February 2018

Table of contents
First discussion
End of page
New post

Shortcuts

The policy section of the village pump is used to discuss proposed policies and guidelines and changes to existing policies and guidelines.
If you want to propose something new that is not a policy or guideline, use Village pump (proposals).
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.

« Archives, 177, 178, 179, 180, 181, 182, 183, 184, 185, 186, 187, 188, 189, 190, 191, 192, 193, 194, 195, 196, 197

Criteria for inclusion in Births and Deaths sections of Wikipedia date articles

Per previous discussions over at Wikipedia talk:Days of the year, it seems that there is some level of support for some kind of inclusion criteria for what articles to include on the Births and Deaths sections. There are some concerns that these sections are too-Western centric (i.e. people from North America or Europe are over-represented).

The question now is: should we have some kind of guideline for inclusion in Births and Dates articles? Or is the status-quo fine? In my case, my pet proposal is that a proposed inclusion criteria would be similar to what's currently done at WP:DYK, where no more than half of each set can be about US-related topics. Though of course, other editors are free to propose other proposals here. Narutolovehinata5 ^tccsdnew 03:16, 28 January 2018 (UTC)[reply]

Just axe these sections. They're useless trivia. KMF (talk) 04:12, 28 January 2018 (UTC)[reply]

I agree with KMF that this is trivia. There is no possible way to develop an objective criteria for inclusion, and any volunteer time wasted on this would be better spent actually improving the encyclopedia. Cullen³²⁸ Let's discuss it 05:10, 28 January 2018 (UTC)[reply]

If you're reading the Wikipedia article about a particular day of the year, I would surmise that probably you are very much in the market for useless trivia! CapitalSasha ~ talk 05:18, 28 January 2018 (UTC)[reply]

With the exception of a few incidents which are frequently referred to by their dates (e.g September 11 attacks), or dates which represent holidays on the Gregorian calendar (e.g Storming of the Bastille, which is the source of Bastille Day), all data on date pages are trivia. I see no reason why it's any less trivia that the Titanic sank on April 15 than that the actress Emma Watson was born on this date. עוד מישהו Od Mishehu 07:59, 28 January 2018 (UTC)[reply]

The best option in my opinion would be to branch out "Born on ..." and "Died on ..." into separate articles (many of these lists online, but lots of misinformation, and none that are verifiable), maintained by bots and linked to on the DoY pages. This would reduce editor time spent to practically zero, does away with arbitrary inclusion criteria, and makes sure the info is still there for people who want it. The only objection that I've come across is that this could be done by category instead, but this makes it a nightmare to sort by year, and prevents the brief summary of what the people were notable for. ‑‑Yodin^T 12:19, 28 January 2018 (UTC)[reply]
I think the inclusion could be based on quality of linked articles. For example, limit inclusion to articles that have 500 words of pure prose and have no major clean up tags. Renata (talk) 14:44, 28 January 2018 (UTC)[reply]

That makes sense for a internal stuff...but that's not exactly an encyclopaedic inclusion criteria? That's the same problem with Narutolovehinata5's proposal - "than half of each set can be about US-related topics." is fine for internal inclusion, but not for an objective encyclopaedia. Galobtter (pingó mió) 14:50, 28 January 2018 (UTC)[reply]

Well, Wikipedia is mature enough that truly notable people generally have bios that are pretty decent. Of course, there are all kinds of exceptions and anomalies. But I think it would be very useful to have some sort of arbitrary criteria based on article quality to avoid lengthy discussions on who is more notable. Renata (talk) 03:56, 29 January 2018 (UTC)[reply]

In my view a notability criterion would be relevant, but that may be different from an article quality criterion. Many highly important people from (e.g.) the 18th century have short, underdeveloped articles, while many largely irrelevant sports or music (mainly US and UK) people from today have lengthy well developed articles maintained by fans. So a quality criterion developed along lines of development of article, would not solve the problem raised at the start of this post and in fact may even worsen it. Splitting off list of births and deaths on this date as Yodin suggests would not be perfect, but would at least largely solve the problem. This not in the least because such lists would allow much more entries, without overwhelming the rest of the entries on the day article (thus taking the sting out of discussion there). Arnoutf (talk) 07:11, 29 January 2018 (UTC)[reply]

It's simple. Include every single individual who was born/died on any given day. The Rambling Man (talk) 07:34, 29 January 2018 (UTC)[reply]

@The Rambling Man: Wouldn't such list articles (assuming the sections get split, as proposed above by some users) end up being very long and potentially falling afoul of WP:IINFO? Narutolovehinata5 ^tccsdnew 13:15, 29 January 2018 (UTC)[reply]

Policy has nothing to do with it. It's too unweildy. As a quick Fermi approximation, Wikipedia has 5.5 million articles. If 10% of those were about people (not an unreasonable guess) that'd be 550,000 biographies here at Wikipedia. We'd guess about 1/365 would have any random birth or death date. That's approximately 1500 people per day born, and 1500 people per day die (a bit less, since some of those people haven't died yet). Aproximately 3000 lines of text just to keep track of birthdates and deathdates is unreasonable. --Jayron 32 16:11, 31 January 2018 (UTC)[reply]

I don’t know if this is possible tech-wise, but what would be helpful to the reader would be to group “on this day” entries into sub-lists... non-birthday events that occurred on the day go in one section... birthdays in another (I would even divide the birthday listings up into sub-sub-sections by profession groups: Performing arts, business, politics, etc). This would help readers USE the lists more efficiently... to more easily find the information they are looking for. Blueboar (talk) 11:35, 29 January 2018 (UTC)[reply]
Could this be better handled by categorifying the data? That way, the category "Born on XXXX" would automagically be populated. Surely there is some better semi-automated way to handle this better than relying on people randomly coming by to add a name to a page. --Jayron32 15:11, 29 January 2018 (UTC)[reply]
- See above: Categories don't allow readers to see a brief summary of each person, or even display which year they were born. Also, if you wanted to try to sort these categories by year it would be problematic and very counterintuitive (even if you add leading zeroes to account for years < 1000), B.C. dates would still be sorted alphabetically (so 1 BC first, 300 BC last), followed by A.D. sorted alphabetically (1 AD first, 2017 last). If not, then you end up with just an unreadable list of names sorted alphabetically, something I doubt any of the readers (for example those mentioned above by CapitalSasha and Od Mishehu) would be interested in. With Wikidata, it should be straightforward to get a bot to maintain these lists as articles, rather than resorting to categories of use to neither man nor bot. What do you reckon? ‑‑Yodin^T 16:17, 29 January 2018 (UTC)[reply]

I'm against this, primary because I fear it would have potential to creep over to the "years" article, in which the inclusion of everyone that has a wikipage is very useful. I also glimpsed at two random dates in January and it did not seem that outrageous, when you consider the attempted scope of the article. (Granted this was on the desktop version) We could include tools to make it easier to navigate however on mobile,but I'm not in favor of limiting the amount of people that could be there. --Deathawk (talk) 22:37, 29 January 2018 (UTC)[reply]

I would say that, in line with some others here, we should get rid of these sections; they seem irrelevant to information about the date (so most people on the page for a given date probably won't care about this information) and it's inherently too hard to come up with an objective standard for who should and shouldn't be included. Perhaps a set of categories for people who were born or died on a given date would be an improvement (i.e. Category:People born on January 1, etc.) Every Morning (there's a halo...) 00:34, 30 January 2018 (UTC)[reply]

I think much of this debate comes from a fear that these pages will get too long too quickly and will become out of control. This, for the most part, is unfounded, as the pages are edited by humans and most people will not actually have time to edit these in such a way that it gets unmanageable. And if they do, we can split it off into a separate article. I agree with a sentiment explained already in this threat that the people who go into a date article probably are looking for a list of who was born and who died on that day. What I'm saying is, I don't think this is a feature that our readers are annoyed by, so much as editors are, and we should be in service to the reader. --Deathawk (talk) 02:07, 30 January 2018 (UTC)[reply]

I agree with Deathawk's position. It is trivia, but the reader looking up a date like January 30 probably is looking for this kind of trivia. Coming up with DYK-like restrictions for it seems to serve editors more than readers, IMHO. Double sharp (talk) 05:56, 30 January 2018 (UTC)[reply]

No. Critreria is not needed. L3X1 Become a New Page Patroller! (distænt write) 15:29, 31 January 2018 (UTC)[reply]

There has to be some way to manage these lists. Right now, Category:1980s births has approximately 15,000 people per year. Given that everyone born will die, and that Wikipedia continues to exist, that's roughly 1,000 new entries per date every ten years. That's untenable. The argument that this won't happen because people won't do it strikes me as flawed because that's not a guarantee that it won't happen, and it wouldn't be hard to write a bot to populate those lists or for one determined editor to do so. The fact that it hasn't happened yet is probably due more to the fact that these lists are currently curated, even though we don't have clear guidelines. Personally, I think it'd be best to create a new article People born on (x date) and leave a tiny subset of the most notable (determined perhaps by restricting it to a certain number per article or by set criteria) on the actual date article itself.

As to the other arguments, I agree that these lists are largely trivia, but that does seem to be the purpose of the DOY articles, and I’m okay with that. I don't think a category suffices because it doesn't include the brief descriptions and because categories are merely alphabetical and not chronological. -- irn (talk) 14:16, 3 February 2018 (UTC)[reply]

A summary of my opinion:

These sections are of value and are the kind of thing people expect to see in an article about a given year or date.
They should not be allowed to become too long. 100 names in each section should be the absolute limit.
An effort should be made to ensure a spread of nationalities, occupations, and historical period.

There will be a lot of work needed to establish criteria but to me it seems essential that we make the effort. — Preceding unsigned comment added by Deb (talk • contribs)

If nothing is done we'll have to put up with seeing the Births and Deaths sections grow to enormous length – I recently saw someone going through methodically adding all the footballers from a particular country, and we have no rule against this. I've estimated potentially 3,000 names under Births for each day. Otherwise we need criteria for "super-notability" to go on these lists. Something on the lines of Deb's suggestion may work if we have subsections for each date with really tight and unarguable eligibility, such as "Monarchs, presidents and prime ministers born on this day", "Nobel prizewinners born on this day", "Olympic gold medallists born on this day" ... then "... died on this day", all chosen to ensure Deb's "spread of nationalities, occupations, and historical period": Noyster (talk), 17:19, 3 February 2018 (UTC)[reply]

I like that suggestion a lot. The unarguable eligibility for super-notable subsections seems a little difficult to me, though, when dealing with entertainers and sportspeople. (Michael Jackson and Pelé come immediately to mind as examples.) I think it should be doable, but we might need to elaborate the criteria elsewhere and just label the subsections "Entertainers" and "Athletes", for example. -- irn (talk) 17:42, 3 February 2018 (UTC)[reply]

Any notability criteria is likely to be subjective and devolve into protracted discussions over personal preference of notability, to the detriment of time spent actually improving the encyclopedia. I suggest adopting the type of standard used at "On this day - born/died" which is (I think) B-class articles or above. This would encourage editors to improve their favourite biographies to B-class to get them included on the day page, and would also be an objective standard. I have seen editors going through the day pages removing names which they personally consider non-notable and it's very subjective of course - "not her, she's a porn star and that's not on" etc etc. It should also be easy to get this automated if it's pulling on the pools of B, A, GA and FA articles only. MurielMary (talk) 09:39, 4 February 2018 (UTC)[reply]

B-class isn't exactly a objective criteria..anyone can change ratings.Galobtter (pingó mió) 09:44, 4 February 2018 (UTC)[reply]

I really like the incentive for editors to improve the articles. While it might not be a perfect solution, I think it would address the concerns of editors who work on DoY articles, in that the lists won't become unmanagable (for at least the next decade or so), and we shouldn't allow the potential fixing mentioned above to prevent a good idea from being implemented. It also seems to follow the pattern of WP:ITN, in that it's not just about "more or less notable", but quality of their coverage on Wikipedia. Would love to help with an improvement drive to address WP:BIAS on this. ‑‑Yodin^T 12:39, 4 February 2018 (UTC)[reply]

Just tossing out an idea here... If we really want to base inclusion on article quality, then perhaps the criteria should be “good article” status. “Good article” status is a more defined process which means the article has been reviewed and has achieved a substantive quality standard. The down side is that some notable subjects may not be listed (if the article about them is poorly written) ... the up side is that this would encourage editors to work on these articles, and bring them up to “good article” standards. Blueboar (talk) 13:37, 4 February 2018 (UTC)[reply]
- The snag with this is - what do we do if, for example, "Michael Jackson" has not achieved GA status? Deb (talk) 09:39, 5 February 2018 (UTC)[reply]
  - Work on the Michael Jackson article and GET it to “Good article” status? Blueboar (talk) 11:17, 5 February 2018 (UTC)[reply]

There are 6,490 biographies classified as GA and above,[1] making about 18 per day of the year. No Thomas Jefferson, no Mussolini, no Beethoven, no Mozart ... All these are B's and I'm starting to think we may have to go with B-class and above, recognising the flaws. I'd have preferred to base it on importance of person rather than quality of article, but neither Top-importance nor Vital articles will yield nearly enough names, and the difficulties of establishing any other criterion of importance are obvious: Noyster (talk), 11:10, 5 February 2018 (UTC)[reply]

I'm thinking limiting it to B articles might work quite well. Deb (talk) 11:44, 5 February 2018 (UTC)[reply]

The problem I see with limiting this to a certain class of article is that it's not exactly user friendly. I imagine that the majority of editors adding content to these pages are relatively inexperienced to Wikipedia, and would be unaware of what a "B class article" means. It would be devastating for them to come and have there edit reverted. I could imagine some editors who might prove useful to the project being turned away from it as a result. It's just too much CREEP. One thing that might work is instead language that encourages the inclusion of "high class" articles as opposed to underdeveloped ones. A good example is how Wikipedia: Unusual Articles, states that the articles should be of "decent quality" but does not further expand on what that means, as a result the editors somewhat police themselves. --Deathawk (talk) 03:41, 6 February 2018 (UTC)[reply]

"Decent quality" is rather subjective, and, if editors got together and put a definition on "decent quality" I suspect they would just be re-inventing the wheel - WP already has definitions of quality in the Stub/Start/C/B/A/GA etc scale. I think In The News has a definition of "decent quality" for inclusion in their corner of the main page which is something like "no orange tags, all statements cited, no copy vios of images" but this is a pretty low bar and I think using something this minimal wouldn't go far to reduce the quantity of articles on the day pages. What I've noticed at In The News is that someone nominates an article for inclusion, someone else tags it with an orange tag, then the nominator gets to work fixing up the article, the orange tag is removed and it gets published on the main page. Good for the encyclopedia to have all that effort going into improving articles. MurielMary (talk) 10:48, 6 February 2018 (UTC)[reply]

I still maintain that this is problem mostly imagined. Personally I find it a bit ridiculous to have a Wikipedia article for every day of the year, but I don't really see it as problematic and if people find it interesting I don't mind either way. Having said that if you include a list of every date and have a listing of birthdays and death dates for the page, then it stands to reason that you are going to get a lot of listings . However this is the purpose of the page and it is fulfilling that roll. To somehow modify that list, you are now making it actually less useful, and it's falling farther and farther from the purpose. --Deathawk (talk) 20:17, 6 February 2018 (UTC)[reply]

@Deathawk: There are over 1.5 million biography articles at the moment, that's more than 4,000 births for each day, plus deaths, with more being added all the time. If we don't attempt to curate them, they would quickly reach article size limits. I would personally agree that complete lists make sense, and aren't a problem, but they would have to be split from the main pages. But either way, we've got three options I suppose:

No births & deaths on the DoY pages (and optionally splitting the lists into separate articles).
Having a list without the names of people that very few readers would have interest in (e.g. a very obscure mid 20th century sportsman compared to, say, Alexander the Great) – again, this could be done in conjunction with separate lists, but doesn't have to be, as at present.
Ignoring the DoY articles, allowing them to fill up, quickly becoming very slow, to the point of being unreadable on mobiles, and eventually reaching the absolute article limit, preventing editing, etc..

A fair number of editors are trying to prevent #3 from happening, but it's a complete pain without guidelines that would make the process easier (and hopefully automated, to free us up to do more positive editing!). I guess you're not actively trying to prevent this from happening, but opposing it on the grounds that it's imagined makes me think you don't do much editing on DoY pages? Either way, it seems that for the first time in a long while we're finally pretty close to reaching a consensus – would be great to reach the point where a clear guideline proposal could be made. ‑‑Yodin^T 21:53, 7 February 2018 (UTC)[reply]

A bit late to the discussion, but the original question was whether the pages were too America-centric. I've been attempting to correct this by deliberately adding people from around the world. A problem that comes up often is that many of these are stubs, or need content from another wiki. Add to that the new requirement that dates of birth and death need good Wikipedia references, and it's a lot more work to edit these pages with quality content.

For the record, I guess I'd go with option 2 above. There's a lot of interest in "born on this day" and "died on this day", so I think births and deaths are relevant. Natalie Bueno Vasquez (talk) 06:23, 8 February 2018 (UTC)[reply]

As for the proposals above which suggests that all articles that are mentioned in Births/Deaths sections need to be at least B-class, I'm not sure it would work in filtering out systemic bias; if anything, it could only help worsen it. Some articles on even the most well-known Western people are at C-class or lower, meaning that they'd have to be left out; on the other hand, from experience, articles on non-American or non-European topics tend to be of a lower quality as well, meaning that even very popular names wouldn't be mentioned. So while article quality could potentially work as a standard for inclusion, it also has its drawbacks and might not solve the problem at all. As for the suggestion of simply making separate list articles and listing all births/deaths there, that would be wildly impractical: such articles would be way too long. Narutolovehinata5 ^tccsdnew 07:37, 8 February 2018 (UTC)[reply]

Lists of births & deaths could easily be broken down (either by the people's roles as suggested by another editor above, or by century). ‑‑Yodin^T 09:58, 8 February 2018 (UTC)[reply]

Cut births and deaths entirely. This sort of navigation can be done on en-wiki via categories. Searching this sort of question is best done via Wikidata. Chris Troutman (talk) 01:40, 17 February 2018 (UTC)[reply]

I would support removing those sections completely. Besides the constant stream of non-notable people who get added to them, it's really questionable how useful that trivia is. Make it a category so that people can use cross-cat tools to find whatever intersection they're looking for. If we have to keep these lists, split them off into "List of people born on X" type articles (and then delete them as trivia...) Matt Deres (talk) 18:21, 20 February 2018 (UTC)[reply]

Guidance on removing comments from closed discussions

The consensus here is that closed discussions (i.e. those discussions to which a closing or archiving box has been applied in good faith) are intended to be preserved as-is, and may not be edited. Subsequent good-faith edits inside the box should be moved outside the box. Comments should not be reverted for this sole reason, but may qualify for removal for reasons described at WP:TPO. Ivanvector (^Talk/_Edits) 15:01, 27 February 2018 (UTC)

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.

Just a few minutes ago, I reverted a commented added to a closed discussion (the RfC above about airline destinations). My revert was then reverted by Mandruss, citing WP:TPO. The language on the RfC closing template seems to contradict WP:TPO. Can anyone help clarify what should be done here? Thanks. –Deacon Vorbis (carbon • videos) 14:12, 28 January 2018 (UTC)[reply]

Re: [2][3][4]
I'll ask again: What part of WP:TPO authorizes this removal? The fact that a comment violates a guideline (let alone a comment generated by a template, which was what was cited by Francis Schonken) does not authorize removal, or we would be allowed to remove vios of NOTFORUM etc. We are not (and, by the way, NOTFORUM is part of a policy). Removal is a serious action and it is reserved for the most egregious situations. Even if commenting in a closed discussion is considered disruptive, TPO bullet 3 states: "Posts that may be considered disruptive in various ways are another borderline case and are usually best left as-is or archived." It is not considered disruptive in my experience, and in fact I was roundly chastised once in my younger days for simply objecting to comments added after a close. A close is a suggestion, not the 11th commandment.
The rules must be applied evenly to all comments, including useless comments by new editors. To do otherwise is a very slippery slope. ―Mandruss ☎ 14:20, 28 January 2018 (UTC)[reply]

Rather than REMOVING a comment added to a closed discussion, I would suggest that the appropriate action would be to create a new sub-section (perhaps entitled “Comments made after closure”), and MOVE the added comment into that sub-section. This way others know the sequence of events. Blueboar (talk) 16:30, 28 January 2018 (UTC)[reply]

Right, it makes perfect sense that you wouldn't want it to look like the comment occurred before the close. It could be done as you say, or one could just move the comment below the {{closed rfc bottom}}, {{abot}}, etc. Either would be acceptable under the refactoring provision, as I see it. Removal is not refactoring any way you shake it. ―Mandruss ☎ 19:25, 28 January 2018 (UTC)[reply]

And it was my bad for not doing that instead of the plain revert. ―Mandruss ☎ 19:28, 28 January 2018 (UTC)[reply]

Support removal - The bottom of that closed discussion clearly states The above discussion is preserved as an archive of the debate. Please do not modify it. No further edits should be made to this discussion.

Admittingly after maybe an hour I've added a comment to a closed discussion as part of an update or to say thanks but other than that discussions shouldn't really be edited especially after 5 days of it being closed, Removal was fine. –Davey2010^Talk 19:43, 28 January 2018 (UTC)[reply]

There is nothing in TPO about removal of comments that "shouldn't really be" posted. If you're invoking WP:IAR (aka WP:IJDLI), at least say so. Or, you could play the "Wikipedia does not have firm rules" card, or any of the various other trump cards that shut down policy/guideline arguments. ―Mandruss ☎ 19:50, 28 January 2018 (UTC)[reply]

Discussion

I never said there was - TPO IMHO is unrelated, I'm not invoking anything - Read the template which again I will quote for you! - The above discussion is preserved as an archive of the debate. Please do not modify it. No further edits should be made to this discussion. - It clearly states No further edits should be made to this discussion. - What's hard to understand about that ?..... He shouldn't of added it and you shouldn't of blindly reverted the reverter,

WP:WIKILAWYERING isn't going to help you at all - Accept you were wrong and move on. –Davey2010^Talk 21:57, 28 January 2018 (UTC)[reply]

Hey dude, save the tone for noobs who are impressed by it. When the community (read reasonable consensus here) tells me that a message generated by a template trumps TPO, when neither TPO nor the template message say anything to that effect, I'll gladly defer to community consensus. In almost 5 years, I've yet to defer to intimidation attempts by lone editors. ―Mandruss ☎ 22:13, 28 January 2018 (UTC)[reply]

No one is intimidating you and I'm by no means "The voice of Wikipedia" but it's common sense .... if the bottom of a templates tell you not to edit that discussion then you don't edit it it's that simple and as you've been here for more than 5 years none of this should be new to you, Point is you shouldn't of reverted and point is TPO is wholly unrelated here. –Davey2010^Talk 22:54, 28 January 2018 (UTC)[reply]

I have never known "Don't do this on talk pages" to automatically and invariably translate to "It's ok to remove this if somebody does it". Look at the template message produced by {{atop}}. 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. It does not say No further edits should be made within this close box—it says "discussion" and that means thread—and yet experienced editors often add comments below the close box when there is a legitimate reason. Are those comments removed because they violate the letter of the template message? No, they are not. The comments aren't even collapsed, let alone removed. And "legitimate reason" gets a very liberal interpretation, and even pointless humor is tolerated unless it drags on too long.
If your common sense is so common, how do you explain the fact that 12-year editor Blueboar said something completely different above? ―Mandruss ☎ 23:19, 28 January 2018 (UTC)[reply]

Support removal - when someone adds content to a closed discussion, they make it look like this content was part of the content which the closing admin had before him/her and considered when determining the consensus. Such sections should be removed, in order not to mislead subsequent users viewing the discussion. עוד מישהו Od Mishehu 09:14, 29 January 2018 (UTC)[reply]

Support removal--Per OD and that's how we normally do things.Winged Blades^Godric 11:58, 29 January 2018 (UTC)[reply]
Support removal as per the template instruction Atlantic306 (talk) 12:17, 29 January 2018 (UTC)[reply]
- The "template instruction" is only about the text within the box of the closed discussion. It doesn't (and shouldn't) ordain what text should appear outside it. – Uanfala (talk) 00:20, 31 January 2018 (UTC)[reply]
Keep the comment especially in this case – a newish editor expressing their frustration with Wikipedia, to then have a notification saying that their complaint had been reverted without explanation is a great way to WP:BITE a newbie. How much more work would it have been to move the comment into a new subsection below it, to at least acknowledge them? Either way, WP:TPO should be updated to cover closed discussions, and I don't think it should be used as a reason to silence others' comments on a subject unless in the most extreme cases (e.g. posting personal information, etc.). ‑‑Yodin^T 12:52, 29 January 2018 (UTC)[reply]
Keep the comment in some way We actually do have an established practice by many experienced editors to sometimes add comments after something is "boxed" closed - it usually is placed directly below the box - so, generally do that. Alanscottwalker (talk) 13:04, 29 January 2018 (UTC)[reply]
I agree with Alan. It shouldn't be deleted outright, but Od Mishehu is right in that leaving it within the closed discussion box leaves a on incorrect impression of what the closer actually saw. Moving the comment below the close box (possibly with a subheader) is the best solution. oknazevad (talk) 13:22, 29 January 2018 (UTC)[reply]
Support removal. Closed discussions are supposed to be a snapshot of what the closer saw – thus the bold, red text that tells you not to modify it. NinjaRobotPirate (talk) 13:27, 29 January 2018 (UTC)[reply]
Keep in some way- outside the box is fine, and if it's inside the box then it should be moved out of it. Particularly if someone is writing a comment then gets edit conflicted by the closer. Reyk _YO! 13:29, 29 January 2018 (UTC)[reply]
Remove and/or Move the comment to outside the box as needed. Each case should be taken of its own accord; as a general policy we should not allow editing within a closed archive box; however if additional commentary is needed, the option should exist to either remove it (for inappropriate comments or ones which are not needed) or move it to outside the box (if necessary; i.e. commentary on the close itself). If an archive box is used with a summary statement, it is inappropriate to add additional commentary inside the box, as it implies the closer had access to that statement when closing. We should leave legitimately closed discussions as-is in most cases, and if additional comments are needed, start a new thread. --Jayron 32 15:08, 29 January 2018 (UTC)[reply]
Generally Move the comment to outside the box per Alanscottwalker. Although Jayron32 is right that this is a case by case decision. Some comments can probably be removed as disruptive or untimely, but the default rule is (or ought to be) to move a late comment "outside the box".
Regarding having comments added after the closed discussion: at least once I've added a comment after the closed discussion and it was removed. I appreciate there are situations where prolonging the discussion is undesirable (such as a discussion that has been going around in circles for some time). I think it will depend a lot on the nature of the comment: if it's yet another repetition of a point that's already been made multiple times, then it can probably be safely deleted without affecting matters. If it's something new, then it may be reasonable to keep the post-closure comment (outside of the closed discussion). isaacl (talk) 21:20, 29 January 2018 (UTC)[reply]
The comment should be transferred to the talk page of the closed AfD. Xxanthippe (talk) 21:36, 29 January 2018 (UTC).[reply]
Keep in some way outside the close box - Assuming of course that the comment is not qualified for removal per WP:TPO. Completely clueless comments like the one that triggered this discussion are sometimes removed as trolling (TPO bullet 3), but that word gets as much misuse as the V word. Actual trolling has no purpose but to disrupt and produce a big negative reaction, and there needs to be fairly clear evidence of that intent. Outright removal should be used very conservatively, and we should err on the side of retention. ―Mandruss ☎ 02:09, 30 January 2018 (UTC)[reply]
Keep, but move outside the box. Adding comments to a closed discussion is discouraged simply because they're most likely to be ignored: the community has discussed the matter, a decision has been taken and then everyone has moved on. But if an editor decides to add a comment, then there's nothing stopping them. There are many cases where it's useful to add such comments – say, for an update or a follow-up comment, and even in cases where it isn't (for example when the poster is venting about the injustice of the close), they're tolerated. And obviously, the comment should be moved outside the box because otherwise it would be misleading. – Uanfala (talk) 00:20, 31 January 2018 (UTC)[reply]
Support removal the person can move them outside the box themselves afterwards if they feel like it. Reversion is fine. TonyBallioni (talk) 00:24, 31 January 2018 (UTC)[reply]
Keep but move outside the box per Uanfala. Double sharp (talk) 06:32, 31 January 2018 (UTC)[reply]
Keep, outside the box. It is useful to have, for example, a link to a further discussion about implementing the agreed action, without it being either removed on procedural grounds or mistaken for part of the decision process. Certes (talk) 15:31, 1 February 2018 (UTC)[reply]
Keep but move outside the box. (Technically, that's moving the box and/or the comments in it, in a relativistic way) The whole "WP:consensus can change" thing implies that no discussion is ever truly closed - only the box is closed. Wnt (talk) 12:24, 15 February 2018 (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.

Rfc: Change default <math> to be inline

Please consider joining the feedback request service.

An editor has requested comments from other editors for this discussion. This page has been added to the following lists:

When discussion has ended, remove this tag and it will be removed from the lists. If this page is on additional lists, they will be noted below.

Should the "default" <math> be changed to inline in the future?--Debenben (talk) 22:47, 6 February 2018 (UTC)[reply]

Background information

Some time ago I did a little survey in the German Wikipedia on how to resolve several problems with the current markup for inline and block equations. The solution with the most support was turning "default" <math> into true inline equations, equivalent to <math display="inline"> or <math>\textstyle and using <math display="block"> or a new shortcut notation like <math block> for block equations, replacing the current :-indented markup.

Since technical limitations of the current math extension prevent several types of block-formulas from using the new notation and/or such a conversion would negatively impact the appearance on certain devices/browsers, this Rfc does not propose to implement such changes immediately. If this Rfc is successful, the intention for such a change should be written into Wikipedia:Manual of Style/Mathematics along with a recommendation: For formulas that are not block equations but still look better with large symbols, editors should specify \displaystyle explicitly instead of relying on <math> being displaystyle by default.

Some problems the proposed solution might solve in the future

Display options in the VisualEditor (here with German descriptions).

"default" exists for historic reasons and backwards compatibility. For most purposes "default" without further modifications like : indentation or \textstyle is technically wrong.
Using <math display="inline"> or <math>\textstyle for each inline formula makes the source code difficult to read and type.
New editors are confused by the "default" layout. They expect one notation for inline and one for block formulas with the inline markup using textstyle by default.
Some editors might not be familiar with the textstyle and displaystyle commands since they are used to LaTeX, MathJax etc. choosing it automatically.
Some editors do not bother to select textstyle explicitly, especially if there are only marginal differences e.g. $\textstyle e^{x}$ vs $\displaystyle e^{x}$ .
Editors using the VisualEditor cannot create block formulas with : indentation and can get frustrated trying to get a comparable layout example
: is a definition list that creates invalid HTML and can be annoying for screen readers. It also creates its own paragraph <p> which is technically wrong and leads to inappropriately large separations in some browsers/devices.
Having two markups for block formulas, i.e. :-indentation and display="block" parameter creates inconsistent layout. For most browsers/devices the visual appearance of both is only similar in the English Wikipedia due to common.css.
The optimal layout of block equations depends on other layout choices such as placement of figures which can be different for mobile devices. Editors should not hard-code those choices manually e.g. by number of :-indentations. Instead, indentation would be with respect to the surrounding text without creating surplus indentation if block equations are chosen to be centered.
Some more advanced features such as a referencing/numbering system for block equations and automatic line breaking require a clear distinction between inline and block-equations.

Some alternatives to this solution

Alternatives that were discussed in the survey:

creating new HTML-tags or keywords for inline and block equations and <math> retaining its behavior,

a solution which got slightly less support and people indicated that they regard it as the second best choice only. Alternatives that got mostly oppose-votes were:

keeping the :-syntax for block formulas and trying to work around some of the issues
solutions that involve templates

Some technical problems that hinder implementing the solution

If people are interested I am happy to write and discuss these further. I don't expect much progress here and it is only worth discussing if the general intention of the proposal receives enough support.

And last but not least: I don't have any experience with Rfcs and the conventions here. Feel free to change things I did wrong and notify people that might have some opinion on this matter.--Debenben (talk) 19:56, 5 February 2018 (UTC)[reply]

@Debenben: We discussed this topic recently. Please review WP:Village pump (policy)/Archive 138#RfC: Accessibility versus convenience in indentation. --Izno (talk) 20:20, 5 February 2018 (UTC)[reply]

And especially, the discussion I started at WP:Village pump (policy)/Archive 138#Math block display. --Izno (talk) 20:22, 5 February 2018 (UTC)[reply]

@Izno: You are right, I should have mentioned this previous Rfc. I got a ping from user:Whatamidoing (WMF) because I discussed the issue with him a year ago [5] and I also left a comment. I had the impression that the closing statement "Final note, since much of the opposition was related to the mode of resolving this screen-reader compliance problem, rather than the underlying idea of addressing the problem in the first place, it's of course all right for someone interested in the discussion to formulate a new proposal without waiting for days or months to pass." referred to my comment. Therefore the above focuses on addressing the problem without providing a technical solution. A possible technical solution (also solving other problems) would have been [6] but it did not get enough support. Still, if this proposal gets through it might encourage Media-Wiki developers to do something about it.--Debenben (talk) 20:52, 5 February 2018 (UTC)[reply]

I added the Question and RFC-template to the above in order to get more input.--Debenben (talk) 22:47, 6 February 2018 (UTC)[reply]

Survey: Change default <math> to be inline

Oppose. Surveys of English Wikipedia editors on English Wikipedia policy have no jurisdiction over Wikimedia technical formatting issues. The actual solution is up to the developers, but even if we wanted a survey of readers and editors to suggest better directions for the allocation of the developers' time, the correct place for that would be meta because this affects all Wikimedia sites not just this one. But regardless of all that, this proposal would break the formatting of all displayed (on a line by themselves) equations on Wikipedia. That's a lot of damage in exchange for very intangible benefits. —David Eppstein (talk) 23:42, 6 February 2018 (UTC)[reply]
Changing is not a good idea, there must be 100000s or more pages that would need to be altered. It would cause such a huge mess, including in the knowledge of the people that use the tag. Graeme Bartlett (talk) 00:47, 7 February 2018 (UTC)[reply]
Oppose unless benefits are clearer. Xxanthippe (talk) 01:47, 7 February 2018 (UTC).[reply]
Oppose. In principle this would have been a good idea, but formatting is already entrenched. Among many proposals to do with math formatting that English Wikipedia could decide to approach devs with, this has very minimal benefits. Sławomir Biały (talk) 11:16, 7 February 2018 (UTC)[reply]

Some remarks: For the survey in the German Wikipedia I did a rough estimate on the numbers of affected block-formulas: There were in total 237 779 occurences of math tags (in the main namespace), among those roughly 55 435 block-formulas. A simple algorithm similar to the one implemented in the old MathJax rendering mode or the one still existing today on scholarpedia, transforming all : indented math tags on its own line (without anything except for a space or punctuation mark) into a block formula would recognize around 82% of them correctly. The others have different number of indentations, text-elements or labels on the same line. They would get "broken" (meaning that they get an unconventional, less beautiful layout) and need to be marked as block formulas manually or by a bot using a more sophisticated algorithm. I guess there would be a slightly higher percentage of block formulas on the English Wikipedia and the total number would roughly scale with the article count.

For all those oppose votes I would be interested in their preferred solution. As I said, the alternative of introducing new tags (something like <imath> <dmath> <ichem> <dchem>) and avoid breaking the current math formatting had only slightly less supporters. A similar solution that involved creating a new markup for inline formulas was proposed on phabricator around 2012, but blocked due to the lack of community support. The WMF has no view on the issue, currently all development and maintenance of the math extension is done by one volunteer.--Debenben (talk) 14:00, 7 February 2018 (UTC)[reply]

I think the ideal solution would be to implement  and \[ \] as math delimiters. This would also solve the most recent problem of the non-accessible way that Wikimedia interprets the colon operator as part of a definition list, when the colon is used for indentation of inline equations. Sławomir Biały (talk) 19:47, 7 February 2018 (UTC)[reply]

That is probably the dream of every mathematician and LaTeX fan. It would need an equally strong concensus and I would be concerned that other people don't like it. Like: If you ask for too much you don't get anything.--Debenben (talk) 15:58, 8 February 2018 (UTC)[reply]

On the contrary, I think the approach solves a lot of problems we've been having lately. Offer the developers and editors a solution and they might implement it. Think big! Sławomir Biały (talk) 19:41, 8 February 2018 (UTC)[reply]

Just as a more "stupid" idea: What you suggested would already work today: $\sum_{n=0}^\infty \frac{x^n}{n!} \text{this should become inline}$ and \[\sum_{n=0}^\infty \frac{x^n}{n!} \text{this should become block}\] if one would simply write something like

$("head").append("<script type=\"text/x-mathjax-config\">MathJax.Hub.Config({'HTML-CSS': {preferredFont: 'STIX', webFont: 'STIX-Web', mtextFontInherit: true}, 'SVG': {mtextFontInherit: true}});</script>");
$("head").append("<script type=\"text/javascript\" async src=\"https://cdnjs.cloudflare.com/ajax/libs/mathjax/2.7.2/MathJax.js?config=TeX-AMS_HTML\"></script>");

into Mediawiki:Common.js. --Debenben (talk) 21:40, 8 February 2018 (UTC)[reply]

Fairly easy in principle to implement, I'll grant. Sławomir Biały (talk) 01:16, 9 February 2018 (UTC)[reply]

True. I improved the configuration a little:

$("head").append("<script type=\"text/x-mathjax-config\">MathJax.Ajax.config.path['mhchem'] = 'https://cdnjs.cloudflare.com/ajax/libs/mathjax-mhchem/3.2.0'; MathJax.Hub.Config({TeX: { extensions: ['mediawiki-texvc.js', 'AMSmath.js', 'AMSsymbols.js', '[mhchem]/mhchem.js'], equationNumbers: { autoNumber: 'AMS' }, mhchem: { legacy: false }}, displayAlign: 'left', displayIndent: '2em', 'HTML-CSS': {preferredFont: 'STIX', webFont: 'STIX-Web', mtextFontInherit: true, linebreaks: { automatic: true }}, 'SVG': {mtextFontInherit: true, linebreaks: { automatic: true }}, 'CommonHTML': {mtextFontInherit: true, linebreaks: { automatic: true }}});</script>");
$("head").append("<script type=\"text/javascript\" async src=\"https://cdnjs.cloudflare.com/ajax/libs/mathjax/2.7.2/MathJax.js?config=TeX-AMS_HTML\"></script>");

I think cloudflare wouldn't mind if we use their servers since they get an easy way to track all readers, but it probably violates some guidelines. Does anyone have access to something like a Wikipedia-toolserver that he can spare, so we can have our own cdn? I would be really looking forward to present some of the new features:

Working math also for devices like Ipads (In case someone is interested delivering the good news to the poor guy [7])
Working textmode, especially for all languages that don't use latin charakters
Working mhchem package
Copyable formulas, proper HTML
Fully editable in the VisualEditor (unfortunately the alpha version is lacking support for the visual formula editor)
Support of automatic referencing and numbering, support for linebreaking, support for missing commands like \middle
Support for defining macros, linking websites, popups etc. (Some of those features should probably be disabled in production)
Great user support, if you find a bug and report it at Github you probably get a patch within days

--Debenben (talk) 18:55, 9 February 2018 (UTC)[reply]

Ahh, and I forgot: An excellent accessibility explorer, where you can navigate through the formula with arrow keys and any average screen-reader can read out the generated text piece-by-piece.--Debenben (talk) 19:01, 9 February 2018 (UTC)[reply]

@Xxanthippe: I wanted to avoid a lengthy explanation because I was hoping for other peoples comments to highlight some of the current problems. Since this is not the case and you explicitly asked for the benefits to be clearer, I will attempt to illustrate some of the bullet points above:

A lot of inline formulas use the "default" layout, usually because the editor did not bother to specify it or is not familiar with the \textstyle command. For example if I write

A^{T}

, then for me, if I use a standard setting in firefox in combination with the svg rendering that most people get, the expression is just a little bit too large to fit into a normally spaced line, therefore the spacing of the lines in the text is not equal but a little bit different. For most people this is only the case for larger operators like

\sum _{i=0}^{\infty }

. This can be avoided by using the correct inline formatting, either by adding \textstyle or the parameter display="inline", resulting in

\textstyle A^{T}

or

\textstyle \sum _{i=0}^{\infty }

. If you happen to have a browser/device where the

A^{T}

example already uses a little bit too much space, then for you there will be more inline formulas that would get fixed by the change than those that get broken. Of course adding an additional \textstyle or the parameter display="inline" for all inline formulas would already be possible today. However the wikitext would become increasingly hard to read. In the survey I used the example of w:de:Satz des Pythagoras having three sentences with seven inline formulas each, where you don't want to clutter the source code with \textstyle or display="inline" parameters for each of them. Pythagorean theorem has a similar amount of inline formulas, however they are, probably due to other deficiencies, not using math-tags. That is what I wanted to express with the flawed "slightly higher percentage of block formulas" comment above. If you had a math extension were formulas are copyable, look good etc. for everyone, then you would want to use inline math for each of them. With the proposed change, editors could forget about \textstyle or display="inline", because it would have the correct formatting by default. This is the behavior people outside of Wikipedia would expect and how it works in LaTeX or any other typesetting system. The reason it is different in Wikipedia is, that originally the math extension was not designed for inline formulas, but as a replacement for images and ascii-art block formulas. Because a lot of mathematical expressions cannot easily be obtained with normal HTML-characters, editors also used the math extension for inline formulas, even though it did not have proper size or alignment for the text (and today this is still a problem, at least for a lot of browsers/devices).

Since the original idea behind math was to create images, and you would want to be able to use those images for example in tables etc., it did not have a proper layout for block equations either (and today this is also still a problem). Editors used the : markup because it is the easiest. However it is part of a definition list markup and produces invalid HTML. As far as I know it gets indented in every major browser, but in principle the layout of a definition list can be anything and the behavior of an invalid definition list is undefined. When I select "print this page" in firefox, everything indented with : gets printed with a large font size, which I guess is due to broken definition lists. An average screenreader would tell you for every :-indented block-formula that a definition will follow, which I guess can be annoying, especially in the middle of a sentence. The other thing that is wrong is the paragraph <p> that gets created, which means that there will be a space before and after every block formula that matches the space of a new paragraph in the text and depending on the browser/device can be inappropriately large. It is also semantically wrong, because the whole point of indenting or centering block formulas is to show readers that the early line-break is not a new paragraph, but just for accommodating a large expression that cannot easily wraparound into the next line. With the proposal above, those 82% of block formulas (or whatever the exact percentage on the English Wikipedia is) would get proper HTML like the one you get on websites like math.stackexchange that is not broken, does not abuse definition list markup or create a new paragraph. The others would get proper HTML if they get fixed manually or with a bot.

Another problem concerns editors unfamiliar with the wikitext or LaTeX markup. I cannot tell first-hand, but only from looking at strange edits of new accounts or when they ask for help. Imagine you are unfamiliar with wikitext-markup. Then you would assume that you can use the VisualEditor to edit mathematical articles. You effectively cannot because you can't add :-indentations or change them. However you would not know what those indentations are. You click on an equation that is clearly an inline equation and it will show you that it is "default". Maybe it begins with \textstyle - a command even some mathematicians or physicists don't know because normally it is not needed in LaTeX. If you click on inline - nothing happens. If you click on "block" you generally get a block formula that is centered (and the English Wikipedia uses commons.css to make it indented, solving this issue and creating different problems). If you want to edit another block formula - it is also "default". If you create a "default" formula yourself you cannot get it indented. With the proposal above this would get fixed, because there would only be one inline and one block option to choose from, and if you add a new formula and don't select anything it would be a correct inline formula. If you select block formula, it would become a true block formula. I believe it would especially help people not familiar with LaTeX because they could use the formula editor of the VisualEditor, since the formula is rendered or the error message is shown immediately. They also wouldn't need to search for a formula they want to edit in the source code, where you often rely on searching for generic LaTeX commands or words somewhere next to it.

These are the main points. As you can see from the bullet points above, there are some other (in my view minor issues) that would get solved. There is also a whole bunch of things problematic with current usages of the display="block" parameter which I have not touched. Since this fortunately only concerns 165 pages at the moment I have left this out for now.--Debenben (talk) 15:58, 8 February 2018 (UTC)[reply]

Oppose anything that would break the formatting in thousands of existing pages. Maproom (talk) 08:07, 9 February 2018 (UTC)[reply]

I don't know what I did wrong: I did not expect only support votes, but I expected some comments and discussion on the issue. I'll try to discuss with myself the comments so far:

Its a global issue: True. The purpose of this Rfc is to gather feedback directly from editors affected by such a change that can be used (e.g. in a discussion on meta) to supplement the feedback I got from German Wikipedia and Wikisource editors. So far I get the impression that the English Wikipedia editors just don't care.
It's up to the developers: As I pointed out, I had a discussion with Whatamidoing. For now it seems, the WMF does not have any resources to spend on working out a solution or fixing some of the problems.
The proposal breaks a lot of block formulas: True, although I think "breaking" is a strong word for a less beautiful layout for some equations which is compensated by a more beautiful layout for others. I respect people that do not want the existing articles to change at all. For the math tag this essentially means it cannot get fixed (unless someone can come up with a miracle solution nobody has thought of so far). Consequently this translates into the alternative, which is support for introduction and migration to a new notation.
It causes confusion among the editors: I would say this proposal would rather reduce the confusion. The argument of creating even more confusion was the main reason why at the German Wikipedia this solution was preferred to the alternative of creating a new notation. Editors can continue to use "default" in the text and get the proper inline formatting. If one is worried by a solution that would treat the indentation markup as a modifier as opposed to also replacing those 82% with a bot: This is not part of the proposal and (in my view) can be discussed after it is decided if the current <math> notation should be rescued or not.
The benefits are unclear: This could be a reason why people don't want to vote on the issue, but please leave a question or comment, this would help others to make up their mind.
Introducing  and \[ \] as math delimiters: A great solution. Some background: The two delimiters are the minimal set of LaTeX commands required to get all necessary features. For those that wonder about commands like ref, eqref etc: They can be used inside the delimiters like it is done for align today, which, from a LaTeX (and MathJax) point of view is correct, only a bit more complicated than necessary:

The example
\[\begin{align}
one \label{thefirstlabel}\\ 
two \label{mysecondlabel}
\end{align}\]
as a fraction 
\[\begin{equation}
\frac{\eqref{thefirstlabel}}{\eqref{mysecondlabel}}=\frac{ne}{tw} \label{theresult}
\end{equation}\]
does not make sense. Also, equation \(\ref{theresult}\) does not show that \(\ce{H2O}\) means water.

When adding the javascript above to common.js and removing the syntaxhighlight it already works today. The drawback: This is similar to what was proposed around 2012. I am especially worried that it will be me, having to convince people that mixing the HTML-like wikitext notation with LaTeX commands is worth it and that at the end of the day I have wasted even more time with discussions and achieved nothing.

A question which did not come up: What does it have to do with MathJax? In principle nothing, because all the problems mentioned in the bullet points are caused by the notation and don't get solved by a new rendering system. I wanted to show how other websites handle it, that Wikipedia is essentially the only website with these problems and some features necessary for being able to convert all current block-formulas. There is some hope: The Mathjax-Node spin-of currently generating the svg images and MathML in Wikipedia will be eaten up by MathJax version 3.0 in the future, creating the possibility that some developers take the opportunity to get MathJax 3.0 fully implemented in MediaWiki.

--Debenben (talk) 16:14, 12 February 2018 (UTC)[reply]

Oppose for reasons given. I have not done much (any?) editing along these lines, but would have little or no objection to a new format if it has any clear benefit, even in moderately unusual situations, but not as a new default. It would have to be a newly added facility and would be up to those benefiting, to discover the documentation. JonRichfield (talk) 05:14, 14 February 2018 (UTC)[reply]

RFC: Should Wikipedia have lists of transportation service destinations?

Please consider joining the feedback request service.

An editor has requested comments from other editors for this discussion. This page has been added to the following list:

Wikipedia policies and guidelines

When discussion has ended, remove this tag and it will be removed from the list. If this page is on additional lists, they will be noted below.

Should we update WP:NOTDIR to explicitly state that lists of transportation service destinations are outside the scope of Wikipedia? What is the relationship between WP:NOTDIR and WP:GNG for transportation related lists? BillHPike (talk, contribs) 23:50, 9 February 2018 (UTC)[reply]

Background

For transportation services, we have many lists of verbose lists of destinations served by transportation services:

In a recent VPP dicussion, a consensus was reached that it was not appropriate for Wikipedia to have lists of airline destinations (special:diff/821923737). In that RFC, the closer noted that, per WP:NOTDIR, these lists were inappropriate. In a related AfD, Spartaz closed by noting that, like WP:BLP1E, WP:NOTDIR supersedes WP:GNG. BillHPike (talk, contribs) 23:50, 9 February 2018 (UTC)[reply]

Notifications

Previous RFCs on this topic has been impacted by canvassing. For transparency, please only leave neutrally worded notifications and list them in this section.

User talk:Spartaz notified by BillHPike (talk, contribs) 23:57, 9 February 2018 (UTC)[reply]
Message left at Wikipedia talk:WikiProject Airlines left by BillHPike (talk, contribs) 00:12, 10 February 2018 (UTC)[reply]
Message left at WT:WikiProject Streetcars BillHPike (talk, contribs) 00:16, 10 February 2018 (UTC)[reply]
Message left at WT:WikiProject Stations BillHPike (talk, contribs) 00:20, 10 February 2018 (UTC)[reply]
Message left at WT:WikiProject Rapid transit BillHPike (talk, contribs) 00:24, 10 February 2018 (UTC)[reply]
Message left at WT:Wikiproject Trains BillHPike (talk, contribs) 00:26, 10 February 2018 (UTC)[reply]
Message left at User Talk:Beeblebrox BillHPike (talk, contribs) 00:32, 10 February 2018 (UTC)[reply]
Message left at WT:WikiProject Buses BillHPike (talk, contribs) 00:48, 10 February 2018 (UTC)[reply]
Comment left at WP:Deletion review/Log/2018 February 9#Adria Airways destinations BillHPike (talk, contribs) 00:56, 10 February 2018 (UTC)[reply]
Comment left at WT:What Wikipedia is not per suggestion of User:Kusma BillHPike (talk, contribs) 08:13, 10 February 2018 (UTC)[reply]
Message left at WT:WikiProject Lists BillHPike (talk, contribs) 08:19, 10 February 2018 (UTC)[reply]
Message left at WT:Notability. BillHPike (talk, contribs) 02:37, 12 February 2018 (UTC)[reply]

Comments

Strongly oppose if what this poorly-worded RFC is actually proposing—as it appears to be—is a ban on mentioning on where a transport firm operates, or lists of routes from an individual station. Particularly when it comes to railways, the routes operated by any given firm are essential to an understanding of that firm (especially in a fragmented market like the UK, where key routes like London–Birmingham and London–Edinburgh are served by multiple operators using different routes); likewise, the services which run to and from any given station and how those services have changed over time are essential to an understanding of the significance of that station. That doesn't mean we have to include such lists if they're not appropriate, but articles about transportation—a topic which varies wildly both from country to country and within individual countries—are pretty much the poster children for "decisions which should always be made on a case-by-case basis". Aside from anything else, even the tightest interpretation of this proposal, as "only delete pages which have titles in the format [[List of destinations served by...]]"—would wipe out (at the time of writing) 24 Featured Lists. ‑ Iridescent 00:28, 10 February 2018 (UTC)[reply]
(adding) I'll also point out—as it seems to have slipped your mind—that mass deletion has literally just been declared inappropriate in this context with a consensus that these should be dealt with on a case-by-case basis. When a decision is reached that you don't like, it's usually good form to at least wait a few days before forum-shopping to try to get it overturned. ‑ Iridescent 00:39, 10 February 2018 (UTC)[reply]
Comment -- A peak at the 2011 backlog of unreferenced articles shows hundreds of Japanese railway stations and trolley stops. The current count of unreferenced rail transport articles is 22,554 [8] , a tenth of all the unreferenced articles in the English language Wikipedia. I'm not sure why this category gets a pass, when high schools lost the presumption of notability that required only one (1) reference.

Lists of airline and bus destinations will be outdated the day after they are edited. They are simply a waste of Wikipedia resources and editors' time. Rhadow (talk) 00:34, 10 February 2018 (UTC)[reply]

WP:SOFIXIT. The category itself is full of articles that have had references added but did not have their talk page templates updated (e.g. Akabuchi Station and 39th Street (Sacramento RT)), so I would not use it for an accurate count.
In developed cities, bus routes may go unchanged for years, if not decades, but notability will need to be discussed on a case-by-case basis. Some systems even have articles for individual bus routes that clearly pass notability, e.g. Route 41 (King County Metro), so they should not be judged so broadly. Sounder Bruce 07:22, 10 February 2018 (UTC)[reply]

Regarding The current count of unreferenced rail transport articles is 22,554, Category:Unreferenced rail transport articles is obviously inaccurate. Looking at the first three articles on that list, they're all referenced; it appears that the tag which adds "this article lacks sufficient inline citations" (my emphasis) to the talkpage (e.g. a specific fact is uncited) is categorising the pages as being completely unreferenced. ‑ Iridescent 09:37, 10 February 2018 (UTC)[reply]

Moral support because it appears to be the opinion of many editors that community consensus only counts if it is codified into policy. However, I would need to see specific wording in order to support fully. The phrasing should allow, for instance, lists of destinations of historical companies and perhaps destination lists embedded within articles. AdA&D ★ 00:38, 10 February 2018 (UTC)[reply]

On another note, I fear this situation turning into a trainwreck with a simultaneous DRV taking place. Suppose the DRV results in overturn then this RFC succeeds. What then? AdA&D ★ 00:46, 10 February 2018 (UTC)[reply]

AdA&D, you are right. Editors ignore the results of RfC. We need a policy here. Case-by-case has been abused. Rail is different from bus, ship, and airline, whose routes can change daily. A train station requires concrete. A train station article should require independent reliable press coverage, else it is not notable. It can go in a list of stations on the line. As to the modes of transport not tied to a fixed origin-destination pair, that's basically a schedule and doesn't belong. Any edits will be out of date the next day. Let the article point to the subject's schedule website. Rhadow (talk) 00:49, 10 February 2018 (UTC)[reply]

Procedurally, I believe that DRV should be overturned. The entire procedure of that RfD/AfD/DRV has been bizarre from start to finish, was too limited in scope to be true policy, and is why we're here now. If we decide here transport destination articles aren't encyclopedic, we reopen the deletion discussion - I'll even side with deleting those lists if consensus exists. What's important to me is deciding when and how this information gets displayed. SportingFlyer (talk) 02:19, 10 February 2018 (UTC)[reply]

Oppose The proposer fails to provide any justification for this blatant bias and it is our policy that Wikipedia is not censored. People who don't like planes, trains and automobiles should please read about whatever it is that interests them instead. Per WP:NOTPAPER, there is plenty of room for any number of topics. Andrew D. (talk) 01:05, 10 February 2018 (UTC)[reply]
Speedy Close - We need to wait for the DRV to finish before we start on something like this. - Knowledgekid87 (talk) 01:11, 10 February 2018 (UTC)[reply]

Nah. If we wait for the decision on a single article, we'll never get to the policy discussion. There will always be "one more discussion" to finish before we tackle the big issues. Rhadow (talk) 01:18, 10 February 2018 (UTC)[reply]

@Knowledgekid87: A major argument made in the deletion discussion was that the previous RFC was binding. I think it is best for us to have an RFC to update the policies so we can avoid wikilawyering at AfDs and DRV. BillHPike (talk, contribs) 01:20, 10 February 2018 (UTC)[reply]

This is a mistake though in my opinion as these are three huge topics. I would be fully opposed to railroad stations as they are more concrete in history and notability. - Knowledgekid87 (talk) 01:30, 10 February 2018 (UTC)[reply]

Knowledgekid87, please clarify what you mean by "I would be fully opposed to railroad stations." Right now, there are several thousand railway station articles without a single reference. What do you favor? Rhadow (talk) 01:36, 10 February 2018 (UTC)[reply]

Those are article fix up issues that can be handled on a case by case basis as would any normal AFD go. - Knowledgekid87 (talk) 01:39, 10 February 2018 (UTC)[reply]

Case-by-case is fine for specific and rare cases. The problem with railway articles is systemic. It is pervasive. There are 22,554 of them. If I nominate five of them, the railroad cabal will jump on this girl like a scrum. Rhadow (talk) 02:07, 10 February 2018 (UTC)[reply]

Would you mind linking an example railway article? SportingFlyer (talk) 02:11, 10 February 2018 (UTC)[reply]

Akechi Station (Ena), Akechi Station (Kani), Aki-Imuro Station, Aki-Nakano Station, and Akiaga Station are all examples of unreferenced railway articles. Ainoki Station is in the list of 22,554. The others aren't. Rhadow (talk) 12:06, 10 February 2018 (UTC)[reply]

First, thanks for the links - second, it appears the proper procedure with those articles would be to add references, not to delete them because they don't have references. SportingFlyer (talk) 19:17, 10 February 2018 (UTC)[reply]

By contrast, SportingFlyer, it's easy to look on a JR schedule, add the article, then challenge others to find a reference when the article is PRODded. It is up to the creating editor to back the article up with references. Try PRODding any one of those. Likely it will be reverted. If you take it to AfD, you will be attacked for an insufficient BEFORE, then magically, a printed book in Japanese will appear in the references (the same book as for a neighboring station). It's not my desire to delete good work willy-nilly, but to see that rail fans and airline fans -- and school fans like me -- contribute well-referenced material, not just to make fun lists. Rhadow (talk) 15:15, 11 February 2018 (UTC)[reply]

From an airline perspective, I don't see adding where an airline flies to as a "fun list." An airline schedule, or a list of airline routes, is clearly uncyclopaedic: that's not what we're fighting for, though! I don't have any problem with a list of train routes, either. They don't need to be blue-linked to be notable; a list of stations could be easily referenced, and indeed Wikipedia even has train route diagram templates. SportingFlyer (talk) 21:08, 11 February 2018 (UTC)[reply]

Strong oppose and ask for speedy close. A broad, sweeping change like this one should not be discussed without a firm case. Railway station lists are widely accepted as having encyclopedic value (which is why they are accepted at WP:FL) and have purpose beyond being mere tourist guides. The stations themselves are individually notable and discussed as a group (in almost all cases), which fufils the requirements at WP:LISTN. At the very least, these lists should be judged on a case-by-case basis, with local editors providing input (unlike some AfDs that are crafted to avoid invovelment from knowledgeable editors). Sounder Bruce 01:23, 10 February 2018 (UTC)[reply]

Many lists individuals airline destinations pass WP:GNG and some lists of destinations were featured lists. If WP:NOTDIR bars lists of airline destinations, surely the same applies to lists of rail stations? I think we need to update our policies to clarify such situations. BillHPike (talk, contribs) 01:36, 10 February 2018 (UTC)[reply]

Hello SounderBruce -- The case against lists ... Oh, forget the lists, let's discuss the underlying articles for train stations and airports, for which there are thousands, an enormous number of which are completely unreferenced. In the case of Japanese trolley stops, you cannot even be sure that the photos (with Japanese signs) match the English text of the article. And now we want to make lists of every route? There is a small but vocal interest group here that fights for every station article. Is it encyclopedic? I argue no. Railway articles are ten percent of the unreferenced articles in the English language Wikipedia. Are ten percent of readers looking up trolley stops? I'll bet not. This group likes the status quo; they argue for a speedy close. No speedy close. Let's have the discussion. A little light on this dark corner of Wikipedia would do some good. Rhadow (talk) 01:51, 10 February 2018 (UTC)[reply]

I think you're onto something, but I think you're going off topic: this would create policy transportation destination lists violate WP:NOTDIR. A better example than train stations would be List of NSW TrainLink train routes. — Preceding unsigned comment added by SportingFlyer (talk • contribs)

Thank you for linking that, I would say that yes that article is comparable to the lists of airline destinations. - Knowledgekid87 (talk) 02:27, 10 February 2018 (UTC)[reply]

Even with a little work, almost every little train station can have a decent article. Either you create separate articles for each station, or you have a horrendously long article for each line that includes this information for each stop's surroundings, history, construction details, layout, public art, and nearby developments. For example, Tukwila International Boulevard station is little more than two platforms on stilts above a parking lot, and yet it easily met FA guidelines. The status quo was worked out long ago by discussions similar to this (which is why editors are sick and tired of this), and it's generally agreed that the current notability guidelines are sufficient for an encyclopedia that will never run out of paper. The proper forum is a non-binding discussion at the WikiProjects involved, or at deletion discussions for individual stations that are nominated. Not as something as broad and without depth as this. Sounder Bruce 02:57, 10 February 2018 (UTC)[reply]

This discussion should be specifically about lists of destinations, not about train stations. I believe the "lists of railway stations" is a mistake. SportingFlyer (talk) 03:34, 10 February 2018 (UTC)[reply]

I'm sure most of the members of WP:WikiProject Airlines would prefer to retain the list of airline destinations, but, as noted at the AfD, “cross project consensus on policy has more validity then that from a group of editors enthusiastic about a subject” and it is irrelevant that the lists “pass the GNG and are effectively useful”. We should either accept the same logic for other modes of transportation and update WP:NOTDIR, or overturn the previous consensus. BillHPike (talk, contribs) [[07:21, 10 February 2018 (UTC)[reply]

Oppose.~~I want to keep this information.~~ This is a badly needed discussion and has a large impact. First, there's a discussion going on regarding the lists of destinations on airport pages and how they should be presented. Second, there's a deletion discussion for lists of airline destinations. The policy at the last Village Pump discussion was limited to airline destination lists but if applied to other topics would have a large impact: as an example, those lists seem almost exactly similar to this article section: https://en.wikipedia.org/wiki/Great_Western_Railway_(train_operating_company)#Routes.

There have been several past deletion requests for airline destinations and they have survived every time.
First, railway stations and airports are similar as they are places. I think there's a lot of train stations which aren't notable, but they do exist in real life. For airports and railway stations alike, I believe where these places connect is worth including in list form, and is not directory information.
Train routes/destinations and airplane destinations also similar as they are not places. Train routes typically are fixed in place due to the nature of railways. Airline routes can change at any time, and I think many editors are having problems with this fact. However, airline destinations - which is what we have lists of - change rarely, and when they do, you almost always get verifiable third-party articles talking about added/dropped routes. Furthermore, we have lists of airline destinations for failed airlines, which will never need to be updated. We haven't had a problem maintaining this information for over a decade, and it's important in being able to show the geographic scope of an airline through time, arguably better than a narrative format. Furthermore, since where an airline flies is an important part of the airline, reducing these lists to a narrative format will cause problems: what constitutes a notable route worth mentioning?
I'd also like to see which other articles have been deleted for violating WP:NOTDIR. I view a directory as something which involves people: where they live, their phone number, their office number. These clearly don't. SportingFlyer (talk) 02:02, 10 February 2018 (UTC)[reply]

Comment: on an anecdotal level I remember an attempt about 10 years ago to delete a list of mediaeval monasteries based on WP:NOTDIR - like everything else on Wikipedia it's been misused by people pursuing their own agendas. Eustachiusz (talk) 14:40, 11 February 2018 (UTC)[reply]

Comment I find pretty unfair to have this discussion and, simultaneously, the one at DRV.--Jetstreamer ^Talk 02:12, 10 February 2018 (UTC)[reply]

I don't: I think the fact we need better policy shows the DRV needs to be overturned, at least for the time being. SportingFlyer (talk) 02:21, 10 February 2018 (UTC)[reply]

And someone realised we need a better policy after a DRV (the fourth instance of the discussion of articles including airlines destinations) was started? Even though we are in opposite sides of the AfD and the DRV discussion, I'm with Knowledgekid87 in this one.--Jetstreamer ^Talk 12:47, 10 February 2018 (UTC)[reply]

Well, destination lists keep getting AfD'd repeatedly, and they ultimately always get kept (it looks like this time as well). I hoped this discussion would help minimise the risk of another scrum in the future, but it's not really helping anything at the moment and should probably be closed. SportingFlyer (talk) 08:26, 11 February 2018 (UTC)[reply]

Oppose. First of all, this is the wrong venue to ask for deletion of these articles. If what you are asking for is a clarification of NOTDIR (so a change to WP:NOT), you should also post a notification at WT:NOT, the appropriate policy talk page. I find it difficult to understand why you single out transport-related lists. List of programs broadcast by Cartoon Network and List of Nestlé brands seem to be equally worthy of discussion. As to airline destination lists: like airline fleets, their destinations are an integral part of who they are, and both fleets and destinations receive frequent coverage in reliable sources. For other transportation, the List of London Underground stations is an important part of who they are. Some people have argued that we should just point to the transportation providers as sources for the information. That is fine for a travel guide (but Wikipedia is not one), but unacceptable for an encyclopaedia: we can (and should) give critical commentary and historical context for the list items. General-purpose encyclopaedias bound by paper-based restrictions may not have such lists, but detailed information can be found in specialised encyclopaedias, for example this one. Wikipedia is both a general and a collection of specialised encyclopaedias, and all of these lists are perfectly on topic. —Kusma (t·c) 08:05, 10 February 2018 (UTC)[reply]
Comment Some have argued for a speedy close of this RFC. However, Fish and karate and Spartaz, both respected administrators, have closed discussion by stating that WP:NOTDIR meant Wikipedia should not have these articles. Beeblebrox (talk · contribs) also deleted over 400 lists of airline destinations, stating that there was a community policy decision with a clear consensus and that if any other admins undid his deletions, they would wind up at ANI (see diff). It is clear that a significant minority of our community view these changes to WP:NOTDIR as simply codifying a status quo consensus, so our community should have a full discussion on this matter. BillHPike (talk, contribs) 11:48, 10 February 2018 (UTC)[reply]
- This discussion should then include the entire population of lists in Wikipedia, as WP:NOTDIR should apply to all of them. You and me know the result of that discussion well in advance.--Jetstreamer ^Talk 12:55, 10 February 2018 (UTC)[reply]
  - Describing Fish & karate as a "respected administrator" is stretching things somewhat—"legacy admin who has been inactive since 2008 and logs in once or twice a year to avoid losing the tools automatically" would be nearer the mark. What you fail to mention is that, while Beeblebrox did indeed threaten that anyone who challenged his unilateral supervote would wind up at ANI, it was, challenged, did wind up at ANI, and the consensus was overwhelming that his deletion was inappropriate. ‑ Iridescent 15:22, 10 February 2018 (UTC)[reply]
Comment -- I have concentrated previously on rail stations. I used the category of unreferenced rail articles as my guide. The counterargument is the category is out of date. As I demonstrated earlier, while the category is out of date, it is also incomplete. The alternative now is to approach individual articles on a case-by-case basis, which will be a tremendous waste of time. It can be done.

As to lists of airline destinations, the problem is best discussed in terms of database architecture. When two tables purport to have the same information, one of them will always be wrong. Take JetBlue destinations for example. It has more than one hundred entries. There are only twenty-three references. The same information is duplicated at John_F._Kennedy_International_Airport#Passenger where only two destinations have citations. A portion of the destination list is found at JetBlue#Mint. Databases are now constructed in third normal form, so that an entry needs to exist only once. A correction made once fixes once every place the entry appears. Perhaps someone is looking after JetBlue. I doubt the same care is being taken with Emirates.

In all of these cases, the bar to entry is low and the cost to correct or delete is high. The transportation fans have staked out their ground, often ten years ago, when article standards were lower. Now they ask for case-by-case review. At AfD, the defense is fierce. Only if we have a reasonable policy can this turned around. Else we are looking at another decade of original research articles plugging up the unreferenced backlog. Rhadow (talk) 13:05, 10 February 2018 (UTC)[reply]

I'm in favour of keeping the articles, and I'm perfectly aware of the current article standards, as I've taken (with or without help) several articles to GA status.--Jetstreamer ^Talk 13:27, 10 February 2018 (UTC)[reply]

Oppose per Iridescent. I would also note that the language is far too sweeping and would be more likely to cause confusion and problems than solve them. Dennis Brown - 2¢ 14:10, 10 February 2018 (UTC)[reply]
Summary of opposition arguments thus far

RFC not specific enough ("too sweeping")
Deal with unreferenced articles on a case by case basis
Category:Unreferenced rail transport articles is obviously inaccurate.
The issue is not tranportation-related, but a general discussion of WP:NOTDIR
WP is not printed, therefore no limitation is required
Wait till the Adria Airways DRV is completed

All of these objections are deflective; none addresses the matter of the airline destination lists themselves. Only one objection addresses the matter directly. Airline destinations are a crucial description of the purpose of an airline. Is it international or domestic? What freedoms of the air does it exercise? How do these routes demonstrate economic and social ties?

The policies surrounding lists are stretched when these lists are unreferenced. In the area of schools, to include an alumnus, the list member must be notable (blue-linked) AND have a citation demonstrating that the member is an alum. The same can apply to transport lists. Airports are notable. To get on a destination list, there should be a reference. Rhadow (talk) 15:52, 10 February 2018 (UTC)[reply]

- That is silly. Claiming the RFC is too broad and sweeping is as valid a reason as any. If someone wanted to change policy to "all bad edits should be reverted", I would say the same thing: it is too broad and sweeping. An RFC to change policy has to state the problem, explain why it is a problem, provide the solution and offer a degree of protection from collateral damage. Since this doesn't do that, it is comical that you think opposition should be dismissed out of hand. Your "conclusion" shows why you shouldn't be closing discussions. Dennis Brown - 2¢ 17:24, 10 February 2018 (UTC)[reply]
  - Not to mention that this discussion not coming to and end is somewhat disrupting Wikipedia. As many others, I am a contributor to airline destinations articles, for which all my contributions are impeccably sourced, but I'm not making any edits to them in view of the possibility (rapidly vanishing, though) that these articles will be deleted. I don't want to waste my time in such situation.--Jetstreamer ^Talk 17:41, 10 February 2018 (UTC)[reply]

Hello Dennis Brown, Jetstreamer -- This discussion is not twenty-four hours old and you claim that by its protracted nature, it is disrupting Wikipedia. You like the status quo. I get that. Calling my thinking comical is not contributing to that discussion. I looked at El Al destinations. It's great. It's not like JetBlue destinations, John_F._Kennedy_International_Airport#Passenger, or United_Airlines_destinations. Here is a simple solution: agree that a destination must be notable (easy) and that any edit needs a reference. In the airline realm, I don't think that's too much to ask. No one is likely to touch Pan Am destinations. When a destination list includes an unreferenced trolley stop or bus shelter, that's when we say no. But if we agree, then the no must be firm and not subject to special pleadings. Otherwise, someone will add the Moon to the Pan Am article ... and come up with a dodgy reference. We've gone through the same thing with the cricket fans who insisted on retaining articles about players who played in one game, for whom no one knew their first name, and for whom there was no press coverage. Those articles are going. The bad lists of destinations need to be improved or go. That's my two cents. Rhadow (talk) 18:41, 10 February 2018 (UTC)[reply]

I said no such thing. Please retract or strike my name as your statement about my "claim" is pure fiction. Dennis Brown - 2¢ 11:09, 11 February 2018 (UTC)[reply]

This type of discussion has stretched on for weeks now in RfCs, AfDs, and deletion reviews. SportingFlyer (talk) 19:10, 10 February 2018 (UTC)[reply]
Furthermore, with regards to destination lists, you shouldn't include only notable destinations: "notable" is meaningless in that case. A list should either be exhaustive or not exist. The destination itself doesn't need to be notable; we don't need to blue-link everything. SportingFlyer (talk) 19:14, 10 February 2018 (UTC)[reply]

As to trains, I've seen articles for some Indian routes that even included schedules, which is something I definitely oppose. As one of the strongest enforcers of WP:VERIFY (at least in the airline-related field) I totally agree with the inclusion of reliable references. As many more, I'm not a fan but an editor, and have plenty knowledge of the content policies. We have, on the other side, occasional contributors that think this is a fansite and make all kind of changes in line with anything but an encyclopedia, likely because they are not familiar wih our policies but pretty familiar with the fact that anyone can contribute; the solution relies on reverting, protecting, or discussing the matter at the corresponding talk page, but not on extraneous interpretations of the policies. One thing is for sure: proposing the deletion of these pages will not solve the problem, as it won't at many, many other topics. The discussion regarding airlines destinations should stop at some point, here or elsewhere.--Jetstreamer ^Talk 20:42, 10 February 2018 (UTC)[reply]

@Dennis Brown: An RFC to change policy has to...

state the problem, ... Many respected users, including several admins, interpret WP:NOTDIR as mandating the deletion of lists of transporation service destinations, notwithstanding WP:GNG
explain why it is a problem, ... A significant number of users feels that the above users are misinterpreting policy.
provide the solution ... I’ve proposed two solutions: The first solution is to update WP:NOTDIR to explicitly state, that for lists of transportation service destinations, NOTDIR both disallows these lists and supersedes GNG. The second solution is for our community to come to a consensus that some users are incorrectly interpreting NOTDIR to delete articles they don’t like.
and offer a degree of protection from collateral damage Each of the two solutions offer the same protection from collateral damage that each of the existing interpretations NOTDIR already provide. BillHPike (talk, contribs) 22:21, 10 February 2018 (UTC)[reply]

I could pick it apart, but suffice it to say that there is a lot of conjecture here (admin's opinions don't carry any extra weight on interpretation, btw). It isn't that I'm in love with these lists, but I'm less in love with your solution. Dennis Brown - 2¢ 11:20, 11 February 2018 (UTC)[reply]

Jetstreamer is worried about the notability of airports listed in airline destination lists. I venture to guess that all international airports have blue-links. Where train stations are concerned, the path is tortuous. I nominated Akita-Shirakami Station for deletion. It had been unreferenced since 2006. Under my proposal, had it been deleted, it would have been ineligible for a destination list. Two references in Japanese were promptly provided with the argument that the subject had the "same notability as all the other stations on this line." Same is not necessarily sufficient or significant coverage. I cannot be sure that the two books provided include sufficient or significant coverage. The other article includes a mention of the station, not a discussion of it. Certainly it exists. I doubt whether the station is noteworthy in a general Wikipedia sense. I am quite sure, however, that no one party to this discussion wants to go through an AfD for 22,558 articles (or however many there truly are). And I was right, editors did pile on the AfD like a scrum. Rhadow (talk) 12:06, 11 February 2018 (UTC)[reply]

Oppose this proposal seems overly broad. I think it would mandate that we would have to delete, say, List of London railway stations. This is a natural grouping of notable topics, it has obvious navigational value, and I don't see how it's in any way unencyclopedic. I'm sure there are cases where lists of transportation destinations fall foul of WP:NOT, but introducing a sweeping rule like this is not the way to deal with them. And I agree this is the wrong venue, the right place to suggest policy changes is the talk page of the policy. Hut 8.5 18:35, 11 February 2018 (UTC)[reply]
Oppose far too sweeping a proposal that would remove many good articles, each article has its own merits or demerits and need to be judged on a case by case basis Atlantic306 (talk) 19:47, 11 February 2018 (UTC)[reply]
Oppose. First, I don't think the RFC question is too broad or sweeping. I can perfectly well answer. No, WP:NOTDIR should certainly not state that lists of transportation service destinations are outside the scope of Wikipedia. Thincat (talk) 20:04, 11 February 2018 (UTC)[reply]
Oppose WP:NOT has become a means of giving teeth to WP:IDONTLIKEIT. Would prefer to see WP:NOT curtailed, not extended. Hawkeye7 (discuss) 21:14, 11 February 2018 (UTC)[reply]
Oppose. I really don't understand the opposition to lists that neatly summarizes information that lends itself to this kind of presentation. Removing these lists makes information much harder to find for a regular reader, and leads to a messier encyclopedia. Featured lists such as List of London Underground stations are not directories, and it requires a ludicrously pedantic reading of the NOTDIR policy to interpret it as such. Sjakkalle (Check!) 21:18, 11 February 2018 (UTC)[reply]

Meh... removing the lists may make it harder to find the information ON WIKIPEDIA... but the information is relatively easy to find elsewhere. That’s why the issue centers on WP:NOT. We don’t just present information for the sake of presenting it (because we can)... There are some kinds of information that Wikipedia leaves for OTHER websites. The question is: is this the kind of information we want Wikipedia to present (or not)? My reading of NOTDIR makes me lean towards saying “not”. Blueboar (talk) 23:05, 11 February 2018 (UTC)[reply]

Following your reasoning we may proceed with the removal of the entire project as the content of all Wikipedia articles can be found elsewhere, this encyclopedia is built by using external sources.--Jetstreamer ^Talk 00:00, 12 February 2018 (UTC)[reply]

Oppose - I changed my vote to oppose as this is way too broad of a proposal, as I said above I also believe that the DRV should close first. - Knowledgekid87 (talk) 00:48, 12 February 2018 (UTC)[reply]
Proposed wording A pharasing that would reflect how the previous dicussions have been interpreted would be to add the following to WP:NOTDIR

8. Lists of transportation service destinations. Wikipedia is not a collection of lists of transportation service destinations, such as lists rail stops, airline destinations, or bus services. Such articles should be deleted even if service to the destination passes other inclusion criteria such as WP:GNG.

See previous VP RFC close and AfD Close. I would personally be opposed to this change, but since several admins have indicated that they feel this wording represents the status quo, it is worth having a full discussion on clarifying the meaning of WP:NOTDIR. BillHPike (talk, contribs) 00:57, 12 February 2018 (UTC)[reply]

We are not discussing WP:NOTDIR's bullet number 8 because it does not exist at all. Presenting it this way is at least confusing and I strongly suggest to strike this text out.--Jetstreamer ^Talk 02:21, 12 February 2018 (UTC)[reply]

The proposed text would be inserted after WP:NOTDIR#simplelists and become bullet point number 8. BillHPike (talk, contribs) 02:29, 12 February 2018 (UTC)[reply]

How are these being claimed to meet the GNG? Or more specifically, while there are definitely a few routes on these lists that meet the GNG, the whole of the lists do not - sourcing doesn't appear to be independent nor secondary. --Masem (t) 02:45, 12 February 2018 (UTC)[reply]
Strong oppose I still have yet to see a compelling reason to remove these valuable, sourced, accurate, and informative pages from WP. We should be focused on building the project, not taking it down, no? Some of these are featured lists--and editors have spend a long time ensuring they are a valuable addition to the project. Tofutwitch11 ^(TALK) 02:50, 12 February 2018 (UTC)[reply]
Oppose per WP:CREEP. We don't need special rules to outlaw topics we don't like. Their notability should stand or fall like that of other lists. —David Eppstein (talk) 03:24, 12 February 2018 (UTC)[reply]
Oppose. I tend to think that many of the lists are notable, and in general that there are no issues with the usual AfD process for these lists if there are some that need to be deleted. Policy should not be this granular; issues like this should be interpreted at AfD. CapitalSasha ~ talk 04:14, 12 February 2018 (UTC)[reply]
Oppose many lists mentioned under this policy are lists of notable entries and actually help organise Wikipedia and make it easier to navigate. --Donald Trung (Talk) (Articles) 09:22, 12 February 2018 (UTC)[reply]
Oppose we have WP:NOTDIR...aaaand this isn't in it. We have WP:GNG. The proposal seems to be wanting to delete material which would otherwsie fulfil notability criteria. Which I don't agree with. Cas Liber (talk · contribs) 11:58, 12 February 2018 (UTC)[reply]

Comment Reading some of the discussion, I think we need to reapproach this. We can't group airline, train, and bus equivalently here. I do think that there is appropriateness of airports, train stations, and main bus terminal articles (these are fixed structures, typically built by tax money, so there's going to be attention given to them. Bus stops by themselves do not have the same aspect here.) The schedules however are much more transient which is the issue from the prior airline destination discussion - but this is more true for airlines and buses - trains you really can't change all that much, and hence why I'd not be surprised at volumes of books I could read on the London Underground or any major city's subway lines. I would say that - barring true GNG notability for an airline/bus route - where there is nothing that forces them to follow the same path - that their transient nature makes them inappropriate. --Masem (t) 14:33, 12 February 2018 (UTC)[reply]

I had argued for a speedy close earlier but now it seems like a lost cause. I fully agree that this discussion is too broad which should be the central flaw here. - Knowledgekid87 (talk) 15:08, 12 February 2018 (UTC)[reply]

Please consider List of MBTA crosstown bus routes -- which relies on a single source and whose content has not been updated since 2012. Better yet is the sprawl of New Jersey bus-route writing, which has required the creation of an article Lists of New Jersey Transit bus routes, which is a list of lists. Another egregious example is List of bus routes in Hong Kong, a 120,000 character article with one (1) reference. This is the future of a Wikipedia without a sensible standard for transportation-related lists. Rhadow (talk) 14:42, 12 February 2018 (UTC)[reply]

You really should read WP:PROBLEM. - Knowledgekid87 (talk) 15:20, 12 February 2018 (UTC)[reply]

Hello Knowledgekid87 -- Thank you for the reading I summarize as, "No article is beyond redemption." I interpret it as an excuse for "one bad apple." My point is that the family of articles List of bus routes in ... is a systemic problem, not just a couple of bad examples. List of bus routes in Lahore includes every route and every stop. It has two references. The rest is original research. List of Chennai Metropolitan Bus Routes has one reference, but every stop on every route. Some lists are very specific, an example is List of night buses in London, which includes stops as well as routes, and is a fork of List of bus routes in London. Sure, Knowledgekid87, none of these articles has an insurmountable editing problem. As a group, however, there is a big problem that allows low-quality articles like these. Rhadow (talk) 16:22, 12 February 2018 (UTC)[reply]

Hello Masem -- Perhaps the proposal should have been that all transportation lists are notable. Then the chorus would disagree. Here are a few examples that have been discussed in both academic works and in the popular media: Rhadow (talk) 16:59, 12 February 2018 (UTC)[reply]

Strong oppose Where a transportation company serves is relevant, and notable. It provides important context that is needed to understand the subject, not to mention it receives significant coverage in reliable sources. Arguments against basically boil down to WP:IDONTLIKEIT as people throw out irrelevant policies. Smartyllama (talk) 18:10, 12 February 2018 (UTC)[reply]
Oppose - Not only is the proposal overly broad, NOTDIR doesn't apply as these lists are very discriminate and very specific, not at all indiscriminate which is what NOTDIR applies to. There has been zero lessoning to encyclopedic value of WP as a whole since these have existed, which is basically as long as WP existed. These have only been complemental enhancements of this project. --Oakshade (talk) 03:55, 13 February 2018 (UTC)[reply]
Comment Please note that the discussion at DRV was closed as ″overturn″ [9].--Jetstreamer ^Talk 21:56, 18 February 2018 (UTC)[reply]
Oppose such a policy will degrade Wikipedia by removing potentially useful information. Graeme Bartlett (talk) 03:09, 19 February 2018 (UTC)[reply]

A different direction

Considering that the RFC above perhaps a bit too diffuse, I would like to propose (for discussion, no formal proposal) considering "permanence" when talking about transportation lists. In this frame, the following would very much likely be notable due to the fact that they typically are permanent structures and will have good documenting in local newssources about their cost of construction, changes over the years, etc.:

Roads (highways/interstates)
Train/subway stations
Train/subway lines (lists of stations a line serves, but not its schedule)
Bus terminals
Port/Ferry terminals
Airports, including hub airports for air carriers

While the following have too much temporal variation (they are not forced to travel a fixed route) and should not be considered appropriate for WP, unless one can show it meets the GNG. These are primarily only going to be sourcable to the agency running the service, and since they can be changed on a whim, difficult to document.

Bus route/schedules and intermediate bus stops, and lists thereof
Air route/schedules and destination cities, and lists thereof
Ship/ferry route/schedules and lists thereof.

How to put that into any type of policy or not, I don't know, but I'd like to open that up for discussion. --Masem (t) 16:32, 12 February 2018 (UTC)[reply]

Support - Any discussion that leads to a proposal to establish a line when it comes to "permanence" in transportation lists. Railroad stations aren't going anywhere anytime soon, but for airline destinations those are advertised and fall under schedules. - Knowledgekid87 (talk) 16:45, 12 February 2018 (UTC)[reply]

Would you support the removal of information about which trains services stops at specific stations? For example, service to Tacoma station is clearly ephemeral. BillHPike (talk, contribs) 16:50, 12 February 2018 (UTC)[reply]

Many specific flight numbers have served the same origin / destination pair for over 50 years and pass WP:GNG. It would be silly to carve out an exception to GNG to bar any reference to these flights, but keep entries on trivial rail stations. BillHPike (talk, contribs) 16:53, 12 February 2018 (UTC)[reply]

Lets get the lists sorted out before talking about article issues. Any proposal given should talk about what transportation lists are right/not right for Wikipedia to maintain. - Knowledgekid87 (talk) 16:55, 12 February 2018 (UTC)[reply]

Comment Airlines typically have more staff and more permanent assets at minor outstations compared to what railroad maintain at minor stops. Many rail stations are unstaffed and the permanent facilities are little more than a few signs and and maybe an awning. Furthermore, what about ferry services operated by railroads, like the Gravesend–Tilbury Ferry, which has operated for over 150 years? We need to have a consistent policy that doesn't carve out exemptions because certain editors like trains and dislike airplanes. BillHPike (talk, contribs) 17:17, 12 February 2018 (UTC)[reply]
- If we have a better measure of permanence for not-quite-hub airports, that would be great. For example, I know there's coverage of Delta establishing a major route through Seattle lately, though I dare not say Seattle is a Delta hub, but it's more than an outlier. What we don't want is the list of all destination cities an airline services. Maybe it's based on airport size or capacity? I don't know, but I feel there's something we can determine as a clear line to avoid indiscriminate while still reflecting the importance of these routes. --Masem (t) 17:29, 12 February 2018 (UTC)[reply]
  - Could the info just be placed within the main article or a split-off that focuses on the airline's history? - Knowledgekid87 (talk) 17:31, 12 February 2018 (UTC)[reply]
    - Oh, easily. You probably don't need a separate list per-carrier for this. I would figure for the largest airlines, this is probably somewhere between 6 to 12 cities long if you narrow it down to hubs and not-quite-hubs, so that fits easily in the airline's article, and can be mentioned on the airport's page. But this still gets back to the idea of permanance, does this make sense here? Somethings, airlines cannot change on a whim. --Masem (t) 17:45, 12 February 2018 (UTC)[reply]
      - I disagree. There's nothing wrong with the destination lists as they exist right now. They are binary: has this airline ever served this airport? Do they currently serve this airport? They aren't lists of routes, nor are they schedules, and while the "do they currently serve this airport" isn't permanent, the fact they have served the airport is permanent. It's also easily verified and doesn't change all that much. Furthermore, including all destinations both helps demonstrate an airline's reach (including historical reach) better than limiting which destinations are mentioned, plus then you get into a slippery slope argument of when should a specific destination be mentioned. SportingFlyer (talk) 23:07, 12 February 2018 (UTC)[reply]
- Further point: It would be absurd for Wikipedia to have articles dedicated to the Heathrow Express service to LHR or the Narita Express service to NRT, but bar any mention of the fact that Japan Airlines has operated a direct flight between those airports for longer then either rail service has existed. (Reference: Fairhall, David (May 16, 1968). "Flight Plans that's stuck in the crowd". The Guardian. p. 20 – via Newspapers.com.) BillHPike (talk, contribs) 17:56, 12 February 2018 (UTC)[reply]
Oppose. The guiding principle should be what we can write fully verifiable articles about. I don't see why "permanence" should have a huge influence. Many lists are not permanent at all (List of current heads of state and government etc.). Why make a special case for "non-permanent transportation-related lists"? Non-permanent sports or television-related lists (List of current NBA team rosters, List of programs broadcast by American Broadcasting Company) do not seem to be inherently better or worse than transportation-related ones. By all means delete or merge unreferenced and unmaintained lists to a suitable parent, but do not outlaw a random class of articles based on random criteria. —Kusma (t·c) 17:46, 12 February 2018 (UTC)[reply]
- For all those cases (current government, current team lineups, current TV schedules), those all then filter to per-year or per-term articles that have historic significance. For example, it is not that we have the current lineup for a given team, but that we end up writing the article about the team's season, which stays historical from then on; we keep broad-stroke TV schedules because there is interest in historical competition between networks, and so forth.

Transportation routes on the other hand do not get that type of historic treatment. I'm sure that there are "trainspotters" here that have keen interest in what the London bus routes were in 1998, for example, but this doesn't get - from what I've seen - the same type of secondary coverage we'd see from the other venues. There certainly can be historically significant routes and those should be documented if they meet the GNG, but not ones that can only be listed from official timetables or databases.

Permanance is not a random criteria here: to have any of the "permanent" items I gave above requires millions of investment often using local taxes, so it's going to be reported on. Schedule changes are not. --Masem (t) 17:56, 12 February 2018 (UTC)[reply]

Would you favor deleting the articles in Category:Former Amtrak routes since they are obviously not permanent sevices? For rail services, the capital investment for a new service over existing rail infrastructure is far less than the capital investment associated with a new route served by widebody airliners. Furthermore, many airlines are state owned, so providing air service also requires a significant investment of tax dollars. BillHPike (talk, contribs) 18:06, 12 February 2018 (UTC)[reply]

"Transportation routes on the other hand do not get that type of historic treatment". Well, that is just wrong, they do. I used to care about trams when I was a kid, and had a book about Trams in Mainz that included a complete history of line changes (not just for trams, but also trolleybuses and the replacement by bus lines) and of the rolling stock used. You will find books about the transportation history of any major European city in any good local library. —Kusma (t·c) 20:49, 12 February 2018 (UTC)[reply]

As long as you can show GNG notability, then you're fine; I would not be surprised to find such books exist for the world's oldest public transit systems (which will start with Europe). However, I doubt every major city will have a similar level of detail for their transit.

But this case brings up the key point here: We're looking at parts of transportation that have been recognized as historically significant in their field. Selected air routes that haven't changed for 50 years will likely have that, but the current full list of routes today from an air carrier is not. The point of starting with permenance, with GNG as a backup if needed, is that permanent routes or structures will have the type of documentation one expects these to have, not any random schedule or flexible route. --Masem (t) 20:58, 12 February 2018 (UTC)[reply]

As I noted above, these aren't lists of routes: they're lists of destinations, both current and historic. SportingFlyer (talk) 23:08, 12 February 2018 (UTC)[reply]

Given the hub-and-spoke approach used by most carriers, while it is true that we're not listing out all routes with a list of destinations, it's pretty dang close to one. But as I mentioned above, if we limited those lists to larger airports as to where an airline having a presence is a significant undertaking, that might be something better. For example, I'd fully approve that the list of hubs (past and present) in Delta Airlines is appropriately encyclopedic and significant. --Masem (t) 23:14, 12 February 2018 (UTC)[reply]

The fact Delta flies to, say, Huntsville, Alabama is appropriately encyclopedic and significant for both the scope of where Delta flies and to understand the level of connectivity of the Huntsville Airport, connectivity being important for transportation-related articles. An article with a list showing Delta flies from Atlanta to Huntsville would not be encyclopedic, or an article on the Delta to Huntsville route would not be encyclopedic. Also, "significant undertaking" would be really hard to define. SportingFlyer (talk) 01:35, 13 February 2018 (UTC)[reply]

Oppose Permanence is irrelevant to notability, and airlines rarely change destinations randomly on a whim unless there's some intervening factor (natural disaster, war, etc.), which is rare. Usually there's some advance notice and clear announcements. Smartyllama (talk) 18:14, 12 February 2018 (UTC)[reply]

I thinks its worth emphasizing that while airlines frequently update flight times and tweak schedules, it is less common for airlines to add or remove all service to a destination. BillHPike (talk, contribs) 18:25, 12 February 2018 (UTC)[reply]

Here is what administrator Necrothesp says, "We generally regard all railway stations as notable. I'm not sure if she is speaking for Wikipedia editors in general, or for administrators. In either case, I see now how foolish I was to point out that that this railway station failed the WP:N standard. The law, apparently, is irrelevant when the judge has already made up her mind. Rhadow (talk) 19:02, 12 February 2018 (UTC)[reply]

Per WP:NTS, Services with likely notability include... train stations. (Note that NTS was withdrawn as policy in 2009). BillHPike (talk, contribs) 21:57, 12 February 2018 (UTC)[reply]
I am a he, not a she, if you'd bothered to look. I have never known a railway station deleted at AfD (and many have been nominated for deletion over the years). That is consensus and consensus is how we determine notability on Wikipedia. No idea why you mention I'm an admin. It's utterly irrelevant. -- Necrothesp (talk) 10:42, 13 February 2018 (UTC)[reply]

Oppose. Agreed with Smartyllama. Permanence is not required for notability. Sjakkalle (Check!) 21:08, 12 February 2018 (UTC)[reply]
Oppose Too broad. Air route schedules (airlines/destinations) are fairly consistent, and notable. The lists on the other hand are an entirely different argument. Bus and train schedules less consistent, though, and perhaps this would work for them. Tofutwitch11 ^(TALK) 21:55, 12 February 2018 (UTC)[reply]
- I want to stress that permanence here is not meant to be the sole deciding factor, only that we can see the defining line between what we agree is acceptable and what is seen as problematic is when the element lacks the permanence expected. A transient element like an air travel route can still be notable on its own. What is not appropriate based on the previous discussion is a listing of all those routes just because one can, unless you can show that the whole of that schedule is of note. --Masem (t) 22:01, 12 February 2018 (UTC)[reply]

I tried to start with what I thought were the least defensible lists of this nature, but there is a whole world of these destination and route list articles. Why? To me it makes no sense. Literally nobody is using these to plan anything, and even if they were, Wikipedia is explicitly not a travel guide. This type of content is just information as opposed to actual knowledge.

That being said I find it extremely unlikely that this RFC will or could succeeed in arriving at a decision not to host any of this. Beeblebrox (talk) 22:02, 12 February 2018 (UTC)[reply]

If nobody is using these to plan anything , then surely WP:NOTTRAVEL does not apply? Perhaps the contributors to these pages wanted Wikipedia coverage of airlines to be as comprehensive as specialised print encyclopedias (Example: 1942-, Endres, Günter G., (2002). Major airlines of the world (2nd ed ed.). Shrewsbury, England: Airlife. ISBN 1840373407. OCLC 51781211. {{cite book}}: |edition= has extra text (help); |last= has numeric name (help)CS1 maint: extra punctuation (link) CS1 maint: multiple names: authors list (link) BillHPike (talk, contribs) 22:41, 12 February 2018 (UTC)[reply]

A good list of airline destinations provides knowledge about the airline's current route network, the airline's route network over time and how the airline developed historically in the same way as the development of a fixed transport network such as a tram, though. It has nothing to do with being a travel guide. Not all lists are "good" yet, true, but that doesn't mean they should be deleted. SportingFlyer (talk) 23:23, 12 February 2018 (UTC)[reply]

And let me add that the concept of knowledge is totally subjective.--Jetstreamer ^Talk 23:57, 12 February 2018 (UTC)[reply]

Comment (I'm willing to plainly ″oppose″, but I want to hear what other editors have to say). Per proposer, transportation infrastructure seems to be notable enough for stand-alone articles. I therefore don't fully understand what the proposal is, as nobody should add information without a reliable source. It seems to be a rewording of WP:VERIFY, a very basic policy. ~~And this discussion started because of the mass deletion of airline destinations: why is this topic not explicitly mentioned?~~--Jetstreamer ^Talk 22:50, 12 February 2018 (UTC)[reply]
Oppose. I don't actually mind the proposal that much - I think adding weight to permanence would be helpful for determining whether a transportation article has notability or violates WP:NOTTRAVEL. I've found a couple bus route articles like Stagecoach Gold bus route S5 which although sourced I would consider proposing for deletion under WP:N and WP:NOTTRAVEL, however something like London Buses route 1 has survived two AfDs (they were both bulk deletes of all routes, and one was withdrawn) and has some history. However using it as the main criteria doesn't seem like it works, plus then you get into an argument about whether a list of airline destinations are routes or not. SportingFlyer (talk) 23:40, 12 February 2018 (UTC)[reply]
Comment. Yes, most of the first section should be considered notable as individual items (although the proposal actually appears to be about lists). We have generally consistently found all of them to be notable at AfD over many years, so there is clear consensus for this. The only exceptions are bus terminals, where we have generally found only the most significant to be notable, and ports, which haven't been tested very much at AfD. But main roads, stations, rail lines and airports? Definitely. -- Necrothesp (talk) 10:55, 13 February 2018 (UTC)[reply]
Comment -- No discussion about whether it is practical to retain all these lists. Take, for example Caribair, likely out of business since 2009. Its list of Caribair destinations still reads, "This is a list of destinations that Caribair currently serves,". It is a completely unreferenced article. It survived AfD in 2015. Rhadow (talk) 14:36, 13 February 2018 (UTC)[reply]

In this particular case, I'd support to merge into the parent article. Meanwhile, I've tagged the article as unreferenced, that is the first step. How can anyone knows the page lacks references without proper tagging? By the way, I've jumped into Category:All articles lacking sources. Are you going to propose the deletion of all these articles just because they don't have references?--Jetstreamer ^Talk 15:47, 13 February 2018 (UTC)[reply]

Hello Jetstreamer -- I know better than to propose it for deletion. The crowd already spoke. They like it just fine with no references. Destination lists are a protected class, just like railway stations. Here's another article I like Air Arabia destinations. An editor asserts that discontinued destinations come from the subject's commercial website. Rhadow (talk) 17:29, 13 February 2018 (UTC)[reply]

That's patently false - there needs to be more references for these articles. The lack of references doesn't mean they can't be cleaned up, though. SportingFlyer (talk) 17:37, 13 February 2018 (UTC)[reply]

Comment - began referencing the Air Arabia article. It's very easy to do. SportingFlyer (talk) 18:23, 13 February 2018 (UTC)[reply]

Cool.--Jetstreamer ^Talk 20:47, 13 February 2018 (UTC)[reply]

Oppose as a blanket policy/guideline is too overreaching when there are specific examples such as 150 year old ferry routes as mentioned above. As long as the routes are correctly sourced and updated by the many transport fan editors I don't see a problem Atlantic306 (talk) 18:07, 16 February 2018 (UTC)[reply]
Comment -- Atlantic306 is spot on ..correctly sourced. Articles that fail are not so rare in this category. That's a systemic problem, not just a couple of bad apples. Rhadow (talk) 00:56, 18 February 2018 (UTC)[reply]
Aero California destinations
Baboo destinations
Blue Panorama destinations
bmibaby destinations
Boliviana de Aviación destinations
CanJet destinations
Caribair destinations
Centralwings destinations
City Airline destinations
Clickair destinations
First Choice Airways destinations
Flyglobespan destinations
Holidays Czech Airlines destinations
Jet4you destinations
MexicanaClick destinations
MexicanaLink destinations
Monarch Airlines destinations
Orbest Orizonia Airlines destinations
SATENA destinations
Skyservice destinations
Ted destinations
Travel Service Airlines destinations
TRIP Linhas Aéreas destinations
Wizz Air Ukraine destinations
...
Aerosvit destinations
AnadoluJet destinations
Estonian Air destinations
Iran Aseman Airlines destinations
IZair destinations
SATENA destinations
I have no problem with unreferenced destination lists being redirected to the parent article. That is normal editing, and does not require centralised discussion. We are in this mess because some people want to have an all-or-nothing answer treating everything the same, although notability of different airlines and their destination systems clearly is not the same for every airline (the low-cost carriers of recent years are very different from the major airlines of the 1960s, when countries were a lot more protectionist about their airspace). We should not have an article about every single road, but we should not outlaw articles about roads. We should not have articles about every single bus line, but we should not outlaw articles about bus lines. —Kusma (t·c) 11:18, 18 February 2018 (UTC)[reply]

Hello Kusma -- Try it. In the rare instance that the article is a dupe, the response will be, "Why didn't you just do this without asking?" In almost every other instance, the objections will be legion. "The history is valuable; you need to look in the wayback machine." "You just don't like these articles." "It's really not any trouble to confirm this article every couple of months." Forget the notion that the lede sets the bar quite high: This is a list of the current destinations of Acme Airlines. What had been a transcription of the subject's route map requires a separate reference for every terminated destination. (They don't appear on the subject website.) Look carefully. Many articles have a single source, the subject's website. When the airline fails, the sole reference disappears. The wayback machine is inadequate; it doesn't always retain the content of drop-down boxes. I understand the ease of copying the subject's website. In most of Wikipedia this wouldn't be allowed, where train stations and airline destinations are concerned, it appears to be an accepted practice. The argument goes like this, "All the other stations on this line are notable, therefore this one is too." These arguments all center on the authority to retain an article while disregarding the responsibility and cost to keep it up to date. What seems like an easy upgrade to an article -- naming a city airport -- makes maintenance much more difficult. When a destination says an airline serves London, that is one level of complexity. When the article specifies Heathrow, Gatwick, and Luton, the digging needs to be much deeper. That challenge is world-wide. Kiev has two international airports. I sure hope this conversation and the DRV acknowledge the high workload required to maintain the factual accuracy of these articles. Rhadow (talk) 12:14, 18 February 2018 (UTC)[reply]

OK, I have tried one redirection. Why? I thought it would improve things, so I was WP:BOLD. —Kusma (t·c) 13:06, 18 February 2018 (UTC)[reply]

Just an example: take the case of SBA destinations, which Rhadow recently AfDed. I suggested a simple redirect. There also was Santa Barbara Airlines destinations, which I redirected to SBA Airlines destinations, since the airline changed its name to SBA Airlines ten years ago. I'm also taking care of the parent article, adding some references and expanding it. Rhadow tagged the article in a wrong manner [10]: it actually had references and someone realised about this [11]; furthermore, official urls in infoboxes do not need a citation, it's just clicking on them to check. I don't doubt about the good intentions of Rhadow, but we need to be more careful on our tagging. And again, we don't need to delete, we need to take care of articles. Proposal: what about assigning different articles to experienced and responsible users to update and put them into shape? I've seen this in other projects and it might work here too.--Jetstreamer ^Talk 13:26, 18 February 2018 (UTC)[reply]

Permit me please, Jetstreamer, to explain my logic with respect to SBA's website. It is referenced several times in the article and does not support various assertions on the page. SBA is grounded; the website (at the time) was locked with a notice that they were moving their offices in Miami. In fact, as a result, for financial reasons, operations are shut down. I'm not expecting that Wikipedia be updated with daily events, but if a major edit is taking place, then a cursory BEFORE search occur to make sure nothing huge is missing. Your work in reorganizing REDIRECTs to duplicated pages is awesome. If only everyone were as diligent. Thanks. Rhadow (talk) 14:34, 18 February 2018 (UTC)[reply]

Allow for emoji's in signatures

Not happening!, Majora has hit the nail on the head and I'll repeat it here - Use your words like a normal person and leave the emojis to text messages and Facebook. –Davey2010^Talk 16:34, 21 February 2018 (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.

Currently some users can get permabanned for having emoji's in their signature, but some users like having emoji's because it makes their signatures more easy to recognise, the signature policy doesn't advise against emoji's but it's not uncommon for people to be requested not to use them. I would like to propose that all users can add emoji's to their signatures as they are not disruptive and are purely decorative. --Donald Trung (Talk) (Articles) 09:20, 12 February 2018 (UTC)[reply]

Emojis are allowed in signatures. What is not allowed is emojis in usernames. —Kusma (t·c) 09:43, 12 February 2018 (UTC)[reply]

Donald Trung, note that Kusma is speaking generally, and not with regards to your particular case. You are banned from using emojis (and special characters in general) in "in edit summaries or non-talk pages"—with signatures as implicit in that, since it would otherwise mean you couldn't comment on WP-space pages like this—as part of your unblock conditions. ‑ Iridescent 10:00, 12 February 2018 (UTC)[reply]

I would say that any page which is used for discussions (including this one, AN, etc.) is a talk page; any other sort of Wikipedia: namespace page should generally not be signed. עוד מישהו Od Mishehu 16:12, 12 February 2018 (UTC)[reply]

Support. CLCStudent (talk) 21:49, 17 February 2018 (UTC)[reply]

Oppose: Not only do emojis present an accessibility problem for those that do not have the right thing installed on their computer they are unencyclopedic nonsense. They make everything much more difficult to read, disrupt the flow of conversations, and make it impossible to take the person using them seriously (in my opinion). Use your words like a normal person and leave the emojis to text messages and Facebook. --Majora (talk) 22:40, 17 February 2018 (UTC)[reply]
Oppose I agree with Majora's analysis of this proposal. Cullen³²⁸ Let's discuss it 04:27, 19 February 2018 (UTC)[reply]
Oppose per a cursory overview of the OP's signatures on other Wikimedia Wikis as the prime example of how excessive use of emojis in signatures is disruptive. We already allow emojis in signatures, what we de facto don't allow are ridiculous signatures that use multiple emojis in a manner that makes communication difficult and makes it feel like we're being trolled. That's not technically part of policy, but it's part of the standard "give someone who has an obnoxious signature a kind nudge on their talk page." Any policy that would make the kind nudge ineffective would be a negative. TonyBallioni (talk) 04:31, 19 February 2018 (UTC)[reply]
Oppose - Majora hits the nail on the head. Wikipedia is not a social network or a chat media. It's an encyclopedia. I may be old fashioned but I would at least like to keep the informal nonsense out of the signatures. IMO there's too much leeway in signatures already. Kudpung กุดผึ้ง (talk) 12:57, 21 February 2018 (UTC)[reply]
Strong oppose--Per Majora and Kudpung.~ Winged Blades^Godric 13:15, 21 February 2018 (UTC)[reply]
Leaning trout ...all things considered. GMG ^talk 13:27, 21 February 2018 (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.

The case of a block enacted after a page protection

Hi.

So, please imagine this case: Editor A and B are in a dispute. Nobody else is in that dispute. Admin C protects the disputed page. But then, other things happen and Admin C blocks Editor A for his or her conduct in that said dispute, for a period equal to or longer than the page protection length, and revokes his talk page access. Naturally, at this stage, Editor B has no way of engaging in any sort of discussion, which was the purpose of the protection.

Now what should happen to the protection?

Should it be left intact even though it serves no purpose?
Should it be extended to by the period of Editor A's block plus the original protection length?
Should it be lifted?

Of course, I am open-minded to this issue not being a wholly trinary case.

Best regards,
Codename Lisa (talk) 10:25, 14 February 2018 (UTC)[reply]

In your first option you say that, at that point, the page protection "serves no purpose". First, A was blocked for conduct, not for being wrong in the content dispute. I posit that most often B would still need a cool down period too, and that is the "purpose" of leaving the page protection for the time being. B should realise it is not about "winning" a dispute, and cooling down instead of rushing to convert the page to their preferred version is usually best. B can, if they're sure they're "right" on the content issue (when what they consider the "wrong version" got protected), request to implement the improvements they suggest via an {{editprotected}} template on the talk page, and someone uninvolved would evaluate. They can request the page protection be lifted, if it is very obvious that A had disrupted mainspace (i.e. in the article) before being blocked. Also in this case, someone else would evaluate whether the requested unprotection is justified. But generally I suppose B cooling down for the period of the initial page protection period, and making themselves useful elsewhere in the mean while, being the best option. --Francis Schonken (talk) 10:53, 14 February 2018 (UTC)[reply]

@Francis Schonken: Hi. Thanks for the reply. I am afraid I find it biased, biased and biased, as it assumes Editor B has the following attributes:

He or she cannot edit already, because of protection
He or she wants to edit and the current state isn't to his or her satisfaction
He or she needs to cool down in the first place
That cooling down is even possible when he or she has permission to edit other places (Your very strong wording draws a picture of jerk from Editor B. Such a person is already a high risk that might do other not-so-okay things elsewhere.)

Also, {{editprotected}} suggestion is not helpful: In case of a dispute a page is fully protected. Only admins can respond to edit request and they explicitly avoid responding to the edit requests from B, per their "no wheel-warring" mandate, that it is not a good idea to defeat the purpose of a protection by permitting Editor B get his or her way anyway and the controversial "wrong version" issue to which you alluded.

Best regards,
Codename Lisa (talk) 12:57, 14 February 2018 (UTC)[reply]

@Codename Lisa: what a nonsense you're writing now (very strong wording intended). I implied nor pre-supposed any of that. --Francis Schonken (talk) 13:23, 14 February 2018 (UTC)[reply]

"I implied nor pre-supposed any of that." Then, are you saying a person who can edit, doesn't want to edit, does not need to cool down, and is not struck by any measure that either eases or facilitates his or her cooling down still needs to cool down? Same question about "winning". —Codename Lisa (talk) 14:24, 14 February 2018 (UTC)[reply]

Again, what nonsense: I implied nothing of the kind. --Francis Schonken (talk) 14:40, 14 February 2018 (UTC)[reply]

Whoa! No need to bite. I didn't come here with the intention of talking nonsense. If you I feel have grossly misinterpretted your comments, then I am afraid your comments are susceptible to gross misinterpretation. But let's not escalate the discussion like what happens in content disputes. At worst, we can bow out and agree to disagree. —Best regards, Codename Lisa (talk) 18:30, 15 February 2018 (UTC)[reply]

A page protection does not mean only those previously engaged should discuss the issue. In fact, B can use the time to invite neutral editors D, E and F to give their input, hopefully reaching a consensus before the protection expires. Plus, A's block does not mean they or their sympathizers won't restart the edit-warring if protection is lifted without a consensus on how to handle to issue. Regards So Why 13:26, 14 February 2018 (UTC)[reply]

@SoWhy: Hi. I can clearly see there is more experience behind your answer. Here is a couple of things though:

You argued against option 1. Still, that begs the question: do you endorse option 2 or 3?
Is a consensus established in absence of Editor A even valid? I am just asking; this not a rhetorical question. Because there are arguments in favor and against it. One is that an in absentia consensus does not resolve the dispute, for Editor A can argue that if "I were there, I would have argued my case successfully." Furthermore, it does not improve the relation between A and B. The counter-argument is: Editor B's privilege to participate has been revoked because of his or her own failure to use it. But then again, if he or she has lost the privilege to be part of the consensus, the protection is not necessary either.

Best regards,
Codename Lisa (talk) 14:17, 14 February 2018 (UTC)[reply]

SoWhy's reply seems perfectly compatible with option 1. I don't see in what sense they "argued against option 1"? --Francis Schonken (talk) 14:25, 14 February 2018 (UTC)[reply]

(edit conflict) No, I argued for option 1: The protection (and its length) are not void just because one editor is (forcibly) absent. And consensus is not valid or invalid based on whether certain people participated or not. If A disqualified themselves from editing because of his behavior after the protection, they have no leg to stand on claiming a consensus invalid. After all, they removed themselves from the discussion by behaving like they did after protection was set. Consider this to understand my point: What if A was not blocked but chose to go offline for a few days. Should we also wait for them to return to find a consensus? And if so, why?

As for the other part, I already noted why protection should not be lifted, mainly because A's block alone neither means they won't come back (as socks) nor that others won't "fight" their battle for them. Regards So Why 14:26, 14 February 2018 (UTC)[reply]

I see. I also see why I thought you argued against it: When you said "they won't come back", you actually meant WP:EVADE. Alright, that's a lot clearer now. —Codename Lisa (talk) 14:30, 14 February 2018 (UTC)[reply]

Here are a couple of other things though:

When an edit war is resolved by blocking one of the parties, no page protection is enforced out of the fear of WP:EVADE or illegitimate canvassing. Hence, your argument seems to permit a flaw.
There is still room for option 2.
What if these other who "fight their war for them" actually fight fair? Isn't assuming good faith a policy here? Even better, these additional editors might actual improve other areas of the article or improve the disputed area to the point that the dispute becomes moot.

Best regards,
Codename Lisa (talk) 14:38, 14 February 2018 (UTC)[reply]

Re. "Is a consensus established in absence of Editor A even valid" – taking this as an example (editor A "indeffed for undisclosed paid editing" and for "plenty of WP:NOTGETTINGIT" during page protection), any consensus "established in absence of Editor A" would be valid. So it largely depends on circumstances (in different circumstances it may be better to involve the A editor in reaching consensus). --Francis Schonken (talk) 14:40, 14 February 2018 (UTC)[reply]

Hence, my message above. —Codename Lisa (talk) 18:30, 15 February 2018 (UTC)[reply]

@Codename Lisa: Sorry, it's clear that you have a specific case in mind. I'm afraid that speaking in the general without being able to review the specific case you are disputing is not helpful here. If you can refer us to the specific case (rather than your partial characterization of it) we can review it and speak intelligently on it. --Jayron 32 04:13, 15 February 2018 (UTC)[reply]

Hi, Jayron32.

None of us come here because one day we wake up and think "Wow! I wonder what happens if an admin did such-and-such." But I can guarantee that I am NOT here seeking appeal to another admin's decision under the facade of a general question. If you feel I have a certain case in my mind, all you have to do is to ignore that feeling and answer generally.

But then again, I can definitely say the same thing about the other participants here. Nobody took each of my three recommended couses of action to analyze its pros and cons individually and objectively. Instead:

Francis Schonken said highly judgmental things about a totally imaginary editor, for which I had supplied no previous data whatsoever. I shudder to think what this could imply. He assumed bad faith by default, in violation of WP:AGF.
SoWhy's reply is an example of behavior for which Wikipedia admins have gained notoriety. People outside Wikipedia often judge us and I hear their judgments without letting them know I am their target. One of the comments on admins here is that they go to a ridiculous length and breadth to avoid disagreeing with existing policies and their fellow admins, to the point that if two admins do completely opposite and comflicting things, they are ready to swear that they agree with what both did, and their actions are in no way contradictory. And they are not wrong too. SoWhy is very careful to totally discourage the idea of there being the slightest flaw in the existing policy, so much so that intially, it is not obvious whether he is against option 1 or in favor of it.

Best regards,
Codename Lisa (talk) 18:30, 15 February 2018 (UTC)[reply]

Re. "said highly judg[e]mental things about a totally imaginary editor" – wrong in every direction, that's why I called the reply nonsense. --Francis Schonken (talk) 18:40, 15 February 2018 (UTC)[reply]

And yet you do not make any attempt to correct that wrong. Come on now, Village Pump is not about winning, so there is no need to feel you have lost. It is about intellectually positive exchange. So, there is no need to feel your dignity is smeared. At least, that's not the intention here. Also, "judgmental" is correct; there is no "e" between "g" and "m". —Best regards, Codename Lisa (talk) 18:50, 15 February 2018 (UTC)[reply]

Lisa, I don't understand why you've responded with hostility to everyone who has tried to respond to your inquiry. The only one who's failed to assume good faith here is you, and this comment is frankly bordering on personal attacks. If you're trying to prod the participants into some kind of realization about an error in policy that you think needs to be corrected, you are doing a transparently bad job of it. Nonetheless, I'll add my insight into the scenario you posited, and I hope that if you need to respond you will not assume I am your enemy as you seem to have done with everyone else here. If you think I've made an errant assumption in my reply I'm happy to discuss, but please don't assume I'm jumping to conclusions. You posted an interesting but somewhat vague scenario (not "wholly trinary" as you aptly put it) and we're all doing our level best here.

I would try my very best in this scenario to not block either of the editors if I've already protected the page, though I acknowledge this is a possibility. Given the exact scenario I would not automatically modify the protection. Responding to your suggestions point-by-point:

I would not assume that leaving the page protected serves no purpose. That could be the case, depending on the circumstances. It could just as easily be the case that the remaining editor is still trying to add unsuitable content, or perhaps the profile raised by the dispute has attracted other editors and discussion is proceeding. There could be reasons to keep the protection just as easily as there could be reasons to lift it; it's impossible to answer definitively given the generality of the scenario.
I can however say for certain that I would not extend the protection as a result of one participant's block, as it is effectively sanctioning the other editor as well, and that is pointlessly punitive. Something along the lines of what SoWhy said, that one editor behaving themselves into a block ought not to cause an impediment to any other editor, insofar as we can avoid doing so. And as a side note if the blocked user were to use their own talk page while blocked to try to participate in the discussion anyway, I would warn them once before revoking talk page access. Although in your scenario talk page access was already revoked, so this doesn't apply.
Again, no, not automatically. See #1.

Full protection is not a cookie-cutter solution, it's a response normally to complicated editing issues that have failed to be resolved through other methods, and as such it's likely a bad idea to suggest that the resolution of any situation involving full protection can be compared to any other such situation. As for your comments about (my flavouring) admins falling over themselves to agree with each other, I see that as less about avoiding the perception of disagreement and more about there being a general overarching consensus about how our policies and guidelines are to be applied. Although I do understand that that's not how it looks to some. Ivanvector (^Talk/_Edits) 19:28, 15 February 2018 (UTC)[reply]

(edit conflict) And to the edit-conflicted comment: this isn't Americapedia; "judgemental" is a perfectly valid spelling in other flavours of English. It even says so in the link you provided. Ivanvector (^Talk/_Edits) 19:28, 15 February 2018 (UTC)[reply]

"If you're trying to prod the participants into [...]". I categorically said there is no such thing.

"you've responded with hostility to everyone". Five years ago, I would have been embarrassed and would have wasted no time to apologize upon reading this. But five years of experience tells me that admins such as yourself simply enjoy preaching and perhaps five years of humbleness on my parts have been a mistake that emboldened your kind. There was no hostility. There was no personal attacks. And WP:NPA isn't meant to be an excuse to suffocate criticism of criticable conduct.

The rest of what you wrote. Didn't read. I doubt there is anything intellectual in them. Alright! I have held back long enough! Clearly we are not having an intellectual debate under this thread; never had. All because you are doing what admins always do: Playing priest and calling people "sinners". Five years ago, when I came here, admins were nothing short of holy to me. Now, most of the Wikipedians with whom I enjoyed working have left; those who have stayed often refrain from entering discussions, which are now markedly more bitter. Admins are supposed to be role models; instead, they are ordinary Wikipedians with extra power, no oversight, and overwhelming need for oversight. WP:BEANS illustrates the behavior seen in babies, not sensible mature people. So, when I say no prodding is intended, and you level that exact same accusation, you not a sensible mature person, let alone admin-worthy.

Enraged, heartbroken, and mistreated,
Codename Lisa (talk) 20:40, 15 February 2018 (UTC)[reply]

P.S. I am unwatching this page. Please refrain from pinging or coming to my talk page about it. —Codename Lisa (talk) 20:43, 15 February 2018 (UTC)[reply]

Well, I'm sad that you didn't read any of the part of my comment which actually offered input on your question, I was looking forward to your feedback. But I'm going to stand by the assertion that there's only one person playing "holier-than-thou" in this thread, and I still don't understand why. I'm assuming you're not going to read this anyway, and by your request I'm not pinging you.

Does anyone else want to continue this discussion? I do think it's an interesting scenario. Ivanvector (^Talk/_Edits) 20:54, 15 February 2018 (UTC)[reply]

You have given a few facts about the real or hypothetical case. Each case would inevitably have much more that is very relevant to the answer to your question. So the premise that an answer is determinable from the facts that you gave is incorrect. North8000 (talk) 20:59, 15 February 2018 (UTC)[reply]

My only comment is this: the fact that the article was protected is but a TEMPORARY inconvenience for Editor B... sure, he/she can not edit the article RIGHT NOW, but that restriction will change SOON. Any changes that need to be made CAN be made... everyone just needs to have some patience. Blueboar (talk) 21:44, 15 February 2018 (UTC)[reply]

I'm thinking this is about Opera (web browser). There's a simple answer: go to the admin who protected the page (in this case, me) and talk to them. --NeilN ^{talk to me} 21:55, 15 February 2018 (UTC)[reply]

@NeilN: Surprise! I had a change of heart and I came back! (Not really; I was watching your contribution log.) The "Opera (web browser)" case was one of the many cases that made me file this request. But let me be clear about one thing: If I wanted that article unprotected, the one thing I wouldn't have done is to come here, for the very simple reason that it is unlikely to get fast results here. Village Pump discussions often take a long time; weeks maybe. Plus, if that was my intention, I'd have done something to grab your attention before (not after) the protection expires.

Seriously, theories of conduct in Wikipedia are sometimes very movie-like. —Codename Lisa (talk) 22:31, 15 February 2018 (UTC)[reply]

Hi Codename Lisa. I think my general point still stands. Every case has its own nuances so it's hard to formulate a general guideline. For example, for me, if one side turns out to be a sock, that's an automatic unprotect (if I remember). If one editor has left an unanswered post on the talk page before being blocked I'm less likely to unprotect. If the dispute has attracted more editors after the block I'll take a look at the talk page. That's why I think talking to the protecting admin is the best first course of action. --NeilN ^{talk to me} 22:51, 15 February 2018 (UTC)[reply]

Well, thank you for your no-nonsense no-sidetalk straight-down-to-business answer. 👍 Of course, per Wikipedia policies, talking to the protecting admin is mandatory, unless there is evidence of him being on extended absence. In case of "Opera (web browser)" I certainly do not want compromise my integrity by damaging the olive branch that I offered and you took into consideration. Hence, whether its protection is removed, left untouched, or extended, I certainly don't want to be part of the decision-making process.

Here is the thing though: I have been on the other side of the protection before. You see, there was once a dispute in a template. It was fully protected. I contacted the protecting admin and asked the protection to be dropped to Template Editor level, so that I can edit it. I assurred him that I don't intend to touch the disputed region, which would cost me my Template Editor privilege. He kindly told me that he wouldn't believe me doing such a thing, but because full protection in case of a dispute is the policy anyway, he wouldn't oblige.

Best regards,
Codename Lisa (talk) 23:14, 15 February 2018 (UTC)[reply]

And is that template still protected? Blueboar (talk) 23:44, 15 February 2018 (UTC)[reply]

All options listed are acceptable. It's a case of Admin discretion. On examining a situation, the Admin could conclude that the block fully resolved the problem and that the initial protection wasn't necessary or appropriate anymore. One could equally conclude that B's edits to the article were part of the conflict, and the protection stays in place for B to cool down or seek collaborative input, or any other reason. (One could simply leave protection in place as an inaction-default.) One could also conclude that A WILL be returning to the article, that resolving the situation WILL require discussion, for example some sort of NPOV resolution between A's POV and B's POV might be needed (hopefully with outside input), and that the protection needs to lock down the article long enough for those discussions to occur. It all depends on how the Admin reads the particular situation. Alsee (talk) 13:32, 22 February 2018 (UTC)[reply]

Is it canvassing to notify all participants of a previous AFD if they all !voted the same way?

Per WP:CANVASS, notifying all editors who participated in a previous AFD is generally considered allowed, especially when little time has passed since the last nomination. But what if the last AFD closed as straight keep with no delete !votes except the nominator? Then notifying all participants would mean alerting all people who argued to keep the article even though you would not exclude anyway (assuming both AFDs are started by the same person). Is it still allowed to notify those users based on CANVASS's appropriate notification rule or is it now votestacking because you can not avoid notifying people who already expressed an opinion (but who might change it given the new arguments)? Regards So Why 14:34, 15 February 2018 (UTC)[reply]

As long as no one is excluded, notifying all previous contributors to a discussion in a neutral manner is not canvassing. Only in death does duty end (talk) 14:42, 15 February 2018 (UTC)[reply]

I've done such notifications sometimes when people contested my deletions, and never has anyone complained about it. I am minded to agree that so as long as you aren't leaving off some users it should be proper. Jo-Jo Eumerus (talk, contributions) 15:23, 15 February 2018 (UTC)[reply]

Votestacking (trying to establish your desired result by selective notifications) is only an issue if your list of notified users is intentionally chosen by the expected result. "Everyone who participated in the most recent relevant discussion" is a truly neutral criterion, even if the discussion went in your favor. Do make sure the nominator of the original discussion is aware of the new discussion (not an issue if this same user is the nominator of the second discussion). עוד מישהו Od Mishehu 15:43, 15 February 2018 (UTC)[reply]

What they said. If the criteria (everyone) and the method (without imposing a viewpoint in the notification) are neutral, then it isn't canvassing. Dennis Brown - 2¢ 13:35, 17 February 2018 (UTC)[reply]
The most efficient way to resolve an issue is generally by people already familiar with the subject. It is perfectly appropriate to make an unbiased notification of an previous appropriate and unanimous consensus. The only way I see a problem is if there is some other problem involved. For example if it turns out that the unanimous discussion was itself a canvassed/meatpuppet fanclub voting to keep their favorite band. Then the notification would be re-canvassing of the original canvassed group. That would warrant (at minimum) a stern canvassing warning, and as a closer I'd certainly evaluate it as a re-canvassed group. But that is a corner case. Notifying a unanimous consensus is, in general, appropriate. Alsee (talk) 14:00, 22 February 2018 (UTC)[reply]

Everipedia

Is it acceptable to reuse content from Everipedia with attribution? I remember Bazzi (musician) had a few lines which duplicate those on the Everipedia page (his page on Everipedia was created when he was a minor social media celebrity but would have failed the GNG), but those revisions were deleted for copyright infringement. Jc86035 (talk) 12:19, 16 February 2018 (UTC)[reply]

No... unless we are directly quoting a source, we should never simply cut and paste. Instead, our editors should rewrite the material so it presents the same information using different words, and then cite the sources that support it. (However, in this case, don’t even do that, since Everipedia is not considered reliable). Blueboar (talk) 12:42, 16 February 2018 (UTC)[reply]

as Blueboar suggests, the question should not arise because Everipedia is a crowd-sourced site and no open wiki is reliable. - Sitush (talk) 12:53, 16 February 2018 (UTC)[reply]

A slight addendum to the above, with basically the same advice: technically, text in the public domain OR text which has been licensed under the proper copyleft licenses to be compatable with Wikipedia's own license are technically OK to reuse, HOWEVER, you'll find that most of it would be improper to use at Wikipedia anyways for one of two reasons 1) the source itself is not reliable, or 2) The material is not written in a tone or style which is expected at Wikipedia, and would need a complete rewrite anyways to conform to Wikipedia standards. Given that, it is rarely (read: basically never) acceptable to simply copy text and put it wholesale in Wikipedia even if there is no legal hurdle against doing so. It is always (read: always) better to simply write original text which references the reliable source. That is, however, academic in this specific case. Everipedia isn't reliable as a source, so you're best just finding better sources and writing original text anyways. --Jayron 32 12:55, 16 February 2018 (UTC)[reply]

OK... there is a distinction between “allowed” and “should”... we are allowed to copy material that is in the public domain, but that does not mean we should do so. Simply copy pasting stuff from another website is intellectually lazy, even if allowed. Plus, if you always rephrase in your own words, you never have to worry about copyright. Blueboar (talk) 13:54, 17 February 2018 (UTC)[reply]

I can’t imagine that we would or could consider Everipedia a reliable source. I would suggest taking this to WP:RSN for further discussion. Beeblebrox (talk) 00:12, 18 February 2018 (UTC)[reply]

The talk above here about Everipedia being a reliable source or not is irrelevant. Let's assume you find some text on Everipedia that is well-written and well-sourced. You still can't use that because it was probably copied from another website, an ebook or social media. So copyrighted. And Everipedia does not care. Whatever you find on Everipedia that is not also on Wikipedia should be assumed to be copyrighted content. Alexis Jazz (talk) 04:46, 19 February 2018 (UTC)[reply]

Change to the wording of Wikipedia:No original research

Diff. Comment by @Chris troutman: "While you're probably right, I don't think it's appropriate to change the wording of a policy without consensus.". I didn't think I really changed the meaning, but I can see the point, so lets see if there would be consensus. Alexis Jazz (talk) 04:54, 17 February 2018 (UTC)[reply]

I'm not opposed to the addition, although I think some wordsmithing might be needed since the following sentence about something being attributable versus being attributed better appears immediately following the point about Paris. I would like to see if there's consensus for this change. Chris Troutman (talk) 04:59, 17 February 2018 (UTC)[reply]
I would oppose it, but for a rather nuanced reason. The "citing the sky is blue" trope is too idiomatic at Wikipedia to carry meaningful policy weight; there's an entrenched, old debate over the specific idiom to the point where we have competing essays, Wikipedia:You don't need to cite that the sky is blue and Wikipedia:You do need to cite that the sky is blue and the nuance is that sometimes you do actually need to cite the obvious and sometimes you don't, and context (not policy) will tell you when. I think the OP made a good-faith clarification, but the Paris, France example is sufficient and unlikely to carry the cultural baggage that the "sky is blue" idiom just does at Wikipedia. --Jayron 32 05:05, 17 February 2018 (UTC)[reply]

@Jayron32: Okay. I didn't really make the edit to clarify it though, it just seemed like the most sensible way to put WP:BLUESKY in there. Any suggestions to link BLUESKY, or should it not be linked at all in the policy? Or should BLUESKY be changed to FRENCHCAPITAL? Alexis Jazz (talk) 05:11, 17 February 2018 (UTC)[reply]

I don't think you should link anything there, the meaning of the sentence is plain and unambiguous and doesn't need further elaboration. --Jayron 32 05:13, 17 February 2018 (UTC)[reply]

I wouldn’t link to WP:BLUESKY without also linking to WP:NOTBLUE. So best to not link either. Blueboar (talk) 10:56, 17 February 2018 (UTC)[reply]

Something else to consider... the reason why "The capitol of France is Paris" is a good example to use in the NOR policy isn't so much that the truth of the statement is obvious... but that (as a statement) it is extremely verifiable. There are literally thousands of sources that could be cited to support it. In other words, it is the fact that the statement isn't original research that is obvious. Now... "the sky is blue" is also quite verifiable (and thus is not OR)... but... the counter argument (that the sky isn't actually blue) is also quite verifiable. So it does not make for a good example to use in our NOR policy. Blueboar (talk) 13:13, 17 February 2018 (UTC)[reply]

I don't see the addition adding to the policy. In general, the shorter the policy, the better, and any addition that doesn't add context or explain the policy better is superfluous. Making it longer just to add a link WP:BLUE seems pointless since that information page isn't about original research, it is about citations for things that are obvious. Dennis Brown - 2¢ 13:33, 17 February 2018 (UTC)[reply]
As for the proposal, I suppose it wasn't the best idea.

As for France, @Blueboar: I am starting to have some doubts. How would you source the fact that the capital of France is Paris? Sure, you could link some maps. But that's not exactly an authoritative source. You could link paris.fr, that may be slightly better but still not the source. On the Paris article the statement "By the end of the 12th century, Paris had become the political, economic, religious, and cultural capital of France." is backed up by a 2010 city guide. Um. It seems to trace back to "Clovis the Frank, the first king of the Merovingian dynasty, made the city his capital from 508." which looks like an uncited fact. (although I suppose it'll be found in "Paris, des origines à Clovis" cited all the way at the end of the paragraph) I now actually do wonder what a proper source for the statement "The capital of France is Paris" would even look like. My best guess would be it's codified in law somewhere. I wouldn't mind if Wikipedia linked that law, even if only for historical purposes. Alexis Jazz (talk) 15:43, 19 February 2018 (UTC)[reply]

Alex... just about any modern atlas could be cited for “the capitol of France is Paris”... it is also mentioned in numerous encyclopedias, dictionaries, almanacs, newspaper articles, tourism guides... etc. etc. etc. this isn’t the kind of controversial fact where we would require a high end scholarly source (but if someone insisted, I am sure there are plenty that could be cited). Blueboar (talk) 18:30, 19 February 2018 (UTC)[reply]

How about a source for this statement: "There was no hurricane anywhere in Modesto California yesterday." North8000 (talk) 18:50, 19 February 2018 (UTC)[reply]

@North8000: You would probably use something like https://www.wrh.noaa.gov/mesowest/getobext.php?wfo=sto&sid=KMOD&num=72&raw=0 as a source for that, although that only proves it wasn't that windy. In general you can't prove a negative. A source for "The capital of France is Paris" could be given, but a source for "There is no God" can't be given. Have some tea. Alexis Jazz (talk) 19:27, 19 February 2018 (UTC)[reply]

@Alexis Jazz: But that would be O/R / synthesis to derive my statement from that :-). My example was kind of whimsical, but we had a real life issue like that. An otherwise-RS made an error (or poor choice of words) and called a public figure something that was somewhat negative but obviously in error, so blatantly untrue that (like my hurricane example) that no source is going to cover to say the opposite and refute it. Some POV folks liked the obvious error and used wiki-policy to keep it in. North8000 (talk) 22:44, 19 February 2018 (UTC)[reply]

@North8000: Now I'm curious what exactly you are talking about. What is it? Alexis Jazz (talk) 01:34, 20 February 2018 (UTC)[reply]

@Alexis Jazz:It was a painful old dispute that was formative in my wiki thought process that I really don't want to go back to, but the statement was that Ron Paul (the guy advocating trade with Cuba) is an isolationist. I think the mis-statement came from him being a non-interventionist. I learned a few things from that. One is that even genuinely wp:"reliable" sources can be unreliable on a particular topic. The second is that sources don't cover implausible statements that practically nobody is making. Such as my hurricane statement. North8000 (talk) 11:51, 20 February 2018 (UTC)[reply]

@Blueboar: So citing another encyclopedia for a fact is acceptable? Did not know that. I won't insist on a source, but I wondered what it would look like. I mean, if we were to cite an atlas you could ask the atlas people "so how do you know?", you ask whoever they mention how they know and eventually you should arrive at some actual source. I wondered what that might be. Alexis Jazz (talk) 19:27, 19 February 2018 (UTC)[reply]

Well, a lot depends on the specific encyclopedia and the specific fact... but yes... just about any published general encyclopedia would be quite acceptable for verifying which cities are national/regional capitols. As for what the citation of an atlas might look like... it would look something like this:^[1]

^ The Times Comprehensive Atlas of the World (14th ed.). HarperCollins UK;. 2014. p. 23. ISBN 0007551401.{{cite book}}: CS1 maint: extra punctuation (link)

(note: I don't have an actual copy of the Times Atlas in front of me, so I did make up the page number - just for the sake of giving an example... obviously if I were formatting an actual citation, in an actual article, I would take the time to look up the actual page to cite). Blueboar (talk) 20:41, 19 February 2018 (UTC)[reply]

Thanks for your answer and information on citing another encyclopedia. What I actually meant though with "what it would look like" was if you would ask the atlas people how they know, they point (for example) to the map makers and you ask them how they know, they point to some database and you ask the people who made that how they know.. And in the end I guess you will end up with a law or similar I think? And what does that law look like. For "The United States is a nation" for example, I think you'll end up with the United States Declaration of Independence. But I don't know what you would get for "The capital of France is Paris" and that's what I am curious about. Alexis Jazz (talk) 01:34, 20 February 2018 (UTC)[reply]

That would be a primary source, which policy says we should avoid when possible WP:PRIMARY. At the time, there wasn't universal acceptance that the Declaration of Independence established the United States as a nation, so it is not irrefutable. Some people might say it is the Constitution or some other document that established the United States as nation, and some might say that the Second Continental Congress had no legal right to declare independence from the Kingdom of Great Britain (the British certainly disputed it at the time). Thus we need WP:SECONDARY WP:RELIABLE sources to verify that the United States is a nation. As for Paris, I'm just not sure. What makes you think that Paris is the capital of France? Right now, the source in the Paris article is Le Parisien and, on the face of it, I can't consider that source to be completely impartial. Jack N. Stock (talk) 01:59, 20 February 2018 (UTC)[reply]

@Jacknstock: I can't thank you enough for your response. No seriously, I can't. The thanks system is broken. And you are absolutely right. I think Le Parisien is pulling our leg when they say Paris is the capital of France. Everybody knows Paris is in Denmark. Alexis Jazz (talk) 12:22, 20 February 2018 (UTC)[reply]

Just a reminder: You (the individual editor) should not revert anything unless you personally object to its actual content. Your objection can be quite minor, but it should be an objection that you actually hold. This is actually our formal policy on the subject of updating policies: "you should not remove any change solely on the grounds that there was no formal discussion indicating consensus for the change before it was made. Instead, you should give a substantive reason for challenging it and, if one hasn't already been started, open a discussion to identify the community's current views."

One of the reasons for this is if you revert something because of your guess that some other, hypothetical editor might object (or because you don't think that WP:NOTBURO should be a policy), then the BRD-based resolution process is going to be broken. Those conversations tend to go like this:

Bold editor: So why do you object to this change? How can I improve it?

Reverter: I don't.

Bold editor: So why the heck did you revert it?

Reverter: Aren't you supposed to get written permission first, before making a change?

Bold editor: Not according to WP:POLICY. Not according to WP:NOTBURO. Not even according to WP:CONSENSUS.

Reverter: Well, someone would probably object. I'm sure there's something in every change to a policy that would bother someone.

Bold editor: Well, nobody actually did object, did they?

Reverter: I dunno. But someone told me last year that I had to get consensus for my change, so you have to get consensus for yours.

Bold editor: <screams>

Let's not have that, okay? If you personally don't believe that a change makes a page worse, then please (please!) let the reverter be someone who actually does hold that POV. Then the bold editor actually has a chance at finding out what's wrong with the proposal. WhatamIdoing (talk) 04:39, 24 February 2018 (UTC)[reply]

Toronto Sun cannot be used in Wikipedia?

User ****** wrote that the Toronto Sun is an unreliable citation. I looked in Wikipedia and it doesn't confirm this. Is the Toronto Sun, which appears to be a major newspaper of Toronto ok to use as a citation in Wikipedia? Vanguard10 (talk) 22:36, 18 February 2018 (UTC)[reply]

It would be better to ask WP:RS/N :) .--cyclopia ^speak! 22:39, 18 February 2018 (UTC)[reply]

And notify users if you are going to discuss them. Ian.thomson (talk) 22:49, 18 February 2018 (UTC)[reply]

I have redacted her username. Vanguard10 (talk) 23:38, 18 February 2018 (UTC)[reply]

The Toronto Sun certainly is one of the least reliable "newspaper" in Canada, and is modeled after The Sun of the UK. It's a tabloid, not a serious source of news. Headbomb {t · c · p · b} 23:16, 18 February 2018 (UTC)[reply]

RfC: Non-admin closure of AfD

Please consider joining the feedback request service.

An editor has requested comments from other editors for this discussion. This page has been added to the following list:

Wikipedia policies and guidelines

When discussion has ended, remove this tag and it will be removed from the list. If this page is on additional lists, they will be noted below.

Background

Given recent disruption caused by non-admin closures of WP:AFD, I am proposing that non-admin closures/relistings be banned except in very limited circumstances. The most obvious exception being when someone withdraws their own nomination (there may be one or two other exceptions but that's the only one that comes to mind for me). Here are two recent ANIs where someone has created disruption by closing an AfD [12] & [13]. This seems to be a recurring issue and I think this is the best way to deal with it. I understand that admins are busy and others try to help, but it is actually creating more work when someone has to go back and review poor closings/relistings.--Rusf10 (talk) 01:37, 19 February 2018 (UTC)[reply]

Comments

Oppose - We do have some problems, but most non-admin closers do fine. What happens is sometimes a new closer comes in and won't listen to feedback, or non-admin closes AFDs that they shouldn't close. Policy already states they should only close the most obvious AFDs. If they do this, closing those that do not require a lot of accountability, then they are helping. Admin have higher accountability due to policy, but we aren't smarter by virtue of the bit. Once a non-admin shows they aren't accountable or receptive, then they just need to be taken to ANI and topic banned from closing anything. Thankfully, those are rare cases, which would make changing policy a bad idea as we would be missing out on the good work of most non-admin. Dennis Brown - 2¢ 01:46, 19 February 2018 (UTC)[reply]
Oppose Per Dennis - we have means to deal with the bad apples, but the process is otherwise fine. --Masem (t) 02:08, 19 February 2018 (UTC)[reply]
Oppose as above. Those two examples look like the system is working. Someone steps out of line, they get taken to ANI. It seems we've got quite diligent folks observing and watching AfDs, so it doesn't seem too drastic of an issue. Each case appears to be specific to the user, and I wouldn't want to paint all NACs with a broad brush, especially when they do so much good. I do think there's a chance that an NAC can fly under the radar, if folks aren't aware of who all the sysops are, so I could support a bot auto-labeling NACs when they happen. ~ Amory (u • t • c) 02:10, 19 February 2018 (UTC)[reply]
Oppose this is a baby and bathwater approach. There isn't a widespread problem at AfD with NAC's except in rare cases. Given the ratio of non-problematic NAC's versus problematic NAC's is vanishingly small, it is best to deal with it on a case by case basis. Blackmane (talk) 02:24, 19 February 2018 (UTC)[reply]
Oppose This seems to come up about once a year, maybe a bit more. It does not pass because of the fundamental open editing ethos of Wikipedia. So, until Wikipedia is no longer Wikipedia, it will not pass. Suggest it be added to Wikipedia:Perennial proposals. Jbh ^Talk 02:28, 19 February 2018 (UTC)[reply]
Oppose - I believe that in the legal world they say "Hard cases make bad law". If some non-admin is closing things inappropriately, deal with that person, or ask for a re-opening. There's no need for this. Beyond My Ken (talk) 02:31, 19 February 2018 (UTC)[reply]
Opposeas too Draconian. It has to be noted that there are non-admins who make correct closures and this would bring that to a halt. MarnetteD|Talk 02:49, 19 February 2018 (UTC)[reply]
Oppose per above power~enwiki (π, ν) 02:55, 19 February 2018 (UTC)[reply]
Oppose, per WP:NOSE. Non-admin XfD closures are not causing significant disruption (as far as I can tell), and I don't see any reason we should prevent experienced editors without the bit from assessing consensus on XfDs. Indeed, there are some non-admin editors I'd trust to assess consensus better than certain uers with the bit! -- Thanks, Alfie. ^{talk to me | contribs} 03:44, 19 February 2018 (UTC)[reply]
Support - admins are vetted for their ability to interpret community consensus. It makes sense to leave closing deletion discussions, which decide whether or not a specific sysop tool is used, to those in the sysop group. -- Ajraddatz (talk) 04:37, 19 February 2018 (UTC)[reply]
Support per ajr. It's been mentioned in recent RfAs that one of the big things the community wants more admins for is for AfD closures, and there is a general sense that the current quality of NACs is low at AfD, and wanting more sysops to deal with it. WP:Relist bias is probably the best essay on the subject as it relates to AfD and relisting, but the general principles are the same. The things that non-admins should feel comfortable closing aren't the things that are taking up much time anyway: clear cut keeps. Anything beyond that, should be an admin call per our guidance. There are plenty of places that are more NAC-friendly (I was a frequent RM closer before I got the bit, and RM is probably the most NAC-friendly environment we have on en.wiki), but AfD really isn't one of them.
People like NACing there as it seems like an easy way to get experience for RfA, but it usually isn't even that, as someone will either make a bunch of dumb closes and get opposed on the grounds of general annoyance without citing diffs or the closes will be so boring that no one will really care. I see no real negatives to this proposal for the community or for the individuals closing. TonyBallioni (talk) 04:43, 19 February 2018 (UTC)[reply]
Oppose - if I wasn't able to do NACs, I probably wouldn't have wanted to become an admin, and if you read my RfA and TP archives, I certainly wasn't perfect as a closer, and still am not (I'm certainly not much better at avoiding completely unnecessary run-ons ). We should give people a chance. If they do a bad job and aren't receptive to feedback, then deal with them individually. I'd say most NACs are probably fine. ansh 666 08:09, 19 February 2018 (UTC)[reply]
Oppose The only privilege admins should have is the direct use of the extra tools in the admin toolkit. Closing discussions should merely require a keyboard and (optionally) a brain. If a user is causing a problem, handle that as you would any other dispute or source of disruption. --Jayron 32 16:01, 19 February 2018 (UTC)[reply]
Oppose - This would need evidence of sustained and pervasive disruption, which does not mean two recent ANI threads. See also availability heuristic. GMG ^talk 16:10, 19 February 2018 (UTC)[reply]
Oppose--Needless policy-expansion.Echo GMG.~ Winged Blades^Godric 16:27, 19 February 2018 (UTC)[reply]
Oppose "Bad" closes are not limited to non-admins, and all can be corrected. Alanscottwalker (talk) 20:38, 19 February 2018 (UTC)[reply]
Oppose The only reason admins are the primary closers is that they have the tools needed to delete if that's the consensus. Admins are also called on at AN to evaluate consensus but there, like here, any editor in good standing can and should be able to do it. The only practical reason for non-sysops to not close "delete" results is the possibility that they can't find a sysop who's willing to go along, with resulting drama and disruption. If we had a rule that admins had to enforce non-sysop "delete" closures without dithering (and without fear of being criticized), I'd be fine with that. This should be a community decision; not a sysop-filtered one. (Which is not to criticize admins in the slightest; this is just a comment on this being a wiki, not on admins.) Regards, TransporterMan (TALK) 23:06, 19 February 2018 (UTC)[reply]
Strong Oppose - As mentioned above, this is a very bad idea in general. Admins are already overloaded with work, and in many cases don't have time to close AfD discussions (which can end in Keep/Merge/Redirect/No Consensus outcomes, none of which require sysop involvements). While there are occasional issues with non-admin closures, these are relatively small in proportion to the number of good ones (and remember that even admins sometimes make questionable closes too, hence WP:DRV). As for the issues with users making questionable closes, this is better resolved through other means specifically meant for that particular user, as opposed to a blanket ban on NACs, the vast majority of which are constructive. Narutolovehinata5 ^tccsdnew 01:49, 20 February 2018 (UTC)[reply]
Oppose I've closed and relisted AfD discussions. I've made a few mistakes starting out (see here and here), but I am happy to listen and correct my errors. It becomes a problem when folks cannot listen to constructive criticism. We should be looking at how many 'naccers' there are on average and how many of them are causing problems. Hopefully the numbers should reveal the actual extent of the problem. !dave 08:13, 21 February 2018 (UTC)[reply]
Oppose this and the alternate proposal. The few non-admin closing errors are easily corrected. It seems the reduced workload for admins by having non-admin closers and relisters far outweighs the work created by an occasional error. That being said, I personally have never closed an AfD as there is no rush, I'm happy to wait for an admin to get around to it. I wouldn't encourage another non-admin to start doing this unless they are trying to establish a case for future RfA. Jack N. Stock (talk) 08:23, 21 February 2018 (UTC)[reply]
Oppose. I'm opposing this because I believe we can handle it on a case-by-case basis. That said however, because maintenance areas are very clearly a playground for new and/or inexperienced users and those who simply enjoy the power of being 'anyone who can tinker with Wikipedia's back office', we must be more firm in asking them to refrain from NAC until they are more competent, or face a T-ban from NAC. Anyone who makes NAC to gain 'experience' in order to become an admin should already know enough about reading consensus at AfD without messing about with it. Anyway, that's how I learned about it, and I didn't close or need to close any before I ran for the bit. I had nominated a few hundred though and watched them to see what happened to them. Kudpung กุดผึ้ง (talk) 10:59, 21 February 2018 (UTC)[reply]
Oppose. It's disappointing to see my essay, WP:Relist bias, being used to support non-admins being barred from making closes over a wide class. The real issue is poor NACs, not NACs in general. We have plenty of non-admins who are fine closers, and many of our experienced admin closers got their starts as non-admin closers (myself included, though I've not been particularly active closing discussions recently). If non-admins make a mistake, try talking to them. This step is often skipped in favor of complaining about their action, but usually, a quick word can make a difference. If the non-admin is particularly stubborn in refusing to listen to advice from experienced editors and makes persistent mistakes, then that's a behavioral issue that can be dealt with as usual. ~ Rob₁₃^Talk 03:42, 25 February 2018 (UTC)[reply]

Alternate proposal

How about we make it so that NACs/relistings can only take place after 8 days, as opposed to the ordinary 7? I know NOTBURO and CREEP are concerns, but this would temper the super rushed attitudes of many non-admin closers. ansh 666 02:38, 19 February 2018 (UTC)[reply]

This still seems to be fixing a problem that doesn't really exist. The current system seems to be working fine, so I'm hesitant to make the policy more complicated for a problem that is already under control. Dennis Brown - 2¢ 02:54, 19 February 2018 (UTC)[reply]
Comment (edit conflict) If we are going to address hasty closes we might as well say best practice is that no one close an AfD until it rolls into the old log. This was suggested at WT:AFD#When did AfDs go from running for 7 days to 6 and a bit days? because of a perceived problem with admins closing AfDs too soon. Personally I think it would be a good idea and should cut down on a bit of drama. Mind, I think drama is a constant on Wikipedia and if we tamp it down at AfD it will merely rise again elsewhere - but might as well give it a try. Jbh ^Talk 02:59, 19 February 2018 (UTC)[reply]
Support- It seems that the non-admin closures mostly occur before an admin has had a chance to close, this would prevent this. I don't see why anyone should oppose AfDs closures being delayed up to an entire day if the outcome ends up being correct, rather than have someone jump the gun and do a poorly thought out close. Of course, there still needs to be the exception for withdrawing your own nomination.--Rusf10 (talk) 03:20, 19 February 2018 (UTC)[reply]
Support - We may as well try it, although I may have a CoI because I am one of the editors mentioned at the top. :) Jdcomix (talk) 03:45, 19 February 2018 (UTC)[reply]
Support and I'd actually make it wait until it hits the second day on the old log. TonyBallioni (talk) 04:16, 19 February 2018 (UTC)[reply]
Oppose as a rule, though I'd support this as a suggestion. power~enwiki (π, ν) 04:34, 19 February 2018 (UTC)[reply]
I don't think requiring non-admins to wait an extra day is going to make any significant difference. They'll just be jumping at the bit to close the discussion at the new time. I think a better idea would be to consider why the non-admin closers are so rushed, when the admin closers don't seem to be. -- Ajraddatz (talk) 04:39, 19 February 2018 (UTC)[reply]
- Ajraddatz, see my comment above re: RfA for the first part of your question. I highly suspect people view it as a way to get experience for an RfA not realizing it isn't something anyone really looks at unless you make mistakes or are annoying and relist everything without thinking. Admins are relaxed because most of these things aren't emergencies, and IMO, AfDs are relatively boring to deal with. I've been doing more AfD closes of late, but I generally don't enjoy them and mainly do it as a chore because I think that it's an area admins should help out in at least once in a while to keep aware of the practical application of community consensus. TonyBallioni (talk) 04:48, 19 February 2018 (UTC)[reply]
Oppose WP:SNOW closes are not restricted to admins nor should anyone have to wait for them to occur. Also waiting 24 hours makes no difference to a close. MarnetteD|Talk 04:50, 19 February 2018 (UTC)[reply]
Comment - I didn't explain very clearly in the original proposal (and it's certainly not ready wording-wise in any case), so here's some more detail. Within the last year or two, there have been a spate of non-admins closing and relisting discussions rapidly, frequently before or right after the discussions come to the 168-hour mark. The latest went through the newest "Old" log barely an hour after it ticked over (midnight GMT), making questionable closes and relists before a more competent closer was able to get to them. Maybe they're racing to get pseudo-admin edits in before the actual admins get there, I don't know. This new rule (I'm fine with it being just a suggestion per Power, as well) would slow down the non-admin rush, cut down some on relist bias, and help give admins - who as Tony says are generally a lot more relaxed about closing times - a chance to see discussions that have petered out and can be closed (especially those that should be closed as delete) before, for example, someone gets to them and puts them in a new log just because the outcome isn't immediately obvious. Of course, the obvious exceptions for speedy/SNOW closures would still apply. And at the very least, if this doesn't come to pass, we should add a reminder somewhere about WP:There is no deadline and that having old AfDs sit in logs that are over 7 days old isn't necessarily a bad thing. ansh 666 08:04, 19 February 2018 (UTC)[reply]
Ping Dennis Brown, Ajraddtz, and MarnetteD for my explanation above; sorry about the short initial statement, but I was in a bit of a rush and didn't get to explain as well as I should have. In short, I do think it'll make a difference, both in the quality of closes and in the number of meaningless relists. ansh 666 08:26, 19 February 2018 (UTC)[reply]
/facepalm I can't spell Ajraddatz, sorry! ansh 666 08:26, 19 February 2018 (UTC)[reply]
Oppose - I don't see that an additional day makes any difference at all. Either they're allowed or they're not. Again, if a particular editor is a problem, they can be dealt with individually via warnings, sanctions, or bans. Beyond My Ken (talk) 12:32, 19 February 2018 (UTC)[reply]
Oppose implies that admins are prefered when closing discussions. They should not be. Admins are only preferred when protecting an article, blocking a user, or deleting an article. The actual closure of discussions should not be restricted to admins, nor should admins be given preferential treatment thereof. --Jayron 32 16:02, 19 February 2018 (UTC)[reply]
WP:NAC (Experienced non-admin editors in good standing are allowed (although not necessarily encouraged) to close some XfD discussions. - emphasis mine), the existence of WP:BADNAC, and WP:DELPRO/WP:NACD (Usually, both closing and relisting are administrator actions.) disagree. The scope of NAC has grown a lot since I started at AfD about 5 years ago - it was intended for super obvious cases, but because of the super-backlog year or two at AfD, non-admins started doing more complicated closes and more relists. Non-admins are unable to consider the full spectrum of results, which results in bias towards certain results - I still have my own bias towards merge/relist, which was a source of opposition at my RfA regarding bad NACs. There are obviously varying opinions on whether this bias is a problem or not, but the fact that, as you say, admins are preferred when closing discussions shouldn't be under dispute. ansh 666 18:55, 19 February 2018 (UTC)[reply]
It should be under dispute, and we should be constantly pushing back against any notion that admins are a special class of editors who deserve special privileges beyond that which their toolset directly grants them. Non-admins are not automatically lesser citizens in the Wikipedia world, and should not be treated as lesser. They have full respect and rights until such time as they have proven untrustworthy as individuals. --Jayron 32 13:17, 20 February 2018 (UTC)[reply]
A fine sentiment, and one which is true in most places on Wikipedia. But it's wholly unsupported by policy in this specific area. Non-admins do not have the "right" to close discussions as delete, which leads to problems which this proposal is intended to address. (And honestly, nobody has any rights here, only privileges, but that's a whole different discussion.) ansh 666 19:01, 20 February 2018 (UTC)[reply]
Arguably, Wikipedia is built neither on rights or privileges, but on utility. You're only judged by how useful you are in working on the organization's core mission. You don't have rights or privileges, you are only useful or not useful. And on the question of policy, policy does not exist before us, it exists after us. Wikipedia policy does not shape behavior; Wikipedian's behavior shapes policy, and if we decide we want to stop treating non-admins like second-class citizens at Wikipedia, then we just do that. Policy is only as useful as it is useful to our mission, and we don't follow policy simply because someone who got here before us wrote it. We follow policy because following the policy makes for a better encyclopedia. --Jayron 32 19:07, 20 February 2018 (UTC)[reply]
So you're saying that you want non-admins to be able to delete pages? Because I don't understand what else you could do to "stop treating non-admins like second-class citizens" at AfD. As I said, in this area there are certain things that the community has determined that non-admins shouldn't be able to do, to, as you say, make for a better encyclopedia. (I'm honestly not understanding what you're getting at here). ansh 666 19:13, 20 February 2018 (UTC)[reply]
I've never used those words. Until such time as you read the words I've said, and are able to correctly quote them, I'm not sure we can have a productive discussion. When you deliberately misattribute something I say to serve your own purpose, that is not a way to treat one's interlocutor with respect. It's a shitty thing to do, and I did nothing to deserve that. Vaya con dios. I'm out.--Jayron 32 04:50, 22 February 2018 (UTC)[reply]
I'm trying to figure out what you're trying to say, since I legitimately don't understand your point. ansh 666 03:16, 23 February 2018 (UTC)[reply]
Oppose Seven days is not really "rushed". Alanscottwalker (talk) 20:41, 19 February 2018 (UTC)[reply]
The rush is after the seven days. Admin or not, discussions shouldn't be closed before then anyways. ansh 666 03:17, 23 February 2018 (UTC)[reply]
Oppose as this would be an effective ban on the non-speedy cases of WP:NOTBADNAC, except when a backlog develops at AFD. Most closers know when to close and when not to close, and as has been said already, those that don't can be dealt with on a case by case basis. Iffy★Chat -- 13:01, 23 February 2018 (UTC)[reply]
Oppose there are many very experienced good NAC closers so this is unnecessary. Where there is a problem with a closer they can be looked at individually Atlantic306 (talk) 10:04, 25 February 2018 (UTC)[reply]

Why are there no ethnic galleries anymore?

As the title says. I really liked it back when I could see examples of people from certain ethnic groups/diaspora. Why was it forbidden? --Spafky (talk) 16:03, 19 February 2018 (UTC)[reply]

I'll try to dig up the discussion, but there was a lengthy policy debate about this a few years back, and the consensus was that a) the galleries were a source of constant squabbling, discord, and disruption, and more importantly 2) The decision as to who's picture best to represent a particular ethnicity was open to rife abuse and amounted to original research. I'll try to find the discussion. --Jayron 32 16:05, 19 February 2018 (UTC)[reply]

Yeah, WP:DUE regarding who was selected also. - Sitush (talk) 16:08, 19 February 2018 (UTC)[reply]

Wikipedia talk:WikiProject Ethnic groups/Archive 13 is the original discussion that closed them down; it was from November 2015; though there had been several other discussions beforehand that led to that final discussion on the matter. --Jayron 32 16:10, 19 February 2018 (UTC)[reply]

One issue was Verifiability... how could the reader be sure that the person or people depicted in the image were actually FROM the nation or region in question (and not a tourist/visitor from some other country)? Blueboar (talk) 16:16, 19 February 2018 (UTC)[reply]

Actually, most of the galleries were of famous people who had citations in their article which clearly established their self-identification with the people groups; that was one thing we got right. However, there was still the problem that the sampling of people represented the ethnic groups well, a host of problematic no true Scotsman arguments, and the way that the specific choices could be used to influence WP:NPOV in some really bad ways (such as, for example, carefully choosing people of a particular skin tone, to represent a people group, etc.) It was all too much. --Jayron 32 17:11, 19 February 2018 (UTC)[reply]

"They are not black enough" being one particular argument I recall. Only in death does duty end (talk) 18:03, 19 February 2018 (UTC)[reply]

I think the RFC linked at WP:NOETHNICGALLERIES was the last one. Gråbergs Gråa Sång (talk) 22:49, 19 February 2018 (UTC)[reply]

While not "galleries" you can still find many of these images categorized on commons: for example in Category:Ethnic groups in the United States's sub cats. — xaosflux ^Talk 00:03, 20 February 2018 (UTC)[reply]

user:Yelysavet vs. Interlanguage-links

Yelysavet has been deleting scores of interlanguage-links from articles. Apparently without checking whether they had been or even can be correctly transferred to Wikidata.

User:Andy Dingley and myself have pointed out to him that relevant links pointing to the respective articles in sister Wikipedias have been lost by his wholesale removals.

I have brought this to the administrators noticeboard but was not able to evoke much interest. Instead I was advised to post the issue here.

I am not sure what policies and common practices apply and what to do about this.

I personally would like to see the Interwiki-links restored and I would appreciate your input on this matter.

best regards, KaiKemmann (talk) 12:21, 20 February 2018 (UTC) between[reply]

RfC: update to banning policy for repeat sockmasters

Please consider joining the feedback request service.

An editor has requested comments from other editors for this discussion. This page has been added to the following list:

Wikipedia policies and guidelines

When discussion has ended, remove this tag and it will be removed from the list. If this page is on additional lists, they will be noted below.

After being pointed out by Newyorkbrad at AN earlier that we might want to find a streamlined way to deal with community bans for repeated sockmasters to avoid what has become a recent trend of seeking formal bans for them at AN, I began workshopping some language with other users, and would like to propose the following additions be made to Wikipedia:Banning policy:

Editors who have been found to have engaged in sockpuppetry on at least two occasions after an initial indefinite block, for whatever reason, are considered de facto banned by the Wikipedia community. Publicly documented CheckUser evidence should typically be involved before a user is considered banned in this way. Users fitting this criteria are subject to the same unban conditions as users banned by community discussion.
Administrators should typically place a notice at Wikipedia:Administrators' Noticeboard alerting the community of such a ban as well as place Template:Banned user to the master's user page and add the user to any relevant Arbitration Committee sanctions enforcement list.

The terms of the proposal would make it so that after three indefinite blocks, a user is considered de facto banned under the banning policy. TonyBallioni (talk) 19:31, 20 February 2018 (UTC)[reply]

Comment – "this criteria" should be corrected to "this criterion", the correct singular. "Criteria" is plural. Dicklyon (talk) 05:34, 23 February 2018 (UTC)[reply]

RfC !votes

Support as proposer. Common sense alternative that codifies existing practice on unblocks in these scenarios, and will cut down on the threads at AN. The second paragraph being the standard form of enforcement, but distinct from the core of the proposal which in the first paragraph. TonyBallioni (talk) 19:31, 20 February 2018 (UTC)[reply]
Support A return to the way it used to be. This used to be codified into policy years ago, something to the effect of "Any user which no admin would unblock is considered de facto banned, and subject to the same restrictions as any banned user". Somewhere along the line, the common sense of that thinking was replaced by stupid worthless bureaucracy. It's time we returned to the notion that we don't have to vote on everything, if someone has been shown the door and can't stay away, they're just not welcome anymore. --Jayron 32 19:38, 20 February 2018 (UTC)[reply]
Support This will end the need for threads at AN and AN/I about these editors. MarnetteD|Talk 19:48, 20 February 2018 (UTC)[reply]
Support - The AN/ANI threads like this are ridiculous and only serve to give recognition to the trolls. Anyone who is socking to the point of being blocked on sight doesn't need a community discussion for us to know that they shouldn't be here. -- Ajraddatz (talk) 20:29, 20 February 2018 (UTC)[reply]
Support GMG ^talk 20:31, 20 February 2018 (UTC)[reply]
Comment I would support if that second paragraph were removed. You want administrators to notify the community via AN whenever an editor is found to have engaged in sockpuppetry twice? That wouldn't reduce the number of ban threads, it would greatly increase them. Sro23 (talk) 20:57, 20 February 2018 (UTC)[reply]
- Sro23, it depends on the situation, this was seen as a positive during the brainstorming as a way to keep accountability up. Obviously DENY is in play here, and the second paragraph was tweaked because of that. Looking over the AN threads, the comments I received on my draft of this, and other comments I received off-wiki, people prefer that there be some accountablility here, and that the tagging here fall under admin accountability, even if it is mainly clerical.
  I thought of this earlier today, and I think in practice the implementation would be somewhat like the requirement to notify for ECP or AN/RFC: a transcluded subpage could exist that archived quickly, but allowed for more public viewing of actions here. I don't think this is something that would be necessary for the random trolls and copyvio people who have made less than 100 edits, but would be something we want for vested contributors who later turn out to be sockmasters in order to promote transparency.
  As I said during the drafting, a lot of these concerns are about specifics of implementation that can be dealt with on a more practical level after the RfC by bold edits. The feedback I got was that people wanted a streamlined system that was also accountable. I think this is the best way to accomplish both of those goals, and think that there are ways to address your concerns. TonyBallioni (talk) 21:08, 20 February 2018 (UTC)[reply]
- The WP:AN thread would consist of "I blocked XXXX the sockpuppet of YYYY and put a banned tag on YYYY's page as this is the 3rd instance of socking by this indef blocked editor. Putting here in case anyone wants to review." That is about it. It won't be a long drawn out discussion. Maybe a few editors will say "looks good", or if I have screwed up, they will say so. Tagging like this should be an admin only thing, and subject to WP:ADMINACCT, thus we need reporting. Dennis Brown - 2¢ 13:48, 21 February 2018 (UTC)[reply]
Support per the clarification below and subject to it only applying once enacted and not retrospectively. Mjroots (talk) 21:22, 20 February 2018 (UTC)[reply]
Support per Jayron and applying a sudden outbreak of common sense. And I'd rather see a dozen "Notification" threads then yet another "Let's discuss this but we all know how it's going to happen and then hopefully there will be a snarky close which I will chuckle at" thread. ~ Amory (u • t • c) 21:24, 20 February 2018 (UTC)[reply]
Support would reduce the number of pointless noticeboard discussions. Hut 8.5 22:16, 20 February 2018 (UTC)[reply]
Support: Much faster process than opening a discussion at AN or ANI. — MRD2014 ^Talk 00:47, 21 February 2018 (UTC)[reply]
Support Considering TonyBallioni's reply to my question below.--Jetstreamer ^Talk 00:56, 21 February 2018 (UTC)[reply]
Support, but suggest using a parameter in Template:Sockpuppeteer to indicate banned status, rather than slapping around separate templates. GAB^gab 02:35, 21 February 2018 (UTC)[reply]
Support. Time to stop wasting time with these people. ♠PMC♠ (talk) 04:57, 21 February 2018 (UTC)[reply]
Support The latest 3 or so banning discussions on AN proved that something like this is long overdue, because the pile on support is just symbolic since no reasonable editor can argue against enacting such ban on prolific socks and recidivist vandals (cf. Dysklyver speedily closed ban discussion). I also agree with GAB's suggestion, to add parameter to {{Sockpuppeteer}} to indicate this kind of auto-ban. The traditional {{banned}} then can still be used where the discussion did indeed take place, since this proposal is not proposing abolishment of ban discussions completely. –Ammarpad (talk) 06:33, 21 February 2018 (UTC)[reply]
Support Avoids the ANI thread of horror. !dave 06:51, 21 February 2018 (UTC)[reply]
Support It will save a lot of time and frustration. How to deal with articles started by those sockpuppeteers and sockpuppets? The Banner talk 11:07, 21 February 2018 (UTC)[reply]
Support - time the process was streamlined. Not that banning will stop the socking - like it didn't with Kumioko's WMF ban (Ha! I actually met that guy) - but it will be easier to close the SPIs they cause and range block them. Kudpung กุดผึ้ง (talk) 11:13, 21 February 2018 (UTC)[reply]
Support - This solves a couple of problems, including the perpetual AN ban discussions for editors who are already banned, as well as answering the question about automatically reverting edits of their socks. Rarely do we really need a de jure ban discussion for prolific sockmasters, so this would reduce the paperwork for what is always blindingly obvious. Dennis Brown - 2¢ 13:39, 21 February 2018 (UTC)[reply]
Support - This sounds reasonable and will hopefully free up admin attention to other priority topics. - Knowledgekid87 (talk) 14:55, 21 February 2018 (UTC)[reply]
Support - Each time a thread is started we're essentially giving recognition to the trolls/socks, Doing it this way is not only quicker but also we're pretty much DENYING any sort of recognition, 110% support. –Davey2010^Talk 16:41, 21 February 2018 (UTC)[reply]
Support per nom and pretty much everything written above. -Ad Orientem (talk) 16:47, 21 February 2018 (UTC)[reply]
Support for the reasons given above. These come up more than occasionally at Category:Requests for unblock and I believe this proposal will help clarify such cases. I don't particularly see a need to post a nice at WP:AN but I believe we expect such notices would be literally that, a notice where typically nobody needs to comment. So, fine, I can see the value. :) --Yamla (talk) 18:11, 21 February 2018 (UTC)[reply]
Comment I have been myself treating a couple of sockmasters that they are "on verge of getting sitebanned".[14][15] This proposal will make things easier but I disagree with "CheckUser evidence should typically be involved". Banned editors like Colton Cosmic have been socking with IP [16] and CheckUser won't help you there. D4iNa4 (talk) 18:26, 21 February 2018 (UTC)[reply]
Oppose. If CU evidence is involved, they should be CU blocked, not community banned. Note that any such community ban would be appealable to ArbCom, as private information (CU evidence) would be involved. ~ Rob₁₃^Talk 18:32, 21 February 2018 (UTC)[reply]

No, BU Rob13, CU don't make policy, they just provide us with the information we need to help us in our decisions to block and/or ban. A 'CU block' is only where private information, such as linking a name to an IP is not allowed, but in many banning cases, the socks have already done that for themselves. And of course, try as they may, Arbcom do not make policy either - they implement it. Kudpung กุดผึ้ง (talk) 00:09, 22 February 2018 (UTC)[reply]

I don't care at all about that, obviously. It doesn't change ArbCom's workflow at all. It does make it impossible for individual CUs to lift blocks on long-term sockmasters without community consultation, but they don't do that anyway. What I do care about is that now almost every CU block ArbCom reviews will also (technically) be a community ban. That's going to cause drama that no-one really wants to deal with. ~ Rob₁₃^Talk 02:12, 27 February 2018 (UTC)[reply]

Neither group makes policy, but the existing blocking policy allows CheckUsers to make any block based on CU data a CU block. The data they based the block upon is the private information you reference. The Arbitration Policy allows ArbCom to review the appeal of any block or banned user. We choose not to review community bans except in the presence of private information. As noted earlier, CU data is always private information, so any block or ban based on CU data can be appealed to ArbCom. ~ Rob₁₃^Talk 01:34, 22 February 2018 (UTC)[reply]

I raised the option of making CU blocks effectively bans in an earlier discussion. The RFC takes nothing away from existing CU blocks that involve private date, but is for removing the unnecessary bureaucracy of ban discussions on publicly known sockmasters where a CU Admin has confirmed that 2, or more, accounts are linked. Mixing CU blocks involving private information with this discussion muddies the waters. Blackmane (talk) 03:43, 22 February 2018 (UTC)[reply]

@Blackmane: The point of a community ban is to force community review before the editor is unblocked. That is the only purpose of a ban, since our policy treats banned and blocked editors otherwise the same. In the case of CU blocks, those blocks can't be lifted by the community, and so a community ban is pointless. Note that individual CheckUsers essentially never lift CU blocks for reasons other than mistakes; they just let ArbCom handle it. ~ Rob₁₃^Talk 16:59, 22 February 2018 (UTC)[reply]

Not entirely true: ArbCom does have the capacity to review CU blocks and bans involving private information, nothing would change that. ArbCom already might be involved in the reviews of every CU block that is also reviewed by the community: nothing here would change that either.

You are wrong, however, in saying that it is not normal for the community to review CU blocks. It is relatively standard for a blocked user to make an unblock request via UTRS or even on their talk page, a CU to review it, post results, and then it be brought to the community for discussion. These are all examples of CheckUser blocks reviewed by the community: [17], [18], [19], [20], [21]. This addition has no impact on the ability of ArbCom to review a CheckUser block. What it does do, however, is require that in situations where a user has block evaded multiple times, that short of an appeal to ArbCom, they must have community review.

If this is already standard procedure for non-ArbCom reviewed CU blocks, then all we are doing is codifying it, which is a good thing as it makes sure these reviews are consistent. If it is not already the standard procedure, then it is also something that the community clearly wants as this has near unanimous support. Nothing here impacts ArbCom's abilities to review blocks. All it does from an unblocking angle is make procedures clearer for CUs and admins who are dealing with requests made on user talk pages or via UTRS. If what you say is true that all CU unblock reviews should be handled by ArbCom and people see this as an making it harder to be unblocked short of a direct appeal to ArbCom, then it would also be good for you as it would encourage them to make an appeal there. TonyBallioni (talk) 23:50, 22 February 2018 (UTC)[reply]

@BU Rob13: The purpose of the RFC iss to define the practice around editors being indefinitely blocked, but not by a CU. If a CU comes along and makes the call to levy a CU block, that changes the block conditions to those governed by the CU block policy, and would be at the discretion of the CU admin. This RFC has no impact on that. What is being set up here is a process whereby editors who are indefinitely blocked by non-CU admins and who have been caught socking, with the assistance of a CU admin, are considered banned, but not as a CU levied block. The block would remain a non-CU indefinite block just that the conditions around that block would now fall under the banning policy. I'm not sure where the confusion is. Blackmane (talk) 03:17, 23 February 2018 (UTC)[reply]

For clarity, CU blocks would fall under this, but the ability of ArbCom to review them would not be impacted. This simply cuts down on the pointless ban discussions and sets a procedure for when a user has not specifically appealed to ArbCom, but has appealed on their talk or via UTRS (which any search of the AN archives shows is not out of the ordinary.) TonyBallioni (talk) 03:37, 23 February 2018 (UTC)[reply]

Cuts down on the discussions by initiating a discussion for every single editor blocked twice for socking? This will increase discussions, given the reporting requirement at AN. I'll reiterate that CU blocks should be used if CU evidence conclusively proves socking. Given the requirement for "publicly documented CheckUser evidence" before implementing a ban of this type, that's your whole use case. ~ Rob₁₃^Talk 03:39, 25 February 2018 (UTC)[reply]

Support Seems like a sensible way of streamlining the process. --Malcolmxl5 (talk) 20:03, 21 February 2018 (UTC)[reply]
Support — Per nomination, and other support votes, would greatly streamline the process.
Regards, SshibumXZ (Talk) (Contributions). 20:42, 21 February 2018 (UTC)[reply]
Support – I've never really understood the need to request a community ban for these kinds of editors. The administrative state of affairs changes only marginally, if at all, before and after the decision to ban. As this proposal is designed to cut back on such proposals at the admin noticeboards, I suppose I support this in principle, though I'm not sure whether even Template:Banned user is necessary per WP:DENY. Mz7 (talk) 21:03, 21 February 2018 (UTC)[reply]
Support I cannot understand BU Rob13's opposition (as in, I'm reading his words but can't make out the meaning). Anything that closes the door on ne'er-do-wells is a good thing, private information be damned. Chris Troutman (talk) 02:04, 22 February 2018 (UTC)[reply]
- @Chris troutman: I'm saying that CU blocks already close the door. You're building a second door and then shutting that one. If the original door were to open, the fact the new door is closed would be irrelevant. Perhaps I'm straining the analogy, but I think it actually works fairly well; if ArbCom accepted an appeal of a CU block, we would also lift the community ban. This is adding a bunch of process wonkery that is completely irrelevant to any end results. It has no effect but to increase bureaucracy, make a bunch of pointless threads at AN, and waste the time of editors who could do good elsewhere. ~ Rob₁₃^Talk 17:02, 22 February 2018 (UTC) Fixing ping: Chris troutman ~ Rob₁₃^Talk 17:03, 22 February 2018 (UTC)[reply]

BU Rob13, this is beginning to divert from the essence of the proposal. As I read it, the RfC not intended to endanger the 'power' vested in you (or others) in giving you the CU bit or you being an Arbcom member. Kudpung กุดผึ้ง (talk) 18:34, 26 February 2018 (UTC)[reply]

Support As I was involved in a small way with the drafting of the RFC, my support is obvious. Blackmane (talk) 03:45, 22 February 2018 (UTC)[reply]
Support - I'm one of those editors who almost always !votes in favor of a formal ban for such editors, feeling that an understood de facto ban was just not enough, and a formal ban give a little more protection to those deleting the contributions of those editors. I'm happier with this, although I don't think the phrase "de facto" needs to be in there, as what is being proposed is essentially a formal ban under X circumstances. Nevertheless, I support this, as the formalization of a de facto ban in policy makes it a formal ban, and therfore no longer de facto. (I hope that wascomprehensible.) Beyond My Ken (talk) 05:13, 22 February 2018 (UTC)[reply]
@Beyond My Ken: Perhaps I understand you. "De facto" should not be in this proposal and should be removed now. Because what usually happens is that a repeat sockpuppeteer (Like Dysklever example above) is usually de facto banned once they accumulate like 2-3 entries at SPI and that's why discussion to turn the ban into de jure is usually closed speedily as enacted. Now if this proposal passes, then it will effectively triggers de jure ban automatically at second instance of socking which is as effective as any ban enacted after AN discussion. Therefore since ban enacted after AN discussion is not de facto but formal this one too is not de facto but formal. But if the proposer is aware of this and still meant it to be de facto then still we need to discuss the real formal ban at AN. And from the impressions of everyone above and the intent of the proposal (as I understand it) is to stop the needless and largely symbolic ban discussions at AN which are time waste and even dignifying to the recidivist sockmasters whom we should WP:DENY. –Ammarpad (talk) 07:39, 22 February 2018 (UTC)[reply]
@Beyond My Ken and Ammarpad: to borrow a line from BMK's talk page, this is a crowdsourced horse. I mainly drafted it and got feedback on certain points in order to craft language that I thought would be a consensus version that everyone could get behind when put to an RfC, even if they had minor quibbles. The de facto language was wanted by some because it made clear that there had not been a discussion. I don't think it necessary, but I also don't see the harm. The language is clear that WP:UNBAN applies to these cases, which is the only functional difference between an indef block and a ban. Because that is the case, the distinction between de jure and de facto ban is no existent in terms of actual impact. The only difference is whether a discussion has been held. TonyBallioni (talk) 14:19, 22 February 2018 (UTC)[reply]
I can live with it, I was just pointing out a logical inconsistency. Better to have it than not. Beyond My Ken (talk) 00:56, 23 February 2018 (UTC)[reply]
Agree too, it is an improvement, though not as I expected. So under the current system, a repeat sockpuppetter is usually seen by the community as banned both through despising their actions and how they respond in banning or unblocking discussion about them. But this practice is not codified and not written anywhere, and that's the essence of this proposal to codify and give written recognition to this accepted practice. –Ammarpad (talk) 06:40, 23 February 2018 (UTC)[reply]
Support proposal in spite of believing its verbiage can be improved. It is sufficiently sound and no time limits prevent improvements from coming about later; over time.--John Cline (talk) 20:51, 22 February 2018 (UTC)[reply]
Support - The less long and useless threads, the better. RileyBugz^{私に叫ぼう}_私の編集 00:07, 23 February 2018 (UTC)[reply]
Support with minor tweak. "De facto" means that it's not codified; that's like saying "When someone's found to have gotten three indef blocks for sockpuppetry, he's officially been unofficially banned." But the point of the proposal is great. Almost never do we need to have those ban discussions, because such users are almost guaranteed never to be unblocked without a long and careful discussion. And in the situations where we do need those discussions, it's because the user's somehow less obvious (e.g. making appeals on UTRS) and might get unblocked by someone not aware of the situation. Such users should never be unblocked without a discussion, so let's make it official that they are to be considered banned and that we can place a template indicating "banned user" onto the userpage, to ward off ignorant unblocks. Nyttend (talk) 05:02, 23 February 2018 (UTC)[reply]
Support wording and implementation can always be tweaked, but the idea is right - avoid unneeded ban discussions and show baby-sockmasters that they are sitting on the ejection seat. Agathoclea (talk) 15:19, 23 February 2018 (UTC)[reply]
Easy support Makes perfectly reasonable sense. Doc James (talk · contribs · email) 11:50, 24 February 2018 (UTC)[reply]
Support per TonyBallioni and further it saves time to avoid Ani discussions and clearly a way to steamline the process.Pharaoh of the Wizards (talk) 16:37, 24 February 2018 (UTC)[reply]
Support I was actually thinking about this the other day; it makes it easier to go to sites like Fiverr, Upwork etc. and go "this user is indefinitely community banned on Wikipedia, please remove their paid editing services from your site". jcc (tea and biscuits) 19:11, 26 February 2018 (UTC)[reply]

RfC discussion

Question "The terms of the proposal would make it so that after three indefinite blocks, a user is considered de facto banned under the banning policy" - this applies only to sockmasters yes? If an editor had three indefs for other reasons, they would not fall foul of this, would they? Mjroots (talk) 21:16, 20 February 2018 (UTC)[reply]
- Mjroots: No, they would not. That was my simplifying the wording to surmise the impact it would have re: socking and block evasion, not part of the actual proposal (which is in green). The simpler and more precise way of putting it would be: any user who socks twice after being indefinitely blocked is de facto banned. Thanks for the question. TonyBallioni (talk) 21:20, 20 February 2018 (UTC)[reply]
Question I'd tend to support, but why there should be two occasions after an indef block? Wouldn't it be enough with just one? Sockmasters are warned about their behaviour, especially after a CU.--Jetstreamer ^Talk 23:10, 20 February 2018 (UTC)[reply]
- Jetstreamer, well for one, I don't think we could get consensus for de facto ban on the first occurrence of socking for block evasion, and so I wrote the proposal for what I thought would pass, but on top of that, we recognize that users fuck up. There are users like DrStrauss, who got CU blocked, and then tried to clean start, and got blocked again. He made a mistake, and I know for a fact that there are many admins and functionaries, and likely some ArbCom members who would probably be willing to unblock him after a CU gave the all clear without needing the whole ceremony of an AN appeal (and I say this as the editor who filed the SPI on him), and if you opened up a ban conversation on him now, it would likely fail at AN.
  Nothing in the proposal prohibits admins for taking blocks to AN for review, nor does it prohibit users from asking for a ban at AN if there circumstances that would warrant it before two occasions of using socks to block evade. It just sets a clear criteria for when the conversation isn't needed. TonyBallioni (talk) 00:08, 21 February 2018 (UTC)[reply]
- Furthermore, in some cases users forget to log on and get blocked because it is believe they are socking. It's bit harsh to drop the banhammer in that case. Others may lose their password and create a new one account but neglect to create the link between the two. Various permutations on these sorts of things will happen, especially to new users. The proposal allows for some level of AGF. Blackmane (talk) 03:48, 22 February 2018 (UTC)[reply]
Comment - while I support the merits of this proposal, I do believe that where it says "... to have engaged in sockpuppetry ...", sockpuppetry should be piped from Wikipedia:Sock puppetry#Inappropriate uses of alternative accounts as: "sockpuppetry", to remove any confusion as to whether or not Wikipedia:Sock puppetry#Legitimate uses are meant to be part of the cumulative threshold for banning; perhaps they are?--John Cline (talk) 06:09, 21 February 2018 (UTC)[reply]
Can you come up with a single legitimate reason to use a sockpuppet to dodge a valid block? --Jayron 32 13:39, 21 February 2018 (UTC)[reply]

By definition, if you use a 2nd account for legitimate reasons, it isn't a sock puppet, it is an alternative account. The term sock puppet is only used (or should only be used) when describing the use of an alternative account for abusive purposes. No further explanation should be needed. Dennis Brown - 2¢ 13:42, 21 February 2018 (UTC)[reply]

yep, that is what i was going to say. nonissue. Jytdog (talk) 16:54, 21 February 2018 (UTC)[reply]
No Jayron32, I can not. Was there something in my comment that led you to ask such a question? Dennis Brown If the term sock puppet should only be used to describe the use of an alternative account for abusive purposes, why does our policy on sock puppetry have an entire section on legitimate uses? I merely suggested, in light of the policy oxymoron, that the raw term has the potential of being confused whereas piping the term, as described, allayed that potential at the cost of added clarity. If it's a nonissue, it's a nonissue raised in good faith. I'll rest on that.--John Cline (talk) 18:16, 21 February 2018 (UTC)[reply]
Yes, John. In a discussion about people using a second account to dodge a block on a first account, you brought up the point that are legitimate uses of second accounts. I was questioning the relevance of your point, since I have not, in 12ish years at Wikipedia, ever seen a situation where a person who was blocked on a first account ever had a legitimate excuse for then using a second account. So, I get that there ARE legitimate uses of second accounts. None of them are relevent to this discussion, which involves someone first being blocked, THEN using a second account, THEN being blocked again for that and THEN using yet ANOTHER account. I was struggling to understand a scenario where that qualified as, "any confusion" over "legitimate uses". --Jayron 32 18:27, 21 February 2018 (UTC)[reply]
Thank you Jayron32. I understand your dismay in the context described. I disagree, however, that such context ought be intuitively gleaned from the proposal as written. Found to have engaged in sockpuppetry on at least two occasions after an initial indefinite block does not unequivocally mean the engagement in sockpuppetry occurred while the indefinite block was active. It could as easily mean sockpuppetry that commenced after the initial indefinite block had been successfully appealed; I would argue that the ban provision is best served by allowing for both eventualities, as it is written. I assure you that if the proposal had said: found to have engaged in sockpuppetry on at least two occasions, circumventing an active block (or something similar) I'd not have commented as I did. Cheers.--John Cline (talk) 20:40, 21 February 2018 (UTC)[reply]
Actually it seems to me John Cline has hit on an important point here. Isn't this policy only intended to cover editors who sock while indefed blocked? I mean if someone gets indefed and then is unblocked, and then later, perhaps much later, is socks twice for reasons unrelated to ban evasion is this policy intended to cover that? As worded it seems it does but I'm not sure if that's the intention. After all it excludes people who sock twice but have never been indefed. Nil Einne (talk) 00:00, 22 February 2018 (UTC)[reply]
If someone block evades twice involving CU data, it is highly unlikely they will not be indef'd. This doesn't cover people who haven't been indef'd, as well, they aren't indef'd, so it makes no sense to go to unblocked to banned immediately. This is focused on block evasion after an indefinite block. TonyBallioni (talk) 00:08, 22 February 2018 (UTC)[reply]
To follow on, Jayron32's reply also asserts, if I may paraphrase, that this proposal intends only to weigh on indefinitely blocked sockmasters who are subsequently indefed again for socking anew to evade their initial block, and then found evading sanctions once again from yet another sock still. While I believe this is the requisite criteria intended for triggering a ban under this proposal, you can not expect ambiguous verbiage like editors who have been found to have engaged in sockpuppetry on at least two occasions after an initial indefinite block to adequately convey that premise.

Unless you expect users downstream to refer to this discussion for understanding, IIMO that the proposal's text ought to be reworked to reduce confusion and improve clarity. "At least two occasions" does not exclusively mean "two unique sock accounts", one account can certainly be found to have engaged in sockpuppetry on two distinct occasions and nothing currently written suggests the occasions (or sock accounts) must emerge sequentially, as given in Jayron's reply, with the first sock evading and being blocked before the second sock publishes its first evasive edit. Thank you all for considering my regards, or for ignoring them with civility and kind manners. I am beholden either way. Cheers.--John Cline (talk) 20:41, 22 February 2018 (UTC)[reply]

And at the very top of that section, it points to the two main Categories for legitimate alternate accounts, and goes on to say why it ISN'T sock puppetry to use accounts for the following reasons, ie: "These accounts are not considered sockpuppets." (emphasis mine) So it couldn't be more plain. It is logical to explain what is (top section) and what isn't (bottom section) in the same article, since people throw the term "sock puppet" around. I go into greater detail in the essay Wikipedia:Dealing with sock puppets, which I started after working at SPI for a year. To call multiple accounts "socking" requires a showing of ABUSE. Dennis Brown - 2¢ 18:23, 21 February 2018 (UTC)[reply]
Thank you Dennis Brown. I acquiesce to your expertise in this regard. Cheers.--John Cline (talk) 20:40, 21 February 2018 (UTC)[reply]

RfC: Coverage of mass shootings in firearms articles

Please consider joining the feedback request service.

An editor has requested comments from other editors for this discussion. This page has been added to the following lists:

When discussion has ended, remove this tag and it will be removed from the lists. If this page is on additional lists, they will be noted below.

Should articles about firearms include information about mass shootings?–dlthewave ☎ 17:11, 21 February 2018 (UTC)[reply]

Background

After several recent mass shooting events, edit warring has taken place over whether or not an article about a specific firearm model should cover the weapon's use in mass shootings. This has been centered around various AR-15 style rifles, but the argument could apply to any firearm used to commit a crime.

There is also disagreement over whether or not AR-15 style rifle should include information about the category's prevalence in mass shootings, which has received significant RS coverage.

Relevant WikiProject Firearms essay

"In order for a criminal use to be notable enough for inclusion in the article on the gun used, it must meet some criteria. For instance, legislation being passed as a result of the gun's usage (ex. ban on mail-order of firearms after use of the Carcano in JFK's assassination would qualify). Similarly, if its notoriety greatly increased (ex. the Intratec TEC-DC9 became infamous as a direct result of Columbine). As per WP:UNDUE, "Neutrality requires that each article or other page in the mainspace fairly represent all significant viewpoints that have been published by reliable sources, in proportion to the prominence of each viewpoint in the published, reliable sources.". Therefore, the addition of said information should be limited to a simple link in the "See also" section."

Relevant talk page discussions

The first three discussions were consolidated to Wikipedia talk:WikiProject Firearms#Use of AR-15 Style Rifles in Mass Shootings. The centralized discussion has developed significant support for an RfC outside of WikiProject Firearms.

Terminology

Editors should be aware that there is some confusion surrounding the AR-15 name. "AR-15" is a trademark of Colt and technically only applies to the Colt AR-15. However, many manufacturers produce their own generic versions based on the same design, and these are often referred to as "AR-15" by the media and general public. Within Wikipedia, AR-15 style rifle covers the general category of weapons that use the AR-15 design. The article was recently moved from Modern sporting rifle and the two terms are used somewhat interchangeably. Efforts to reduce this confusion is outside the scope of this RfC.

Survey Questions

Two questions, pick one answer for each:

1. Should an article about a specific firearm model include information about its use in mass shootings?
- A. Do not include
- B. Include links to notable shootings in the "See Also" section (Current WikiProject Firearms essay)
- C. Include a paragraph-style section
- D. Evaluate how much to include on a case-by-case basis
2. Should AR-15 style rifle include information about the category's prevalence in mass shootings?
- A. Do not include
- B. Include only statistical data
- C. Include a paragraph-style section
- D. Discuss at Talk:AR-15 style rifle Option added 27 Feb 18

Straw-poll: Coverage of mass shootings in firearms articles

Situational: 1. C | 2. C - In the case of the AR-15, I am convinced that a neutral paragraph can be forged. These paragraphs should only be added if the school shooting in question has had an impact on the gun, or new regulations have been put forward as a result. - Knowledgekid87 (talk) 17:19, 21 February 2018 (UTC)[reply]
Oppose. The current guidelines are sufficient. If a particular instance changes it, then we decide then. For example, the Douglas High shooting may, in fact, lead to legislative changes that result in the use being particularly notable. Currently, it has not. So the rush to make this change is premature. Slow down. Many editors I see trying to put this everywhere (dare I say spam it) seem to be more driven by something other than a desire for accuracy. And whether or not well-intentioned people incorrectly use the term AR15, using a Ruger AR-556 doesn't belong in the article about the Colt AR15. Niteshift36 (talk) 17:27, 21 February 2018 (UTC)[reply]
Depends (1D and 2C). More specifically:
- For individual firearms (e.g. SIG MCX), firearm manufacturers (e.g. Smith & Wesson), and firearm types/classes (e.g. assault rifle or combat shotgun): Depends. Barring exceptional circumstances such as those suggested by Knowledgekid87, a major cultural impact (i.e. Tommy gun (Saint Valentine's Day Massacre), Carcano (Assassination of JFK), or AR-18 (Provisional IRA) level), or a highly-publicised lawsuit against the manufacturer, they should generally not contain information on criminal use.
- For Colt AR-15 and AR-15 style rifle: Yes, there should be neutral, factually correct, and in-context information about mass shootings, given the high level of coverage in the media - but which also notes that the media is often incorrect.
Please ping me if anyone has any questions about my comments here; I won't be watching this discussion. ansh 666 18:10, 21 February 2018 (UTC)[reply]
(Changed 1C to 1D, since we're using that now. ansh 666 03:14, 23 February 2018 (UTC))[reply]
1C if indeed that coverage is there. (Impugning others' motives, not a good thing.) If someone holds up a bank with a gun of a certain type, or shoots their neighbor with it in some dispute, that's never going to deliver the coverage necessary: that coverage needs to specifically address the weapon, and political discussion about the weapon will help--et cetera. This is nothing new.
2C but duh, we're going to need a bigger paragraph. And, as I indicated below, the Colt AR-15 article should already include a brief summary of what weapons based on it have been used for. Drmies (talk) 18:21, 21 February 2018 (UTC)[reply]
1C/2C Assuming that sufficient reliable sources exist to craft NPOV text then Wikipedia needs to address the issues brought up by the sources. I would not consider lots of articles consisting of mere mentions that a given weapon/class of weapons were used to be 'sufficient' in this context. - Mere mentions in sources are sufficient for mentioning and linking the weapon/type from the event article but we should avoid back linking that would result in "this weapon was used in list of events" sections. Jbh ^Talk 18:31, 21 February 2018 (UTC)[reply]
1 = A...2 = A Oppose addition of crime and mass shooting content --RAF910 (talk) 18:36, 21 February 2018 (UTC)[reply]
Its no secret that guns are used in crimes and mass shootings though. If for example an AR-15 is modified due to an event then it would be notable enough for inclusion as an effect on how the gun is used going forward. - Knowledgekid87 (talk) 18:40, 21 February 2018 (UTC)[reply]
Yes..."Its no secret that guns are used in crimes and mass shootings though." In fact it's such common knowledge that there is absolutely no reason to even mention it in these articles. Like knives, we all know that they are used in crimes. In fact, world wide knives are the weapon of choice for criminals and killers, but we don't mention it in every knife article, do we.--RAF910 (talk) 19:32, 21 February 2018 (UTC)[reply]
If a type of knife is modified or banned as a result of a deadly event then yes of course we would mention it per WP:N. - Knowledgekid87 (talk) 21:59, 21 February 2018 (UTC)[reply]
OK, since were going down the rabbit hole anyway...I recommend that this policy be applied to all knife, weapons, vehicle, aircraft, anaimal and anything else that could possibly be used to commit crimes and kill people pages. We can call it "WP:Murder, Death, Kill". for short--RAF910 (talk) 22:14, 21 February 2018 (UTC)[reply]
We already do that... under aircraft types we have accidents and notable incidents, under car types we have recall mentions. The point is when people are killed and the killing device is changed to make improvements then it is noted. - Knowledgekid87 (talk) 23:39, 21 February 2018 (UTC)[reply]
1A - 2B - But it all depends, if a shooting took place and the specific model of AR used is important it should be mentioned on that models page. If it is general that an AR was used but the model is not mentioned or notable it should be on the AR-15 style rifle article. More specifically for individual models eg. Colt AR-15 and the like information should only be included if it lead to legislation or similar. An example would be Port Arthur massacre (Australia) where the Colt AR-15 was used and kicked off the legislation to ban guns. PackMecEng (talk) 18:49, 21 February 2018 (UTC)[reply]
1C iff the sources warrant it for the specific model, otherwise 1B, or at least a link the use of AR-15 style rifles in mass shootings (rather than individual shootings). 2C should most definitely be done. Headbomb {t · c · p · b} 18:52, 21 February 2018 (UTC)[reply]
1C and 2C. Especially 2C. The amount of coverage that the AR-15 has gotten in relation to mass shootings (whether rightly or wrongly) is way too extensive to ignore. It'd actually be a WP:NPOV and WP:DUE violation NOT to include it.Volunteer Marek (talk) 18:56, 21 February 2018 (UTC)[reply]
Oppose - any changes to the current policy (noted as "1B". This !vote is not based in any political ideology, (not "anti-gun" or "pro-gun") but simply the projects guidelines, such as WP:NPOV. If we start adding "paragraph-sized entries" to the articles of any firearm, or firearm type, brand or maker involved, these articles will quickly fill up with huge "mass-shooting and other related incidents" (or "Controversy") sections that will outweigh the remainder of the entire article. I'm not seeking to suppress this info in any way. These mass-shootings and other types of firearms-related incidents almost always have their own articles here already. Lengthy, detailed articles that always include extensive information about the firearm(s) used and links to the related pages of the firearm, it's type, brand and/or manufacturer. That is sufficient. (most of this I've already posted elsewhere, but I will add; there is nothing stopping anyone here from writing an article about "the use of "AR-15 style rifles" in mass-shootings", and linking it to every related article; mass-shootings and other related incidents, and articles about the firearms, related firearm types, brands and makers, etc. Just a thought. - ^theWOLFchild 19:13, 21 February 2018 (UTC)[reply]
1A, 2A (usually) These events are not related to the specific gun models. If an event impact sales, regulation of the specific gun model, or variant gun design (as in TEC9) - then that would ge a reason to cover it in the model. We do not usually document individual use cases in weapon articles - it would become an unmanageable list for some.Icewhiz (talk) 19:29, 21 February 2018 (UTC)[reply]
Oppose as existing guidelines are sufficient, and this should be decided on the article talk page. We can't foresee every possibility, so to set a hard policy or guideline that dictates the content of an article is wrong minded. This is an issue of CONTENT, and guidelines shouldn't be getting this specific on what to include. That is what editors are for. Dennis Brown - 2¢ 19:59, 21 February 2018 (UTC)[reply]
Oppose. Existing guidelines (1B) are sufficient. What will be notable a year from now is hardly discernible today. See: WP:CrystalBall. Meanwhile, we should not conflate all firearms. Besides, a decade ago, every rifle used criminally was an AK47. Even if it wasn't. Now, every rifle used criminally is an AR-15, even if it isn't. The Firearms Project guidelines are sufficient. And, when something becomes notable, then more than a mention becomes important. Miguel Escopeta (talk) 21:27, 21 February 2018 (UTC)[reply]
1-D This seems like an obvious case-by-case basis and any hard rules are just going to create poor articles. Let the editors decide through talk page consensus whether it needs to be mentioned and how much to mention. As an aside the current guideline (1-B) is the worst option. See alsos should not be used to shoehorn links into articles. AIRcorn (talk) 21:54, 21 February 2018 (UTC)[reply]
Generally opposed to making sweeping editorial decisions on an untold (and many as yet unwritten surely) number of articles. This should probably be decided on a case-by-case basis. GMG ^talk 21:58, 21 February 2018 (UTC)[reply]
Oppose. Existing guidelines are sufficient. Regards, TransporterMan (TALK) 22:47, 21 February 2018 (UTC) Clarify: General policies and guidelines, i.e. those unrelated to this specific topic area, are sufficient. - TransporterMan (TALK) 02:01, 22 February 2018 (UTC)[reply]
Comment Currently, these decisions are not being made on a case-by-case basis. When attempts are made to add mass shooting information to an article, the WikiProject Firearms ~~guideline~~ essay is often cited as a "policy" that prohibits anything beyond a "See also" link. –dlthewave ☎ 23:11, 21 February 2018 (UTC)[reply]

The guideline needs to be looked at by the community then, remember that this isn't confined to just the United States in terms of English speaking scope. - Knowledgekid87 (talk) 23:32, 21 February 2018 (UTC)[reply]

Oppose as I also feel the existing guidelines are sufficient. Springee (talk) 01:06, 22 February 2018 (UTC)[reply]
1A, 2A per COATRACK. Please leave your politics on your end of the keyboard. Chris Troutman (talk) 02:06, 22 February 2018 (UTC)[reply]

Exactly, and how do you reconcile disallowing a particular aspect of a subject irrespective of how much coverage that aspect receives with Wikipedia policy and guidelines. IAR "because politics"? — Rhododendrites ^talk \\ 06:27, 22 February 2018 (UTC)[reply]

1C and 2C according to notability. Articles on firearms such as Carcano Rifle, AR-15, Röhm RG-14, etc. that have been used in significant crimes should WP:DUE-ly contain coverage of those crimes. (How is including a couple sentences about the crime - in an article about a type of weapon that was used in a famous crime - being "political"?????) - LuckyLouie (talk) 04:13, 22 February 2018 (UTC)[reply]
1A, 2A. I agree with Chris Troutman. These articles should remain Apolitical.--Limpscash (talk) 05:17, 22 February 2018 (UTC)[reply]

The beauty of Wikipedia's policies and guidelines is that they are apolitical (actually, it's fraught to say that, so let's say they try to be apolitical). We cover a subject according to how reliable sources cover a subject, without imposing our own opinions (political or not) about what aspects of the subject must be covered or must not be covered. — Rhododendrites ^talk \\ 06:29, 22 February 2018 (UTC)[reply]

Oppose (1A/2A) - I am, personally, an extremely strong gun-control advocate, but I don't see where it serves any encyclopedic purpose to list in every firearm article what mass shootings it was used in. However, a specific article about "Mass shootings using X firearm" would be a different matter, and I would support the encyclopedic value of such articles, which would then reasonably be listed in the firearm article's "See also" section. Beyond My Ken (talk) 05:19, 22 February 2018 (UTC)[reply]
1A under the assumption the individual manufacturer's execution of the generic design did not impart any particular advantage or disadvantage in the event(s) described. & 2C If the rifle truly fits within the definition (given the potential problems of using a prototype designation to describe a forked spectrum of improvements which may not be evident to many writers focusing on casualties rather than causes.) The truly important part of the description would be why executioners have chosen this rifle as opposed to a different method of killing (vehicle ramming attack, fire, poison, pressure-cooker bombs, blades, arrows, clubs, etc.) or a different type of firearm (shotgun, handgun, machinegun, semi-automatic rifle, lever-action rifle, bolt-action rifle, pump-action rifle, mortar, etc.) The paragraph should focus on features (sales volume, distribution of ammunition, ease of concealment, weight, range, accuracy, cartridge energy, bullet design, magazine capacity, reloading method, etc.) making this firearm more effective than other firearms (or merely more available than more effective firearms) and the factors making the targets uniquely vulnerable to attack by firearms, as opposed to alternative killing methods, unless firearms are simply more widely portrayed in the popular press as the preferred method for mass killing. Since an appropriately meaningful description might be interpreted as a how-to article on mass murder, we might better keep the description in the event articles to avoid identifying inappropriate uses of inanimate objects. Thewellman (talk) 07:01, 22 February 2018 (UTC)[reply]

1D - ????????????????? How is this not the !vote of every experienced editor in this thread? Coverage of aspects of a subject is based on the weight/prevalence of those aspects in the literature about the subject. Simply because a gun was used in a particular event doesn't mean it should be included. If a great deal of coverage of the subject/gun is about particular ways in which it has been used, that should be included. And everything in between. Both 1A and 1C (and to a lesser extent 1B) are blanket rules that have no connection with the rest of Wikipedia policies and guidelines. We don't ban a particular aspect of a subject when that aspect comprises a major amount of the subject's coverage, and we don't include specific instances of a subject['s use] just because they exist or because it's true. That it was used obviously doesn't need anything more than a mention, if that, but in some cases there's in-depth coverage of the particular weapon used, analysis of a weapon used in multiple attacks, etc. As such 2C is clear in that instance given the incredible amount of sourcing on that aspect of the subject, but that doesn't mean it should be included in all cases. — Rhododendrites ^talk \\ 06:17, 22 February 2018 (UTC)[reply]

To be clear, regarding "How is this not..", I see that some have objected to this RfC and/or expressed opinions along the lines of 1D -- I'm just surprised to see so many 1As in general, and 1Cs without heavy qualification (the sort that basically turns it into 1D). — Rhododendrites ^talk \\ 07:21, 22 February 2018 (UTC)[reply]

Because 1D effectively says "this whole debate must be repeated in every mass shooting talk page". This is a poor use of editors' time. Maproom (talk) 07:33, 24 February 2018 (UTC)[reply]

Oppose any prescriptive outcome of this RFC. Complete WP:UNDUE consolidation of ill-defined information used in an attempt to draw a conclusion via WP:SYNTHESIS or make some kind of political point. Who decides which incidents get listed? Why stop at the model of rifle... why not go to gun and make a section of all shooting deaths? Do you see the inherent absurdity that this proposal can be extrapolated to? I get that people are in the midst of a bit of hysteria on this topic, but wikipedia is not here to "right great wrongs". We're here to be informative, not influential. -- Netoholic @ 08:17, 22 February 2018 (UTC)[reply]
1D I do not see why there must be a general guideline, nor why a project-based essay must be treated as such. Mass killings should be covered in a specific article if they are given significant mention in literature about that topic. That's all. Obviously, for a good many gun types, that means a paragraph; for a good many others, it means nothing at all. Vanamonde (talk) 08:47, 22 February 2018 (UTC)[reply]
- I agree with Vanamonde. There should not be a specific rule at all, it is already covered under existing policy and guidelines such as WP:DUE and WP:RS. This is WP:CREEP, and could create a temptation to WP:BITE. Naturally, people will be curious about a firearm that is used in a mass shooting, and it seems reasonable that they will expect to see some mention in the article. If they don't see it, they might add it. If such an addition is not WP:UNDUE and is well-sourced, there's no reason to remove it. On the other hand, there's no need to impose a formula so that every firearm article has an identical prescribed section on its use in crime. How can we ignore all rules when there are so many of them? Jack N. Stock (talk) 09:07, 22 February 2018 (UTC)[reply]
Support 1 C - When RS coverage of the weapons used exists, it belongs in the article.E.M.Gregory (talk) 12:48, 22 February 2018 (UTC)[reply]
Oppose as I really do not see why this is relevant. It may well be verifiable, but seems to me we are making a special case with guns (after all do we do this with makes of knives or swords?). In fact I do not think (as I imply) that I do not see why this is ever relevant to a make of gun.Slatersteven (talk) 16:25, 22 February 2018 (UTC)[reply]
1D, 2C this should be determined on a case-by-case basis, depending on the coverage and sourcing for particular weapons and particular incidents. In general, I think if many of the sources about the weapon draw attention to its use in an event then this should push towards including a brief description of the event in the article. On the other hand, if the only sources making the link are descriptions of the event that merely mention the type of gun used, then the event shouldn't be brought up in the gun model's article. In the case of AR-15 style rifles, I think the number of sources specifically about them and their use in mass shootings has probably reached the point where this connection should be mentioned in the article itself. Red Rock Canyon (talk) 16:48, 22 February 2018 (UTC)[reply]
1C, 2C The fact that civilian access to AR-15 pattern rifles is politically controversial is just that, a fact. That controversy doesn't wash away when you spin off daughter articles dedicated to specific brands. The Colt AR-15, is clearly an AR-15, it's a progenitor of the design. Yet some are arguing that policy issues around AR-15s generally shouldn't be mentioned in the Colt AR-15 article if the sources never specify a brand. This is not NPOV. Geogene (talk) 17:08, 22 February 2018 (UTC)[reply]
1A, 2C (with limited discretion on individual articles) We shouldn't mention that John Wesley Hardin or Billy the Kid used a .44 Colt, we shouldn't mention the Dirty Harry quote on .44 Magnum, and we shouldn't mention mass shooters on page about that specific brand of firearm. For lack of a better term, it's "negative promotion", and we should avoid it the same way we would avoid including normal promotion. I do feel it's absolutely necessary to talk about the general trend on AR-15 style rifle. power~enwiki (π, ν) 17:24, 22 February 2018 (UTC)[reply]
Unless the incident had relevance to the gun (i.e. legislation, design changes, etc.), it is generally well-intentioned WP:Coatracky to gather individual criminal events in the gun article. According to Gun_violence_in_the_United_States, Approximately 1.4 million people have been killed using firearms in the U.S. between 1968 and 2011. Even if you try to limit it to events with 'major news coverage', it's just a permanently growing craplist. Just because the gun is important to the criminal-event topic doesn't mean the criminal-event is important to the gun topic. Alsee (talk) 22:46, 22 February 2018 (UTC)[reply]
1D, 2C. AR-15 style rifle in fact redirects to modern sporting rifle. If the category is broad like that, then discussion of the use of modern sporting rifles in mass shootings is appropriate, as Assault weapon (but not Assault rifle, for good reason) contains political and legal information about the previous ban. The use of AR-15 style rifles in mass shootings is a subject gaining substantial RS coverage and it should be mentioned. For 1, however, I think the decision should be made on a case-by-case basis. For example, Charleston shooting mentions the Glock 41 but the Glock article does not. Carcano mentions the Kennedy assassination and probably always will. Roches (talk) 00:08, 23 February 2018 (UTC)[reply]
Do like everything else and require coverage in reliable secondary sources. Do the secondary sources deem a specific shooting an important incident in the history of the firearm? Remember that news reports are primary sources, and most journalists are not reliable sources for this subject: reliable secondary sources in this field are scholars publishing well after the fact and relying on primary sources like news reports. This will weed out the political/coatracky type stuff without excluding the occasional momentous incident. Nyttend (talk) 04:56, 23 February 2018 (UTC)[reply]
Please clarify "C. Include a paragraph-style section", do you mean a simple reference to each such crime in paragraph form such as is currently the the case in Modern sporting rifle or do you intend that a paragraph be added per crime, or somewhere in the middle? Cavalryman V31 (talk) 06:53, 23 February 2018 (UTC)[reply]

Dlthewave, as the nominator please can you clarify the above? Cavalryman V31 (talk) 11:17, 26 February 2018 (UTC).[reply]

The format used at AR-15 style rifle and SIG MCX is what I had in mind for most firearms: List the most notable shootings and briefly discuss legislative changes or other significant effects, with links to more in-depth coverage. However, AR-15 style rifle could include a longer Cultural Impact section similar to AK-47. –dlthewave ☎ 13:27, 26 February 2018 (UTC)[reply]

1C & 2D. A discussion about a specific page's content belongs on that page's talk page. Cavalryman V31 (talk) 14:26, 26 February 2018 (UTC).[reply]

Our existing polices are not broken and do not need fixing. The particular policy that applies here is WP:UNDUE, and this particular situation is described in WP:COATRACK. --Guy Macon (talk) 16:47, 23 February 2018 (UTC)[reply]

WRONGLY POSED QUESTION: There cannot be a general solution to this question, since the sources about the weapon in each case will have to determine whether the coverage of use in specific events is notable enough to include. It is completely wrong to seek to get a general across the board solution for this. Policy very clearly tells us that the SOURCES are what guides us in determining what is sufficiently relevant to include in the article. We do not need a general decision on this.·maunus · snunɐɯ· 16:46, 23 February 2018 (UTC)[reply]

1D but the option feel for 2 is not there. In general, just because X was part of a crime does not necessarily make X notable, nor does it need to be the case to call out the crime on the article about X if it is already notable. X here can be anything - a firearm, a vehicle, software, whatever. However, if it is the case that X is specifically talked about after the crime where people are calling for legislation, regulation, or if the manufacturer takes steps specifically in response, etc. then the event can be named. A good example, Discord (software) was called out for harboring alt/far-right servers which were use to organize the "Unite the Right" rallys that became violent. In direct response, the developers affirmed new TOS and kicked out those servers. Same logic applied to guns. As for the second question, this is where we need sources that discuss broadly the number of crimes that the specific weapon has been linked to and if that has become a point of contention for the weapon. Just because the gun has been named as the weapon in numerous crimes, it is SYNTH to argue for a paragraph about that unless we have reliable secondary sources making that criticism about the gun. This is a case-by-case decision, and not listed among the options. --Masem (t) 16:57, 23 February 2018 (UTC)[reply]
1C / 1C , based on existing guidelines. I would also recommend specifically rejecting the current WP:GUNS section on the topic which has been used in the past to specifically exclude such material from articles based on project-specific consensus, including in very notable cases. For example, the use of Colt AR-15 semi-automatic rifle in the Port Arthur massacre led to the enactment of the National Firearms Programme Implementation Act 1996. Under the present WP:GUNS content guide, this would only warrant a "See also" link. Other samples:

In contrast, here are two prior RfC which concluded with "Include":

Talk:Ruger_Mini-14#Rfc:_Add_major_incidents_to_article?, in Ruger_Mini-14
Talk:SIG_MCX/Archive_1#RFC:_Is_the_Orlando_shooting_relevant?, in SIG MCX. Note that this 2016 RfC is on the same article is in one of the diffs above, removing (in 2017) the content per "per Wikipedia:WikiProject Firearms".

I see such a project-specific consensus to be not conducive to building a neutral encyclopedia. K.e.coffman (talk) 08:11, 24 February 2018 (UTC)[reply]

In as much as this question has an answer, it's clearly 1D/2C, but it's rather disappointing that this is being presented as if it's some kind of overall question about inclusion of trivia, when actually it's all about trying to play down the role of ~~assault weapons~~ modern sporting rifles in mass shootings. That might be what the NRA want, but we are a neutral encyclopaedia and right now the main reason people are interested in that article is that it is the weapon of choice of American mass shootings. Which is to say: mass shootings, since almost all of them happen in America. If anyone is looking up the article on the AR15 right now it is almost certainly to answer the question: why is this weapon front and centre in the current debate over gun control in America. It's kind of hard to answer that question without discussing it, which is of course precisely why the NRA came up with its always-too-soon narrative on discussing gun control. We should have a policy page: Wikipedia:Wikipedia is not Newspeak. Guy (Help!) 09:00, 24 February 2018 (UTC)[reply]
- We must take care to avoid the narrative of the gun control lobby as well as the narrative of the NRA. For example, we know that some terrorists/mass murderers use guns, we know that some terrorists/mass murderers use bombs, and we know that some terrorists/mass murderers use trucks. Yet our article on Mercedes Benz doesn't mention the many times that brand of truck was used in an attack, and our article on Vehicle-ramming attack and our articles on individual vehicle-ramming attacks don't appear to mention what kind of truck was used. Nor do we ephasise what kind of explosive was used in the making of the bombs. Yes, some guns are better or worse choices for shooting up a school, but it is also true that some trucks are better or worse choices for plowing into a crowd. The ASR15 is front and center in the current debate over gun control in America because the gun control advocates want to make that particular weapon illegal even though other weapons are just as capable of being used in a school shooting (for example, a sawed off semi-automatic shotgun would be far more effective at such close ranges). If we are to be a neutral encyclopaedia, we should not let the pro-gun or anti-gun lobbies decide what the narrative is. --Guy Macon (talk) 09:37, 24 February 2018 (UTC)[reply]
  - I agree with all of this but would throw in a consideration of WP:RECENTISM. If just now the debate is above banning the ASR15 due only to the recent school shooting, it might be too soon to consider including it because of the nearness of the event. If in a month that debate is still going, then that issue has legs and inclusion is reasonable per Guy's logic related to UNDUE/WEIGHT and staying neutral. But if this debate evaporates in a few weeks, it might not be appropriate to include. On the other hand, if the ASR15 has a history of people wanting to ban it after shooting events like this, then its reasonable to discuss that as a whole. (I just had to do similar with video games after Trump's statement this week; games have been attributed in several past shootings including Sandy Hook - though here, no specific games, just the form in general). --Masem (t) 14:31, 24 February 2018 (UTC)[reply]
1C or 1D (which probably amount to the same thing, because use in a mass shooting is likely to have attracted a lot of RS about the gun) and 2C. These articles are subject to the content policies like any other. Therefore, if a gun is used in a mass shooting and there is coverage in RS about the gun as a result of that, it belongs in the article, preferably in its own sub-section. If there's a lot of coverage it belongs in the lead too, per WP:LEAD: "It should ... summarize the most important points, including any prominent controversies." Wikipedia:WikiProject Firearms#Criminal use should be rewritten to reflect policy. SarahSV ^(talk) 19:08, 24 February 2018 (UTC)[reply]
1C/1D I would surmise by extrapolation reading Derringer perma-link, and the prominent picture concerning its most famous killing. As for question 2, go to the article talk page where all the sources can be discussed and have consensus decide based on those. Alanscottwalker (talk) 19:52, 24 February 2018 (UTC)[reply]
1C, 2C - we include exhaustive lists of notable incidents for aircraft, I don't see why notable incidents involving specific firearms should be treated any differently. Ivanvector (^Talk/_Edits) 12:16, 26 February 2018 (UTC)[reply]
Case by case. The key point is how much was the specific model discussed by reliable sources in reference to the shooting. If reliable sources merely mention that shooter happened to use this model, but didn't go into detail, and imply it might as well have been any other of a dozen models, we probably do not want to mention it at all; they might as well mention the kind of car the shooter drove up in. If reliable sources say the impact that the shooting had on the company or sales of the model, we might want to have a sentence. If reliable sources state or imply that the specific item was an important factor in the event (like the bump stocks in the Las Vegas shooting), then we want a paragraph or more. --GRuban (talk) 17:06, 26 February 2018 (UTC)[reply]
1C, 2C - Mass shootings are highly notable, and the weapons used are highly noteworthy. There may be rare exceptions to 1C, for example where a firearm is so generic and common (e.g. Glock n) or several firearms are involved, but some did not have a significant role in the shooting. Notably, some of these firearms articles read like product brochures and are overly-dependent on primary sources from the manufacturer. Adding information about how products are used (or misused) would tend to make the articles more well-rounded and compliant with WP:NPOV.- Mr X 🖋 22:38, 26 February 2018 (UTC)[reply]
1D, 2D Both depend and should be on a case by case basis. Emir of Wikipedia (talk) 22:51, 26 February 2018 (UTC)[reply]

straw poll update

Just an count of what we have so far, people can of course continue contributing/!voting. 42 people have posted so far, (as of Alanscottwalker @ 19:52, 24 February). There is a mixture of results, because of all the options and the way the RfC is written. Of the 42, 4 are clearly not !notes, but a question, a criicism and 2 comments, which leaves 38 !votes which so break down as follows;

Oppose - 7
Oppose (support 1B) - 3
Oppose ("unless relevance to the gun, ie: law changes") - 1
Oppose (support 1A/2A) - 1
1A/2A - 4
1A - 1
1A/2B - 1
1A/2C - 1

"if sourced" 1C, "if not" 1B/2C - 1
1C - 2
1C/2C - 5
"situational" 1C/2C - 1
1C "or" 1D - 1
1C/1D - 1
"depends" 1D/2C - 1
1D/2C - 3
1D - 4
(other)
- "do like everywhere else"
- "comment"
- "please clarify C"
- "wrongly posed question"

Carry on. - ^theWOLFchild 22:20, 24 February 2018 (UTC)[reply]

If we're compiling !votes, it might be useful to have one set of totals for each question instead of tallying up all of the possible combinations. –dlthewave ☎ 23:52, 24 February 2018 (UTC)[reply]

Go right ahead. I just listed what was there, !votes that were the same were added up, !votes that had any variation or distinction, were noted separately. It's by no means meant to be official, final or even determinative. It's just for anyone curious to see what kind numbers are in so far. Cheers - ^theWOLFchild 04:26, 26 February 2018 (UTC)[reply]

Threaded Discussion: Coverage of mass shootings in firearms articles

Just a quick question on item 1. Is it asking if information should be included on say the Colt AR-15 article even if it was not a Colt AR-15 used but another AR type rifle? PackMecEng (talk) 17:24, 21 February 2018 (UTC)[reply]

No, I would consider that to be a separate discussion –dlthewave ☎ 17:57, 21 February 2018 (UTC)[reply]

On second thought, I would consider that to be part of item 2.

It would be undue to include the complete list of murders and massacres committed with AR-15 type rifles. But it would be disingenuous to not have a single mention of the ubiquity of the AR-15 type rifle in the Colt AR-15 article. And the whole Kleenex/paper tissue argument is just a red herring: you can't have an AR-15 type rifle without the original AR-15; not mentioning it (prominently, in the lead, since it is that well-sourced and that important) does no service to the reader and is intellectually dishonest. We do not need to defend Colt, and including a neutrally written paragraph is no attack on Colt, who I am sure are well aware of this matter. It is our job to inform the reader about where these guns come from and what their relation is to the "original". Drmies (talk) 18:16, 21 February 2018 (UTC)[reply]
I just want to state for the record that I oppose the idea of putting a list of school shootings in the "See also" section for gun articles. The event in question either had an impact on the gun or it didn't. - Knowledgekid87 (talk) 18:33, 21 February 2018 (UTC)[reply]
Didn't we have this discussion at some time in the past? What was the results of that discussion? I'm sure there's an old RFC out there that was about this exact issue. If someone remembers it as well, and knows where to find it, reading it may give some insight into the existing community consensus on this. --Jayron 32 18:54, 21 February 2018 (UTC)[reply]

That is a significant part of the problem here. Every now and then, a small groups of editors have discussions on various talk pages which often result in a "local consensus", that they then try to rely on when making edits to other pages. Edits that often come in conflict with the "local consensus" established by yet another small group from a different talk page. We need a one-time, centralized discussion with a solid community-wide consensus that can also be written into the guideline (or policy), so that going forward, we can actually rely on that guideline or policy, and not another local consensus cooked up by a yet another small group of editors. At least 3 such discussions started on 3 different pages. They were closed and directed to the talk page of the project that the articles fell under the scope of. There was a discussion going there, but suddenly, it seems we're having it here now. - ^theWOLFchild 19:38, 21 February 2018 (UTC)[reply]

@Jayron32: Here's a relevant RfC that was held on a Talk page of a firearm article: Talk:Ruger_Mini-14#Rfc:_Add_major_incidents_to_article?. The result was "Include". K.e.coffman (talk) 23:39, 21 February 2018 (UTC)[reply]

I recall that one, it was close. Here is another recent RfC. The result was exclude. The results were also close. [[22]]. Here is a related RfC about adding use in crimes to automotive pages. Interesting that since it was about automobiles instead of guns, the results were strongly against inclusion.[[23]] In that RfC, claims of censorship were made as were WP:NOTE. Both are effectively addressed by the idea that not everything has to go in every article. No material is being excluded as it appears in the articles about the topic. Springee (talk) 01:05, 22 February 2018 (UTC)[reply]

These two RfCs mentioned directly above (by K.e.coffman & Springee) completely validate my previous comments about conflicting local consensuses. Any group of 5 or 6 pro-gun guys can put together a pro-gun consensus on a particular issue on one page, while at the exact same time, 5 or 6 anti-gun guys can put together an anti-gun consensus on another page, about the same issue. This is one of the reasons we have projects, and the appalling lack of faith and baseless accusations of bias have basically negated the very project that covers this topic and now we're having debates all over the place. What's next? - ^theWOLFchild 01:54, 22 February 2018 (UTC)[reply]

If it wasn't a Colt AR-15 then no, it shouldn't be mentioned. We have a parent article about AR-15s (which seems to be changing names quite often) then we have this article about one particular model. If the crime didn't involve this model why would we even consider linking the two. It's like linking James Dean to the Mustang he didn't drive to his death. Springee (talk) 19:24, 21 February 2018 (UTC)[reply]

To me, trying to pin people down would go against our WP:Editing policy by imposing a global rule where it should depend on the circumstances and the consensus of editors. Thus I would stick with my original opposition. Dennis Brown - 2¢ 00:23, 22 February 2018 (UTC)[reply]

@Masem: the reason question 2 doesn't have a "maybe" option is that it deals with only one article (which currently, but not for much longer, resides at modern sporting rifle). ansh 666 02:25, 24 February 2018 (UTC)[reply]

If the information to be included in the generic firearm article doesn't describe the why as explained above, I would change my response to 2B since mere identification seems comparatively trivial. I am concerned about the preponderance of reliable sources treating mass murder as a macabre competition by describing events as a US record or annual record. Professional and amateur contenders are differentiated by exclusion of events like the My Lai Massacre and the Waco siege. Perhaps the next step will differentiate individual achievement from team participation events like the Columbine High School massacre or the 2015 San Bernardino attack. This competitive focus may encourage individuals with self-esteem issues to seek recognition by achieving a higher body count using similar methods. Thewellman (talk) 20:11, 24 February 2018 (UTC)[reply]

Why? Why do we discuss jello shots in Jell-o, it's something people do with it that RS talk about. Alanscottwalker (talk) 21:12, 24 February 2018 (UTC)[reply]

I don't understand the basis for comparison. I suppose we discuss jello shots in the Jell-o article because there does not appear to be a separate article for jello shots, while this discussion involves potential duplication in the event article and the firearm article. Thewellman (talk) 00:24, 25 February 2018 (UTC)[reply]

No. We also discuss jello shots in Gelatin dessert -- we discuss many (most?) things in more than one article because that's how encyclopedic topics work. And really, you don't understand, it's something people do with it that RS talk about. Alanscottwalker (talk) 00:41, 25 February 2018 (UTC)[reply]

Some may not understand the value of links to avoid a duplicated description at every mention of an unfamiliar term, and separated sources without Wikipedia's spectrum of information may require independent discussion because of a lack of linking options. I acknowledge the benefit of a separate description if sources describe firearm characteristics significant in the context of that event, but I consider a simple tabular link adequate if sources merely identify the firearm. Thewellman (talk) 22:39, 25 February 2018 (UTC)[reply]

Coverage of mass shootings: RfC wording & prior RfC

Comment -- I have concerns about the structure of this RfC and the language used, which can lead to misunderstandings. For example, [[Relevant WikiProject Firearms [[Wikipedia:WikiProject Firearms#Criminal use|guideline]] is presented as a guideline. This is, in fact, a project-specific essay and does not supersede actual policies and guidelines, such as WP:NPOV or WP:NOT. This language has been included in the RfC and several !votes (emphasis mine):

B. Include links to notable shootings in the "See Also" section (Current WikiProject Firearms guideline) (language in the RfC)
Oppose - any changes to the current policy (noted as "1B")
Oppose. Existing guidelines (1B) are sufficient.

Some of the resulting votes are therefore subject to varying interpretations. For example:

Oppose: as existing guidelines are sufficient, and this should be decided on the article talk page.

this could be read as "Oppose, use WP:NPOV instead" or "Oppose, use WikiProject Firearms guideline" (I think it's the former, but if you look at vote #3 above, it's also an oppose based on a "guideline". ping @Dennis Brown: for clarification.

The selection of prior discussions also appears to be limited. I therefore suggest that:

a. the language in the RfC be changed to [[Relevant WikiProject Firearms [[Wikipedia:WikiProject Firearms#Criminal use|essay]] & "B. Include links to notable shootings in the "See Also" section (per Current WikiProject Firearms essay)"

b. this past page-specific RfC be added to the section on "Relevant talk page discussions": Talk:Ruger_Mini-14#Rfc:_Add_major_incidents_to_article? permalink. I believe that the RfC is relevant since it addressed the same question.

Ping @Dlthewave: as the author of the RfC to see if these two changes can be made. I don't think we should be conflating project-specific recommendations with community policies and guidelines. K.e.coffman (talk) 23:25, 21 February 2018 (UTC)[reply]

Thanks for the suggestion, I've made the requested changes. –dlthewave ☎ 23:53, 21 February 2018 (UTC)[reply]

So, after numerous editors have posted !votes with attached comments in the RfC straw-poll, the wording of the RfC is now going to be changed? wow... - ^theWOLFchild 01:59, 22 February 2018 (UTC)[reply]

- I've already clarified above. This kind of hamstringing goes against WP:Editing policy, which is a policy. Let editors decide on a case by case basis. Twice I've been asked to explain, but my objection is much simpler than it is being made out to be. Dennis Brown - 2¢ 02:31, 24 February 2018 (UTC)[reply]

Possible Wikipedia:Canvassing

K.e.coffman added this notice to the Wikipedia:Fringe theories/Noticeboard.

RfC notice: Coverage of mass shootings in firearms articles
An RfC relevant to this project has been opened at:

Wikipedia:Village pump (policy)#RfC: Coverage of mass shootings in firearms articles

Interested editors are invited to participate. --K.e.coffman (talk) 01:23, 22 February 2018 (UTC)

Thanks, but... how does this relate to fringe theories, which are the focus of this noticeboard? Shock Brigade Harvester Boris (talk) 01:25, 22 February 2018 (UTC)

I too wonder..."how does this relate to fringe theories, which are the focus of this noticeboard?"--RAF910 (talk) 02:16, 22 February 2018 (UTC)[reply]

@Shock Brigade Harvester Boris: I've been advised by a WikiProject Firearms member in this discussion that nothing stopping you from posting notifications on the "WP:NPOVN or WP:VP" talk pages, or anywhere else for that matter, to involve as much of the community as possible. I assume various noticeboards qualify as "as much community as possible". However, I'd be happy to remove the notice if there's a concern. K.e.coffman (talk) 02:24, 22 February 2018 (UTC)[reply]

No concern at all. My first thought was that there might be some kind of fringe/conspiracy angle to the RfC that I had missed. So I was a bit puzzled but now see that you simply were casting the net as wide as possible. In any event accusations of canvassing are off the mark. I can't see how participating at WP:FTN implies a view one way or the other on issues like gun control, or favored firearm brands, or anything else related to the RFC. Shock Brigade Harvester Boris (talk) 02:36, 22 February 2018 (UTC)[reply]

I was the one that made that comment. That was of course, in support of having the discussion on the project talk page where it belongs in the first place, and where it had been moved to once already, (3 times actually), and where it had already begun, and where several editors had already contributed. I made that comment in response to your claims that editors from the Firearms Project were "biased" and that it wouldn't be possible to have a fair discussion there. But the discussion has since been moved (yet again) to this page, (though I'm not entirely sure why, possibly to quiet your concerns and accusations I suppose). So now that that the discussion (and RfC) is on "neutral ground", your multiple notifications are needless and indeed bordering on canvassing. You've also posted notices at Wikipedia talk:WikiProject Crime and Criminal Biography and Wikipedia talk:WikiProject Death. Where else are you going to post notices? "WikiProject:Mothers Against Guns"? At what point could one be considered "getting carried away" with all this? - ^theWOLFchild 03:28, 22 February 2018 (UTC)[reply]

I have not participated at all in this little kerfluffle but it's hard to imagine those notifications as canvassing. Why would participants at either of those two projects be biased one way or the other on the subject of this RFC? Shock Brigade Harvester Boris (talk) 04:22, 22 February 2018 (UTC)[reply]

If you suspect canvassing, you should follow the process at WP:CANVASS. Bring it up on the user's talk page and take it to ANI if it continues. This is not the appropriate place to discuss.–dlthewave ☎ 04:31, 22 February 2018 (UTC)[reply]

User:K.e.coffmans notice to the Wikipedia talk:WikiProject Crime and Criminal Biography is appropriate, because we are talking about crime. His notice to the Wikipedia talk:WikiProject United States seems reasonable, because this is a major issue in the U.S. right now. His notice to the Wikipedia talk:WikiProject Death is a stretch, but I can see it. His notice to the Wikipedia:Fringe theories/Noticeboard, I wonder about that one myself. Also, there’s nothing wrong with shining light on this matter here and asking involved editors for their opinions. That's what we're suppose do here.--Limpscash (talk) 05:51, 22 February 2018 (UTC)[reply]

Posting to the Fringe and Paranormal noticeboards can be a form of canvassing. For example, Wikipedia:Articles for deletion/John Traynor (Royal Marine) was posted at Wikipedia:WikiProject Deletion sorting/Paranorma. Traynor was a Lourdes pilgrim, an ex-soldier from Liverpool crippled by a wound during WWI who announced that he had been miraculously cured at Lourdes in 1923, an era when pilgrimage to Lourdes was a mass phenomenon; a mainstream Catholic religious practice. The Traynor story turned out to be unusually well sourced; SIGCOV in both popular and academic books and in major newspapers ongoing for over a century. Yet when I began to clean up and source the page, I was assailed by accusations of "adding sources written by believers into the article that support fringe claims. This is a problem for WP:Fringe." Similar attacks on Young Earth creationism, a religious beliefs that is mainstream in some Muslim and Christian circles, but Wikipedia:Articles for deletion/Is Genesis History?, about a film supporting Young Earth creationism, was posted at fringe. It is, of course, an "theory," with no support among scientists. The problem is that the debate was not an evaluation of notability. After it was posted at Fringe theories/Noticeboard, editors arrived who treated the AfD as a debate about ""A fringe subject... inside the creationist universe.", asserting that "The fact that it is a film promoting a fringe theory and not an article about the theory itself doesn't really change anything." which as closing editor said, shifted the discussion to the question of "do we apply the notability standards for fringe theories (which require sources independent from those associated with the theory), or for other subjects like films (which just require reliably sourced coverage independent from the subject itself, i.e., the film)?" As with the current AfD Wikipedia:Articles for deletion/The Spark: A Mother's Story of Nurturing Genius, the point of posting an article about a film, a book or a Lourdes pilgrim to the fringe or paranormal' boards appears to be to draw the attention of true believers who take up the cudgels, against Young Earth creationism, against ways of conceptualizing autism, against Lourdes water, against the lack of effective gun control. In other words, for a certain range of issues, posting at fringe and/or paranormal is effectively a type of canvassing that brings out holy warriors to join the crusade against... whatever is intensely disliked. They rush to articles posted at these boards and iVote delete without - as is very clear at Wikipedia:Articles for deletion/The Spark: A Mother's Story of Nurturing Genius - arguing that editors should IGNORE ALL RULES, in comments that too often show that they have not read the policies or the sources that they cite. E.M.Gregory (talk) 11:11, 22 February 2018 (UTC)[reply]

In this case, however, the post at FTN was NOT canvassing. It was a simple notification, phrased in neutral language. Blueboar (talk) 11:34, 22 February 2018 (UTC)[reply]

Posting on a noticeboard unconnected with the topic of the AfD can be a form of canvassing if the point of posting there is to attract a group of editors likely to share the posting editor's perspective. User:K.e.coffman has responded that there is no bar on posting to noticeboards, but has not explained his reasons for posting to this particular noticeboard, and, as I explain above, it such postings can skew discussions.E.M.Gregory (talk) 14:04, 22 February 2018 (UTC)[reply]

In order for requesting outside input to be canvassing, it has to be done with the intent to selectively recruit participants to sway the result one way. Maybe on some subjects simply alerting the fringe noticeboard could be canvassing, but I can't for the life of me guess what bias regulars on the fringe noticeboard would bring to this particular discussion. The topic is completely unrelated. That certainly makes the decision to request input there odd, but it was a completely neutral notification that the discussion exists. Unless you have an argument about how this particular instance constituted a deliberate attempt to fill the debate with anti-gun editors, calling it canvassing would really be assuming bad faith on K.e.coffman's part. Your argument amounts to: "It happened before, so it's also happening now. He hasn't explained himself, therefore he's clearly up to no good." Red Rock Canyon (talk) 20:32, 22 February 2018 (UTC)[reply]

I have been volunteering at the Fringe Theories Noticeboard for several years. Can someone please tell me what my political position should be, and what things I should "intensely dislike", because I didn't get any instruction in that regard. - LuckyLouie (talk) 23:35, 22 February 2018 (UTC)[reply]

I think you are expected to be against fringe weapons, and in favor of mainstream ones. So no mention of mass murders in any article about Tesla’s “death ray” (or even “Tesla style death rays”). ;) Blueboar (talk) 02:58, 23 February 2018 (UTC)[reply]

Page move request notice

User K.e.coffman has moved Modern sporting rifle to "AR-15 style rifle" without first seeking consensus. As a controversial and contested page move, made while related discussions were actively taking place (including here, hence this notice), the page has been moved back and a proper page move request has now been posted. Please see Talk:Modern sporting rifle#Requested move 22 February 2018 for more information, and if you wish to participate in the page move discussion. - ^theWOLFchild 03:03, 22 February 2018 (UTC)[reply]

@K.e.coffman: - You should take some time to cool down, this is the second thing I have seen you involved in here. Just hope the editing isn't getting to you is all. - Knowledgekid87 (talk) 03:09, 22 February 2018 (UTC)[reply]

questions about the the Retrieved date on a citation

What is the purpose and the update process for the Retrieved date on a citation?- Bevo (talk) 22:15, 25 February 2018 (UTC)[reply]

If it is online, web sites change content on their pages, so it is helpful for other editors to know what version of the URL was intended in the citation. Even news stories change online. Also, if the source is no longer available, it helps someone find a good archived copy, hopefully the same version that was originally cited. Jack N. Stock (talk) 22:58, 25 February 2018 (UTC)[reply]

Agree with Jack N. Stock. I'd add that if you are thinking of updating the retrieved date, you should verify that the version of the website you are reading still supports the statement in the Wikipedia article. It's always possible that the source never really supported the statement, or it used to at the time the citation was added, but the web site has changed. Jc3s5h (talk) 23:56, 25 February 2018 (UTC)[reply]

Dating and other relationships

Do any of the guideline pages cover when to report that people are dating? I'm asking in connection with a series of edits over the last few months at Brandon Flynn and Sam Smith (singer). Following the posting of photos last fall of the two of them kissing, there were a flurry of claims in these articles that the two were dating. I reverted them, as they were unsourced (though I could find sources myself, but those were just snapshots and gossip), and who even knows whether a couple pictured together for the first time last week are still together this week? Now, several months later, it's fairly well established in sources that they're dating, but is that still to be mentioned in either article? And, now, someone added Sam Smith as "partner" in the Brandon Flynn infobox. With no source. I'm assuming that people aren't partners until a reliable source says so, right? Anyway, even though I'm not second-guessing my actions, I figured I'd find out whether this is all covered somewhere already. Largoplazo (talk) 03:44, 27 February 2018 (UTC)[reply]

Decisions about what information to include or not include in an article is subject to both reliable sourcing and consensus. One or the other is NOT enough. It should be handled on a case-by-case basis and decisions should be made based on discussion on the article talk page where there is some disagreement. Don't let anyone say "because I have a reference, this MUST be in the article" or get upset about "removal of sourced information" or some such. Having a source is a necessary but not sufficient condition for putting some information in an article, there also needs to be agreement that the information is relevent. I have no opinion one way or another on this specific bit of information, but that decision has to be reached (in consultation with the sources; the type of source and depth of coverage is good evidence of relevence, for example) by discussion and no policy at Wikipedia will ever be able to bypass the need to discuss and reach consensus. --Jayron 32 13:03, 27 February 2018 (UTC)[reply]

[1] The Times Comprehensive Atlas of the World (14th ed.). HarperCollins UK;. 2014. p. 23. ISBN 0007551401.{{cite book}}: CS1 maint: extra punctuation (link)

[1]

@@ Line 86: / Line 86: @@
 == Guidance on removing comments from closed discussions ==
+<div class="boilerplate" style="background-color: #EDEAFF; padding: 0px 10px 0px 10px; border: 1px solid #8779DD;">{{Quote box
+  | title =
+  | title_bg = #C3C3C3
+  | title_fnt = #000
+  | quote = The consensus here is that closed discussions (i.e. those discussions to which a closing or archiving box has been applied in good faith) are intended to be preserved as-is, and may not be edited. Subsequent good-faith edits inside the box should be moved outside the box. Comments should ''not'' be reverted for this sole reason, but may qualify for removal for reasons described at [[WP:TPO]]. [[User:Ivanvector|Ivanvector]] (<sup>[[User talk:Ivanvector|Talk]]</sup>/<sub>[[Special:Contributions/Ivanvector|Edits]]</sub>) 15:01, 27 February 2018 (UTC)
+  | width = 30%|halign=left}}
+:''The following discussion is closed. <span style="color:red">'''Please do not modify it.'''</span> Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.''<!-- from Template:Archive top-->
+----
 Just a few minutes ago, I [https://en.wikipedia.org/w/index.php?title=Wikipedia:Village_pump_(policy)&diff=prev&oldid=822780391 reverted] a commented added to a closed discussion (the RfC above about airline destinations).  My revert was then [https://en.wikipedia.org/w/index.php?title=Wikipedia:Village_pump_(policy)&diff=next&oldid=822780391 reverted] by {{u|Mandruss}}, citing [[WP:TPO]].  The language on the RfC closing template seems to contradict WP:TPO.  Can anyone help clarify what should be done here?  Thanks.  &ndash;[[User:Deacon Vorbis|Deacon Vorbis]]&nbsp;([[User Talk:Deacon Vorbis|carbon]]&nbsp;&bull;&nbsp;[[Special:Contributions/Deacon Vorbis|videos]]) 14:12, 28 January 2018 (UTC)
@@ Line 123: / Line 130: @@
 *'''Keep''', outside the box.  It is useful to have, for example, a link to a further discussion about implementing the agreed action, without it being either removed on procedural grounds or mistaken for part of the decision process. [[User:Certes|Certes]] ([[User talk:Certes|talk]]) 15:31, 1 February 2018 (UTC)
 *'''Keep''' but '''move outside the box'''.  (Technically, that's moving the ''box'' and/or the comments in it, in a relativistic way)  The whole "[[WP:consensus can change]]" thing implies that no discussion is ever truly closed - only the box is closed. [[User:Wnt|Wnt]] ([[User talk:Wnt|talk]]) 12:24, 15 February 2018 (UTC)
+----
+: ''The discussion above is closed.  <b style="color: #FF0000;">Please do not modify it.</b> Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.''<!-- from [[Template:Archive bottom]] --></div><div style="clear:both;"></div>
 == Rfc: Change default <nowiki><math></nowiki> to be inline ==